Suse/NovellThis Forum is for the discussion of Suse 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.
does not list the device.
I commented out the /dev/sda5 line and booted teh system.
yast2 partioner also does not show the device now.
I have seen this kind of behavior in early release of mandrake 10.0 which did not have support for sata drives either.
This drive is important. is there any way I can roll back the kernel update?
OK, maybe there may be a problem with your particular S-ATA controller. Do you know which? What driver does MEPIS use (lsmod)?
In /etc/sysconfig/kernel, all the modules that are included into initrd are listed. Maybe the required driver is not among them (for whatever reason). But if you know the module, you can load it into initrd the same way like I suggested above for ext3.
Do you see any messages in /var/log/boot.msg about the drive detection?
Maybe a plain mkinitrd will work already. If not, load your MEPIS CD again and mount the S-ATA partition, then check with lsmod, which driver is used. Now get back to SUSE and try to load the module manually with 'modprobe <module>'.
Add this module to initrd by either typing 'mkinitrd -m <module>' or adding the driver to the list in /etc/sysconfig/kernel and running just 'mkinitrd' (this command look in the cofig file for modules to include).
1. You can use the repair function of the suse cd/dvd to bring back the old kernel. You should also check /etc/sysconfig/kernel; in this file the initrd modules are listed; the driver fro ext3 is included in the kernel (not as module)
2. Have a look in the mainboard manual. The chipset or additional sata-controller should be listed.
Hmm, just checked my /lib/modules for the sis5513 driver. Couldn't find it in SCSI! The kernel config claims the driver is compiled as module, so I was a bit confused. But then I found it under ide/pci! Not sure if it was always there, but it may be that the drive is now recognized as hdb5 instead of sda5. Can you find your S-ATA drive as hdx in 'fdisk -l'?