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

[Matthias Saou]

Shahms King wrote :

> It sounds like your problem is *nearly* identical to mine on the Shuttle
> SN95G5, except you can actually get the installer to boot:
> 
> https://bugzilla.redhat.com/beta/show_bug.cgi?id=135302
> 
> 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.

OK... bugzilla.redhat.com was down when I was struggling with all this a
few days ago, so I hadn't found all that info since google doesn't seem to
index all of it. Nor does it seem to have indexed the OSDL bug for that
matter.

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

Nope, Maxtor DiamondMax 10 (IIRC, the "10" I'm sure of) 200GB.

> The kernel bugzilla entry has a small workaround (that has been included
> in 2.6.10) that fixes the problem for me. [...]

Thanks for the pointer and tip. Unfortunately, downloading a kernel source
rpm simply wasn't an option, and I only had the install DVD (which doesn't
contain the .src.rpms anymore), so I would have been stuck anyway without a
single kernel to recompile.

What _really_ puzzles me is that the FC3 install works fine for me. Booting
the DVD in rescue mode too. But no installed system is able to see the SATA
drive again...

Thanks for all the pointers! Now I just need to figure out how to explain
all this to a non-expert over the phone... *sigh*

Matthias

-- 
Clean custom Red Hat Linux rpm packages : http://freshrpms.net/
Fedora Core release 3 (Heidelberg) - Linux kernel 2.6.9-1.681_FC3.r300
Load : 0.41 0.23 0.34