On Sat, 2011-07-16 at 11:42 +0200, Stan Hoeppner wrote:
> On 7/16/2011 3:52 AM, Tomas Kral wrote:
> 
> > linux-image-2.6.32-5-686  2.6.32-35
> > 
> > $ su -c'mount /dev/fd0 /media/floppy0' # or
> > $ mount /floppy
> 
> > [ 8744.146621] FAT: utf8 is not a recommended IO charset for FAT
> > filesystems, filesystem will be case sensitive!
> > 
> > But no floppy is really mounted
> 
> > as it should as per fstab
> > $ cat /etc/fstab | grep floppy
> > /dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0
> > 
> > Is there a floppy support in 2.6.32-5-686 at all?
> > In /boot/config-2.6.32-5-686
> > There is no floppy module set
> > CONFIG_BLK_DEV_IDEFLOPPY=m
> 
> Is this a standard floppy interface drive or an IDE floppy?
> 
> > Also noticed kernel boots with SCSI devices
> > /dev/sda.. /dev/sr..
> > But my hardware is IDE/ATAPI based.
> 
> Read about libata:  https://ata.wiki.kernel.org/index.php/Libata_FAQ
> 
> > How do I enable IDE on Squeeze?
> > Many thanks.
> 
> You don't.  It's already enabled.  Libata manages your IDE and SATA
> devices.  The old IDE drivers are deprecated.
> 
> -- 
> Stan
> 
> 

Just build my own custom kernel from linux-source-2.6.32 package
I enabled VIA module in the .config, since VIA is my chipset
And there comes up E-IDE at the boot up.

tcat@lynx:/usr/src/linux$
diff /boot/config-2.6.32-5-686 /boot/config-2.6.32-10.00.Custom

4c4
< # Sat Jun 11 19:11:36 2011 
---
> # Mon Jul 18 07:09:10 2011
1436a1437
> CONFIG_IDE_TIMINGS=y
1494c1495
< # CONFIG_BLK_DEV_VIA82CXXX is not set
---
> CONFIG_BLK_DEV_VIA82CXXX=m

It took a while to compile, about 8 hours.
Not sure what is better for me, end/user/wise, SCSI or E-IDE?
Devices in both kernels report themselves as UDMA-xxx (VIA vt82c686b),

I notice a slight performance gain in E-IDE one flavour.

-- 
Tomas Kral <thomas.k...@email.cz>


--
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/1311017807.2803.21.camel@lynx.localhost.localdomain

Reply via email to