I have an old PC that I need to use to do work on. It has some decent specs (P4 with 1GB RAM). The thing is after a few minutes or a few hours after boot, the machine completely locks up. I have a feeling it has something to d with the video, but I’m not sure as I don’t know where to go to check the logs.
Plus since opensuse 11.2 has no xorg.conf, I can’t change to vesa. Here is the output for lspci
I may be off track, but could you maybe start up a couple terminals with “tailf /var/log/messages” and “tailf /var/log/Xorg.0.log”? Then let it sit till it locks up; see what’s last in those files.
Also, for experimenting, you can generate an xorg.conf with “Xorg -configure”. IIRC, that will create the same config that Xorg would otherwise automatically “create” on startup. That should let you see what settings and drivers are in use (and tweak them if necessary).
From a quick google search, it appears this is a well known bug. You may have to settle for a less-than-optimal driver until the issue is resolved (hopefully openSUSE will include the fix in the updates).
check /var/log/messages there can be useful info about last fatal error. Also, what do you mean by “locks up”, could you move the mouse? Could you restart X Windows? It can be hard drive problem, since it is very old computer…
Well it froze again, and i have the results. not too happy with them either:
tailf /var/log/messages:
Dec 8 14:38:07 linux-e5we smartd[1670]: Device: /dev/sda [SAT], SMART Usage Attribute: 199 UDMA_CRC_Error_Count changed from 182 to 122
Dec 8 14:57:54 linux-e5we rsyslogd: -- MARK --
Dec 8 14:58:32 linux-e5we dhclient: DHCPREQUEST on eth0 to 192.168.0.1 port 67
Dec 8 14:58:32 linux-e5we dhclient: DHCPACK from 192.168.0.1
Dec 8 14:58:32 linux-e5we dhclient: bound to 192.168.0.184 -- renewal in 1602 seconds.
Dec 8 15:08:07 linux-e5we smartd[1670]: Device: /dev/sda [SAT], SMART Usage Attribute: 199 UDMA_CRC_Error_Count changed from 122 to 180
Dec 8 15:25:14 linux-e5we dhclient: DHCPREQUEST on eth0 to 192.168.0.1 port 67
Dec 8 15:25:14 linux-e5we dhclient: DHCPACK from 192.168.0.1
Dec 8 15:25:14 linux-e5we dhclient: bound to 192.168.0.184 -- renewal in 1764 seconds.
Dec 8 15:27:07 linux-e5we foo2zjs-wrapper: foo2zjs-wrapper -P -z1 -L0 -r1200x600 -p1 -m1 -s7
and tailf /var/log/Xorg.0.log:
(II) intel(0): EDID vendor "DEL", prod id 40992
(II) intel(0): I2C bus "CRTDDC_A" initialized.
(II) intel(0): I2C bus "CRTDDC_A" removed.
(II) intel(0): I2C bus "CRTDDC_A" initialized.
(II) intel(0): I2C device "CRTDDC_A:E-EDID segment register" registered at address 0x60.
(II) intel(0): I2C device "CRTDDC_A:ddc2" registered at address 0xA0.
(II) intel(0): I2C device "CRTDDC_A:ddc2" removed.
(II) intel(0): I2C device "CRTDDC_A:E-EDID segment register" removed.
(II) intel(0): I2C bus "CRTDDC_A" removed.
(II) intel(0): EDID vendor "DEL", prod id 40992
(II) intel(0): Using hsync ranges from config file
(II) intel(0): Using vrefresh ranges from config file
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz)
(II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
(II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
(II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
(II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
(II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
(II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
(II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
(II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
(II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(II) intel(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz)
(II) intel(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
(II) intel(0): EDID vendor "DEL", prod id 40992
starting to wonder if it is my HDD thats the problem though. I changed the HDD lately and this started to happen
Can’t say I’m too happy with those results either.
The last message in /var/log/messages is interesting. foo2zjsis an open source printer driver for printers that use ZjStream wire protocol. Do you have such a printer? I don’t see how that would cause a lockup. Googling “foo2zjs lockup” only brings up printer lockup issues, as would be expected.
Then you have a DHCP renewal; what ethernet card/driver are you using? Are there any known issues with that?
And yes, the hard drive; you have two messages concerning the error count from smartd. Is this a new drive? Can you verify that the trouble started when you changed drives?
I have experienced lockups when a hard drive was failing, so that is a real possibility.
I don’t see anything of interest in the Xorg.0.log, so it looks like maybe your video driver isn’t the culprit after all?
Hope this gives you some idea of what to look for. I’ll check back.