Broadcom 4312 problems following upgrade

Scrivener · 2009-08-09 04:13:32

I think I fixed it. I had to blacklist ssb also. My modules line now looks like this:

MODULES=(lib80211_crypt_tkip wl !b43 !ssb)

Edit: Nope. It worked once, but stopped after a reboot. Also, I used the netcfg instructions here: http://wiki.archlinux.org/index.php/Netcfg to set up a network profile and that didn't help. ArchAssistant says it's connected but I can't go anywhere.

Last edited by Scrivener (2009-08-09 04:28:26)

jdiez · 2009-08-09 04:36:46

Can you post ifconfig? Maybe your connection is trying to route through ethernet.

quick fix: ifconfig eth0 down && netcfg -r <your_network_profile>

Scrivener · 2009-08-09 16:10:04

I really think it's an issue with the new kernel. Everything worked fine before that update.

Here's the ifconfig result:

eth0      Link encap:Ethernet  HWaddr 00:21:CC:36:D7:B3  
          UP BROADCAST MULTICAST  MTU:1500  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:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:27 Base address:0x8000 

eth1      Link encap:Ethernet  HWaddr 00:24:2B:E8:D2:1D  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  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:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:18 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          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)

I took down eth0 and ran netconfig -r home as directed. (My wireless settings are in the "home" profile in network.d.) It said it came back up, but I had no network connection.

jdiez · 2009-08-09 16:37:14

Okay, which is your wireless adapter?
Can you post those?:
ping <router>
ping google.com

Scrivener · 2009-08-09 23:12:56

eth1 is my wireless. Pings to my router at 192.168.0.1 give me a "Network is unreachable" error.

Edit: I downgraded to the 30-2 kernel and rebooted. It worked once. After another reboot (with no settings changes) it refused to start again. I don't know what could cause that or even where to report it as a bug.

Last edited by Scrivener (2009-08-09 23:30:39)

jdiez · 2009-08-09 23:26:31

Yes, but the interesting bit is "X bytes from". Please post them.
EDIT:
anyway, the ifconfig you posted said it is trying to route through ethernet.

Last edited by jdiez (2009-08-09 23:27:36)

Scrivener · 2009-08-09 23:34:05

jdiez wrote:

Yes, but the interesting bit is "X bytes from". Please post them.

I'm sorry. I'm not understanding you. Here's what it looks like in my console:

$ ping 192.168.0.1
connect: Network is unreachable
$

I'm not seeing "X bytes from" anywhere in the output. Is there a ping option that I'm missing?

jdiez · 2009-08-09 23:39:30

You have taken down ethernet, right?

Scrivener · 2009-08-09 23:46:35

Yes. I've taken down eth0, but I'm still not able to connect on eth1. If I take down eth1, I'm not able to connect on eth0.

Thank for your help but I think we're going in circles. The issue seems to be that my wireless card isn't being properly detected on subsequent reboots. If it was a manual configuration issue and I hadn't changed any settings it would continue to work on subsequent reboots. So something is stopping the detection of the wireless or detecting it incorrectly. Would that be hal?

Scrivener · 2009-08-11 13:48:30

I'm pretty sure I fixed it. I ran pacman -U /var/cache/pacman/pkg/hal-info-0-20090414-1-x86_64.pkg.tar.gz to revert hal-info back to its previous version. After that I rebooted and my wireless came up normally. I rebooted again to check that it was working and came up again.

So it seems the problem lies in the newest version of hal-info.

Last edited by Scrivener (2009-08-11 13:48:58)

scrawler · 2009-08-11 17:57:52

howdy guys,

Yesterday or the day before a big upgrade broke wireless on my hp laptop. I had been using ndiswrapper. After some fiddling, and a couple of failed attempts to get it right, however, I am now happily online. I followed the wiki article referenced (Broadcom BCM4312) and life is good.

ymmv
:-)

tomk · 2009-08-11 18:30:05

Thread title changed, as the OP no longer seems to be here.

Bogart · 2009-08-13 11:00:48

I have the same wireless adapter and the same problem. It worked fne until a few days ago, but now it sometimes work and sometimes doesn't. Basically, the problem is that the b43 module tries to load before wl module and screws things up. On a good boot, if I do "dmesg | grep b43", the output is empty. On a bad one, there are a few lines.

