Hi all, >> Same issue as reported in this report, hotplug worked fine, cold boot >> failed. Did some udev debugging and saw the dispatcher did get started. >> Did some more debugging, changing scripts here and there (to prevent >> forking to the background and redirecting output) and finally saw that due >> to /root being mounted read-only on boot, usb-modeswitch failed to extract >> the right config from the data tarball. >> >> I extracted the config manually placed it in the right folder and >> everything was working fine after that.
This works for me, too! Specifically, extracting the config for 12d1:1446 (my USB modem's ID) and placing it in /etc/usb_modeswitch.d. On 10/14/2011 09:08 AM, Sander Geerts wrote: >> I'm not sure your situation is the same as that of the original >> reporter. Christian Kastner found no trace at all of usb_modeswitch >> running during boot. > > I'm not sure whether he checked the system logs or the output during > boot. I couldn't find a trace of usb_modeswitch in my syslog but when > inspecting the output of udev the hard way (using scroll lock etc) I did > find it called usb_modeswitch. > > Not sure why it doesn't show in the syslog, could be another side effect > of the read-only root filesystem though I'm no expert. I checked syslog + udev verbose output, and saw nothing... no idea why. Also, all the other log-generating parts (be it syslog or u-m's debug log) did show up with 1.1.4 -- don't ask me why that worked... You seem to be right on the money though with your diagnosis. >> Christian or Sander, can you try this on a Wheezy/Sid system? Sorry, I don't have any free machines available at the moment, but I guess that it's no longer relevant: Sander nailed it. But: if you need an alpha/beta tester for the upcoming 1.2.0 packages, just let me know and I'd be happy to test them! Regards, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
