Bugzilla – Bug 148296
no driver works with my laptop
Last modified: 2006-02-19 17:42:12 UTC
This is probably related to 148292, but it feels like a different bug. I tried changing the driver from 'nv' to 'vesa' and restarting kdm. This is what I get in /var/log/Xorg.0.log: II) Reloading /usr/X11R6/lib/modules/linux/libint10.so (II) VESA(0): initializing int10 (II) VESA(0): Primary V_BIOS segment is: 0xc000 (II) VESA(0): VESA BIOS detected (II) VESA(0): VESA VBE Version 3.0 (II) VESA(0): VESA VBE Total Mem: 16384 kB (II) VESA(0): VESA VBE OEM: NVidia (II) VESA(0): VESA VBE OEM Software Rev: 3.17 (II) VESA(0): VESA VBE OEM Vendor: NVidia Corporation (II) VESA(0): VESA VBE OEM Product: NV11 Board (II) VESA(0): VESA VBE OEM Product Rev: Chip Rev B2 (==) VESA(0): Write-combining range (0xf0000000,0x1000000) (II) VESA(0): virtual address = 0xb6933000, physical address = 0xf0000000, size = 16777216 and that's it. No X. However, while the machine itself appears totally frozen, I *can* ssh into it. Since neither the vesa driver nor the nv driver appear to work, at this point I feel like I'm out of luck.
I think i figured it out. Comment this out and it works: #Option "CrtcNumber" "0" Why is that option set? I can't be sure but this likely won't work well for laptops.
This option is never set. Did you enable it manually. Please attach /etc/X11/xorg.conf, SaX2 has written before you edited it.
I certainly never added that option by hand. In fact, the first time I ever edited was to comment out that option. However, just to be sure, I did a second ground-up reinstall. This time X wouldn't start at all, the reason being it has an entry 'ChangeMe' in what looks like a dummy xorg.conf file. sax2 /still/ tries to use the NV driver which does not work properly. I'll try to get more information when I can.
I'll note that 10.1b4 seems to have fixed this, although this time I did not do a VNC install. If I encounter this again I'll be sure to update this bug.
Ok. Reopen if you encounter this again.