Updated USB Modeswitch OR WWAN0?

[Juanito]

When I start the dbus daemon the status reports that it has started..

[onelife]

I also don't want to side track from the modem - but noticed this in dmesg - Doesn't look good - But maybe it's fine?

Code: [Select]

[   17.611855] cfg80211: Problem loading in-kernel X.509 certificate (-22)
[   17.612030] cfg80211: failed to load regulatory.db

[Juanito]

That loads correctly for me, what exact version of piCore are you using on which RPi?

[onelife]

Code: [Select]

processor : 0
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4

processor : 1
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4

processor : 2
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4

processor : 3
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4

Hardware : BCM2835
Revision : a020d3
Serial : 0000000058da172e
Model : Raspberry Pi 3 Model B Plus Rev 1.3

snb@snb:~$ version
13.0.3

snb@snb:~$ uname -a
Linux snb 5.10.16-piCore-v7 #1 SMP Tue Feb 16 19:08:42 UTC 2021 armv7l GNU/Linux

[Juanito]

After some more checking, modemmanager needed org.freedesktop.ModemManager1.conf and networkmanager to be running in oder to work - networkmanager was broken by an update to nettle, so nettle7 has been added to its dep file.

With the updated modemmanager and networkmanager:

without networkmanager running:

Code: [Select]

$ mmcli -L
error: couldn't find the ModemManager process in the bus
with networkmanager running:

Code: [Select]

$ mmcli -L
No modems were found

[Juanito]

..which is to be expected without a modem to test (testing done with an RPi3 using piCore-13.0.3).

What is not clear is why you cannot start the dbus daemon and why you believe the usb-modeswitch extensions are not the most recent versions.

[Rich]

Hi Juanito

... why you believe the usb-modeswitch extensions are not the most recent versions.

In reply #17 he said he ran  "usb_modeswitch -e"  which reported  "Version 2.1.0 (C) Josua Dietze 2013".

Then in reply #20 he said:

So seems modeswitch is correct so something else ...

So maybe he then updated his extensions.

[Juanito]

That's what's confusing - usb-modeswitch wasn't in the repo before, and now:

Code: [Select]

$ usb_modeswitch -e

 * usb_modeswitch: handle USB devices with multiple modes
 * Version 2.6.0 (C) Josua Dietze 2017
 * Based on libusb1/libusbx

 ! PLEASE REPORT NEW CONFIGURATIONS !


[Rich]

Hi Juanito
Maybe he found it in one of the older repos?

[onelife]

seems the internal server error is stopping me from posting

trying an attachment instead.

[onelife]

I'm really just poking at what I have no idea of how it works - but in trying a manual start I get this :

Code: [Select]

snb@snb:~$ sudo dbus-daemon --system
Failed to start message bus: Could not get UID and GID for username "tc"
I deleted the tc user as no need so now somehow dbus only wants that user?

[onelife]

So I modified :

Code: [Select]

/usr/local/share/dbus-1/system.conf
And now a bit closer maybe as dbus says running :

Code: [Select]

snb@snb:~$ sudo /usr/local/etc/init.d/dbus status

dbus is running.
But I still get :

Code: [Select]

snb@snb:~$ mmcli -L
error: couldn't find the ModemManager process in the bus
Is not having the TC user now going to break this?

[Paul_123]

Yes, the dbus configuration defaults to using the user tc, so if your system does not have tc, then you need to change any config that references user tc

You will need to make sure those configuration files are backed up, as the defaults will no longer work for you.


I would highly recommend you start over with a default image.   Leave the username as tc.  Don't change that until you understand how things work.

[Juanito]

Note also, that when testing, networkmanager needed to be running for modemmanager to work.

The above shouldn't be the case, but it's not obvious why...