Wireless Not working on HP Mini 110

LazerPhreak · 02-06-2010, 10:56 PM

After exhausting all other resources, I am here to ask of all your assistance. Here's my dilemma, short and simple: I can see a list of wireless networks, but when I click connect, it spins for about a minute and shows me disconnected. Here's my details, maybe you can make better progress than me.

Version

Code:

Ubuntu 9.10 UNR

Kernel

Code:

2.6.31-19-generic

lshw -C network

Code:

  *-network
       description: Wireless interface
       physical id: 2
       logical name: wlan1
       serial: 0c:ee:e6:8b:b4:dd
       capabilities: ethernet physical wireless
       configuration: broadcast=yes driver=b43 driverversion=2.6.31-19-generic firmware=N/A link=no multicast=yes wireless=IEEE 802.11bg

lspci -nn -vv

Code:

01:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01)
	Subsystem: Hewlett-Packard Company Device [103c:1507]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at feafc000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: b43-pci-bridge
	Kernel modules: ssb

dmesg | grep b43

Code:

[    3.731171] b43-pci-bridge 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    3.731198] b43-pci-bridge 0000:01:00.0: setting latency timer to 64
[   18.268805] b43: disagrees about version of symbol ssb_device_is_enabled
[   18.268818] b43: Unknown symbol ssb_device_is_enabled
[   18.269935] b43: Unknown symbol ssb_pmu_set_ldo_paref
[   18.270454] b43: disagrees about version of symbol ssb_pcicore_dev_irqvecs_enable
[   18.270465] b43: Unknown symbol ssb_pcicore_dev_irqvecs_enable
[   18.271327] b43: disagrees about version of symbol ssb_bus_may_powerdown
[   18.271339] b43: Unknown symbol ssb_bus_may_powerdown
[   18.272131] b43: disagrees about version of symbol ssb_dma_free_consistent
[   18.272141] b43: Unknown symbol ssb_dma_free_consistent
[   18.273682] b43: disagrees about version of symbol ssb_bus_suspend
[   18.273693] b43: Unknown symbol ssb_bus_suspend
[   18.276263] b43: disagrees about version of symbol ssb_bus_unregister
[   18.276275] b43: Unknown symbol ssb_bus_unregister
[   18.278017] b43: disagrees about version of symbol ssb_bus_resume
[   18.278028] b43: Unknown symbol ssb_bus_resume
[   18.278405] b43: disagrees about version of symbol ssb_set_devtypedata
[   18.278415] b43: Unknown symbol ssb_set_devtypedata
[   18.279758] b43: disagrees about version of symbol ssb_device_disable
[   18.279769] b43: Unknown symbol ssb_device_disable
[   18.280189] b43: Unknown symbol ssb_pmu_set_ldo_voltage
[   18.281015] b43: disagrees about version of symbol ssb_dma_alloc_consistent
[   18.281025] b43: Unknown symbol ssb_dma_alloc_consistent
[   18.281632] b43: disagrees about version of symbol ssb_dma_set_mask
[   18.281642] b43: Unknown symbol ssb_dma_set_mask
[   18.283843] b43: disagrees about version of symbol ssb_device_enable
[   18.283856] b43: Unknown symbol ssb_device_enable
[   18.284742] b43: disagrees about version of symbol ssb_driver_unregister
[   18.284753] b43: Unknown symbol ssb_driver_unregister
[   18.285866] b43: disagrees about version of symbol __ssb_driver_register
[   18.285879] b43: Unknown symbol __ssb_driver_register
[   18.287599] b43: Unknown symbol ssb_bus_pcmciabus_register
[   18.287951] b43: disagrees about version of symbol ssb_bus_powerup
[   18.287960] b43: Unknown symbol ssb_bus_powerup
[   18.291971] b43: disagrees about version of symbol ssb_dma_translation
[   18.291982] b43: Unknown symbol ssb_dma_translation
[   18.299808] b43: disagrees about version of symbol ssb_device_is_enabled
[   18.299821] b43: Unknown symbol ssb_device_is_enabled
[   18.300890] b43: Unknown symbol ssb_pmu_set_ldo_paref
[   18.301462] b43: disagrees about version of symbol ssb_pcicore_dev_irqvecs_enable
[   18.301474] b43: Unknown symbol ssb_pcicore_dev_irqvecs_enable
[   18.302319] b43: disagrees about version of symbol ssb_bus_may_powerdown
[   18.302330] b43: Unknown symbol ssb_bus_may_powerdown
[   18.302999] b43: disagrees about version of symbol ssb_dma_free_consistent
[   18.303009] b43: Unknown symbol ssb_dma_free_consistent
[   18.304526] b43: disagrees about version of symbol ssb_bus_suspend
[   18.304538] b43: Unknown symbol ssb_bus_suspend
[   18.324653] b43: disagrees about version of symbol ssb_bus_unregister
[   18.324666] b43: Unknown symbol ssb_bus_unregister
[   18.326515] b43: disagrees about version of symbol ssb_bus_resume
[   18.326528] b43: Unknown symbol ssb_bus_resume
[   18.326899] b43: disagrees about version of symbol ssb_set_devtypedata
[   18.326909] b43: Unknown symbol ssb_set_devtypedata
[   18.328236] b43: disagrees about version of symbol ssb_device_disable
[   18.328247] b43: Unknown symbol ssb_device_disable
[   18.328608] b43: Unknown symbol ssb_pmu_set_ldo_voltage
[   18.329484] b43: disagrees about version of symbol ssb_dma_alloc_consistent
[   18.329497] b43: Unknown symbol ssb_dma_alloc_consistent
[   18.330104] b43: disagrees about version of symbol ssb_dma_set_mask
[   18.330115] b43: Unknown symbol ssb_dma_set_mask
[   18.332292] b43: disagrees about version of symbol ssb_device_enable
[   18.332303] b43: Unknown symbol ssb_device_enable
[   18.333217] b43: disagrees about version of symbol ssb_driver_unregister
[   18.333227] b43: Unknown symbol ssb_driver_unregister
[   18.334343] b43: disagrees about version of symbol __ssb_driver_register
[   18.334355] b43: Unknown symbol __ssb_driver_register
[   18.356265] b43: Unknown symbol ssb_bus_pcmciabus_register
[   18.356625] b43: disagrees about version of symbol ssb_bus_powerup
[   18.356634] b43: Unknown symbol ssb_bus_powerup
[   18.360622] b43: disagrees about version of symbol ssb_dma_translation
[   18.360633] b43: Unknown symbol ssb_dma_translation
[   18.404408] b43: disagrees about version of symbol ssb_device_is_enabled
[   18.404420] b43: Unknown symbol ssb_device_is_enabled
[   18.405580] b43: Unknown symbol ssb_pmu_set_ldo_paref
[   18.406088] b43: disagrees about version of symbol ssb_pcicore_dev_irqvecs_enable
[   18.406096] b43: Unknown symbol ssb_pcicore_dev_irqvecs_enable
[   18.406918] b43: disagrees about version of symbol ssb_bus_may_powerdown
[   18.406925] b43: Unknown symbol ssb_bus_may_powerdown
[   18.407599] b43: disagrees about version of symbol ssb_dma_free_consistent
[   18.407606] b43: Unknown symbol ssb_dma_free_consistent
[   18.409118] b43: disagrees about version of symbol ssb_bus_suspend
[   18.409126] b43: Unknown symbol ssb_bus_suspend
[   18.410088] b43: disagrees about version of symbol ssb_bus_unregister
[   18.410096] b43: Unknown symbol ssb_bus_unregister
[   18.411829] b43: disagrees about version of symbol ssb_bus_resume
[   18.411836] b43: Unknown symbol ssb_bus_resume
[   18.412194] b43: disagrees about version of symbol ssb_set_devtypedata
[   18.412203] b43: Unknown symbol ssb_set_devtypedata
[   18.413556] b43: disagrees about version of symbol ssb_device_disable
[   18.413568] b43: Unknown symbol ssb_device_disable
[   18.413928] b43: Unknown symbol ssb_pmu_set_ldo_voltage
[   18.414756] b43: disagrees about version of symbol ssb_dma_alloc_consistent
[   18.414766] b43: Unknown symbol ssb_dma_alloc_consistent
[   18.415367] b43: disagrees about version of symbol ssb_dma_set_mask
[   18.415377] b43: Unknown symbol ssb_dma_set_mask
[   18.417677] b43: disagrees about version of symbol ssb_device_enable
[   18.417689] b43: Unknown symbol ssb_device_enable
[   18.418545] b43: disagrees about version of symbol ssb_driver_unregister
[   18.418556] b43: Unknown symbol ssb_driver_unregister
[   18.419676] b43: disagrees about version of symbol __ssb_driver_register
[   18.419687] b43: Unknown symbol __ssb_driver_register
[   18.425906] b43: Unknown symbol ssb_bus_pcmciabus_register
[   18.426253] b43: disagrees about version of symbol ssb_bus_powerup
[   18.426260] b43: Unknown symbol ssb_bus_powerup
[   18.430200] b43: disagrees about version of symbol ssb_dma_translation
[   18.430211] b43: Unknown symbol ssb_dma_translation
[   18.508873] b43: disagrees about version of symbol ssb_device_is_enabled
[   18.508886] b43: Unknown symbol ssb_device_is_enabled
[   18.510058] b43: Unknown symbol ssb_pmu_set_ldo_paref
[   18.510593] b43: disagrees about version of symbol ssb_pcicore_dev_irqvecs_enable
[   18.510604] b43: Unknown symbol ssb_pcicore_dev_irqvecs_enable
[   18.511439] b43: disagrees about version of symbol ssb_bus_may_powerdown
[   18.511450] b43: Unknown symbol ssb_bus_may_powerdown
[   18.512145] b43: disagrees about version of symbol ssb_dma_free_consistent
[   18.512156] b43: Unknown symbol ssb_dma_free_consistent
[   18.513745] b43: disagrees about version of symbol ssb_bus_suspend
[   18.513757] b43: Unknown symbol ssb_bus_suspend
[   18.514757] b43: disagrees about version of symbol ssb_bus_unregister
[   18.514768] b43: Unknown symbol ssb_bus_unregister
[   18.516568] b43: disagrees about version of symbol ssb_bus_resume
[   18.516579] b43: Unknown symbol ssb_bus_resume
[   18.516970] b43: disagrees about version of symbol ssb_set_devtypedata
[   18.516979] b43: Unknown symbol ssb_set_devtypedata
[   18.518372] b43: disagrees about version of symbol ssb_device_disable
[   18.518386] b43: Unknown symbol ssb_device_disable
[   18.518754] b43: Unknown symbol ssb_pmu_set_ldo_voltage
[   18.519589] b43: disagrees about version of symbol ssb_dma_alloc_consistent
[   18.519600] b43: Unknown symbol ssb_dma_alloc_consistent
[   18.520203] b43: disagrees about version of symbol ssb_dma_set_mask
[   18.520214] b43: Unknown symbol ssb_dma_set_mask
[   18.522468] b43: disagrees about version of symbol ssb_device_enable
[   18.522480] b43: Unknown symbol ssb_device_enable
[   18.523332] b43: disagrees about version of symbol ssb_driver_unregister
[   18.523345] b43: Unknown symbol ssb_driver_unregister
[   18.524527] b43: disagrees about version of symbol __ssb_driver_register
[   18.524539] b43: Unknown symbol __ssb_driver_register
[   18.624741] b43: Unknown symbol ssb_bus_pcmciabus_register
[   18.625117] b43: disagrees about version of symbol ssb_bus_powerup
[   18.625125] b43: Unknown symbol ssb_bus_powerup
[   18.629095] b43: disagrees about version of symbol ssb_dma_translation
[   18.629102] b43: Unknown symbol ssb_dma_translation
[   21.652454] b43-pci-bridge 0000:01:00.0: PCI INT A disabled
[   25.209396] b43-pci-bridge 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   25.209430] b43-pci-bridge 0000:01:00.0: setting latency timer to 64
[   25.297396] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
[   25.462488] Registered led device: b43-phy0::tx
[   25.462547] Registered led device: b43-phy0::rx
[   25.462611] Registered led device: b43-phy0::radio
[   25.544176] b43 ssb0:0: firmware: requesting b43/ucode15.fw
[   25.604576] b43 ssb0:0: firmware: requesting b43/lp0initvals15.fw
[   25.614618] b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw
[   25.768175] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)

