sec:u Re: Huawei E220 3G devices
0n Fri, Jan 19, 2007 at 03:25:33PM +0100, Volker wrote: usbctl is part of a package called usbutil. You may download a package from the website of Bernd Walter: http://www.cosmo-project.de/~bernd/usbutil.tgz However, I don't why such a great tool isn't part of the ports tree (obsd + nbsd do have it in the tree). usbctl shows the interfaces and endpoints of a usb device. You may find a sample output of usbctl at http://bsd.vwsoft.com/3g/merlin_u740.html What is meant by endpoints of a usb device ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Huawei E220 3G devices
On 2/5/07, Jes [EMAIL PROTECTED] wrote: Hi Volker: I've got the usbctl printouts. First the 'dmesg': ucom0: HUAWEI Technologies HUAWEI Mobile, rev 1.10/0.00, addr 2 ucom0: Could not find interrupt in device_attach: ucom0 attach returned 6 ucom0: HUAWEI Technologies HUAWEI Mobile, rev 1.10/0.00, addr 2 ucom0: Could not find interrupt in device_attach: ucom0 attach returned 6 usbctl -f /dev/usb0 USB device 1: 9 USB device 2: 0 2 USB devices found DEVICE addr 1 DEVICE descriptor: bLength=18 bDescriptorType=device(1) bcdUSB=1.00 bDeviceClass=9 bDeviceSubClass=0 bDeviceProtocol=0 bMaxPacketSize=64 idVendor=0x idProduct=0x bcdDevice=100 iManufacturer=1(Intel) iProduct=2(UHCI root hub) iSerialNumber=0() bNumConfigurations=1 CONFIGURATION descriptor 0: bLength=9 bDescriptorType=config(2) wTotalLength=25 bNumInterface=1 bConfigurationValue=1 iConfiguration=0() bmAttributes=40 bMaxPower=0 mA INTERFACE descriptor 0: bLength=9 bDescriptorType=interface(4) bInterfaceNumber=0 bAlternateSetting=0 bNumEndpoints=1 bInterfaceClass=9 bInterfaceSubClass=0 bInterfaceProtocol=0 iInterface=0() ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=1-in bmAttributes=interrupt wMaxPacketSize=8 bInterval=255 current configuration 1 HUB descriptor: bDescLength=9 bDescriptorType=41 bNbrPorts=2 wHubCharacteristics=0a bPwrOn2PwrGood=50 bHubContrCurrent=0 DeviceRemovable=0 Hub status Port 1 status=0103 change= Port 2 status=0100 change= -- DEVICE addr 2 DEVICE descriptor: bLength=18 bDescriptorType=device(1) bcdUSB=1.10 bDeviceClass=0 bDeviceSubClass=0 bDeviceProtocol=0 bMaxPacketSize=64 idVendor=0x12d1 idProduct=0x1003 bcdDevice=0 iManufacturer=1(\u0c05¤) iProduct=2(\u0c05¤) iSerialNumber=0() bNumConfigurations=1 CONFIGURATION descriptor 0: bLength=9 bDescriptorType=config(2) wTotalLength=32 bNumInterface=1 bConfigurationValue=1 iConfiguration=0() bmAttributes=a0 bMaxPower=500 mA INTERFACE descriptor 0: bLength=9 bDescriptorType=interface(4) bInterfaceNumber=0 bAlternateSetting=0 bNumEndpoints=2 bInterfaceClass=8 bInterfaceSubClass=6 bInterfaceProtocol=80 iInterface=0() ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=3-in bmAttributes=bulk wMaxPacketSize=64 bInterval=0 ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=4-out bmAttributes=bulk wMaxPacketSize=64 bInterval=0 current configuration 1 -- usbctl -f /dev/usb1 USB device 1: 9 1 USB devices found DEVICE addr 1 DEVICE descriptor: bLength=18 bDescriptorType=device(1) bcdUSB=1.00 bDeviceClass=9 bDeviceSubClass=0 bDeviceProtocol=0 bMaxPacketSize=64 idVendor=0x idProduct=0x bcdDevice=100 iManufacturer=1(Intel) iProduct=2(UHCI root hub) iSerialNumber=0() bNumConfigurations=1 CONFIGURATION descriptor 0: bLength=9 bDescriptorType=config(2) wTotalLength=25 bNumInterface=1 bConfigurationValue=1 iConfiguration=0() bmAttributes=40 bMaxPower=0 mA INTERFACE descriptor 0: bLength=9 bDescriptorType=interface(4) bInterfaceNumber=0 bAlternateSetting=0 bNumEndpoints=1 bInterfaceClass=9 bInterfaceSubClass=0 bInterfaceProtocol=0 iInterface=0() ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=1-in bmAttributes=interrupt wMaxPacketSize=8 bInterval=255 current configuration 1 HUB descriptor: bDescLength=9 bDescriptorType=41 bNbrPorts=2 wHubCharacteristics=0a bPwrOn2PwrGood=50 bHubContrCurrent=0 DeviceRemovable=0 Hub status Port 1 status=0100 change= Port 2 status=0100 change= -- usbctl -f /dev/usb2 USB device 1: 9 1 USB devices found DEVICE addr 1 DEVICE descriptor: bLength=18 bDescriptorType=device(1) bcdUSB=1.00 bDeviceClass=9 bDeviceSubClass=0 bDeviceProtocol=0 bMaxPacketSize=64 idVendor=0x idProduct=0x bcdDevice=100 iManufacturer=1(Intel) iProduct=2(UHCI root hub) iSerialNumber=0() bNumConfigurations=1 CONFIGURATION descriptor 0: bLength=9 bDescriptorType=config(2) wTotalLength=25 bNumInterface=1 bConfigurationValue=1 iConfiguration=0() bmAttributes=40 bMaxPower=0 mA INTERFACE descriptor 0: bLength=9 bDescriptorType=interface(4) bInterfaceNumber=0 bAlternateSetting=0 bNumEndpoints=1 bInterfaceClass=9 bInterfaceSubClass=0 bInterfaceProtocol=0 iInterface=0() ENDPOINT descriptor: bLength=7 bDescriptorType=endpoint(5) bEndpointAddress=1-in bmAttributes=interrupt wMaxPacketSize=8 bInterval=255 current configuration 1 HUB descriptor: bDescLength=9 bDescriptorType=41 bNbrPorts=2 wHubCharacteristics=0a bPwrOn2PwrGood=50 bHubContrCurrent=0 DeviceRemovable=0 Hub status Port 1 status=0100 change= Port 2 status=0100 change= -- usbctl -f /dev/usb3 USB device 1: 9 1 USB devices found DEVICE addr 1 DEVICE descriptor: bLength=18 bDescriptorType=device(1) bcdUSB=2.00 bDeviceClass=9 bDeviceSubClass=0 bDeviceProtocol=1 bMaxPacketSize=64 idVendor=0x idProduct=0x bcdDevice=100 iManufacturer=1(Intel) iProduct=2(EHCI root hub) iSerialNumber=0()
Re: Huawei E220 3G devices
Hi Joao and everybody: I hacked ubsa as well before posting in this list with no positive result. My system do not detect any serial port. I'm very frustrated with this issue because I can't use the modem in FreeBSD... an Option HSDPA pcmcia doesn't work too... very very disappointed... Thanks, greetings, Jes On Wed, 14 Feb 2007 16:11:21 + Joao Barros [EMAIL PROTECTED] wrote: Hi all, Sorry for my late coment on this, but after getting a new Macbook Pro I got distracted ;) In December I was looking into this and (I'm talking out of my head now) after I patched ubsa with this device IDs I got it to be detected, although it only connects to one of the two serial devices present, the modem one I think. From what I recall I was able to register the device to the network by sending the PIN command through the modem port but after using a software usb sniffer in windows I noticed that this command and others (network status maybe) are sent using the 2nd serial port. If this is correct, the PIN command can be sent through the normal dialup script, with a pause before the dialing attempt to let the device register. Of course after the device is registered this is unnecessary and time consuming. I'm thinking of doing a small daemon where you just need to configure the 2nd serial port and the PIN and it takes cares of registering the device on the network, monitor network status, signal strength,etc. The Vodafone OSX driver+App does this, contrary to the I'm on/off Windows App so if anyone knows a USB data software sniffer for OSX I could get the reverse engineer the commands . Of course, this will only work if the 2nd serial port gets usable in FreeBSD. This small app can then be used to drive more 3G cards which I guess some people would welcome :) ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Huawei E220 3G devices
Hi: I have not such 'usbctl'... What is 'usbctl'? only 'usbdevs' and usbhidctl... and this, usbhidctl, is not very useful I guess... so... I put /var/log/messages and 'usbdevs'. Note that I haven't 'usbmass' in my kernel; it's compiled as a module and not loaded. Then the huawei modem cannot be interpreted as a mass-storage devices can it? /var/log/messages: Dec 18 16:50:10 barbikane kernel: ucom0: HUAWEI Technologies HUAWEI Mobile, rev 1.10/0.00, addr 2 Dec 18 16:50:10 barbikane kernel: ucom0: Could not find interrupt in Dec 18 16:50:10 barbikane kernel: device_attach: ucom0 attach returned 6 Dec 18 16:50:10 barbikane kernel: ucom0: HUAWEI Technologies HUAWEI Mobile, rev 1.10/0.00, addr 2 Dec 18 16:50:10 barbikane kernel: ucom0: Could not find interrupt in Dec 18 16:50:10 barbikane kernel: device_attach: ucom0 attach returned 6 usbdevs -v [EMAIL PROTECTED] usbdevs addr 1: UHCI root hub, Intel addr 1: UHCI root hub, Intel addr 2: HUAWEI Mobile, HUAWEI Technologies addr 1: UHCI root hub, Intel addr 2: ELECOM USB mouse with wheel, ELECO addr 1: EHCI root hub, Intel [EMAIL PROTECTED] usbdevs -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 powered port 2 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 addr 2: full speed, power 500 mA, config 1, HUAWEI Mobile(0x1003), HUAWEI Technologies(0x12d1), rev 0.00 port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 addr 2: low speed, power 100 mA, config 1, ELECOM USB mouse with wheel(0x0010), ELECO(0x056e), rev 0.00 port 2 powered Controller /dev/usb3: addr 1: high speed, self powered, config 1, EHCI root hub(0x), Intel(0x), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered port 5 powered port 6 powered port 7 powered port 8 powered uname -a: FreeBSD barbikane 6.0-RELEASE FreeBSD 6.0-RELEASE #4: Fri Nov 24 19:03:59 CET 2006 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/MYKERNEL i386 Greetings, Jes ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Huawei E220 3G devices
Hi folks, I found something in the archives about trouble using an E220 Huawei device. I'm wondering if somebody can send me the verbose output of `usbctl' for that device as I don't have one? To me it seems this device is being detected by umass because of a feature used under Windows. The E220 should be real plug'n play as if a Windows user is plugging the device, the (Win) drivers are installed straight from the box (no CDROM is necessary). I suspect this is being done by a umass emulation. Supporting this device with it's basic functionality should be as easy as defining vendor-ID and device-ID in ubsa and we're done. Again, is anybody able to provide me with the output of usbctl for that device? Greetings, Volker ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
