SliTaz SliTaz Forum

You are not logged in.

#1 2013-02-28 13:24:41

emgi
Member
Registered: 2012-12-17
Posts: 127

WLAN config not persistant.

My WLAN config is working, but only after manual adjustments.

When starting the slitaz panel > hardware > kernel modules I can see driver 'b43' was loaded and not 'wl'.

Then I need to go to console and do the following:

root@slaptop:/home/leo# modprobe -r b43

root@slaptop:/home/leo# modprobe wl

root@slaptop:/home/leo# /etc/init.d/network.sh restart

Stopping all interfaces

ifconfig: SIOCGIFFLAGS: No such device

Killing all daemons

killall: udhcpc: no process killed

wlan0     No such device

wlan0 is not a wifi interface, changing it.

Configuring eth1...                                                  [ OK ]

Starting wpa_supplicant for WPA-PSK...

Starting udhcpc client on: eth1...

Selected interface 'eth1'

root@slaptop:/home/leo#

For some reason, the system keeps using the incorrect module b43.

I already tried running depmod (with no options) but to no avail.

How can I make this change permanent?

/emgi

Offline

#2 2013-02-28 16:27:15

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: WLAN config not persistant.

b43 and ssb conflict with wl because they are drivers for the same wifi chipsets.

Normally you could use a blacklist to prevent conflicting modules from autoloading.

Blacklisting doesn't reliably work in Slitaz.

b43 is owned by linux-wireless which has other critical modules so it can't be removed with tazpkg

You could move or delete b43 and run [c]# depmod -a[/c]

The easiest solution in my opinion is remove broadcom-wl and install b43 firmware so you can use b43.
[*][c]# tazpkg remove broadcom-wl[/c]

[*][c]# tazpkg install[/c] b43-firmware-4.150.10.5.tazpkg

b43 module must be loaded after firmware is installed
[*]Reboot or:

[c]# modprobe -r b43[/c]

[c]# modprobe b43[/c]

[c]ls /sys/class/net[/c]

b43 registers as wlan0
[*]Configure /etc/network.conf

[*]Reboot or restart networking

[c]# /etc/init.d/network.sh restart[/c]

Offline

#3 2013-02-28 18:12:50

emgi
Member
Registered: 2012-12-17
Posts: 127

Re: WLAN config not persistant.

Almost there but something is still not working. First of all, midori doesn't download the above file from this location. I had to use another machine to get it. ;-(

Then I removed the broadcom-wl and a slightly newer version of b43-firmware (5.100.xxx) and installed

the version I just downloaded.

The result is this:

root@slaptop:/home/leo# lsmod | grep b43

b43                   132593  0

mac80211              145388  1 b43

cfg80211               99896  2 b43,mac80211

ssb                    24436  1 b43

root@slaptop:/home/leo# lsmod | grep wl

root@slaptop:/home/leo# ls /sys/class/net/

dummy0  eth0    lo      wlan0

root@slaptop:/home/leo# cat /etc/network.conf

# /etc/network.conf: SliTaz system wide networking configuration.

# Config file used by: /etc/init.d/network.sh

#

# Set default interface.

INTERFACE="wlan0"

# Dynamic IP address.

# Enable/disable DHCP client at boot time.

DHCP="yes"

# Static IP address.

# Enable/disable static IP at boot time.

STATIC="no"

# Set IP address and netmask for a static IP.

IP="192.168.0.6"

NETMASK="255.255.255.0"

# Set route gateway for a static IP.

GATEWAY="192.168.0.1"

# Set DNS server for a static IP.

DNS_SERVER="192.168.0.1"

# Wifi connection.

# Enable/disable wireless connection at boot time.

WIFI="yes"

# Wifi interface (iwconfig) and ESSID.

WIFI_INTERFACE="wlan0"

WIFI_ESSID="boshut2"

WIFI_MODE="managed"

WIFI_KEY="????"

WIFI_KEY_TYPE="WPA"

WPA_DRIVER=""

WIFI_CHANNEL=""

WIFI_IWCONFIG_ARGS=""

root@slaptop:/home/leo# /etc/init.d/network.sh restart

Stopping all interfaces

Killing all daemons

Shutting down wifi card

ifconfig: SIOCSIFFLAGS: Operation not possible due to RF-kill

Configuring wlan0...                                                 [ OK ]

Starting wpa_supplicant for WPA-PSK...

Starting udhcpc client on: wlan0...

Selected interface 'eth1'

Failed to connect to wpa_supplicant - wpa_ctrl_open: Connection refused

root@slaptop:/home/leo#

I can see the wireless networks in the wifi configuration tool but after selecting mine and entering the password,  nothing happens. My wlan interface :

root@slaptop:/home/leo# ifconfig wlan0