paulsm4 · 02-07-2010, 12:58 AM

Hi -

You've made an effort to include good information - thank you.

Unfortunately, it's still not enough to determine exactly what you're trying (there are several different routes you could be going), or exactly what's going wrong (driver level? 802.11 level? DHCP or DNS level? etc etc)

STRONG SUGGESTION:
Please look at this troubleshooting guide - I think it might help:

https://help.ubuntu.com/community/Wi...eShootingGuide

LazerPhreak · 02-07-2010, 01:11 AM

I believe it is a driver issue. It worked fine until I updated to 2.6.32-19 from 2.6.32-17. I just switched back to 17 though and the problem is still there. Any information you need feel free to ask. I'm lost.

Hangdog42 · 02-07-2010, 06:49 AM

Did you install firmware for the b43 driver? It doesn't work unless you do and Ubuntu can't distribute it directly, you'll probably need to use one of the unrestricted repositories.

That said, Broadcom's driver should work with that chipset. There is a bug at the moment, but if you read this link it isn't difficult to solve.

LazerPhreak · 02-07-2010, 01:01 PM

First, I would like to think your for your assistance and ask in advance your forgiveness because I know when this is all said and done it will be something simple. Here's where I am:

I downgraded back to kernel revision 17, and installed bcmwl-kernel-source. Using network manager, I see a list of networks and attempt to connect to mine. The icon spins for about a minute and says "Acquiring network address". Then it shows "Wireless network disconnected", and the list of wireless networks disappears So, what can I do to pinpoint where the problem lies?