The main suspects are the latest initscripts+udev upgrades. I have just downgraded them and the first boot has worked. I'll report if it fixes it completely. (Note that if you downgrade these packages you'll have to be careful to adjust your /etc/inittab file to the old style).

vacant · 2009-08-13 11:57:33

Bogart wrote:

Basically, the problem is that the b43 module tries to load before wl module and screws things up. On a good boot, if I do "dmesg | grep b43", the output is empty.

The b43 module is loading even though you are blacklisting it (assuming you've followed this thread)?

Bogart · 2009-08-13 16:35:10

Yes, blacklisting b43 doesn't work. It might still try to load and screw everything.

I'm still testing if it's initscripts + udev upgrade. Else I'll try the hal-info downgrade.

vacant · 2009-08-14 06:51:43

Well it that case, move b43 somewhere depmod won't find it (and ssb while you're at it?).

F · 2009-08-17 19:18:40

Solution:

1. don't use b43 drivers.
2. build broadcom-wl from AUR.
3. run depmod -a;
4. put the following in MODULES: wl !b43 !b43-legacy !ssb
5. reboot
6. use ifconfig to bring up the device if necessary.
7. use iwconfig to connect to wireless network
8. run dhcp tool to request IP (dhcpcd for me)
9. ???
10. PROFIT!

edit:
$ lspci -nn | grep Broadcom
03:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01)

Last edited by F (2009-08-17 19:19:59)

stefek · 2009-08-18 09:45:54

Hi everyone!!
I've got Dell Studio 1555 with Broadcom BCM4322 wireless card. There is one irritating problem. Every second restart it detects wireless networks. When I shutdown laptop and start again there is no problem. I've got broadcom-wl built from aur and blacklisted b43, b43-legacy and ssb, but it doesn't want to work. I thought that is a bug in network manager which i used with kde plasmoid, so i've installed wicd, but it's the same problem. lspci detects card correctly.
Does anyone know the solution for this problem?
stefek

Bogart · 2009-08-18 10:55:56

stefek wrote:

Hi everyone!!
I've got Dell Studio 1555 with Broadcom BCM4322 wireless card. There is one irritating problem. Every second restart it detects wireless networks. When I shutdown laptop and start again there is no problem. I've got broadcom-wl built from aur and blacklisted b43, b43-legacy and ssb, but it doesn't want to work. I thought that is a bug in network manager which i used with kde plasmoid, so i've installed wicd, but it's the same problem. lspci detects card correctly.
Does anyone know the solution for this problem?
stefek

A couple of questions:

- Did it work reliably before some upgrade that happened recently?

- When it doesn't work, does the command "dmesg | grep b43" output anything?

stefek · 2009-08-18 11:39:12

It hasn't work properly since i installed arch(29th July). When it doesn't work, there are empty output for dmesg | grep b43.

Scrivener · 2009-08-18 14:31:44

Hal-info was updated on 8/15/09 and that version is working fine for me. At least it is so far. I've rebooted a few times after the install and gotten a solid connection to my router.

Bogart · 2009-08-18 14:31:59

Ah, then it's a different problem from the one in this thread. No idea about what's the problem, sorry

I also wanted to confirm that the problem described in this thread (at least for me) was introduced by some upgrades from August 8th (initscripts and udev, actually, but not sure which one of them) but blacklisting b43, b43-legacy and ssb seems to have solved the problem here.

stefek · 2009-08-18 16:35:09

Here is wicd log when my wifi works properly:

