[SOLVED] Problem with wifi setup on slackware64-current

bogzab · 06-08-2015, 02:09 PM

Duplicated message - see text below - edited down to this note...

bogzab · 06-08-2015, 02:28 PM

Duplicated message - see text below - edited down to this note...

bogzab · 06-08-2015, 02:32 PM

Tried :
1. setting the region correctly (Wales is part of GB - so far!)
2. Disabling 11n
3. Disabling power management in the driver

None of these steps seemed to help - alone or in combination.

In terms of re-installing software I have only re-installed the firmware code but I will have a go at the other suggested re-installs.

Meanwhile here are some of the relevant startup messages I see - not sure if there is a clue somewhere here or whether these are just re-stating of what I already know (that the PC never really connects to the router). btw How come it connects for the purposes ofthe iwscan list command?

About three-quarters of the way through startup:

Code:

eth0: adding address fe80::a750::ec54::188a::b559
eth0: if_addaddress6: operation not supported
eth0: waiting for carrier
eth0: timed out
wlan0: adding address fe80::e885::d964::46fe::6210 
wlan0: if_addaddress6: operation not supported
wlan0: waiting for carrier
wlan0: timed out
dhcpcd exited
starting internet superserver daemon

Then after launcing various /etc/r.cd services:

Code:

dhcpcd-6.8.1 starting
dev: loaded udev
eth0: adding address fe80::a750::ec54::188a::b559
eth0: pltime infinity, vltime infinity
if_addaddress6: Permission denied
wlan0: adding address fe80::e885::d964::46fe::6210
wlan0: pltime infinity, vltime infinity
if_addaddress6: Permission denied
eth0: executing /lib/dhcpcd/dhcpcd-run-hooks PREINIT
eth0: executing /lib/dhcpcd/dhcpcd-run-hooks NOCARRIER
wlan0: executing /lib/dhcpcd/dhcpcd-run-hooks PREINIT
wlan0: executing /lib/dhcpcd/dhcpcd-run-hooks NOCARRIER
no interfaces have a carrier

Note that the above messages were generated during a boot-up when the ethernet cable was not plugged in - so no carrier for any interface. When I later connected the ethernet cable, network manager did not seem to be able to connect to the eth0 interface. To do so I had to re-start dhcpcd (dhcpcd -x followed by dhcpcd -d). So wired behaviour also looks a little odd - should not network manager interact with a dhcpcd daemon without requiring re-start?

bassmadrigal · 06-08-2015, 02:45 PM

You could try disabling ipv6 (this used to be a common issue, but increasingly it seems to not be needed as much).

Code:

rmmod ipv6

If you're able to connect after this, you would need to blacklist that module from being used when booting (there's lots of instructions on how to blacklist modules on Google).

JackHair · 06-08-2015, 10:52 PM

I've had problems getting my wifi to work on Current too. For me the solution was to use dhclient instead of dhcpcd. Without Networkmanager just eth0 worked fine with dhcpcd. But when combined with Networkmanager/wifi dhcpcd gave me nothing but problems.

Code:

Open /etc/NetworkManager/NetworkManager.conf
and change dhcpcd to dhclient.

[main]
plugins=keyfile
dhcp=dhclient

bogzab · 06-09-2015, 01:19 AM

@JackHair:
Thanks for that - this look like a solution at least when using Network Manager - both eth0 and wlan0 now connect and disconnect in response to NM commands. Seen wireless internet connectivity on this laptop for the first time!

Presumably there are ways of re-configuring the startup scripts so that dhclient is used during startup rather than dhcpcd which seems to be incompatible with the intel driver/firmware as it is currently delivered by -current.

@bassmadrigal:
I had already tried blacklisting ipv6 and that did not help, so I think the solution of using the other DHCP client is all I need.

JackHair · 06-09-2015, 01:29 AM

Quote:

Originally Posted by bogzab

@JackHair:
Thanks for that - this look like a solution at least when using Network Manager - both eth0 and wlan0 now connect and disconnect in response to NM commands. Seen wireless internet connectivity on this laptop for the first time!

Presumably there are ways of re-configuring the startup scripts so that dhclient is used during startup rather than dhcpcd which seems to be incompatible with the intel driver/firmware as it is currently delivered by -current.

Networkmanager is supposed to be used with dhcp set to no in /etc/rc.d/rc.inet1.conf. You can however assign static IP's in /etc/rc.d/rc.inet1.conf which Networkmanager has no problem with.