paulsm4 · 02-07-2010, 02:29 PM

Hi -

With all due respect (and as you're already very aware), the problem can be in one (or more) of several different places. You just have to start at the "bottom" and work your way up.

1. This link honestly seems to be a good troubleshooting guide:

Ubuntu Wireless Troubleshooting Guide

2. You've already done a great deal of this work (at least through step 4, it looks like). I assume step 5 (iwconfig) does *not* work. If not, it might be useful to cut/paste specific error messages you're getting.

3. But you also said:
a) it *used* to work (before you upgraded the kernel)
b) you have the kernel source (good!)
... and ...
c) you're getting many "dmesg" errors like this:

Quote:

[ 18.268805] b43: disagrees about version of symbol ssb_device_is_enabled
[ 18.268818] b43: Unknown symbol ssb_device_is_enabled
[ 18.269935] b43: Unknown symbol ssb_pmu_set_ldo_paref
[ 18.270454] b43: disagrees about version of symbol ssb_pcicore_dev_irqvecs_enable

4. Fair enough.
So definitely try:
a) Uninstalling your current bt43 driver
b) Updating your kernel headers and/or kernel source (make sure they're in synch with your running kernel)
c) Updating your bt43 driver source (probably OK as-is: but why not double-check)
d) rebuilding the driver (latest/greatest bt43 source with latest/greatest kernel source)
<= *Definitely* cut/paste any errors you encounter!
e) try installing the new driver
<= Again, cut/paste any errors you encounter!
f) See if you can get past step 4) in the Troubleshooting Guide

