On 12/08/2007 04:54 AM, Carlos E. R. wrote: > > > The Friday 2007-12-07 at 14:08 -0500, Felix Miata wrote: > > > On 2007/12/07 12:29 (GMT-0500) Carlos E. R. apparently typed: > > >> The Friday 2007-12-07 at 11:26 -0500, Felix Miata wrote: > > >>> other than the YaST installer? > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Ok, ok, but it was Yast who wrote that parameter. > > > kernel /boot/vmlinuz root=/dev/disk/by-label/H16A-22factory > showopts noapic noresume splash=0 3 vga=788 > > > # mount > > /dev/hda22 on / type ext3 (rw,noatime,acl) > > /dev/hda7 on /disks/hda/boot type ext2 (rw,noatime,acl) > > /dev/hda14 on /home type ext3 (rw,noatime,acl) > > /dev/hda17 on /pub type ext3 (rw,noatime,acl) > > /dev/hda18 on /srv type ext3 (rw,noatime,acl) > > /dev/hda19 on /usr/local type ext3 (rw,noatime,acl) > > /dev/hda20 on /usr/src type ext3 (rw,noatime,acl) > > That is indeed a surprise to me. I'm utterly surprised... I don't > understand. I'll have to try myself... I wonder if hwprobe=-modules.pata is passed to the installer, it includes the older module in the initrd and perhaps blacklists the libata one. Surely the initrd controls what module loads on boot to access the hard drives. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64
-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
