Page 1 of 2

BLANK screen live or installed.. help!

Posted: Tue Sep 04, 2007 7:52 am
by nitrotrike
I tried installing it on a Toshiba P25-s477 laptop. I see the load screen (where it is scrolling the drivers. etc), then everything goes blank. Tried burning it at different speeds (as slow as 4X), same thing.
Then tried the live CD, also at different speeds, same results - blank screen, but laptop is still 'on'. When trying to run it live, it never makes it past (goes blank) the "press any key to boot from CD" screen. I am about to give up on this whole idea. I don't know what else I can possibly do :roll:

Posted: Tue Sep 04, 2007 9:52 pm
by Guennie1568
I think, ROS doesn't support onboard graphics chips and shared memory, because I have the same "problem" too on my notebook.
But on my PC with PCIe graphics card I can see the installer till he comes to the position who he searches the HDD. So the installer also doesn't support SATA yet too.

Posted: Wed Sep 05, 2007 10:59 pm
by GreatLord
Hi
after long search on the internet
it seam u graphic card only support one res it
is 1280x1024x32, you need set that res in reactos register before u trying boot reactos to gui mode.

I think we should add a safe guard, like if only one mode are detected we hould use it, and do not care about the register value.
at moment if no sute mode are detected it always fail back to 640x480x16


facts I found about u graphic card.
GeForce FX Go5200 - No QE, No Coreimage, Vesa 3.0 @ 1280x1024x32

Posted: Thu Sep 13, 2007 4:55 pm
by cruzades
specs:

sempron 2400
256 memory DDR266
cd-writer
floppy drive
40gb 7200rpm seagate
128mb fx5200 video card

i encountered blank screen as well.

Posted: Thu Sep 13, 2007 8:03 pm
by dasnk
Same here... PCIe GeForce MX440 SE, AMD Duron. ATA hard drive.

Also same result on my Toshiba Satellite laptop.

Edit: I don't see load screen.

Press any key to boot from CD. And then just a black screen, doesn't boot.

Posted: Thu Sep 13, 2007 9:05 pm
by Z98
Two words: Debug logs.

Posted: Thu Sep 13, 2007 10:48 pm
by Guennie1568
dasnk wrote:Same here... PCIe GeForce MX440 SE, AMD Duron. ATA hard drive.
I think, GeForce hasn't any 440 Graka with PCIe support
dasnk wrote: Also same result on my Toshiba Satellite laptop.
And I think as 2nd, that ROS don't support shared memory
dasnk wrote: Edit: I don't see load screen.

Press any key to boot from CD. And then just a black screen, doesn't boot.
Same as Z98 has written: Send a debug.log to the devs or the Bug list.

Posted: Thu Sep 13, 2007 10:58 pm
by dasnk
You're right sorry, the card is AGP.

And as i'm using the live CD and it doesn't boot at all, there is no way I can get a log, is there?

