[SOLVED]Broadcom Wireless Startup Not Reliable

duke11235 · 2010-09-14 00:01:31

Sometimes it start up, and sometimes I am unable to get anything from the card. I know the wl driver was installed correctly, as it works occasionally.
To try to fix the weird network card swapping, I created 10-network.rules

SUBSYSTEM=="net", ATTR(address)=="00:1f:f3:fb:9f:3a", NAME="eth0"
SUBSYSTEM=="net", ATTR(address)=="00:1f:5b:ff:75:2c", NAME="wlan1"

Any other helpful information I could provide?

SOLUTION: Be sure to blacklist all the modules on the wiki page, one was conflicting. Once I did that everything worked great.

Last edited by duke11235 (2010-10-10 17:28:13)

karol · 2010-09-14 00:07:59

And your rc.conf? 'ifconfig -a'?

duke11235 · 2010-09-14 02:21:07

rc.conf

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.UTF-8"
HARDWARECLOCK="UTC"
TIMEZONE="America/Los_Angeles"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(lib80211_crypt_tkip wl !b43 !b43legacy)

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="yes"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="myhost"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
# 
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#

#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(eth0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
 
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"

# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng dbus !network netfs crond wicd alsa mpd sensors)

ifconfig -a

-- mod edit: read the Forum Etiquette and only post thumbnails (and in this case, just use text): http://wiki.archlinux.org/index.php/For … s_and_Code --

Last edited by duke11235 (2010-09-15 02:06:02)

karol · 2010-09-14 02:24:51

And why can't you post the output of 'ifconfig -a' instead of this screenshot?

You have just one interface listed

INTERFACES=(eth0)

Have you tried adding the other one too?

The screenshot says one thing, your udev rule another: 00:1f:5b:ff:75:2c - what card is it?

Last edited by karol (2010-09-14 02:29:22)

duke11235 · 2010-09-14 03:33:44

I haven't yet implemented copy paste out of urxvt, or xterm(don't know how), and the output was quite long. That is why I used the screenshot, which I then had to transfer to another partition to upload.

karol · 2010-09-14 03:38:24

duke11235 wrote:

I haven't yet implemented copy paste out of urxvt, or xterm(don't know how), and the output was quite long. That is why I used the screenshot, which I then had to transfer to another partition to upload.

ifconfig -a > some.file

will save the output to a file.

Generally, you select a text (with the mouse or otherwise) and the selection gets copied automatically. Press middle mouse button or Shift + Insert to paste.

duke11235 · 2010-09-14 03:46:08

Here it is then:
From Linux(it changes, annoyingly):

[duke@myhost ~]$ ifconfig -a
eth0-wlan Link encap:Ethernet  HWaddr 00:1F:F3:FB:9F:3A  
          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:17 Base address:0xc000 

wlan1     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:213 errors:0 dropped:0 overruns:0 frame:0
          TX packets:213 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:15586 (15.2 Kb)  TX bytes:15586 (15.2 Kb)

and Perhaps more helpfully, from Mac terminal:

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
    inet6 ::1 prefixlen 128 
    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
    inet 127.0.0.1 netmask 0xff000000 
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    ether 00:1f:f3:fb:9f:3a 
    media: autoselect
    status: inactive
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    ether 00:1f:5b:ff:75:2c 
    inet6 fe80::21f:5bff:feff:752c%en1 prefixlen 64 scopeid 0x5 
    inet 10.0.1.6 netmask 0xffffff00 broadcast 10.0.1.255
    media: <unknown subtype>
    status: active

en0 is known as ethernet in bsd style naming and en1 is my airport card.

Since I am using wicd, I though the contents of that file would be irrelevant. Do you still recommend changing them?

Last edited by duke11235 (2010-09-14 03:50:19)

pseudonomous · 2010-09-14 04:14:23

There's something seriously screwed up with your networking configuration; you've managed to assign "wlan0" your local loopback address (the address your computer uses to talk to itself). Furthermore, you don't HAVE a loopback interface listed (and that can't be good).