'Hope that helps .. PSM

LazerPhreak · 02-07-2010, 02:53 PM

OK So I made a little progress:

I discovered part of the problem was excessive blacklisting. I got rid of everything and did a fresh driver install and that got rid of the dmesg errors. I tried to connect via command line and this is what happened:

Code:

:~$ sudo ifconfig wlan1 down

[sudo] password for kasha: 

:~$ sudo dhclient -r wlan1

Internet Systems Consortium DHCP Client V3.1.2

Copyright 2004-2008 Internet Systems Consortium.

All rights reserved.

For info, please visit http://www.isc.org/sw/dhcp/



Listening on LPF/wlan1/0c:ee:e6:8b:b4:dd

Sending on   LPF/wlan1/0c:ee:e6:8b:b4:dd

Sending on   Socket/fallback

:~$ sudo ifconfig wlan1 up

:~$ sudo iwconfig wlan1 "dd-wrt"

iwconfig: unknown command "dd-wrt"

:~$ sudo iwconfig wlan1 essid "dd-wrt"

:~$ sudo iwconfig wlan1 mode Managed

:~$ sudo dhclient wlan1

Internet Systems Consortium DHCP Client V3.1.2

Copyright 2004-2008 Internet Systems Consortium.

All rights reserved.

For info, please visit http://www.isc.org/sw/dhcp/



