Re: nokia-modem (N900) not detected after migration to udevng
On Mon, Sep 11, 2017 at 01:49:05PM -0500, Denis Kenzior wrote:
If Jonas or you want to combine these into a single proper patch,
I'll take it up.
Challenge accepted! Combined patch below.
-Clayton
plugins/udevng.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/plugins/udevng.c b/plugins/udevng.c
index 518eda8e..a4b99aa4 100644
--- a/plugins/udevng.c
+++ b/plugins/udevng.c
@@ -1013,8 +1013,6 @@ static gboolean setup_isi_serial(struct modem_info* modem)
if (value)
ofono_modem_set_integer(modem->modem, "Address", atoi(value));
- ofono_modem_set_string(modem->modem, "Device", info->devnode);
-
return TRUE;
}
@@ -1325,7 +1323,7 @@ static void add_serial_device(struct udev_device *dev)
devnode = udev_device_get_devnode(dev);
- if (!syspath || !devname || !devpath || !devnode)
+ if (!syspath || !devpath)
return;
modem = g_hash_table_lookup(modem_list, syspath);
@@ -1337,7 +1335,7 @@ static void add_serial_device(struct udev_device *dev)
modem->type = MODEM_TYPE_SERIAL;
modem->syspath = g_strdup(syspath);
modem->devname = g_strdup(devname);
- modem->driver = g_strdup("legacy");
+ modem->driver = g_strdup(driver);
g_hash_table_replace(modem_list, modem->syspath, modem);
}
@@ -1357,7 +1355,7 @@ static void add_serial_device(struct udev_device *dev)
info->subsystem = g_strdup(subsystem);
info->dev = udev_device_ref(dev);
- modem->devices = g_slist_append(modem->devices, info);
+ modem->serial = info;
}
static void add_device(const char *syspath, const char *devname,
___
ofono mailing list
ofono@ofono.org
https://lists.ofono.org/mailman/listinfo/ofono
Re: nokia-modem (N900) not detected after migration to udevng
Hi Clayton, On 09/11/2017 10:44 AM, Clayton Craft wrote: Hi Denis, The following patches are also necessary to help bring up the isimodem device, I don't think they were accepted/merged. If you need anything else to help get these in, please let me know! https://lists.ofono.org/pipermail/ofono/2017-September/017463.html https://lists.ofono.org/pipermail/ofono/2017-September/017465.html https://lists.ofono.org/pipermail/ofono/2017-September/017483.html -Clayton If Jonas or you want to combine these into a single proper patch, I'll take it up. Regards, -Denis ___ ofono mailing list ofono@ofono.org https://lists.ofono.org/mailman/listinfo/ofono
Re: nokia-modem (N900) not detected after migration to udevng
Hi Denis, The following patches are also necessary to help bring up the isimodem device, I don't think they were accepted/merged. If you need anything else to help get these in, please let me know! https://lists.ofono.org/pipermail/ofono/2017-September/017463.html https://lists.ofono.org/pipermail/ofono/2017-September/017465.html https://lists.ofono.org/pipermail/ofono/2017-September/017483.html -Clayton On Sat, Sep 09, 2017 at 01:29:33PM -0500, Denis Kenzior wrote: Hi Clayton, On 09/09/2017 12:58 PM, Clayton Craft wrote: Ok, now the modem is initializing (after applying 3 patches from Jonas), I get this seg fault in ofonod when I run the "enable-modem" test script: See https://lists.ofono.org/pipermail/ofono/2017-May/017311.html Regards, -Denis ___ ofono mailing list ofono@ofono.org https://lists.ofono.org/mailman/listinfo/ofono
Re: nokia-modem (N900) not detected after migration to udevng
Would it be possible to merge the three patches that Jonas produced, so at least the modem will make it through the initialization phase? I will take a long, hard look at some point into the patchset you linked in your other mail, and one day I might try to fix it, but being able to avoid the previous init problems when that day comes would be really nice :) -Clayton On Sat, Sep 09, 2017 at 01:29:33PM -0500, Denis Kenzior wrote: Hi Clayton, On 09/09/2017 12:58 PM, Clayton Craft wrote: Ok, now the modem is initializing (after applying 3 patches from Jonas), I get this seg fault in ofonod when I run the "enable-modem" test script: See https://lists.ofono.org/pipermail/ofono/2017-May/017311.html Regards, -Denis ___ ofono mailing list ofono@ofono.org https://lists.ofono.org/mailman/listinfo/ofono
Re: nokia-modem (N900) not detected after migration to udevng
See https://lists.ofono.org/pipermail/ofono/2017-May/017311.html Oh, wow, that's a bit of a downer.. but thanks for the info. Is there a reason the ISI RFC patch you mentioned there was not merged? -Clayton ___ ofono mailing list ofono@ofono.org https://lists.ofono.org/mailman/listinfo/ofono
Re: nokia-modem (N900) not detected after migration to udevng
Hi Clayton, On 09/09/2017 12:58 PM, Clayton Craft wrote: Ok, now the modem is initializing (after applying 3 patches from Jonas), I get this seg fault in ofonod when I run the "enable-modem" test script: See https://lists.ofono.org/pipermail/ofono/2017-May/017311.html Regards, -Denis ___ ofono mailing list ofono@ofono.org https://lists.ofono.org/mailman/listinfo/ofono
Re: nokia-modem (N900) not detected after migration to udevng
Ok, now the modem is initializing (after applying 3 patches from
Jonas), I get this seg fault in ofonod when I run the "enable-modem" test
script:
ofonod[1502]: plugins/nokia-gpio.c:phonet_status_cb() Link phonet0 (2) is up
ofonod[1502]: plugins/nokia-gpio.c:gpio_write() ("cmt_rst_rq", "inactive")
ofonod[1502]: plugins/nokia-gpio.c:gpio_power_state_machine()
(POWER_EVENT_PHONET_LINK_UP) @ state POWER_STATE_NONE
ofonod[1502]: plugins/n900.c:n900_enable() modem=0x586ad0 with 0x586cd0
ofonod[1502]: plugins/nokia-gpio.c:gpio_power_state_machine() (POWER_EVENT_ON)
@ state POWER_STATE_NONE
ofonod[1502]: plugins/nokia-gpio.c:gpio_power_set_state()
(POWER_STATE_ON_STARTED) at (POWER_STATE_NONE)
ofonod[1502]: plugins/nokia-gpio.c:gpio_start_modem_power_on()
ofonod[1502]: plugins/nokia-gpio.c:gpio_write() ("cmt_apeslpx", "inactive")
ofonod[1502]: plugins/nokia-gpio.c:gpio_write() ("cmt_rst_rq", "inactive")
ofonod[1502]: plugins/nokia-gpio.c:gpio_write() ("cmt_en", "inactive")
ofonod[1502]: plugins/nokia-gpio.c:gpio_write() ("cmt_bsi", "inactive")
ofonod[1502]: plugins/nokia-gpio.c:gpio_write() ("cmt_rst", "inactive")
ofonod[1502]: plugins/nokia-gpio.c:gpio_write() ("cmt_en", "active")
ofonod[1502]: plugins/nokia-gpio.c:gpio_write() ("cmt_rst", "active")
ofonod[1502]: plugins/nokia-gpio.c:gpio_write() ("cmt_rst_rq", "active")
ofonod[1502]: plugins/n900.c:n900_power_cb() power state POWER_STATE_ON_STARTED
ofonod[1502]: plugins/nokia-gpio.c:phonet_status_cb() Link phonet0 (2) is down
ofonod[1502]: plugins/nokia-gpio.c:gpio_power_state_machine()
(POWER_EVENT_PHONET_LINK_DOWN) @ state POWER_STATE_ON_STARTED
ofonod[1502]: plugins/nokia-gpio.c:phonet_status_cb() Link phonet0 (2) is up
ofonod[1502]: plugins/nokia-gpio.c:gpio_write() ("cmt_rst_rq", "inactive")
ofonod[1502]: plugins/nokia-gpio.c:gpio_power_state_machine()
(POWER_EVENT_PHONET_LINK_UP) @ state POWER_STATE_ON_STARTED
ofonod[1502]: plugins/nokia-gpio.c:gpio_power_set_state() (POWER_STATE_ON) at
(POWER_STATE_ON_STARTED)
ofonod[1502]: plugins/nokia-gpio.c:gpio_finish_modem_power_on()
ofonod[1502]: plugins/nokia-gpio.c:gpio_write() ("cmt_en", "inactive")
ofonod[1502]: plugins/nokia-gpio.c:gpio_power_set_state() Power on
ofonod[1502]: plugins/n900.c:n900_power_cb() power state POWER_STATE_ON
ofonod[1502]: plugins/n900.c:mtc_reachable_cb() QSO: PN_MTC [0x15] v018.000
ofonod[1502]: plugins/n900.c:mtc_query_cb() Modem state:
current=MTC_RF_INACTIVE (0x0A) target=MTC_RF_INACTIVE (0x0A)
ofonod[1502]: plugins/n900.c:report_powered() Powered on
ofonod[1502]: examples/emulator.c:powered_watch() Adding modem 0x586ad0 to the
list
ofonod[1502]: examples/emulator.c:create_tcp() Created server_watch: 40
ofonod[1502]: examples/emulator.c:create_tcp() Created server_watch: 41
ofonod[1502]: src/modem.c:modem_change_state() old state: 0, new state: 1
ofonod[1502]: plugins/n900.c:n900_pre_sim() (0x586ad0) with phonet0
ofonod[1502]: drivers/isimodem/sim.c:sim_reachable_cb() QSO: PN_SIM [0x09]
v-01.-01
ofonod[1502]: drivers/isimodem/devinfo.c:reachable_cb() QSO: PN_PHONE_INFO
[0x1B] v008.005
ofonod[1502]: drivers/isimodem/audio-settings.c:isi_call_verify_cb() QSO:
PN_CALL [0x01] v007.020
ofonod[1502]: drivers/isimodem/voicecall.c:pn_call_verify_cb() QSO: PN_CALL
[0x01] v007.020
ofonod[1502]: drivers/isimodem/voicecall.c:pn_modem_call_verify_cb()
PN_MODEM_CALL not reachable, removing client
ofonod[1502]: src/sim.c:ofono_sim_add_state_watch() 0x57dfe0
ofonod[1502]: src/sim.c:ofono_sim_add_state_watch() 0x57dfe0
ofonod[1502]: src/sim.c:ofono_sim_add_state_watch() 0x57dfe0
ofonod[1502]: src/sim.c:ofono_sim_add_state_watch() 0x57dfe0
ofonod[1502]: src/sim.c:ofono_sim_add_state_watch() 0x57dfe0
ofonod[1502]: drivers/isimodem/sim.c:sim_resp_status() Request failed:
SIM_SERV_SIM_NOT_INITIALISED
ofonod[1502]: drivers/isimodem/sim.c:sec_state_resp_cb()
SEC_STATE_RESP(cause=0x7)
ofonod[1502]: drivers/isimodem/sim.c:sim_ind_cb()
ofonod[1502]: drivers/isimodem/sim.c:sim_ind_cb()
ofonod[1502]: drivers/isimodem/sim.c:sim_ind_cb()
ofonod[1502]: drivers/isimodem/sim.c:sim_ind_cb()
ofonod[1502]: drivers/isimodem/sim.c:sim_ind_cb()
ofonod[1502]: drivers/isimodem/sim.c:sim_ind_cb()
ofonod[1502]: drivers/isimodem/sim.c:sim_ind_cb()
ofonod[1502]: drivers/isimodem/sim.c:sim_ind_cb()
ofonod[1502]: drivers/isimodem/sim.c:sim_ind_cb()
ofonod[1502]: drivers/isimodem/sim.c:sim_ind_cb()
ofonod[1502]: drivers/isimodem/sim.c:sim_server_ready_ind_cb()
ofonod[1502]: drivers/isimodem/sim.c:sim_ind_cb()
ofonod[1502]: drivers/isimodem/sim.c:sim_set_passwd_state() new state "none"
ofonod[1502]: Interface org.ofono.AllowedAccessPoints not found on the
interface_list
ofonod[1502]: drivers/isimodem/sim.c:isi_query_locked()
ofonod[1502]: drivers/isimodem/sim.c:isi_query_locked()
ofonod[1502]: drivers/isimodem/sim.c:isi_query_locked()
ofonod[1502]: drivers/isimodem/sim.c:sim_ind_cb()
ofonod[1502]: drivers/isimodem/sim.c:sim_ind_cb()
ofonod[1502]: drivers/isimodem/sim.c:sim_ind_cb()
ofonod[1502]:
Re: nokia-modem (N900) not detected after migration to udevng
Ok so after applying the two patches submitted by Jonas, I can get a
little further, but it appears that init is still failing:
ofonod[12522]: plugins/udevng.c:create_modem()
/sys/devices/platform/6800.ocp/48058000.ssi-controller/ssi0/port0/n900-modem
ofonod[12522]: plugins/udevng.c:create_modem() driver=n900
ofonod[12522]: src/modem.c:ofono_modem_create() name: (null), type: n900
ofonod[12522]: plugins/udevng.c:destroy_modem()
/sys/devices/platform/6800.ocp/48058000.ssi-controller/ssi0/port0/n900-modem
ofonod[12522]: src/modem.c:ofono_modem_remove() 0x622770
ofonod[12522]: src/private-network.c:ofono_private_network_driver_register()
driver: 0x60f334, name: Example Private Network Driver
After poking around in gdb, I've determined that this condition is failing:
from setup_isi_modem in plugins/udevng.c:
if (g_strcmp0(udev_device_get_subsystem(info->dev), "net") != 0)
It looks like the modem->serial object does not have any valid data. The
cstrings in that struct contain gibberish. info->dev is NULL, and other
info members are not valid strings and definitely do not represent what they
should. I added a DBG() print of them here to demonstrate:
ofonod[12905]: plugins/udevng.c:setup_isi_serial() **devpath: `aX, devnode:
(null), subsystem: X
Patches applied so far:
https://lists.ofono.org/pipermail/ofono/2017-September/017463.html
https://lists.ofono.org/pipermail/ofono/2017-September/017465.html
-Clayton
On Fri, Sep 08, 2017 at 04:12:25AM +0200, Jonas Bonn wrote:
On 09/08/2017 03:38 AM, Clayton Craft wrote:
Here's the info you requested, please let me know if I can gather
anything else to help!
OK, good. It's not a driver issue in any case. Now we need to figure
out why ofono is rejecting the device. The debug output from ofonod
would be useful. Try running ofono as:
ofonod -d -n
and paste the output here.
/Jonas
localhost:/home/user# udevadm info --query all --path
/sys/bus/hsi/devices/n900-modem
P: /devices/platform/6800.ocp/48058000.ssi-controller/ssi0/port0/n900-modem
E:
DEVPATH=/devices/platform/6800.ocp/48058000.ssi-controller/ssi0/port0/n900-modem
E: DRIVER=nokia-modem
E: MODALIAS=hsi:n900-modem
E: OFONO_DRIVER=n900
E: OFONO_ISI_ADDRESS=108
E: OF_COMPATIBLE_0=nokia,n900-modem
E: OF_COMPATIBLE_N=1
E:
OF_FULLNAME=/ocp@6800/ssi-controller@48058000/ssi-port@4805a000/hsi-client
E: OF_NAME=hsi-client
E: SUBSYSTEM=hsi
E: USEC_INITIALIZED=337086386
localhost:/home/user# udevadm info --attribute-walk --path
/sys/bus/hsi/devices/n900-modem
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device
'/devices/platform/6800.ocp/48058000.ssi-controller/ssi0/port0/n900-modem':
KERNEL=="n900-modem"
SUBSYSTEM=="hsi"
DRIVER=="nokia-modem"
looking at parent device
'/devices/platform/6800.ocp/48058000.ssi-controller/ssi0/port0':
KERNELS=="port0"
SUBSYSTEMS==""
DRIVERS==""
looking at parent device
'/devices/platform/6800.ocp/48058000.ssi-controller/ssi0':
KERNELS=="ssi0"
SUBSYSTEMS==""
DRIVERS==""
looking at parent device
'/devices/platform/6800.ocp/48058000.ssi-controller':
KERNELS=="48058000.ssi-controller"
SUBSYSTEMS=="platform"
DRIVERS=="omap_ssi"
ATTRS{driver_override}=="(null)"
looking at parent device '/devices/platform/6800.ocp':
KERNELS=="6800.ocp"
SUBSYSTEMS=="platform"
DRIVERS=="omap_l3_smx"
ATTRS{driver_override}=="(null)"
looking at parent device '/devices/platform':
KERNELS=="platform"
SUBSYSTEMS==""
DRIVERS==""
-Clayton
On Fri, Sep 08, 2017 at 03:29:27AM +0200, Jonas Bonn wrote:
On 09/08/2017 03:17 AM, Clayton Craft wrote:
This is on HSI bus. I am running ofono on the N900 (not tethering).
OK, from what I understand, you should be able to find this device
under /sys/class/net/
See if you can find the device there and run:
udevadm info --query all --path /sys/class/net/
and
udevadm info --attribute-walk --path /sys/class/net.
Post that output here if it's sane so that we can see what info
udev is giving you for the device.
/Jonas
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
Re: nokia-modem (N900) not detected after migration to udevng
On 09/08/2017 03:38 AM, Clayton Craft wrote:
Here's the info you requested, please let me know if I can gather
anything else to help!
OK, good. It's not a driver issue in any case. Now we need to figure
out why ofono is rejecting the device. The debug output from ofonod
would be useful. Try running ofono as:
ofonod -d -n
and paste the output here.
/Jonas
localhost:/home/user# udevadm info --query all --path
/sys/bus/hsi/devices/n900-modem
P:
/devices/platform/6800.ocp/48058000.ssi-controller/ssi0/port0/n900-modem
E:
DEVPATH=/devices/platform/6800.ocp/48058000.ssi-controller/ssi0/port0/n900-modem
E: DRIVER=nokia-modem
E: MODALIAS=hsi:n900-modem
E: OFONO_DRIVER=n900
E: OFONO_ISI_ADDRESS=108
E: OF_COMPATIBLE_0=nokia,n900-modem
E: OF_COMPATIBLE_N=1
E:
OF_FULLNAME=/ocp@6800/ssi-controller@48058000/ssi-port@4805a000/hsi-client
E: OF_NAME=hsi-client
E: SUBSYSTEM=hsi
E: USEC_INITIALIZED=337086386
localhost:/home/user# udevadm info --attribute-walk --path
/sys/bus/hsi/devices/n900-modem
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device
'/devices/platform/6800.ocp/48058000.ssi-controller/ssi0/port0/n900-modem':
KERNEL=="n900-modem"
SUBSYSTEM=="hsi"
DRIVER=="nokia-modem"
looking at parent device
'/devices/platform/6800.ocp/48058000.ssi-controller/ssi0/port0':
KERNELS=="port0"
SUBSYSTEMS==""
DRIVERS==""
looking at parent device
'/devices/platform/6800.ocp/48058000.ssi-controller/ssi0':
KERNELS=="ssi0"
SUBSYSTEMS==""
DRIVERS==""
looking at parent device
'/devices/platform/6800.ocp/48058000.ssi-controller':
KERNELS=="48058000.ssi-controller"
SUBSYSTEMS=="platform"
DRIVERS=="omap_ssi"
ATTRS{driver_override}=="(null)"
looking at parent device '/devices/platform/6800.ocp':
KERNELS=="6800.ocp"
SUBSYSTEMS=="platform"
DRIVERS=="omap_l3_smx"
ATTRS{driver_override}=="(null)"
looking at parent device '/devices/platform':
KERNELS=="platform"
SUBSYSTEMS==""
DRIVERS==""
-Clayton
On Fri, Sep 08, 2017 at 03:29:27AM +0200, Jonas Bonn wrote:
On 09/08/2017 03:17 AM, Clayton Craft wrote:
This is on HSI bus. I am running ofono on the N900 (not tethering).
OK, from what I understand, you should be able to find this device
under /sys/class/net/
See if you can find the device there and run:
udevadm info --query all --path /sys/class/net/
and
udevadm info --attribute-walk --path /sys/class/net.
Post that output here if it's sane so that we can see what info udev
is giving you for the device.
/Jonas
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@ofono.org
https://lists.ofono.org/mailman/listinfo/ofono
___
ofono mailing list
ofono@ofono.org
https://lists.ofono.org/mailman/listinfo/ofono
___
ofono mailing list
ofono@ofono.org
https://lists.ofono.org/mailman/listinfo/ofono
___
ofono mailing list
ofono@ofono.org
https://lists.ofono.org/mailman/listinfo/ofono
___
ofono mailing list
Re: nokia-modem (N900) not detected after migration to udevng
Here's the info you requested, please let me know if I can gather
anything else to help!
localhost:/home/user# udevadm info --query all --path
/sys/bus/hsi/devices/n900-modem
P: /devices/platform/6800.ocp/48058000.ssi-controller/ssi0/port0/n900-modem
E:
DEVPATH=/devices/platform/6800.ocp/48058000.ssi-controller/ssi0/port0/n900-modem
E: DRIVER=nokia-modem
E: MODALIAS=hsi:n900-modem
E: OFONO_DRIVER=n900
E: OFONO_ISI_ADDRESS=108
E: OF_COMPATIBLE_0=nokia,n900-modem
E: OF_COMPATIBLE_N=1
E:
OF_FULLNAME=/ocp@6800/ssi-controller@48058000/ssi-port@4805a000/hsi-client
E: OF_NAME=hsi-client
E: SUBSYSTEM=hsi
E: USEC_INITIALIZED=337086386
localhost:/home/user# udevadm info --attribute-walk --path
/sys/bus/hsi/devices/n900-modem
Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.
looking at device
'/devices/platform/6800.ocp/48058000.ssi-controller/ssi0/port0/n900-modem':
KERNEL=="n900-modem"
SUBSYSTEM=="hsi"
DRIVER=="nokia-modem"
looking at parent device
'/devices/platform/6800.ocp/48058000.ssi-controller/ssi0/port0':
KERNELS=="port0"
SUBSYSTEMS==""
DRIVERS==""
looking at parent device
'/devices/platform/6800.ocp/48058000.ssi-controller/ssi0':
KERNELS=="ssi0"
SUBSYSTEMS==""
DRIVERS==""
looking at parent device
'/devices/platform/6800.ocp/48058000.ssi-controller':
KERNELS=="48058000.ssi-controller"
SUBSYSTEMS=="platform"
DRIVERS=="omap_ssi"
ATTRS{driver_override}=="(null)"
looking at parent device '/devices/platform/6800.ocp':
KERNELS=="6800.ocp"
SUBSYSTEMS=="platform"
DRIVERS=="omap_l3_smx"
ATTRS{driver_override}=="(null)"
looking at parent device '/devices/platform':
KERNELS=="platform"
SUBSYSTEMS==""
DRIVERS==""
-Clayton
On Fri, Sep 08, 2017 at 03:29:27AM +0200, Jonas Bonn wrote:
On 09/08/2017 03:17 AM, Clayton Craft wrote:
This is on HSI bus. I am running ofono on the N900 (not tethering).
OK, from what I understand, you should be able to find this device
under /sys/class/net/
See if you can find the device there and run:
udevadm info --query all --path /sys/class/net/
and
udevadm info --attribute-walk --path /sys/class/net.
Post that output here if it's sane so that we can see what info udev
is giving you for the device.
/Jonas
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@ofono.org
https://lists.ofono.org/mailman/listinfo/ofono
___
ofono mailing list
ofono@ofono.org
https://lists.ofono.org/mailman/listinfo/ofono
___
ofono mailing list
ofono@ofono.org
https://lists.ofono.org/mailman/listinfo/ofono
___
ofono mailing list
ofono@ofono.org
https://lists.ofono.org/mailman/listinfo/ofono
___
ofono mailing list
ofono@ofono.org
https://lists.ofono.org/mailman/listinfo/ofono
Re: nokia-modem (N900) not detected after migration to udevng
On 09/08/2017 03:17 AM, Clayton Craft wrote: This is on HSI bus. I am running ofono on the N900 (not tethering). OK, from what I understand, you should be able to find this device under /sys/class/net/ See if you can find the device there and run: udevadm info --query all --path /sys/class/net/ and udevadm info --attribute-walk --path /sys/class/net. Post that output here if it's sane so that we can see what info udev is giving you for the device. /Jonas 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@ofono.org https://lists.ofono.org/mailman/listinfo/ofono ___ ofono mailing list ofono@ofono.org https://lists.ofono.org/mailman/listinfo/ofono ___ ofono mailing list ofono@ofono.org https://lists.ofono.org/mailman/listinfo/ofono ___ ofono mailing list ofono@ofono.org https://lists.ofono.org/mailman/listinfo/ofono
Re: nokia-modem (N900) not detected after migration to udevng
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@ofono.org https://lists.ofono.org/mailman/listinfo/ofono ___ ofono mailing list ofono@ofono.org https://lists.ofono.org/mailman/listinfo/ofono ___ ofono mailing list ofono@ofono.org https://lists.ofono.org/mailman/listinfo/ofono
Re: nokia-modem (N900) not detected after migration to udevng
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@ofono.org https://lists.ofono.org/mailman/listinfo/ofono ___ ofono mailing list ofono@ofono.org https://lists.ofono.org/mailman/listinfo/ofono
