LiveCD on Real Hardware

[milon]

I figured it was time to try ROS again on my hardware. Here's what I've got:

Pentium 4 Dual Core 2.6GHz processor
ASUS P5Q-VM motherboard
2GB of RAM
640GB SATA harddisk

I burned LiveCD build 55277 to a CD-RW and rebooted. I let it do the default LiveCD (Debug) option first. That yielded a screen that halted at:

Code: Select all

ReactOS (R) Kernel Version 5.2 (Build 3790: Service Pack 1, V. 55227)
1 System Processor [2013 MB Memory]
multi(0)disk(0)cdrom(111)\reactos\system32\Drivers\UNIATA.SYS
multi(0)disk(0)cdrom(111)\reactos\system32\Drivers\BUSLOGIC.SYS
multi(0)disk(0)cdrom(111)\reactos\system32\Drivers\CDROM.SYS
multi(0)disk(0)cdrom(111)\reactos\system32\Drivers\DISK.SYS
multi(0)disk(0)cdrom(111)\reactos\system32\Drivers\FASTFAT.SYS
multi(0)disk(0)cdrom(111)\reactos\system32\Drivers\RAMDISK.SYS
multi(0)disk(0)cdrom(111)\reactos\system32\Drivers\NMIDEBUG.SYS
multi(0)disk(0)cdrom(111)\reactos\system32\Drivers\CDFS.SYS
multi(0)disk(0)cdrom(111)\reactos\system32\Drivers\CDFS.SYS
multi(0)disk(0)cdrom(111)\reactos\system32\Drivers\MUP.SYS
multi(0)disk(0)cdrom(111)\reactos\system32\Drivers\NDIS.SYS

The color band at the bottom stopped moving once it got to this point. There were two CDFS lines as shown above. I restarted and tried again, this time choosing the LiveCD option. That led to a BSoD with error I01_INITIALIZATION_FAILED.

Any thoughts as to why? Any ideas about what I can try next? I apologize if this is a known event. I've not had time for any ROS testing for a couple weeks now.

[elhoir]

what about enabling NDIS debug?

http://www.reactos.org/wiki/Debugging#T ... mpile_time

[elhoir]

"640GB SATA harddisk"

Oh, are you using AHCI as HDD I/O mode?

UniATA doesnt support that, so you should switch to IDE compatibility mode at BIOS, if so

[aicommander]

what about enabling NDIS debug?

Just because it stops there, doesn't mean that NDIS is responsible. In fact, NDIS does nothing without a NIC or protocol driver which loads much later in boot. People always like to think NDIS is the bad guy when people get these hangs, but I'll bet you just about anything that the driver has nothing to do with this hang. The bugcheck makes that more apparent. NDIS happens to be loaded at the end of the boot start drivers and right before the system start start drivers which is stage 1 boot.

[milon]

"640GB SATA harddisk"

Oh, are you using AHCI as HDD I/O mode?

UniATA doesnt support that, so you should switch to IDE compatibility mode at BIOS, if so

I was running it using AHCI, good thought. I went into my BIOS and switched it to IDE mode. Same result - hangs right after NDIS.SYS loads.

So, what's the next thing to try?

[milon]

I just tested with ReactOS 0.3.14 LiveCD. Same BSoD.

[vicmarcal]

I just tested with ReactOS 0.3.14 LiveCD. Same BSoD.

Sadly AHCI is not well supported by the UNIATA driver
The only way to help you is obtaining a debuglog.

[milon]

Sadly AHCI is not well supported by the UNIATA driver
The only way to help you is obtaining a debuglog.

How do I get that on real hardware? Is logging to USB supported? I don't have any other PC's I can connect to for a serial dump.

[SomeGuy]

Currently ReactOS can only log to COM ports, not USB.

To record debugging information you will need your computer and another computer connected together using their COM ports with a nullmodem cable. PCI serial COM port add-on cards are supported.

BTW, this sounds similar to the error: http://www.reactos.org/bugzilla/show_bug.cgi?id=6575

Is your CD-drive attached via SATA or IDE? And does it appear as a "master" or "slave" device?

One of the things you might try is placing one of the (older) versions of UniATA from http://alter.org.ua/soft/win/uni_ata/ on the boot CD, and see if that makes a difference.

[milon]

Both the HDD and the DVD are SATA drives. I have tried on IDE mode, but as you know that didn't work. I honestly can't recall if SATA uses master/slave but if it does than the HDD is mater and the DVD is slave (or else they're both master on different channels?). It's been some years since I put this machine together and I haven't had occasion to take it apart since then. Anyway, I'll do more testing and post again when I've got some results. And maybe I'll look at my hardware configuration too.