On Monday 11 August 2014 15:16:47 Michael Biebl wrote: > Am 11.08.2014 15:10, schrieb David Baron: > > On Monday 11 August 2014 14:13:23 you wrote: > >> Am 11.08.2014 12:58, schrieb David Baron: > >>> On Monday 11 August 2014 12:28:39 Michael Biebl wrote: > >>>> Am 11.08.2014 11:50, schrieb David Baron: > >>>>> Package: udev > >>>>> Version: 208-7 > >>>>> Severity: normal > >>>>> > >>>>> --- Please enter the report below this line. --- > >>>>> Module use to auto-load as of 2.04.14 > >>>>> Workaround is simple enough: manually or rc.local modprobe snd-seq > >>>> > >>>> Have you rebooted after the upgrade to 208-7? > >>>> Do you have a /dev/snd/seq device after the reboot? > >>>> The 208-7 package has a fix for udev under sysvinit to create the dead > >>>> /dev/snd/seq device node. > >>>> > >>>> With that device available accessing /dev/snd/seq does auto-load the > >>>> snd-seq module here. > >>> > >>> Was rebooted. First thing I tried. > >> > >> What is the output of > >> "kmod static-nodes --format=tmpfiles" > > > > I assume you want this without my modprobing. > > > > This is what I get now, after having modprobed and qjackqtl runs: > > ~$ sudo kmod static-nodes --format=tmpfiles > > c /dev/autofs 0600 - - - 10:235 > > c /dev/fuse 0600 - - - 10:229 > > c /dev/cuse 0600 - - - 10:203 > > c /dev/btrfs-control 0600 - - - 10:234 > > c /dev/loop-control 0600 - - - 10:237 > > d /dev/net 0755 - - - > > c /dev/net/tun 0600 - - - 10:200 > > c /dev/ppp 0600 - - - 108:0 > > c /dev/uinput 0600 - - - 10:223 > > d /dev/mapper 0755 - - - > > c /dev/mapper/control 0600 - - - 10:236 > > d /dev/vfio 0755 - - - > > c /dev/vfio/vfio 0600 - - - 10:196 > > c /dev/vhci 0600 - - - 10:137 > > c /dev/uhid 0600 - - - 10:239 > > c /dev/vhost-net 0600 - - - 10:238 > > d /dev/snd 0755 - - - > > c /dev/snd/timer 0600 - - - 116:33 > > d /dev/snd 0755 - - - > > c /dev/snd/seq 0600 - - - 116:1 > > > >> Please add "set -x" to your /etc/init.d/udev init script and attach the > >> output you get during boot. > >> > >>> What about same fix but using systemd? > >> > >> Not sure what you mean by that? > > > > Systemd is the bootup system, not sysvinit (for which 208-7 was fixed). > > Ok, this was not clear from your bug report. > > > I am still running the 204.14 systemd. > > Oh, you shouldn't probably mix systemd 204 with udev 208. > > The creation of static device nodes was moved out of udev. > Under systemd this is now handled by > /lib/systemd/system/kmod-static-nodes.service (which is shipped in the > systemd package), under sysvinit, we added the creation of the static > device nodes to the /etc/init.d/udev init script. > > Since you upgraded udev to 208, but kept systemd at 204, you ended up > with this broken setup. > > Please update systemd to 208 as well and try again. > > To avoid this version mismatches, we might make systemd have a strictly > versioned dependency on udev.
The udev got upgraded by accident. I was avoid that as well. I have been asking and not getting good replies about how safe going to the 207-8 systemd packages is. But if sysvinit is still operational, I can place a fallback boot item with init= for that and try that first. If OK, no problem to upgrade the rest and be done. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