wlan0     Link encap:Ethernet  HWaddr 00:14:A5:E9:7F:46

          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)

root@slaptop:/home/leo# udhcpc -i wlan0

udhcpc (v1.18.4) started

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

Sending discover...

root@slaptop:/home/leo#

EDIT: This is also not OK I presume:

root@slaptop:/home/leo# tazpkg remove b43-firmware-4.150.10.5.tazpkg

b43-firmware-4.150.10.5 is not installed.

However, the b43 module IS installed:

root@slaptop:/home/leo# lsmod | grep b43

b43                   132593  0

mac80211              145388  1 b43

cfg80211               99896  2 b43,mac80211

ssb                    24436  1 b43

root@slaptop:/home/leo#

I did the install using --forced but no change.

/emgi

Offline

#4 2013-02-28 19:20:09

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: WLAN config not persistant.

I just downloaded the b43-firmware from mediafire with Slitaz-4.0 midori-0.4.4

I don't see in your reply where you unload/load b43 module after you install the b43-firmware.

It doesn't appear you removed broadcom-wl, only checked that wl wasn't loaded.

[c]# /etc/init.d/network.sh restart[/c]

This is a sign of the problem=>  Selected interface 'eth1'

Then you remove the b43-firmware

I think we have a communication problem @_@
[*]Reinstall b43-firmware open a 2nd terminal

[*]Terminal2 will monitor kernel messages:

[c]tail -f /var/log/messages[/c]
[*]Terminal 1 unload/load b43:

[c]# modprobe -r b43[/c]

[c]# modprobe b43[/c]
[*]Post any errors in terminal 2 about b43 firmware loading ,etc.

Offline

#5 2013-02-28 20:53:39

emgi
Member
Registered: 2012-12-17
Posts: 127

Re: WLAN config not persistant.

My midori version is 0.4.6.

When doing as you request, I get a lot of output upon unloading: (I did the unload at  21:45:12)

leo@slaptop:~$ tail -f /var/log/messages

Feb 28 21:42:46 (none) user.notice error binding udev control socket

Feb 28 21:42:46 (none) daemon.err udevd[2307]: error binding udev control socket

Feb 28 21:42:46 (none) daemon.err udevd[2309]: bind failed: Address already in use

Feb 28 21:42:46 (none) user.notice error binding udev control socket

Feb 28 21:42:46 (none) daemon.err udevd[2309]: error binding udev control socket

Feb 28 21:42:46 (none) daemon.err udevd[2308]: bind failed: Address already in use

Feb 28 21:42:46 (none) user.notice error binding udev control socket

Feb 28 21:42:46 (none) daemon.err udevd[2308]: error binding udev control socket

Feb 28 21:42:48 (none) user.info kernel: tg3 0000:02:0e.0: eth0: Link is up at 100 Mbps, full duplex

Feb 28 21:42:48 (none) user.info kernel: tg3 0000:02:0e.0: eth0: Flow control is off for TX and off for RX

Feb 28 21:45:12 (none) daemon.err udevd[2346]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2346]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2347]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2347]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2348]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2348]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2349]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2349]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2351]: bind failed: Address already in use

Feb 28 21:45:12 (none) daemon.err udevd[2350]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2350]: error binding udev control socket

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2351]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2352]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2352]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2353]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2353]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2354]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2355]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2355]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2354]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2356]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2356]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2358]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2358]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2359]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2359]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2360]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2360]: error binding udev control socket

Feb 28 21:45:12 (none) user.info kernel: b43-pci-bridge 0000:08:00.0: PCI INT A disabled

Feb 28 21:45:12 (none) daemon.err udevd[2361]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2361]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2363]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2363]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2362]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2362]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2364]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2364]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2365]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2365]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2366]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2366]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2367]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2367]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2368]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2368]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2369]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2369]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2370]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2370]: error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2371]: bind failed: Address already in use

Feb 28 21:45:12 (none) user.notice error binding udev control socket

Feb 28 21:45:12 (none) daemon.err udevd[2371]: error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2374]: bind failed: Address already in use

Feb 28 21:45:28 (none) daemon.err udevd[2375]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2375]: error binding udev control socket

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2374]: error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2376]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2376]: error binding udev control socket

Feb 28 21:45:28 (none) user.info kernel: cfg80211: Calling CRDA to update world regulatory domain

Feb 28 21:45:28 (none) daemon.err udevd[2378]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2378]: error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2379]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2379]: error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2381]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2381]: error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2380]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2380]: error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2386]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2386]: error binding udev control socket

Feb 28 21:45:28 (none) user.info kernel: b43-pci-bridge 0000:08:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16

Feb 28 21:45:28 (none) user.debug kernel: b43-pci-bridge 0000:08:00.0: setting latency timer to 64