Posted: Thu Sep 13, 2007 11:09 pm
by Guennie1568
If your PC has a serial port and you have a second PC (e.g. a laptop) you can boot in debug mode. But if you cannot se any boot screen, you cant make a log file :(

same problems on older PC

Posted: Wed Oct 17, 2007 9:31 pm
by PCS
I am experiencing the exact same screen blanking problem. Upon review of other's problems here, I tried installing a dedicated S3 Trio64V+ 86c765 PCI VGA card, which yielded the exact same results. In both cases, my system STILL goes blank right after loading the SERIAL.SYS driver. I had also specified resolutions during setup as low as 640x480x4 to help resolve any potential compatibility issues. Seems to me that with such simplistic, legacy hardware listed below, it should work with the greatest of ease. The most current PCLinuxOS/Knoppix/SLAX Kill Bill LIVE CD's boot to desktop and function perfectly with current system configuration.

OEM SYSTEM SPECS:
eMachines 566i
iCeleron 566
i810 Chipset
256MB RAM
7.5GB HDD
Intel Direct 3D AGP integrated video

Blank Screen NVidia GForce 5200 FX

Posted: Sat Oct 20, 2007 7:01 am
by ohiomike
Boot Live CD: several msg on monitor, then blank screen.
(Note- debug is with PNY AGP video card, got same result with a PCI video card instead)

>> Hardware:
ABIT IS7 motherboard (socket 478)
Intel P4e (3.0 GHz HT)
1 GB ram
PNY video card:
..AGP 82685G Bridge_Host (PCI Bus #0, Dev #0, Func #0)
..GForce 5200 FX (PCI Bus #1, Dev #0, Func #0)
NIC, on-board: RealTek 8169 (PCI Bus #2, Dev #2, Func #0)
1 40 GB HDD (hda1= NTFS, hda2..6= ext3)

>> ReactOS Debug:
(ntoskrnl/kd/kdio.c:191) -----------------------------------------------------
(ntoskrnl/kd/kdio.c:192) ReactOS 0.4-SVN (Build 20071020-r29695)
(ntoskrnl/kd/kdio.c:193) Command Line: MININT DEBUGPORT=COM1 SOS
(ntoskrnl/kd/kdio.c:197) ARC Paths: multi(0)disk(0)cdrom(159) \ multi(0)disk(0)cdrom(159) \reactos\
(ntoskrnl/mm/mminit.c:266) Base\0x09\0x09Length\0x09\0x09Type
(ntoskrnl/mm/mminit.c:272) 00000000\0x0900000001\0x09FirmwarePermanent
(ntoskrnl/mm/mminit.c:272) 00000001\0x0900000002\0x09MemoryData
(ntoskrnl/mm/mminit.c:272) 00000003\0x0900000035\0x09Free
(ntoskrnl/mm/mminit.c:272) 00000038\0x0900000008\0x09MemoryData
(ntoskrnl/mm/mminit.c:272) 00000040\0x090000005F\0x09Free
(ntoskrnl/mm/mminit.c:272) 0000009F\0x0900000001\0x09SpecialMemory
(ntoskrnl/mm/mminit.c:272) 000000A0\0x0900000050\0x09FirmwarePermanent
(ntoskrnl/mm/mminit.c:272) 000000F0\0x0900000010\0x09SpecialMemory
(ntoskrnl/mm/mminit.c:272) 00000100\0x0900000700\0x09Free
(ntoskrnl/mm/mminit.c:272) 00000800\0x0900000288\0x09SystemCode
(ntoskrnl/mm/mminit.c:272) 00000A88\0x090000000E\0x09BootDriver
(ntoskrnl/mm/mminit.c:272) 00000A96\0x090000001A\0x09HalCode
(ntoskrnl/mm/mminit.c:272) 00000AB0\0x0900000009\0x09BootDriver
(ntoskrnl/mm/mminit.c:272) 00000AB9\0x090000000F\0x09RegistryData
(ntoskrnl/mm/mminit.c:272) 00000AC8\0x0900000004\0x09RegistryData
(ntoskrnl/mm/mminit.c:272) 00000ACC\0x0900000011\0x09NlsData
(ntoskrnl/mm/mminit.c:272) 00000ADD\0x0900000011\0x09NlsData
(ntoskrnl/mm/mminit.c:272) 00000AEE\0x0900000002\0x09NlsData
(ntoskrnl/mm/mminit.c:272) 00000AF0\0x0900000017\0x09BootDriver
(ntoskrnl/mm/mminit.c:272) 00000B07\0x0900000015\0x09BootDriver
(ntoskrnl/mm/mminit.c:272) 00000B1C\0x090000000D\0x09BootDriver
(ntoskrnl/mm/mminit.c:272) 00000B29\0x0900000011\0x09BootDriver
(ntoskrnl/mm/mminit.c:272) 00000B3A\0x0900000019\0x09BootDriver
(ntoskrnl/mm/mminit.c:272) 00000B53\0x0900000011\0x09BootDriver
(ntoskrnl/mm/mminit.c:272) 00000B64\0x0900000029\0x09BootDriver
(ntoskrnl/mm/mminit.c:272) 00000B8D\0x0900000012\0x09BootDriver
(ntoskrnl/mm/mminit.c:272) 00000B9F\0x090000002F\0x09BootDriver
(ntoskrnl/mm/mminit.c:272) 00000BCE\0x09000003F2\0x09Free
(ntoskrnl/mm/mminit.c:272) 00000FC0\0x090000003F\0x09FirmwareTemporary
(ntoskrnl/mm/mminit.c:272) 00000FFF\0x0900000001\0x09SpecialMemory
(ntoskrnl/mm/mminit.c:272) 00001000\0x090003EFF0\0x09Free
(ntoskrnl/mm/mminit.c:272) 0003FFF0\0x0900000010\0x09SpecialMemory
(ntoskrnl/mm/mminit.c:272) 000FEC00\0x0900001400\0x09SpecialMemory
(ntoskrnl/mm/mminit.c:276) Total: 00041400 (1044 MB)
Used memory 1048512Kb
(ntoskrnl/ke/i386/kiinit.c:47) Large Page support detected but not yet taken advantage of!
IoReportResourceUsage at ntoskrnl/io/iomgr/iorsrce.c:701 is unimplemented, have a nice day
IoReportResourceUsage at ntoskrnl/io/iomgr/iorsrce.c:701 is unimplemented, have a nice day
(ntoskrnl/io/iomgr/driver.c:1283) '\Driver\BUSLOGIC' initialization failed, status (0xc00000c0)
(drivers/storage/class/disk/disk.c:1161) IoReadPartitionTable() status: 0x00000000
MmPageEntireDriver at ntoskrnl/mm/drvlck.c:89 is unimplemented, have a nice day
MmPageEntireDriver at ntoskrnl/mm/drvlck.c:89 is unimplemented, have a nice day
MmPageEntireDriver at ntoskrnl/mm/drvlck.c:89 is unimplemented, have a nice day
(drivers/video/videoprt/videoprt.c:670) No PNP Videocard .
(drivers/video/videoprt/videoprt.c:670) No PNP Videocard .
(ntoskrnl/io/iomgr/file.c:414) Using IopParseDevice() hack
(ntoskrnl/vdm/vdmmain.c:42) VME detected but not yet supported
(lib/rtl/registry.c:362) RTL: Expand variables for %SystemRoot%\system32\cmd.exe failed - Status == c0000023 Size a8 > 7e <e>
(lib/rtl/registry.c:362) RTL: Expand variables for %SystemRoot%\bin;%SystemRoot%\system32;%SystemRoot% failed - Status == c0000023 Size f4 > ac <14>
(drivers/filesystems/vfat/fsctl.c:279) SysType \0xebR\0x90N
(base/system/autochk/autochk.c:281) GetFileSystem() failed with status 0xc000000d
(lib/rtl/registry.c:362) RTL: Expand variables for %SystemRoot%\system32 failed - Status == c0000023 Size a0 > 7e <6>
(drivers/filesystems/cdfs/fsctl.c:536) CDFS: IRP_MN_USER_FS_REQUEST
(drivers/filesystems/cdfs/fsctl.c:536) CDFS: IRP_MN_USER_FS_REQUEST
(drivers/filesystems/cdfs/fsctl.c:536) CDFS: IRP_MN_USER_FS_REQUEST
(drivers/filesystems/cdfs/fsctl.c:536) CDFS: IRP_MN_USER_FS_REQUEST
(dll/win32/iphlpapi/ifenum_reactos.c:101) openTcpFile for <\Device\Tcp> failed: 0xc0000034
(dll/win32/iphlpapi/ifenum_reactos.c:101) openTcpFile for <\Device\Tcp> failed: 0xc0000034
Received V86 Emulation Opcode: 0

Re: same problems on older PC

Posted: Sat Oct 20, 2007 7:34 am
by PCS
UPDATE: Attempted SVN bootcd-29650-rel install with same hardware + same results; immediately blanks out after loading SERIAL.SYS driver. <ESC> key will blue-screen then reboot itself. Very well could be a Shared Video Memory issue. And I had such high hopes for ReactOS. I guess I'll just have to wait patiently for future releases and hope... :(
PCS wrote:I am experiencing the exact same screen blanking problem. Upon review of other's problems here, I tried installing a dedicated S3 Trio64V+ 86c765 PCI VGA card, which yielded the exact same results. In both cases, my system STILL goes blank right after loading the SERIAL.SYS driver. I had also specified resolutions during setup as low as 640x480x4 to help resolve any potential compatibility issues. Seems to me that with such simplistic, legacy hardware listed below, it should work with the greatest of ease. The most current PCLinuxOS/Knoppix/SLAX Kill Bill LIVE CD's boot to desktop and function perfectly with current system configuration.

OEM SYSTEM SPECS:
eMachines 566i
iCeleron 566
i810 Chipset
256MB RAM
7.5GB HDD
Intel Direct 3D AGP integrated video

me too...

Posted: Sun Dec 02, 2007 3:39 am
by mgmechanics
My Posting

http://www.reactos.org/forum/viewtopic. ... highlight=

seems to better fit into this topic.

Posted: Sun Dec 02, 2007 5:29 pm
by Haos
Thanks for your testing. I suggest putting those bugreports in Bugzilla, with debug logs attached. That way they wont get lost or misplaced.

Posted: Sat Dec 08, 2007 11:02 am
by aicommander
Any video card that is not compatible with VESA 2.0 will not work in ROS now. Our VGA driver is broken, but it will be fixed by 0.3.4 as it is a release blocker.