Listening on LPF/wlan1/0c:ee:e6:8b:b4:dd

Sending on   LPF/wlan1/0c:ee:e6:8b:b4:dd

Sending on   Socket/fallback

DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 4

DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 8

DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 12

DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 21

DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 16

No DHCPOFFERS received.

No working leases in persistent database - sleeping.

:~$ iwlist scan

lo        Interface doesn't support scanning.



eth0      Interface doesn't support scanning.



wlan1     No scan results



:~$ ifconfig

eth0      Link encap:Ethernet  HWaddr 18:a9:05:8c:ce:5f  

          inet addr:192.168.1.127  Bcast:192.168.1.255  Mask:255.255.255.0

          inet6 addr: fe80::1aa9:5ff:fe8c:ce5f/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:2320 errors:0 dropped:0 overruns:0 frame:0

          TX packets:2275 errors:0 dropped:0 overruns:0 carrier:1

          collisions:0 txqueuelen:1000 

          RX bytes:1734542 (1.7 MB)  TX bytes:341735 (341.7 KB)

          Interrupt:26 



lo        Link encap:Local Loopback  

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0 

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)



wlan1     Link encap:Ethernet  HWaddr 0c:ee:e6:8b:b4:dd  

          inet6 addr: fe80::eee:e6ff:fe8b:b4dd/64 Scope:Link

          UP BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:2 errors:0 dropped:0 overruns:0 frame:0

          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000 

          RX bytes:120 (120.0 B)  TX bytes:1972 (1.9 KB)



wlan1:avahi Link encap:Ethernet  HWaddr 0c:ee:e6:8b:b4:dd  

          inet addr:169.254.12.125  Bcast:169.254.255.255  Mask:255.255.0.0

          UP BROADCAST MULTICAST  MTU:1500  Metric:1

Other computer (including my server) can connect via dhcp (wirelessly and wired), no problem.

Any ideas?

nimnull22 · 02-07-2010, 03:05 PM

configuration: broadcast=yes driver=b43 driverversion=2.6.31-19-generic firmware=N/A link=no multicast=yes wireless=IEEE 802.11bg

One question - B43 needs firmware - but from the output: firmware=N/A

Please check if you have it and if this driver needs it.

LazerPhreak · 02-07-2010, 03:39 PM

OK So I attempted to install firmware and apparently I'm not doing it right. How should I go about this?

nimnull22 · 02-07-2010, 04:25 PM

You need to download it and put to appropriate place where driver will read it.
But are you sure you need it.
Please do:
modprobe -r b43
modprobe b43
dmesg | tail -n 30.

Please post outputs

Thanks.

LazerPhreak · 02-07-2010, 04:47 PM

So, I managed to get it working with a combination of tutorials. First I updated to kernel 2.6.32. Then I followed this tutorial http://ubuntuforums.org/showthread.php?t=1266620
However, The problem lay in this command:

Code:

 echo "options b43 pio=1" | sudo tee -a "/etc/modprobe.d/b43-thingy.conf"

After a reboot, I ran a dmesg | grep b43 to see what errors there were now and noticed several unrecognized pio errors. So I removed options b43 pio=1 from b43-thingy.conf and rebooted. Then i ran modprobe b43 and wallah! problem solved. Thank you all for your help! If you need any more information that I did not post in order to help others feel free to ask!