Porteus

Hello everyone, my first post here. After downloading version 1.2 a couple of days ago,
everything works fine except network manager....no networks found, and this is very strange
because I'm writing this in Porteus from a Starbucks coffee shop and the wifi connection is
very strong here. In order to connect, I stopped the network service and connected manually
with iwconfig and dhcpcd. However, even this way, the connection comes up but doesn't last
long and I end up having to manually start the connection again every couple of minutes or so.
This problem is inherent with this installation of Porteus...I tried connecting a few minutes
ago from my other install of Slax 6.1.2 and it works just fine, both with wicd and iwconfig/dhcpcd
manually.
Your help will be much appreciated. Thanks.

my psinfo:

02:06.0 Network controller [0280]: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller [14e4:4320] (rev 03)
Subsystem: Hewlett-Packard Company Broadcom 802.11b/g WLAN [103c:12f8]
Kernel driver in use: b43-pci-bridge
Kernel modules: ssb

===== LOGS INFO =====
dmesg | tail

[ 8547.174605] wlan0: deauthenticated from **************** (Reason: 2)
[ 8547.178656] cfg80211: Calling CRDA to update world regulatory domain
[ 9303.232119] wlan0: authenticate with ****************
[ 9303.241194] wlan0: send auth to **************** (try 1/3)
[ 9303.242787] wlan0: authenticated
[ 9303.244030] wlan0: associate with **************** (try 1/3)
[ 9303.245965] wlan0: RX AssocResp from **************** (capab=0x401 status=0 aid=156)
[ 9303.245970] wlan0: associated


cat /var/log/messages | tail

Jan 2 15:50:49 (none) avahi-daemon[1651]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.5.119.
Jan 2 15:50:49 (none) avahi-daemon[1651]: Interface wlan0.IPv4 no longer relevant for mDNS.
Jan 2 15:50:49 (none) kernel: [ 8547.178656] cfg80211: Calling CRDA to update world regulatory domain
Jan 2 16:03:25 (none) dhcpcd[2222]: wlan0: carrier acquired
Jan 2 16:03:25 (none) dhcpcd[2222]: wlan0: rebinding lease of 192.168.5.119
Jan 2 16:03:25 (none) dhcpcd[2222]: wlan0: acknowledged 192.168.5.119
Jan 2 16:03:25 (none) dhcpcd[2222]: wlan0: leased 192.168.5.119 for 3600 seconds
Jan 2 16:03:25 (none) avahi-daemon[1651]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.5.119.
Jan 2 16:03:25 (none) avahi-daemon[1651]: New relevant interface wlan0.IPv4 for mDNS.
Jan 2 16:03:25 (none) avahi-daemon[1651]: Registering new address record for 192.168.5.119 on wlan0.IPv4.

It seems NetworkManager is acting on your connection by applying some parameters which appears to be wrong and at end this appears to disconnects you from the network after the end of the lease. It just doesn't like you wanted because the system doesn't renew the lease as all others.

Thanks, but what can I do to make it work? Any ideas on how to dig a little deeper and find out to do it?
Could it be related to the fact that I have changed my hostname to something different than Porteus?
How do I go about it?

I don't think the fact you changed the hostname has the made the problem. It's (must be confirmed) related NetworkManager which doesn't renew the lease.

hi claude,

please upload whole /var/log/messages to pastebin.com and link here for review,
thanks

@fanthom

http://pastebin.com/FmYeNVbi

Thanks.

@fanthom

What you'll see in the posted /var/log/messages is this: I booted Porteus anew. Network Manager of course
did not work. Then in order to connect to internet, I stopped NM and killed the two nm-applet and
nm-applet.sh processes and removed the dhcpcd pid files from /var/run so as to be able to start the internet connection manually with iwconfig and dhcpcd. However, even so, the connection is not stable, it often
falls and I have to keep entering the wifi essid with iwconfig in order to reconnect each time.
Thanks for your help.

EDIT: could the fact that I have restricted access to 127.0.0.1 only via /etc hosts.allow, hosts.deny
and login.access have anything to do with it? These are the only changes I have made, besides changing
the hostname in /etc/HOSTNAME, /etc/hosts and /etc/NetworkManager/NetworkManager.conf

@claude
we are using opensource broadcom firmware (so we can ship it without the fear) which could be the reason of instability. slax-6.1.2 shipped restricted firmware (despite of fact that it's redistribution is not allowed) which i assume works better.

please follow this HOWTO to extract the firmware from broadcom proprietary driver:
http://linuxwireless.org/en/users/Drivers/b43#firmware

make sure you extract the firmware from version 3.130.20.0 of Broadcom's proprietary driver as this is the right one for your chipset (supported by b43legacy driver)

let us know if that helped.

@Fanthom

Thank you so much, it now works like a charm!
The only thing is that I had to use the firmware for driver b43 (not b43-legacy) since I have a
BCM4306 ver3 (not ver2). Placed the produced firmware in rootcopy and of course
put a line in /etc/rc.d/rc.local to remove /lib/firmware/b43-open at bootup.
Works great!!!

Don't forgot add [Solved] in your initial post