You are not logged in.

#1 2010-12-18 17:39:02

NaX_sa
Member
From: South Africa
Registered: 2010-12-18
Posts: 12

Dell Studio 17, Broadcom Wireless 4353, BCM43XX, KDE + NetworkManager

Hi

I have a new Dell Studio 17. I have recently started using Arch and I am really enjoying it, previously I was on OpenSuse.

I have gotten most of what I need working. The only thing I have gotten stuck on is my wireless drivers.

I previously had an older Dell Studio 17 that was stolen but I easily got the wireless working in OpenSuse.

This new machine that is  an insurance replacement seems to be using a much newer wireless chipset.

Can anybody please help me sort this out. I have read that some people have had some success with this chipset.

I have been using the following wiki page as my primary reference for setup and trouble shooting.
- https://wiki.archlinux.org/index.php/Broadcom_BCM43XX

I am able to see my wireless network in NetworkManager but I am unable to connect to it.

My wireless network is setup to use WPA-PSK.

lspci -nn | grep 14e4 returns:

08:00.0 Network controller [0280]: Broadcom Corporation Device [14e4:4353] (rev 01)

/var/log/messages.log - I think the " failed to activate (timeout)" is the problem

Dec 18 18:15:55 justin NetworkManager[4218]: <info> Activation (lan0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 18 18:15:55 justin NetworkManager[4218]: <info> Activation (lan0) Stage 1 of 5 (Device Prepare) started...
Dec 18 18:15:55 justin NetworkManager[4218]: <info> Activation (lan0) Stage 2 of 5 (Device Configure) scheduled...
Dec 18 18:15:55 justin NetworkManager[4218]: <info> Activation (lan0) Stage 1 of 5 (Device Prepare) complete.
Dec 18 18:15:55 justin NetworkManager[4218]: <info> Activation (lan0) Stage 2 of 5 (Device Configure) starting...
Dec 18 18:15:55 justin NetworkManager[4218]: <info> (lan0): device state change: 4 -> 5 (reason 0)
Dec 18 18:15:55 justin NetworkManager[4218]: <info> Activation (lan0) Stage 2 of 5 (Device Configure) successful.
Dec 18 18:15:55 justin NetworkManager[4218]: <info> Activation (lan0) Stage 3 of 5 (IP Configure Start) scheduled.
Dec 18 18:15:55 justin NetworkManager[4218]: <info> Activation (lan0) Stage 2 of 5 (Device Configure) complete.
Dec 18 18:15:55 justin NetworkManager[4218]: <info> Activation (lan0) Stage 3 of 5 (IP Configure Start) started...
Dec 18 18:15:55 justin NetworkManager[4218]: <info> (lan0): device state change: 5 -> 7 (reason 0)
Dec 18 18:15:55 justin NetworkManager[4218]: <info> Activation (lan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Dec 18 18:15:55 justin NetworkManager[4218]: <info> Activation (lan0) Stage 3 of 5 (IP Configure Start) complete.
Dec 18 18:15:55 justin NetworkManager[4218]: <info> Activation (lan0) Stage 4 of 5 (IP4 Configure Get) started...
Dec 18 18:15:55 justin NetworkManager[4218]: <info> Activation (lan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Dec 18 18:15:55 justin NetworkManager[4218]: <info> Activation (lan0) Stage 4 of 5 (IP4 Configure Get) complete.
Dec 18 18:15:55 justin NetworkManager[4218]: <info> Activation (lan0) Stage 5 of 5 (IP Configure Commit) started...
Dec 18 18:15:56 justin NetworkManager[4218]: <info> (lan0): device state change: 7 -> 8 (reason 0)
Dec 18 18:15:56 justin NetworkManager[4218]: <info> Policy set 'Home - eth' (lan0) as default for IPv4 routing and DNS.
Dec 18 18:15:56 justin NetworkManager[4218]: <info> Activation (lan0) successful, device activated.
Dec 18 18:15:56 justin NetworkManager[4218]: <info> Activation (lan0) Stage 5 of 5 (IP Configure Commit) complete.
Dec 18 18:42:32 justin NetworkManager[4218]: <warn> connection /org/freedesktop/NetworkManagerSettings/1 (scope 2) failed to activate (timeout)
Dec 18 18:42:52 justin NetworkManager[4218]: <info> (lan0): device state change: 8 -> 3 (reason 0)
Dec 18 18:42:52 justin NetworkManager[4218]: <info> (lan0): deactivating device (reason: 0).
Dec 18 18:42:52 justin NetworkManager[4218]: <info> Activation (lan0) starting connection 'Home - eth'

/etc/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="Africa/Johannesburg"
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=(acpi-cpufreq cpufreq_ondemand cpufreq_powersave cpufreq_powersave cpufreq_conservative lib80211 lib80211_crypt_tkip wl !b43 !ssb !i915)

# 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="justin"

# 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.3 netmask 255.255.255.0 broadcast 192.168.0.255"
#eth0="dhcp"
INTERFACES=(!eth0 !wlan0)

# 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
#
# Note: If you already have hal specified in your DAEMONS, there is no need 
# to add acpid. HAL will automatically detect and load the acpid daemon.
#
DAEMONS=(syslog-ng dbus hal dhcpcd bluetooth networkmanager !network netfs alsa crond)

Offline

#2 2010-12-19 22:53:05

NaX_sa
Member
From: South Africa
Registered: 2010-12-18
Posts: 12

Re: Dell Studio 17, Broadcom Wireless 4353, BCM43XX, KDE + NetworkManager

I found what the problem was.

I am very pleased to say that it was not the drivers that were causing the problem.

The problem turned out to be NetworkManager. I really like the NetworkManager GUI so I am not please to have to give it up.

I am currently giving wicd + wicd-client-kde a try and if I don't like it I might try Netcfg.

At least now I have a working wireless solution.

Offline

#3 2010-12-28 15:19:34

jhf2442
Member
Registered: 2010-09-29
Posts: 17

Re: Dell Studio 17, Broadcom Wireless 4353, BCM43XX, KDE + NetworkManager

Same issue here (but with different laptop brand). doing sudo /etc/rc.d/networkmanager restart after loging in solves the issue

has however to be done upon *each* login

Offline

Board footer

Powered by FluxBB