Arch Linux

ehabreda

Member

From: Qatar

Registered: 2011-07-22

Posts: 52

Website

Kernel-ck (Broadcom wireless)

Hello guys,

I installed the CK core 2 with nvidia, broadcom-wl. (64 bit)
It was all OK and even I can see my wireless network. I also installed wicd to help me out figuring how to setup my wireless.
When I try to pick my wl it always give me connection failed unable to get IP address.

Is there any other settings to apply.

I also tried to setup my wireless with the normal Arch kernel and I have the same problem (I have tried everything)

Please help me out.

ehab@myhost ~]$ lspci | grep -i net
04:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)

[root@arch ehab]# lspci -vnn | grep 14e4
04:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)

[ehab@myhost ~]$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:23:5A:44:9E:C1  
          inet addr:192.168.1.93  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::223:5aff:fe44:9ec1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:170252 errors:0 dropped:0 overruns:0 frame:0
          TX packets:144546 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:239504626 (228.4 Mb)  TX bytes:9420101 (8.9 Mb)
          Interrupt:48 Base address:0xe000 

eth1      Link encap:Ethernet  HWaddr 00:24:2C:56:00:6B  
          inet6 addr: fe80::224:2cff:fe56:6b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:2935
          TX packets:0 errors:189 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
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:35010 errors:0 dropped:0 overruns:0 frame:0
          TX packets:35010 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2761188 (2.6 Mb)  TX bytes:2761188 (2.6 Mb)

[ehab@myhost ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:23:5a:44:9e:c1 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:24:2c:56:00:6b brd ff:ff:ff:ff:ff:ff

My rc.conf

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

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
#   Note: Using "localtime" is discouraged, using "" makes hwclock fall back
#   to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
#   Note: if unset, the value in /etc/localtime is used unchanged
# 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"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="Asia/Qatar"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
#   Replace every !module by an entry as on the following line in a file in
#   /etc/modprobe.d:
#     blacklist module
#   See "man modprobe.conf" for details.
#
MODULES=(fuse)

# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30

# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"

# Scan for BTRFS volumes at startup
USEBTRFS="no"

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

# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
#
# Wired network setup
#   - interface: name of device (required)
#   - address: IP address (leave blank for DHCP)
#   - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
#   - broadcast: broadcast address (ignored for DHCP) (optional)
#   - gateway: default route (ignored for DHCP)
# 
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
#
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=

interface=eth0
address=
netmask=
broadcast=
gateway=

# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"

# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as 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 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
#
# If something other takes care of your hardware clock (ntpd, dual-boot...)
# you should disable 'hwclock' here.
#
DAEMONS=(hwclock syslog-ng dbus hal fam !network !networkmanager wicd netfs crond alsa gdm appset-helper)

My wired network works perfectly.

moetunes

Member

From: A comfortable couch

Registered: 2010-10-09

Posts: 1,033

Re: Kernel-ck (Broadcom wireless)

does it show in   ifconfig -a   ?

---

You're just jealous because the voices only talk to me.

graysky

Wiki Maintainer

From: :wq

Registered: 2008-12-01

Posts: 10,597

Website

Re: Kernel-ck (Broadcom wireless)

I also tried to setup my wireless with the normal Arch kernel and I have the same problem (I have tried everything)

Please change the topic of your thread to remove the "kernel-ck" since this is very likely a problem with your hardware, not the kernel26-ck package.

---

CPU-optimized Linux-ck packages @ Repo-ck  • AUR packages • Zsh and other configs

ehabreda

Member

From: Qatar

Registered: 2011-07-22

Posts: 52

Website

Re: Kernel-ck (Broadcom wireless)

I also tried to setup my wireless with the normal Arch kernel and I have the same problem (I have tried everything)

Please change the topic of your thread to remove the "kernel-ck" since this is very likely a problem with your hardware, not the kernel26-ck package.

I meant before installing the CK-Kernel.

So at the moment I am having the kernel and still not working.

ehabreda

Member

From: Qatar

Registered: 2011-07-22

Posts: 52

Website

Re: Kernel-ck (Broadcom wireless)

does it show in   ifconfig -a   ?

Yes as follows:

[ehab@myhost ~]$  ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:23:5A:44:9E:C1  
          inet addr:192.168.1.93  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::223:5aff:fe44:9ec1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2493 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1866 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1866211 (1.7 Mb)  TX bytes:286127 (279.4 Kb)
          Interrupt:48 Base address:0x6000 

eth1      Link encap:Ethernet  HWaddr 00:24:2C:56:00:6B  
          inet6 addr: fe80::224:2cff:fe56:6b/64 Scope:Link
          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
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:14 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:884 (884.0 b)  TX bytes:884 (884.0 b)

xclaude

Member

Registered: 2011-07-07

Posts: 17

Re: Kernel-ck (Broadcom wireless)

in your rc.conf you have to add the modul for your driver. in your case 'wl' (without quotes).
make sure, other incompatible drivers are blacklisted with a conf-file in '/etc/modprobe.d/', but this should have been done when broadcom-wl was installed.

/etc/rc.conf

...
MODULES=(fuse wl)
...

now it should work for you.

personaly, i have the same chipset in my HP Laptop. When i configured it 1st, i had some problems with wicd. i have changed to use networkmanager (change this in your DAEMONS-Section in /etc/rc.conf) and for configuration in kde i installed 'kdeplasma-applets-networkmanagement' from official repo.
In yor kde systempanel right-click on the litle arrow and configure it, unlock the applets and tick networkmanagement on. now you can configure your wireless lan in a graphical environment.

Edit: Don't forget to uncomment (or change this to interface= ) the following line in your rc.conf, or networkmaner will not work !!!!
interface=eth0

Last edited by xclaude (2011-08-10 08:56:34)