Works for me with Martin's /lib/udev/rules.d/61-mobile-action.rules,
though I'm confused as why the same thing in /etc/udev/rules.d won't
work. I debugged it with logger it, and it logs _after_ I unplug the usb
stick:
/etc/udev/rules.d/49-ZTE.rules:
ENV{ID_CDROM}=="1", ENV{ID_VENDOR_ID}=="19d2",
I encountered this problem in Ubuntu Karmic.
After trying all suggestions in many pages with no result, I tried this
:
rename /lib/udev/rules.d/61-mobile-action.rules,
to /lib/udev/rules.d/51-mobile-action.rules
Then plugging in the modem works as it was in Jaunty (yes, my ZTE MF622
was working
Przemysław Kulczycki [2009-12-01 16:46 -]:
> I meant an official update in the repositories, to make the hardware
> detection better also in older releases.
> Would it be possible to do such thing regularly as a matter of policy?
They need to be tested individually, though. E. g. for new key
m
2009/12/1 Martin Pitt :
> Przemysław Kulczycki [2009-12-01 14:04 -]:
>> Would it be possible to backport these rules to Karmic?
>
> Yes, you can just grab the ones from lucid.
I meant an official update in the repositories, to make the hardware
detection better also in older releases.
Would it
Przemysław Kulczycki [2009-12-01 14:04 -]:
> Would it be possible to backport these rules to Karmic?
Yes, you can just grab the ones from lucid.
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
--
ZeroCD de
2009/12/1 Launchpad Bug Tracker <281...@bugs.launchpad.net>:
> This bug was fixed in the package udev - 147-1
>
> ---
> udev (147-1) lucid; urgency=low
>
> * Update to 147 release:
> - Includes previous GIT updates.
> - udev-acl now requires ConsoleKit 0.4.1
> - gudev API no l
This bug was fixed in the package udev - 147-1
---
udev (147-1) lucid; urgency=low
* Update to 147 release:
- Includes previous GIT updates.
- udev-acl now requires ConsoleKit 0.4.1
- gudev API no longer marked as experimental
- rules updates. LP: #281335, #215035,
I really think it should work now. I committed this to trunk now (commit
6badb06).
** Changed in: udev (Ubuntu)
Status: Incomplete => Fix Committed
--
ZeroCD devices (on 3G modems) are not ejected automatically
https://bugs.launchpad.net/bugs/281335
You received this bug notification beca
Ah, I think I figured it out. The previous rules could never match the
fake CD-ROM device, which is what we need to match on and eject.
Can you please remove your rule in /etc/ again, install this one with
sudo cp 61-mobile-action.rules /ilb/udev/rules.d/
and test again?
Thanks!
** Attachmen
Well, maybe they should match, but they don't. Actually, *none* of them matches.
Instead, this works:
SUBSYSTEMS=="usb", ATTRS{bDeviceClass}=="00|ff",
ATTRS{bDeviceSubClass}=="00|ff", GOTO="mobile_action_switch"
All of the above checks match, and the ZeroCD is being ejected. Please
note that I us
Thanks for the attribute-walk outputs, they showed that all attribute
checks in
SUBSYSTEM=="usb", ATTR{bDeviceClass}=="00|ff",
ATTR{bDeviceSubClass}=="00|ff", ENV{DEVTYPE}=="usb_device"
*should* match.
Now I still don't understand why the rule doesn't work in the
mobile_action_switch block. Th
And the same command, but this time with the rule located under
/lib/udev/rules.d (not working). The device is in CD-ROM mode:
looking at device '/devices/pci:00/:00:1d.7/usb2/2-4':
KERNEL=="2-4"
SUBSYSTEM=="usb"
Here it is, with the device being already switched and connected to the
Internet:
looking at device '/devices/pci:00/:00:1d.7/usb2/2-4':
KERNEL=="2-4"
SUBSYSTEM=="usb"
DRIVER=="usb"
Good, thanks. Now plug it into the same port you used before, and
afterwards copy&paste the output of
udevadm info --attribute-walk
--path=/devices/pci:00/:00:1d.7/usb2/2-4
Thanks!
--
ZeroCD devices (on 3G modems) are not ejected automatically
https://bugs.launchpad.net/bugs/281335
Yo
** Attachment added: "lib_udev.txt"
http://launchpadlibrarian.net/32028501/lib_udev.txt
--
ZeroCD devices (on 3G modems) are not ejected automatically
https://bugs.launchpad.net/bugs/281335
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** Attachment added: "etc_udev.txt"
http://launchpadlibrarian.net/32028491/etc_udev.txt
--
ZeroCD devices (on 3G modems) are not ejected automatically
https://bugs.launchpad.net/bugs/281335
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Ok, did it twice:
1. The rule is located in file /etc/udev/rules.d/ZTE.rules
- the ZeroCD has been ejected, modem detected
- output attached as "etc_udev.txt"
2. The rule is located in file /lib/udev/rules.d/61-mobile-action.rules
- the ZeroCD has not been ejected, no modem
- output at
Then I guess one of these checks fails:
SUBSYSTEM=="usb", ATTR{bDeviceClass}=="00|ff",
ATTR{bDeviceSubClass}=="00|ff", ENV{DEVTYPE}=="usb_device"
Sergio, please do
udevadm monitor --udev -e
then plug in the device, and copy&paste the output. Thanks!
--
ZeroCD devices (on 3G modems) are not
Then I guess one of these checks fails:
SUBSYSTEM=="usb", ATTR{bDeviceClass}=="00|ff",
ATTR{bDeviceSubClass}=="00|ff", ENV{DEVTYPE}=="usb_device"
Sergio, please do
udevadm monitor --udev -e
then plug in the device, and copy&paste the output. Thanks!
** Changed in: udev (Ubuntu)
Status
No, it has not been fixed.
The rule inserted in "61-mobile-action.rules" is correct, but doesn't do
anything, probably because it's misplaced.
Placing that same rule in any file located under /etc/udev/rules.d (i.e.
ZTE.rules) makes it work, so it's definitely a problem of precedence.
--
ZeroC
** Changed in: udev (Ubuntu)
Status: Fix Released => Confirmed
--
ZeroCD devices (on 3G modems) are not ejected automatically
https://bugs.launchpad.net/bugs/281335
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
This bug was fixed in the package udev - 147~-1
---
udev (147~-1) karmic; urgency=low
FFE LP: #427356.
* Update to GIT HEAD (pre 147 release):
- worker signal mask corrected. LP: #407428.
- database format change to avoid path length issues. LP: #377121.
- multiple
Giuseppe,
I updated the upstream rules accordingly in commit bfde03a, to also
match on class/subclass "00". Thanks!
--
ZeroCD devices (on 3G modems) are not ejected automatically
https://bugs.launchpad.net/bugs/281335
You received this bug notification because you are a member of Ubuntu
Bugs, wh
I am sorry but i made a mistake, i am a newbie as regards udev stuff.
In fact, the rules are correct and in my karmic box both work as
expected, provided that they are outside the "mobile_action_switch"
block.
I couldn't get the SUBSYSTEM rule to work for my device, though.
--
ZeroCD devices (o
I have a ZTE ZeroCD device, with the same vendor and product id
19d2:2000, but the above rule doesn't work for me in karmic.
The device is branded by Vodafone It as K3565-Z. Plugging the device
result in the cd-rom being displayed, when manually ejected it switchs
to a modem as usual. The prod and
Great, all sounds good then :)
Thanks Martin :)
Regards from
Tom :)
--
ZeroCD devices (on 3G modems) are not ejected automatically
https://bugs.launchpad.net/bugs/281335
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
Tom [2009-08-24 11:56 -]:
> It's great to seee action taking place about this. Martin, your
> upstream bug-report
That wasn't a bug report, but a code change to the upstream code.
> only mentions 1 type of modem but i think this is a
> more widespread problem affecting a lot of different usb
Hi :)
It's great to seee action taking place about this. Martin, your
upstream bug-report only mentions 1 type of modem but i think this is a
more widespread problem affecting a lot of different usb wireless
dongles and other stuff too? Anyway, it's good to see the report out
there :) Nicely don
I committed the eject rule upstream to the existing 61-mobile-
action.rules file. I hope it still works like that, testing appreciated.
http://git.kernel.org/?p=linux/hotplug/udev.git;a=commit;h=3c47b388eef138cab2d931b73019650914305799
** Changed in: udev (Ubuntu)
Status: Confirmed => Fix
Tested on Karmic - it doesn't work. Debug output:
r...@dell:/lib/udev# ./modem-modeswitch -v 0x19d2 -p 0x2000 -t option-zerocd -d
D: Found mass storage device:
D: Endpoints: 2
D: Cla
Right, but I meant that all the other rules use /lib/udev/modem-
modeswitch for this, which is the intended program for this operation.
Can you please try whether this works, too?
ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="2000", RUN+="modem-
modeswitch -v 0x%s{idVendor} -p 0x%s{idProduct} -t o
Nope, there are no "interfaces" at this stage, and nm-modem-probe has
nothing to do with CD-ROMs.
A little background:
When ZeroCD devices are plugged in, they are not modems at all. They appear as
real CD-ROM drives, with data on them. No interfaces, no modems. USB IDs (e.g.
for ZTE MF series)
Martin, I haven't caught up with the stuff that moved in from udev-
extras yet - do you know what we do about this kind of thing?
** Changed in: udev (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
ZeroCD devices (on 3G modems) are not ejected automatically
https://bugs.launchpad.
33 matches
Mail list logo
