Bug#757777: [udev] Fails to Load Also snd-seq
On Monday 11 August 2014 17:17:30 Marco d'Itri wrote: On Aug 11, David Baron d_ba...@012.net.il wrote: 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. Please just upgrade. Upgraded successfully, rebooted without a hitch with systemd 208-7. snd-seq was indeed modprobed successfully without any workaround. Can close, but with note about this interdependence of systemd and udev which might not have been all-around the best idea. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757777: [udev] Fails to Load Also snd-seq
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 --- System information. --- Architecture: amd64 Kernel: Linux 3.14-2-amd64 Debian Release: jessie/sid 500 unstableftp.us.debian.org 500 testing ftp.us.debian.org 500 sid linux.dropbox.com --- Package information. --- Depends (Version) | Installed =-+-== libacl1 (= 2.2.51-8) | 2.2.52-1 libblkid1 (= 2.19.1) | 2.20.1-5.8 libc6 (= 2.17) | libkmod2 (= 5~) | libselinux1 (= 2.0.65) | libudev1 (= 204-14) | lsb-base (= 3.0-6) | util-linux (= 2.16) | procps| Package's Recommends field is empty. Package's Suggests field is empty. --- Output from package bug script --- -- BEGIN ATTACHMENTS -- /tmp/tmp.mV58GHnpby/udev-database.txt -- END ATTACHMENTS -- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757777: [udev] Fails to Load Also snd-seq
On Aug 11, David Baron d_ba...@012.net.il wrote: Workaround is simple enough: manually or rc.local modprobe snd-seq I am not sure if this driver can and/or should be autoloaded. -- ciao, Marco signature.asc Description: Digital signature
Bug#757777: [udev] Fails to Load Also snd-seq
On Monday 11 August 2014 11:55:11 Marco d'Itri wrote: On Aug 11, David Baron d_ba...@012.net.il wrote: Workaround is simple enough: manually or rc.local modprobe snd-seq I am not sure if this driver can and/or should be autoloaded. Maybe not, but it always was before. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757777: [udev] Fails to Load Also snd-seq
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. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#757777: [udev] Fails to Load Also snd-seq
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 about same fix but using systemd? Program looking for /dev/snd/seq is qjackctl. Here are it messages in its log: 12:44:22.033 Patchbay deactivated. 12:44:22.050 Statistics reset. 12:44:22.083 ALSA connection change. 12:44:22.105 D-BUS: Service is available (org.jackaudio.service aka jackdbus). Cannot connect to server socket err = No such file or directory Cannot connect to server request channel ... On program start, it shows the missing file or direcotry as /dev/snd/seq -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757777: [udev] Fails to Load Also snd-seq
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 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? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#757777: [udev] Fails to Load Also snd-seq
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. Marco, what do you think? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#757777: [udev] Fails to Load Also snd-seq
Am 11.08.2014 15:16, schrieb Michael Biebl: 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. An alternative suggestion might be to move /lib/systemd/system/kmod-static-nodes.service and /lib/systemd/system/sysinit.target.wants/kmod-static-nodes.service into the udev package (adding appropriate Breaks/Replaces). We should also consider adding a Recommends: kmod to udev and add a Breaks: kmod ( 15) which is the version that introduced kmod static-nodes which is used in the udev init script and kmod-static-nodes.service. The alternative would be to have a versioned dependency on kmod (= 15), but Marco wanted to keep the option of not having to install kmod in a container environment. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#757777: [udev] Fails to Load Also snd-seq
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
Bug#757777: [udev] Fails to Load Also snd-seq
On Aug 11, David Baron d_ba...@012.net.il wrote: 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. Please just upgrade. -- ciao, Marco signature.asc Description: Digital signature
Bug#757777: [udev] Fails to Load Also snd-seq
Am 11.08.2014 17:13, schrieb David Baron: 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. By whom? Pretty please don't believe everything that is written on the debian-user mailing list. In a lot of cases the information you get there is plainly wrong. 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. With sysvinit 2.88dsf-53.3 you have a sysvinit binary in /lib/sysvinit/ which you can booth via init=/lib/sysvinit/init -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
