Comment 7 for bug 160718

Hello Leann,

First and foremost, thanks for your help and interest. Since the last time I've written I've kept on upgrading here and there. Following the instructions indicated in the link you pointed out, I herein summarize all the relevant info, especially regarding the wireless (which I believe to be the partly the source of our noapic problem) and therefafter proceed to attach it as recommended.

uname -a > uname-a.log :
Linux alekubuntu 2.6.24-5-generic #1 SMP Thu Jan 24 19:29:14 UTC 2008 x86_64 GNU/Linux

cat /proc/version_signature > version.log :
Ubuntu 2.6.24-5.8-generic

sudo lspci -vvnn > lspci-vvnn.log (wireless card section):

03:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11a/b/g [14e4:4312] (rev 01)
 Subsystem: Hewlett-Packard Company Unknown device [103c:1361]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 19
 Region 0: Memory at c4000000 (32-bit, non-prefetchable) [size=16K]
 Capabilities: [40] Power Management version 2
  Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=2 PME-
 Capabilities: [58] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
  Address: 00000000 Data: 0000
 Capabilities: [d0] Express Legacy Endpoint IRQ 0
  Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
  Device: Latency L0s <4us, L1 unlimited
  Device: AtnBtn- AtnInd- PwrInd-
  Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
  Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
  Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
  Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s, Port 0
  Link: Latency L0s <4us, L1 <64us
  Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
  Link: Speed 2.5Gb/s, Width x1

dmesg > dmesg.log :
[ 0.000000] Command line: root=UUID=84c70404-b16e-4f22-b824-38b775014fda ro

I would just like to point out tha I still needed to boot with the noapic option until I properly installed the b43 driver for my card following the indications at

http://linuxwireless.org/en/users/Drivers/b43#firmwareinstallation

Precisely for my card I used:
1. Firmware version 4.80.53.0 at http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2 since I believe I am using the 2.6.24(-rc) (or earlier - but not the compat package)
2. I untared it,
3. I downloaded the b43-fwcutter version for 2.6.24(-rc) (or earlier - but not the compat package) from http://bu3sch.de/b43/fwcutter/b43-fwcutter-009.tar.bz2
4. I untared it and installed it (make & sudo make install)
5. I installed the previously untared firmware by cding to the /broadcom-wl-4.80.53.0/kmod directoring and typing the following command
sudo b43-fwcutter -w /lib/firmware /wl_apsta_mimo.o

I still have a feeling that I get inconsistent boot success.. Whenever I upgrade anything and I after I reboot my computer it crashes at "Loading Hardware Drivers" I usually end up rebooting, editing the boot command by adding noapic noirqdebug and then reinstalling the wireless....

I'll try to find an unsuccesful boot example so that you may compare, but they hardly ever get logged properly.... (or I'm not looking where I should be looking).

In any case I am willing to try all possibilities.... I'm in the mood to be a guinea pig.

Thanks for your time