topic title: Cannot connect to wifi networks with Ceni or wicd.
Posts: 5
Asmo
Joined: 25 Oct 2011
#1
So yeah, like the topic says, I've been having trouble connecting to wifi networks in Antix. In wicd, I can detect networks and everything, but when I actually try to connect, it attempts to but then I get an error along the lines of"Could not get IP address".

If it helps, my network controller is Broadcom Corporation BCM4312 802.11b/g (rev 01).

And I'm pretty sure
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://amritasoda.tk/stuff/HNI_0083.JPG"
linktext was:"this error I'm getting in ttys"
====================================
has something to do with the problem I've been having.
Posts: 4,164
rokytnji
Joined: 20 Feb 2009
#2
I don't use broadcom chip on my wireless interfaces. I'm posting from my wireless Motorcycle shop Desktop.

Code: Select all

 lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0bda:8189 Realtek Semiconductor Corp. RTL8187B Wireless 802.11g 54Mbps Network Adapter
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
OHH (a member here is the broadcom guru) so hopefully he will weigh in on your thread. You can search the net for oldhoghead broadcom antix also. Edit: did it for you


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.google.com/search?source=ig&hl=en&rlz=1G1ACAWCENUS372&=&q=oldhoghead+broadcom+BCM4312+&btnG=Google+Search&oq=oldhoghead+broadcom+BCM4312+&aq=f&aqi=&aql=&gs_sm=s&gs_upl=58l42950l0l44016l18l18l0l14l0l0l732l1632l0.2.5-1.1l4l0"
linktext was:"http://www.google.com/search?source=ig& ... .5-1.1l4l0"
====================================


In the meantime. Post your

Code: Select all

$ inxi -F
System:    Host: biker Kernel: 2.6.38-7.dmz.2-liquorix-686 i686 (32 bit) 
           Desktop Fluxbox 1.3.1 Distro: antiX-M11-base-686 Jayaben Desai 25 April 2011
Machine:   System: GATEWAY product: W3507 version: 500
           Mobo: Intel model: D102GGC2 version: AAD70214-201
           Bios: Intel version: GC11020M.15A.2010.2006.0817.0956 date: 08/17/2006
CPU:       Single core Intel Celeron D CPU (-UP-) cache: 512 KB flags: (lm nx sse sse2 sse3) clocked at 3200.167 MHz 
Graphics:  Card: ATI RC410 [Radeon Xpress 200] X.Org: 1.11.1 driver: radeon Resolution: 1024x768@85.0hz 
           GLX Renderer: Gallium 0.4 on ATI RC410 GLX Version: 2.1 Mesa 7.11
Audio:     Card: ATI IXP SB4x0 High Definition Audio Controller driver: HDA Intel Sound: ALSA ver: 1.0.23
Network:   Card: Realtek RTL-8139/8139C/8139C+ driver: 8139too 
           IF: eth0 state: down speed: 10 Mbps duplex: half mac: <filtered>
Drives:    HDD Total Size: 120.0GB (5.5% used) 1: /dev/sda ST3120213A 120.0GB 
Partition: ID: / size: 109G used: 6.2G (6%) fs: ext3 ID: swap-1 size: 2.17GB used: 0.00GB (0%) fs: swap 
Sensors:   System Temperatures: cpu: 49.9C mobo: 49.9C 
           Fan Speeds (in rpm): cpu: 2279 fan-2: 1111 fan-4: 0 
Info:      Processes: 81 Uptime: 15:50 Memory: 168.2/880.0MB Client: Shell inxi: 1.7.23
readout and have a looksee on enabling broadcom chip on


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://wiki.debian.org/wl#Wheezy"
linktext was:"http://wiki.debian.org/wl#Wheezy"
====================================


also post output of

Code: Select all

