Arch Linux

Angle

Member

Registered: 2009-06-15

Posts: 21

[Solved] Wireless Broadcom Woes

Hello,
I just installed Arch on my laptop and it is running great. I have everything working but the wireless. Unfortunately, it has a Dell 1397 card (I should have upgraded when I bought it ). I followed the instructions here to install the Broadcom-wl. I used AUR and installed the module then added it to my /etc/rc.conf modules list, so it now looks like this:

MODULES=(lib80211_crypt_tkip wl)

The problem is when I reboot my computer it will show

:: Starting Network 
dhcpcd: timed out

However, when I manually launch dhcpcd when the computer boots up, everything works. I have searched quite a bit but none of the solutions have seemed to help. If anyone knows what's going on, it would be much appreciated.

Last edited by Angle (2009-07-12 00:17:03)

jbusch

Member

Registered: 2009-01-27

Posts: 20

Re: [Solved] Wireless Broadcom Woes

Could you cat your entire /etc/rc.conf ?

Just a guess, but your computer might be trying to dhcpcd an ethernet interface on boot.

- J

Angle

Member

Registered: 2009-06-15

Posts: 21

Re: [Solved] Wireless Broadcom Woes

I didn't know how else to configure rc.conf, so I just left it as it was.

#
# /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"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# 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.utf8"
HARDWARECLOCK="local"
USEDIRECTISA="no"
TIMEZONE="America/Chicago"
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)

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

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

# 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
#
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)
 
# 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 network netfs crond alsa)

kgas

Member

From: Qatar

Registered: 2008-11-08

Posts: 718

Re: [Solved] Wireless Broadcom Woes

Your interface list only the wired connection and no wireless that is to be corrected. blacklist bc* modules (!bc43 eg, in the modules array if it got loaded check this thro' lsmod). put the correct gw address in gateway="default gw 192.168.0.1"  and keep ROUTES=(gateway). This works fine. If you use wicd it is straight and simple.

jbusch

Member

Registered: 2009-01-27

Posts: 20

Re: [Solved] Wireless Broadcom Woes

This might help:
http://wiki.archlinux.org/index.php/Wir … ork_daemon

So maybe if you change the top part of your networking section to

eth0="dhcp"
wlan0="dhcp"
INTERFACES=(eth0 wlan0)

It will work?

I have to set my wireless back up come this fall, so I suppose helping you is good practice for me. 

- J

Edit: Try what kgas posted first, as kgas sounds knowledgeable about the subject

Last edited by jbusch (2009-07-11 04:11:13)

Square

Member

Registered: 2008-06-11

Posts: 435

Re: [Solved] Wireless Broadcom Woes

I have the exact same wireless card, and with broadcom-wl it works flawlessly.

In my modules line I have:

MODULES=(... !b43 lib80211_crypt_tkip wl ...)

For my interface:

eth0="dhcp"
INTERFACES=(!eth0)

ROUTES=(!gateway)

And then I use netcfg, so I have a network named wireless in /etc/network.d, and then wireless listed in my NETWORKS array in my rc.conf

My 'wireless' network a.k.a. /etc/network.d/wireless:

CONNECTION="wireless"
DESCRIPTION="A simple WEP encrypted wireless connection"
INTERFACE=eth0
SCAN="no"
SECURITY="wep"
ESSID="xxxxxxx"
KEY="xxxxxxxxx"
IP="dhcp"

I only have WEP encryption (yes, I know, blah blah blah), but for everything else there really isn't anything special. It just works.

Edit: Note - net-profiles must be in your DAEMONS array in rc.conf for netcfg, and the netcfg package must be installed. (I assumed these obvious, but then again there's that phrase about when you assume...)

Last edited by Square (2009-07-11 05:18:01)

---

 

Angle

Member

Registered: 2009-06-15

Posts: 21

Re: [Solved] Wireless Broadcom Woes

Thanks Square, jbusch, and kgas. I tried the first two suggestions and they half-way worked. I eventually did what Square suggested and installed netcfg. It worked great.

Last edited by Angle (2009-07-12 00:17:25)