Did you do anything to "/etc/rc.sysint"? I can't imagine how else you can avoid having a loopback, unless, by some bizarre confluence of software configuration you've managed to rename your loopback interface "wlan1". (That's also probably not good).

What I think you might want to do is try booting up without loading wicd and make sure you have a loopback address. If you don't, try loading up without your udev rules and see if you have a loopback address.

Also, there has got to be something wrong with your udev rules because you've got an interface named "eth0-wlan", you shouldn't have something named that, you should only have "eth0" and "wlan0". Also, you should have at least one loopback interface.

karol · 2010-09-14 09:25:05

pseudonomous wrote:

There's something seriously screwed up with your networking configuration; you've managed to assign "wlan0" your local loopback address (the address your computer uses to talk to itself). Furthermore, you don't HAVE a loopback interface listed (and that can't be good).
Did you do anything to "/etc/rc.sysint"? I can't imagine how else you can avoid having a loopback, unless, by some bizarre confluence of software configuration you've managed to rename your loopback interface "wlan1". (That's also probably not good).
What I think you might want to do is try booting up without loading wicd and make sure you have a loopback address. If you don't, try loading up without your udev rules and see if you have a loopback address.
Also, there has got to be something wrong with your udev rules because you've got an interface named "eth0-wlan", you shouldn't have something named that, you should only have "eth0" and "wlan0". Also, you should have at least one loopback interface.

In the first post the was a screenshot of 'ifconfig -a' that had all three: wlan1, loopback and eth0-wlan.
00:1f:5b:ff:75:2c address wasn't wlan1, as you would think looking at the udev rules, but eth0.

duke11235 · 2010-09-14 21:49:18

I know, it changes randomly, despite the rules. Loopback is shown on mac as lo0 and was in my screenshot

duke11235 · 2010-09-16 01:00:38

What do you guys recommend? A complete reinstall? Do you need more information? I haven't done any special editing to rc.sysint intentionally. Sorry if I seem a bit whiny, but my internet connection is very important to me

codycarey · 2010-09-16 02:01:04

Not necessarily reinstall, but start over. First off, delete your udev rules (which I think are wrong actually, ATTR{} and not ATTR()), remove 'eth0' from INTERFACES and re-enable 'network' in DAEMONS of your rc.conf and reboot. Then post the output of 'ifconfig -a'.

Last edited by codycarey (2010-09-16 02:04:15)

duke11235 · 2010-09-17 04:55:26

Thanks codycarey those brackets were supposed to be { and not this ). It fixed the incredibly slow udev time. But now ifconfig -a still shows no eth1, but it does show eth0 and loopback. Any further helpful tips

Last edited by duke11235 (2010-09-18 00:10:48)

Arch Linux

#1 2010-09-14 00:01:31

[SOLVED]Broadcom Wireless Startup Not Reliable

#2 2010-09-14 00:07:59

Re: [SOLVED]Broadcom Wireless Startup Not Reliable

#3 2010-09-14 02:21:07

Re: [SOLVED]Broadcom Wireless Startup Not Reliable

#4 2010-09-14 02:24:51

Re: [SOLVED]Broadcom Wireless Startup Not Reliable

#5 2010-09-14 03:33:44

Re: [SOLVED]Broadcom Wireless Startup Not Reliable

#6 2010-09-14 03:38:24

Re: [SOLVED]Broadcom Wireless Startup Not Reliable

#7 2010-09-14 03:46:08

Re: [SOLVED]Broadcom Wireless Startup Not Reliable

#8 2010-09-14 04:14:23

Re: [SOLVED]Broadcom Wireless Startup Not Reliable

#9 2010-09-14 09:25:05

Re: [SOLVED]Broadcom Wireless Startup Not Reliable

#10 2010-09-14 21:49:18

Re: [SOLVED]Broadcom Wireless Startup Not Reliable

#11 2010-09-16 01:00:38

Re: [SOLVED]Broadcom Wireless Startup Not Reliable

#12 2010-09-16 02:01:04

Re: [SOLVED]Broadcom Wireless Startup Not Reliable

#13 2010-09-17 04:55:26

Re: [SOLVED]Broadcom Wireless Startup Not Reliable

Board footer