Bug 441382 - Fedora does not start up
Summary: Fedora does not start up
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 8
Hardware: i686
OS: Linux
low
urgent
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-07 19:50 UTC by Angelo Borsotti
Modified: 2008-08-19 18:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-08-19 18:43:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Angelo Borsotti 2008-04-07 19:50:40 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. switch on the computer
2. wait
3.
  
Actual results:

Grub bootstraps Fedora. A console window appears, in which the notification
of the starting of some components appears.
After that, the following is displayed:

SIOCSIFFLAGS: operations not supported
./ifup-wireless line 60:
  1945 Segmentation fault

Then the computer enters a state in which NOTHING can be done, except
power it off. There is no way to terminate the startup sequence and
bring up Fedora. P.S. Ubuntu boots successfully.

Expected results:


Additional info:

Comment 1 Jeremy Katz 2008-04-08 03:42:03 UTC
Are the keyboard LEDs flashing at this point?

Comment 2 John W. Linville 2008-04-17 15:09:27 UTC
What kernel are you using?  What is your wireless hardware?

Comment 3 Angelo Borsotti 2008-04-17 22:41:53 UTC
The keyboard LEDs are not flashing.
The kernel is the one of Fedora 8.
The wireless hardware is a PCI Atgheros board, and it works properly with Ubuntu.

Comment 4 John W. Linville 2008-04-18 12:22:31 UTC
Could you be a bit more specific about which kernel you are using?  There are 
dozens of Fedora 8 kernels.  Please post the output of 'uname -r'...thanks!

Comment 5 John W. Linville 2008-08-19 18:43:49 UTC
Closed due to lack of response...


Note You need to log in before you can comment on or make changes to this bug.