hdparm.conf

John Nilsson john at milsson.nu
Fri Jul 29 05:17:45 UTC 2005


On fre, 2005-07-29 at 07:37 +0800, Wenzhuo Zhang wrote:
> Two possible reasons:
> 
> 1. The kernel does not support your chipset well.

Same kernel and same driver as I've had before...

> 2. The hdparm init script gets run very early in the sysinit stage, and the ide
> drivers haven't been loaded yet; i.e. "Setting disc parameters..." occurs
> before "Loading modules...". This problem can be easily resolved by updating
> the initrd image to load the required ide drivers first.

Sounds more likley

> $ sudo su -
> # cp -p /etc/mkinitrd/modules /etc/mkinitrd/modules.orig
> # vi /etc/mkinitrd/modules

Good habits die hard? -p seems unnecesary in that line ;-)

> and add the following lines to /etc/mkinitrd/modules:
> 
> piix
> ide-core
> ide-cd
> ide-disk
> ide-generic

Does ide-generic actually add some value? I was thinking that it's a
fallback if via82cxx (my chipset) isn't availible...

> 
> Depending on your motherboard chipset, you may have to replace piix with
> something relevant.
> 
> Then, regenerate the initrd image:
> 
>   # cp -p /boot/initrd.img-2.6.10-5-686 /boot/initrd.img-2.6.10-5-686.orig
>   # mkinitrd -o /boot/initrd.img-2.6.10-5-686 2.6.10-5-686

So thats how you do it, my current initrd has got drivers for anything
under the sun, quite annoying actually. No "dpkg-reconfigure"  or other
sillyness? I've got the impression that debian provides wrappers for
anything you might want to do ;-)

> Hope it helps,

Very much so. Thank you.

/John





More information about the ubuntu-users mailing list