2009/08/18 18:18:42 :: wicd is version 1.6.2 436
2009/08/18 18:18:42 :: setting backend to external
2009/08/18 18:18:42 :: trying to load backend external
2009/08/18 18:18:43 :: successfully loaded backend external
2009/08/18 18:18:43 :: trying to load backend external
2009/08/18 18:18:43 :: successfully loaded backend external
2009/08/18 18:18:43 :: Automatically detected wireless interface eth0
2009/08/18 18:18:43 :: setting wireless interface eth0
2009/08/18 18:18:43 :: automatically detected wired interface eth1
2009/08/18 18:18:43 :: setting wired interface eth1
2009/08/18 18:18:43 :: setting wpa driver wext
2009/08/18 18:18:44 :: setting use global dns to False
2009/08/18 18:18:44 :: setting global dns
2009/08/18 18:18:44 :: global dns servers are None None None
2009/08/18 18:18:44 :: domain is None
2009/08/18 18:18:44 :: search domain is None
2009/08/18 18:18:44 :: setting automatically reconnect when connection drops True
2009/08/18 18:18:44 :: Setting dhcp client to 0
2009/08/18 18:18:44 :: Wireless configuration file found...
2009/08/18 18:18:44 :: Wired configuration file found...
2009/08/18 18:18:44 :: chmoding configuration files 0600...
2009/08/18 18:18:44 :: chowning configuration files root:root...
2009/08/18 18:18:44 :: Using wireless interface...eth0
2009/08/18 18:18:44 :: Using wired interface...eth1
2009/08/18 18:18:52 :: Autoconnecting...
2009/08/18 18:18:52 :: No wired connection present, attempting to autoconnect to wireless network
2009/08/18 18:18:55 :: trying to automatically connect to...default
2009/08/18 18:18:55 :: Connecting to wireless network default
2009/08/18 18:18:55 :: Putting interface down
2009/08/18 18:18:55 :: Releasing DHCP leases...
2009/08/18 18:18:55 :: Setting false IP...
2009/08/18 18:18:55 :: Stopping wpa_supplicant
2009/08/18 18:18:55 :: Flushing the routing table...
2009/08/18 18:18:55 :: Putting interface up...
2009/08/18 18:18:55 :: Running DHCP
2009/08/18 18:18:55 :: dhcpcd: version 5.0.6 starting
2009/08/18 18:18:55 :: 
2009/08/18 18:18:55 :: dhcpcd: eth0: rebinding lease of 192.168.2.100
2009/08/18 18:18:55 :: 
2009/08/18 18:18:59 :: dhcpcd: eth0: acknowledged 192.168.2.100 from 192.168.2.1
2009/08/18 18:18:59 :: 
2009/08/18 18:18:59 :: dhcpcd: eth0: checking for 192.168.2.100
2009/08/18 18:18:59 :: 
2009/08/18 18:19:03 :: dhcpcd: eth0: leased 192.168.2.100 for 946080000 seconds
2009/08/18 18:19:03 :: 
2009/08/18 18:19:03 :: dhcpcd: forking to background
2009/08/18 18:19:03 :: 
2009/08/18 18:19:03 :: 
2009/08/18 18:19:03 :: DHCP connection successful
2009/08/18 18:19:03 :: Connecting thread exiting.
2009/08/18 18:19:07 :: Sending connection attempt result Success

And when something is wrong:

2009/08/18 17:42:54 :: wicd is version 1.6.2 436
2009/08/18 17:42:54 :: setting backend to external
2009/08/18 17:42:54 :: trying to load backend external
2009/08/18 17:42:55 :: successfully loaded backend external
2009/08/18 17:42:55 :: trying to load backend external
2009/08/18 17:42:55 :: successfully loaded backend external
2009/08/18 17:42:55 :: Automatically detected wireless interface eth0
2009/08/18 17:42:55 :: setting wireless interface eth0
2009/08/18 17:42:56 :: automatically detected wired interface eth1
2009/08/18 17:42:56 :: setting wired interface eth1
2009/08/18 17:42:56 :: setting wpa driver wext
2009/08/18 17:42:56 :: setting use global dns to False
2009/08/18 17:42:56 :: setting global dns
2009/08/18 17:42:56 :: global dns servers are None None None
2009/08/18 17:42:56 :: domain is None
2009/08/18 17:42:56 :: search domain is None
2009/08/18 17:42:56 :: setting automatically reconnect when connection drops True
2009/08/18 17:42:56 :: Setting dhcp client to 0
2009/08/18 17:42:56 :: Wireless configuration file found...
2009/08/18 17:42:56 :: Wired configuration file found...
2009/08/18 17:42:56 :: chmoding configuration files 0600...
2009/08/18 17:42:56 :: chowning configuration files root:root...
2009/08/18 17:42:56 :: Using wireless interface...eth0
2009/08/18 17:42:56 :: Using wired interface...eth1
2009/08/18 17:43:04 :: Autoconnecting...
2009/08/18 17:43:04 :: No wired connection present, attempting to autoconnect to wireless network
2009/08/18 17:43:05 :: Unable to autoconnect, you'll have to manually connect
2009/08/18 17:43:07 :: Autoconnecting...
2009/08/18 17:43:07 :: No wired connection present, attempting to autoconnect to wireless network
2009/08/18 17:43:08 :: Unable to autoconnect, you'll have to manually connect
2009/08/18 17:43:12 :: Autoconnecting...
2009/08/18 17:43:12 :: No wired connection present, attempting to autoconnect to wireless network
2009/08/18 17:43:13 :: Unable to autoconnect, you'll have to manually connect
2009/08/18 17:43:17 :: Autoconnecting...
2009/08/18 17:43:17 :: No wired connection present, attempting to autoconnect to wireless network
2009/08/18 17:43:18 :: Unable to autoconnect, you'll have to manually connect
2009/08/18 17:45:48 :: Daemon going down, killing wicd-monitor...
2009/08/18 17:45:48 :: Removing PID file...
2009/08/18 17:45:48 :: Shutting down...

