Quote:
Originally Posted by rtmistler
I think it's just "X --configure" not Xorg, but I may be incorrect.
Since you have it working when you're root, try comparing the Xorg.0.log from the good session versus the bad session.
|
X is just a symlink to Xorg, so it's the same thing.
I did try comparing the two Xorg.log files. What I found was this:
In the working file, these two lines are followed by literally pages and pages of VESA reported data.
Code:
(II) VESA(0): initializing int10
(II) VESA(0): Primary V_BIOS segment is: 0xc000
While, in the non-working log file, those two lines are replaced with these:
Code:
(II) VESA(0): initializing int10
(EE) VESA(0): Cannot read int vect
After which it unloads the modules "vesa," "int10" and "vbe" and then gives the "No screens found" error.
Does this help?