On Friday 29 Mar 2013 23:40:18 Stefan G. Weichinger wrote: > Am 29.03.2013 22:40, schrieb Stefan G. Weichinger: > > Am 29.03.2013 22:03, schrieb Stefan G. Weichinger: > >> I don't know about NM's preferences ... I just assume this could be > >> the problem. > >> > >> Gotta dig up some udev-ruling for this, any quick pointers anyone? > > > > even "easier": > > > > You can change the device name using ifrename from package > > wireless_tools. > > > > Now I have device wwan0 but still NM does not care about it. > > > > I really don't want to rant ... but ... you know. > > Just an observation: > > Started a VM on my main workstation ... Windows XP inside of VMware Player. > Not even KVM or something ... > > Connected that funny stick to that very VM ... and connected to funky > internet on first try ...
Don't you loooove OS automation? Especially when it works! ;-) If you look at the device manager you will probably find different strings describing the USB device interfaces that WinXP detects/assigns compared to your Linux OS + udevd + systemd. When you tried adding the new module you should see a load more interfaces coming up in dmesg, through usbserial_generic and then cdc_wdm and qmi_wann, like this: http://www.spinics.net/lists/linux-usb/msg64061.html This guys seems to be getting 3 x ttyUSBX popping up. Once you get to this stage with an appropriate udev rule if need be, then apparently you need to emerge this: $ eix -l libqmi * net-libs/libqmi Available versions: ~ 1.0.0 [doc static-libs test] ** 9999 [doc static-libs test] Homepage: http://cgit.freedesktop.org/libqmi/ Description: QMI modem protocol helper library and see if that with its qmicli utility allows you to manage your connection. HTH. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
