[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Behavior differences between anaconda and "real" boot? (sata_nv problem)

It sounds like your problem is *nearly* identical to mine on the Shuttle
SN95G5, except you can actually get the installer to boot:


There is also another SATA-related installer bug that might be related.
One of the comments in #135302 points to an OSDL kernel bugzilla entry
with more information.

You wouldn't happen to be using a Seagate SATA drive would you?

The kernel bugzilla entry has a small workaround (that has been included
in 2.6.10) that fixes the problem for me.  I ended up having to do a
two-drive monte from a spare PATA drive to get it installed:
     1. Install on PATA hard-drive
     2. Compile src.rpm with patched sata_nv.c
     3. Create a boot disk (this *should* have been step 3, but wasn't)
     4. Reboot with new kernel
     5. Migrate data from PATA hard-drive (LVM2 makes this much easier)
     6. Run grub-install on the SATA hard-drive and hope it gets
        everything correct.
     7. Remove the old hard-drive.
     8. Don't update to anything less than a 2.6.10 kernel.

Note that you might want to reboot between step 5 and 6 to make sure the
data migrated correctly as well as between 6 and 7.  I know I had to do
some extra work to get grub-install working correctly (this was why
making the boot disk should have been step 3).

Since you don't have any problem getting it installed, it doesn't sound
like you'll have to go through all of those machinations, but I hope
this helps.

Shahms E. King <shahms shahms com>
Multnomah ESD

Public Key:
1612 054B CE92 8770 F1EA  AB1B FEAB 3636 45B2 D75B

Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]