Activity log for bug #95892
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2007-03-25 13:10:24 | Mikko Ohtamaa | bug | added bug | ||
| 2007-03-25 15:40:17 | Ben Collins | linux-meta: status | Unconfirmed | Needs Info | |
| 2007-03-25 15:40:17 | Ben Collins | linux-meta: assignee | ben-collins | ||
| 2007-03-25 15:40:17 | Ben Collins | linux-meta: statusexplanation | You are missing a considerable amount of needed information. Please attach the output of these commands (do not paste into comment). Use the web interface: dmesg lspci -vv lspci -vvn | ||
| 2007-03-25 20:44:43 | Mikko Ohtamaa | bug | added attachment 'dmesg.txt' (dmesg) | ||
| 2007-03-25 20:45:00 | Mikko Ohtamaa | bug | added attachment 'lspci.vv.txt' (lscpi -vv output) | ||
| 2007-03-25 20:45:37 | Mikko Ohtamaa | bug | added attachment 'lspci.vvn.txt' (lspci -vvn output) | ||
| 2007-03-28 14:30:03 | Ben Collins | linux-source-2.6.20: status | Needs Info | Rejected | |
| 2007-03-28 14:30:03 | Ben Collins | linux-source-2.6.20: statusexplanation | You are missing a considerable amount of needed information. Please attach the output of these commands (do not paste into comment). Use the web interface: dmesg lspci -vv lspci -vvn | This looks more like a boot script issue. First, do you have linux-restricted-modules-generic installed (so that you have ipw3945d user space daemon), and also is the device configured correctly in /etc/network/interfaces? If the latter is not true, then I suggest commenting out the entry for it in /etc/network/interfaces so that the startup scripts do not attempt to start the device (and hence, wait for it to come up, which is the cause of the delay). Then just use NetworkManager to configure the interface. Either that, or configure it correctly in /etc/network/interfaces. | |
| 2009-05-18 11:40:20 | Herve Rousseau | linux-meta (Ubuntu): status | New | Invalid |
