How to load sata_nv before pata_amd on Kubuntu Hardy 8.04

Tom H tomh0665 at gmail.com
Mon Nov 8 03:28:55 GMT 2010


On Sun, Nov 7, 2010 at 2:33 PM, Nigel Henry <cave.dnb2m97pp at aliceadsl.fr> wrote:
> On Sunday 07 November 2010 13:45, Jonas Norlander wrote:
>> 2010/11/4 Nigel Henry <cave.dnb2m97pp at aliceadsl.fr>:
>> > I added a pata harddrive to my machine that already has 2 sata
>> > harddrives.
>> >
>> > Hardy is loading pata_amd before sata_nv. Is there a way to load sata_nv
>> > first?
>> >
>> > I have a bunch of distros on this machine, with many FAT32 data
>> > partitions shared, so the drive order is important.
>> >
>> > Dapper is loading them in the correct order: 1, sda; 2, sdb; 3, hda (no
>> > libata).
>> >
>> > Intrepid is loading them in the correct order: 1, sda; 2, sdb; 3, sdc
>> > (the pata drive).
>> >
>> > All the Fedora installs are as Intrepid above.
>> >
>> > Had a problem with drive ordering with Archlinux, but appending the
>> > kernel line in grub with -earlymodules --sata_nv resolved that problem.
>> > Archlinux uses mkinitcpio for the initramfs so that wouldn't work for the
>> > Hardy problem, but is there something similar I could append the kernel
>> > line with in Hardy, that would load the sata_nv module before the pata
>> > one?
>>
>> I'm not sure I understand why you want the devices in specific order?
>> It's not very often you need to access the device nodes direct, rather
>> through the mount point. Do you use LABEL or UUID  to mount the
>> partitions?
>
> Mainly for consistency across the 10 distros that are installed on this
> machine. I don't use Label or UUID's to mount them, but just point to the
> device nodes for the partitions I want to mount.

You can use labels in one distro, uuids in second, hardware ids in a
third, and device nodes in fourth without any problems.



More information about the kubuntu-users mailing list