Hello
the device called:
Telekom Speedstick LTE II
Alcatel Alcatel One Touch L100V LTE
an may be more.
With the ID
idVendor=1bbb, idProduct=f017 (cdrom-dummy)
and after
eject /dev/sr0
idVendor=1bbb, idProduct=011e (network-mode)
works well with option and qmi_wwan .
echo "1bbb 011e" > /s
> Telekom Speedstick LTE II
> Alcatel Alcatel One Touch L100V LTE
only for completeness of data/infos:
the device works in UMTS/HSPA mode also with IPv6
Thomas
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majo
Is this device here the same?:
http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=3&t=942&hilit=tp+link+hsupa+2357
If, yes. I am a little confused about the three device IDs:
2357:f006
2357:0200
2357:0201
If you like try "option", "qmi_wwan" and post the results.
Regards,
Thomas
--
Am 09.01.2013 09:54, schrieb hockseng leow:
I got the dmesg after having the parameters, usbserial.vendor=0x2357
> usbserial.product=0x0200" in the linux start-up.
That looks not very nice.
> I already got the modem working under usb_modeswitch.
What about other people with the same devi
Am Mittwoch, 9. Januar 2013, 22:24:14 schrieben Sie:
> > No further work need to be done in the kernel.
>
> Are you able to provide the Windows .INF files from the device so we can
> determine what kernel drivers each interface of the device requires?
> Basically, instead of modeswitching the dev
Here are all infos about this device. I think I catched the relevant data.
Switching to modem/network-mode works with
eject /dev/sr0
It works with "option"
/dev/ttyUSB2 has accepted at-commands
and qmi_wwan (in testcase with interface 1 instead of 0)
I was able get an IPv4- connection via qm
ly and IPv6only, without true dualstack)
works also as expected and in the same way as the huawei E398/Vodafone K5005.
Regards,
Thomas Schäfer
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,
with
http://download.opensuse.org/repositories/Kernel:/linux-
next/standard/x86_64/kernel-vanilla-3.5.rc7.next.20120720-1.1.x86_64.rpm
No one of my sticks works in qmi/wwan mode anymore. The modules seems to be
loaded, option and qmi_wwan, but the dial-in-skripts do nothing.
While removin
Am Sonntag, 22. Juli 2012, 08:54:32 schrieben Sie:
> "Thomas Schäfer" wrote:
> >with
> >
> >http://download.opensuse.org/repositories/Kernel:/linux-
> >next/standard/x86_64/kernel-vanilla-3.5.rc7.next.20120720-1.1.x86_64.rpm
> >
> >No one
Am Sonntag, 22. Juli 2012, 17:08:41 you wrote:
> Could you do a quick verification: please test if the problem
> disappear if you blacklist your serial driver (option?). If so,
> then I hope someone else can look into it. I seem to vaguely
> remember a similar report, but cannot find it right no
I tried this patch-set today, applied to linux-next-20120727.
As the RFC "Fixing usb_wwan NULL pointer dereferencing" set from yesterday it
did help to avoid oopses while unplugging the stick.
That is the good thing.
But there is still a problem - wwan0 doesn't work.
/dev/cdc-wdm0 answers t
Am Freitag, 27. Juli 2012, 20:37:38 schrieben Sie:
> Ah, right. I don't really use those scripts myself anymore. I just use
> the qmicli tool from libqmi. And I assume that works for you as well?
>
It did not. But I gave up in an early state. But this project has its own
mailing list. We ca
uname
next-20120730
I used the new feature
echo "vid pid" >/sys/bus/usb/drivers/qmi_wwan/new_id
dmesg
[ 229.784142] usb 1-2: new high-speed USB device number 3 using ehci_hcd
[ 229.919579] usb 1-2: New USB device found, idVendor=19d2, idProduct=1017
[ 229.919594] usb 1-2: New USB device st
The network connection is working via wwan1 , at least with IPv4.
The LTE speed here with 8-16Mbit/s is limited by my contract, not the device.
At the moment I have problems with IPv6, but I think this is not a problem of
the device, more a problem of my apn, which may be only accessible via 3G.
Am Donnerstag, 2. August 2012, 21:25:49 schrieben Sie:
> Hi Thomas,
>
> > At the moment I have problems with IPv6, but I think this is not a
> > problem of the device, more a problem of my apn, which may be only
> > accessible via 3G.
>
> if you are on Vodafone Germany LTE, then yes, it only gi
Now I can confirm the device works via wwan-interface with ipv6 too.
In detail: ipv6 works in 3G-mode. (umts/hspa)
My problem was: I am more and more surrounded by LTE, and I was not able to
force the device to register to the right network.
LTE and IPv6 seems to be a new topic, not for the li
Am 17.08.2012 08:38, schrieb Marcel Holtmann:
Hi Thomas,
which German operator is giving you IPv6 over LTE?
No one.
I do test with the new qmi-wwan-driver:
IPv4 at 2G/3G/4G (regular contract t-mobile)
IPv6 at 2G/3G in a test environment by vodafone
The option-driver(ppp) works for me only in
short status update:
Confirmation: the "qmi_wwan" works as expected. (/dev/cdc-wdm0 and wwan0
work)
Missing the "option" patch for /dev/ttyUSBX for at-commands/classic
ppp-connections
Thomas
dmesg
[ 110.500114] usb 1-1: new high-speed USB device number 3 using ehci_hcd
[ 110.635759] usb
Despite the patch
{ USB_DEVICE_AND_INTERFACE_INFO(ZTE_VENDOR_ID, 0x1018, 0xff, 0xff,
0xff),
.driver_info = (kernel_ulong_t)&net_intf3_blacklist },
is included in option, it has no effect.
[ 1109.116127] usb 1-4: new high-speed USB device number 3 using ehci_hcd
[ 1109.251733]
Am Dienstag, 4. September 2012, 11:21:44 schrieben Sie:
> Could you post the output of lsusb -v or /sys/kernel/debug/usb/devices
> (with debugfs mounted) for this device?
Here they are:
dmesg
lsusb
/sys/kernel/debug/usb/devices
[ 1080.264122] usb 1-4: new high-speed USB device number 3 usi
The P4200 has two IDs, one for CD-Mode, one for modemmode.
cd
VID 0x106c PID 0x3b14
modem
VID 0x106c PID 0x3721
eject /dev/sr0 does work for switching.
This (stolen from similar device)
usb_modeswitch -v 0x106c -p 0x3b14 -M
"5553424312345678240088ff02444556434847"
did
Am Sonntag, 30. Juni 2013, 00:35:20 schrieben Sie:
> > But the usb id says a different story:
> > Bus 003 Device 023: ID 12d1:1506 Huawei Technologies Co., Ltd. E398
> > LTE/UMTS/GSM Modem/Networkcard
> >
> > But this hardware in particular doesn't support LTE.
>
> Huawei reuse device IDs. 12d1
Am Montag, 1. Juli 2013, 00:37:14 schrieben Sie:
> Hi!
> I'm trying to investigate on the Huawei E3131 wwan interface -
Is the E3131 an HILINK-Modem?
Have you tried simply starting dhcp/automatic-configuration?
Open a Browser to get connected.
If dns-redirection doesn't work, try the router o
Am Sonntag, 11. August 2013, 15:08:26 schrieben Sie:
> Hello,
..
> 1. Smartfren xStream e781a with vid 0x1bbb and pid 0x0106
> 2. Smartfren AC682 with vid 0x19d2 and pid 0xffdd
> I have tested those modems. They run perfectly with option usb serial
> driver (/sys/bus/usb-serial/drivers/option1/new_
Am 01.10.2013 13:27, schrieb edison...@fa.sg:
Hi,
Please help me to add the driver on my TP-Link device based on the
dmesg log below.
Ok, this is an TP-link MA260.
option and qmi_wwan Kernel-modules work with that device.
You should not try to load usbserial. May be you did it or a wrong s
Hi Edison,
we should start again.
You are using ubuntu 12?
Is it right, that your kernel-version is 3.2.0-30 ?
(uname -a )
I am not sure, but in this case you can forget qmi and you can focus on
"option".
In your first mail usb-switch did work correctly.
you should see 2357:f000 directly
Hi,
The vodafone K5150 is a LTE device, default is "hilink" mode.
This works under Linux 3.7 in the same way as it under windows vista does.
[ 248.255172] usb 1-1: new high-speed USB device number 3 using ehci_hcd
[ 248.518600] usb 1-1: New USB device found, idVendor=12d1, idProduct=1f16
[ 248.51
Am Montag, 7. Oktober 2013, 16:04:49 schrieben Sie:
> Have you verified that the latest version of usb-modeswitch doesn't fix
> this issue? I think I've seen reports that it does, but it would be
> good if you could test that out and verify it.
May be it is intention. Under win8 it does not chan
hpmini:~ # usb_modeswitch -j -v 12d1 -p 1f16
Search USB devices...
Found device, searching for MBIM configuration...
2
hpmini:~ # usb_modeswitch -W -j -v 12d1 -p 1f16
Taking all parameters from the command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.5 (C) Josua D
Am 09.10.2013 09:03, schrieb Bjørn Mork:
>modprobe cdc_mbim
>echo "12d1 1f16" > /sys/bus/usb/drivers_mbim/new_id
>
>has had no effect.
Well, it shouldn't have any effect. The driver should already be
autoloaded based on the class. Is it not? Does the probe fail?
The driver is not already lo
Am Mittwoch, 9. Oktober 2013, 10:50:38 schrieben Sie:
> Could you mount debugfs and send the relevant part of
> /sys/kernel/debug/usb/devices ? I'd like to verify which configuration
> and altsettings are currently active
>
(1 and 2 before and after plug in of the device)
diff -u 1.txt 2.txt
-
> OK, so it didn't switch at all. Then we are back to usb_modeswitch
> failure (or more likely: missing config for this device).
>
> You could test switching it manually:
>
> echo 2 > /sys/bus/usb/devices/1-2/bConfigurationValue
This was the point!
[ 4007.213187] usb 1-2: new high-speed US
Hi Bjørn,
I can't answer your Questions.
Do you recommend / know a usb-sniffer for Win8?
In the meantime, I have got the first ipv4-connection:
hpmini:~ # mbim-network /dev/cdc-wdm0 start
Loading profile...
APN: internet.telekom
Querying subscriber ready status 'mbimcli -d /dev/cdc-wdm0 --
Bjørn writes:
>
> > In the meantime, I have got the first ipv4-connection:
> Yes, that should work.
12d1 1f16 conf 2
Unfortunately IPv6 does only work one way. (no firewall)
ModemManager/mmcli works - connected
slaac - ok - address and default-route are there
ping6 ???
packets go out, th
Bjørn writes:
> Could be the driver. I don't know if it is ever tested with IPv6, and
> it does a bit of header magic so it is possible to screw up. Of course,
> the same goes for the firmware (including the testing, i assume :-)
>
> usbmon dumps would be interesting.
I attached a file, I am
Am Samstag, 12. Oktober 2013, 13:46:19 schrieb Bjørn Mork:
> > happens:
> > ifconfig wwan0 arp
>
> Nope, that won't make any difference. At least on a proper ethernet
> interface we still answer NS for our addresses, even if we disable
> sending them.
>
> So the questions still are: Do you se
Am Samstag, 12. Oktober 2013, 13:46:19 schrieben Sie:
> So the questions still are: Do you see those solicitatins going from the
> driver to the IP layer? And do you see any Neighbor Advertisement
> replies from the IP layer? If the respective answers are yes/no, then
> you should look elsewhere
Am Mittwoch, 9. Oktober 2013, 23:29:49 schrieb Bjørn Mork:
> >> will show you a number of interesting debug sites which can be enabled
> >> without rebuilding anything. See Documentation/dynamic-debug-howto.txt
> >> for details on how to use this.
>
I played a little bit with it, but there are
Hi,
I have some news about this device. Under Windows 8.1 (6.3)(testversion)
with these IDs:
USB\VID_12D1&PID_1F16&REV_0102&MI_00
USB\VID_12D1&PID_1F16&MI_00
USB\Class_02&SubClass_0e&Prot_00
USB\Class_02&SubClass_0e
USB\Class_02
the device works as mobile broadband device with IPv6.
So I thin
Am 24.10.2013 11:45, schrieb Bjørn Mork:
Any chance you could snoop the Windows IPv6 session? I'm interesting in
seeing the NS and NA messages. In particular any NA from Windows. Don't
need many packets, only the part where the modem tries to discover the
host "L2 address".
To answering one q
Am Donnerstag, 24. Oktober 2013, 11:45:39 schrieben Sie:
> Did you try any of the ND tuning controls on Linux? Turning on ARP
> before bringing up the interface might work on IPv6 (but fail for IPv4):
> ifconfig wwan0 arp
This solved the problem. (IPv6 positive , IPv4 at the moment untested)
Am Samstag, 26. Oktober 2013, 16:01:26 schrieben Sie:
> Thomas Schäfer writes:
> > Am Donnerstag, 24. Oktober 2013, 11:45:39 schrieben Sie:
> >> Did you try any of the ND tuning controls on Linux? Turning on ARP
> >>
> >> before bringing up the interface m
Hi Bjørn,
I tested your patch with the K5150 in mbim-mode
with ipv6 only - ok.
with Ipv4 only - ok.
I have only one mbim-device, this 5150.
Let me know, if you need further tests.
Thank you!
Regards,
Thomas
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the bod
Am Montag, 28. Oktober 2013, 09:46:30 schrieben Sie:
> The patch requires v3.12
I tried it.
It hasn't crashed, but it hasn't worked too.
Two traces are attached.
Regards,
Thomas
mbim-5150-20131029-any.pcapng.7z
Description: application/7z-compressed
mbim-5150-20131029-wwan0.pcapng.7z
Bjørn Mork writes:
> That was probably a bit too brief. What I meant was: Try changing the
> last argument to ipv6_stub->ndisc_send_na() from "false" to "true" and
> see if that makes any difference.
It made a difference. It works.
For checking en detail:
http://www.cis.uni-muenchen.de/~tho
Hi,
I know that next-kernel may not stable/work. But for your information.
I tried 3.12.0-next-20131107-1-vanilla (next repository from Suse, because
compiling needs time and patience :-))
Two devices which worked with cdc_ncm now changed to huawei_cdc_ncm. So far so
ok.
But: E5776-s-32 (loc
> >
> > The second device with problems is Huawei E3276 (Speedstick LTE III,
> > Telekom, no Hilink, but ipv6-cabable version) This device worked before
> > with SLAAC, now with -next-20131107 it doesn't.
> Ouch. I noticed after submitting this driver that it probably has some
> flawed logic wr
Hi,
> I do not have any Huawei NCM device, so I cannot really test the new
> huawei_cdc_ncm.
> A simple test would be just reverting commit 9fea037de5f3 ("net:
> cdc_ncm: remove non-standard NCM device IDs"), to make the cdc_ncm
> driver (with all the recent changes) handle this device again.
> If that still does not change anything, then I'd really appreciate it if
> you could run through (assuming the v3.11 driver was OK):
>
> git bisect start 9fea037de5f3 v3.11 -- drivers/net/usb/cdc_ncm.c
>
That failed too.
(switching was ok, compiling was ok, booting, recognizing the devic
Hi,
Yesterday I have had a access to a new notebook with built in UMTS-device.
The live-cd with kernel 3.7 tried qmi_wwan, but failed:
[ 12.115215] qmi_wwan 1-1.5:2.5: CDC functional descriptors missing
[ 12.115226] qmi_wwan: probe of 1-1.5:2.5 failed with error -1
[ 12.115244] usbcore: re
Hi,
I have it already mentioned somewhere. Sorry for duplicates.
The Huawei E5776
(normal use, classic IPv4, hilink mode (with webinterface and RFC1918 IP-
config including NAT)
worked well with 3.12 and before, but it doesn't work any more with 3.13.
At least one local branded version of th
Am 27.11.2013 13:33, schrieb Bjørn Mork:
Thomas Schäfer writes:
Hi,
I have it already mentioned somewhere. Sorry for duplicates.
The Huawei E5776
(normal use, classic IPv4, hilink mode (with webinterface and RFC1918 IP-
config including NAT)
So this is always connected and you don&#
> Am 27.11.2013 13:33, schrieb Bjørn Mork:
> > How about looking at usbmon differences? That should show us where
> > things start to go wrong.
Here are the two cases
3.12 with a short connection dhcp and ping
3.13 with failing dhcp
I hope I caught the right bus. Because of the size of fil
I collected some additional information about this device.
The windows-view:
http://www.cis.uni-muenchen.de/~thomas/pantech-p4200-usb.png
and the usbsnoop-logfile:
http://www.cis.uni-muenchen.de/~thomas/pantech-p4200-usbsnoop.log.bz2
Has anybody suggestions, what could I do next?
Regards,
Thoma
Am Mittwoch, 19. September 2012 um 20:45:26 schrieb Bjørn Mork:
> > Has anybody suggestions, what could I do next?
>
> I am wondering exactly how qmi_wwan does "not work"...
I should test more than three times. More checking, use more test-kernels,
check if modemmanger is disturbing, or other
One mysterious thing:
at&v at /dev/ttyACM via minicom
crashs/resets the modem.
Other at-command like ate, ati, c+cgdcont
work, but getting all settings via at&v fails.
Have other pantech-modems this feature too?
Thomas
--
To unsubscribe from this list: send the line "unsubscribe linux-usb
P4200: test ok:
udev/usbmodeswitch and this patch made the modem usable without user-interaction
# dmesg
[ 127.708165] usb 1-1: new high-speed USB device number 3 using ehci_hcd
[ 127.843187] usb 1-1: New USB device found, idVendor=106c, idProduct=3b14
[ 127.843201] usb 1-1: New USB device st
Am Mittwoch, 10. Oktober 2012 um 21:02:02 schrieb United Seabears Corp.:
> Hi there:
>
> I am seeking assistance with a USB Wimax modem for Sprint/Virgin Mobile
> to be used on a laptop with Kubuntu 12.04 and/or 12.10. The modem is a
> 3G/4G modem, Franklin Wireless U600 and Beceem ??? for the 4G
Hi,
the LTE-stick huawei 3276 (in Germany also alias "Telekom Speedstick
LTE III") works well with linux. (also IPv6)
Here is the output of dmesg (IPv4-connection).
at^ndisdup=1,1,"internet.telekom"
OK
^NDISSTAT:1,,,"IPV4"
[ 97.342188] usb 1-1: new high-speed USB device number 3 using
Am Freitag, 17. Mai 2013, 14:41:20 schrieben Sie:
> Thomas Schäfer writes:
> > Hi,
> >
> > the LTE-stick huawei 3276 (in Germany also alias "Telekom Speedstick
> > LTE III") works well
One thing is little mysterious.
The byte-statistics at the in
Hello Bjørn
...
TX-counter-problem
...
> This is expected as a result of the cdc_ncm <=> usbnet design.
.
>
> The buffer filling may seem strange, but Alexey has explained it several
> times here on this list. It has to do with device DMA optimizations.
> Google it or search this list if
Hi,
a short description of the situation:
focus is on IPv6
3.12:
start of Modemmanager and device plugged in
little bit waiting
then the "trick" because of arp/noarp/nd-problem: "ifconfig wwan0 arp"
mmcli --simple connect
confirmed with ok
/sbin/ip link set wwan0 up
got addresses
Hi Bjørn,
it seems to me that this patch solved some problems.
( time out )
Some other problems "introduced" in 3.13 are still there.
mbim wwan and dhcpv4 does not work (worked in 3.12) K5150
huawai ncm wwan and dhcpv4 does not work (ncm worked in 3.12) E5776
Unfortunately I can not test IPv6-b
Am 23.12.2013 08:41, schrieb Bjørn Mork:
my QMI (MC7710, E392) and MBIM (MC7710, DWM-156) modems all work
fine with v3.13-rc3 and IPv6, except for the Huawei E367 which doesn't
support IPv6 PDPs at all (at least not with the firmware revision I
have). None of the modems seem to respond to DHCPv
d be self explaining.
I am ready for further questions and/or RFT.
Regards,
Thomas Schäfer
eject /dev/sr1
may be someone finds also the usb_modeswitch-string
modprobe option
echo "19d2 0326" > /sys/bus/usb-serial/drivers/option1/new_id
AT-interfaces are to find at
/dev/t
The modem works at /dev/USB2.
In my point of view "19d2 0326" should/could be added to the option driver.
Thomas
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-i
Not for kernel-code, but usefull for testers/users:
udev-rules/usb_modeswitch
/lib/udev/rules.d/40-usb_modeswitch.rules
# ZTE MF821DO2
ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0325", RUN+="usb_modeswitch '%b/%k'"
/usr/share/usb_modeswitch/19d2:0325
# ZTE MF821DO2
DefaultVendor= 0x19
Am 09.07.2012 10:22, schrieb Oliver Neukum:
Am Sonntag, 8. Juli 2012, 13:32:42 schrieb Thomas Schäfer:
Not for kernel-code, but usefull for testers/users:
udev-rules/usb_modeswitch
/lib/udev/rules.d/40-usb_modeswitch.rules
Be careful. The expert from draisberghof told me yesterday that is
Am Montag, 9. Juli 2012, 10:25:27 schrieben Sie:
> Thomas Schäfer writes:
> > The modem works at /dev/USB2.
> posted:
> | diag 19d2:0326 MI00\6
> | nema 19d2:0326 MI01\6
> | at- 19d2:0326 MI02\6
> | modem 19d2:0326 MI03\6
> | ndis 19d2:0326 MI04\6
>
> I am
I wrote:
> Be careful. The expert from draisberghof told me yesterday that is only
> the SCSI-command for eject and
> can have collateral damage.
The latter is rubbish
I misunderstood his statement:
> http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?t=946
Sorry, for confusion.
Am 14.03.2014 10:24, schrieb Enrico Mioso:
Other than this, I do not have this device at hand, so can't see what happens.
From the version number, I expect the firmware being HiSilicon (not Qualcomm).
Try also using dhcpcd if you can / want / like :) .
Thank you.
dhcpcd doesn’t work too.
I h
Am Montag, 17. März 2014, 16:25:18 schrieben Sie:
> This is a context modified revert of commit 6a9612e2cb22
> ("net: cdc_ncm: remove ncm_parm field") which introduced
> a NCM specification violation, causing setup errors for
> some devices. These errors resulted in the device and
> host disagreein
>
> I will test also a further device(k5150), which was not working since 3.13,
> later this week.
The test was ok. The K5150 from HUAWEI/Vodafone (mbim) works again.
At least with IPv4. No statement about IPv6.
Regards,
Thomas
--
To unsubscribe from this list: send the line "unsubscribe lin
auth 9af38645 subscribe linux-usb tschae...@t-online.de
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
74 matches
Mail list logo
