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.

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2010.11.12.19.49.30@gmail.com">http://lists.debian.org/pan.2010.11.12.19.49.30@gmail.com

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:

hugo@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

hugo@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.

Hugo



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: ibk709$lcc$1@dough.gmane.org">http://lists.debian.org/ibk709$lcc$1@dough.gmane.org

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:

hugo@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
hugo@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
hugo@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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: ibk7un$pk6$1@dough.gmane.org">http://lists.debian.org/ibk7un$pk6$1@dough.gmane.org

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:

hugo@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
hugo@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
hugo@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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: ibk847$q4u$1@dough.gmane.org">http://lists.debian.org/ibk847$q4u$1@dough.gmane.org

On Fri, 12 Nov 2010 14:10:48 -0600, Hugo Vanwoerkom wrote:

> On 11/12/2010 01:49 PM, Camaleón wrote:

(...)

>> Compare both "lsmod | grep ata" outputs.
>>
>>
> Good suggestion:
>
> hugo@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

If that's correct, then I'm missing :-)

kernel 2.6.32 was not the one using legacy driver _but_ it is
loading it (pata_via).

hugo@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.

Yep, but 2.6.32 was using "/dev/sd*" nomenaclature for Maxtor disk >:-?

2.6.32-5-686
/dev/sda1: LABEL="6Y080P0.01" UUID="1205def1-2141-4b3a-97d0-0b94ca1c4ff2" TYPE="ext2"
/dev/sda5: LABEL="6Y080P0.05" UUID="dc767bc6-ebe4-4dfb-a8f1-739709598dc7" TYPE="ext2"
/dev/sda6: LABEL="6Y080P0.06" UUID="a7cfe5f2-b136-4a73-ac8a-f3e2121102c8" TYPE="ext2"
/dev/sda7: LABEL="6Y080P0.07" UUID="45ee8af8-c443-42d4-ae59-6f68e33932e8" TYPE="ext2"
/dev/sda8: LABEL="win_D" UUID="4131-BA32" TYPE="vfat"
/dev/sda9: LABEL="6Y080P0.09" UUID="5a09faf0-6f8e-4c72-a23b-46fe963754ef" TYPE="swap"
/dev/sda10: LABEL="6Y080P0.10" UUID="66c1d026-1e4c-4392-8aa0-e0d9f2cb4277" TYPE="ext2"

2.6.36-hvw
/dev/hda1: LABEL="6Y080P0.01" UUID="1205def1-2141-4b3a-97d0-0b94ca1c4ff2" TYPE="ext2"
/dev/hda5: LABEL="6Y080P0.05" UUID="dc767bc6-ebe4-4dfb-a8f1-739709598dc7" TYPE="ext2"
/dev/hda6: LABEL="6Y080P0.06" UUID="a7cfe5f2-b136-4a73-ac8a-f3e2121102c8" TYPE="ext2"
/dev/hda7: LABEL="6Y080P0.07" UUID="45ee8af8-c443-42d4-ae59-6f68e33932e8" TYPE="ext2"
/dev/hda8: LABEL="win_D" UUID="4131-BA32" TYPE="vfat"
/dev/hda9: LABEL="6Y080P0.09" UUID="5a09faf0-6f8e-4c72-a23b-46fe963754ef" TYPE="swap"
/dev/hda10: LABEL="6Y080P0.10" UUID="66c1d026-1e4c-4392-8aa0-e0d9f2cb4277" TYPE="ext2"

Is that right?

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2010.11.12.21.13.07@gmail.com">http://lists.debian.org/pan.2010.11.12.21.13.07@gmail.com

On Fri, 12 Nov 2010 14:10:48 -0600, Hugo Vanwoerkom wrote:


On 11/12/2010 01:49 PM, Camaleón wrote:


(...)


Compare both "lsmod | grep ata" outputs.



Good suggestion:

hugo@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


If that's correct, then I'm missing :-)

kernel 2.6.32 was not the one using legacy driver _but_ it is
loading it (pata_via).

hugo@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.


Yep, but 2.6.32 was using "/dev/sd*" nomenaclature for Maxtor disk >:-?

2.6.32-5-686
/dev/sda1: LABEL="6Y080P0.01"
UUID="1205def1-2141-4b3a-97d0-0b94ca1c4ff2" TYPE="ext2"
/dev/sda5: LABEL="6Y080P0.05"
UUID="dc767bc6-ebe4-4dfb-a8f1-739709598dc7" TYPE="ext2"
/dev/sda6: LABEL="6Y080P0.06"
UUID="a7cfe5f2-b136-4a73-ac8a-f3e2121102c8" TYPE="ext2"
/dev/sda7: LABEL="6Y080P0.07"
UUID="45ee8af8-c443-42d4-ae59-6f68e33932e8" TYPE="ext2"

/dev/sda8: LABEL="win_D" UUID="4131-BA32" TYPE="vfat"
/dev/sda9: LABEL="6Y080P0.09"
UUID="5a09faf0-6f8e-4c72-a23b-46fe963754ef" TYPE="swap"
/dev/sda10: LABEL="6Y080P0.10"
UUID="66c1d026-1e4c-4392-8aa0-e0d9f2cb4277" TYPE="ext2"


2.6.36-hvw
/dev/hda1: LABEL="6Y080P0.01"
UUID="1205def1-2141-4b3a-97d0-0b94ca1c4ff2" TYPE="ext2"
/dev/hda5: LABEL="6Y080P0.05"
UUID="dc767bc6-ebe4-4dfb-a8f1-739709598dc7" TYPE="ext2"
/dev/hda6: LABEL="6Y080P0.06"
UUID="a7cfe5f2-b136-4a73-ac8a-f3e2121102c8" TYPE="ext2"
/dev/hda7: LABEL="6Y080P0.07"
UUID="45ee8af8-c443-42d4-ae59-6f68e33932e8" TYPE="ext2"

/dev/hda8: LABEL="win_D" UUID="4131-BA32" TYPE="vfat"
/dev/hda9: LABEL="6Y080P0.09"
UUID="5a09faf0-6f8e-4c72-a23b-46fe963754ef" TYPE="swap"
/dev/hda10: LABEL="6Y080P0.10"
UUID="66c1d026-1e4c-4392-8aa0-e0d9f2cb4277" TYPE="ext2"


Is that right?

Right


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 4CDEB0E5.5090508@care2.com">http://lists.debian.org/4CDEB0E5.5090508@care2.com