Network appears, but refuses to connect

Glahardt · #1 (**permalink**) 24-Aug-2009, 05:49

HP Mini 2140 here.

So I finally got madwifi to work and my network card(BCM4312) finally gets a device name and appears on Knetwork Manager, but it still would not connect. At first it would be in "ip configuration" for about 30 seconds before going into "disconnected" when prompted to connect, but now the configuration icon appears for less than a second. I'm still looking around for solutions, but I really don't know what to do at the time being.
I do believe the connection is not encrypted, access code is not needed.

/sbin/ifconfig gave me this.

Code:

wlan0     Link encap:Ethernet  HWaddr 00:21:00:F8:65:91
          inet6 addr: fe80::221:ff:fef8:6591/64 Scope:Link
          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:16

/usr/sbin/iwconfig gave me this.

Code:

lo        no wireless extensions.

eth0      no wireless extensions.

wlan0     IEEE 802.11  Access Point: Not-Associated

/usr/sbin/iwlist scan tells me that "Interface doesn't support scanning.

lwfinger · #2 (**permalink**) 24-Aug-2009, 07:43

Glahardt wrote:
> HP Mini 2140 here.
>
> So I finally got madwifi to work and my network card(BCM4312) finally
> gets a device name and appears on Knetwork Manager, but it still would
> not connect.

What does madwifi have to do with a BCM4312?

If you run the command '/sbin/lspci -nnv | grep 14e4', does it
show "14e4:4315" or "14e4:4312"? If the former, then you need the
Broadcom-wl package from Akolleth's repository. If the latter, you
need to install the bcm43xx firmware.

Glahardt · #3 (**permalink**) 24-Aug-2009, 14:29

It shows 14e4:4315.
I've installed the Broadcom-wl package, nothing happens, no difference at all. I've tried getting bcm43xx firmware as well, no difference.

lwfinger · #4 (**permalink**) 24-Aug-2009, 15:37

Glahardt wrote:
> It shows 14e4:4315.
> I've installed the Broadcom-wl package, nothing happens, no difference
> at all. I've tried getting bcm43xx firmware as well, no difference.

The bcm43xx firmware does you absolutely no good. You need to
blacklist ssb and b43. Then wl will load. To test this, enter the
following commands:

sudo /sbin/modprobe -rv b43
sudo /sbin/modprobe -v wl

If the Broadcom package is installed correctly, you should see the wl
module loading with the second command.

Just for the record, the b43 group is now working on a driver for the
4315 units. At the moment, it can receive on channels 6-7, but the
transmitter is not working yet. My guess is that the driver will be
working by 2.6.33.

Glahardt · #5 (**permalink**) 24-Aug-2009, 18:36

Only a line of output appeared after the second command, can't remember what it is because wlan0 disappeared from Knetwork manager again, I reseted the comp without copying the output. Anyway, after the reset, wlan0 came back but appears to be exactly the same.

lwfinger · #6 (**permalink**) 24-Aug-2009, 20:25

Glahardt wrote:
> Only a line of output appeared after the second command, can't remember
> what it is because wlan0 disappeared from Knetwork manager again, I
> reseted the comp without copying the output. Anyway, after the reset,
> wlan0 came back but appears to be exactly the same.

Until you blacklist the ssb and b43 modules, your system will return
to the original form after every reboot.

Incidentally, you should write down any massages. If we are to spend
time helping you, you need to provide the best info you can.

I could tell you how to blacklist a module, but I want you to do the
research.

Glahardt · #7 (**permalink**) 25-Aug-2009, 06:42

Tried to chance the blacklist file using a text editor, it won't let me save to to already existing blacklist.local.
I have no idea how to use the root privileges in anywhere else other than in Konsole.

deltaflyer44 · #8 (**permalink**) 25-Aug-2009, 12:47

Depending on your DE,you could type,in a console

kdesu kate Name_of_file_to_edit
gnomesu gedit Name_of_file_to_edit

Just add root's password when asked

Andy

Glahardt · #9 (**permalink**) 25-Aug-2009, 13:35

Already did it and edited the blacklist, thanks.
But it still doesn't work. I'm going to try resetting it a few more times, but I'm not optimistic about this.

lwfinger · #10 (**permalink**) 25-Aug-2009, 14:57

Glahardt wrote:
> Already did it and edited the blacklist, thanks.
> But it still doesn't work. I'm going to try resetting it a few more
> times, but I'm not optimistic about this.

Check the output of 'lsmod | grep ssb'. That command should return
nothing. Then 'lsmod | wl'.

Have you configured the interface?

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode