-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
cdrom.sys ( current SVN ) freezes the system when starting the installer and when booting the live cd. No bluescreen is displayed.
Is there a way to aquire debug information in such a case ( from installer or when booting the live cd ).
Greetings, Jan Schiefer!
From: Jan Schiefer
cdrom.sys ( current SVN ) freezes the system when starting the installer and when booting the live cd. No bluescreen is displayed.
Hmm, I have no problems on VMware (r16205) with either DBG = 0 or 1.
Is there a way to aquire debug information in such a case ( from installer or when booting the live cd ).
Before creating the live cd, edit bootdata/livecd.ini. For the boot cd, you can adjust OsLoadOptions in bootdata/txtsetup.sif (again before doing "make bootcd").
Gé van Geldorp
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Ge van Geldorp schrieb:
From: Jan Schiefer
cdrom.sys ( current SVN ) freezes the system when starting the installer and when booting the live cd. No bluescreen is displayed.
Hmm, I have no problems on VMware (r16205) with either DBG = 0 or 1.
Is there a way to aquire debug information in such a case ( from installer or when booting the live cd ).
Before creating the live cd, edit bootdata/livecd.ini. For the boot cd, you can adjust OsLoadOptions in bootdata/txtsetup.sif (again before doing "make bootcd").
Gé van Geldorp
I'm running it with QEMU 0.7.0. Command line: qemu -user-net -cdrom ReactOS-LiveCD.iso -serial stdio -boot d
When I starts "Loading cdrom.sys..." is the last thing displayed.
This is the debug output:
(ntoskrnl/ke/main.c:292) - --------------------------------------------------------------- (ntoskrnl/ke/main.c:293) ReactOS 0.3-SVN (Build 20050621-r16205) Used memory 131072Kb (ntoskrnl/mm/mminit.c:375) Kernel Stack Limits. InitTop = 0x80100000, Init = 0x800fd000 (ntoskrnl/mm/mm.c:327) No current process (ntoskrnl/ldr/loader.c:327) Could not open module file: \SystemRoot\system32\drivers\ne2000.sys (ntoskrnl/io/pnpmgr.c:1785) Initialization of service Ne2000 failed (Status c0000001)
It seems that ne2000.sys can't be opened. When I search for ne2000.sys it is found in reactos/output-i386/drivers/net/dd/ne2000 and reactos/output-i386/livecd/reactos/system32/drivers.
PS: Sorry for the stupid typo "cdron.sys".
Greetings, Jan Schiefer!
Jan Schiefer wrote:
I'm running it with QEMU 0.7.0. Command line: qemu -user-net -cdrom ReactOS-LiveCD.iso -serial stdio -boot d
When I starts "Loading cdrom.sys..." is the last thing displayed.
This is the debug output:
(ntoskrnl/ke/main.c:292)
(ntoskrnl/ke/main.c:293) ReactOS 0.3-SVN (Build 20050621-r16205) Used memory 131072Kb (ntoskrnl/mm/mminit.c:375) Kernel Stack Limits. InitTop = 0x80100000, Init = 0x800fd000 (ntoskrnl/mm/mm.c:327) No current process (ntoskrnl/ldr/loader.c:327) Could not open module file: \SystemRoot\system32\drivers\ne2000.sys (ntoskrnl/io/pnpmgr.c:1785) Initialization of service Ne2000 failed (Status c0000001)
It seems that ne2000.sys can't be opened. When I search for ne2000.sys it is found in reactos/output-i386/drivers/net/dd/ne2000 and reactos/output-i386/livecd/reactos/system32/drivers.
I think it has something to do with the hardware detection routine of the ne2000.sys driver. On qemu for windows I see:
(ntoskrnl\ldr\loader.c:327) Could not open module file: \SystemRoot\system32\drivers\ne2000.sys (ntoskrnl\io\pnpmgr.c:1785) Initialization of service Ne2000 failed (Status c0000001) (drivers\net\dd\ne2000\ne2000\8390.c:71)(NICCheck) Found adapter at 0xc100
The plug and play manager does try to start the same driver at different points while booting. The first two lines comes from the very early boot phase, where only some low level drivers are available which are loaded by freeldr. The third line comes from the second try to load ne2000.sys. You should change the debug trace level to MID_TRACE or MAX_TRACE in ne2000\main.c to see what is going on.
- Hartmut
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I still get aboloutly the same output with MAX_TRACE. How to change verbosity of cdrom.sys and ntoskrnl.exe?
Does it freeze on your qemu too?
Greetings, Jan Schiefer!
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Here's one from KDBG. I tried the commands bt, mod and regs.
How can I squeeze more revelant information out of KDBG?
Greetings, Jan Schiefer!
Jan Schiefer wrote:
Here's one from KDBG. I tried the commands bt, mod and regs.
How can I squeeze more revelant information out of KDBG?
Greetings, Jan Schiefer!
Can you convert the addresses to line numbers? You can use addr2line:
addr2line -e ntoskrnl.nostrip.exe 0x800b4007
The addresses from ntoskrnl.exe are always 0x800xxxxx.
- Hartmut
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hartmut Birr schrieb:
Jan Schiefer wrote:
Here's one from KDBG. I tried the commands bt, mod and regs.
How can I squeeze more revelant information out of KDBG?
Greetings, Jan Schiefer!
Can you convert the addresses to line numbers? You can use addr2line:
addr2line -e ntoskrnl.nostrip.exe 0x800b4007
The addresses from ntoskrnl.exe are always 0x800xxxxx.
- Hartmut
I can't find any *.nostrip.* files. So addr2line can't work correctly.
How to build them? How to supress stripping?
Greetings, Jan Schiefer!
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I searched the mailing list and found how to build nostrip executables.
Here's the output:
mrsuicide@mrsuicide:~/reactos/output-i386/ntoskrnl$ addr2line -e ntoskrnl.nostrip.exe 0x800b4007 /home/mrsuicide/reactos/ntoskrnl/ex/init.c:570
Seems like IoInit2(BootLog); in ExpInitializeExecutive(VOID) crashes.
Only ntoskrnl.exe and hal.dll are loaded at this point. ( KDB "mod" command )
Greetings, Jan Schiefer!
Jan Schiefer wrote:
I searched the mailing list and found how to build nostrip executables.
Here's the output:
mrsuicide@mrsuicide:~/reactos/output-i386/ntoskrnl$ addr2line -e ntoskrnl.nostrip.exe 0x800b4007 /home/mrsuicide/reactos/ntoskrnl/ex/init.c:570
Seems like IoInit2(BootLog); in ExpInitializeExecutive(VOID) crashes.
Only ntoskrnl.exe and hal.dll are loaded at this point. ( KDB "mod" command )
Greetings, Jan Schiefer!
What you see isn't a crash. In the early boot phase, the kernel debugger is always entered. If you will continue at this point, you have to hit 'cont'.
- Hartmut
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I just did a "svn up" and rebuild.
It won't freeze on this place anymore. The bootcd works flawlessly, the livecd freezes ( qemu freezes, not ROS ! ) in the Reactos build blah... screen, before the GUI appears.
Greetings, Jan Schiefer!
sorry, my message with header '/lib/kernel32/misc/comm.c and /lib/kernel32/file/find.c' - have been corrupted