Re: Problems using 0.7.1 on Intrepid

[Dan Williams <dcbw redhat com>]

On Fri, 2009-04-17 at 19:48 +0200, Martin Bammer wrote:
> Ok, I've found the problem. The reason why udev failed on my system was
> that the install script installs 77-nm-modem-probe.rules
> to /lib/udev/rules.d by default, independent which version of udev is
> installed. I moved the script to /etc/udev/rules.d and now udev works as
> expected and ID_NM_MODEM_GSM and other attributes are set correctly.

I don't mind adding some code to detect udev version and install that
file in the right place accordingly.  Usually I'd rather not clutter up
the codebase with too much backwards compatibility stuff, but in this
case it would be fairly easy as it would simply be makefile magic.

Dan

> Cheers, Martin
> 
> 
> Am Freitag, den 17.04.2009, 09:48 -0400 schrieb Dan Williams:
> > On Thu, 2009-04-16 at 22:53 +0200, Martin Bammer wrote:
> > > Don't know where to start to search.
> > > What I've found on the web is that
> > > /sbin/udevadm info --export-db
> > > should output some lines like:
> > > E: ID_NM_MODEM_GSM=1
> > > But it doesn't. These lines are missing although there is a correctly
> > > detected umts modem up an running.
> > > My idea is that udev version 124-9ubuntu0.2 is too old.
> > > Could that be the reason?
> > 
> > I'm running udev-124 here too though; where is the installed
> > 77-nm-modem-probe.rules file?  For udev-124, it should be
> > in /etc/udev/rules.d, while for more recent udev versions, it goes
> > in /lib/udev/rules.d.
> > 
> > Next, you can get udev debugging information by using "/sbin/udevadm
> > control --log_priority=debug", then plug your card in, and mail me the
> > resulting output, which will be in syslog.  That will show the exact
> > steps that udev goes through, and we'll be able to figure out whether
> > the prober runs correctly.
> > 
> > Dan
> > 
> > > Martin
> > > 
> > > 
> > > Am Donnerstag, den 16.04.2009, 15:04 -0400 schrieb Dan Williams:
> > > > On Thu, 2009-04-16 at 20:30 +0200, Martin Bammer wrote:
> > > > > The function libudev_get_modem_capabilities in nm-hal-manager returns
> > > > > "success" even if udev doesn't report gsm or cdma capabilities on
> > > > > Intrepid (because udev in Intrepid is too old?). If udev is too old the
> > > > > function should return "failed".
> > > > 
> > > > The return value from that function isn't an indicator of whether or not
> > > > the hardware supports GSM/CDMA, it's an indicator of whether or not
> > > > there were any errors trying to query the udev database, irregardless of
> > > > what device properties were.  If it returns TRUE and didn't find any GSM
> > > > or CDMA capabilities, then either you don't have the prober set up
> > > > correctly, or the prober needs to be fixed up to detect your modem.
> > > > 
> > > > Dan
> > > > 
> > > > 
> > > 
> > 
>