Regular Segmentation Fault: HELP!!!

1999-11-08 Thread Matthias Burghardt
Hi, I've been running Debian Linux for one year now on my P200MMX (mainboard FIC VA-502, chipset VIA 580VPX, AWARD BIOS, memory 2x32MB SDRAM, ATI Mach64 RageII+DVD, harddisks Quantum Bigfoot 2.1GB on /dev/hda, Seagate ST3491A 428MB on /dev/hdc, 24xCDROM on /dev/hdb, soundcard SB16 clone). The syst

Re: Segmentation Fault Help! 2nd call!

1999-10-24 Thread Doug Thistlethwaite
I hope somebody has an idea on what to do with my system. I am at a lost on what to do except to remove and re-install the packages which have the bad programs in. I get major warnings against doing this by dselect so I am holding off until I can get some more information on the implementation

Segmentation Fault Help!

1999-10-24 Thread Doug Thistlethwaite
Help! It seems that I really screwed my system up when I allowed dselect to update packages on my potato system. I am having a problem with segmentation faults for the following commands: su login passwd Because of this, I am not able to login any other processes (virtual terminals) nor will my

Re: Segmentation fault - help please -

1999-03-09 Thread Ralf G. R. Bergs
On Tue, 09 Mar 1999 22:45:17 +0100, [EMAIL PROTECTED] wrote: >$ pon provider >hda: irq timeout: status=0x50 { Drive Ready SeekComplete } You obviously have hardware problems with your hard drive... >/usr/bin/pon: line2: 5552 Segmentation fault /usr/sbin/pppd call >${1:-provider} ...that lead

Segmentation fault - help please -

1999-03-09 Thread homega
Hi, I quit x-window and try to connect as I did a while ago: $ pon provider hda: irq timeout: status=0x50 { Drive Ready SeekComplete } /usr/bin/pon: line2: 5552 Segmentation fault/usr/sbin/pppd call ${1:-provider} try again to the same results (just the 5552 number changes to 5562, 5572, 557