linux-kernel - Unable to find root fs with libata only 2.6.18-mm3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 07 Oct 2006 20:52:48 -0400
From:	Ed Sweetman <safemode2@...cast.net>
To:	linux-kernel@...r.kernel.org
Subject: Unable to find root fs with libata only 2.6.18-mm3

I dont have scsi or ide/ata support compiled into my kernel, only the 
libata drivers, now that they're split out from the scsi tree.  As far 
as I could see from the "help" dialog, this was a valid configuration.   
However, I can't load the root fs using any scsi device name or ide 
device name.  eg, /dev/sda1, /dev/sdb1, /dev/sdc1, /dev/hda1 etc etc.  I 
tried the LABEL=/ option in the boot args, which should work and that 
gave me nothing.   

My question is, do I still need to compile in scsi disk/cdrom/generic 
support into my kernel to get libata devices to work or is there some 
other syntax i'm missing?    Libata detects my drives, but as far as I 
could see, and it flies by too fast to read, no device nodes were 
assigned to them.

If you do need scsi support, why isn't that done automatically when you 
select your libata drivers? or at least a pointer in the "Help" dialog 
to tell you to enable that ?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/