SlackwareThis Forum is for the discussion of Slackware 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've put a fresh install of 10.2 on my PC but it is failing to see my SATA disks. The motherboard is an ASUS P5NSLI.
When I start the install I use the sata.i kernel. But when I try to upgrade my kernel to 126.96.36.199 I get:
Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(8,2).
This is because it cannot see any of the SATA disks. I can boot beautifully into my 2.4.31 kernel, so I know there is nothing wrong with any of the hardware. The disks appear as sda and sdb respectively.
I have compiled Ext2 (my FS of choice), sata_nv and just about all Nvidia chipsets into the kernel directly but still no luck.
In Dmesg I get the following:
ata1: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xE400 irq 27
ata2: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xE408 irq 27
sata_nv 0000:00:0e: irq 27 request failed: -38
Does anyone have an idea would could be causing the IRQ problem? Or indeed what I could be missing?
I think so. I'm using the Nvidia SATA drivers under the SCSI sub-section, which I think is libata.
I can't give you an lsmod from the 188.8.131.52 kernel (as it won't load), but under 2.4.31 I get:
ide-scsi 9392 0
sk98lin 141768 1
If I try to boot 184.108.40.206, I get errors about IRQ assignment and to check with the vendor - but it goes really quickly and the kernel then panics. I can't scroll up as the machine then becomes non-responsive. As the root partition doesn't load, nothing gets written to dmesg or /var/log/messages.
I'm not sure the issue is surrounding which SATA driver to use, but more the fact that it can't access the SATA hardware due to some messing around with the IRQs.
"I can't give you an lsmod from the 220.127.116.11 kernel (as it won't load), but under 2.4.31 I get:"
Oh, duh. Sorry about that. (insert red-faced emoticon here).
They changed things around when they went from 2.4 to 2.6, so you can't really rely on what used to work. I have an Asus A7N8X mobo, but I'm not booting from SATA. But, I do have a SATA disk hooked up to it. The only two modules that seem to be needed are libata and sata_nv. Have you tried booting a livecd and see what things look like? That would probably be my next step.
Me and you both buddy. Slack is my first distribution of linux, except for a SuSE introduction for about 3 weeks which was soon ditched for the light.
Yeah man, I keep getting the same error, yet I will admit, I am having slightly more success. I got my kernel recompiled and bootable, everything works, with 18.104.22.168; however, I downlaoded kernel 22.214.171.124 because I became aware it's a known version that'll work with my ATI proprietary drivers. Also, the patches available are, i think, only available for a couple versions of the 2.6 kernel. Anyway, here i am trying to figure this out, going over and over this menuconfiguration thing, trying to sort out the whack junk that doesn't need to be there and what does. I got the idea not too long ago about booting into 126.96.36.199 and viewing the .config file from menuconfig before, and compare. If I can do something to help ya, let me know. Want me to try and post my whole .config?
I, too, have an Asus motherboard. I have a Seagate baracooda SATA hard drive, just one - not two. It's not on IDE, that wide, thin gray connector. But eyah, I somehow got it to work. My motherboard is a P4C800 Deluxe. Lemme know if there's some sort of command I can output for ya.
This isn't directly Slackware related, but I believe there's a boot option "pci=nomsi" that you can use to enable SATA drives to be seen properly. I do know I needed this for a recent openSUSE 10.2 install I did on a brand-new Dell laptop with a SATA drive.