On 2004 12 18 (Saturday) 16:14, Lotsa Cabo wrote:
> Okay, where do I start? I've tried searching, but I'm not entirely sure
> what I'm searching for. I've found a ton of pages that give switches to
> disable certain items, but nothing really explains what the switches
> are. The pages that do explain the switches do not explain what
> ramifications they will have.
>
> Here's the problem...
>
> I tried installing FC3 and had to disable ACPI. Then, I could not get
> my wireless NIC functioning. I found a ton of threads discussing ACPI
> and PCMCIA NICs with DriverLoader, so I decided to ditch it and go back
> to FC2. I installed FC2 with the 2.6.5-1.358 kernel and it works fine
> (that's what I'm on now). My first update brought with it kernel
> 2.6.9-1.6_FC2 which I cannot boot at all.
>
> My questions are simple (I think):
>
> 1. What is the best way to tell what is causing the boot to fail?
Remove any quiet and rhgb cheatcodes from /etc/grub.conf and
look at the output :)
> 2. What the heck is so special with with kernel 2.6.5-1.358 that it is
> the only one I can boot?
Maybe the new kernels don't have 'noacpi' option? Look at grub.conf.
You can edit grub's command with 'e' ('p' to enter password if any)
at boottime without having to edit grub.conf also. You might want to
fill a BUG report at bugzilla.redhat.com when you have more specific
data - what is your hardware (CPU/MB/NICs). Look at /var/log/messages
for hints too...
--
Regards,
Doncho N. Gunchev Registered Linux User #291323 at counter.li.org
GPG-Key-ID: 1024D/DA454F79 http://pgp.mit.edu
Key fingerprint = 684F 688B C508 C609 0371 5E0F A089 CB15 DA45 4F79
