Hello there,

    I recently updated two Devuans to ASCII.  I noticed, toying with
kernels vers. 4.11, 4.12 and 4.13, that I cannot use the WiFi and that ALSA
too doesn't work (both before and after removing pulseaudio).  I wonder
if someone else has tried that too, and if they experienced the same issues
or if someone knows why does that happen.
  Both the distribution's 4.9.0-3-amd64 and a custom 4.9.48 kernel work fine.

I noticed the same things happen with kernels 4.11 and 4.12 on a Fedora
26 and an Ubuntu 17.04, so I think it's not a Devuan-specific issue.

A few more details:

1) last kernel version that works is 4.10.17, now longer maintaned upstream;
2) later kernels do not automatically load all modules, but manually loading
them does not correct the situation;
3) wifi interface does not show up after successful boot and login:
ip link list dev wlan0
returns nothing. After doing modprobe iwldvm it does show up:

3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN mode DEFAULT
group default qlen 1000
    link/ether 00:01:03:46:a3:c7 brd ff:ff:ff:ff:ff:ff

wpa_supplicant is not able to configure it though:

wpa_supplicant -s -i wlan0 -c /etc/wpa_supplicant.conf -D nl80211 -B
-P /run/wpa_supplicant/wpa_supplicant.pid

returns exit status 255 and log reports:

Sep 13 11:03:06 ayu kernel: [10951.057545] wlan0: authenticate with
1c:bd:b9:89:4c:c1
Sep 13 11:03:06 ayu kernel: [10951.062128] wlan0: send auth to
1c:bd:b9:89:4c:c1 (try 1/3)
Sep 13 11:03:06 ayu kernel: [10951.126509] wlan0: authenticated
Sep 13 11:03:06 ayu kernel: [10951.128378] wlan0: associate with
1c:bd:b9:89:4c:c1 (try 1/3)
Sep 13 11:03:06 ayu kernel: [10951.132066] wlan0: RX AssocResp from
1c:bd:b9:89:4c:c1 (capab=0x411 status=0 aid=1)
Sep 13 11:03:06 ayu kernel: [10951.134720] wlan0: associated
Sep 13 11:03:06 ayu kernel: [10951.489809] wlan0: deauthenticating from
1c:bd:b9:89:4c:c1 by local choice (Reason: 1=UNSPECIFIED)

rfkill list wifi reports it unblocked.

Ethernet interface too isn't working after boot, but manually loading
modules af_packet and af_packet_diag fixes that.

Regarding the audio, /dev/snd only has these devices:

crw-rw---- 1 root 116, 1 set 13 10:38 seq
crw-rw---- 1 root 116, 33 set 13 08:01 timer

and no more show up after manually inserting missing snd_* modules.

Did anyone try using >= 4.11 kernels?