modem is plugged. Put this below the first "ACTION" line in
/lib/udev/rules.d/40-usb_modeswitch.rules:
ATTR{idVendor}=="1c9e", ATTR{idProduct}=="9801", RUN+="/path/to/your/script"
Good luck,
Josua Dietze
Am 27.01.2016 um 06:47 schrieb Jon Forsberg:
This is how I invoke it:
usb_modeswitch --default-vendor=0x12d1 --default-product=0x1446 -J -Q
There is a bit of a misunderstanding there.
The log is created during the automatic invocation of usb_modeswitch, when
the wrapper
I have just released upstream version 2.3.0 of usb_modeswitch and version
20160112 of the data package.
The bug with the missing log is fixed, as well as a potentially disruptive
other bug in the wrapper (see
http://draisberghof.de/usb_modeswitch/bb/viewtopic.php?p=16240 ).
However, I have
Am 09.01.2016 um 00:14 schrieb Blake Miner:
Honestly, I did try the whole usbmodeswitch logging thing to no avail
There is only the one global switch in /etc/usb_modeswitch.conf - if that did
not work, then it's very likely that the dispatcher is never run.
I'll have a closer look at
Am 09.01.2016 um 00:14 schrieb Blake Miner:
Honestly, I did try the whole usbmodeswitch logging thing to no avail
I have found a stupid bug in the dispatcher which prevented early
logging ...
Edit the dispatcher script "/sbin/usb_modeswitch_dispatcher" (or
"usb_modeswitch.tcl" in the source).
Am 08.01.2016 um 21:25 schrieb Blake Miner:
Bump. Any another thoughts on this bug? It's hard to tell if this is a
usb-modeswitch bug (i.e. a problem with usb_modeswitch_dispatcher) or if this
is a problem with the udev rule itself (a usb-modeswitch-data bug).
Have you tried to enable
Am 19.11.2015 um 01:00 schrieb Blake Miner:
The catch-all udev rule does not work:
# Generic entry for all Huawei devices
ATTRS{idVendor}=="12d1", ATTR{bInterfaceNumber}=="00", ATTR{bInterfaceClass}=="08",
RUN+="usb_modeswitch '%b/%k'"
Thanks for the report. Upstream dev here.
This has
Thanks for the hint!
I have applied the patch to the new upstream version of the data package
(20151101), available as of now; I was in the process of releasing it when you
filed the bug. Great timing!
Best regards,
Josh
being handed to systemd, and no more escaping is done.
Odyx, if you want I can cobble together a patch to back-port the fix to 2.2.0.
Regards,
Josua Dietze (usb_modemswitch upstream)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
{bInterfaceClass}==08,
RUN+=usb_modeswitch '%b/%k'
The correction is included with the latest upstream release of the data
package, version 20150627.
Regards,
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
from %I to %i, so
there will be no escaping at all.
I'm confident that this will solve the problem with your modem.
Best regards,
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
to the top in usb_modeswitch's log starting with
Raw args from udev:
Thanks again! As soon as I have double-checked that raw argument, I'll
incorporate your fix in the coming release 2.2.2.
Best regards,
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
Weitergeleitete Nachricht
Von: Hugh Pumphrey hugh.pumph...@ed.ac.uk
OK, here it is
Bus 001 Device 007: ID 12d1:1037 Huawei Technologies Co., Ltd. Ideos
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass
address. It's best to simply
hit Reply to all.
Regards,
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
.
Thanks!
BTW, you don't have to uninstall usb_modeswitch. Just edit
/etc/usb_modeswitch.conf and set DisableSwitching to 1.
Regards,
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
.
Regards,
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Am 02.08.2014 19:43, schrieb Didier 'OdyX' Raboud:
Josua: what do you think could be done there?
Uh, sorry, this was not on my radar anymore ...
I just checked version 1.2.5 with two cascaded USB hubs and got the same
problem as Stefano with a mutilated device path.
It seems I have
For completeness' sake, here is the excerpt from the rules file. Only the
relevant lines are included.
/lib/udev/rules.d/40-usb_modeswitch.rules
ACTION!=add|change, GOTO=modeswitch_rules_end
[...]
# Don't continue
O.K., here is a suggestion about how to test the new Huawei udev rule.
Obviously the new versions of usb-modeswitch and usb_modeswitch-data should be
installed.
1. Disable mode-switching (edit /etc/usb_modeswitch.conf) just to be on the
safe side, run this command:
udevadm monitor
and plug
Am 12.07.2014 21:22, schrieb Maciej Kotliński:
I tested switching as you wrote.
Thanks, Maciej.
I can see no reason why the Huawei rule should not trigger.
Odyx, can we somehow involve the udev maintainer(s)?
For the record, my udev version is 208 (udevadm --version).
Josh
--
To
Hmm. The modem looks like it should. The udev rule should trigger when this
interface is added.
bInterfaceNumber0
...
bInterfaceClass 8 Mass Storage
Last night, I tested all my six Huawei modems with the new catch-all rule -
again. No problems of any kind.
There is a
Am 11.07.2014 21:23, schrieb Maciej Kotliński:
My Huawei E3272 (12d1:1f01) does not get switched after plugging.
Please join this bug report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754348
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Thanks for the report, Giacomo.
Can you post one more information detail?
With your stick *not* switched, run sudo lsusb -v -d 12d1:1446 E1800.lsusb
and paste the content of the E1800.lsusb file to your reply.
Josh (usb_modeswitch 'upstream')
--
To UNSUBSCRIBE, email to
Did the problem go away when you downgraded?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
it to /etc/modeswitch.d where it can be modified to try out several things.
For you it would be the config file named 12d1:14fe. Don't bother about the
name in the description, model names are hardly ever consistent when it comes to mobile
modems.
Regards,
Josua Dietze
--
To UNSUBSCRIBE
boot, but it may be worth a try.
Set EnableLogging = 1 in /etc/usb_modeswitch.conf and go to /var/log after
booting with the stick.
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
It's clear now that usb_modeswitch can't do anything here.
Please reassign - my guess is that it's a kernel driver thing, either USB 3.0
host or usb-storage (or both).
Am 04.12.2013 15:07, schrieb Ben Hutchings:
Le mercredi, 4 décembre 2013, 11.01:14 Josua Dietze a écrit :
It's clear now that usb_modeswitch can't do anything here.
I don't see that at all. There could be some magic file on the virtual
CD-ROM that Windows already knows how to interpret. (I
usb_modeswitch works.
Note that if a special Windows driver is required for actually ACCESSING the
disk (not just for initialization), then a new Linux driver may be required as
well ...
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe
the problem.
Regards,
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Am 10.06.2013 13:39, schrieb Didier 'OdyX' Raboud:
Apparently you forgot to include this change in the new rules file (also in
the gen_rules.tcl) apparently; was that intentional?
Darn - of course not ... That's what you get for waiting too long between
releases.
I am about to issue annother
Am 19.01.2013 10:30, schrieb Stefano Rivera:
With 20121109-1 I get /var/log/usb_modeswitch_1-1.2 containing:
| USB_ModeSwitch log from Sat Jan 19 11:25:40 SAST 2013
|
| Raw args from udev: /1-1.2
|
| Using global config file: /etc/usb_modeswitch.conf
| Could not determine top device dir from
Am 18.01.2013 10:01, schrieb Didier 'OdyX' Raboud:
That's very weird as 20120815-2 and 20121109-1 have the exact same
configuration file for 12d1:14fe :
I was just about to write and point out that very same fact.
Stefano, can you retrieve a mode-switching debug log?
See
Am 16.01.2013 10:57, schrieb Didier 'OdyX' Raboud:
Le mercredi, 16 janvier 2013 09.53:26, John Hedges a écrit :
Symlinks created by local rules for ttyUSB devices are lost because of the
following rule in /lib/udev/rules.d/40-usb_modeswitch.rules
KERNEL==ttyUSB*, ATTRS{bNumConfigurations}==*,
Fortunately (or not, depending on the point of view) I just had a direct report
about this same problem.
At the heart of the matter is the decision of the phone/firmware makers to
re-use the USB ID of the MediaTek modems. Now we have to separate phones from
modem sticks.
The solution is to
/usb_modeswitch.conf and see how far the
log goes?
Thanks,
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
=...) at vfprintf.c:1620
I think this is the known bug 656688:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656688
Can you try the patched source pack provided there?
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Am 24.01.2012 21:21, schrieb Kein Kommentar:
this version works for me. Thank you.
usb-modeswitch-1.2.2-1.tar.bz2
Thanks for the confirmation, everyone.
I will do an upstream bugfix release which Odyx can just package as usual.
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist
folder, run make install.
For any new deb package, run make uninstall in the source folder
before installing it. There will be no side effects.
Note that this is a special source package tailored for Debian. I'm
looking forward to hearing any reports.
Josua Dietze
--
To UNSUBSCRIBE, email
from the rest of the
script code.
Unfortunately, I have run into bug #656063 afterwards, but that's
annother story.
Josua Dietze
diff -urN usb-modeswitch-1.2.2/dispatcher.c usb-modeswitch-1.2.2-1/dispatcher.c
--- usb-modeswitch-1.2.2/dispatcher.c 2012-01-19 01:01:50.0 +0100
+++ usb
from the
command line will succeed as expected.
I have attached a patch for an immediate work-around.
Further research is neccessary though.
Josua Dietze
diff -urN usb-modeswitch-1.2.2/usb_modeswitch.tcl
usb-modeswitch-1.2.2-1/usb_modeswitch.tcl
--- usb-modeswitch-1.2.2/usb_modeswitch.tcl
=656688
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
protection ip:7eff71e72038
sp:7fffca3fc790 error:0 in libc-2.13.so[7eff71e2e000+17a000]
Downgrading back to 1.2.1+repack0-1+0fix656248~0 fixed the problem.
This bug is known as #656688 so it is not necessary to re-open this one.
See
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656688
Josua Dietze
by.
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656248
Can you try the fixed version 1.2.2? It is up on
http://packages.debian.org/sid/usb-modeswitch
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
Odyx et al., upstream version 1.2.2 is available.
Only changes against 1.2.1 are the bug fix for #656248 and a more detailed
log output in case of target parameter mismatch.
Cheers,
Josh
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
Am 17.01.2012 20:26, schrieb Ralf Jung:
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 03f0:002a
found matching vendor ID
found matching product ID
target class 07 not matching
No devices in default mode found. Nothing to do. Bye.
Am 03.11.2011 10:11, schrieb Wojtek Zabolotny:
Josua Dietze wrote:
Also, what happens if you put the unpacked file in /usr/share/usb_modeswitch
(beside the package file) instead of /etc/usb_modeswitch.d ?
Yes, unpacking into /usr/share/usb_modeswitch halped also.
In that case, version 1.2.0
Am 17.10.2011 12:27, schrieb Didier Raboud:
After a rapid look trough it, I noticed that you embed jimtcl 0.71;
unfortunately, this fact somehow means that I will have to package jimtcl
independently from usb-modeswitch, patch it out from the source tarball we
release and patch usb-modeswitch's
Am 14.10.2011 23:14, schrieb Christian Kastner:
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.
Aah. That restores my faith in determinism :-)
But: if you need an alpha/beta tester for the upcoming 1.2.0
Am 15.10.2011 08:29, schrieb Josua Dietze:
Taking your word for it - here we are:
Sorry, wrong link, use this one:
http://www.draisberghof.de/usb_modeswitch/usb-modeswitch-1.2.0beta.tar.bz2
Josh
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
by for version 1.2.0 ...
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
the unpacked file in /usr/share/usb_modeswitch
(beside the package file) instead of /etc/usb_modeswitch.d ?
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Am 17.08.2011 01:10, schrieb Christian Kastner:
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 am almost out of clues about what else is there to test. I'll try further to
evoke the problem on my systems somehow. So far, this has failed.
reply?
You will find it in /var/log a while after you re-plugged the stick.
Thanks,
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Am 16.08.2011 14:41, schrieb Detlev Brodowski:
I have activated logging.
Thanks for the logs. They confirmed the bug very nicely.
I've done some testing and found one system where the same error was occurring.
For a fix, edit /usr/sbin/usb_modeswitch_dispatcher and look for line 244.
It
Am 16.08.2011 20:47, schrieb Detlev Brodowski:
It works. :)
Odyx, can you release the fix as a patched-up version? I would not like to do a
full release if I don't have to.
Thanks,
Josh
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
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
Am 11.08.2011 00:34, schrieb Christian Kastner:
Strange thing: on my netbook the problem hasn't changed, but on my
desktop PC switching occurs with versions 1.1.4 to 1.1.9 (as confirmed
by lsusb and dmesg output), but the /dev/gsmmodem symlink does not get
set up in versions 1.1.7 and above.
Am 09.08.2011 15:47, schrieb Didier Raboud:
I would like to have Josua's (upstream author) input on this bug. I think
doing nothing but closing as such would be OKay, but his take on that would
be valuable.
Everything seems fine ... Just one thing kept bothering me:
kernel: [48972.216084] usb
Am 09.08.2011 20:14, schrieb Didier Raboud:
I'd be happy to close this bug, _but_ I don't want to lose information: in
short, this is a kernel bug, right? Are you aware of an opened bug for the
upstream Linux kernel ? If not, I propose to reassign this bug to the Debian
kernel package and help
with the modem, then this
would point to ModemManager as likely culprit.
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
device ...
Usually, there is *no* serial interface initially, just an install partition
containing the drivers.
What happened on Windows when you plugged in for the first time? Have you been
offered a driver installation immediately?
Regards,
Josua Dietze
--
To UNSUBSCRIBE, email to debian
Am 20.07.2011 22:23, schrieb Francesco Poli (wintermute):
I installed usb-modeswitch in order to prevent my USB HSDPA modem to be
seen as a storage device.
That may be a misunderstanding. After a mode switch, there may still be storage
interfaces exposed in a modem device. The difference is
Am 22.06.2011 09:56, schrieb Josua Dietze:
If you want you can check for the other variables too; just before the case
line, the values for v_id and p_id should be set.
echo ums variables: v_id $v_id, p_id $p_id 2
I have to correct myself here; the variables mentioned are *not* relevant
Am 22.06.2011 10:24, schrieb Didier Raboud:
FYI, the logs also contained the following linces (twice):
'/lib/udev/usb_modeswitch' (stderr) '/lib/udev/usb_modeswitch: 33:'
'/lib/udev/usb_modeswitch' (stderr) 'arithmetic expression: expecting
EOF: 0x'
'/lib/udev/usb_modeswitch' (stderr) ''
This
Am 20.06.2011 15:03, schrieb Christian Kastner:
No luck, sorry...
O.K., time to remove the velvet gloves and get really nasty.
Two things to do (staying at version 1.1.8):
1. Edit /usr/sbin/usb_modeswitch_dispatcher,
insert these lines in the {Log} procedure before line 616:
--- snip
Am 18.06.2011 22:24, schrieb Josua Dietze:
I'm just now working on the next version, 1.1.8, which tries to use a fallback
in case of said quirks instead of bailing out.
Now I have prepared a full test package of 1.1.8. I will release tonight if no
quirks are reported.
Get it here:
http
I have prepared a full test package of 1.1.8, including the changes we were
discussing. I will release tonight if no quirks are reported.
Get it here:
http://www.draisberghof.de/usb_modeswitch/usb-modeswitch-1.1.8-test.tar.bz2
Am 18.06.2011 16:11, schrieb Christian Kastner:
I have attached a file with the following contents:
1. output of lsusb when plugged in at boot, then removed, then plugged
back in, and `diff -U 0`
a) from boot to removed
That output is enough to confirm that there was no switching
Am 18.06.2011 19:09, schrieb Christian Kastner:
On 06/18/2011 06:04 PM, Josua Dietze wrote:
To circle in further, can you install version 1.1.4 and just swap the
little shell script usb_modeswitch in /lib/udev with the updated file
from upstream 1.1.7 ?
With the above configuration, it's
Am 18.06.2011 22:11, schrieb Christian Kastner:
With 1.1.4 and udev, dispatcher from 1.1.7, it still appears to be
switching properly at boot:
So it's most likely a problem with the binary C program.
There has been a change regarding determining the current device configuration
since 1.1.6.
Am 16.06.2011 08:51, schrieb Didier Raboud:
Le jeudi, 16 juin 2011 09.21:10, Alex Hermann a écrit :
There are more software packages using this scheme (udev, mysql, pam)
although most place all configs in /etc. I have no idea about the amount
of support/bugreports this causes. IMHO, if a user
Am 16.06.2011 20:22, schrieb Didier Raboud:
Le jeudi, 16 juin 2011 19.21:25, Josua Dietze a écrit :
To wrap it all up, the future priority logic would run like this:
As far as I can tell, this is mostly how the Debian-patched usb-modeswitch
works. But it's better if it's upstream, sure.
I
is the problem that it's hard to get any log if you plug
before booting. The file system is mounted read-only first, so switching may
succeed but there is no logging at all.
Are you sure the switching itself is not happening? Did you check the device ID
after booting with the stick?
Josua Dietze
Am 14.06.2011 12:06, schrieb Didier Raboud:
Thanks for your time and skills !
Just want to let you know that I'm on the job now and following this exchange.
Originally, the packed config file was not intended for default use on desktop
systems. It kind of amazed me to see this happening on
Am 15.06.2011 21:56, schrieb Alex Hermann:
On Wednesday 15 June 2011, Josua Dietze wrote:
Why not use the
/usr/share/usb_modeswitch folder, alongside the package?
IMHO I think the folder change is not a good idea. The /usr/share folder is
supposed to be under package manager control, not user
modems are getting a different target ID with
that command which may not be included with the respective config file.
I suspect that may be the reason why you don't get the gsmmodem link.
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
Am 16.05.2011 16:23, schrieb Carlo Marchiori:
No I didn't check, I wouldn't know what to check actually, I'm IT literate but
just a Debian user.
With checking, I just meant to have a look if it's there at all ...
/lib/udev/hotplug.functions
This is the Debian patch for the little shell
boot processing worked
reliably.
Concerning the timing, it makes sense to run the whole switching procedure
detached from the boot process because the devices concerned do need from 2 to
20 seconds to return in their new mode.
Josua Dietze
Michael Biebl bi...@debian.org schrieb:
Hi Didier
I have changed this upstream in version 1.1.7 which was just released.
No more /etc/usb_modeswitch.d ...
Josh
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
might in fact be needed during boot.
Josua Dietze
(upstream)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
in wrapper version 1.1.4 which has to be reflected in
the udev rule.
Since we obviously cannot expect any more help from the reporter, I'm
pleading for rejecting the error report after the version update.
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
finding the problem, can we agree to close
this bug?
Josua Dietze
Nils Radtke nils.rad...@think-future.de schrieb:
Hi,
There is specific information and even a patch showing how it should work.
Not working is precise enough, as it is: Not Working. Also, there's the
indication
Not working is a bit unspecific. Please post the per-interface logs that the
custom dispatcher script puts out. And check if you are using the latest data
package.
Josua Dietze
Nils Radtke l...@think-future.de schrieb:
Using 1.1.4-1 w/ the dispatcher packaged and the one w/ md5sum
/usb_modeswitch/usb_modeswitch_dispatcher.gz
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Am 22.08.2010 18:43, schrieb er...@ikki.ws:
The 19d2:2000 entries are only in 40-usb_modeswitch.rules and
etc/usb_modeswitch.d/19d2:2000.
Thanks for confirming. From my point of view I think we could as well
close this bug.
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist
Am 21.08.2010 01:27, schrieb er...@ikki.ws:
Some questions:
What happens if you leave the usb_modeswitch config file intact but
disable the rule in 61-mobile-action.rules (out-comment, reload rules) ?
Ok, usb_modeswitch config file intact (19d2:2000)
1) 61-mobile-action.rules, it has the
I released a new version which does not use the temp file mechanism
anymore. And it's fit for boot time usage now (tested on Debian 5 and
many other systems).
This should fix this error.
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
I released a new version (1.1.4) which incorporates the changes
mentioned earlier. I could test it myself with single-interrupt
devices only but I'm very confident that it will fix the problem.
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
script in earlier versions), but in addition
the whole package is now boot-proof. This was tested on Debian 5 and
many other systems.
The sleep periods are still part of the process but they are not
blocking anything except the script (well, they are supposed to).
Josua Dietze
script in earlier versions), but in addition
the whole package is now boot-proof. This was tested on Debian 5 and
many other systems.
The sleep periods are still part of the process but they are not
blocking anything except the script (well, they are supposed to).
Josua Dietze
I released a new version (1.1.4) where the changes of Didier's fix
were incorporated. I use the wait_for_file function inline because
no other distribution I tested on provides hotplug.functions.
The whole package is now boot-proof. This was tested on Debian 5 and
many other systems.
Josua
I released a new version (1.1.4) from which the grep lines are removed.
Oh, and it has never been called recursively ...
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
it last night. I have CC'd Nils Radtke among others.
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
will not ask about your definition of going
berserk :-)
Josua Dietze - Berserk Upstream
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
system its size is
6688 Bytes.
This may be useful on systems with constrained resources.
Regards,
Josua Dietze
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Please ignore message #62.
It was intended for bug #591761.
Sorry, temporary loss of track.
Josh
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Am 05.08.2010 19:50, schrieb Marco d'Itri:
You are trying to solve this at the wrong level. You should use an
IMPORT rule triggered by KERNEL=ttyS* (or something like this) and then
a SYMLINK rule triggered by an exported variable.
Anyway, you should not manually create symlinks in /dev.
If you
Am 07.08.2010 18:12, schrieb Didier 'OdyX' Raboud:
Hi Marco and Josh,
So here's a first patch for this bug. Marco: would that sound okay for you ?
http://git.debian.org/?p=collab-maint/usb-modeswitch.git;a=commitdiff;h=a41dcc4
That's absolutely fine with me, taking the alsa way. For the
1 - 100 of 115 matches
Mail list logo
