From: Clayton Craft <clayton@craftyguy.net>
To: ofono@ofono.org
Subject: Re: nokia-modem (N900) not detected after migration to udevng
Date: Thu, 07 Sep 2017 18:17:41 -0700 [thread overview]
Message-ID: <20170908011741.GC3@computer.craftyguy.net> (raw)
In-Reply-To: <7333b099-d68f-80d3-ddb5-a36693f420b0@southpole.se>
[-- Attachment #1: Type: text/plain, Size: 1984 bytes --]
This is on HSI bus. I am running ofono on the N900 (not tethering).
From what I understand, I am loading all of the necessary drivers for
this to work (nokia-modem, which pulls in its dependencies
automaticall).
As I stated in my original note, before moving 'legacy
device' initialization to udevng, ofono would at least 'see' the
modem. The test script 'list-modems' would list it, now it does not
list anything.
-Clayton
On Fri, Sep 08, 2017 at 03:13:03AM +0200, Jonas Bonn wrote:
>On 09/08/2017 02:51 AM, Clayton Craft wrote:
>>Hi,
>>I've been debugging why the n900 modem is not recognized by ofono
>>for a few days now, and have determined that the cause is because the
>>calls in udevng to udev_device_get_devnode return NULL. It seems that
>>the nokia-modem driver does not create any device nodes under /dev.
>
>What bus does this modem sit on? Are you running ofono _on_ the N900
>or are you trying to tether the N900 to some system with ofono?
>
>If you are tethering, what udev events do you get when you plug in the
>modem? Try running "udevadm monitor" and watch what happens when you
>plug the modem in.
>
>Not getting a device node sounds mostly like there's a driver missing,
>though...
>
>/Jonas
>
>>
>>This seems to be a regression in functionality since the move to
>>udevng as previous versions of ofono seem to detect the n900 modem
>>correctly (right before this commit
>>3ac449e25fc8cb9880c48b8f309189c6a644f200)
>>This issue occurs from this commit onwards, including the latest commit
>>as of this mail.
>>
>>https://git.kernel.org/pub/scm/network/ofono/ofono.git/tree/plugins/udevng.c#n1316
>>
>>
>>-Clayton
>>
>>_______________________________________________
>>ofono mailing list
>>ofono(a)ofono.org
>>https://lists.ofono.org/mailman/listinfo/ofono
>
>
>_______________________________________________
>ofono mailing list
>ofono(a)ofono.org
>https://lists.ofono.org/mailman/listinfo/ofono
next prev parent reply other threads:[~2017-09-08 1:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 0:51 nokia-modem (N900) not detected after migration to udevng Clayton Craft
2017-09-08 1:13 ` Jonas Bonn
2017-09-08 1:17 ` Clayton Craft [this message]
2017-09-08 1:29 ` Jonas Bonn
2017-09-08 1:38 ` Clayton Craft
2017-09-08 2:12 ` Jonas Bonn
2017-09-09 3:09 ` Clayton Craft
2017-09-09 8:56 ` [PATCH 1/1] udev: add serial_info struct to modem Jonas Bonn
2017-09-09 9:05 ` Jonas Bonn
2017-09-09 17:40 ` Clayton Craft
2017-09-09 17:58 ` nokia-modem (N900) not detected after migration to udevng Clayton Craft
2017-09-09 18:29 ` Denis Kenzior
2017-09-09 18:43 ` Clayton Craft
2017-09-09 20:34 ` Clayton Craft
2017-09-10 16:41 ` [PATCH 1/1] isimodem: Use correct callback for pin status Clayton Craft
2017-09-10 17:47 ` Denis Kenzior
2017-09-10 18:41 ` Clayton Craft
2017-09-11 15:37 ` Denis Kenzior
2017-09-11 15:44 ` nokia-modem (N900) not detected after migration to udevng Clayton Craft
2017-09-11 18:49 ` Denis Kenzior
2017-09-11 19:54 ` Clayton Craft
2017-09-12 7:51 ` Jonas Bonn
2017-09-12 8:11 ` [PATCH 1/2] udev: fixes for detection of non-USB modems Jonas Bonn
2017-09-12 8:11 ` [PATCH 2/2] udev: isi modems do not use 'Device' property Jonas Bonn
2017-09-12 17:28 ` [PATCH 1/2] udev: fixes for detection of non-USB modems Denis Kenzior
2017-09-08 3:17 ` [PATCH 1/1] udev: devnode is not a required modem property Jonas Bonn
2017-09-08 6:06 ` Clayton Craft
2017-09-08 8:07 ` [PATCH 1/1] udev: set driver for serial drivers Jonas Bonn
2017-09-08 15:25 ` Clayton Craft
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=20170908011741.GC3@computer.craftyguy.net \
--to=clayton@craftyguy.net \
--cc=ofono@ofono.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox