| 2006-04-01 00:25:17 |
Kaglan |
bug |
|
|
added bug |
| 2006-04-01 13:31:39 |
Kaglan |
None: severity |
Normal |
Major |
|
| 2006-04-01 13:31:39 |
Kaglan |
None: statusexplanation |
|
Raised severity to major, since several minute hangs in the boot process are major problems. |
|
| 2006-04-01 13:34:34 |
Kaglan |
description |
[Dapper, update/dist-upgraded to repositories as of March 31st 2006]
Earlier version of Dapper (a week or so) did not exhibit this problem. Had to reinstall flight five from CD. Installer correctly recognized and configured wireless card, and pulled packages (I think) from the Internet.
Also tried installing Breezy, and dist-upgrading to dapper. Following problem appears after both upgrade-to-dapper approaches:
During boot, system hangs at "Loading hardware drivers." Eventually times out and continues to hang at "Configuring the network...". System completes booting, but the wireless card seems not to be recognized. (it appears in lshw, bound to the hostap driver, but is labeled disabled).
Errors during safe mode boot talk about wifi0: failing at everything it tries to do. Wpa supplicant (scrolls by quickly in the boot process) returns an exit code 1.
Computer: Toshiba Satellite 2435.
Kernel 2.6.15-19-686
Wireless Card: (returned by cardctl ident)
Toshiba, version 01.01, manfid 0x0156, 0x0002, function 6
|
[Dapper, update/dist-upgraded to repositories as of March 31st 2006]
This problem appeared only within the last couple weeks of upgrades. I was able to reproduce it with a clean install of flight six.
During boot, system hangs at "Loading hardware drivers." Eventually the error times out and boot continues, only to hang at "Configuring the network...". After a few minutes, the system completes booting, but the wireless card seems not to be recognized. (it appears in lshw, bound to the hostap driver, but is labeled disabled).
Errors during safe mode boot talk about wifi0: failing at everything it tries to do. Wpa supplicant (scrolls by quickly in the boot process) returns an exit code 1.
Computer: Toshiba Satellite 2435.
Kernel 2.6.15-19-686
Wireless Card: (returned by cardctl ident)
Toshiba, version 01.01, manfid 0x0156, 0x0002, function 6
|
|
| 2006-04-01 17:37:49 |
Kaglan |
bug |
|
|
added attachment 'messages.txt' (/var/log/messages) |
| 2006-04-04 21:45:27 |
Alexandre Otto Strube |
None: status |
Unconfirmed |
Confirmed |
|
| 2006-04-04 21:45:27 |
Alexandre Otto Strube |
None: statusexplanation |
Raised severity to major, since several minute hangs in the boot process are major problems. |
several confirmations for this bug, changing status |
|
| 2006-04-22 08:44:43 |
Sitsofe Wheeler |
title |
[Dapper] Boot hangs at loading hardware drivers, wireless fails |
[hostap] [Dapper] Boot hangs at loading hardware drivers, wireless fails |
|
| 2006-04-23 15:46:03 |
x |
bug |
|
|
added attachment 'lsmod' (Output from lsmod) |
| 2006-04-23 15:46:30 |
x |
bug |
|
|
added attachment 'dmesg' (dmesg) |
| 2006-04-23 18:22:28 |
x |
title |
[hostap] [Dapper] Boot hangs at loading hardware drivers, wireless fails |
[Dapper] Boot hangs at "Loading Hardware Drivers", Internetconnection fails |
|
| 2006-05-01 13:02:44 |
x |
bug |
|
|
added attachment 'udev' (/var/log/udev after boot) |
| 2006-05-02 12:10:28 |
joenix |
bug |
|
|
added attachment 'udev' (/var/log/udev after boot (joenix)) |
| 2006-05-02 14:34:26 |
Scott James Remnant (Canonical) |
None: assignee |
|
keybuk |
|
| 2006-05-02 14:34:26 |
Scott James Remnant (Canonical) |
None: statusexplanation |
several confirmations for this bug, changing status |
|
|
| 2006-05-02 14:35:11 |
Scott James Remnant (Canonical) |
title |
[Dapper] Boot hangs at "Loading Hardware Drivers", Internetconnection fails |
dapper 180s boot-stall ... probable hdparm on IDE CD drives |
|
| 2006-05-02 14:36:06 |
Scott James Remnant (Canonical) |
description |
[Dapper, update/dist-upgraded to repositories as of March 31st 2006]
This problem appeared only within the last couple weeks of upgrades. I was able to reproduce it with a clean install of flight six.
During boot, system hangs at "Loading hardware drivers." Eventually the error times out and boot continues, only to hang at "Configuring the network...". After a few minutes, the system completes booting, but the wireless card seems not to be recognized. (it appears in lshw, bound to the hostap driver, but is labeled disabled).
Errors during safe mode boot talk about wifi0: failing at everything it tries to do. Wpa supplicant (scrolls by quickly in the boot process) returns an exit code 1.
Computer: Toshiba Satellite 2435.
Kernel 2.6.15-19-686
Wireless Card: (returned by cardctl ident)
Toshiba, version 01.01, manfid 0x0156, 0x0002, function 6
|
(Note: original reporter's problem went away and was probable wireless rename bug that's been fixed in dapper -- this bug now refers to Thilo Six's problem)
$ uname --all
Linux ubuntu2 2.6.15-20-386
# cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 6
model name : AMD Athlon(tm) XP 2000+
Motherboard is a ASROCK K7VT 4A Pro (Via VT8237 chipset).
Nic is a onboard:
product: VT6102 [Rhine-II]
vendor: VIA Technologies, Inc.
|
|
| 2006-05-02 19:11:18 |
x |
bug |
|
|
added attachment 'udev' (/var/log/udev from a "broken" boot - with hdparm) |
| 2006-05-02 19:11:45 |
x |
bug |
|
|
added attachment 'hdparm.conf' (/etc/hdparm.conf) |
| 2006-05-02 19:22:54 |
x |
bug |
|
|
added attachment 'udev' (/var/log/udev without hdparm) |
| 2006-05-02 19:26:09 |
x |
bug |
|
|
added attachment 'hdparm.conf' (/etc/hdparm.conf) |
| 2006-05-03 18:45:43 |
Scott James Remnant (Canonical) |
udev: status |
Confirmed |
Rejected |
|
| 2006-05-03 18:45:43 |
Scott James Remnant (Canonical) |
udev: statusexplanation |
|
Ok, marking this as Rejected as you added those hdparm lines yourself.
If the documentation that told you to do that was from an Ubuntu source, please ask the author to remove it; on Ubuntu dma is enabled automatically if it's possible -- forcing it to be enabled can cause problems.
The reason you were having problems is due to hdparm being unable to enable dma itself, which isn't needed because it was already enabled anyway. |
|
