Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I just put the post there because I thought it might help with the kernel panic thing since the problem with konqueror is not related to a particular distro or kernel. Also had the same problem with reisser and ext2,ext3 filesystems.
Weird, strictly Konq and doesn't make the machine crash... have you tried to check to see if its a bug in that version of konq. Or better yet, maybe konq has a verbose de-bugging option, you could launch it from the X-term, make it crash, and watch if it spits errors to the term.
It doesn't really crash - it just slows down to a point where it takes about 1min just to change a directory. Top doesn't show it eating up CPU. Didn't want to butt in on this thread - just thought it might be interesting.
Well I'll try tomorrow to get DRI working with my SIS730 after that I am probably in line for a new install anyway.
Couldn't get it to crash yesterday - as always the error never shows up when you need it.
Compiling a new kernel right now (for different reasons) - lets see what that is doing.
BTW lolx have fun with debian i put it on 1 month ago and love it so far.
P.S If you want to upgrade debian or install it you really only need bootdisks and then download just the stuff you want - no need for downloading the whole cd's
Last edited by crashmeister; 06-18-2002 at 10:53 AM.
As i wanted to install Debian, i had a very big surprise : a few minutes after entering the install procedure i had a ... kernel panic !!!
At last i was sure that the problem was a hardware problem but at this time i didn t know what it was : i ve tested the ram, the drives seemed to work okay, the network cards, the video card ,
the processor, and the cpu ... Nothing ...
As my system disk was erased, i tried to take it off the server and mounted it to a win station ... After format and intensive file transfert there were no problem about the drive .... But ... as soon i wanted to put it off the tower, i noticed something very surprising again : it was VERY HOT !!! I nearly couldn t take it in my hands for a few seconds ...
So i definitely put the
QUANTUM FIREBALLP AS20.5, ATA DISK drive
out of from the server, backuped the IBM-DTLA-307020 (20GO) on the IC35L040AVER07-0 (IBM 40Go) and then installed mandy 8.2 again on a newly created IBM-DTLA-307020 system partition as well as the original IBM-DTLA-307020 data on a second partition ...
I could walk trough the install process without problem, now i am planning a set of tests including intensive file transfer to see if the kernel panic wants its revenge ; ) ....
Whoa, the disk got to hot to hold? holy fat cats batman. Now I'm a little gimped from some of my compatriots in hardware because I'm on a nickel and dime budget, but I'm pretty certain Hard drives aren't support to fry eggs. Did that thing take a low level format or an integrity check or anything? If so how did it pass 'em and get that bloomin' warm?