| LinHES Forums http://forum.linhes.org/ |
|
| 7.1 Boot EDID issues? http://forum.linhes.org/viewtopic.php?f=22&t=22314 |
Page 1 of 1 |
| Author: | bpmcgee [ Sun Nov 13, 2011 2:52 pm ] |
| Post subject: | 7.1 Boot EDID issues? |
I started experiencing a new problem with 7.1 -- if I boot my front end connected to my TV it will hang with a black screen before it even begins to unpack the kernel. While investigating this, I tried setting "vga=ask" in the kernel command line, and doing a mode scan when prompted. It hangs in exactly the same way! So, I booted with the TV disconnected, and ran get-edid when it was booted. Very interesting: get-edid: get-edid version 2.0.0 Performing real mode VBE call Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0 Function supported Call successful VBE version 300 VBE string at 0x2110 "NVIDIA" VBE/DDC service about to be called Report DDC capabilities Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0 Function supported Call successful Monitor and video card combination does not support DDC1 transfers Monitor and video card combination does not support DDC2 transfers 0 seconds per 128 byte EDID block transfer Screen is not blanked during DDC transfer Reading next EDID block VBE/DDC service about to be called Read EDID Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0 Function supported Call failed The EDID data should not be trusted as the VBE call failed Error: output block unchanged Does this have to do with KMS and the NVidia drivers? I'm running an NVidia card. B |
|
| Author: | koneill [ Tue Nov 15, 2011 9:21 am ] |
| Post subject: | |
I don't know if this is any help, but I had to add: vmalloc=256M to my boot options for my system to boot with my NVidia card. |
|
| Author: | psicard [ Sat Nov 26, 2011 7:16 pm ] |
| Post subject: | |
I'm having a similar problem - screen goes black right after the BIOS stuff and stays that way. I tried adding the vmalloc=256M to all of the choices in /boot/grub/menu.lst. No change. I did a fresh install. No change. I poked around online and saw a few folks were having similar problems with the 290.10 drivers and other 7xxx chipsets. Some had success by rolling back to 285.05.09. I haven't tried that yet because I haven't quite figured out how to yet... FWIW: I have an nVidia 7150/630i. |
|
| Author: | brfransen [ Sat Nov 26, 2011 7:22 pm ] |
| Post subject: | |
psicard wrote: I poked around online and saw a few folks were having similar problems with the 290.10 drivers and other 7xxx chipsets. Some had success by rolling back to 285.05.09. I haven't tried that yet because I haven't quite figured out how to yet... 7.1 has 285.05.09, not 290.xx.
|
|
| Author: | psicard [ Sat Nov 26, 2011 11:24 pm ] |
| Post subject: | |
Thanks - I should've looked more carefully. Arch has 290 as the current version. I ran the beta of LinHES 7 fine for months with no problems until I rebooted after performing upgrades this week. I see the driver was updated from 280.13 in October - I'll have to try to switching to that. |
|
| Page 1 of 1 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|