From: Gabriel C <nix.or.die@googlemail.com>
To: shacky <shacky83@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-hotplug@vger.kernel.org
Subject: Re: Udev problem
Date: Fri, 28 Dec 2007 03:29:04 +0100 [thread overview]
Message-ID: <47745F70.7090204@googlemail.com> (raw)
In-Reply-To: <7fedbc910712271434v56f45b37r875203063bc38be8@mail.gmail.com>
shacky wrote:
[ Added linux-hotplug to CC ]
> Hi.
Hi,
>
> I'm writing here because I didn't found a mailing list specific for udev.
There it is :
http://vger.kernel.org/vger-lists.html#linux-hotplug
> I'm sorry if I am out of topic. In this case please tell me.
>
> I'm trying to get an Huawei e220 UMTS/HSDPA USB modem working on my Ubuntu 7.10.
> The problem of that peripheral is that when you plug the modem in the
> USB port, it is recognise as an USB CD-ROM.
> I have the 2.6.22 kernel, which shouldn't recognise this modem as a
> CD-ROM (I read this on http://oozie.fm.interia.pl/pro/huawei-e220/),
> but this doesn't happen.
>
> To make this modem works you have to execute a program named
> "huaweiAktBbo", whose source can be found at
> http://www.kanoistika.sk/bobovsky/archiv/umts/huaweiAktBbo.c
> I compiled it and I saved the compiled program in /sbin.
> Please note that the program works perfectly if executed from the shell as root.
>
> So I wrote a new udev rule (/etc/udev/rules.d/50-huwaei-e220.rules)
> with this rule:
>
> SUBSYSTEM=="usb", SYSFS{idProduct}="1003", SYSFS{idVendor}=="12d1",
> RUN+="/sbin/huaweiAktBbo"
>
> But when I plug the modem in the USB port I get this errors in /var/log/syslog:
>
> Dec 23 23:06:39 studio2 udevd-event[5644]: run_program: '/sbin/huaweiAktBbo'
> Dec 23 23:06:39 studio2 udevd-event[5644]: run_program:
> '/sbin/huaweiAktBbo' (stderr) 'huaweiAktBbo: huaweiAktBbo.c:113: main:
> Assertion `dev' failed.'
> Dec 23 23:06:39 studio2 udevd-event[5644]: run_program:
> '/sbin/huaweiAktBbo' (stdout) 'Hladam HUAWEI E220 a prepnem na modem -
> bbo 06'
> Dec 23 23:06:40 studio2 udevd-event[5644]: run_program:
> '/sbin/huaweiAktBbo' abnormal exit
>
> If I run that program as root from the console, it works, and I can
> use the modem well:
>
> Hladam HUAWEI E220 a prepnem na modem - bbo 06
> 4 set feature request returned 0
> Prepnute-OK, Mas ttyUSB0 ttyUSB1 (cez usbserial vendor=0x12d1 product=0x1003)
> pozri /proc/bus/usb/devices
>
> I contacted the creator of the program, and he told me that the
> program doesn't work because it doesn't found the device in the bus.
> But udev recognise the device, because it executes the script as you
> can see in the logs.
> he told me that the problem can be if udev execute the rule before it
> adds the device in the kernel, is it possible?
>
> Is it possible to delay the execution of the rule after the device is
> recognised in the kernel and added to the device list in the bus
> (lsusb)?
>
> Could you help me, please?
> Thank you very much in advance for your help!
> Bye.
next prev parent reply other threads:[~2007-12-28 2:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-27 22:34 Udev problem shacky
2007-12-28 2:29 ` Gabriel C [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-30 7:12 Sander Knopper
2004-09-08 23:13 ` Greg KH
2004-09-09 8:33 ` Kay Sievers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47745F70.7090204@googlemail.com \
--to=nix.or.die@googlemail.com \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shacky83@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.