Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 had this problem in RH 8 and now the same issue in 9. I'm running a machine that has an on-board SCSI controller - Qlogic ISP1040. Both RH 8 & 9 identified it as a ISP1020 which worked on initial installation for both 8 & 9. The problem starts when I use RHN to update the OS. Every subsequent update (at least 6 updates of the kernel in 8 and now one in 9) result in the kernel panic-ing on boot-up. It happens at isp_mod.o and says something about loading support for FCAL or something like that.
I'm not really sure where to look first. I guess it would help to be able see the boot messages, but I cannot find the boot log when the kernel panics, I guess the kernel doesn't even write the log to the drive before it panics!? I heard you can re-direct the boot output to a serial port and capture it on another CPU, bit don't know how to do that either!
It sounds like with subsequent updates the OS is trying to load an additional driver over the mid-level SCSI driver that it should not be doing, but I don't know where to change it from trying that. Any pointers on what to try next, or read next would be appreciated!