Re: New build - halt on ACPI Controller
- From: "Peter Boulton" <peter@data*no-spam*perceptions.co.uk>
- Date: Wed, 31 Oct 2007 13:32:14 -0000
Hi John,
You were quite right! Brilliant - thanks! I think the boot order was wrong - hard drive (unformatted) before CDROM. When I switched to CDROM first I could boot from a cdrom no problem.
I then enabled AHCI for my sata drives in the bios and started the Vista install. Vista found my new sata drive, I tried (successfully) to load the sata chipset drivers but then setup stopped with this message:
"Windows could not establish whether this computer has a valid system volume"
Have you come across this before?
I am currently installing Vista as I write this, but having ignored the opportunity to load the sata drivers at the start of the install. Does this mean I will be irrevocably tied to IDE emulation mode for ever, or once Windows starts can I install the drivers then?
Thanks again!
Pete
"John Jordan" <junk@xxxxxxxxxxxx> wrote in message news:5oqirtFo4i67U1@xxxxxxxxxxxxxxxxxxxxx
Johnny B Good wrote:The message <fg88pk$nnl$1$8300dec7@xxxxxxxxxxxxxxxx>
from "Peter Boulton" <peter@data*no-spam*perceptions.co.uk> contains
these words:
OP here - just to say, problem still happening even after cmos reset. I've uploaded a screen shot here:
http://www.dataper.demon.co.uk/misc/helpme.jpg
There are a remarkably large number of hardware adapters in that list
sharing a remarkably small number of IRQ lines. Assuming PCI Bus 0 is
the on-board stuff, and PCI Bus 1, 3 and 4 are the actual PCI slots, all
I can suggest is you try removing the RAID controller and the network
adapter (Gbit?) and see if it will get past that point. It looks as
though there might well be an IRQ sharing compatability issue with one
or more of your add in cards (which a reshuffle _might_ sort out).
I strongly suspect that PCI "bus" 3 and 4 are PCI-E connected and motherboard-integrated chips. Similarly, PCI bus 1 is probably the PCI-E slot that the graphics card is connected to.
I suspect that this screenshot is a red herring - the ACPI controller is often the last item on the list, and I don't think the bus/dev etc. info is valid for it.
This would suggest that the board is actually sticking at the stage where it searches for boot devices. This can happen for reasons as trivial as having a dubious CD in the drive.
I'm no expert in interpreting such POST information, but a good
approach to such POST time boot hangs is to minimise the hardware
collection to just the bare essentials (or even less!) and proceed from
there. Apologies if you've already tried this.
Ditto to this. Remove all drives, all USB devices, all cards except video, and see what it does.
--
John Jordan
.
- Follow-Ups:
- Re: New build - halt on ACPI Controller
- From: Peter Boulton
- Re: New build - halt on ACPI Controller
- References:
- New build - halt on ACPI Controller
- From: Peter Boulton
- Re: New build - halt on ACPI Controller
- From: Peter Boulton
- Re: New build - halt on ACPI Controller
- From: Johnny B Good
- Re: New build - halt on ACPI Controller
- From: John Jordan
- New build - halt on ACPI Controller
- Prev by Date: Re: Was XP as bad as this when it came out?
- Next by Date: Making a Win2K slipstreamed CD?
- Previous by thread: Re: New build - halt on ACPI Controller
- Next by thread: Re: New build - halt on ACPI Controller
- Index(es):
Relevant Pages
|