SuSE 7.3 updated to KDE 2.2.2 and 2.4.16 with latest X update. / is ext3. I recently installed 7.3, then went to update over a couple of days. I was able to update KDE through YOU with good success :-) (thanks SuSE!), as well as downloaded the kernel update and X update. Yesterday, my system started locking up tight (it never did this under 6.4). The KOffice update started causing errors with susewm, so I just uninstalled it thinking it maybe was causing the lockups as well. To digress a bit, when I booted yesterday evening, hda7 had reached maximal mount count and was fskd (which took a while, just like ext2), but then booted fine. A little later, it crashed (in KDE). When it crashed, CTL-ALT-BSP, mouse, keyboard anything would not work. I could only hit the reset button. Rebooting showed the advantages of ext3, as it was able to recover in seconds from the crash. But it crashed again several times, each running a different program. Since removing the KOffice update fixed only the susewm problem, I backtracked. I am now back to the original X, and so far no problems. That prompts me to ask if anyone else has seen this (BTW video card is ATI Rage Fury 128)? Also, besides installing the X updates via YaST, is there anything else that should be done to update X? Does the updated SAX2 need to be run to configure something new? Until I get some feedback, I think I will stick with the original X 4.10 and see if I no longer see the hard crashes. TIA for any help. :-) -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: www.mydestiny.net/~joe_morris Registered Linux user 231871 "We can stand affliction better than we can prosperity, for in prosperity we forget God." --Dwight Lyman Moody
On Tuesday 08 January 2002 15.55, Joe & Sesil Morris (NTM) wrote:
That prompts me to ask if anyone else has seen this
Yes, I had severe problems when I upgraded X. Ben Rosenberg had something similar too, and he adviced me to go back to the version on the CDs and since then I've had no problems. //Anders
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Try adding append = "disableapic vga=0x0314" to lilo.conf & run lilo. All kernels now come with apic enabled, which causes this very problem on uniprocessors. :) On Tuesday, 8 January 2002 8:55, you wrote:
SuSE 7.3 updated to KDE 2.2.2 and 2.4.16 with latest X update. / is ext3.
I recently installed 7.3, then went to update over a couple of days. I was able to update KDE through YOU with good success :-) (thanks SuSE!), as well as downloaded the kernel update and X update. Yesterday, my system started locking up tight (it never did this under 6.4). The KOffice update started causing errors with susewm, so I just uninstalled it thinking it maybe was causing the lockups as well. To digress a bit, when I booted yesterday evening, hda7 had reached maximal mount count and was fskd (which took a while, just like ext2), but then booted fine. A little later, it crashed (in KDE). When it crashed, CTL-ALT-BSP, mouse, keyboard anything would not work. I could only hit the reset button. Rebooting showed the advantages of ext3, as it was able to recover in seconds from the crash. But it crashed again several times, each running a different program. Since removing the KOffice update fixed only the susewm problem, I backtracked. I am now back to the original X, and so far no problems. That prompts me to ask if anyone else has seen this (BTW video card is ATI Rage Fury 128)? Also, besides installing the X updates via YaST, is there anything else that should be done to update X? Does the updated SAX2 need to be run to configure something new? Until I get some feedback, I think I will stick with the original X 4.10 and see if I no longer see the hard crashes. TIA for any help. :-)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8PKqUnQ18+PFcZJsRAijHAJ95e3ji/+XV6Em5h0ff2Wtu5Zte4ACfS0Yd IATMQNwEKhFfgqgCAB1XFVo= =MZOs -----END PGP SIGNATURE-----
Try adding append = "disableapic vga=0x0314" to lilo.conf & run lilo.
All kernels now come with apic enabled, which causes this very problem on uniprocessors.
:)
On Tuesday, 8 January 2002 8:55, you wrote:
Yesterday, my system started locking up tight (it never did this under 6.4).
Thanks for the suggestion, but after reading about this problem for the
Carl A. Cook wrote: past several months, I did this on install (knowing I only have one processor). I have disableapic vga=0x0317 hdd=idescsi apm=no-power-off (got this one from sdb as I was getting a segmentation fault just before reached master resource level 0, I have an AT power supply not an ATX). So it is not an APIC problem, but I have traced it down to (apparently) something in the 2.4.16 kernel. So far, using the 2.4.10 that came with 7.3, it has not locked up (but I am still testing as it randomly happened). I have reinstalled the X update, tried both the k_deflt and k_i386 2.4.16 kernel from the ftp site, and on both kernels I get the lockups. I never had this computer lock so tight under 6.4, so I am going to conyinue with 2.4.10 til I can verify it is not locking up for another reason, then try to find out what in 2.4.16 is causing this. BTW, machine is AMD K6-3 400. 384M. It ran flawlessly under the previous 2.2.19 I had with 6.4. Thanks again for trying. -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: www.mydestiny.net/~joe_morris Registered Linux user 231871 "We can stand affliction better than we can prosperity, for in prosperity we forget God." --Dwight Lyman Moody
participants (3)
-
Anders Johansson -
Carl A. Cook -
Joe & Sesil Morris (NTM)