Here is my output of lsusb -v, hope it helps
Bus 000 Device 001: ID 8086: Intel Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
On 2013-02-28, Maximo Pech wrote:
> The patch that Stuart provided worked for my ZTE MF668 device.
>
> I got this on dmesg:
>
> umsm0 at uhub0 port 3 configuration 1 interface 0 "ZTE,Incorporated
> ZTE HSPA Technologies MSM" rev 2.00/0.00 addr 2
> umsm0 detached
> umsm0 at uhub0 port 3 configurat
The patch that Stuart provided worked for my ZTE MF668 device.
I got this on dmesg:
umsm0 at uhub0 port 3 configuration 1 interface 0 "ZTE,Incorporated
ZTE HSPA Technologies MSM" rev 2.00/0.00 addr 2
umsm0 detached
umsm0 at uhub0 port 3 configuration 1 interface 0 "ZTE,Incorporated
ZTE HSPA Techn
It turns out that my modem is not the ZTE MF626, it is in reality the ZTE
MF668 and it works on /dev/cuaU1
2013/2/14 Kirill Bychkov
> On Thu, February 14, 2013 07:49, Kirill Bychkov wrote:
> > On Thu, February 14, 2013 06:24, Maximo Pech wrote:
> >> Hi list, I see this was asked before but never
Finally I got it to work, but strangely my device comes up on /dev/cuaU1
not on /dev/cuaU0. Still have not tested the diff though.
2013/2/14 Maximo Pech
> The AT command thing did the trick, now I have some trouble setting up
> ppp.conf, but I hope to get that sorted out.
>
> At this time I can'
The AT command thing did the trick, now I have some trouble setting up
ppp.conf, but I hope to get that sorted out.
At this time I can't test the patch, but I promise to do it later.
El miércoles, 13 de febrero de 2013, Kirill Bychkov escribió:
> On Thu, February 14, 2013 06:24, Maximo Pech wrot
On 2013-02-14, Maximo Pech wrote:
> Hi list, I see this was asked before but never got solved, so I ask again.
>
> Has someone got this device working on openbsd? Is it supported?
>
> Thanks and regards.
>
>
It is likely to work with this diff:
Index: umsm.c
=
On Thu, February 14, 2013 07:49, Kirill Bychkov wrote:
> On Thu, February 14, 2013 06:24, Maximo Pech wrote:
>> Hi list, I see this was asked before but never got solved, so I ask again.
>>
>> Has someone got this device working on openbsd? Is it supported?
>>
>> Thanks and regards.
>>
>>
> Hi. I p
On Thu, February 14, 2013 06:24, Maximo Pech wrote:
> Hi list, I see this was asked before but never got solved, so I ask again.
>
> Has someone got this device working on openbsd? Is it supported?
>
> Thanks and regards.
>
>
Hi. I plugged this modem on my Win7 notebook, installed software and driv
Hi list, I see this was asked before but never got solved, so I ask again.
Has someone got this device working on openbsd? Is it supported?
Thanks and regards.
I don't know if it is the way, but kind of works:
./umsm.c: {{ USB_VENDOR_QUALCOMM3, USB_PRODUCT_QUALCOMM3_ZTE_626 }, 0},
./usbdevs.h:#define USB_PRODUCT_QUALCOMM3_ZTE_626 0x0031 /*
ZTE-626 MSM */
./usbdevs_data.h: USB_VENDOR_QUALCOMM3, USB_PRODUCT_QUALCOMM3_ZTE_626
On Wed, Oct 14, 2009 at 10:11:20AM -0300, Giancarlo Razzolini wrote:
>>
> I do have this modem working on linux. The problem with it is that, when
> you plug it in, it is detected as a cdrom device. On linux I use a
> program called usb_modeswitch. It changes the mode of operation of the
>
On Wed, Oct 14, 2009 at 01:14:00PM -0500, Sergio Andris Gsmez del Real wrote:
> Thanks for the reply.
>
> Indeed, I use usb_modeswitch under Linux, it is, however, quite just
> for Linux, cause it reloads a certain kernel module. With GENERIC
> kernel, usb_modeswitch does not even recognize the de
Thanks for the reply.
Indeed, I use usb_modeswitch under Linux, it is, however, quite just
for Linux, cause it reloads a certain kernel module. With GENERIC
kernel, usb_modeswitch does not even recognize the device. However,
compiling it (the kernel) without umass support, that is, the device
bein
Sergio Andris Gsmez del Real escreveu:
Hi again.
Sometimes I get the following:
OpenBSD 4.5 (GENERIC.MP) #2133: Sat Feb 28 15:02:16 MST 2009
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 2143023104 (2043MB)
avail mem = 2069721088 (1973MB)
mainbus0 at root
b
Hi again.
Sometimes I get the following:
OpenBSD 4.5 (GENERIC.MP) #2133: Sat Feb 28 15:02:16 MST 2009
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 2143023104 (2043MB)
avail mem = 2069721088 (1973MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xf72
Ok, here is full output of dmesg and usbdevs -v
OpenBSD 4.5 (GENERIC.MP) #2133: Sat Feb 28 15:02:16 MST 2009
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 2143023104 (2043MB)
avail mem = 2069721088 (1973MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4 @
Read the FAQ first before switching. In your case especially part 9
And dmesg or usbdevs give every info needed.
2009/10/12 Sergio AndrC)s GC3mez del Real :
> Sorry about the duplicate, I'm not used to a mail list :(
>
> Isn't that really the relevant info? It is the generic kernel of OpenBSD
4.5
2009/10/12 Sergio Andris Gsmez del Real :
> Isn't that really the relevant info? It is the generic kernel of OpenBSD
4.5
> -release...
As a general point, if you are having a problem and you can't fix it
yourself, then by definition, you are not qualified to determine
what's relevant.
Specificall
Sorry about the duplicate, I'm not used to a mail list :(
Isn't that really the relevant info? It is the generic kernel of OpenBSD 4.5
-release...
I don't know what extra relevant info could dmesg, or usbdevs offer FOR THIS
CASE, please, if I'm wrong, or if there is an official protocol for
report
On 2009-10-12, Sergio Andr?s G?mez del Real wrote:
> Well, I guess this is the relevant output from startup:
Don't try and guess what is relevant, just send the COMPLETE dmesg.
Also send usbdevs -v.
Didn't you send something like this about a month ago?
http://www.nabble.com/HSDPA-USB-Modem-td25308434.html
If the devs don't have one, maybe you'd donate your modem temporarily
to get the support. Just asking is going to be nearly useless. If
you donate/loan the hardware, you increase your ch
Well, I guess this is the relevant output from startup:
umass0 at uhub1 port 1 configuration 1 interface 0 "ZTE, Incorporated ZTE
CDMA Technologies MSM" rev 2.00/0.00 addr 2
umass0: using ATAPI over Bulk-Only
scsibus1 at umass0: 2 targets, initiator 0
umass0: BBB reset failed, IOERROR
umass0: BBB
23 matches
Mail list logo
