On 04/10/2012 01:37 PM, Michael Hennebry wrote:
On Mon, 9 Apr 2012, Adam Williamson wrote:
> On Mon, 2012-04-09 at 21:14 -0500, Michael Hennebry wrote:
>> On Mon, 9 Apr 2012, Adam Williamson wrote:
>> > I'm pretty sure there must be a less strange and rarely-used way of
>> > doing it that would be usable in your situation...
>>
>> If you know what it is, I'm all eyes.
>> I started by burning a minimal F16 install CD.
>> It didn't work.
>> So far anything involving F16 or F17 has crashed my system.
>
> If it's that bad, then I'm not at all sure F16 or F17 would work if you
> somehow bypassed the regular installation method...
I've been told that a kernel bug broke my motherboard for the F16 install.
An install mechanism that uses a recent kernel should to the trick.
Preupdate might be one, but I need a disposable place from which to start.
If this is the kernel bug you are referring to, perhaps there is a
workaround you could use to get your minimal CD running in order to do
an install.
https://bugzilla.redhat.com/show_bug.cgi?id=730007
That issue appears to be related to the following ACPI patch.
http://marc.info/?l=linux-acpi&m=133002974918284&w=2
The description of that patch suggests that passing any one of these
kernel parameters will prevent the problem.
acpi=off
processor.nocst=1
maxcpus=1
If one of those works, you should then be able to install F16, boot it
the same way, and upgrade the kernel to one which contains the patch.
-Mike