Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

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.

I'm trying to upgrad from kernel 2.6.32.9 to 2.6.34.3 and I'm having problems.

The boot finished with that old gem "Kernel panic - not syncing: Attempting to kill init !"

I suspect that it's something to do with my PATA IDE driver because there have been kernel changes in this area.

My problem is all the boot messages scroll off the top of the screen before I can read them and it's no use saying look at dmesg or /var/log/messages because the root fs isn't there - another reason why I think it's to do with the drivers.

So my question is, is there some way I can slow down the boot process so that I have a chance of reading the messages ?

Tried Ctrl-S/Ctrl-Q and it doesn't work.

thanks

Click here to see the post LQ members have rated as the most helpful post in this thread.