Announcement

Collapse
No announcement yet.

[AMD64-desktop] iMac aluminum keyboard freezes when booted from CD.

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [AMD64-desktop] iMac aluminum keyboard freezes when booted from CD.

    Hey,

    I'm having a problem getting past the first options when the image is
    booted from CD. Interestingly, the options against 1 and 2, have no
    labels and the keyboard freezes but the cursor blinks.

    I created and verified the amd64 CD image and then checked the MD5
    which all checked out OK. I'm under the impression that it should work
    as AMD creates it's chips from Intel specifications anyway.

    Are their compatibility issues with iMac?

    System.
    iMac 17" (late 2006)
    Intel duo2 1.83 GHz

    #2
    Additional...

    Just tried i386-desktop and it seems to show no problems of booting
    from the CD.

    Comment


      #3
      amd64 is just the term for the 64 bit architecture - Intel uses the same and it runs fine on Intel chips.

      But I believe that not all Intel Core 2 Duo (I assume that's what you mean) chips are 64-bit capable.

      Since the i386 version boots to the live desktop, run the following command and post the output here. Please use [code][/code] tags around the output!

      Code:
      cat /proc/cpuinfo
      I'd rather be locked out than locked in.

      Comment


        #4
        The Core2Duo T2400 in your iMac is a 32-bit processor, I'm afraid.

        http://ark.intel.com/products/27235/...z-667-MHz-FSB)
        Last edited by wizard10000; Feb 10, 2012, 08:08 AM.
        we see things not as they are, but as we are.
        -- anais nin

        Comment


          #5
          Originally posted by SecretCode View Post
          run the following command and post the output here
          Or you could just look it up like wizard1000000000000000 did. Never mind then!
          I'd rather be locked out than locked in.

          Comment


            #6
            Originally posted by SecretCode View Post
            Or you could just look it up like wizard1000000000000000 did. Never mind then!


            Figured I'd save him the trouble - I wanted to know which C2D processors are 32-bit too
            we see things not as they are, but as we are.
            -- anais nin

            Comment


              #7
              Thanks for all the replies, but...

              After having the above problems and then the Software Manager
              continuously crashing in i386, I burned a x86_64 version of KDE
              openSUSE and it's purring along. I've also been using 64bit builds
              in OSX for years with no complaints.

              I'll try and pull off the processor details from openSUSE and get
              back soon.

              Comment


                #8
                Right then... Looks like a T5600 chip...
                Code:
                processor       : 0
                vendor_id       : GenuineIntel
                cpu family      : 6
                model           : 15
                model name      : Intel(R) Core(TM)2 CPU         T5600  @ 1.83GHz
                stepping        : 6
                cpu MHz         : 1000.000
                cache size      : 2048 KB
                physical id     : 0
                siblings        : 2
                core id         : 0
                cpu cores       : 2
                apicid          : 0
                initial apicid  : 0
                fpu             : yes
                fpu_exception   : yes
                cpuid level     : 10
                wp              : yes
                flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts tpr_shadow
                bogomips        : 3662.09
                clflush size    : 64
                cache_alignment : 64
                address sizes   : 36 bits physical, 48 bits virtual
                power management:
                
                processor       : 1
                vendor_id       : GenuineIntel
                cpu family      : 6
                model           : 15
                model name      : Intel(R) Core(TM)2 CPU         T5600  @ 1.83GHz
                stepping        : 6
                cpu MHz         : 1833.000
                cache size      : 2048 KB
                physical id     : 0
                siblings        : 2
                core id         : 1
                cpu cores       : 2
                apicid          : 1
                initial apicid  : 1
                fpu             : yes
                fpu_exception   : yes
                cpuid level     : 10
                wp              : yes
                flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts tpr_shadow
                bogomips        : 3661.57
                clflush size    : 64
                cache_alignment : 64
                address sizes   : 36 bits physical, 48 bits virtual
                power management:
                Curiously, CPU speed in processor 0 is 1GHz versus 1.83GHz in processor 1!

                Comment


                  #9
                  Originally posted by ASGR View Post
                  Right then... Looks like a T5600 chip...
                  Curiously, CPU speed in processor 0 is 1GHz versus 1.83GHz in processor 1!
                  The rating shown in the "model name" row is the maximum speed your processor will run. The value shown in the "cpu MHz" row is the current speed of your processor. For some time now, kernels have defaulted to the ondemand governor. What you're seeing in the list is that core #0 is running at 1.0 GHz while core #1 is running at 1.833 GHz.

                  Second thing to explore is graphics drivers. Perhaps the driver on the openSUSE CD is a different version?

                  Comment


                    #10
                    Originally posted by ASGR View Post
                    I burned a x86_64 version of KDE
                    openSUSE and it's purring along. I've also been using 64bit builds
                    in OSX for years with no complaints.
                    So 64bit support is fine. The first bit of evidence is that it runs ... and the other is the token 'lm' in the flags line (long mode).

                    Are you still hoping to get Kubuntu 64bit running on this machine? I see no reason why it shouldn't.

                    Did you say how much RAM you have?
                    I'd rather be locked out than locked in.

                    Comment


                      #11
                      Thanks again.

                      For diagnostic purposes, I did run the memory testing tools that are
                      an option on the front screen. Didn't report any errors. The GFX chip
                      detected by the binary was something like i950 which is similar to
                      what OSX detects with System Profiler. I'd be surprised if the GFX
                      chip isn't supported as it's now quite an old chip.

                      With openSUSE working so well I don't think I'll be trying any time soon
                      to install Kubuntu again. Might work better on a more recent iMac Model
                      but I'm not in a position to try.

                      I've got the max 2GB of RAM.

                      Thanks for all the help guys.
                      Last edited by ASGR; Feb 11, 2012, 10:41 AM.

                      Comment

                      Working...
                      X