Which windows x64 chipset driver (IDE/ATA) is working on an iMac 24" (early 2009)?

The bootcamp software that came with the imac is not working in Windows 8. Is there a separate x64 driver for that chipset? I found several drivers for the nforce chipset which all did not work. I have found drivers for all other devices in that iMac. The missing IDE driver results in a very slow System. Thanks for any suggestions.

From the Boot Camp System Requirements located here: http://support.apple.com/kb/HT5634
Your computer does not support Windows 8: It only supports Windows 7, Vista, and XP all 32 bit.
iMac (24-inch, Early 2009)
4
DVD
DVD

Similar Messages

  • IMac 20" early 2009. Windows 7 x64. "Boot Camp x64 is unsupported on this computer model"

    Dear all,
    I just install windows 7 x64 in my iMac 20" early 2009. But I have a problem with the installation of the drivers of bootcamp in windows 7.
    iMac 20" early 2009
    Processor 2,66 GHz Intel Core 2 Duo
    Graphics NVIDIA GeForce 9400 256 MB
    Software OS X 10.8.4 (12E55)
    I already tried:
    Mac OS X v10.6: equipos Mac que utilizan el kernel de 64 bits
    http://support.apple.com/kb/HT3770?viewlocale=es_ES
    OS X: Cómo iniciar el equipo con el kernel de 32 bits o de 64 bits
    http://support.apple.com/kb/HT3773?viewlocale=es_ES
    Boot Camp: System requirements for Microsoft Windows operating systems
    http://support.apple.com/kb/HT5634
    I check this also and try with this bootcamp
    Mac model
    Windows 8, 64-bit
    Windows 7, 64-bit
    Windows 7, 32-bit
    Windows Vista, 64-bit
    Windows Vista, 32-bit
    Windows XP, 32-bit
    iMac (20-inch, Early 2009)
    4
    4
    4
    But I can't find a solution. Any suggestion?

    If you can grab Boot Camp 3.0 thru 3.x you should be able to get the drivers you need.
    Apple took more agressive steps to really lock out and lock down drivers from being used and installed on systems that did not fall under the guide of 'supported'.
    So if you have 10.6 DVD that does have Boot Camp 3.0 on it and you would need to update to 3.2, which use to be posted for manual download (so could do so even from Windows) if not thru the Apple Software Update utility in Windows.
    If you can find a more "no we won't allow you to" I have never seen it.
    And Google as best you can.

  • TSP and Windows X64

    I have a CCM in version 4.0 and TSP version was 4.0(0.2203).
    I try to install the CISCO TSP in Windows X64 but it is doesn't works.
    In the Advanced tab, I can't see any "Cisco IOS Telephony Service provider". All works perfectly in other windows version.
    Witch TSP version was compatibly with Windows X64??
    Thanks for your help
    Regards
    Sebastien

    As of now TSP is not compatible with Win xp 64 bit because TSP drivers are not yet available.Drivers for all the other versions are available.

  • Which external cd/dvd drives are compatible?

    my optical drive has broke in my standard macbook, think its from 2007. It is too expensive to get repaired so i was just wondering which external cd/dvd drive are reconised and work with this macbook from the UK? thanks!

    This is not that easy to say as compatibility depends on the slave/master settings and therefore you would need to ask an ASP.
    Maybe check some lightscribe ODDs and ask the guys from ASP.
    But honestly, would you really want to waste your money on this feature? I know, those discs look pretty nice when used ligthscribe on it, but is it worth it?
    I have one in my other notebook but I have only used it once.
    And you will need special blank CDs/DVDs with this surface to use lightscribe feature.

  • Drive Mode no longer works on my LifeDrive

    Ever since upgrading to 10.4.9, Drive Mode no longer works on my iMac. Syncing continues to work fine. Lots of other people on the Palm forums are having the same problem since upgrading to 10.4.9. Did something change in the way the OS handles mountable drives that could be causing this problem?

    I have same problem with Palm T5 and MacBook since 10.4.9
    When I turn Drive Mode On, the Palm hangs after 5 seconds.
    On the /var/log/system.log on mac :
    kernel[0]: USBF: 1567.341 AppleUSBUHCI[0x309d000]::Found a transaction which hasn't moved in 5 seconds on bus 29, timing out!
    kernel[0]: USBF: 1573.342 AppleUSBUHCI[0x309d000]::Found a transaction which hasn't moved in 5 seconds on bus 29, timing out!
    kernel[0]: USBF: 1579.342 AppleUSBUHCI[0x309d000]::Found a transaction which hasn't moved in 5 seconds on bus 29, timing out!
    kernel[0]: USBF: 1585.342 AppleUSBUHCI[0x309d000]::Found a transaction which hasn't moved in 5 seconds on bus 29, timing out!
    kernel[0]: USBF: 1591.342 AppleUSBUHCI[0x309d000]::Found a transaction which hasn't moved in 5 seconds on bus 29, timing out!
    kernel[0]: USBF: 1597.343 AppleUSBUHCI[0x309d000]::Found a transaction which hasn't moved in 5 seconds on bus 29, timing out!
    kernel[0]: USBF: 1603.343 AppleUSBUHCI[0x309d000]::Found a transaction which hasn't moved in 5 seconds on bus 29, timing out!
    kernel[0]: USBF: 1607.234 ControlTransaction: control packet 1 error 0xe0004057
    kernel[0]: USBF: 1607.234 [0x339f300] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 1 of hub @ location: 0x1d000000)
    kernel[0]: USBF: 1608. 6 AppleUSBUHCI[0x309d000]::DeviceRequest - dmaCommand (0x3395780) already had memory descriptor (0x3233a80) - clearing
    kernel[0]: USBF: 1613.343 AppleUSBUHCI[0x309d000]::Found a transaction which hasn't moved in 5 seconds on bus 29, timing out!
    kernel[0]: USBF: 1619.344 AppleUSBUHCI[0x309d000]::Found a transaction which hasn't moved in 5 seconds on bus 29, timing out!
    kernel[0]: USBF: 1625.344 AppleUSBUHCI[0x309d000]::Found a transaction which hasn't moved in 5 seconds on bus 29, timing out!
    MacBook Black 2Ghz 1Go RAM   Mac OS X (10.4.9)  

  • PCI standard PCI-to-PCI bridge error when install Chipset driver to T430 with Windows XP

    Hi, 
    I have one T430 and wanna downgrade to Windows XP. After I finished installing OS and procceded to update drivers, this error message
    "Cannot Install this Hardware
    There was a problem installing this hardware PCI standard PCI-to-PCI bridge
    An error occurred during the installation of the device
    The data is invalid"
    came out when trying to install Chipset driver, which is the only one I failed.
    Any ideas about this problem? Thank you.

    Hi,
    Please restart your system and re-install.
    Ps should work now.
    Regards,
    Ashutosh

  • Problem installing Laserjet 4050 in Windows 7 x64, No driver in Universal Print Driver v5.0.3

    I have just installed Windows 7 64Bit operating system.  I have be successful in installing several other more recent HP printers in the office.  However, my main "workhorse" printer is a HP Laserjet 4050 and I have downloaded the Universal Printer Driver v5.0.3 for Windows x64 - PCL 5 and PCL 6, and in both cases it does not find a suitable driver. The HP download site states these Universal Drivers will work, but I cannot get it to install.
    Is there a driver that will work on the 4050 in Windows 7 X64?  Thanks everyone.

    You're probably getting the "Windows cannot locate a suitable printer driver" error if you're trying to add the driver while adding a printer that is shared over the network. You see, HP's Universal Printer Driver (UPD) doesn't contain the PnpIDs of every printers it supports, so when you specify HP's UPD as the drivers for the network printer, if Windows can't find a match for the printer's PnpID it spits out the driver isn't compatible.
    The way to overcome this is to install a "generic" printer locally, using HP's UP driver, and change the port afterwards to point to the shared printer. So, first, add a local printer (that will be using the LPT1 port - make sure no printer is attached!), and click on "Have disk(s)" to browse to and select HP's UPD. Going through the remaining steps should install a locally-attached printer named something like "HP Universal Printing PCL 5" (or "[..] PCL 6"). You'll then go in the new printer's properties, on the "Ports" tab, and click on "Add Port...". If you're installing a shared printer, you'll select "Local Port", click on "New Port..." and specify the path to the printer (e.g. \\myserver\hplaserj) as the port name. Those steps should do the trick.
    Last thing: beware, though, as HP's UPD PCL 6 might not be compatible (anymore) with your LaserJet 4050, as they use a PCL XL class number/revision (class 2.1; sort of a version number of the protocol) that is higher than what your printer's firmware might support for PCL6 (should be class 2.0) I know the latest versions of HP's UPD PCL 6 doesn't work with our LJ 4000 & 4050 printers, so you might have to use the PCL5e driver for those 64-bit workstations.
    Background info:
    PCL XL error on Laserjet 4550n with PCL 6 driver [IT Resource Center Forums]
    Universal Print Driver PCL6 broken on LaserJet 4000 [IT Resource Center Forums]
    Printer Command Language [Wikipedia]
    Let us know if it works.

  • Windows x64 and recently released Sounblaster Live! 64 bit driv

    I downloaded the new SB Li've! drivers (Creative Sound Blaster Li've! x64 Driver (2.23MB) released 2 Augh 05) - uninstalled all Creative programs and all Audio drivers on my system, and proceeded to install the drivers as instructed. I reboot my system and I get sound...but only in my front left, front right, and subwoofer. I go to my sound and audio settings, switch my advanced settings to 7. home theatre, and still only the 2 front speakers and the sub are working. Why would Creative release a driver that doesn't work? Any help? [email][email protected]][email protected][/url] or AIM = t0ide
    I've been trying to make this thing work since I've been using Windows x64...about 5 months now. Any help is highly appreciated.
    Mike

    Let me guess, CMSS is disabled?

  • Satellite U500-1EZ (PSU9ME) need Windows 7 Ultimate 32bit Chipset Driver

    Iv been searching all over for a few days, and i cant find the Toshiba Satellite U500-1EZ PSU9ME Windows Seven Ultimate 32bit Chipset Driver.
    If anyone knows where i can find it or can post a download link, itll be really nice..
    thnx
    No_Joke

    Hello
    Unfortunately your notebook model is not supported for Win7 32bit but I have checked notebook specification and your Satellite has Mobile Intel HM55 Express Chipset.
    The same chipset has Tecra A11 and is supported for Win7 32bit so you can install THIS driver.

  • New Driver Creative Sound Blaster Live! 24-bit 1.04.0050 WHQL For Windows x64

    This is the new  Official Audio driver  released by Creative for  Sound Blaster Live! 24-bit for Windows x64.
    You can not install this driver in your MSI nForce4 based boards without first applying the OnBoard Sound EEPROM fix first found  here
    You have to boot in win98 or  winMe using a boot diskette in order to run the fix.
    enjoy 
    Markoul

    Quote from: Markoul on 22-May-05, 00:07:32
    This is the new  Official Audio driver  released by Creative for  Sound Blaster Live! 24-bit for Windows x64.
    You can not install this driver in your MSI nForce4 based boards without first applying the OnBoard Sound EEPROM fix first found  here
    You have to boot in win98 or  winMe using a boot diskette in order to run the fix.
    enjoy 
    Markoul
    Have you actually tired it yourself?  I'm wondering if this is a workaround, or will this be the official solution.  I wouldn't mind trying it, but I don't want to mess it up for when the Official driver is released.

  • Z97 Gaming 3 chipset driver issue. Any ideas?

    Hey peeps!:)
    I got the Z97 Gaming 3 mobo. Installed every driver from MSI's website.
    But when I look up at the device manager the system devices... the:
    -Intel(R) Z97 Chipset LPC Controller - 8CC4
    - Intel(R) 9 Series Chipset Family PCI Express Root Port 1 - 8C90
    - Intel(R) 9 Series Chipset Family PCI Express Root Port 3 - 8C94
    - Intel(R) 9 Series Chipset Family SMBus Host Controller - 8CA2
    - Intel(R) 4th Gen Core processor DRAM Controller - 0C00
    Are still uses the Microsoft version driver from the date 2006.06.21, driver verion : 6.3.9600.17031
    I installed the chipset several times, restarted the PC. No help at all. Tried to manually install the
    driver, and browse the driver from hard drive. When it finishes, its says:
     "The best driver for your device is already installed"
    Anyone with the same problem? Any ideas guys?:S

    its happen to everyone who own z97 or any 9 series chipset. after installing "latest chipset driver" either downloaded from msi or from intel website, device manager still shows that drivers is taken from microsoft and dated 2006.
    until intel fixed their crap drivers, nothing that we can do.

  • Should I use MSI's or Intel's chipset driver with a G31M3-L V2 motherboard?

    I just purchased an MSI G31M3-L V2 motherboard, bundled with an Intel E5200 CPU from Fry’s Electronics, and I plan to build a computer with the other parts (listed below in the signature) that I already have. 
    This will be only my second build so I was doing some research to see that I do it right.  One thing I wanted to make sure about was the proper order for installing drivers since that appears to be important.
    All seem to agree that the first driver to be installed after the basic Windows installation is the chipset driver.  Some even say that the chipset driver should be installed before even installing Windows patches, updates and service packs.  Others say to complete the Windows installation first, but all agree that the chipset driver should be the first driver.  Ok, so far so good. 
    There is a driver on the MSI web site labeled “Intel INF Drivers for 945/955/965/975/Q3x/P3x/G3x/X3x Chipsets.”  It has a version number of  8.3.0.1013 and an update date of 2008-01-16.
    Well that’s great, but in my internet travels today I also came across a chipset driver on the Intel web site which also seems to be for the G31 chipset.  It is labeled “INF Update Utility – Primarily for Intel 4, 3, 900 Series Chipsets.”  It has a version number of 9.0.0.1008 and a date of 8/2/2008.  A look into the release notes for this item indicates that it is for Windows XP and the G31 Express chip set, among others.
    Well, of course, my first impulse is to use the Intel supplied driver since it has a higher version number and a later release date, so it must be the better driver, right?
    Then I got to thinking:  why wouldn’t MSI have this, apparently, newer chipset driver on its web site?  Is it possible that I would be better off with the, apparently, older driver on the MSI site?  Is it possible, perhaps, that MSI may have made changes to the driver they offer that makes it better for an MSI board than the, apparently, newer Intel driver?  Now I don’t know what to think!
    So which should I use, the version 8 driver from MSI or the version 9 driver from Intel?   

    I am building a computer with the parts listed below, but I thought that since the MSI G31M3-L V2 motherboard has on board video, and sound, it might be simpler to start out with that and add my video, and sound, cards later.  Of course this means I will have to install the Intel VGA driver and the Realtek audio driver and then add the nVIDIA and Creative drivers when I add those parts.
    On the one hand it seems like to get the computer up and stable first and then add in other parts later would be a good idea but on the other hand everyone seems to suggest that the graphics driver should pretty much be the next one installed after the chipset driver, so If I wait to add the nVIDIA card later I’m not really following this guideline.
    What do you experienced system builders do in a similar situation, put everything in all at once or start out with the on board stuff first and add the cards in later?

  • Satellite C850D-11C PSCC2E - CHIPSET driver for Win 7 64bit needed

    Hi,
    I've been stuck in a long convo over at the techsupportforum and was finally told to try here.
    So, I own a Satellite C850D-11C PSCC2E with Windows 7 x64.
    I can't seem to find the chipset driver for my laptop in the list of drivers.
    I first tried to install all available drivers, but it's obvious without a chipset I will have problems, and I do.
    The USB ports don't work like they should etc.
    Where is the chipset driver for the C850D-11C PSCC2E?
    Thanks!

    Hi
    Your notebook is equipped with an Ati (AMD) graphic chip.
    This means that the chipset must be from AMD too.
    According to some information which i found in internet, the AMD A68M Chipset should be built in the notebook.
    Furthermore as far as I know the ATI chipset driver is part of the ATI/AMD graphic card driver and therefore you should install the GPU driver to get the chipset driver installed

  • Question nVidia Chipset Drive Package Version Number.

    Question nVidia Chipset Drive Package Version Number.
    Hope this question is in the right sub forum.
    I have see this question asked on several Forums, but never see a answer.
    How do you tell which Chipset Driver Package Version is installed on your system, other than going to the Device Manager calling up the properties for each device and record the version number and comparing it to what listed for the Drive Package version?
    Roger

    I agree with you Richard.
    I wouldn't say super fast ram though, I buy Crucial. It is very nice ram and does not break the bank. (no heatsinks on it or any other expenses)
    Maybe I offended you, Bcc, by accident. I'm just trying to help folks on these forums and I have been with the nforce since day one. I have never seen this issue happen (or anything like it) on this board.
    Like my suggestion, (if that didn't work, I would have continued to work) if I couldn't disable the agp host I would have uninstalled it (the device itself) and let windows try again. It could have been an nforce package issue and not with the detonator. I wish when these problems occurred, that I had the opportunity to try and fix these very rare occurences and examine the issue at my own desk.
    I see too many people jump to the conclusion that they have found the mystery bug and go tell nvidia to recall the boards and fix it. I would not try to tell you that you are clueless about computers, as I don't have any idea how well you know them. But as an experienced technical writer/helper, I'm inclined to speak to the people as if they are dumb. As you can guess, many aren't, and they think that I may be saying they are, but at least they understand the situation.
    More than the majority of problems are caused by heat. Too much heat will cause funny things to start happening to your computer. Sometimes it's just the ram, or maybe the cpu that get overheated. With summer coming, it's prime time to see the 'heat' problem creep up. I'm sure this wasn't the case with your issue, but it is overlooked most of the time.
    Anyway, I'm glad your happy and your problem is fixed.

  • Failed boot after moving hard drive (IDE not SATA)

    Greetings all.
    I am attempting to setup a headless box, and in doing so I am installing Arch on one system (Sapphire Axion A3-M275 Motherboard), then moving the hard drive to the new system (SGS1660, a VIA CLE266/VT8235 based headless rack-solution). After moving the drive into the SGS1660, the system fails to boot. Attached output from the Serial Console:
    Booting 'Arch Linux'
    root (hd0,0)
    Filesystem type is ext2fs, partition type 0x83
    kernel /vmlinuz26 root=/dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b r
    o console=ttyS0,115200
    [Linux-bzImage, setup=0x3600, size=0x1ad6d0]
    initrd /kernel26.img
    [Linux-initrd @ 0x2ff21000, 0x9e7a5 bytes]
    Linux version 2.6.30-ARCH (root@T-POWA-LX) (gcc version 4.4.0 20090630 (prerelease) (GCC) ) #1 SMP PREEMPT Mon Jul 20 11:20:32 UTC 2009
    KERNEL supported cpus:
    Intel GenuineIntel
    AMD AuthenticAMD
    NSC Geode by NSC
    Cyrix CyrixInstead
    Centaur CentaurHauls
    Transmeta GenuineTMx86
    Transmeta TransmetaCPU
    UMC UMC UMC UMC
    BIOS-provided physical RAM map:
    BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
    BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
    BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
    BIOS-e820: 0000000000100000 - 000000002ffd0000 (usable)
    BIOS-e820: 000000002ffd0000 - 000000002ffde000 (ACPI data)
    BIOS-e820: 000000002ffde000 - 0000000030000000 (ACPI NVS)
    BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
    BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved)
    DMI 2.3 present.
    AMI BIOS detected: BIOS may corrupt low RAM, working around it.
    last_pfn = 0x2ffd0 max_arch_pfn = 0x100000
    x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Scanning 0 areas for low memory corruption
    modified physical RAM map:
    modified: 0000000000000000 - 0000000000010000 (reserved)
    modified: 0000000000010000 - 000000000009fc00 (usable)
    modified: 000000000009fc00 - 00000000000a0000 (reserved)
    modified: 00000000000e0000 - 0000000000100000 (reserved)
    modified: 0000000000100000 - 000000002ffd0000 (usable)
    modified: 000000002ffd0000 - 000000002ffde000 (ACPI data)
    modified: 000000002ffde000 - 0000000030000000 (ACPI NVS)
    modified: 00000000fec00000 - 00000000fec01000 (reserved)
    modified: 00000000ff780000 - 0000000100000000 (reserved)
    init_memory_mapping: 0000000000000000-000000002ffd0000
    RAMDISK: 2ff21000 - 2ffbf7a5
    ACPI: RSDP 000f6ad0 00014 (v00 ACPIAM)
    ACPI: RSDT 2ffd0000 0002C (v01 A M I OEMRSDT 09000521 MSFT 00000097)
    ACPI: FACP 2ffd0200 00084 (v02 A M I OEMFACP 09000521 MSFT 00000097)
    ACPI: DSDT 2ffd0390 03270 (v01 MiniV MiniV080 00000080 INTL 02002026)
    ACPI: FACS 2ffde000 00040
    ACPI: OEMB 2ffde040 00046 (v01 A M I AMI_OEM 09000521 MSFT 00000097)
    0MB HIGHMEM available.
    767MB LOWMEM available.
    mapped low ram: 0 - 2ffd0000
    low ram: 0 - 2ffd0000
    node 0 low ram: 00000000 - 2ffd0000
    node 0 bootmap 00011000 - 00016ffc
    (9 early reservations) ==> bootmem [0000000000 - 002ffd0000]
    #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
    #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
    #2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
    #3 [0000100000 - 0000626e44] TEXT DATA BSS ==> [0000100000 - 0000626e44]
    #4 [002ff21000 - 002ffbf7a5] RAMDISK ==> [002ff21000 - 002ffbf7a5]
    #5 [0000099c00 - 0000100000] BIOS reserved ==> [0000099c00 - 0000100000]
    #6 [0000627000 - 0000629230] BRK ==> [0000627000 - 0000629230]
    #7 [0000010000 - 0000011000] PGTABLE ==> [0000010000 - 0000011000]
    #8 [0000011000 - 0000017000] BOOTMAP ==> [0000011000 - 0000017000]
    Zone PFN ranges:
    DMA 0x00000010 -> 0x00001000
    Normal 0x00001000 -> 0x0002ffd0
    HighMem 0x0002ffd0 -> 0x0002ffd0
    Movable zone start PFN for each node
    early_node_map[2] active PFN ranges
    0: 0x00000010 -> 0x0000009f
    0: 0x00000100 -> 0x0002ffd0
    Using APIC driver default
    ACPI: PM-Timer IO Port: 0x808
    SMP: Allowing 1 CPUs, 0 hotplug CPUs
    No local APIC present or hardware disabled
    PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
    PM: Registered nosave memory: 00000000000a0000 - 00000000000e0000
    PM: Registered nosave memory: 00000000000e0000 - 0000000000100000
    Allocating PCI resources starting at 40000000 (gap: 30000000:cec00000)
    NR_CPUS:8 nr_cpumask_bits:8 nr_cpu_ids:1 nr_node_ids:1
    PERCPU: Embedded 11 pages at c1606000, static data 24444 bytes
    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 194911
    Kernel command line: root=/dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b ro console=ttyS0,115200
    Enabling fast FPU save and restore... done.
    Enabling unmasked SIMD FPU exception support... done.
    Initializing CPU#0
    NR_IRQS:512
    PID hash table entries: 4096 (order: 12, 16384 bytes)
    Fast TSC calibration using PIT
    Detected 1326.894 MHz processor.
    Console: colour dummy device 80x25
    console [ttyS0] enabled
    Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
    Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
    Initializing HighMem for node 0 (00000000:00000000)
    Memory: 772708k/786240k available (2905k kernel code, 12976k reserved, 1052k data, 392k init, 0k highmem)
    virtual kernel memory layout:
    fixmap : 0xfff4e000 - 0xfffff000 ( 708 kB)
    pkmap : 0xff800000 - 0xffc00000 (4096 kB)
    vmalloc : 0xf07d0000 - 0xff7fe000 ( 240 MB)
    lowmem : 0xc0000000 - 0xeffd0000 ( 767 MB)
    .init : 0xc04e3000 - 0xc0545000 ( 392 kB)
    .data : 0xc03d647f - 0xc04dd6a8 (1052 kB)
    .text : 0xc0100000 - 0xc03d647f (2905 kB)
    Checking if this processor honours the WP bit even in supervisor mode...Ok.
    SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
    Calibrating delay loop (skipped), value calculated using timer frequency.. 2654.36 BogoMIPS (lpj=4422980)
    Security Framework initialized
    Mount-cache hash table entries: 512
    CPU: L1 I Cache: 64K (32 bytes/line), D cache 64K (32 bytes/line)
    CPU: L2 Cache: 64K (32 bytes/line)
    Checking 'hlt' instruction... OK.
    SMP alternatives: switching to UP code
    Freeing SMP alternatives: 10k freed
    ACPI: Core revision 20090320
    ACPI: setting ELCR to 0200 (from 8c20)
    weird, boot CPU (#0) not listed by the BIOS.
    SMP motherboard not detected.
    Local APIC not detected. Using dummy APIC emulation.
    SMP disabled
    Brought up 1 CPUs
    Total of 1 processors activated (2654.36 BogoMIPS).
    net_namespace: 1056 bytes
    Booting paravirtualized kernel on bare hardware
    NET: Registered protocol family 16
    ACPI: bus type pci registered
    PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=1
    PCI: Using configuration type 1 for base access
    bio: create slab <bio-0> at 0
    ACPI: Interpreter enabled
    ACPI: (supports S0 S1 S3 S4 S5)
    ACPI: Using PIC for interrupt routing
    ACPI: Power Resource [URP1] (off)
    ACPI: Power Resource [URP2] (off)
    ACPI: Power Resource [FDDP] (off)
    ACPI: Power Resource [LPTP] (off)
    ACPI: No dock devices found.
    ACPI: PCI Root Bridge [PCI0] (0000:00)
    pci 0000:00:07.0: PME# supported from D0 D3hot D3cold
    pci 0000:00:07.0: PME# disabled
    pci 0000:00:10.0: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:00:10.0: PME# disabled
    pci 0000:00:10.1: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:00:10.1: PME# disabled
    pci 0000:00:10.2: PME# supported from D0 D1 D2 D3hot D3cold
    pci 0000:00:10.2: PME# disabled
    HPET not enabled in BIOS. You might try hpet=force boot option
    pci 0000:00:11.0: quirk: region 0800-087f claimed by vt8235 PM
    pci 0000:00:11.0: quirk: region 0400-040f claimed by vt8235 SMB
    ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15)
    ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
    ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15)
    ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11 12 14 *15)
    PCI: Using ACPI for IRQ routing
    NetLabel: Initializing
    NetLabel: domain hash size = 128
    NetLabel: protocols = UNLABELED CIPSOv4
    NetLabel: unlabeled traffic allowed by default
    pnp: PnP ACPI init
    ACPI: bus type pnp registered
    pnp: PnP ACPI: found 10 devices
    ACPI: ACPI bus type pnp unregistered
    system 00:05: ioport range 0xe900-0xe90f has been reserved
    system 00:05: ioport range 0xea00-0xea0f has been reserved
    system 00:05: ioport range 0xeb00-0xeb2f has been reserved
    system 00:05: ioport range 0xec00-0xec7f has been reserved
    system 00:05: ioport range 0xe800-0xe83f has been reserved
    system 00:07: ioport range 0x3e0-0x3e7 has been reserved
    system 00:07: ioport range 0x4d0-0x4d1 has been reserved
    system 00:07: ioport range 0x800-0x87f has been reserved
    system 00:07: ioport range 0x400-0x41f could not be reserved
    system 00:09: iomem range 0x0-0x9ffff could not be reserved
    system 00:09: iomem range 0xe0000-0xfffff could not be reserved
    system 00:09: iomem range 0x100000-0x2fffffff could not be reserved
    pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
    pci 0000:00:01.0: IO window: disabled
    pci 0000:00:01.0: MEM window: 0xddd00000-0xdfdfffff
    pci 0000:00:01.0: PREFETCH window: 0x000000d5c00000-0x000000ddbfffff
    NET: Registered protocol family 2
    IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
    TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
    TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
    TCP: Hash tables configured (established 131072 bind 65536)
    TCP reno registered
    NET: Registered protocol family 1
    Unpacking initramfs...
    Freeing initrd memory: 633k freed
    apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
    apm: overridden by ACPI.
    Scanning for low memory corruption every 60 seconds
    audit: initializing netlink socket (disabled)
    type=2000 audit(1248948860.509:1): initialized
    VFS: Disk quotas dquot_6.5.2
    Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
    msgmni has been set to 1510
    alg: No test for stdrng (krng)
    Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
    io scheduler noop registered
    io scheduler anticipatory registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    pci 0000:00:01.0: disabling DAC on VIA PCI bridge
    isapnp: Scanning for PnP cards...
    isapnp: No Plug & Play device found
    Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
    serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
    input: Macintosh mouse button emulation as /devices/virtual/input/input0
    PNP: No PS/2 controller found. Probing ports directly.
    serio: i8042 KBD port at 0x60,0x64 irq 1
    serio: i8042 AUX port at 0x60,0x64 irq 12
    mice: PS/2 mouse device common for all mice
    cpuidle: using governor ladder
    cpuidle: using governor menu
    TCP cubic registered
    NET: Registered protocol family 17
    Using IPI No-Shortcut mode
    registered taskstats version 1
    Initalizing network drop monitor service
    Freeing unused kernel memory: 392k freed
    :: Loading Initramfs
    :: Running Hook [udev]
    :: Loading udev...SCSI subsystem initialized
    pata_acpi 0000:00:11.1: can't derive routing for PCI INT A
    pata_acpi 0000:00:11.1: can't derive routing for PCI INT A
    done.
    Waiting 10 seconds for device /dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b ...
    Root device '/dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b' doesn't exist, attempting to create it
    ERROR: Failed to parse block device ids for '/dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b'
    ERROR: Unable to detect or create root device '/dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b'
    You are being dropped to a recovery shell
    Type 'reboot' to reboot
    Type 'exit' to try and continue booting
    NOTE: klibc contains no 'ls' binary, use 'echo *' instead
    If the device '/dev/disk/by-uuid/93df0562-c6e6-4583-9a79-51cd2091247b' gets created while you are here,
    try adding 'rootdelay=10' or higher to the kernel command-line
    ramfs$
    I think what is happening is that the kernel does not have the drivers for the IDE controller on the board for the CLE266/VT8235. Does this seem accurrate? And if so, how can I verify the current kernel config, then compile a kernel with everything else Arch needs to boot properly? I am familiar with the old means of setting up a kernel using the 'make menuconfig; make; make modules_install' etc method.
    Thanks for the help in advance!

    Hi, not sure if this is still causing you an issue, but I just ran into the same problem.
    For me, I have a Sharp PC=MM1110 which has no cd drive and doesn't like to boot from USB. To get Arch installed on it, I had to attach it to another PC (via it's docking cradle, which lets it show up as a USB hard drive), then boot the other PC from an Arch install cd and select the USB hdd for all of the partitioning etc.
    When I rebooted after the installation, the Sharp wouldn't boot.
    First, I had to edit the grub menu entry to point to (hd0,0), at which point I got the error listed in the first post... Failed to parse block device id's.
    If i booted into fallback mode, it booted without a problem.
    For me, the solution to finally get it working was to boot into fallback mode, remount the filesystem as r/w, and run mkinitcpio -g filename to rebuild the kernel. Once completed all I had to do was point grub to the new kernel image and it booted ok.
    Hope this is useful to someone

Maybe you are looking for