Added kernel and hal tasks to investigate the right way to solve this.
Here's a paste of relevant bits of the upstream discussion (for a
different device, mentally substitute numbers ;p)
Start it off with a Novatel modem that must be ejected to work properly
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
+# Novatel USB devices need to be ejected so as to work properly as a modem
+SYSFS{idProduct}=="5010", SYSFS{idVendor}=="1410", RUN+="/usr/bin/eject %k"
> *ejected*? Do I even want to know why?
"Smart" devices which may appear either as a mass storage device which
contains windows drivers or as the device itself.
> I guess we should just eject the block device that comes from this
> device, when it shows up, instead of relying on magic of the eject
> program to find it.
I'm noticing, however, we already have code in unusual_devs.h to handle
this situation - why are we adding yet another solution?
> 2) Devices which have a fake CD-ROM that we don't care about, and are
> trying to "hide" from the user.
We already handle this in the desktop just fine [1]. And I think that's
the way forward for this; causal mom+pop users won't see any cdrom icons
anywhere in the UI when using a Sandisk U3 Cruzer (or whatever) but you
can still access and mount /dev/sr1 from the command line if you're into
that kind of kinky stuff. Who knows, maybe Wine is into that kind of
stuff.
[1] : right now via hal via fdi files but in a shiny future it will just
be yet another udev rule that merges a property DEVICE_SHOULD_BE_IGNORED
that the deskops will use to ignore the device.
--
Bandrich C100 HSPDA modem failure due to udev or hald actions
https://bugs.launchpad.net/bugs/199887
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
