Hallo,
I have found a problem. SVN-version cannot boot from cdrom on real HW and Qemu (?!), but on 1 of 2 systems only. ros-3.11 works on 2 of 2 systems (real,qemu) s. details
Whats going wrong? maybe a conflict with any HW.
Heiko
details:
- test real HW (*1)
1. boot cd ReactOS Setup load .... ext2.sys -> hang! screen: black
Version: 47265, 47751
*1 $ lspci | egrep "Host|VGA|Ether" 00:00.0 Host bridge: Intel Corporation 82845 845 [Brookdale] Chipset Host Bridge (rev 03) 02:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA 1064SG [Mystique] (rev 02) 02:04.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang]
# fdisk -l Device Boot Start End Blocks Id System /dev/sda1 1 256 2056288+ a9 NetBSD /dev/sda2 257 768 4112640 83 Linux /dev/sda3 * 769 1792 8225280 b W95 FAT32 /dev/sda4 1793 4865 24683872+ 5 Extended /dev/sda5 1793 1825 265041 82 Linux swap / Solaris /dev/sda6 1826 2849 8225248+ 83 Linux /dev/sda7 2850 4865 16193488+ a9 NetBSD
- table summary num system ver real/VM result 1 1 svn real Error 2 1 svn qemu Error 3 2 svn qemu ok. 4 1 3.11 real ok. 5 2 svn real ok.
svn: 47265, 47751 1,2: tested with: Safe Mode, Enable Boot Logging, Enable VGA Mode, Debugging Mode -> no errors was printed 2,3: qemu -hda ros-svn.hda.img -cdrom /dev/cdrom -boot d qemu -hda ros-svn.hda.img -cdrom bootcd-47265-dbg.iso -boot d
btwn: - 1. ReactOS Setup: menu_timeout=0.001 s (to small to read) - 2. ReactOS Setup: F8 works at time, or not (undetermined)
:x
debug log? :)
Date: Fri, 11 Jun 2010 15:56:53 +0200 From: hlehmann@fh-lausitz.de To: ros-general@reactos.org Subject: [ros-general] cannot boot cdrom svn real/qemu
Hallo,
I have found a problem. SVN-version cannot boot from cdrom on real HW and Qemu (?!), but on 1 of 2 systems only. ros-3.11 works on 2 of 2 systems (real,qemu) s. details
Whats going wrong? maybe a conflict with any HW.
Heiko
details:
- test real HW (*1)
- boot cd ReactOS Setup load .... ext2.sys -> hang! screen: black
Version: 47265, 47751
*1 $ lspci | egrep "Host|VGA|Ether" 00:00.0 Host bridge: Intel Corporation 82845 845 [Brookdale] Chipset Host Bridge (rev 03) 02:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA 1064SG [Mystique] (rev 02) 02:04.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang]
# fdisk -l Device Boot Start End Blocks Id System /dev/sda1 1 256 2056288+ a9 NetBSD /dev/sda2 257 768 4112640 83 Linux /dev/sda3 * 769 1792 8225280 b W95 FAT32 /dev/sda4 1793 4865 24683872+ 5 Extended /dev/sda5 1793 1825 265041 82 Linux swap / Solaris /dev/sda6 1826 2849 8225248+ 83 Linux /dev/sda7 2850 4865 16193488+ a9 NetBSD
- table summary num system ver real/VM result 1 1 svn real Error 2 1 svn qemu Error 3 2 svn qemu ok. 4 1 3.11 real ok. 5 2 svn real ok.
svn: 47265, 47751 1,2: tested with: Safe Mode, Enable Boot Logging, Enable VGA Mode, Debugging Mode -> no errors was printed 2,3: qemu -hda ros-svn.hda.img -cdrom /dev/cdrom -boot d qemu -hda ros-svn.hda.img -cdrom bootcd-47265-dbg.iso -boot d
btwn:
- ReactOS Setup: menu_timeout=0.001 s (to small to read)
- ReactOS Setup: F8 works at time, or not (undetermined)
:x
Ros-general mailing list Ros-general@reactos.org http://www.reactos.org/mailman/listinfo/ros-general
_________________________________________________________________ Disfruta de Messenger y Hotmail en tu BlackBerry ¡Hazlo ya! http://serviciosmoviles.es.msn.com/messenger/blackberry.aspx
----- Message d'origine ----
De : Heiko L. hlehmann@fh-lausitz.de À : ReactOS General List ros-general@reactos.org Envoyé le : Ven 11 juin 2010, 20h 04min 12s Objet : Re: [ros-general] cannot boot cdrom svn real/qemu
debug log? :)
num system
ver real/VM result
2
1 svn qemu Error
ros.deb.log-10061119_qemu attached...
(no diff. found between "Safe Mode" and "Debugging Mode")
H.
check your media/hard disk, C0000015 is STATUS_NONEXISTENT_SECTOR.
Kind regards, Sylvain Petreolle
check your media/hard disk, C0000015 is STATUS_NONEXISTENT_SECTOR.
this is a virgin disk (image):
$ qemu-img create ros-svn.hda.img 750M Formatting 'ros-svn.hda.img', fmt=raw size=786432000 ~$ fdisk -l ros-svn.hda.img
Disk ros-svn.hda.img: 0 MB, 0 bytes 255 heads, 63 sectors/track, 0 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000
Disk ros-svn.hda.img doesn't contain a valid partition table
- normal on this step
- this image works with 3.11 (next step: language selection) result: ros-svn.hda.img1 * 1 761 767056+ b W95 FAT32
- test 6 (s. test2 + PT) - use (above) partitioned disk (by 3.11) -> same error
- debug.log: ros.deb.log-10061122_qemu without warning missing EOpt:
$ diff ros.deb.log-10061119_qemu ros.deb.log-10061122_qemu 73d72 < (ntoskrnl/fstub/disksup.c:1487) FSTUB: (IoReadPartitionTable) No 0xaa55 found in partition table 0 75d73 < (ntoskrnl/fstub/disksup.c:1487) FSTUB: (IoReadPartitionTable) No 0xaa55 found in partition table 0 77d74 < (ntoskrnl/fstub/disksup.c:1487) FSTUB: (IoReadPartitionTable) No 0xaa55 found in partition table 0
$ tail -5 ros.deb.log-10061122_qemu (ntoskrnl/fstub/disksup.c:253) ZwOpenSymbolicLinkObject failed for \ArcName\multi(0)disk(0)rdisk(1), status=c0000034 (ntoskrnl/cc/copy.c:213) IoPageRead failed, Status c0000015 (ntoskrnl/mm/section.c:1102) MiReadPage failed (Status c0000015) Entered debugger on first-chance exception (Exception Code: 0xc0000006) (Unknown/User defined exception) kdb:>
$ qemu --version QEMU PC emulator version 0.11.0 (qemu-kvm-0.11.0), Copyright (c) 2003-2008 Fabrice Bellard
Heiko
PS: possible 2 problems, yet test #1 running on real HW with existing partitions.
more debug:
(ntoskrnl/cc/copy.c:213) IoPageRead failed, Status c0000015 (ntoskrnl/mm/section.c:1102) MiReadPage failed (Status c0000015) Entered debugger on first-chance exception (Exception Code: 0xc0000006) (Unknown/User defined exception) kdb:>
kdb:> bt bt Eip: ntdll.dll:18ab7 Frames: ntdll.dll:72bd ntdll.dll:18c8e ntdll.dll:17b33 ntdll.dll:17f3b ntdll.dll:1892a ntdll.dll:189aa ntdll.dll:6b7c ntdll.dll:2a75 ntdll.dll:2b20 ntdll.dll:79a9 kdb:> cont (ntoskrnl/ke/i386/exp.c:1089) Kill smss.exe, ExceptionCode: c0000006, ExceptionAddress: 7c918ab7, BaseAddress: 400000
*** Fatal System Error: 0x00000071 (0x00000000,0x00000000,0x00000000,0x00000000)
Entered debugger on embedded INT3 at 0x0008:0x808eb1c4.
any idea? Heiko