FC2 freezes on ThinkPad T22
Running latest T22 bios (v1.12).
The exact machine type and model is: 2647-8EG ( http://www-307.ibm.com/pc/support/si...Entry=2647-8eg ) Both Win2k and WinXP work 100% stable on this machine. Using 512MB (passed several runs of MemTest), and 500MB swap. This is a very basic FC2 installation without any development or server components. First free happened when I was browsing the Add Remove... 2nd free happened when I was surfing with Mozila. Anyone any idea? Thanks! Tom |
Can you try after running
system-config-display --reconfig --set-driver=vesa as root? Even if you end up with a less nice screen configuration. Could be that the lockup is related to your video driver, in which case submitting a bug report at http://bugzilla.redhat.com could be helpful. Be sure to provide information such as the output of /sbin/lspci -v and your X log files. There are also https://www.redhat.com/mailman/listinfo/fedora-list and https://www.redhat.com/mailman/listinfo/xfree86-list where you could ask. |
Tried that but got the following error message:
-------------------------------------------------------------------------------------------------- [root@xxxxxxx root]# system-config-display --reconfig --set-driver=vesa Traceback (most recent call last): File "/usr/share/system-config-display/xconf.py", line 412, in ? hardware_state.merge_into(xconfig) NameError: name 'hardware_state' is not defined -------------------------------------------------------------------------------------------------- What does it mean? |
Can't reproduce. It seems you are out-of-date as the line of code referred to is different here. Update system-config-display first with up2date or yum, even in text mode to prevent lockups. There is a Fedora Core 2 Update for the utility. You should get this when querying RPM:
$ rpm --query system-config-display system-config-display-1.0.17-2 |
Tried running up2date, and saw the system-config-display-1.0.17-2 update package.
The updates were installed and I restarted the computer, but when I wanted to test the system-config-display version again, it gave me a message that system-config-display is not installed ?!?!?! What have I done wrong? |
Please copy the full input and output from your attempt. I was not standing next to you when you tried it. ;)
|
Fair enough, and sorry :o you're totaly right!
[root@xxxxxxxx root]# rpm --query system-config-display package system-config-display is not installed [root@xxxxxxxx root]# |
Run up2date system-config-display in a console. That should install the package.
Btw, no reboot necessary. Only reason to reboot would be to boot a new kernel. |
Two things learned!
Thanks! :) Now I'll check whether the initial procedure you suggested (system-config-display --reconfig --set-driver=vesa) solves this freeze up problem. |
Don't misunderstand me, though. Turning on the VESA driver is not a fix, but just a test whether your freeze might be related to your other graphics driver.
|
How do I verify which driver is active without changing anything?
|
By reading /etc/X11/xorg.conf
|
When I run: system-config-display --reconfig --set-driver=vesa
it gives me the following result: ---------------------------------------------------------- [root@xxxxxxxx root]# system-config-display --reconfig --set-driver=vesa * ddcprobe returned bogus values: ID: None Name: None HorizSync: None VertSync: None Trying with card: S3 Savage/IX [root@xxxxxxxx root]# ---------------------------------------------------------- What does it means? |
That DDC probing of your display failed.
|
So I just need to choose LCD 1024x768 manually (in the graphic display setting), right?
(that's what IBM suggest) |
All times are GMT -5. The time now is 05:18 AM. |