[SOLVED] Switching from udev to eudev

bassmadrigal · 11-23-2015, 12:13 PM

Quote:

Originally Posted by pchristy

I've created an "ath9k.conf" file in /etc/modprobe.d to set the correct regulatory domain for my wifi card. If I boot my "home-rolled" kernel (4.3.0), there are no problems. If I boot the slackware generic kernel in multi-user mode (3), the regional code does not get set, and defaults to "00". During the boot, I see several calls like this:

Code:

cfg80211: Calling CRDA to update world regulatory domain

Have you checked the config differences between your custom kernel and the stock generic kernel? Maybe it is set differently in that kernel and the config will shed some light...

pchristy · 11-23-2015, 12:26 PM

There are probably an awful lot of differences! The laptop is not overly powerful, so I tend to strip out everything that seems unnecessary! If in doubt, I'll leave it in, but my basic config has worked fine all the time I've used it.

I guess there must be some method (diff?) of automating this. But even if I automate the generation of a diff file, there's going to be a lot to trawl through!

One other issue I've just hit is that Eric's (AlienBob) usb2img2disk.sh script doesn't work on a eudev system. It looks as if the format of the /sys/block/... that he uses to check for the right usb device has changed under eudev. Luckily, I still have an old machine running 14.1, so managed to produce an sd card on that.....

Its getting late in the evening here now, but I'll investigate diff-ing the config files tomorrow.

EDIT: One other thing I'll try is disabling the ath9k.conf file temporarily, and see if that makes a difference.

--
Pete

bassmadrigal · 11-23-2015, 12:51 PM

Quote:

Originally Posted by pchristy

There are probably an awful lot of differences! The laptop is not overly powerful, so I tend to strip out everything that seems unnecessary! If in doubt, I'll leave it in, but my basic config has worked fine all the time I've used it.

I guess there must be some method (diff?) of automating this. But even if I automate the generation of a diff file, there's going to be a lot to trawl through!

You can try using a grep for "ATH" (maybe a grep -i, so case won't matter).

As an alternative, if you have KDE installed, it has a program called kompare, which gives you a better graphical output of the changes, and it likely supports a "find" to help you find ATH related config options.

Didier Spaier · 11-23-2015, 01:13 PM

/usr/src/linux/scripts/diffconfig config1 config2 > /tmp/config12.diff
could also help.

I learned that recently reading a post from Pat

pchristy · 11-23-2015, 01:15 PM

OK, diff between the generic kernal and mine (4.3.0):

Code:

diff /boot/config-generic-4.1.13 /boot/config-4.3.0 | grep -i ath 
< CONFIG_MD_MULTIPATH=y
> # CONFIG_MD_MULTIPATH is not set
< CONFIG_DM_MULTIPATH=m
< CONFIG_DM_MULTIPATH_QL=m
< CONFIG_DM_MULTIPATH_ST=m
> # CONFIG_DM_MULTIPATH is not set
< CONFIG_ATH5K=m
< # CONFIG_ATH5K_DEBUG is not set
< # CONFIG_ATH5K_TRACER is not set
< CONFIG_ATH5K_PCI=y
> # CONFIG_ATH5K is not set
> # CONFIG_ATH5K_PCI is not set
< CONFIG_ATH6KL=m
< CONFIG_ATH6KL_SDIO=m
< CONFIG_ATH6KL_USB=m
< # CONFIG_ATH6KL_DEBUG is not set
< # CONFIG_ATH6KL_TRACING is not set
< CONFIG_ATH10K=m
< CONFIG_ATH10K_PCI=m
< # CONFIG_ATH10K_DEBUG is not set
< CONFIG_ATH10K_DEBUGFS=y
< # CONFIG_ATH10K_TRACING is not set
> # CONFIG_ATH6KL is not set
> # CONFIG_ATH10K is not set
< # CONFIG_INFINIBAND_IPATH is not set

I don't think I've disabled anything essential there. And in any case, my kernel works fine!

Here's what I've set for my chipset:

Code:

cat /boot/config-4.3.0 | grep -i ath9
CONFIG_ATH9K_HW=m
CONFIG_ATH9K_COMMON=m
CONFIG_ATH9K_BTCOEX_SUPPORT=y
CONFIG_ATH9K=m
CONFIG_ATH9K_PCI=y
# CONFIG_ATH9K_AHB is not set
# CONFIG_ATH9K_DEBUGFS is not set
# CONFIG_ATH9K_DYNACK is not set
CONFIG_ATH9K_WOW=y
CONFIG_ATH9K_RFKILL=y
CONFIG_ATH9K_CHANNEL_CONTEXT=y
CONFIG_ATH9K_PCOEM=y
CONFIG_ATH9K_HTC=m
# CONFIG_ATH9K_HTC_DEBUGFS is not set

I get the feeling its more likely to be in the cfg80211 area. I'll go have a look there....

--
Pete

pchristy · 11-23-2015, 01:16 PM

Crossed in the post, Didier!

But thanks! That's a good tip!

--
Pete

pchristy · 11-23-2015, 01:21 PM

This doesn't mean much to me, but nothing stands out as obvious:

Code:

diff /boot/config-generic-4.1.13 /boot/config-4.3.0 | grep -i 80211
< CONFIG_CFG80211_WEXT=y
< CONFIG_CFG80211_WEXT_EXPORT=y
> # CONFIG_CFG80211_WEXT is not set
< CONFIG_LIB80211_CRYPT_WEP=m
< CONFIG_LIB80211_CRYPT_CCMP=m
< CONFIG_LIB80211_CRYPT_TKIP=m
> CONFIG_MAC80211_STA_HASH_MAX_SIZE=0

Does that indicate anything to anyone?

And now I really must go and attend to family duties.....!

--
Pete

pchristy · 11-24-2015, 02:46 AM

I tried disabling the ath9k.conf file this morning, and that fixed the "problem"! Without that file in /etc/modprobe.d the generic kernel boots just fine, without continually looping through cfg80211. However, one other interesting tidbit remains: The hostname defaults to "darkstar" - despite being set in both HOSTNAME and /etc/Networmanager/networkmanager.conf . I know its set in the kernel, so for some reason, under the new eudev, it appears that some of the wireless network configuration is being ignored.

Of course, it may be being ignored in my home-rolled kernel as well, as I set the hostname to my requirements when I configured it!

A minor issue, but perhaps one worth mentioning, in case anyone else is having similar issues.....

--
Pete

bassmadrigal · 11-24-2015, 07:04 AM

Quote:

Originally Posted by pchristy

The first isn't directly related to the eudev upgrade, but re-appeared as a result of the "slackpkg --upgrade-all". On both my desktop and, more importantly my laptop, I've always received a complaint from kde that it couldn't find a power management back-end since upower was upgraded to 0.9.23 some time ago. The solution has been simply to recompile upower from the source package on my machine. I don't have to change anything in the slackbuild - simply recompiling it provides a complete fix! Without this fix, I get no battery monitoring on my laptop, and kde error messages on both machines when logging in. Of course, my upgrade got over-written during the update, and the error complaints re-appeared. Re-compiling has once again provided an instant fix.

Hopefully this fixes your upower issues

Code:

Tue Nov 24 03:31:43 UTC 2015
a/upower-0.9.23-x86_64-2.txz: Rebuilt.

pchristy · 11-24-2015, 09:54 AM

Yep! That fixed it!

That problem has been plaguing me ever since upower was upgraded to 23 from 21! Haven't had a look yet to see what's changed, but since it always worked fine without any changes after a recompile, perhaps the original package was faulty? Very unusual in Slackware, that!

Anyway, working fine now!

--
Pete