PDA

View Full Version : F7-test4 Install gives BSOD on Thinkpad T60p


dj_segfault
2007-05-19, 11:27 PM CDT
This is my first experience with a testing release, so I apologize if
I'm not reporting this right, or not giving enough information.

I just got a Lenovo Thinkpad T60p. It's got a 15.4" WSXGA+
TFT/1680x1050 (16:10) screen driven by a ATI Mobility Fire GL V5250 256MB.

When I attempt a graphical install of F7-test4, after the few initial
"Loading..." screens, I get a few flashes with pretty patterns, then the
screen turns all blue with no writing, and stays that way indefinitely.

When I attempt a text mode install (the pain! the pain!), the install
works, but it doesn't configure X. When I try to run X, I get a quick
screen flash or two, then it kicks me back to the CLI, but now all
sessions are 40 characters wide and twice as tall, so I can't edit files
or type anything out. Nothing but a reboot fixes this. I tried
system-config-display, but that exited out, too. I tried redirecting
the output to a file, and I did at one point see a message about not
being to get Xinerama info.

Since I had nothing to lose, I tried installing FC6, and the graphical
install worked just fine. It couldn't quite pick out the graphics card
("ATI Technologies Inc Unknown device 71d4"), but after changing the
monitor type (to "LCD Panel 1680x1050"), I was able to get X up to
1400x1050 (the screen stretched. It's not 16:10, but it's better than a
BSOD).

I looked in Bugzilla for ATI 5240, but didn't see anything.
Is there something I missed in BugZilla?

Should I enter this as a new bug?

Is there something else I can try?

Thanks in advance.

alpha645
2007-05-20, 12:13 AM CDT
You could try installing the drivers from Ati, because those seem to support your card. Try rebooting into grub and do this:

- Go to your latest FC7test4 kernel
- Select the second line en the menu that appears
- Press 'e'
- Add the line:

video=vesafb vga=0x307

- Press escape
- Press b

Note that the line is not saved, so you need to do this all over again after every reboot.

If this doesn't work, try another mode, and use:

video=vesafb vga=ask

Try some options from that menu if you want.

This should at least give a 1280*1024 (or worse) console. This way, I might be able to help you further, just get this done for now.

dj_segfault
2007-05-20, 05:30 PM CDT
alpha645, thanks. "video=vesafb vga=0x307" was a slight improvement, in that it didn't work, but the screen was left in a usable text mode, so I could see what was happening.

On the stdout of the first pty, it says (roughly: I couldn't mount my thumbdrive to copy files over):
Runing Anaconda.....
Probing for video card: ATI Technologies In M56GL [Mobility FireGL V5250]
Attempting to start native X server
Waiting for X server to start...log located in /tmp/ramfs/X.log
1...2...3...4...5... X server started successfully.

Gdk-ERROR **: error while retrieving Xinerama information
aborting...

The X.log file seems to have several *****ings about font issues, like "No FontPath specified." and "Could not init font path element unix/:7100, removing from list!:
"FreeFontPath: FPE "built-ins" refcount is 2, should be 1; fixing."

It ends with (again, typed by hand):
{EE} AIGLX: DRI module not loaded
(II) GLX:initialized MESA-PROXY GL provider for screen 0
(II) <default pointer>: psZEnabledataReportingL succeeded
Could not init font path element unix/:7100, removing from list!:

Fatal server error:
could not open default font 'fixed'

leigh123linux
2007-05-20, 05:34 PM CDT
alpha645, thanks. "video=vesafb vga=0x307" was a slight improvement, in that it didn't work, but the screen was left in a usable text mode, so I could see what was happening.

On the stdout of the first pty, it says (roughly: I couldn't mount my thumbdrive to copy files over):
Runing Anaconda.....
Probing for video card: ATI Technologies In M56GL [Mobility FireGL V5250]
Attempting to start native X server
Waiting for X server to start...log located in /tmp/ramfs/X.log
1...2...3...4...5... X server started successfully.

Gdk-ERROR **: error while retrieving Xinerama information
aborting...

The X.log file seems to have several *****ings about font issues, like "No FontPath specified." and "Could not init font path element unix/:7100, removing from list!:
"FreeFontPath: FPE "built-ins" refcount is 2, should be 1; fixing."

It ends with (again, typed by hand):
{EE} AIGLX: DRI module not loaded
(II) GLX:initialized MESA-PROXY GL provider for screen 0
(II) <default pointer>: psZEnabledataReportingL succeeded
Could not init font path element unix/:7100, removing from list!:

Fatal server error:
could not open default font 'fixed'


Try adding these to your xorg.conf


Section "Extensions"
Option "Composite" "False"
EndSection


Section "ServerFlags"
Option "AIGLX" "off"
EndSection

Section "DRI"
Mode 0666
EndSection

alpha645
2007-05-20, 11:35 PM CDT
Try adding these to your xorg.conf


Section "Extensions"
Option "Composite" "False"
EndSection


Section "ServerFlags"
Option "AIGLX" "off"
EndSection

Section "DRI"
Mode 0666
EndSection

Ehm, I think he is still using Vesa as driver. That driver is compatible with the compositor... . I think he should turn off xinerama:

Section "ServerFlags"
Option "Xinerama" off
EndSection

leigh123linux
2007-05-21, 03:57 AM CDT
Ehm, I think he is still using Vesa as driver. That driver is compatible with the compositor... . I think he should turn off xinerama:

Section "ServerFlags"
Option "Xinerama" off
EndSection


Well he has a AIGLX DRI error

It ends with (again, typed by hand):
{EE} AIGLX: DRI module not loaded
(II) GLX:initialized MESA-PROXY GL provider for screen 0
(II) <default pointer>: psZEnabledataReportingL succeeded
Could not init font path element unix/:7100, removing from list!:

dj_segfault
2007-05-21, 05:57 AM CDT
Turning off Xinerama helped with that problem, but it still produces all the font errors and dies with the font message at the end. Could it be looking for fonts that will work in that resolution, or at least that aspect ratio?