Am 29.03.2013 19:51, schrieb Mick:
> ifconfig should show a new device has been activated.
>
> Yes?
see below ...
>> When I rmmod them all and plug in again, I get "option" loaded
>> again. Should I remove this one from my .config?
>>
>> Even when I rmmod option, modprobe qmi_wwan and then plugin
>> "option" gets loaded (and no "mobile broadband" in NM).
>
> I would get NM troubleshooted after the device is recognised by the
> kernel and the relevant modules are loaded.
>
>
>> Could it be related to our friend systemd which renames "wwan0"
>> to "wwp0s26u1u1i1" according to dmesg?
>
> I thought that this is a udev issue, rather than systemd.
Sure, udev.
I don't know
> anything about systemd (not tried it yet) and on a stable Gentoo
> install you should be able to see the wwan0 device in ifconfig.
I get no wwan0 but this:
# ifconfig wwp0s26u1u2i1
wwp0s26u1u2i1: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 0c:5b:8f:27:9a:64 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Just read the posting by Diego Petteno on this issue:
http://blog.flameeyes.eu/2013/03/predictably-non-persistent-names
> PS. I should also say that I don't use NM on my machines ... so
> someone else should hopefully be able to help with NM issues. I
> use symlinks in /etc/init.d/ for my NICs.
NM sometimes is very comfortable on notebooks etc. ... so why not ...
I don't know if NM *should* detect that fuzzy interface-name now ...
maybe I should do some udev-rule to get wwan0 back? At least for a test.
Stefan
