On 08/15/2011 05:36 PM, Josua Dietze wrote: > Am 13.08.2011 10:03, schrieb Josua Dietze: >> The main issue was that udev did not run usb_modeswitch _at all_ >> during boot on >> the router. That may shift the focus to the udev rules file, which is >> part of >> the data package. > > Oddly enough, I received a report by mail from someone at AltLinux. He > encountered a boot-n-switch problem as well. His analysis is quite > interesting (quoted): > > "The reason for that is that the kernel emits only 'change' events for > the devices it finds already plugged-in when 'udevadm trigger' is called > on the udev service start. However, only 'add' events are processed by > the modeswitch udev rule script." > > The udev version involved was 172 which is fairly new. > > The fix should be easy - let the rules be evaluated not only for an > "add" event but also for a "change" event. > > To put it in a nutshell: in /lib/udev/rules.d/40-usb_modeswitch.rules > change this line > > ACTION!="add", GOTO="modeswitch_rules_end" > > to this: > > ACTION!="add|change", GOTO="modeswitch_rules_end"
This explanation sounded so plausible and convincing, imagine my disappointment when it didn't work -- the device is still not switched. I did not yet have time to run the full battery of tests (eg [0]), but will do so as soon as I can. I put ~50 reboots in tonight before I realized my dumb mistake mentioned in the other mail... I should have more info tomorrow; Friday latest. Thanks for your patience and perseverance... Christian [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629371#96 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