Feb 28 21:45:28 (none) daemon.err udevd[2389]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2389]: error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2388]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2388]: error binding udev control socket

Feb 28 21:45:28 (none) user.debug kernel: ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x11, vendor 0x4243)

Feb 28 21:45:28 (none) user.debug kernel: ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0A, vendor 0x4243)

Feb 28 21:45:28 (none) user.debug kernel: ssb: Core 2 found: USB 1.1 Host (cc 0x817, rev 0x03, vendor 0x4243)

Feb 28 21:45:28 (none) user.debug kernel: ssb: Core 3 found: PCI-E (cc 0x820, rev 0x01, vendor 0x4243)

Feb 28 21:45:28 (none) user.info kernel: ssb: Sonics Silicon Backplane found on PCI device 0000:08:00.0

Feb 28 21:45:28 (none) daemon.err udevd[2390]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2390]: error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2391]: bind failed: Address already in use

Feb 28 21:45:28 (none) daemon.err udevd[2394]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2394]: error binding udev control socket

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2391]: error binding udev control socket

Feb 28 21:45:28 (none) user.info kernel: b43-phy0: Broadcom 4311 WLAN found (core revision 10)

Feb 28 21:45:28 (none) daemon.err udevd[2398]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2398]: error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2399]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2399]: error binding udev control socket

Feb 28 21:45:28 (none) user.debug kernel: ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'

Feb 28 21:45:28 (none) daemon.err udevd[2400]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2400]: error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2401]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2401]: error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2404]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2404]: error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2405]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2405]: error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2406]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2406]: error binding udev control socket

Feb 28 21:45:28 (none) user.debug kernel: Registered led device: b43-phy0::tx

Feb 28 21:45:28 (none) daemon.err udevd[2409]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2409]: error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2408]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2408]: error binding udev control socket

Feb 28 21:45:28 (none) user.debug kernel: Registered led device: b43-phy0::rx

Feb 28 21:45:28 (none) daemon.err udevd[2407]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2407]: error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2410]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2410]: error binding udev control socket

Feb 28 21:45:28 (none) user.debug kernel: Registered led device: b43-phy0::radio

Feb 28 21:45:28 (none) daemon.err udevd[2412]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2412]: error binding udev control socket

Feb 28 21:45:28 (none) user.info kernel: Broadcom 43xx driver loaded [ Features: PL, Firmware-ID: FW13 ]

Feb 28 21:45:28 (none) daemon.err udevd[2413]: bind failed: Address already in use

Feb 28 21:45:28 (none) user.notice error binding udev control socket

Feb 28 21:45:28 (none) daemon.err udevd[2413]: error binding udev control socket

I repeated the procedure several times, also tried a reboot. The results look the same.

Thnx for your time spent on this.

/emgi

Offline

#6 2013-03-01 18:47:59

emgi
Member
Registered: 2012-12-17
Posts: 127

Re: WLAN config not persistant.

echo "blacklist b43" >> /etc/modprobe.d/blacklist  resulted in a completely non-working wireless meaning I wasn't able to get it running by unloading b43 and loading wl instead.

I think I found a problem though. When checking my latest boot.log it contained the following:

Mar  1 19:30:04 (none) user.err kernel: b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found

Mar  1 19:30:04 (none) user.err kernel: b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found

Mar  1 19:30:04 (none) user.err kernel: b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.

Unfortunately I have already done this twice. The first time I loaded the version which is intended for >= 3.2 kernels. I discovered that mistake yesterday and downloaded the version for "older kernels" (broadcom-wl-5.10.56.27.3). This didn't solve my problem but the b43 driver appeared to load without any errors.

Now the message is back and I'm unsure how to get the proper firmware.

The only difference is the version of bw-cutter. The document states 0.17, the one I installed from the repository is 0.15. Could that really be the issue?

Alternatively, /lib/firmware/ may not be the proper destination.(?)

/emgi

Offline

#7 2013-03-01 20:33:33

emgi
Member
Registered: 2012-12-17
Posts: 127

Re: WLAN config not persistant.

Resolved!

What I did after discovering the kernel messages about the missing firmware was this:

delete the broadcom-wl.tazpkg

delete the b43-firmware-4.150.10.5.tazpkg (!)

re-install the firmware broadcom-wl-5.10.56.27.3_mipsel.tar.bz2 to /lib/firmware/ as described in: http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware

re-install b43-firmware-4.150.10.5.tazpkg

Now my wireless works and keeps working after a reboot.

Thnx to mojo for his 100% correct hints.

/emgi

Offline

#8 2013-03-04 20:17:11

Barocco
Member
Registered: 2013-03-04
Posts: 3

Re: WLAN config not persistant.

That sorted my wireless problem out as well, cheers

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.59 MiB (Peak: 1.77 MiB) ]