Re: Libata in Debian GNU/Linux Lenny

[Stan Hoeppner <stan@hardwarefreak.com>]

Daniel Bareiro put forth on 10/10/2009 7:54 PM:
> Hi all!
> 
> I'm using Debian GNU/Linux Lenny with linux-image-2.6.26-2-amd64 stock
> kernel installed from a binary image from Debian repositories.
> 
> In this case the disks are seen like hdX but using kernel 2.6.31.2
> compiled by myself with the sources of kernel.org the disks are seen
> like sdX. I consider that this difference is because with 2.6.31.2
> libata is being used whereas in 2.6.26 it is disabled. Is it possible?

If this helps your troubleshooting any...

Lenny 5.0, self compiled kernel, source tarball from kernel.org, no
module support, stripped to the bone, Intel PIIX IDE and e100: Intel(R)
PRO/100 compiled into the kernel, again, module support disabled in
menuconfig.  Built 7 days ago.

greer:/# uname -a
Linux greer 2.6.31.1 #1 SMP Sat Oct 3 10:43:14 CDT 2009 i686 GNU/Linux

greer:/# dmesg
..
Uniform Multi-Platform E-IDE driver
piix 0000:00:07.1: IDE controller (0x8086:0x7111 rev 0x01)
piix 0000:00:07.1: not 100% native mode: will probe irqs later
ide: disallowing DMA for hda
ide: disallowing DMA for hdb
    ide0: BM-DMA at 0xf000-0xf007
    ide1: BM-DMA at 0xf008-0xf00f
Probing IDE interface ide0...
hda: ST340823A, ATA DISK drive
hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
Probing IDE interface ide1...
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
ide-gd driver 1.18
hda: max request size: 128KiB
hda: 78165360 sectors (40020 MB) w/512KiB Cache, CHS=65535/16/63
hda: cache flushes not supported
 hda: hda1 hda2 hda3

I disable DMA at boot as the Seagate disk is flaky.  I'm posting merely
to show IDE device naming on a hand built 2.6.31.1 kernel with a built
in PIIX driver.

Are your disks IDE or SATA?  Sure it's possible if you're using disk
driver modules.  Compiling the exact driver module you want used into
the kernel eliminates all doubt.  Thus, one of the reasons I compile
kernels the way I do.  Eliminates the guesswork.

--
Stan