harry@biker:~$ ifconfig -a
bash: ifconfig: command not found
harry@biker:~$ sux
Password: 
root@biker:/home/harry# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:16:76:dd:65:f5  
          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:9 Base address:0x6000 

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:856 errors:0 dropped:0 overruns:0 frame:0
          TX packets:856 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:43792 (42.7 KiB)  TX bytes:43792 (42.7 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:e0:4c:5a:56:07  
          inet addr<filtered> Bcast:<filtered> Mask:255.255.255.0
          inet6 addr: <filtered> Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:152836 errors:0 dropped:0 overruns:0 frame:0
          TX packets:59970 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:106938625 (101.9 MiB)  TX bytes:9037141 (8.6 MiB)
to see if wlan0 shows up at all. Also in Wicd wireless preferences. Did you put in wireless interface like wlan0 which is what my wireless interface is identified as?

Howdy and Welcome to AntiX. __{{emoticon}}__
Posts: 5
Asmo
Joined: 25 Oct 2011
#3

Code: Select all

root@Absol:/home/amos# inxi -F
System:    Host Absol Kernel 2.6.36-1-mepis-smp i686 (32 bit) Distro antiX-M11-686 Jayaben Desai 01 May 2011
CPU:       Single core Intel Atom N270 (-HT-) cache 512 KB flags (nx sse sse2 sse3 ssse3) bmips 3191.86 
           Clock Speeds: (1) 800.00 MHz (2) 800.00 MHz
Graphics:  Card: Intel Mobile 945GME Express Integrated Graphics Controller bus-ID: 00:02.0 X.org 1.9.5 Res: 127x31 Gfx Data: N/A for root 
Audio:     Card Intel N10/ICH 7 Family High Definition Audio Controller driver HDA Intel bus-ID: 00:1b.0
           Sound: Advanced Linux Sound Architecture Version 1.0.23
Network:   Card-1 Broadcom BCM4312 802.11b/g LP-PHY driver b43-pci-bridge bus-ID: 03:00.0
           Card-2 Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller driver r8169 v: 2.3LK-NAPI port 2000 bus-ID: 04:00.0
Disks:     HDD Total Size: 3.8GB (72.8% used) 1: /dev/sda STEC_ATA_DISK_vS 3.8GB 
Partition: ID:/ size: 3.0G used: 2.6G (92%) fs: ext3 
Info:      Processes 109 Uptime 7 min Memory 86.0/491.6MB Runlevel 5 Client Shell inxi 1.4.95
And

Code: Select all

root@Absol:/home/amos# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:21:70:df:40:5a  
          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:40 Base address:0x6000 

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:1228 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1228 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:263865 (257.6 KiB)  TX bytes:263865 (257.6 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:23:08:4f:29:b3  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:362 (362.0 B)
to see if wlan0 shows up at all. Also in Wicd wireless preferences. Did you put in wireless interface like wlan0 which is what my wireless interface is identified as?
Yes, I did. Like I said, it can detect wifi networks just fine, but it's when I try to connect that I have problems.
Howdy and Welcome to AntiX.
Thank you for the warm welcome.
Posts: 4,164
rokytnji
Joined: 20 Feb 2009
#4
Yes, I did. Like I said, it can detect wifi networks just fine, but it's when I try to connect that I have problems.
My bad as I am wrenching on motors and responding to posts when taking a break.

Remember. I am not a broadcom expert, but I think the wl driver is what is required instead of driver b43-pci-bridge (take that statement with a grain of salt because I am broadcom ignorant). __{{emoticon}}__

Edit: In wicd preferences. Have you tried using dhclient only instead of automatic and use measure signal strenth in db to see if connection completes then as a experiment?

2nd Edit: Looking at inxi. Is this a Dell Mini? Because of Broadcom wireless and Intel Atom.
Posts: 117
buttcoffee
Joined: 20 Aug 2010
#5
You gotta use the wl driver.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://www.broadcom.com/support/802.11/linux_sta.php"
linktext was:"https://www.broadcom.com/support/802.11/linux_sta.php"
====================================


Just follow the link riky gave above for how to install it.

I have a bcm4312 P-PHY [14e4:4315] (rev 01) chip, I'm gathering you have the same. the b43 one break on debian for unknown reasons, at least they did for me.
Posts: 5
Asmo
Joined: 25 Oct 2011
#6
rokytnji wrote:Remember. I am not a broadcom expert, but I think the wl driver is what is required instead of driver b43-pci-bridge
buttcoffee wrote:You gotta use the wl driver.
I figured as much. I checked to see what Ubuntu (which I am booting from an external USB HDD) used, and it does indeed use wl, and it works without a problem. I'll mess around later and see if I can't get the wl driver working on Antix. Thank you for your help.
rokytnji wrote:Looking at inxi. Is this a Dell Mini? Because of Broadcom wireless and Intel Atom.
Yeah. It's a Dell Mini 9, which I think Dell discontinued relatively recently.
Posts: 5
Asmo
Joined: 25 Oct 2011
#7
Well,
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://wiki.debian.org/wl#Wheezy"
linktext was:"I followed the instructions rokytnji linked me"
====================================
(sans steps one and two, since I can't do them without wireless working, of course. I just got the packages from packages.debian.org on Ubuntu and manually dpkg'd them) and this happened:

Code: Select all

root@Absol:/media/disk/home/amos/Downloads# m-a a-i broadcom-sta
broadcom-sta, what is broadcom-sta?
I'm probably missing something ridiculously obvious, as I'm new to this whole thing and haven't touched module-assistant before in my life. What do?
Posts: 117
buttcoffee
Joined: 20 Aug 2010
#8
Sorry, i didn't realize there was a deb package for broadcom-sta
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://packages.debian.org/squeeze/broadcom-sta-source"
linktext was:"http://packages.debian.org/squeeze/broadcom-sta-source"
====================================
So, yeah, get that package, then try again

I haven't done it in over a year or so and I thought I used the one from broadcom's site, which i linked to earlier. My mistake.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://wiki.debian.org/wl#Wheezy"
linktext was:"http://wiki.debian.org/wl#Wheezy"
====================================
If you scroll down, you'll see a link for the package also.

If you wanna easily check which precise broadcom4312 you have, enter:

lspci -nn | grep 14e4

and it'll plop out something like this

Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] - that's mine.
Posts: 5
Asmo
Joined: 25 Oct 2011
#9

Code: Select all

root@Absol:/media/disk/home/amos/Downloads# dpkg -i broadcom-sta-source_5.60.48.36-2_all.deb
Selecting previously deselected package broadcom-sta-source.
(Reading database ... 73171 files and directories currently installed.)
Unpacking broadcom-sta-source (from broadcom-sta-source_5.60.48.36-2_all.deb) ...
dpkg: dependency problems prevent configuration of broadcom-sta-source:
 broadcom-sta-source depends on debhelper (>= 7); however:
  Package debhelper is not installed.
 broadcom-sta-source depends on quilt; however:
  Package quilt is not installed.
dpkg: error processing broadcom-sta-source (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 broadcom-sta-source
Ugh... I guess I have to manually fetch a few dependencies to get it to work.
buttcoffee wrote: If you wanna easily check which precise broadcom4312 you have, enter:

lspci -nn | grep 14e4

and it'll plop out something like this

Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] - that's mine.
Yeah, it was in my first post.
Posts: 28
alfred_e_newman
Joined: 16 Nov 2011
#10
Hi Asmo,

Not sure if you still have this issue?

I just tangled with the “Broadcom wireless monster” in AntiX. I have Broadcom 4318.

After trying some suggestions found on message boards .... I just had a hunch it was a “conflict" problem, and did the following:

- Went into Synaptic, and uninstalled ndiswrapper
- Went back to the Control Center, and ran Network Interfaces (ceni). Scanned for connection.

It worked!

Not sure if this is the greatest idea __{{emoticon}}__ But it worked, and do not notice any other “broken” functionality.

If this doesn’t work - you could also try running this command in terminal:

# ifconfig wlan0 up #(replace wlan0 with appropriate number)

Then try ceni again.

Hope this helps.
Posts: 6
wobo
Joined: 19 Dec 2011
#11
Broadcom BCM4312 802.11b/g LP-PHY (rev 01).
antiX-M11-686
Lenovo S10e (netbook)

Sorry for exhuming this thread but I have the same chip and setup

- I installed broadcom-sta-source_5.60.48.36-2_all.deb
- removed the b43 module with modprobe -r
- installed the wl module with modprobe

Code: Select all

lsmod |grep wl
wl  1937183  0
lib80211  2778  2 lib80211_crapt_tkip,wl
Now in ceni I see the device eth1 running with the wl driver, networks are found and connection is up.

Question: After reboot all is back to the unwanted configuration: b43 driver is loaded instead of wl.
How can I permanently remove the b43 module and activate the wl module - in short: make the working configuration permanent?
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#12
You could try blacklisting the b43 module in /etc/modprobe.d/blacklist.conf

Code: Select all

To blacklist these drivers and prevent them from loading in the future:
# echo"blacklist ssb" >> /etc/modprobe.d/blacklist.conf
# echo"blacklist bcma" >> /etc/modprobe.d/blacklist.conf
# echo"blacklist b43" >> /etc/modprobe.d/blacklist.conf

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.broadcom.com/docs/linux_sta/README.txt"
linktext was:"http://www.broadcom.com/docs/linux_sta/README.txt"
====================================
Posts: 6
wobo
Joined: 19 Dec 2011
#13
Thx, first I did the blacklist dance (which worked ok), then I read the whole README at broadcom.com. Either things are different here or whatever. Putting"modprobe wl" into rc.local does not do anything. syslog does not say anything related,"lsmod|grep wl" does not return anything.

Now I did"modprobe wl" manually and after that lsmod showed wl and lib80211 as present. But opening ceni the device is not there.

<rant> Ignore if you want:
Hmm, I've been using Linux for more than 14 years, being quite active with DLD, Debian, Red Hat, Mandriva, Mageia. For installing a driver lately I am used to download a dkms-<drivername> rpm and reboot, the module is built and activated automatically, either directly after installation or at boot-up (even with dkms-broadcom-wl on this machine). So I am quite new with these experiences here. Of course it is interesting to go through all these ancient moves again, things I have been using 12 years ago ... but I've been trying for almost 2 days now to establish a working wifi connection at boot-up, read several howtos and documents, read several forum posts and also wrote one (after eventually received the account activation after several hours) - all this without achieving much.
</rant>
anticapitalista
Posts: 5,955
Site Admin
Joined: 11 Sep 2007
#14
Not knowing which howto's you have tried, here is a link to LMDE one.


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://community.linuxmint.com/tutorial/view/218"
linktext was:"http://community.linuxmint.com/tutorial/view/218"
====================================
Posts: 6
wobo
Joined: 19 Dec 2011
#15
I followed the Debian howto (link has been posted earlier in this thread) which is the source for the LMDE one.

As I wrote earlier:
- I installed broadcom-sta-source_5.60.48.36-2_all.deb
- removed the b43 module with modprobe -r
- installed the wl module with modprobe

Code: Select all

lsmod |grep wl
wl  1937183  0
lib80211  2778  2 lib80211_crypt_tkip,wl
Now in ceni I see the device eth1 running with the wl driver, networks are found and connection is up.
This was ok so far.

Now since I blacklisted b43 (in /etc/modprobe.d/blacklist.conf as suggested by you) and put"modprobe wl" into rc.local the wifi device is not available anymore. When I do"modprobe wl" I get an error message:

Code: Select all

FATAL: Could not read 'lib/modules/2.6.36-1-mepis-smp/kernel/drivers/net//wireless/wl.ko: no such file or directory
A search shows wl.ko in lib/modules/2.6.36-1-mepis-smp/misc with the file date of Dec 28 2010

All this is very confusing.