[gutsy][regression] xorg won't boot if bcm43xx module loaded

Bug #153272 reported by jvargas
6
Affects Status Importance Assigned to Milestone
bcm43xx-fwcutter (Baltix)
Invalid
Undecided
Unassigned
bcm43xx-fwcutter (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: bcm43xx-fwcutter

When the bcm43xx module is loaded (bcm43xx-fwcutter installed + firmware downloaded), the X server (and gdm) won't boot. In fact, it would appear to kernel-panic.

If bcm43xx is not loaded, X will boot and function properly.

For the record, it actually works under Feisty.

Some PC details (from http://www.bab72.com/it/averatec/):

Technical Specifications (From the side of the box):
Model: 3200 Series
Part Number: AV3220H1-01
Processor: Mobile AMD Athlon XP-M 2000+
Display: 12.1" XGA Color TFT (1024x768)
Memory: 256MB DDR333
Hard Drive: 40GB
Optical Drive: Combo DVD+CD-RW
Comm.: Integrated 54Mbps 802.11g WLAN
Integrated 10/100 Network
Integrated 56K Data/Fax Modem
Battery: High Capacity Smart Lithium Ion

Components
Processor: 1.526GHz Athlon XP-M 2000+
Memory: 256MB DDR333
Hard Drive: Model IC25N040ATMR04-0
Ethernet: 10/100 Rhine-II (Via VT6102)
Wireless: Broadcom BCM94306
Modem: Via Tech, Intel 537 (AC97)
USB: USB 2.0 (3 separate controllers)
Graphics: S3 UniChrome chipset
Mouse: Touch pad supports:
Single tap (Left Button)
Double tap (Left Button)
Long Dragging
Hor/Ver Scrolling
Sound: Via VT82xx AC97 Audio Controller

Revision history for this message
johonbravo (jonathan-enns) wrote :

I am getting the exact same problem with Gutsy.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10?

Changed in bcm43xx-fwcutter:
status: New → Incomplete
Revision history for this message
Javier Jardón (jjardon) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in bcm43xx-fwcutter:
status: Incomplete → Invalid
Changed in bcm43xx-fwcutter (Baltix):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.