Fedor 12 wont load
 

I have a fresh install of Fedora 12 (An upgrade from fedora 10) and it freezes during the initial boot. I have a toshiba laptop and one of the errors I get is"

Fatal error inserting Toshiba.ACPI

"Make sure the Kernel has enabled the Toshiba option in the ACPI section"

Fatal Error, could not open:

/proc/acpi/Tohiba/keys

Also there is problem initialising the wireless modem during the first boot. This appears to be a driver problem but unfortunately I dont know how to disable the wireless modem during the first boot phase after installation of F12

These errors occur during the initial boot of my system and the computer never gets to the log in screen.

I would appreciate some help in fixing these problem.

When you get GRUB, press any other key except enter.

it will show you some lines in the Linux entry.

Move to the line which says something like 'vmlinuz' and press a.

type this -

press enter and then b. keep your fingers crossed.

You may want to check the BIOS settings for ACPI, to be sure it is all set to enabled, or if that does not work, try to set ACPI as disabled. Can the ACPI issue be related to a motherboard chip set driver missing?

Also keep in mind that Fedora's target user IS the person who already KNOWS how to fix things like this or the one who WANTS TO LEARN how to fix things like this. Fedora is NOT a "just works" distro.

That description would more better fit for Arch Linux. Fedora works very well man. I started off with Fedora when I was n00b. All the knowledge I have came from using Fedora. :)

I have resolved this problem by reloading Fedora 12, with both the Toshiba Laptop LAN Card, and the Wireless LAN disabled. Once the operating system was installed and working I enabled both Wireless LAN and LAN Cards. That fixed the problem and Fedora 12 is working well now.

Thanks to everyone who helped with this problem.

true but i started off with fedora 4 . and for the most part it has gotten a bit better . and i had only one minor issue with fedora 11 ( no sound ) it was fixed after a kernel bug was fixed

but for a lot of python applications i needed to point them to python2.5 installed in it's own directory .