On 11/12/2010 02:10 PM, Hugo Vanwoerkom wrote:
On 11/12/2010 01:49 PM, Camaleón wrote:
On Fri, 12 Nov 2010 12:06:16 -0600, Hugo Vanwoerkom wrote:
I have 2 kernels: Debian's 2.6.32-5-686 and my own 2.6.36-hvw.
The former no longer has /dev/hd* the latter does as shown by blkid. [1]
blkid for 2.6.32-5-686 and [2] for 2.6.36-hvw.
What kernel option is responsible for that? Obviously I don't have that
set in 2.6.36-hvw.
(...)
In brief, if I got it correctly, your Maxtor hard disk (IDE) is being
detected as "/dev/hd*" in 2.6.36 (using legacy pata module) and as "/dev/
sd*" in 2.6.32 (using new libata module).
Back to days I was using openSUSE, pata modules were loaded by telling
the kernel "hwprobe=-modules.pata" at GRUB prompt (or by stating so in
menu.lst). Maybe you are inadvertenly loading legacy pata module or you
have compiled the kernel with that flag switched on :-?
Compare both "lsmod | grep ata" outputs.
Good suggestion:
h...@debian:/$ grep ata 11.2.6.32-5-686.lsmod
ata_generic 2047 0
libata 115745 3 ata_generic,sata_via,pata_via
pata_via 5701 4
sata_via 5608 0
scsi_mod 101401 6 ums_cypress,usb_storage,sg,sr_mod,sd_mod,libata
h...@debian:/$ grep ata 11.2.6.36-hvw.lsmod
ata_generic 2075 0
libata 116648 2 ata_generic,sata_via
sata_via 5380 0
scsi_mod 100151 5 sg,sd_mod,ums_cypress,usb_storage,libata
So both kernels have libata, but only 2.6.32-5-686 has pata_via and sr_mod.
lsmod | grep sr_mod
h...@debian:/usr/src/linux-2.6.36$ grep CONFIG_BLK_DEV_SR .config
CONFIG_BLK_DEV_SR=m
that is the SCSI CDrom module and that is set in the kernel.
Don't know why it does not show up in lsmod.
That leaves the pata_via module and that indeed is not set.
So the difference in getting /dev/hd* is solely due to the absence of
the pata_via module?
Hugo
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/ibk847$q4...@dough.gmane.org
