>On Mon, 15 Mar 2010 11:40:52 +0000, you wrote: >On 15/03/2010 11:19, George R. Kasica wrote: >[...] >>> Oh dear. You don't have a 1920x1080 mode so the driver's trying >>> 1600x1200 which your monitor may not support. Try adding the following >>> below the VertRefresh line: >>> >>> # 1920x1080 59.96 Hz (CVT 2.07M9) hsync: 67.16 kHz; pclk: 173.00 MHz >>> Modeline "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 >>> 1088 1120 -hsync +vsync >>> >>> Or if your monitor supports reduced blanking: >>> # 1920x1080 59.93 Hz (CVT 2.07M9-R) hsync: 66.59 kHz; pclk: 138.50 MHz >>> Modeline "1920x1080" 138.50 1920 1968 2000 2080 1080 1083 1088 >>> 1111 +hsync -vsync >>> >>> Of course, this is still a workaround until we find out why the driver's >>> not correctly detecting your monitor and getting a suitable modeline >>> directly from it. >> Changes made logs attached since list won't allow long attaches. First >> is the first change...black screen...second one very bad idea...killed >> the keyboard input took a reboot to fix it....for what its worth >> Windows run at 1600 x 1200 here 32 bit color (2 different PCs) should >> we be aiming for that - that would suffice here. > >Neither modeline should have caused a crash like this. I think we have >to go back to earlier in the thread. Have you been into the BIOS and >actually set 64M of video RAM? Yes.way back on the first exchange of emails...the keyboard is totally dead, cant even get a num lock on or off light.
George _______________________________________________ openchrome-users mailing list [email protected] http://wiki.openchrome.org/mailman/listinfo/openchrome-users Main page: http://www.openchrome.org Wiki: http://wiki.openchrome.org User Forum: http://wiki.openchrome.org/tikiwiki/tiki-view_forum.php?forumId=1