Maybe, is here anyone who have similiar problems?
Problems with acpi, bluetooth or edge scrolling not using xorg.conf are nothing in comparison with it.
Thank you!

My laptop managed to find a wireless network 3 times in a row. I don't know what's going on. Maybe there is something wrong with hardware?

Again it can't scan network and this is iwlist eth0 scan output

eth0: Failed to read scan data : Invalid argument

Last edited by stefek (2009-08-18 18:47:13)

Scrivener · 2009-08-23 05:44:03

The hal-info update from 8/15/09 only works sometimes. When it doesn't work, the wl module ends up on eth0 and acts like a wired interface. My wired network module ends up on eth1. I've been taking my chances with a reboot. Sometimes it gets detected correctly, sometimes not.

Bogart, it may be a problem with the initscripts. Something is happening intermittently on boot that messes it up. I might end up blacklisting my wired network module to see if that stabilizes it. Once it comes up, it's stable and solid. I'm not finding anything when I run: dmesg | grep b43

Scrivener · 2009-08-25 07:06:08

I played around with this some more and I'm glad I responded in the Newbie Corner.

It's partly an issue with the wireless ending up on eth0 vs. eth1. But there's an easy workaround. I just go into the wicd preferences and change the wireless to eth0 or eth1.

Arch Linux

#26 2009-08-09 04:13:32

Re: Broadcom 4312 problems following upgrade

#27 2009-08-09 04:36:46

Re: Broadcom 4312 problems following upgrade

#28 2009-08-09 16:10:04

Re: Broadcom 4312 problems following upgrade

#29 2009-08-09 16:37:14

Re: Broadcom 4312 problems following upgrade

#30 2009-08-09 23:12:56

Re: Broadcom 4312 problems following upgrade

#31 2009-08-09 23:26:31

Re: Broadcom 4312 problems following upgrade

#32 2009-08-09 23:34:05

Re: Broadcom 4312 problems following upgrade

#33 2009-08-09 23:39:30

Re: Broadcom 4312 problems following upgrade

#34 2009-08-09 23:46:35

Re: Broadcom 4312 problems following upgrade

#35 2009-08-11 13:48:30

Re: Broadcom 4312 problems following upgrade

#36 2009-08-11 17:57:52

Re: Broadcom 4312 problems following upgrade

#37 2009-08-11 18:30:05

Re: Broadcom 4312 problems following upgrade

#38 2009-08-13 11:00:48

Re: Broadcom 4312 problems following upgrade

#39 2009-08-13 11:57:33

Re: Broadcom 4312 problems following upgrade

#40 2009-08-13 16:35:10

Re: Broadcom 4312 problems following upgrade

#41 2009-08-14 06:51:43

Re: Broadcom 4312 problems following upgrade

#42 2009-08-17 19:18:40

Re: Broadcom 4312 problems following upgrade

#43 2009-08-18 09:45:54

Re: Broadcom 4312 problems following upgrade

#44 2009-08-18 10:55:56

Re: Broadcom 4312 problems following upgrade

#45 2009-08-18 11:39:12

Re: Broadcom 4312 problems following upgrade

#46 2009-08-18 14:31:44

Re: Broadcom 4312 problems following upgrade

#47 2009-08-18 14:31:59

Re: Broadcom 4312 problems following upgrade

#48 2009-08-18 16:35:09

Re: Broadcom 4312 problems following upgrade

#49 2009-08-23 05:44:03

Re: Broadcom 4312 problems following upgrade

#50 2009-08-25 07:06:08

Re: Broadcom 4312 problems following upgrade

Board footer