[SOLVED] current64: udev 90-alsa-restore.rules not being run on startup

When I boot current64, it doesn't look like 90-alsa-restore.rules is being run by udev. I have chmod -x on /etc/rc.d/rc.alsa, and have relied on the udev rules to do the "alsactl restore" up until now. Not exactly sure when this broke, but I know it used to work.

Anyway, if after a boot I udevadm trigger -c add -s sound, the rules are run and the mixer values are set to values stored in asound.state, so the rules do work.

Anyone have any ideas why udev is failing to run these rules during boot? I'm at a loss.

Any useful info in syslog if you turn on udevd's logging? This can be done either with udev.conf or with a kernel command line argument. See udevd(8) and udev.conf(5).

Thanks for the suggestion. That got me to look again.

I'd already checked out the logs and didn't see anything of significance, but it seems neither of the approaches to turning on logging actually work on slackware. In the end I had to add -D 2>/run/udev.debug to the /sbin/udevd --daemon invocation in rc.udev to get it to work.

Anyway, that lead to an answer:

'/usr/sbin/alsactl restore 0'(err) '/usr/sbin/alsactl: load_state:1651: Cannot open /var/lib/alsa/asound.state for reading: Read-only file system'

So, udev not at fault here. Alsa is.


Why a read-only filesystem woould prevent "opening a file for reading" is beyond me. Nice one alsa devs!

So, we have a reason, even if it doesn't make sense.


I have wondered before whether moving the rootfs 'rw' toggle earlier in rc.S wouldn't be a bad idea.

Originally Posted by GazL I have wondered before whether moving the rootfs 'rw' toggle earlier in rc.S wouldn't be a bad idea.

Not before checking the file systems read-only. As an aside checking f2fs file systems is not done. Didn't I post yet about that? Here:

    if [ ! -r /etc/fastboot ]; then
        # The root partition has an F2fs file system
        if [ "$ROOTFS" = "f2fs" ]; then
            PERIODICITY=5
            # PERIODICITY is set in /etc/f2fs.conf if it exists, overriding
            # the value in previous line.
            [ -f /etc/f2fs.conf ] && . /etc/f2fs.conf
            if [ -f /var/lib/f2fs/next ]; then
                NEXT=$(cat /var/lib/f2fs/next)
            else
                NEXT=5
                FIRST="mkdir -p /var/lib/f2fs"
            fi
            if [ $NEXT -gt 0 ]; then
                LATER="echo $((NEXT - 1)) >/var/lib/f2fs/next"
            else
                echo "Checking root file system. Please be patient, this can take several minutes..."
                /usr/sbin/fsck.f2fs -f $ROOTDEV 1>/dev/null
                RETVAL=$?
                LATER="echo $PERIODICITY >/var/lib/f2fs/next"
            fi
        else

I've moved that whole rootfs checking section up near the beginning.
My rc.S now does it in this order:

1. sets the clock
2. mount /proc, /sys, /run.
3. rootfs check and remount section.
4. mtab section
5. rc.loop
6. rc.udev
7. the rest...

I'll mark this as SOLVED.