I saw on the suse website where there is an updated version of XFree86 (4.0.2) as well as an updated xloader and xmodules packages. I will be installing these and see if this solves the problem.
As for my system components: ABIT KT7-RAID Motherboard w/ an Athlon 800 ATI Rage 128 video card SoundBlaster Live 2 Realtek RTL8139B ethernet cards 2 DiamondMax Hard drives Toshiba CD-RW/DVD-ROM #SD-R1002
The output from lspci is: 00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0305 (rev 02) 00:01.0 PCI bridge: VIA Technologies, Inc.: Unknown device 8305 00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super] (rev
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev
00:07.2 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 10) 00:07.3 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 10) 00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30) 00:09.0 Communication controller: Lucent Microelectronics Venus Modem (V90, 56KFlex) 00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev
00:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev
00:0f.0 Multimedia audio controller: Creative Labs SB Live! EMU10000 (rev
00:0f.1 Input device controller: Creative Labs SB Live! (rev 08) 00:13.0 Unknown mass storage controller: Triones Technologies, Inc. HPT366 (rev 03) 01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 RF
On Monday 06 August 2001 11:34, you wrote:
I've seen this kind of thing happen for 2 reasons I've been able to
out on my systems... after running XFree86 4 for a few minutes with my Diamond (since taken over by S3, now SonicBlue... it's so hard to keep track) Stealth III S540 (based on the Savage 4 or 4+, I think), the system will lock up hard... 3.3.6 was no problem, and I haven't tried the latest version of X, which is now supposed to have special drivers for that chipset, and it tends to happen much more often than once every few days, but since I know nothing about your system, I thought I'd mention it... The other thing that seems to cause it is a lot of hard disk activity on an Intel PIIX3 controller (for an old Pentium/166). Copying large files to/from a Reiserfs partition with DMA enabled seems to really do the
I am running SuSE 7.0 with the 2.2.18? kernel. I have not compiled my own kernel before. Last night when attempting to upgrade to XFree86 4.1 I somehow f**ked up my configuration and can now only run X as root and I don't know what changed to cause that to happen. I had backed up my entire partition so the original configuration files are around but I am not sure which files I should restore to get back to my original configuration. I am contemplating upgrading to SuSE 7.2 with the 2.4.x kernel and reformatting my partition to be a Rieserfs file system. Is this configuration likely to be any more stable than my current configuration? -----Original Message----- From: Ben Dow [mailto:bdow@WPI.EDU] Sent: Monday, August 06, 2001 10:43 PM To: wlug@mail.wlug.org Subject: Re: [Wlug] System crash Well, XFree86 4.1 is out, which is what I was referring to, but as far as I know, that's a really well-supported video card (the chipset's been around forever)... what kernel are you running? Is it a stock Suse kernel? Do you know how to compile your own, if it might help? On Mon, 6 Aug 2001, Michael Long wrote: 22) 10) 10) 10) 08) figure trick
(I should probably send in a kernel bug report, really)... but that's another possibility, I guess. Again, tell us some more about your system (lspci often gives useful information). Now to wake up.
Ben
On Mon, 6 Aug 2001, Long, Mike wrote:
Hi all,
I have been having problems with my system locking to the point where I needed to press the reset button to recycle the box. Well, this happened again and this time things are not working properly after bringing the system back up. I have been able to start networking services and I can start KDE desktop but none of my X applications will run. Now I have several questions:
1) What type of problems could have been created by an improper shutdown of the box? 2) Will reinstalling KDE fix this problem? 3) How do I go about figuring out what is causing my machine to lock up? It is happening frequently (every few days) and when I am doing different things. I have not been able to determine a pattern.
Thanks, Mike
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
_______________________________________________ Wlug mailing list Wlug@mail.wlug.org http://mail.wlug.org/mailman/listinfo/wlug
Long, Mike said:
I am running SuSE 7.0 with the 2.2.18? kernel. I have not compiled my own kernel before. Last night when attempting to upgrade to XFree86 4.1 I somehow f**ked up my configuration and can now only run X as root and I don't know what changed to cause that to happen. I had backed up my entire partition so the original configuration files are around but I am not sure which files I should restore to get back to my original configuration.
Only as root? Try looking at /etc/X11/Xserver and see what the second line reads. The first line in this file is the full pathname of the default X server. The second line shows who is allowed to run the X server: RootOnly Console (anyone whose controlling tty is on the console) Anybody (assuming this is the same in 4.1 as it is in 4.0.x, and the filename is the same in Suse as in other distros...) -- Aaron Haviland orion [at] tribble [dot] dyndns [dot] org orion [at] parsed [dot] net Release the Mongoose!
participants (2)
-
Aaron Haviland -
Long, Mike