Re: strange USB timing issue with u3g
On 3/13/2019 11:46 AM, CeDeROM wrote: > Hey there! I also noticed problems with U3G module with my new Quectel > EC25E miniPCI-E module replaced the Sierra Wireless on my Panasonic > CF-C2 notebook.. sometimes (very very often) the /dev/cuaU* is not > created properly so PPP has nothing to connect to.. > > So I have to use simple usbconfig to reset devices at boot.. but that > also sometimes does not help as devices seems to have random order.. > and it causes problems with other devices that are already > attached/enumerated.. this is a bit unreliable.. > > I was wondering is there a problem with U3G module and how could I > quick fix it without the module rewrite? I am not sure its an actual problem with the u3g module per se. The error can happen with or without the u3g module loaded, so even as a ugen device, it will fail to attach. ---Mike > -- > --- > Mike Tancsa, tel +1 519 651 3400 x203 > Sentex Communications, m...@sentex.net > Providing Internet services since 1994 www.sentex.net > Cambridge, Ontario Canada ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: strange USB timing issue with u3g
On 3/13/2019 10:59 AM, Hans Petter Selasky wrote: > > Hi, > > Can you check if the auto-installer is enabled on your device or not? > HUAWEI should have some binaries for updating their dongles somewhere. > Last time I tried this I got the update from where I bought it. Though > it might require MacOS or Windows before it will install :-( > Auto install is not according to the AT commands. Note, this is a mini-pcie device, not an external USB adapter. Thanks for the suggestions! I will keep experimenting with the timings to see if I can find a reliable setting. ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: strange USB timing issue with u3g
On 3/12/2019 5:43 PM, Hans Petter Selasky wrote: > On 3/12/19 9:49 PM, Mike Tancsa wrote: >> > > Hi, > > Maybe the device expects some kind of BIOS to enumerate it quickly and > if not, goes into sleep mode. > > Try setting: > hw.usb.ehci.no_hs=1 > > In /boot/loader.conf . > > Does this change anything? usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_IOERROR usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_IOERROR usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR, ignored) usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR, ignored) seems to reliably come up with this setting on when loading u3g out of loader.conf and letting devd do it later. The other variable that can trigger it is if I load a bunch of other klds like umodem, ucom,uplcom and uftdi. > > USB devices are not allowed to return with a STALL-PID on set-address > messages, so this is violation of established USB standards. Maybe you > need a USB wire-analyzer to nail this issue. > > There are a bunch of tunables for example: > hw.usb.timings Although testing a bit with hw.usb.timings.extra_power_up_time=990 seems to make the error on dmesg just up come up at a different, later point. setting hw.usb.timings.port_powerup_delay=1000 does seem to help! At least I was able to boot up 50% of the time. Trying with 2000 however, does not seem to make it better. still 50/50 > > Which affect how the USB device is enumerated. > > Is your device running the latest firmware from HUAWEI? Not sure. I have never upgraded the firmware in these guys before. Manufacturer: Huawei Technologies Co., Ltd. Model: ME909u-523 Revision: 11.430.63.00.00 IMEI: x +GCAP: +CGSM Do you know of any references on how to do this ? Looking at the AT command manual AT^FOTADET OK ^FOTASTATE: 11 ^DEND: 1,33,IPV4 and tried again AT^FOTADET OK ^FOTASTATE: 11 ^FOTASTATE: 13,13 ^HCSQ: "LTE",50,41,94,10 ^HCSQ: "LTE",44,41,137,22 AT^FOTADLQ ^FOTADLQ: 1,"FIRMWARE1",0,0 I think 13 means "New version query failed" My guess is that I need to setup some specific APN data to talk to Huawei ? The modem is not specifically designed for the carrier, so I dont know if the carrier usually has stuff behind the scenes for such updates. Although the command AT^FWLOAD= This command is used to specify the upgrade type, transmit the upgrade file into the module using 1K-Xmodem, and start the upgrade. The following table lists the ports supported by the full and differential upgrades. So if I can find a firmware file, I can do an old school xmodem-1k upload. I will see if I can find one from Huawei. > > --HPS > > -- --- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
strange USB timing issue with u3g
I have a strange issue I started to see on RELENG11 and RELENG12 that I am not sure when it started or if its always been there. On an PCEngines APU3, with an LTE modem that works with the u3g driver, it will fail to attach if the box does not boot up fast enough. So I am guessing something gets messed up in initialization and timing ? e.g. in loader.conf I have autoboot_delay=2 dcons_load="YES" amdsbwd_load="YES" u3g_load="YES" beastie_disable="YES" comconsole_speed="115200" console="comconsole" #hw.usb.debug=1 If I pause at the boot or make the delay say 10 seconds, the device often errors out. The device normally looks like this ugen2.1: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen1.1: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.1: <0x1022 XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen2.2: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA) ugen1.2: at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA) ugen2.3: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (500mA) ugen2.3: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (500mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x12d1 idProduct = 0x1573 bcdDevice = 0x0228 iManufacturer = 0x0002 iProduct = 0x0003 iSerialNumber = 0x0004 <0123456712ABCA17> bNumConfigurations = 0x0003 But about 50% of the time with a longer delay, at bootup time I get uhub4: 4 ports with 4 removable, self powered usb_alloc_device: set address 3 failed (USB_ERR_STALLED, ignored) usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored) usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_STALLED, ignored) usbd_setup_device_desc: getting device descriptor at addr 3 failed, USB_ERR_STALLED vs ugen0.1: <0x1022 XHCI root HUB> at usbus0 ugen1.1: at usbus1 ugen2.1: at usbus2 uhub0: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 uhub1: on usbus1 uhub2: on usbus2 mmcsd0: 4GB at mmc0 50.0MHz/4bit/65535-block Trying to mount root from ufs:/dev/mmcsd0s1a [ro]... uhub0: 4 ports with 4 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered Starting file system checks: /dev/mmcsd0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/mmcsd0s1a: clean, 386561 free (3113 frags, 47931 blocks, 0.1% fragmentation) ugen1.2: at usbus1 uhub3 on uhub1 uhub3: on usbus1 ugen2.2: at usbus2 uhub4 on uhub2 uhub4: on usbus2 /dev/mmcsd0s3: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/mmcsd0s3: clean, 2829 free (21 frags, 351 blocks, 0.7% fragmentation) /etc/rc: WARNING: hostid: unable to figure out a UUID from DMI data, generating a new one uhub3: 4 ports with 4 removable, self powered uhub4: 4 ports with 4 removable, self powered ugen2.3: at usbus2 u3g0 on uhub4 u3g0: on usbus2 u3g0: Found 5 ports. Enabling debug will make it fail. Any idea what it might be or how I can tweak it to it more reliably initializes ? I first start to notice it when I added a few more klds at boot time. This made the boot up process that much longer that I would run into this issue periodically. ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: USB problems on PC Engines APU2C4
On 7/24/2018 2:48 PM, Stefan Bethke wrote: > The USB2 ports on the APU are not exposed in the case, and I don’t really > feel like trying to drill a hole into the case to try and get the adapter > cable out. The only ports available on the case are the two USB3 ports. > > How could I go about debugging the XHCI driver that apparently has trouble > communicating? Is there some more debug bits I can enable? Not sure about debugging the xhci driver, but if you compile out the xhci driver from your kernel, and then after the APU2 has booted load it (or leave it unloaded) does the USB device behave as expected on its normal external ports ? I had to do this on an older version of the board to work around some timing issues. ---Mike -- ------- Mike Tancsa, tel +1 519 651 3400 x203 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: USB device not working on FreeBSD
On 2/8/2017 2:20 PM, Hans Petter Selasky wrote: > Hi, > > After your device receives the following control endpoint request it > becomes unrecoverable: > >> 13:05:50.860195 usbus0.4 >> SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 >> frame[0] WRITE 8 bytes >> A1 01 52 03 00 00 03 00 -- -- -- -- -- -- -- -- >> |..R.| > ^^ USB read interface class (A1) > ^^ GET_REPORT (01) > ^^ feature (03) >^^ length (3 bytes) >> frame[1] READ 3 bytes >> 13:05:50.860938 usbus0.4 >> DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=0,IVAL=0,ERR=IOERROR >> frame[0] WRITE 8 bytes >> frame[1] READ 0 bytes > I had a look at an older apc 650, and it works just fine after getting that command 15:40:40.803562 usbus0.4 SUBM-CTRL-EP=0080,SPD=LOW,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes A1 01 01 03 00 00 02 00 -- -- -- -- -- -- -- -- || frame[1] READ 2 bytes 15:40:40.804886 usbus0.4 DONE-CTRL-EP=0080,SPD=LOW,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 2 bytes 01 01 -- -- -- -- -- -- -- -- -- -- -- -- -- -- |.. | 15:40:40.805048 usbus0.4 SUBM-CTRL-EP=0080,SPD=LOW,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- || frame[1] READ 4 bytes 15:40:40.806959 usbus0.4 DONE-CTRL-EP=0080,SPD=LOW,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 4 bytes 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- || 15:40:40.807114 usbus0.4 SUBM-CTRL-EP=0080,SPD=LOW,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- || frame[1] READ 4 bytes 15:40:40.809126 usbus0.4 DONE-CTRL-EP=0080,SPD=LOW,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 4 bytes 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- || ugen0.4: at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (2mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0008 idVendor = 0x051d idProduct = 0x0002 bcdDevice = 0x0106 iManufacturer = 0x0003 iProduct = 0x0001 iSerialNumber = 0x0002 <4B1640P41654 > -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: USB device not working on FreeBSD
On 2/8/2017 3:09 PM, Hans Petter Selasky wrote: > > You can also try connecting the device w/ or w/o a USB HUB. I tried with a HUB, but it does not make a difference. ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: USB device not working on FreeBSD
On 2/8/2017 12:55 PM, Hans Petter Selasky wrote: > On 02/08/17 18:38, Mike Tancsa wrote: >> Hi, >> It works without issue on Linux. >> What information from usbdump would be helpful from usbdump ? > > Hi, > > If there are any transaction errors, like non successful USB transfers. Hi, This is with UQ_NO_STRINGS set. I start the dump, start up apcupsd, when a couple of seconds then do an apcaccess to query the daemon ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: USB device not working on FreeBSD
On 2/8/2017 12:33 PM, Hans Petter Selasky wrote: > On 01/24/17 18:12, Mike Tancsa wrote: >> The daemon does attach to it, and it sort of reads some of the info (as >> before adding the quirk) > > Hi, > > Does this device work with apcaccess under Linux? > > Have you tried contacting the maintainers about this? > > usbdump'ing the traffic, from before you attach the device, might give > you some ideas what is going on. Hi, It works without issue on Linux. What information from usbdump would be helpful from usbdump ? Bus 001 Device 005: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x051d American Power Conversion idProduct 0x0002 Uninterruptible Power Supply bcdDevice0.90 iManufacturer 1 American Power Conversion iProduct2 Back-UPS NS 650M1 FW:929.a5 .D USB F iSerial 3 4B1630P12329 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.00 bCountryCode 33 US bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength1049 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 100 Device Status: 0x0001 Self Powered # apcaccess APC : 001,037,0922 DATE : 2017-01-24 09:29:10 -0500 HOSTNAME : loadb06 VERSION : 3.14.12 (29 March 2014) debian UPSNAME : loadb06 CABLE: USB Cable DRIVER : USB UPS Driver UPSMODE : Stand Alone STARTTIME: 2017-01-24 09:25:13 -0500 MODEL: Back-UPS NS 650M1 STATUS : ONLINE LINEV: 118.0 Volts LOADPCT : 0.0 Percent BCHARGE : 96.0 Percent TIMELEFT : 429.9 Minutes MBATTCHG : 5 Percent MINTIMEL : 3 Minutes MAXTIME : 0 Seconds SENSE: Medium LOTRANS : 92.0 Volts HITRANS : 139.0 Volts ALARMDEL : 30 Seconds BATTV: 13.5 Volts LASTXFER : Low line voltage NUMXFERS : 1 XONBATT : 2017-01-24 09:27:37 -0500 TONBATT : 0 Seconds CUMONBATT: 33 Seconds XOFFBATT : 2017-01-24 09:28:10 -0500 SELFTEST : OK STATFLAG : 0x0508 SERIALNO : 4B1630P12329 BATTDATE : 2016-07-27 NOMINV : 120 Volts NOMBATTV : 12.0 Volts NOMPOWER : 360 Watts FIRMWARE : 929.a5 .D USB FW:a5 END APC : 2017-01-24 09:29:44 -0500 On FreeBSD ugen0.8: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (2mA) Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0022 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x bmAttributes = 0x00e0 bMaxPower = 0x0001 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0001 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x bInterfaceProtocol = 0x iInterface = 0x Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x00 RAW dump: 0x00 | 0x09, 0x21, 0x00, 0x01, 0x21, 0x01, 0x22, 0x19, 0x08 | 0x04 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 bmAttributes = 0x0003 wMaxPacketSize = 0x0008 bInterval = 0x0064 bRefresh = 0x bSynchAddress = 0x ugen0.8: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (2mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x051d idProduct = 0x0002 bcdDevice = 0x
Re: USB device not working on FreeBSD
On 1/24/2017 12:03 PM, Hans Petter Selasky wrote: > On 01/24/17 16:14, Mike Tancsa wrote: >> Perhaps some sort of USB quirk needs to be added ? Any ideas on how to >> get things working ? It fails on RELENG8, RELENG_10, and RELENG_11 in >> the same way. usbconfig dump_device_desc fails as its not able to get >> all the info. > > Hi, > > Try setting the UQ_NO_STRINGS quirk for this device and also verify that > the idVendor and idProduct is present in the apcaccess utility. Else it > will not attach! Thanks! The quirk doesnt seem to make a difference to the app, but dump_device_desc works now # usbconfig -d ugen0.4 add_quirk UQ_NO_STRINGS # usbconfig -d 0.4 dump_device_desc ugen0.4: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (2mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x051d idProduct = 0x0002 bcdDevice = 0x0090 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 <4B1630P12329 > bNumConfigurations = 0x0001 The daemon does attach to it, and it sort of reads some of the info (as before adding the quirk) # apcaccess APC : 001,033,0741 DATE : 2017-01-24 12:09:00 -0500 HOSTNAME : offsite2.sentex.ca VERSION : 3.14.14 (31 May 2016) freebsd UPSNAME : offsite2.sentex.ca CABLE: USB Cable DRIVER : USB UPS Driver UPSMODE : Stand Alone STARTTIME: 2017-01-24 12:08:53 -0500 MODEL: STATUS : LINEV: 0.0 Volts LOADPCT : 0.0 Percent BCHARGE : 100.0 Percent TIMELEFT : 447.7 Minutes MBATTCHG : 5 Percent MINTIMEL : 3 Minutes MAXTIME : 0 Seconds SENSE: Unknown LOTRANS : -1.0 Volts HITRANS : -1.0 Volts ALARMDEL : Always BATTV: 0.0 Volts NUMXFERS : 0 TONBATT : 0 Seconds CUMONBATT: 0 Seconds XOFFBATT : N/A SELFTEST : NO STATFLAG : 0x0500 SERIALNO : BATTDATE : NOMINV : 0 Volts NOMBATTV : 0.0 Volts END APC : 2017-01-24 12:09:47 -0500 -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
USB device not working on FreeBSD
-- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: XHCI device probe inconsistency
On 10/8/2014 5:27 AM, Hans Petter Selasky wrote: Hi, If you plug the device after boot, what happens then? What speed does the BIOS enumerate the device at? Have you checked for USB related BIOS settings? Hi, Hmmm, I could not recreate the issue at first!! I tried both a soft and cold boot, and with and without a CF in it and it would always come up as USB3 And then I remember setting the BIOS option Make USB Non Bootable (Enable/Disable) so it would not try and boot from the flash. Once I set that to enable, so it could not boot from a USB device, the CF Reader/Writer always probes as USB3 speed! When its disabled, at boot time it probes as USB2 speeds until I disconnect / reconnect. Thanks! ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
XHCI device probe inconsistency
=0x35b78086 chip=0x8c318086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'Lynx Point USB xHCI Host Controller' class = serial bus subclass = USB bar [10] = type Memory, range 64, base 0xc012, size 65536, enabled cap 01[70] = powerspec 2 supports D0 D3 current D0 cap 05[80] = MSI supports 8 messages, 64 bit enabled with 1 message ehci0@pci0:0:26:0: class=0x0c0320 card=0x35b78086 chip=0x8c2d8086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'Lynx Point USB Enhanced Host Controller' class = serial bus subclass = USB bar [10] = type Memory, range 32, base 0xc142, size 1024, enabled cap 01[50] = powerspec 2 supports D0 D3 current D0 cap 0a[58] = EHCI Debug Port at offset 0xa0 in map 0x14 cap 13[98] = PCI Advanced Features: FLR TP -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
powering off USB hubs / ports
wMaxPacketSize = 0x0001 bInterval = 0x000c bRefresh = 0x bSynchAddress = 0x ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: USB 3 stick
On 2/13/2013 3:17 AM, Hans Petter Selasky wrote: If I boot up the box and then plug the stick into the 3.0 port, it works as expected. Have you tried playing with BIOS USB 3.0 settings? Hi, There are not really any options to set other than enable or disable or legacy mode or not. I will try disabling legacy mode and see what happens. I did upgrade it to the latest version of the BIOS as well. ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
USB 3 stick
Hi,
I picked up a Zalman USB 3.0 flash stick that has problems if its
connected at boot time. If I reboot the box with the stick plugged in
(RELENG_9 from Feb 11), I get the errors below.
xhci_do_command: Command timeout!
usb_alloc_device: set address 2 failed (USB_ERR_TIMEOUT, ignored)
xhci_do_command: Command timeout!
xhci_do_command: Command timeout!
xhci_do_command: Command timeout!
ugen0.2: vendor 0x8087 at usbus0
uhub3: vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2
on usbus0
ugen2.2: vendor 0x8087 at usbus2
uhub4: vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2
on usbus2
xhci_do_command: Command timeout!
Root mount waiting for: usbus2 usbus1 usbus0
xhci_do_command: Command timeout!
xhci_do_command: Command timeout!
uhub3: 4 ports with 4 removable, self powered
xhci_do_command: Command timeout!
xhci_do_command: Command timeout!
uhub4: 6 ports with 6 removable, self powered
xhci_do_command: Command timeout!
Root mount waiting for: usbus1
xhci_do_command: Command timeout!
xhci_do_command: Command timeout!
usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_TIMEOUT,
ignored)
Root mount waiting for: usbus1
xhci_do_command: Command timeout!
uhub_reattach_port: could not allocate new device
and the device does not show up. I can unplug it and replug it, but it
will not work in the USB 3 port. If I replug it into the 2.x port after
the problematic boot, it works.
If I boot up the box and then plug the stick into the 3.0 port, it works
as expected.
speed is good as well
0{USB3}# dd if=/dev/da0 of=/dev/null bs=1024k count=300
300+0 records in
300+0 records out
314572800 bytes transferred in 3.462889 secs (90841146 bytes/sec)
0{USB3}#
0{USB3}# dd if=/dev/zero of=/dev/da0 count=300 bs=1024k
300+0 records in
300+0 records out
314572800 bytes transferred in 3.577376 secs (87933952 bytes/sec)
0{USB3}#
USB output attached. Any ideas what the issue might be ?
---Mike
--
---
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, m...@sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada http://www.tancsa.com/
Base Board Information
Manufacturer: Intel Corporation
Product Name: DH61BE
Version: AAG14062-205
Version: BEH6110H.86A.0109.2012.1221.1455
Release Date: 12/21/2012
Address: 0xF
Runtime Size: 64 kB
ROM Size: 4096 kB
ugen2.1: EHCI root HUB Intel at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps)
pwr=SAVE
Configuration index 0
bLength = 0x0009
bDescriptorType = 0x0002
wTotalLength = 0x0019
bNumInterfaces = 0x0001
bConfigurationValue = 0x0001
iConfiguration = 0x no string
bmAttributes = 0x0040
bMaxPower = 0x
Interface 0
bLength = 0x0009
bDescriptorType = 0x0004
bInterfaceNumber = 0x
bAlternateSetting = 0x
bNumEndpoints = 0x0001
bInterfaceClass = 0x0009
bInterfaceSubClass = 0x
bInterfaceProtocol = 0x
iInterface = 0x no string
Endpoint 0
bLength = 0x0007
bDescriptorType = 0x0005
bEndpointAddress = 0x0081 IN
bmAttributes = 0x0003 INTERRUPT
wMaxPacketSize = 0x0008
bInterval = 0x00ff
bRefresh = 0x
bSynchAddress = 0x
ugen1.1: XHCI root HUB 0x1033 at usbus1, cfg=0 md=HOST spd=SUPER (5.0Gbps)
pwr=SAVE
Configuration index 0
bLength = 0x0009
bDescriptorType = 0x0002
wTotalLength = 0x001f
bNumInterfaces = 0x0001
bConfigurationValue = 0x0001
iConfiguration = 0x no string
bmAttributes = 0x0040
bMaxPower = 0x
Interface 0
bLength = 0x0009
bDescriptorType = 0x0004
bInterfaceNumber = 0x
bAlternateSetting = 0x
bNumEndpoints = 0x0001
bInterfaceClass = 0x0009
bInterfaceSubClass = 0x
bInterfaceProtocol = 0x
iInterface = 0x no string
Endpoint 0
bLength = 0x0007
bDescriptorType = 0x0005
bEndpointAddress = 0x0081 IN
bmAttributes = 0x0003 INTERRUPT
wMaxPacketSize = 0x0002
bInterval = 0x00ff
bRefresh = 0x
bSynchAddress = 0x
Additional Descriptor
bLength = 0x06
bDescriptorType = 0x30
bDescriptorSubType = 0x00
RAW dump:
0x00 | 0x06, 0x30, 0x00, 0x00, 0x00, 0x00
ugen0.1: EHCI root HUB Intel at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps)
pwr=SAVE
Configuration index 0
bLength = 0x0009
bDescriptorType = 0x0002
wTotalLength = 0x0019
bNumInterfaces = 0x0001
bConfigurationValue = 0x0001
iConfiguration = 0x no string
bmAttributes = 0x0040
bMaxPower = 0x
Interface 0
bLength = 0x0009
bDescriptorType = 0x0004
bInterfaceNumber = 0x
bAlternateSetting = 0x
bNumEndpoints = 0x0001
Re: USB3 SATA enclosure
On 12/13/2012 2:24 AM, Hans Petter Selasky wrote: Hi, There is an error message there: xhci0: NEC uPD720200 USB 3.0 controller mem 0xfb90-0xfb901fff irq 18 at device 0.0 on pci4 usbus1: waiting for BIOS to give up control usbus1: timed out waiting for BIOS 1) Can you turn off USB legacy support in the BIOS? 2) Can you boot with bootverbose set using 9-stable and BIOS legacy support enabled? Hi, That did the trick! Actually, legacy was disabled in the BIOS. Enabling it now shows it at full speed! ugen1.2: USB 3.0 SATA Bridge VIA Labs, Inc. at usbus1, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON 0(cage)# dd if=/dev/da1 of=/dev/null bs=1024k count=900 900+0 records in 900+0 records out 943718400 bytes transferred in 6.438713 secs (146569414 bytes/sec) 0(cage)# I still get the error xhci0: NEC uPD720200 USB 3.0 controller mem 0xfb90-0xfb901fff irq 18 at device 0.0 on pci4 usbus1: waiting for BIOS to give up control usbus1: timed out waiting for BIOS xhci0: 32 byte context size. usbus1 on xhci0 ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: USB3 SATA enclosure
On 12/12/2012 2:54 AM, Hans Petter Selasky wrote: Try to tune these up, one by one. I doubled them all, and still only 0(cage)# usbconfig ugen0.1: EHCI root HUB Intel at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.1: XHCI root HUB 0x1033 at usbus1, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE ugen0.3: USB 3.0 SATA Bridge VIA Labs, Inc. at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON Have you tried a 10-current kernel after r243780? Not me. I am running just RELENG_9 from a few days ago. 0(cage)# svn status --show-updates * 244103 contrib/gdb/gdb/cp-valprint.c * 244103 contrib/gdb/gdb/scm-valprint.c * 244103 contrib/gdb/gdb/dwarf2loc.c * 244103 contrib/gdb/gdb/p-valprint.c * 244103 contrib/gdb/gdb/c-valprint.c * 244103 contrib/gdb/gdb/f-valprint.c * 244103 contrib/gdb/gdb/stack.c * 244103 contrib/gdb/gdb/varobj.c * 244103 contrib/gdb/gdb/jv-valprint.c * 244103 contrib/gdb/gdb/valprint.c * 244103 contrib/gdb/gdb/value.h * 244103 contrib/gdb/gdb/frame.c * 244103 contrib/gdb * 244103 usr.sbin/bsdinstall/scripts/mirrorselect * 244103 usr.sbin/bsdinstall/scripts * 244103 usr.sbin/bsdinstall * 244103 lib/libc/net/nsparser.y * 244103 lib/libc * 244103 bin/expr/expr.y * 244103 bin/expr * 244103 sys/kern/vfs_mountroot.c * 244103 sys/kern/vfs_bio.c * 244103 sys/kern/vfs_mount.c * 244103 sys/dev/uart/uart_bus_pci.c * 244103 sys/dev/isci/isci_io_request.c * 244103 sys/dev * 244103 sys Status against revision: 244150 0(cage)# -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: USB3 SATA enclosure
On 12/12/2012 7:53 AM, Hans Petter Selasky wrote: There are some patches for the XHCI I want to backport to 9-stable, but they are not ready yet, due to depending patches and testing. Do you have the possibility to install a 10-current kernel and see if the device is detected correctly during enumeration. Then boot kernel.old and install a 9-stable kernel again? Hi, No luck with HEAD. dmesg from the boot attached. I tried both with and without the sysctl changes and they didnt make a difference 0(cage)# svn info Path: . Working Copy Root Path: /pxe/HEAD/src URL: svn://svn.freebsd.org/base/head Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 244158 Node Kind: directory Schedule: normal Last Changed Author: dteske Last Changed Rev: 244158 Last Changed Date: 2012-12-12 12:49:01 -0500 (Wed, 12 Dec 2012) 0(cage)# ugen0.1: EHCI root HUB Intel at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.1: XHCI root HUB 0x1033 at usbus1, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE ugen2.1: EHCI root HUB Intel at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.2: product 0x17ab vendor 0x0b05 at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen1.3: WinTV HVR-950 Hauppauge at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.2: product 0x0024 vendor 0x8087 at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen2.2: product 0x0024 vendor 0x8087 at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.3: USB 3.0 SATA Bridge VIA Labs, Inc. at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.4: product 0x1400 vendor 0x04d9 at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen0.5: Back-UPS RS 1500G FW865.L3 .D USB FWL3 American Power Conversion at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen0.1: EHCI root HUB Intel at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #0 r244158: Wed Dec 12 15:15:06 EST 2012 mdtan...@cage.simianscience.com:/usr/HEAD/obj/pxe/HEAD/src/sys/GENERIC amd64 WARNING: WITNESS option enabled, expect reduced performance. CPU: Intel(R) Core(TM) i5-2300 CPU @ 2.80GHz (2793.72-MHz K8-class CPU) Origin = GenuineIntel Id = 0x206a7 Family = 0x6 Model = 0x2a Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x1f9ae3bfSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 17179869184 (16384 MB) avail memory = 16347066368 (15589 MB) Event timer LAPIC quality 600 ACPI APIC Table: INTEL DQ67SW FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 hpt27xx: RocketRAID 27xx controller driver v1.0 (Dec 12 2012 15:14:28) ctl: CAM Target Layer loaded cryptosoft0: software crypto on motherboard aesni0: AES-CBC,AES-XTS on motherboard acpi0: INTEL DQ67SW on motherboard acpi0: Power Button (fixed) cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 attimer0: AT timer port 0x40-0x43 irq 0 on acpi0 Timecounter i8254 frequency 1193182 Hz quality 0 Event timer i8254 frequency 1193182 Hz quality 100 atrtc0: AT realtime clock port 0x70-0x71 irq 8 on acpi0 Event timer RTC frequency 32768 Hz quality 0 hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 950 Event timer HPET frequency 14318180 Hz quality 550 Event timer HPET1 frequency 14318180 Hz quality 440 Event timer HPET2 frequency 14318180 Hz quality 440 Event timer HPET3 frequency 14318180 Hz quality 440 Event timer HPET4 frequency 14318180 Hz quality 440 Timecounter ACPI-fast frequency 3579545 Hz quality 900 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 16 at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 vgapci0: VGA-compatible display port 0xf000-0xf03f mem 0xfb40-0xfb7f,0xc000-0xcfff irq 16 at device 2.0 on pci0 agp0: SandyBridge desktop GT1 IG on vgapci0 agp0: aperture size is 256M, detected 32764k stolen memory
Re: USB3 SATA enclosure
On 12/11/2012 2:18 AM, Hans Petter Selasky wrote: As I use it only randomly, I have had to notice that it is not recognised as USB3 on 10. either anymore. Something got changed which stopped it from working. We've only changed some reset timings. See: sysctl -a hw.usb hw.usb.uaudio.default_channels: 0 hw.usb.uaudio.default_bits: 32 hw.usb.uaudio.default_rate: 0 hw.usb.uaudio.debug: 0 hw.usb.ehci.lostintrbug: 0 hw.usb.ehci.iaadbug: 0 hw.usb.ehci.no_hs: 0 hw.usb.ehci.debug: 0 hw.usb.ohci.debug: 0 hw.usb.uhci.loop: 0 hw.usb.uhci.debug: 0 hw.usb.xhci.xhci_port_route: 0 hw.usb.xhci.debug: 0 hw.usb.no_shutdown_wait: 0 hw.usb.no_suspend_wait: 0 hw.usb.no_boot_wait: 0 hw.usb.ctrl.debug: 0 hw.usb.umass.debug: 0 hw.usb.urio.debug: 0 hw.usb.timings.extra_power_up_time: 20 hw.usb.timings.resume_recovery: 50 hw.usb.timings.resume_wait: 50 hw.usb.timings.resume_delay: 250 hw.usb.timings.set_address_settle: 10 hw.usb.timings.port_resume_delay: 40 hw.usb.timings.port_powerup_delay: 300 hw.usb.timings.port_reset_recovery: 250 hw.usb.timings.port_root_reset_delay: 250 hw.usb.timings.port_reset_delay: 50 hw.usb.debug: 0 hw.usb.dev.debug: 0 hw.usb.usb_lang_mask: 255 hw.usb.usb_lang_id: 9 hw.usb.template: 0 hw.usb.ugen.debug: 0 hw.usb.power_timeout: 30 hw.usb.uhub.debug: 0 hw.usb.no_pf: 0 hw.usb.proc.debug: 0 hw.usb.no_cs_fail: 0 hw.usb.aue.debug: 0 hw.usb.axe.debug: 0 hw.usb.cdce.interval: 0 hw.usb.cdce.debug: 0 hw.usb.cue.debug: 0 hw.usb.kue.debug: 0 hw.usb.rue.debug: 0 hw.usb.udav.debug: 0 hw.usb.rum.debug: 0 hw.usb.run.debug: 0 hw.usb.uath.regdomain: 0 hw.usb.uath.countrycode: 0 hw.usb.ural.debug: 0 hw.usb.urtw.preamble_mode: 2 hw.usb.zyd.debug: 0 hw.usb.u3g.debug: 0 hw.usb.ubsa.debug: 0 hw.usb.uftdi.debug: 0 hw.usb.ulpt.debug: 0 hw.usb.uplcom.debug: 0 hw.usb.uslcom.debug: 0 hw.usb.uvisor.debug: 0 hw.usb.uvscom.debug: 0 hw.usb.ucom.cons_baud: 9600 hw.usb.ucom.cons_subunit: 0 hw.usb.ucom.cons_unit: -1 hw.usb.ucom.debug: 0 hw.usb.uhid.debug: 0 hw.usb.ukbd.no_leds: 0 hw.usb.ukbd.debug: 0 hw.usb.ums.debug: 0 -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: USB3 SATA enclosure
On 12/11/2012 6:49 AM, Hans Petter Selasky wrote: On Tuesday 11 December 2012 12:34:11 Mike Tancsa wrote: hw.usb.timings.extra_power_up_time: 20 hw.usb.timings.resume_recovery: 50 hw.usb.timings.resume_wait: 50 hw.usb.timings.resume_delay: 250 hw.usb.timings.set_address_settle: 10 hw.usb.timings.port_resume_delay: 40 hw.usb.timings.port_powerup_delay: 300 hw.usb.timings.port_reset_recovery: 250 hw.usb.timings.port_root_reset_delay: 250 hw.usb.timings.port_reset_delay: 50 Try to tune these up, one by one. I doubled them all, and still only 0(cage)# usbconfig ugen0.1: EHCI root HUB Intel at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.1: XHCI root HUB 0x1033 at usbus1, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE ugen2.1: EHCI root HUB Intel at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.2: product 0x17ab vendor 0x0b05 at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen1.3: WinTV HVR-950 Hauppauge at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen2.2: product 0x0024 vendor 0x8087 at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.2: product 0x0024 vendor 0x8087 at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.3: USB 3.0 SATA Bridge VIA Labs, Inc. at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.4: product 0x1400 vendor 0x04d9 at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
USB3 SATA enclosure
I picked up a USB3 sata enclosure and was surprised at the low speeds I was getting. I should probably just stick with eSata instead, but has anyone got any decent throughput on USB3 drives ? This one seems to be coming up USB2 speeds ugen0.5: USB 3.0 SATA Bridge VIA Labs, Inc. at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0210 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x2109 idProduct = 0x0700 bcdDevice = 0x0005 iManufacturer = 0x0001 VIA Labs, Inc. iProduct = 0x0002 USB 3.0 SATA Bridge iSerialNumber = 0x0003 6121 bNumConfigurations = 0x0001 ugen0.5: USB 3.0 SATA Bridge VIA Labs, Inc. at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0020 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x no string bmAttributes = 0x00c0 bMaxPower = 0x0001 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x0008 bInterfaceSubClass = 0x0002 bInterfaceProtocol = 0x0050 iInterface = 0x no string Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 IN bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0200 bInterval = 0x0001 bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0002 OUT bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0200 bInterval = 0x0001 bRefresh = 0x bSynchAddress = 0x xhci0@pci0:4:0:0: class=0x0c0330 card=0x20088086 chip=0x01941033 rev=0x04 hdr=0x00 vendor = 'NEC Corporation' device = 'uPD720200 USB 3.0 Host Controller' class = serial bus subclass = USB bar [10] = type Memory, range 64, base 0xfb90, size 8192, enabled cap 01[50] = powerspec 3 supports D0 D3 current D0 cap 05[70] = MSI supports 8 messages, 64 bit cap 11[90] = MSI-X supports 8 messages in map 0x10 cap 10[a0] = PCI-Express 2 endpoint max data 128(128) link x1(x1) speed 5.0(5.0) ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected ecap 0003[140] = Serial 1 ecap 0018[150] = unknown 1 PCI-e errors = Correctable Error Detected Unsupported Request Detected Corrected = Advisory Non-Fatal Error RELENG_9 from yesterday. When connected, it comes up ugen0.5: VIA Labs, Inc. at usbus0 umass0: VIA Labs, Inc. USB 3.0 SATA Bridge, class 0/0, rev 2.10/0.05, addr 5 on usbus0 umass0: 8070i (ATAPI) over Bulk-Only; quirks = 0x4000 umass0:13:0:-1: Attached to scbus13 (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (probe0:umass-sim0:0:0:0): Retrying command da1 at umass-sim0 bus 0 scbus13 target 0 lun 0 da1: ST2000DM 001-1CH164 CC24 Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers da1: 1907729MB (3907029165 512 byte sectors: 255H 63S/T 243201C) 1(cage)# camcontrol inquiry 13:0:0 pass6: ST2000DM 001-1CH164 CC24 Fixed Direct Access SCSI-2 device pass6: Serial Number 6121 pass6: 40.000MB/s transfers 0(cage)# ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: APC's Back-UPS devices not recognized as uhid -- only as ugen
: JB0524026679 BATTDATE : 2012-03-10 NOMINV : 120 Volts NOMBATTV : 24.0 Volts NOMPOWER : 865 Watts FIRMWARE : 8.g9 .D USB FW:g9 END APC : 2012-11-02 14:07:31 -0400 0(backup3)# apcaccess status localhost:3553 APC : 001,037,0966 DATE : 2012-11-02 14:07:28 -0400 HOSTNAME : backup3.sentex.ca VERSION : 3.14.10 (13 September 2011) freebsd UPSNAME : RAPIDS CABLE: USB Cable DRIVER : USB UPS Driver UPSMODE : Stand Alone STARTTIME: 2012-10-23 16:28:10 -0400 MODEL: Back-UPS RS 1500 STATUS : ONLINE LINEV: 115.0 Volts LOADPCT : 54.0 Percent Load Capacity BCHARGE : 100.0 Percent TIMELEFT : 12.2 Minutes MBATTCHG : 10 Percent MINTIMEL : -1 Minutes MAXTIME : 0 Seconds SENSE: Medium LOTRANS : 097.0 Volts HITRANS : 132.0 Volts ALARMDEL : 30 seconds BATTV: 26.9 Volts LASTXFER : Low line voltage NUMXFERS : 2 XONBATT : 2012-11-02 11:14:56 -0400 TONBATT : 0 seconds CUMONBATT: 8 seconds XOFFBATT : 2012-11-02 11:14:58 -0400 SELFTEST : NO STATFLAG : 0x0708 Status Flag SERIALNO : 8B0736R21792 BATTDATE : 2007-09-07 NOMINV : 120 Volts NOMBATTV : 24.0 Volts NOMPOWER : 865 Watts FIRMWARE : 8.g9a.D USB FW:g9a END APC : 2012-11-02 14:07:32 -0400 0(backup3)# ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: usb/165154: USB patch for new u3g device
On 2/29/2012 12:19 PM, re...@freebsd.org wrote: Synopsis: USB patch for new u3g device State-Changed-From-To: open-patched State-Changed-By: remko State-Changed-When: Wed Feb 29 17:18:56 UTC 2012 State-Changed-Why: This had been patched to -HEAD and stable/9, set the state to patched. Hi, Any chance to MFC to RELENG_8 as well ? ---Mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: usb umodem support for USR5637
On 2/19/2012 7:39 AM, praise365 wrote: Does anyone know if the usr5637 is currently supported by umodem ? It isn't liisted on the man page. Yes, they work well enough. Just load ucom and umodem or compile them into your kernel. My units show up as ugen1.2: USB Modem U.S.Robotics at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0002 bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x0baf idProduct = 0x0303 bcdDevice = 0x0200 iManufacturer = 0x0001 U.S.Robotics iProduct = 0x0002 USB Modem iSerialNumber = 0x000a 002 bNumConfigurations = 0x0001 # sysctl -a dev.umodem dev.umodem.0.%desc: AltIf0 dev.umodem.0.%driver: umodem dev.umodem.0.%location: bus=1 hubaddr=1 port=1 devaddr=2 interface=0 dev.umodem.0.%pnpinfo: vendor=0x0baf product=0x0303 devclass=0x02 devsubclass=0x00 sernum=002 release=0x0200 mode=host intclass=0x02 intsubclass=0x02 intprotocol=0x01 ttyname=U0 ttyports=1 dev.umodem.0.%parent: uhub1 ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
usb/165154: USB patch for new u3g device
Number: 165154 Category: usb Synopsis: USB patch for new u3g device Confidential: no Severity: non-critical Priority: medium Responsible:freebsd-usb State: open Quarter: Keywords: Date-Required: Class: update Submitter-Id: current-users Arrival-Date: Tue Feb 14 21:20:07 UTC 2012 Closed-Date: Last-Modified: Originator: mike tancsa Release:RELENG_8 Organization: Sentex Communications Environment: 8.2-STABLE FreeBSD 8.2-STABLE #0: Tue Feb 14 14:24:26 EST 2012 i386 Description: Hi, Sierra has a new air card to do LTE (Aircard 313U). It seems to work well with FreeBSD after the simple patches below. ugen3.3: AirCard 313U Sierra Wireless, Incorporated at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x1199 idProduct = 0x68aa bcdDevice = 0x0006 iManufacturer = 0x0003 Sierra Wireless, Incorporated iProduct = 0x0002 AirCard 313U iSerialNumber = 0x0004 01269827166 bNumConfigurations = 0x0001 ugen3.3: AirCard 313U Sierra Wireless, Incorporated at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x00bf bNumInterfaces = 0x0007 bConfigurationValue = 0x0001 iConfiguration = 0x0001 Sierra Configuration bmAttributes = 0x00a0 bMaxPower = 0x00fa Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x00ff bInterfaceSubClass = 0x00ff bInterfaceProtocol = 0x00ff iInterface = 0x no string Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 IN bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0200 bInterval = 0x0020 bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0001 OUT bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0200 bInterval = 0x0020 bRefresh = 0x bSynchAddress = 0x Interface 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x00ff bInterfaceSubClass = 0x00ff bInterfaceProtocol = 0x00ff iInterface = 0x no string Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0082 IN bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0200 bInterval = 0x0020 bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0002 OUT bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0200 bInterval = 0x0020 bRefresh = 0x bSynchAddress = 0x Interface 2 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0002 bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x00ff bInterfaceSubClass = 0x00ff bInterfaceProtocol = 0x00ff iInterface = 0x no string Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0083 IN bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0200 bInterval = 0x0020 bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0003 OUT bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0200 bInterval = 0x0020 bRefresh = 0x bSynchAddress = 0x Interface 3 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0003 bAlternateSetting = 0x bNumEndpoints = 0x0003 bInterfaceClass = 0x00ff bInterfaceSubClass = 0x00ff bInterfaceProtocol = 0x00ff iInterface = 0x no string Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0084 IN bmAttributes = 0x0003 INTERRUPT wMaxPacketSize = 0x0040 bInterval = 0x0005 bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0085 IN bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0200 bInterval = 0x0020 bRefresh = 0x bSynchAddress = 0x
FreeBSD and Sierra Wireless AirCard 313U
The following PPP entry works form me pppgprs: set device /dev/cuaU0.3 set server /var/run/gprs-internet 0177 #set speed 921600 set timeout 0 set authname wapuser1 set authkey wap set dial ABORT BUSY TIMEOUT 2 \ \\ \ AT OK-AT-OK \ AT+CFUN=1 OK-AT-OK \ AT+CMEE=2 OK-AT-OK \ AT+CSQ OK \ AT+CGDCONT=1,\\\IP\\\,\\\internet.com\\\ OK \ AT+CGACT? OK-AT-OK \ AT+CGATT? OK \ AT+CGCLASS? OK \ AT+COPS? OK \ AT+CNUM OK \ ATv OK \ ATD*99# CONNECT set crtscts on #set mtu maximum 296 #set mru maximum 296 disable vjcomp disable acfcomp disable deflate disable deflate24 disable pred1 disable protocomp disable mppe disable ipv6cp disable lqr disable echo nat enable yes enable dns resolv writable set dns 8.8.8.8 set ifaddr 10.1.0.2/0 10.1.0.1/0 255.255.255.255 0.0.0.0 add default HISADDR # See ppp.link* # diff -u usbdevs.prev usbdevs --- usbdevs.prev2012-02-14 15:06:33.0 -0500 +++ usbdevs 2012-02-14 15:13:29.0 -0500 @@ -2974,6 +2974,7 @@ product SIERRA MC8790 0x683C MC8790 product SIERRA MC8791 0x683D MC8791 product SIERRA MC8792 0x683E MC8792 +product SIERRA AC313U 0x68aa Sierra Wireless AirCard 313U product SIERRA AC880 0x6850 Sierra Wireless AirCard 880 product SIERRA AC881 0x6851 Sierra Wireless AirCard 881 product SIERRA AC880E 0x6852 Sierra Wireless AirCard 880E # diff -u u3g.c.prev u3g.c --- u3g.c.prev 2012-02-14 15:05:02.0 -0500 +++ u3g.c 2012-02-14 15:13:52.0 -0500 @@ -432,6 +432,7 @@ U3G_DEV(QUANTA, Q111, 0), U3G_DEV(SIERRA, AC402, 0), U3G_DEV(SIERRA, AC595U, 0), + U3G_DEV(SIERRA, AC313U, 0), U3G_DEV(SIERRA, AC597E, 0), U3G_DEV(SIERRA, AC875E, 0), U3G_DEV(SIERRA, AC875U, 0), ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
serial console on USB ?
I came across a thread mentioning potential patches being added a while back to allow for the console to work with USB, but I am not able to get it to work with RELENG_8 If I just add ttyU0 /usr/libexec/getty std.9600 vt100 on secure I can login to the box no problem. But That does not show bootup access via the serial console. Is there a way to enable that ? I tried adding console=comconsole,vidconsole hw.usb.ucom.cons_unit=0 hw.usb.ucom.cons_baud=9600 to /boot/loader.conf but it did not work # usbconfig ugen0.1: EHCI root HUB Intel at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.1: EHCI root HUB Intel at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.2: product 0x0024 vendor 0x8087 at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.2: product 0x0024 vendor 0x8087 at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.3: usb serial converter ftdi at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen0.4: product 0x1400 vendor 0x04d9 at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON # sysctl -a hw.usb hw.usb.ehci.lostintrbug: 0 hw.usb.ehci.iaadbug: 0 hw.usb.ehci.no_hs: 0 hw.usb.ehci.debug: 0 hw.usb.ohci.debug: 0 hw.usb.uhci.loop: 0 hw.usb.uhci.debug: 0 hw.usb.no_boot_wait: 0 hw.usb.ctrl.debug: 0 hw.usb.umass.debug: 0 hw.usb.debug: 0 hw.usb.dev.debug: 0 hw.usb.usb_lang_mask: 255 hw.usb.usb_lang_id: 9 hw.usb.template: 0 hw.usb.ugen.debug: 0 hw.usb.power_timeout: 30 hw.usb.uhub.debug: 0 hw.usb.no_pf: 0 hw.usb.proc.debug: 0 hw.usb.pr_recovery_delay: 250 hw.usb.pr_poll_delay: 50 hw.usb.no_cs_fail: 0 hw.usb.uftdi.debug: 0 hw.usb.ucom.cons_baud: 9600 hw.usb.ucom.cons_subunit: 0 hw.usb.ucom.cons_unit: 0 hw.usb.ucom.debug: 0 hw.usb.uhid.debug: 0 hw.usb.ukbd.no_leds: 0 hw.usb.ukbd.debug: 0 hw.usb.ums.debug: 0 ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: device reset
On 8/27/2011 9:00 AM, Hans Petter Selasky wrote: On Saturday 27 August 2011 14:59:50 Marcin Wisnicki wrote: On Sat, Aug 27, 2011 at 14:04, Hans Petter Selasky hsela...@c2i.net wrote: On Saturday 27 August 2011 13:19:35 Marcin Wisnicki wrote: Would it be possible to reinstate ability to power-cycle particular port the way it was ~year ago ? This is still possible. There is a sysctl to disable this feature: sysctl hw.usb.no_cs_fail=1 $ sysctl hw.usb.no_cs_fail sysctl: unknown oid 'hw.usb.no_cs_fail' $ uname -v FreeBSD 8.2-STABLE #4: Sun Jun 26 15:10:04 CEST 2011 r...@ghost.pnet.one.pl:/home/obj/usr/src/sys/SERWER_DDB You need the kernel from the latest 8-stable. How do you power cycle just one port ? ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: device reset
On 8/26/2011 2:55 AM, Hans Petter Selasky wrote: Any other tricks you can think of to reset the device short of installing a HUB at each location ? No. Upgrading the modem firmware. Talking to the vendor about it. Understood. I did some more testing with the version of the kernel I have in the field locally. When the 3g modem has not crashed, I can reset it just fine using usbcontrol reset. I also found a Dlink hub that when I issue a usbcontrol power_off and power_on it really does power off and on the port. This will be handy for a couple of remote sites for me... ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
device reset
I am having periodic problems with the odd u3g device that gets hung. If I try and reset it, it totally locks up and I need to do a reboot of the box the recover. Apart from usbconfig reset are is there anything else I can do to recover from such a situation ? usbconfig -d 1.3 dump_info ugen1.3: ZTE CDMA Technologies MSM ZTE, Incorporated at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON usbconfig -d 1.3 dump_all_config_desc ugen1.3: ZTE CDMA Technologies MSM ZTE, Incorporated at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0100 bNumInterfaces = 0x0004 bConfigurationValue = 0x0001 iConfiguration = 0x no string bmAttributes = 0x00a0 bMaxPower = 0x00fa Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x bInterfaceClass = 0x00ff bInterfaceSubClass = 0x00ff bInterfaceProtocol = 0x00ff iInterface = 0x no string Additional Descriptor bLength = 0x05 dmesg shows at bootup time ugen0.2: APC at usbus0 ugen1.3: ZTE, Incorporated at usbus1 ugen1.3: ZTE, Incorporated at usbus1 (disconnected) ugen1.3: ZTE, Incorporated at usbus1 u3g0: ZTE, Incorporated ZTE CDMA Technologies MSM, class 0/0, rev 2.00/0.00, addr 3 on usbus1 u3g0: Found 1 port. umass0: ZTE, Incorporated ZTE CDMA Technologies MSM, class 0/0, rev 2.00/0.00, addr 3 on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x umass0:0:0:-1: Attached to scbus0 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI status: Check Condition (probe0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: ZTE MMC Storage 322 Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present if I do a usbconfig -d 1.3 reset I get u3g0: at uhub1, port 1, addr 3 (disconnected) umass0: at uhub1, port 1, addr 3 (disconnected) (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored) usbd_req_re_enumerate: addr=3, set address failed! (USB_ERR_TIMEOUT, ignored) I have also tried post reset # usbconfig -d 1.3 set_config 255 # usbconfig -d 1.3 set_config 0 usbconfig: could not set config index: Input/output error # This is RELENG_8 on an alix box from July 14th. -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: device reset
On 8/25/2011 3:02 PM, Hans Petter Selasky wrote: On Thursday 25 August 2011 21:00:17 Mike Tancsa wrote: I am having periodic problems with the odd u3g device that gets hung. If I try and reset it, it totally locks up and I need to do a reboot of the box the recover. Apart from usbconfig reset are is there anything else I can do to recover from such a situation ? Hi, Have you tried using an external self-powered HUB? Yes, seems to work with the hub There has been some patches to auto-reset non-responding USB devices, which you might try which was committed to 8-stable not long ago. How recent were those patches applied ? I am running stable from July 14th. ---Mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: boot hang without xhci [updated patch]
On 7/22/2011 4:22 AM, Hans Petter Selasky wrote: Please try the attached patch for /sys/dev/pci: Looks good! Its able to boot up with and without xhci loaded. 0(ich10)# patch p Hmm... Looks like a unified diff to me... The text leading up to this was: -- |=== pci.c |== |--- pci.c (revision 224243) |+++ pci.c (local) -- Patching file pci.c using Plan A... Hunk #1 succeeded at 62. Hunk #2 succeeded at 2782 (offset -175 lines). Hunk #3 succeeded at 2890 (offset -175 lines). Hmm... Ignoring the trailing garbage. done 0(ich10)# none3@pci0:0:31:3: class=0x0c0500 card=0x20088086 chip=0x1c228086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = SMBus bar [10] = type Memory, range 64, base 0xfe624000, size 256, enabled bar [20] = type I/O Port, range 32, base 0xf040, size 32, enabled none4@pci0:2:0:0: class=0x0c0330 card=0x20088086 chip=0x01941033 rev=0x03 hdr=0x00 vendor = 'NEC Electronics Hong Kong' class = serial bus subclass = USB cap 01[50] = powerspec 3 supports D0 D3 current D0 cap 05[70] = MSI supports 8 messages, 64 bit cap 11[90] = MSI-X supports 8 messages in map 0x10 cap 10[a0] = PCI-Express 2 endpoint max data 128(128) link x1(x1) ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected ecap 0003[140] = Serial 1 ecap 0018[150] = unknown 1 I can do a kldload post boot of xhci as well as boot with it loaded at boot time from /boot/loader.conf. xhci0@pci0:2:0:0: class=0x0c0330 card=0x20088086 chip=0x01941033 rev=0x03 hdr=0x00 vendor = 'NEC Electronics Hong Kong' class = serial bus subclass = USB cap 01[50] = powerspec 3 supports D0 D3 current D0 cap 05[70] = MSI supports 8 messages, 64 bit cap 11[90] = MSI-X supports 8 messages in map 0x10 cap 10[a0] = PCI-Express 2 endpoint max data 128(128) link x1(x1) ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected ecap 0003[140] = Serial 1 ecap 0018[150] = unknown 1 ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
boot hang without xhci
More for the archives in case anyone else runs into this. We got a new desktop board in that we were testing out netbooting and noticed that without xhci loaded in the kernel the box hangs with the last thing being initialized em0 (full dmesg etc at http://www.tancsa.com/xhci.txt) Its an Intel DQ67SW ata2: [ITHREAD] ata3: ATA channel 1 on atapci0 ata3: [ITHREAD] pci0: simple comms, UART at device 22.3 (no driver attached) em0: Intel(R) PRO/1000 Network Connection 7.2.3 port 0xf080-0xf09f mem 0xfe60-0xfe61,0xfe628000-0xfe628fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: [FILTER] em0: Ethernet address: 00:22:4d:52:04:46 with usb 3 disabled in the BIOS, or with xhci loaded, all boots fine as shown below. ata2: [ITHREAD] ata3: ATA channel 1 on atapci0 ata3: [ITHREAD] pci0: simple comms, UART at device 22.3 (no driver attached) em0: Intel(R) PRO/1000 Network Connection 7.2.3 port 0xf080-0xf09f mem 0xfe60-0xfe61,0xfe628000-0xfe628fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: [FILTER] em0: Ethernet address: 00:22:4d:52:04:46 ehci0: EHCI (generic) USB 2.0 controller mem 0xfe627000-0xfe6273ff irq 16 at device 26.0 on pci0 ehci0: [ITHREAD] usbus0: EHCI version 1.0 usbus0: EHCI (generic) USB 2.0 controller on ehci0 pci0: multimedia, HDA at device 27.0 (no driver attached) pcib1: ACPI PCI-PCI bridge irq 17 at device 28.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge irq 18 at device 28.6 on pci0 pci2: ACPI PCI bus on pcib2 xhci0: XHCI (generic) USB 3.0 controller mem 0xfe50-0xfe501fff irq 18 at device 0.0 on pci2 xhci0: [ITHREAD] xhci0: 32 byte context size. -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Mapping ugen devices to corresponding /dev/cuaUx ?
On 6/6/2011 10:40 AM, Karl Pielorz wrote: Is there any way of knowing which ugen devices map to which devices in /dev? (The system has cuaU0 through cuaU8). Hi, RELENG_8 has a bit more info. Not sure when the change was in, but in sysctl, I see things like 0(ich10)# usbconfig | grep -i ftd ugen1.2: usb serial converter ftdi at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen2.2: usb serial converter ftdi at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen2.3: usb serial converter ftdi at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON 0(ich10)# sysctl -a dev.uftdi dev.uftdi.0.%desc: usb serial converter dev.uftdi.0.%driver: uftdi dev.uftdi.0.%location: bus=1 hubaddr=1 port=1 devaddr=2 interface=0 dev.uftdi.0.%pnpinfo: vendor=0x0403 product=0x6001 devclass=0x00 devsubclass=0x00 sernum=ftEG4Z0V release=0x0400 intclass=0xff intsubclass=0xff ttyname=U0 ttyports=1 dev.uftdi.0.%parent: uhub1 dev.uftdi.1.%desc: usb serial converter dev.uftdi.1.%driver: uftdi dev.uftdi.1.%location: bus=1 hubaddr=1 port=2 devaddr=2 interface=0 dev.uftdi.1.%pnpinfo: vendor=0x0403 product=0x6001 devclass=0x00 devsubclass=0x00 sernum=ftEG3NR6 release=0x0400 intclass=0xff intsubclass=0xff ttyname=U1 ttyports=1 dev.uftdi.1.%parent: uhub2 dev.uftdi.2.%desc: usb serial converter dev.uftdi.2.%driver: uftdi dev.uftdi.2.%location: bus=1 hubaddr=2 port=2 devaddr=3 interface=0 dev.uftdi.2.%pnpinfo: vendor=0x0403 product=0x6001 devclass=0x00 devsubclass=0x00 sernum=ftEGY0XE release=0x0400 intclass=0xff intsubclass=0xff ttyname=U2 ttyports=1 dev.uftdi.2.%parent: uhub2 0(ich10)# Same with umodem and u3g # usbconfig ugen0.1: OHCI root HUB AMD at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen1.1: EHCI root HUB AMD at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.2: USB Modem U.S.Robotics at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.2: Globetrotter HSDPA Modem Option N.V. at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON # sysctl -a dev. | grep tty dev.umodem.0.%pnpinfo: vendor=0x0baf product=0x0303 devclass=0x02 devsubclass=0x00 sernum=002 release=0x0200 intclass=0x02 intsubclass=0x02 ttyname=U0 ttyports=1 dev.u3g.0.%pnpinfo: vendor=0x0af0 product=0x6901 devclass=0xff devsubclass=0xff sernum=Serial Number release=0x intclass=0xff intsubclass=0xff ttyname=U1 ttyports=3 -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: usb errors on RELENG_8
On 5/11/2011 2:21 AM, Hans Petter Selasky wrote: Try to send this USB control request to the HUB and then re-plug the device. Does it help? usbconfig -d X.Y do_request 0x23 0x09 0x 0x0001 0 Hi, I get this command 0[upsmon1]# usbconfig -d 1.8 do_request 0x23 0x09 0x 0x0001 0 REQUEST = OK 0[upsmon1]# It seems to quiet things down. What does the command do ? ---Mike -- --- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, m...@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
usb/154127: device IDs for MC547 u3g modem
Number: 154127 Category: usb Synopsis: device IDs for MC547 u3g modem Confidential: no Severity: non-critical Priority: low Responsible:freebsd-usb State: open Quarter: Keywords: Date-Required: Class: change-request Submitter-Id: current-users Arrival-Date: Wed Jan 19 00:40:07 UTC 2011 Closed-Date: Last-Modified: Originator: mike tancsa Release:RELENG_8 Jan 17 2011 Organization: Sentex Environment: 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #11: Mon Jan 17 10:44:25 EST 2011 i386 Description: Bell Canada is selling a new Ovation/Novatel 3G modem. NOVATEL MC547. The following two patches add support for the device diff -u usbdevs.orig usbdevs --- usbdevs.orig2011-01-17 10:30:36.0 -0500 +++ usbdevs 2011-01-17 11:33:06.0 -0500 @@ -2388,6 +2388,7 @@ product NOVATEL ZEROCD20x5030 Novatel ZeroCD product NOVATEL U727_2 0x5100 Merlin U727 CDMA product NOVATEL U760 0x6000 Novatel U760 +product NOVATEL MC547 0x7042 Novatel MC547 product NOVATEL MC760 0x6002 Novatel MC760 product NOVATEL2 FLEXPACKGPS 0x0100 NovAtel FlexPack GPS receiver --- u3g.c 2010-12-02 21:34:53.0 -0500 +++ /tmp/u3g.c 2011-01-18 13:48:23.0 -0500 @@ -65,7 +65,7 @@ #include #ifdef USB_DEBUG -static int u3g_debug = 0; +static int u3g_debug = 1; SYSCTL_NODE(_hw_usb, OID_AUTO, u3g, CTLFLAG_RW, 0, USB 3g); SYSCTL_INT(_hw_usb_u3g, OID_AUTO, debug, CTLFLAG_RW, @@ -302,6 +302,7 @@ U3G_DEV(NOVATEL, EU730, 0), U3G_DEV(NOVATEL, EU740, 0), U3G_DEV(NOVATEL, EU870D, 0), + U3G_DEV(NOVATEL, MC547, 0), U3G_DEV(NOVATEL, MC760, 0), U3G_DEV(NOVATEL, MC950D, 0), U3G_DEV(NOVATEL, U720, 0), How-To-Repeat: n/a Fix: The above device id and patch to u3g.c will do the trick! ugen1.3: Novatel Wireless, Inc. at usbus1 u3g_attach: sc=0xc2d83000 u3g0: Novatel Wireless, Inc. Novatel Wireless HSPA, class 0/0, rev 2.00/0.00, addr 3 on usbus1 u3g0: Found 5 ports. ugen1.3: Novatel Wireless HSPA Novatel Wireless, Inc. at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x1410 idProduct = 0x7042 bcdDevice = 0x iManufacturer = 0x0003 Novatel Wireless, Inc. iProduct = 0x0002 Novatel Wireless HSPA iSerialNumber = 0x0004 123456789012341 bNumConfigurations = 0x0001 ugen1.3: Novatel Wireless HSPA Novatel Wireless, Inc. at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x00a1 bNumInterfaces = 0x0006 bConfigurationValue = 0x0001 iConfiguration = 0x0001 Novatel Configuration bmAttributes = 0x00e0 bMaxPower = 0x00fa Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0003 bInterfaceClass = 0x00ff bInterfaceSubClass = 0x00ff bInterfaceProtocol = 0x00ff iInterface = 0x no string Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 IN bmAttributes = 0x0003 INTERRUPT wMaxPacketSize = 0x0040 bInterval = 0x0005 bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0082 IN bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0200 bInterval = 0x0020 bRefresh = 0x bSynchAddress = 0x Endpoint 2 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0001 OUT bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0200 bInterval = 0x0020 bRefresh = 0x bSynchAddress = 0x Interface 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x00ff bInterfaceSubClass = 0x00ff bInterfaceProtocol = 0x00ff iInterface = 0x no string Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0083 IN bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0200 bInterval = 0x0020 bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0002 OUT bmAttributes = 0x0002 BULK wMaxPacketSize = 0x0200 bInterval = 0x0020 bRefresh = 0x bSynchAddress = 0x Interface 2 bLength = 0x0009 bDescriptorType = 0x0004
Re: USB_ERR_TIMEOUT and USB_ERR_STALLED
At 07:49 PM 10/23/2010, Weongyo Jeong wrote: Weongyo is working on a usbdump utility to monitor ongoing USB traffic. It's merged into HEAD not too lately. :-) Hi, I built an image from HEAD that I will try out. How do I get your utility ? ---Mike regards, Weongyo Jeong Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
USB_ERR_TIMEOUT and USB_ERR_STALLED
I am trying to use RELENG_8 to monitor a number of APC upses and it seems when there are more than one, I start to see a lot of USB errors with the devices coming and going In the logs, I see a lot of # grep USB /var/log/all.log | tail Oct 21 10:24:05 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:25:47 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:27:45 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:29:44 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:30:35 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub5 Oct 21 10:32:35 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:37:04 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:38:38 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub4 Oct 21 10:44:14 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub5 Oct 21 10:45:09 upsmon1 root: Unknown USB device: vendor 0x051d product 0x0002 bus uhub5 # usbconfig ugen0.1: UHCI root HUB Intel at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: UHCI root HUB Intel at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen2.1: UHCI root HUB Intel at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.1: EHCI root HUB Intel at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen3.2: product 0xf103 vendor 0x2001 at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.2: Back-UPS RS 1500 FW:8.g8 .D USB FW:g8 American Power Conversion at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.3: Back-UPS RS 1500 FW:8.g8 .D USB FW:g8 American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.4: Back-UPS RS 1500 FW:8.g9a.D USB FW:g9a American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.5: Back-UPS RS 1500 FW:8.g8 .D USB FW:g8 American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.6: Back-UPS RS 1500 FW:8.g9a.D USB FW:g9a American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.7: Back-UPS RS 1500 FW:8.g4 .D USB FW:g4 American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.8: USB2.0 Hub vendor 0x05e3 at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen3.9: Back-UPS RS 1500 FW:8.g8 .D USB FW:g8 American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.10: Back-UPS RS 1500 FW:8.g7 .D USB FW:g7 American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen3.11: Back-UPS RS 1500 FW:8.g8 .D USB FW:g8 American Power Conversion at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON This is with a kernel from Oct 4th, i386. Any idea what might be up or how to debug this ?? Setting hw.usb.debug to anything 0 causes the system to almost hang under the load unfortunately. ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: ZTE USB 3g stick
At 07:49 AM 8/28/2010, Matthew Luckie wrote: ugen6.2: ZTE,Incorporated at usbus6 umass0: ZTE,Incorporated ZTE CDMA Technologies MSM, class 0/0, rev 2.00/0.00, addr 2 on usbus6 cd1 at umass-sim0 bus 0 scbus2 target 0 lun 0 cd1: ZTE USB SCSI CD-ROM 2.31 Removable CD-ROM SCSI-2 device cd1: 40.000MB/s transfers cd1: cd present [31484 x 2048 byte records] Sadly no /dev/cuaU* entries. After the set_config, I have new /dev entries for cd1, iso9660, pass1, and of course ugen6.2. What if you do a camcontrol eject pass0 (or pass1 if its 1) I have also found the odd ZTE stick where post power up, I need to do a reset for some odd reason. Perhaps a firmware issue with some ZTE sticks ? not sure usbconfig -d 6.2 reset or usbconfig -d 6.2 power_off usbconfig -d 6.2 power_on ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
apcupsd port regression from 7x. to 8.x
While apcupsd works fine with one ups hooked up, apcupsd is not able
to find multiple ones like it did on RELENG_7. Looking at the way
the code is compiled, it uses the generic libusd driver to talk to
and find the UPSes on RELENG_8. Not sure if this is a bug with
apcupsd or how it works with RELENG_8.
Running the daemon in debug mode, it loops through the following
code, but always finds the same UPS and never 'moves on' to the next
UPS like it did in RELENG_7. Has anyone got multiple UPSes working
with apcupsd on RELENG_8 ?
/* Initialize libusb */
Dmsg0(200, Initializing libusb\n);
usb_init();
/* Enumerate usb busses and devices */
i = usb_find_busses();
Dmsg1(200, Found %d USB busses\n, i);
i = usb_find_devices();
Dmsg1(200, Found %d USB devices\n, i);
/* Iterate over all devices, checking for idVendor=APC */
bus = usb_get_busses();
while (bus)
{
dev = bus-devices;
while (dev)
{
Dmsg4(200, MDT bus loop %s:%s - %04x:%04x\n,
bus-dirname, dev-filename,
dev-descriptor.idVendor, dev-descriptor.idProduct);
if (dev-descriptor.idVendor == VENDOR_APC) {
Dmsg2(200, Trying device %s:%s\n, bus-dirname, dev-filename);
if (init_device(ups, dev)) {
/* Successfully found and initialized an UPS */
astrncpy(ups-device, bus-dirname, sizeof(ups-device));
astrncat(ups-device, :, sizeof(ups-device));
astrncat(ups-device, dev-filename, sizeof(ups-device));
return 1;
}
}
dev = dev-next;
}
bus = bus-next;
}
/* Failed to find an UPS */
ups-device[0] = 0;
return 0;
}
Where as the following are attached. It only is ever able to talk to
the ups on ugen1.2
0[upsmon1]# usbconfig
ugen0.1: UHCI root HUB VIA at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen1.1: UHCI root HUB VIA at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen2.1: UHCI root HUB VIA at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen3.1: UHCI root HUB VIA at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON
ugen4.1: EHCI root HUB VIA at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON
ugen0.2: Back-UPS ES 725 FW:802.n2.D USB FW:n2 APC at usbus0, cfg=0
md=HOST spd=LOW (1.5Mbps) pwr=ON
ugen4.2: USB2.0 Hub vendor 0x05e3 at usbus4, cfg=0 md=HOST spd=HIGH
(480Mbps) pwr=SAVE
ugen4.3: Back-UPS ES 500 FW:801.e5.D USB FW:e5 APC at usbus4, cfg=0
md=HOST spd=LOW (1.5Mbps) pwr=ON
ugen0.3: Back-UPS RS 1500 FW:8.g7 .D USB FW:g7 American Power
Conversion at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON
ugen4.4: Back-UPS ES 650 FW:825.B1.D USB FW:B1 APC at usbus4, cfg=0
md=HOST spd=LOW (1.5Mbps) pwr=ON
ugen4.5: Back-UPS RS 1500 FW:8.g8 .D USB FW:g8 American Power
Conversion at usbus4, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON
ugen4.6: Back-UPS ES 500 FW:824.B1.D USB FW:B1 APC at usbus4, cfg=0
md=HOST spd=LOW (1.5Mbps) pwr=ON
ugen1.2: Back-UPS ES 500 FW:824.B1.D USB FW:B1 APC at usbus1, cfg=0
md=HOST spd=LOW (1.5Mbps) pwr=ON
0[upsmon1]#
0.000 apcupsd: apcupsd.c:219 Options parsed.
0.001 apcupsd: apcconfig.c:803 After config scriptdir:
/usr/local/etc/apcupsd.a
0.001 apcupsd: apcconfig.c:804 After config pwrfailpath: /var/run/a
0.001 apcupsd: apcconfig.c:805 After config nologinpath: /var/run
0.001 apcupsd: apcupsd.c:242 Config file
/usr/local/etc/apcupsd.a/apcupsd.conf processed.
0.001 apcupsd: :newups.c:102 write_lock at drivers.c:181
0.001 apcupsd: drivers.c:183 Looking for driver: usb
0.001 apcupsd: drivers.c:187 Driver dumb is configured.
0.001 apcupsd: drivers.c:187 Driver apcsmart is configured.
0.001 apcupsd: drivers.c:187 Driver net is configured.
0.001 apcupsd: drivers.c:187 Driver usb is configured.
0.001 apcupsd: drivers.c:190 Driver usb found and attached.
0.001 apcupsd: newups.c:108 write_unlock at drivers.c:207
0.001 apcupsd: drivers.c:209 Driver ptr=0x805c8e4
0.001 apcupsd: apcupsd.c:261 Attached to driver: usb
0.003 apcupsd: newups.c:102 write_lock at generic-usb.c:614
0.003 apcupsd: generic-usb.c:398 Initializing libusb
0.003 apcupsd: generic-usb.c:403 Found 0 USB busses
0.007 apcupsd: generic-usb.c:405 Found 0 USB devices
0.007 apcupsd: generic-usb.c:416 /dev/usb:/dev/ugen1.2 - 051d:0002
0.007 apcupsd: generic-usb.c:419 Trying device /dev/usb:/dev/ugen1.2
0.153 apcupsd: hidutils.c:62 Report descriptor:
0.153 apcupsd: apclog.c:158 Dumping 840 bytes @ 0x2823e000
Mike Tancsa, tel +1 519 651 3400
Sentex Communications,m...@sentex.net
Providing Internet since 1994www.sentex.net
Cambridge, Ontario Canada www.sentex.net/mike
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb
Re: apcupsd port regression from 7x. to 8.x
At 03:56 PM 5/6/2010, Hans Petter Selasky wrote: Have you tried FreeBSD 8-STABLE ? Hi, This is with RELENG_8 as of this morning. ---Mike --HPS Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: apcupsd port regression from 7x. to 8.x
At 04:40 PM 5/6/2010, Hans Petter Selasky wrote: 0.003 apcupsd: generic-usb.c:398 Initializing libusb The FreeBSD LibUSB v0.1 reports the wrong number of busses and devices. I can fix this. Great! 0.003 apcupsd: generic-usb.c:403 Found 0 USB busses 0.007 apcupsd: generic-usb.c:405 Found 0 USB devices The problem is that the UPS code is designed to attach to the first matching device only. LibUSB does not hide devices with drivers already attached, which I think your utility assumes. You should use: pidfile, see man pidfile To create a temporary file with some string which consists of all numbers in udev-filename, separated by .. Or USB LibUSB v.1.0! I am guessing the program would need to be re-written to use v1.0 ? Thanks for the feedback and help as always! I also found another work around by the author of the daemon which works great! http://kroptech.com/mailimport/showmsg.php?msg_id=3665255961db_name=apcupsd-users I've made a small patch, but it won't fix your issue :-( http://p4web.freebsd.org/@@177865?ac=10 --HPS Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: USB serial device naming
iInterface = 0x0005 AltIf0 Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x00 RAW dump: 0x00 | 0x05, 0x24, 0x00, 0x01, 0x10 Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: USB modem?
At 10:40 PM 12/9/2009, Ernst W. Winter wrote: Hello, well I have a NetPC from Asus with a UMTS modem. What is the output of usbdevs -v or if RELENG_8 usbconfig dump_device_desc ---Mike Is there anything for it that I can use with FreeBSD? I can use it with Ubuntu, tried once and testet and it works, but since I use FreeBSD only it would be nice to know that it is possible too with FreeBSD. Thanks in advance for any feedback. Ernst Winter -- O ascii ribbon campaign - stop html mail - www.asciiribbon.org Mail plain ASCII text. HTML Base64 text are spam. ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: USB modem?
At 03:42 PM 12/10/2009, Ernst W. Winter wrote: ugen4.3: HUAWEI Mobile HUAWEI Technology at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x12d1 idProduct = 0x1001 bcdDevice = 0x iManufacturer = 0x0002 HUAWEI Technology iProduct = 0x0001 HUAWEI Mobile iSerialNumber = 0x no string bNumConfigurations = 0x0001 It should be recognized by the stock u3g driver. If you do kldload u3g, do some /dev/cuaU#.# devices appear ? and here the uname -a: FreeBSD eeepc.ewinter.org 9.0-CURRENT FreeBSD 9.0-CURRENT #5: Mon Nov 16 07:57:28 CET 2009 ewin...@eeepc.ewinter.org:/usr/obj/usr/src/sys/eeepc i386 RELENG_8 and above should be the same for this. ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: help setting u3g speed and help with new device
At 03:29 AM 10/3/2009, Hans Petter Selasky wrote: On an older generation 378, all I did was add the device ID and all works just fine Not sure if it makes a difference, but the connect speed on the working 378 shows Jan 1 08:38:33 alix ppp[1758]: tun10: Chat: Received: CONNECT 360 vs Oct 2 10:11:37 378n ppp[1085]: tun10: Chat: Received: CONNECT 720 How do I find out what the right speed is and set it for the device ? Despite the higher connect speed, I get a transfer rate of about 21Kbps. On the older gen modem, I get 1,376Kbps Have you checked the 3GPP specification for AT commands which report which carrier you are connected at? Hi, I am not sure how to do that on this unit. I did look through http://www.shapeshifter.se/wp-content/uploads/2008/04/27007-830.pdf AT command set for User Equipment (UE) but I didnt find anything that seems to report the actual connect speed. Do you know of any better documentation ? Possibly your modem is using GPRS because it doesn't find any HSDPA or whatsoever faster carrier. I cant seem to get anything more than Oct 3 07:28:57 dw994 ppp[3474]: tun0: Chat: Received: ATD*99#^M^M Oct 3 07:28:57 dw994 ppp[3474]: tun0: Chat: Received: CONNECT 720^M which seems like a reasonable speed. The signal q is good and the other modems around it get their full speeds as well at+csq +CSQ: 18,99 OK atv C: 1; D: 2; F: 0; E: 1; I: 0; L: 0; M: 0; Q: 0; V: 1; X: 0; Z: 0; S0: 0; S3: 13; S4: 10; S5: 8; S6: 2; S7: 50; S8: 2; S9: 6; S10: 14; S11: 95; +FCLASS: 0; +ICF: 3,3; +IFC: 2,2; +IPR: 115200; +DR: 1; +DS: 0,0,2048,6; +WS46: 12; +CBST: 0,0,1; +CRLP: (61,61,48,6,0),(61,61,48,6,1),(240,240,52,6,2); +CV120: 1,1,1,0,0,0; +CHSN: 0,0,0,0; +CSSN: 0,0; +CREG: 1; +CGREG: 0; +CFUN:; +CSCS: IRA; +CSTA: 129; +CR: 1; +CRC: 1; +CMEE: 2; +CGDCONT: (1,IP,internet.com,0.0.0.0,0,0) ; +CGDSCONT: ; +CGTFT: ; +CGEQREQ: ; +CGEQMIN: ; +CGQREQ: ; +CGQMIN: ; +CGEREP: 0,0; +CGDATA: PPP; +CGCLASS: A; +CGSMS: 1; +CSMS: 0; +CMGF: 0; +CSCA: +17057969300,145; +CSMP: ,,0,0; +CSDH: 0; +CSCB: 0,,; +FDD: 0; +FAR: 0; +FCL: 0; +FIT: 0,0; +ES: ,,; +ESA: 00,0,255,; +CMOD: 0; +CVHU: 1; +CPIN: ,; +CMEC: 0,0,0; +CKPD: 1,1; +CGATT: 1; +CGACT: 0; +CPBS: SM; +CPMS: SM,SM,SM; +CNMI: 0,0,0,0,0; +CMMS: 0; +FTS: 0; +FRS: 0; +FTH: 3; +FRH: 3; +FTM: 96; +FRM: 96; +CCUG: 0,0,0; +CUSD: 0; +CAOC: 1; +CCWA: 0; +CLVL: 2; +CMUT: 0; +CPOL: 0,2,,0,0,0; +CPLS: 0; +CTZR: 0; +CLIP: 0; +COLP: 1; +CLIR: 0; +CCLK:; +COPS: 0,0,,3; +CSIM: 14,; +CRSM: 0,0,0,0,0,; +CSMINS: 0; +VIP: 0; +VTS: ; +VTD: 1 ---Mike Also check for any stall printouts (not likely) when setting u3g debugging. --HPS Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
help setting u3g speed and help with new device
, 0x78, /* 4..7: CBW Tag, unique 32-bit number */
+0x00, 0x00, 0x00, 0x00, /* 8..11: CBW Transfer Length, no
data here */
+0x00, /* 12: CBW Flag: input */
+0x00, /* 13: CBW Lun */
+0x06, /* 14: CBW Length */
+
+0x01, /* 15+0: opcode */
+0x00, /* 15+1: byte2 */
+0x00, 0x00, /* 15+2..3 */
+0x00, /* 15+4: */
+0x00, /* 15+5: */
+0x00, 0x00, 0x00, 0x00, /* 15+6..15: */
+0x00, 0x00, 0x00, 0x00,
+0x00, 0x00
+};
+
+
static unsigned char cmotech_cmd[31] = {
0x55, 0x53, 0x42, 0x43,/* 0..3: Command Block Wrapper (CBW)
signature */
0x01, 0x00, 0x00, 0x00,/* 4..7: CBW Tag, unique 32-bit number */
@@ -683,6 +708,12 @@
changing ZTE STOR modem to
modem mode\n);
u3gstub_BBB_cmd(sc, ztestor_cmd);
break;
+ case U3GINIT_GTM3782005:
+ if (bootverbose || u3gdebug)
+ device_printf(sc-sc_dev,
+ changing GTM378 STOR modem to
modem mode\n);
+ u3gstub_BBB_cmd(sc, gtm3782005stor_cmd);
+ break;
case U3GINIT_CMOTECH:
if (bootverbose || u3gdebug)
device_printf(sc-sc_dev,
Mike Tancsa, tel +1 519 651 3400
Sentex Communications,m...@sentex.net
Providing Internet since 1994www.sentex.net
Cambridge, Ontario Canada www.sentex.net/mike
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: help setting u3g speed and help with new device
At 10:28 AM 10/2/2009, Mike Tancsa wrote: I am having problems getting the later Option GTM378, 380 and 382 3g modems to work properly with the u3g driver on FreeBSD. Older generation 378s work just fine, but I can crazy slow speeds when using the newer ones. (21kbps vs about 1.5Mb based on the signal here at the office) On an older generation 378, all I did was add the device ID and all works just fine Not sure if it makes a difference, but the connect speed on the working 378 shows Jan 1 08:38:33 alix ppp[1758]: tun10: Chat: Received: CONNECT 360 vs Oct 2 10:11:37 378n ppp[1085]: tun10: Chat: Received: CONNECT 720 How do I find out what the right speed is and set it for the device ? Despite the higher connect speed, I get a transfer rate of about 21Kbps. On the older gen modem, I get 1,376Kbps also, on the newer 378s I need to do a mode switch for it to work. On RELENG_7, I made the following changes based on what was in usb_modeswitch Here is the dmesg from RELENG_7 and RELENG_8. Not sure what the CSW error is about. I use the usb_modeswitch on RELENG_8 for now as I havent figured out how to best patch in the commands into the RELENG_8 version of the driver. u3g0: Qualcomm, Incorporated USB MMC Storage, class 0/0, rev 1.10/0.00, addr 2 on uhub0 u3g0: opening bulk-in pipe on endpoint 132 u3g0: opening bulk-in pipe on endpoint 5 Timecounter TSC frequency 498054012 Hz quality 800 Timecounters tick every 1.000 msec IPsec: Initialized Security Association Processing. u3g0: changing GTM378 STOR modem to modem mode u3g0: Sending CBW ad0: 1953MB SanDisk SDCFH2-002G HDX 4.32 at ata0-master PIO4 u3g0: Reading CSW u3g0: Failed to retrieve CSW to change to modem mode: IOERROR Trying to mount root from ufs:/dev/ad0s1a u3g0: at uhub0 port 2 (addr 2) disconnected u3g0: detached ucom0: Option N.V. Globetrotter HSDPA Modem, class 255/255, rev 1.10/0.00, addr 2 on uhub0 ucom0: Interface 0 of 3, not in use ucom0: Endpoint 0 of 3 ucom0: Endpoint 1 of 3 ucom0: Endpoint 2 of 3 ucom0: port=0 iface=0 in=0x82 out=0x2 ucom0: Interface 1 of 3, not in use ucom0: Endpoint 0 of 2 ucom0: Endpoint 1 of 2 ucom0: port=1 iface=1 in=0x84 out=0x4 ucom0: Interface 2 of 3, not in use ucom0: Endpoint 0 of 2 ucom0: Endpoint 1 of 2 ucom0: port=2 iface=2 in=0x85 out=0x5 ucom0: configured 3 serial ports (U0.%d) And RELENG_8 ugen0.2: USB MMC Storage Qualcomm, Incorporated at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x05c6 idProduct = 0x1000 bcdDevice = 0x iManufacturer = 0x0001 Qualcomm, Incorporated iProduct = 0x0002 USB MMC Storage iSerialNumber = 0x0003 0002 bNumConfigurations = 0x0001 ugen0.2: Qualcomm, Incorporated at usbus0 umass0: Qualcomm, Incorporated USB MMC Storage, class 0/0, rev 1.10/0.00, addr 2 on usbus0 umass0: SCSI over Bulk-Only; quirks = 0x umass0:0:0:-1: Attached to scbus0 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 (probe0:umass-sim0:0:0:0): Medium not present (probe0:umass-sim0:0:0:0): Unretryable error cd0 at umass-sim0 bus 0 target 0 lun 0 cd0: GT HSDPA Modem 3.00 Removable CD-ROM SCSI-2 device cd0: 1.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present and then with the mode switch Received inquiry data (detailed identification) - Vendor String: GT Model String: HSDPA Modem Revision String: 3.00 - Device description data (identification) - Manufacturer: Qualcomm, Incorporated Product: USB MMC Storage Serial No.: 0002 - Setting up communication with interface 0 ... Trying to send the message to endpoint 0x05 ... Sending the message returned error -1. Trying to continue - Run lsusb to note any changes. Bye. ugen0.2: Option N.V. at usbus0 u3g_attach:466: sc=0xc273 u3g0: Data Interface on usbus0 u3g0: Found 3 ports. ugen0.2: Globetrotter HSDPA Modem Option N.V. at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x00ff bDeviceSubClass = 0x00ff bDeviceProtocol = 0x00ff bMaxPacketSize0 = 0x0040 idVendor = 0x0af0 idProduct = 0x6901 bcdDevice = 0x iManufacturer = 0x0001 Option N.V. iProduct = 0x0002 Globetrotter HSDPA Modem iSerialNumber = 0x0004 Serial Number bNumConfigurations = 0x0001 at+csq +CSQ: 19,99 OK ati3 Manufacturer: Option N.V. Model: GTM378 Revision: 2.3.0Hd (Date: Jun 11 2007, Time: 13:48:00) yet doing a fetch shows the same very slow speeds alix# fetch -o /dev/null some big file via
Re: Huawei E160g
At 10:57 AM 10/2/2009, Dave Colborne wrote: Need to get Huawei E160G dongle to work in pcbsd. (Have latest ver.) would appreciate any assistance. What does usbdevs -v show ? ---Mike Thanks. Dave Colborne Best Weight Loss Program - Click Here! http://thirdpartyoffers.netzero.net/TGL2231/fc/BLSrjnxRO9pPmqfILPp86itbqZRZNcJHh4T5UfnpNOMtr1e9CD8FavY2Ns0/ ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Polling support for USB serial port adapters
At 01:09 PM 9/25/2009, Hans Petter Selasky wrote: Hi, At EuroBSDcon 2009 I was requested to add support for polling mode to the USB serial port adapters alike UKBD and UMASS. Which USB serial port adapters should have this support at first? And I also need someone to volunteers testing this! uftdi is the most common around here. I have a couple of manufacturers that I would be happy to try in some high speed and low speed apps. ---Mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: USB_ERR_IOERROR on cold boot, not warm boot
At 03:05 AM 9/5/2009, Hans Petter Selasky wrote: On Friday 04 September 2009 21:21:41 Mike Tancsa wrote: Not sure if this is a faulty device or just a quirk as to how it works. But on cold boot (after a power cycle) it does not work. But if I do a soft reboot, it attaches no problem Here is the diff on the boot verbose on the the cold boot vs warm boot # diff -u bad.txt good.txt | egrep ^\+|^\- -usb_alloc_device:1586: set address 2 failed (USB_ERR_IOERROR, ignored) -usb_alloc_device:1624: getting device descriptor at addr 2 failed, USB_ERR_IOERROR! -usbd_req_re_enumerate:1539: addr=2, set address failed! (USB_ERR_IOERROR, ignored) -usbd_req_re_enumerate:1553: getting device descriptor at addr 2 failed, USB_ERR_IOERROR! -usbd_req_re_enumerate:1539: addr=2, set address failed! (USB_ERR_IOERROR, ignored) -usbd_req_re_enumerate:1553: getting device descriptor at addr 2 failed, USB_ERR_IOERROR! -ugen0.2: (null) at usbus0 (disconnected) -uhub_reattach_port:435: could not allocate new device! -ct_to_ts([2000-01-01 00:01:51]) = 946684911.0 -ct_to_ts([2000-01-01 00:01:51]) = 946684911.0 +ugen0.2: HP at usbus0 +u3g0: Data Interface on usbus0 +u3g0: Found 3 ports. +ct_to_ts([2000-01-01 00:06:04]) = 946685164.0 +ct_to_ts([2000-01-01 00:06:04]) = 946685164.0 Is there something I can do to deal with this specific device differently in the driver ? Its 8.0-BETA3 FreeBSD 8.0-BETA3 #2: Wed Sep 2 using the u3g driver. Does this device have a button to enable it? Does it help pressing that button? One idea is to not power down the port which obviously gives the device power on failures. Hi, Its a mini-pciExpress card that is designed to be inside a laptop, or in this case embedded device. So no buttons. The other similar devices I have dont exhibit this behaviour so it seems to be quirky to this particular model. Here is the card and board http://eastar4.com/ebay/SierraMC8775-2.jpg http://www.pcengines.ch/alix6b2.htm ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
USB_ERR_IOERROR on cold boot, not warm boot
= 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0005 bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x bRefresh = 0x bSynchAddress = 0x alix# ati3 Manufacturer: Sierra Wireless, Inc. Model: MC8775 Revision: H1_1_9_3MCAP C:/WS/FW/H1_1_9_3MCAP/MSM6280/SRC 2007/12/12 11:49:21 IMEI: IMEI SV: 10 FSN: 3GPP Release 5 +GCAP: +CGSM,+DS,+ES ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: usb/138172: Additional dev id for u3g (Option mini PCIe)
The following reply was made to PR usb/138172; it has been noted by GNATS.
From: Mike Tancsa m...@sentex.net
To: bug-follo...@freebsd.org, m...@sentex.ca
Cc:
Subject: Re: usb/138172: Additional dev id for u3g (Option mini PCIe)
Date: Tue, 01 Sep 2009 10:52:00 -0400
Here is an additional device ID for an Option 380 PCIe. The U760 is
also in the diff below (http://www.freebsd.org/cgi/query-pr.cgi?pr=138138)
---Mike
--- /tmp/usbdevs2009-09-01 10:36:23.0 -0400
+++ usbdevs 2009-09-01 10:25:53.0 -0400
@@ -1917,6 +1917,8 @@
product OPTION GTICON322 0xd033 GlobeTrotter Icon322 storage
product OPTION GTMAX36 0x6701 GlobeTrotter Max 3.6 Modem
product OPTION GTMAXHSUPA 0x7001 GlobeTrotter HSUPA
+product OPTION GTMAXHSUPAE 0x6901 GlobeTrotter HSUPA PCIe
+product OPTION GTMAX380HSUPAE 0x7211 GlobeTrotter 380HSUPA PCIe
/* OQO */
product OQO WIFI01 0x0002 model 01 WiFi interface
--- /tmp/u3g-orig.c 2009-09-01 10:37:15.0 -0400
+++ u3g.c 2009-09-01 10:38:24.0 -0400
@@ -16,7 +16,7 @@
* ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
* OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
*
- * $FreeBSD: src/sys/dev/usb/u3g.c,v 1.24.2.5 2009/08/13 07:19:43
n_hibma Exp $
+ * $FreeBSD: src/sys/dev/usb/u3g.c,v 1.24.2.4 2009/07/09 15:29:26
n_hibma Exp $
*/
/*
@@ -134,6 +134,8 @@
{{ USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GPLUS
},U3GSP_UMTS, U3GINIT_NONE },
{{ USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAX36
}, U3GSP_HSDPA,U3GINIT_NONE },
{{ USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAXHSUPA
}, U3GSP_HSDPA,U3GINIT_NONE },
+ {{ USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAXHSUPAE
}, U3GSP_HSDPA,U3GINIT_NONE },
+ {{ USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GTMAX380HSUPAE
}, U3GSP_HSDPA,U3GINIT_NONE },
{{ USB_VENDOR_OPTION, USB_PRODUCT_OPTION_VODAFONEMC3G
},U3GSP_UMTS, U3GINIT_NONE },
/* OEM: Qualcomm, Inc. */
{{ USB_VENDOR_QUALCOMMINC, USB_PRODUCT_QUALCOMMINC_ZTE_STOR
}, U3GSP_CDMA, U3GINIT_ZTESTOR },
@@ -144,6 +146,7 @@
{{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E220
},U3GSP_HSPA, U3GINIT_HUAWEI },
/* OEM: Novatel */
{{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_CDMA_MODEM
},U3GSP_CDMA, U3GINIT_EJECT },
+ {{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U760
}, U3GSP_CDMA, U3GINIT_EJECT },
{{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_ES620
}, U3GSP_UMTS, U3GINIT_EJECT },// XXX
{{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_MC950D
},U3GSP_HSUPA,U3GINIT_EJECT },
{{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U720
}, U3GSP_UMTS, U3GINIT_EJECT },// XXX
# cu -l /dev/cuaU0.2
Connected
ati
Manufacturer: Option N.V.
Model: GTM380
Revision: 2.12.0Hd (Date: May 27 2008, Time: 11:19:10)
OK
ucom0: Option N.V. Globetrotter HSUPA Modem, class 255/255, rev
1.10/0.00, addr 2 on uhub0
ucom0: Interface 0 of 3, not in use
ucom0: Endpoint 0 of 3
ucom0: Endpoint 1 of 3
ucom0: port=0 iface=0 in=0x83 out=0x3
ucom0: Endpoint 2 of 3
ucom0: Interface 1 of 3, not in use
ucom0: Endpoint 0 of 2
ucom0: Endpoint 1 of 2
ucom0: port=1 iface=1 in=0x84 out=0x4
ucom0: Interface 2 of 3, not in use
ucom0: Endpoint 0 of 3
ucom0: Endpoint 1 of 3
ucom0: Endpoint 2 of 3
ucom0: port=2 iface=2 in=0x82 out=0x2
ucom0: configured 3 serial ports (U0.%d)
# usbdevs -v
Controller /dev/usb0:
addr 1: full speed, self powered, config 1, OHCI root hub(0x),
AMD(0x), rev 1.00
port 1 powered
port 2 addr 2: full speed, power 500 mA, config 1, Globetrotter
HSUPA Modem(0x7211), Option N.V.(0x0af0), rev 0.00
port 3 powered
port 4 powered
Controller /dev/usb1:
addr 1: high speed, self powered, config 1, EHCI root hub(0x),
AMD(0x), rev 1.00
port 1 powered
port 2 powered
port 3 powered
port 4 powered
The only odd quirk of this one is that cuaU0.0, cuaU0.1 do not work.
Everything needs to be done through .2 ?
---Mike
Mike Tancsa, tel +1 519 651 3400
Sentex Communications,m...@sentex.net
Providing Internet since 1994www.sentex.net
Cambridge, Ontario Canada www.sentex.net/mike
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: usb/138172: Additional dev id for u3g (Option mini PCIe)
At 11:55 AM 9/1/2009, Hans Petter Selasky wrote: On Tuesday 01 September 2009 17:40:07 Mike Tancsa wrote: Does your patch apply to 8+9-current ? Here are the diffs for 8+9-current I tested the Option mini-pci-express units. I dont have the novatel handy right now, but it should work --- usbdevs.orig2009-09-01 15:39:55.0 -0400 +++ usbdevs 2009-09-01 15:40:32.0 -0400 @@ -1930,6 +1930,8 @@ product OPTION GTMAX36 0x6701 GlobeTrotter Max 3.6 Modem product OPTION GTHSDPA 0x6971 GlobeTrotter HSDPA product OPTION GTMAXHSUPA 0x7001 GlobeTrotter HSUPA +product OPTION GTMAXHSUPAE 0x6901 GlobeTrotter HSUPA PCIe +product OPTION GTMAX380HSUPAE 0x7211 GlobeTrotter 380HSUPA PCIe /* OQO */ product OQO WIFI01 0x0002 model 01 WiFi interface --- u3g.c.prev 2009-08-13 08:44:26.0 -0400 +++ u3g.c 2009-09-01 16:16:45.0 -0400 @@ -180,6 +180,8 @@ U3G_DEV(OPTION, GTMAX36, 0), U3G_DEV(OPTION, GTHSDPA, 0), U3G_DEV(OPTION, GTMAXHSUPA, 0), + U3G_DEV(OPTION, GTMAXHSUPAE, 0), + U3G_DEV(OPTION, GTMAX380HSUPAE, 0), U3G_DEV(OPTION, VODAFONEMC3G, 0), /* OEM: Qualcomm, Inc. */ U3G_DEV(QUALCOMMINC, ZTE_STOR, U3GFL_SCSI_EJECT), @@ -204,6 +206,7 @@ U3G_DEV(NOVATEL, X950D, 0), U3G_DEV(NOVATEL, XU870, 0), U3G_DEV(NOVATEL, ZEROCD, U3GFL_SCSI_EJECT), + U3G_DEV(NOVATEL, U760, U3GFL_SCSI_EJECT), U3G_DEV(DELL, U740, 0), /* OEM: Merlin */ U3G_DEV(MERLIN, V620, 0), alix# usbconfig show_ifdrv ugen0.1: OHCI root HUB AMD at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen0.1.0: uhub0: AMD OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 ugen1.1: EHCI root HUB AMD at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen1.1.0: uhub1: AMD EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1 ugen0.2: Globetrotter HSUPA Modem Option N.V. at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen0.2.0: u3g0: Data Interface alix# ugen0.2: Globetrotter HSUPA Modem Option N.V. at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x00ff bDeviceSubClass = 0x00ff bDeviceProtocol = 0x00ff bMaxPacketSize0 = 0x0040 idVendor = 0x0af0 idProduct = 0x7211 bcdDevice = 0x iManufacturer = 0x0001 Option N.V. iProduct = 0x0002 Globetrotter HSUPA Modem iSerialNumber = 0x0004 Serial Number bNumConfigurations = 0x0001 ugen0.2: Globetrotter HSUPA Modem Option N.V. at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x005f bNumInterfaces = 0x0003 bConfigurationValue = 0x0001 iConfiguration = 0x no string bmAttributes = 0x00a0 bMaxPower = 0x00fa Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x0003 bInterfaceClass = 0x00ff bInterfaceSubClass = 0x00ff bInterfaceProtocol = 0x00ff iInterface = 0x0003 Data Interface Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0083 bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0003 bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x bRefresh = 0x bSynchAddress = 0x Endpoint 2 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0085 bmAttributes = 0x0003 wMaxPacketSize = 0x0010 bInterval = 0x0080 bRefresh = 0x bSynchAddress = 0x Additional Descriptor bLength = 0x03 bDescriptorType = 0x24 bDescriptorSubType = 0x03 RAW dump: 0x00 | 0x03, 0x24, 0x03 Interface 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x bNumEndpoints = 0x0002 bInterfaceClass = 0x00ff bInterfaceSubClass = 0x00ff bInterfaceProtocol = 0x00ff iInterface = 0x0003 Data Interface Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0084 bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0004 bmAttributes = 0x0002 wMaxPacketSize = 0x0040 bInterval = 0x bRefresh = 0x bSynchAddress = 0x Interface 2 bLength = 0x0009 bDescriptorType = 0x0004
Re: usb/138172: Additional dev id for u3g (Option mini PCIe)
At 04:48 PM 9/1/2009, Hans Petter Selasky wrote: On Tuesday 01 September 2009 22:40:25 Mike Tancsa wrote: usb/138172 Here is the commit: http://perforce.freebsd.org/chv.cgi?CH=168061 Thanks! Any chance it will hit the 2 trees ? (the RELENG_7 version) as well as whats in perforce to RELENG_8 and HEAD ? --HPS Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Unrecognized Atheros USB stick ?
I was sent a sample of this USB 802.11n usb wireless nic http://www.tplink.com/products/product_des.asp?id=140 Is it supported by any of the drivers ? Nothing seems to attach to it 0(ich10)# usbconfig -u 0 -a 2 dump_device_desc ugen0.2: USB2.0 WLAN ATHER at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x00ff bDeviceSubClass = 0x00ff bDeviceProtocol = 0x00ff bMaxPacketSize0 = 0x0040 idVendor = 0x0cf3 idProduct = 0x9170 bcdDevice = 0x0106 iManufacturer = 0x0010 ATHER iProduct = 0x0020 USB2.0 WLAN iSerialNumber = 0x0030 12345 bNumConfigurations = 0x0001 0(ich10)# ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: USB update
At 02:19 AM 8/24/2009, Hans Petter Selasky wrote: Hi, The fixes for the last two weeks of reported USB issues has now been committed into freebsd-8-current. FYI, this bug http://lists.freebsd.org/pipermail/freebsd-current/2009-May/006710.html still appears to be there with RELENG_8. Is there anything in the above patch set that might address it ? ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Huawei E169 USB 3G Modem not detected as modem in 7.2
to query device size failed: NOT READY, Medium not present Aug 23 13:58:40 nicknack kernel: (cd0:umass-sim1:1:0:0): error 6 Aug 23 13:58:40 nicknack kernel: (cd0:umass-sim1:1:0:0): Unretryable Error Aug 23 13:58:40 nicknack kernel: (cd0:umass-sim1:1:0:0): error 6 Aug 23 13:58:40 nicknack kernel: (cd0:umass-sim1:1:0:0): Unretryable Error Aug 23 13:58:40 nicknack kernel: (cd0:umass-sim1:1:0:0): error 6 Aug 23 13:58:40 nicknack kernel: (cd0:umass-sim1:1:0:0): Unretryable Error Aug 23 13:58:40 nicknack kernel: (cd0:umass-sim1:1:0:0): error 6 Aug 23 13:58:40 nicknack kernel: (cd0:umass-sim1:1:0:0): Unretryable Error Aug 23 13:58:40 nicknack kernel: (cd0:umass-sim1:1:0:0): error 6 Aug 23 13:58:40 nicknack kernel: (cd0:umass-sim1:1:0:0): Unretryable Error Aug 23 13:58:40 nicknack kernel: (cd0:umass-sim1:1:0:0): error 6 Aug 23 13:58:40 nicknack kernel: (cd0:umass-sim1:1:0:0): Unretryable Error Aug 23 13:58:40 nicknack kernel: GEOM: new disk da1 Aug 23 13:58:40 nicknack kernel: (da1:umass-sim2:2:0:0): error 6 Aug 23 13:58:40 nicknack kernel: (da1:umass-sim2:2:0:0): Unretryable Error Aug 23 13:58:40 nicknack kernel: Opened disk da1 - 6 Aug 23 13:58:40 nicknack kernel: (da1:umass-sim2:2:0:0): error 6 Aug 23 13:58:40 nicknack kernel: (da1:umass-sim2:2:0:0): Unretryable Error Aug 23 13:58:40 nicknack kernel: Opened disk da1 - 6 Aug 23 13:58:40 nicknack kernel: (da1:umass-sim2:2:0:0): error 6 Aug 23 13:58:40 nicknack kernel: (da1:umass-sim2:2:0:0): Unretryable Error Aug 23 13:58:40 nicknack kernel: Opened disk da1 - 6 Aug 23 13:58:40 nicknack kernel: (da1:umass-sim2:2:0:0): error 6 Aug 23 13:58:40 nicknack kernel: (da1:umass-sim2:2:0:0): Unretryable Error Aug 23 13:58:40 nicknack kernel: Opened disk da1 - 6 Aug 23 13:58:40 nicknack kernel: (da1:umass-sim2:2:0:0): error 6 Aug 23 13:58:40 nicknack kernel: (da1:umass-sim2:2:0:0): Unretryable Error Aug 23 13:58:40 nicknack kernel: Opened disk da1 - 6 ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Verizon Novatel U760 (u3g)
Some notes for the archives in case anyone else gets one of these
evdo USB sticks with FreeBSD (in this case, RELENG_7)
I had to make this small addition to u3g.c in order to get the device
to work. Note, you still have to do a camcontrol eject pass0
--- u3g.c.orig 2009-08-11 09:25:47.0 -0400
+++ u3g.c 2009-08-11 09:26:37.0 -0400
@@ -144,6 +144,7 @@
{{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E220
},U3GSP_HSPA, U3GINIT_HUAWEI },
/* OEM: Novatel */
{{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_CDMA_MODEM
},U3GSP_CDMA, U3GINIT_EJECT },
+ {{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U760
}, U3GSP_CDMA, U3GINIT_EJECT },
{{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_ES620
}, U3GSP_UMTS, U3GINIT_EJECT },// XXX
{{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_MC950D
},U3GSP_HSUPA,U3GINIT_EJECT },
{{ USB_VENDOR_NOVATEL, USB_PRODUCT_NOVATEL_U720
}, U3GSP_UMTS, U3GINIT_EJECT },// XXX
before and after camcontrol eject pass0
full speed, power 500 mA, config 1, Novatel Wireless CDMA(0x6000),
Novatel Wireless Inc.(0x1410), rev 0.00
full speed, power 500 mA, config 1, Novatel Wireless CDMA(0x5030),
Novatel Wireless Inc.(0x1410), rev 0.00
Also, not sure if its an activation thing or not, but we had to run
the device once on a windows machine, otherwise we would get 0.0.0.0
as the IP address assigned. It might also be peculiar to Verizon,
but we also needed to add
deny chap
to our ppp.conf stanza.
evdo2:
set device /dev/cuaU0.0
set speed 115200
#set dial ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \
# \\ AT OK-AT-OK ATZ OK AT\$QCMDR=3 OK \\dATDT\\T
TIMEOUT 50 CONNECT
set dial ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \
\\ AT OK-AT-OK ATZ OK \\dATDT\\T TIMEOUT 50 CONNECT
set phone #777
# The authname and authkey are meaningless, but you need to have them set.
# Verizon's servers don't seem to care what you auth as.
#set authname notnee...@vzw3g.com
#set authkey vzw
disable vjcomp
disable acfcomp
disable chap
disable pap
deny chap
disable deflate
disable deflate24
disable pred1
disable protocomp
disable mppe
disable ipv6cp
disable lqr
disable echo
set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0
add default HISADDR# Add a (sticky) default route
disable dns
---Mike
Mike Tancsa, tel +1 519 651 3400
Sentex Communications,m...@sentex.net
Providing Internet since 1994www.sentex.net
Cambridge, Ontario Canada www.sentex.net/mike
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: ZTE MF636 USB u3g modem
At 03:48 AM 5/7/2009, Nick Hibma wrote: u3g0: ZTE, Incorporated ZTE CDMA Technologies MSM, class 0/0, rev 2.00/0.00, addr 2 on uhub1 u3g0: changing CMOTECH modem to modem mode u3g0: sent command to change to modem mode u3g0: failed to read back CSW: 13 u3g0: at uhub1 port 2 (addr 2) disconnected u3g0: detached ucom0: ZTE, Incorporated ZTE CDMA Technologies MSM, class 0/0, rev 2.00/0.00, addr 2 on uhub1 ucom0: port=0 iface=3 in=0x85 out=0x4 ucom0: configured 1 serial ports (U0.%d) This is the real port. Could you dump the descriptors after unloading the driver and loading ugen? Hi, I think this is the info you want ? If not, let me know. Thanks! I also did a usb capture of all the traffic in windows from the point of the device being attached and going online. 0[i7]# usbconfig -u 3 -a 5 dump_device_desc ugen3.5: ZTE CDMA Technologies MSM ZTE, Incorporated at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x19d2 idProduct = 0x0031 bcdDevice = 0x iManufacturer = 0x0002 ZTE, Incorporated iProduct = 0x0001 ZTE CDMA Technologies MSM iSerialNumber = 0x0003 1234567890ABCDEF bNumConfigurations = 0x0001 0[i7]# usbconfig -u 3 -a 5 dump_all_config_desc ugen3.5: ZTE CDMA Technologies MSM ZTE, Incorporated at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0100 bNumInterfaces = 0x0004 bConfigurationValue = 0x0001 iConfiguration = 0x no string bmAttributes = 0x00a0 bMaxPower = 0x00fa Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x bInterfaceClass = 0x00ff bInterfaceSubClass = 0x00ff bInterfaceProtocol = 0x00ff iInterface = 0x no string Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x00 RAW dump: 0x00 | 0x05, 0x24, 0x00, 0x10, 0x01 Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x15 RAW dump: 0x00 | 0x05, 0x24, 0x15, 0x00, 0x01 Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x06 RAW dump: 0x00 | 0x05, 0x24, 0x06, 0x00, 0x00 Additional Descriptor bLength = 0x15 bDescriptorType = 0x24 bDescriptorSubType = 0x12 RAW dump: 0x00 | 0x15, 0x24, 0x12, 0x20, 0x01, 0x98, 0xb0, 0x6a, 0x08 | 0x49, 0xb0, 0x9e, 0x48, 0x96, 0x94, 0x46, 0xd9, 0x10 | 0x9a, 0x28, 0xca, 0x4e, 0x5d Additional Descriptor bLength = 0x06 bDescriptorType = 0x24 bDescriptorSubType = 0x13 RAW dump: 0x00 | 0x06, 0x24, 0x13, 0x00, 0x01, 0x10 Interface 0 Alt 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x0001 bNumEndpoints = 0x0002 bInterfaceClass = 0x00ff bInterfaceSubClass = 0x00ff bInterfaceProtocol = 0x00ff iInterface = 0x no string Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x0020 bRefresh = 0x bSynchAddress = 0x Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0001 bmAttributes = 0x0002 wMaxPacketSize = 0x0200 bInterval = 0x0020 bRefresh = 0x bSynchAddress = 0x Interface 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x bNumEndpoints = 0x bInterfaceClass = 0x00ff bInterfaceSubClass = 0x00ff bInterfaceProtocol = 0x00ff iInterface = 0x no string Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x00 RAW dump: 0x00 | 0x05, 0x24, 0x00, 0x10, 0x01 Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x15 RAW dump: 0x00 | 0x05, 0x24, 0x15, 0x00, 0x01 Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x06 RAW dump: 0x00 | 0x05, 0x24, 0x06, 0x01, 0x01 Additional Descriptor bLength = 0x15 bDescriptorType = 0x24 bDescriptorSubType = 0x12 RAW dump: 0x00 | 0x15, 0x24, 0x12, 0x20, 0x01, 0x98, 0xb0, 0x6a, 0x08 | 0x49, 0xb0, 0x9e, 0x48, 0x96, 0x94, 0x46, 0xd9, 0x10 | 0x9a, 0x28, 0xca, 0x4e, 0x5d
Re: ZTE MF636 USB u3g modem
At 10:01 AM 5/7/2009, Mike Tancsa wrote: This is the real port. Could you dump the descriptors after unloading the driver and loading ugen? I decided to give it a spin on HEAD, but not sure if the recent changes to u3g in HEAD changed the behaviour, or its an issue with me fiddling with the driver. Using http://www.draisberghof.de/usb_modeswitch/usb_modeswitch-0.9.7.tar.bz2 I am able to make the device appear, but as /dev/cuaU0 and not /dev/cuaU0.0 u3g0: ZTE, Incorporated ZTE CDMA Technologies MSM, class 0/0, rev 2.00/0.00, addr 2 on usbus3 umass0: ZTE, Incorporated ZTE CDMA Technologies MSM, class 0/0, rev 2.00/0.00, addr 2 on usbus3 umass0: SCSI over Bulk-Only; quirks = 0x Root mount waiting for: usbus3 umass0:0:0:-1: Attached to scbus0 Root mount waiting for: usbus3 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 (probe0:umass-sim0:0:0:0): Medium not present (probe0:umass-sim0:0:0:0): Unretryable error da0 at umass-sim0 bus 0 target 0 lun 0 da0: ZTE MMC Storage 322 Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not presen da0 is the microSD drive I think the port that attaches is actually the monitor port as there is a stead stream of +ZUSIMR:2 +ZUSIMR:2 +ZUSIMR:2 +ZUSIMR:2 +ZUSIMR:2 +ZUSIMR:2 +ZUSIMR:2 +ZUSIMR:2 In windows, it provides 2 serial ports The following changes, along with using usb_modeswitch seems to get things working, however, ppp sometimes gets confused with the ZUSIMR:2 stuff constantly being spewed out. 0[i7]# diff -u usbdevs usbdevs.zte --- usbdevs 2009-04-21 01:06:31.0 -0400 +++ usbdevs.zte 2009-05-07 23:10:11.0 -0400 @@ -2035,6 +2035,7 @@ product QUALCOMM2 RWT_FCT 0x3100 RWT FCT-CDMA 2000 1xRTT modem product QUALCOMM2 CDMA_MSM 0x3196 CDMA Technologies MSM modem product QUALCOMMINC CDMA_MSM 0x0001 CDMA Technologies MSM modem +product QUALCOMMINC CDMA_MSM6360x0031 MF636 Technologies MSM modem product QUALCOMMINC ZTE_STOR 0x2000 USB ZTE Storage product QUALCOMMINC AC8700 0xfffe CDMA 1xEVDO USB modem 1[i7]# 1[i7]# diff -u u3g.c u3g.c.mdt --- u3g.c 2009-05-07 13:05:03.0 -0400 +++ u3g.c.mdt 2009-05-07 23:09:59.0 -0400 @@ -168,6 +168,7 @@ /* OEM: Qualcomm, Inc. */ U3G_DEV(QUALCOMMINC, ZTE_STOR, U3GFL_SCSI_EJECT), U3G_DEV(QUALCOMMINC, CDMA_MSM, U3GFL_SCSI_EJECT), + U3G_DEV(QUALCOMMINC, CDMA_MSM636, U3GFL_SCSI_EJECT), /* OEM: Huawei */ U3G_DEV(HUAWEI, MOBILE, U3GFL_HUAWEI_INIT), U3G_DEV(HUAWEI, E220, U3GFL_HUAWEI_INIT), 1[i7]# dmesg shows ugen3.2: ZTE, Incorporated at usbus3 u3g0: ZTE, Incorporated ZTE CDMA Technologies MSM, class 0/0, rev 2.00/0.00, addr 2 on usbus3 umass0: ZTE, Incorporated ZTE CDMA Technologies MSM, class 0/0, rev 2.00/0.00, addr 2 on usbus3 umass0: SCSI over Bulk-Only; quirks = 0x Root mount waiting for: usbus3 umass0:0:0:-1: Attached to scbus0 Root mount waiting for: usbus3 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 (probe0:umass-sim0:0:0:0): Medium not present (probe0:umass-sim0:0:0:0): Unretryable error da0 at umass-sim0 bus 0 target 0 lun 0 da0: ZTE MMC Storage 322 Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present Hi, I think this is the info you want ? If not, let me know. Thanks! I also did a usb capture of all the traffic in windows from the point of the device being attached and going online. 0[i7]# usbconfig -u 3 -a 5 dump_device_desc ugen3.5: ZTE CDMA Technologies MSM ZTE, Incorporated at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x19d2 idProduct = 0x0031 bcdDevice = 0x iManufacturer = 0x0002 ZTE, Incorporated iProduct = 0x0001 ZTE CDMA Technologies MSM iSerialNumber = 0x0003 1234567890ABCDEF bNumConfigurations = 0x0001 0[i7]# usbconfig -u 3 -a 5 dump_all_config_desc ugen3.5: ZTE CDMA Technologies MSM ZTE, Incorporated at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0100 bNumInterfaces = 0x0004 bConfigurationValue = 0x0001 iConfiguration = 0x no string bmAttributes = 0x00a0 bMaxPower = 0x00fa Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x
ZTE MF636 USB u3g modem
Has anyone had any luck getting this modem to work under FreeBSD ? I have been trying to modify the driver to get it to recognize and send the unit into modem mode, but no luck. I even tried setting the unit into permanent modem mode first from Windows as referenced in http://www.matt-barrett.com/?p=5 but no luck yet usbdevs shows it as port 2 addr 2: high speed, power 500 mA, config 1, ZTE CDMA Technologies MSM(0x2000), ZTE, Incorporated(0x19d2), rev 0.00 u3g0: sending CD eject command to change to modem mode u3g0: sent command to change to modem mode u3g0: read back CSW ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
configure error with openct and new libusb
Hi, While trying to build openct on a new box, I got the following errors. I was able to build this just a few weeks ago, but all of a sudden configure cant find libusb ? checking for an ANSI C-conforming const... yes checking for uid_t in sys/types.h... yes checking for size_t... yes checking whether time.h and sys/time.h may both be included... yes checking for error_at_line... no checking whether lstat dereferences a symlink specified with a trailing slash... no checking whether stat accepts an empty string... no checking for vprintf... yes checking for _doprnt... no checking for gettimeofday... yes checking for daemon... yes checking for inline... inline checking for socket in -lsocket... no checking ltdl.h usability... yes checking ltdl.h presence... no configure: WARNING: ltdl.h: accepted by the compiler, rejected by the preprocessor! configure: WARNING: ltdl.h: proceeding with the compiler's result checking for ltdl.h... yes checking struct sockaddr_storage::ss_family... ok checking for poll in -lpoll... no checking for LIBUSB... gnome-config: not found no configure: error: Cannot detect libusb === Script configure failed unexpectedly. Please report the problem to a...@freebsd.org [maintainer] and attach the /usr/ports/security/openct/work/openct-0.6.15/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 Stop in /usr/ports/security/openct. *** Error code 1 Stop in /usr/ports/security/openct. in the log I see configure:23074: checking for LIBUSB configure:23082: $PKG_CONFIG --exists --print-errors libusb gnome-config: not found Package libusb was not found in the pkg-config search path. Perhaps you should add the directory containing `libusb.pc' to the PKG_CONFIG_PATH environment variable No package 'libusb' found configure:23085: $? = 1 configure:23100: $PKG_CONFIG --exists --print-errors libusb gnome-config: not found Package libusb was not found in the pkg-config search path. Perhaps you should add the directory containing `libusb.pc' to the PKG_CONFIG_PATH environment variable No package 'libusb' found configure:23103: $? = 1 No package 'libusb' found configure:23131: result: no configure:23133: error: Cannot detect libusb Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: configure error with openct and new libusb
At 04:38 PM 4/9/2009, Mike Tancsa wrote:
Hi,
While trying to build openct on a new box, I got the
following errors. I was able to build this just a few weeks ago,
but all of a sudden configure cant find libusb ?
Just to followup on my own post, I was able to compile and get it to
work by removing the test in configure and added -lusb to the main build.
--- configure.orig 2008-07-31 09:03:41.0 -0400
+++ configure 2009-04-09 16:58:18.0 -0400
@@ -4740,8 +4740,8 @@
;;
esac
-usrlibdir=/usr/lib${libdir##*/lib}
-usrsbindir=/usr/sbin${libdir##*/sbin}
+usrlibdir=`eval eval eval eval eval echo ${libdir} | sed
s#NONE#${prefix}# | sed s#NONE#${ac_default_prefix}#`
+usrsbindir=`eval eval eval eval eval echo ${sbindir} | sed
s#NONE#${prefix}# | sed s#NONE#${ac_default_prefix}#`
full_sysconfdir=`eval eval eval eval eval echo ${sysconfdir} |
sed s#NONE#${prefix}# | sed s#NONE#${ac_default_prefix}#`
full_localstatedir=`eval eval eval eval eval echo
${localstatedir} | sed s#NONE#${prefix}# | sed
s#NONE#${ac_default_prefix}#`
@@ -23074,44 +23074,6 @@
{ echo $as_me:$LINENO: checking for LIBUSB 5
echo $ECHO_N checking for LIBUSB... $ECHO_C 6; }
-if test -n $PKG_CONFIG; then
-if test -n $LIBUSB_CFLAGS; then
-pkg_cv_LIBUSB_CFLAGS=$LIBUSB_CFLAGS
-else
-if test -n $PKG_CONFIG \
-{ (echo $as_me:$LINENO: \$PKG_CONFIG --exists --print-errors
\libusb\) 5
- ($PKG_CONFIG --exists --print-errors libusb) 25
- ac_status=$?
- echo $as_me:$LINENO: \$? = $ac_status 5
- (exit $ac_status); }; then
- pkg_cv_LIBUSB_CFLAGS=`$PKG_CONFIG --cflags libusb 2/dev/null`
-else
- pkg_failed=yes
-fi
-fi
-else
- pkg_failed=untried
-fi
-if test -n $PKG_CONFIG; then
-if test -n $LIBUSB_LIBS; then
-pkg_cv_LIBUSB_LIBS=$LIBUSB_LIBS
-else
-if test -n $PKG_CONFIG \
-{ (echo $as_me:$LINENO: \$PKG_CONFIG --exists --print-errors
\libusb\) 5
- ($PKG_CONFIG --exists --print-errors libusb) 25
- ac_status=$?
- echo $as_me:$LINENO: \$? = $ac_status 5
- (exit $ac_status); }; then
- pkg_cv_LIBUSB_LIBS=`$PKG_CONFIG --libs libusb 2/dev/null`
-else
- pkg_failed=yes
-fi
-fi
-else
- pkg_failed=untried
-fi
-
-
if test $pkg_failed = yes; then
@@ -26369,7 +26331,7 @@
CFLAGS=${CFLAGS} -Wall -Wextra
fi
-pkgconfigdir=\$(libdir)/pkgconfig
+pkgconfigdir=\$(prefix)/libdata/pkgconfig
openctincludedir=\$(includedir)/openct
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: UGEN stall problems
At 08:49 AM 5/6/2008, David Imhoff wrote: Hi, I'm trying to get an Alladin eToken pro (4.2b) and a Kobil mIdentity light smartcard token/reader to work with OpenCT under FreeBSD, but i ran into some problems. Both devices work perfectly when connected through an USB 2.0 hub to the machine, but when connected directly to the root hub they only work partially(eToken) or not at all(mIdentity). Hi, I know this is an 'old' thread, but I came across the same problem and thought I would followup for the archives. Andrew Thompson has fixed the issue with a patch to OpenCT thats in the ports. You need to use the new USB stack in 8.x, but it works great with the 4.2b keys, including the OTP combo versions of the eTokens as well. 0[i7]# cardos-info Running cardos-tool --info [cardos-tool] reader-pcsc.c:996:pcsc_detect_readers: returning with: No readers found Using reader with a card: Aladdin eToken PRO 64k 3b:f2:18:00:02:c1:0a:31:fe:58:c8:09:75 Info : CardOS V4.2B (C) Siemens AG 1994-2005 Chip type: 124 Serial number: 26 04 f6 18 29 0c Full prom dump: 33 66 00 22 9A 9A 9A 9A 7C FF 26 04 F6 18 29 0C 3f.|). 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 OS Version: 200.9 (that's CardOS M4.2B) Current life cycle: 32 (administration) Security Status of current DF: Free memory : 1024 ATR Status: 0x0 ROM-ATR Packages installed: E1 09 40 04 64 03 C8 09 8F 01 01 @.d.. Ram size: 4, Eeprom size: 64, cpu type: 66, chip config: 63 Free eeprom memory: 38404 System keys: PackageLoadKey (version 0xfe, retries 10) System keys: StartKey (version 0xff, retries 10) Path to current DF: 0[i7]# pkcs15-init -E -C --no-so-pin [pkcs15-init] reader-pcsc.c:996:pcsc_detect_readers: returning with: No readers found Using reader with a card: Aladdin eToken PRO 64k 0[i7]# ugen0.3: Token 2.25.1.3 2.6.189 Aladdin Knowledge Systems Ltd. at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0040 idVendor = 0x0529 idProduct = 0x0700 bcdDevice = 0x0100 iManufacturer = 0x0001 Aladdin Knowledge Systems Ltd. iProduct = 0x0002 Token 2.25.1.3 2.6.189 iSerialNumber = 0x no string bNumConfigurations = 0x0001 ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: u3g panic
At 05:50 AM 4/1/2009, Nick Hibma wrote: Mike, and others, We are working on this panic at the moment and there will be a driver out for inclusion in 7.2 (hopefully). It seems to (almost) make ZTE MF626 work as well (mode switch does not work reliably yet). According to Mike Tancsa this driver also makes his Novatel device work without having to manually switch the device. I'd appreciate it if poeple could gives this driver a try to see whether it works for them too. http://people.freebsd.org/~n_hibma/u3g.html I am using it as we speak to submit this message and upload the driver sources, change the HTML text on that page. Its working much better now, but I still get the occasional IOERROR ucom1: Novatel Wireless Novatel Wireless HSUPA Modem, class 0/0, rev 1.10/0.00, addr 3 on uhub0 ucom1: port=0 iface=0 in=0x82 out=0x2 ucom1: port=1 iface=1 in=0x84 out=0x4 ucom1: configured 2 serial ports (U1.%d) ucom1: at uhub0 port 3 (addr 3) disconnected ucom1: ucomreadcb: IOERROR Still 2 threads in cuaU1.0 Still 2 threads in cuaU1.0 Still 2 threads in cuaU1.0 Still 2 threads in cuaU1.0 And then I have to reboot the box or pull the device to get it to work again. I am not sure if the USB stick is crashing or a driver issue ?Is there a way from userland to make the device re-attach in such cases ? We would like to deploy some of these remotely so ideally we would like to catch the error and deal with it programatically. ---Mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
u3g panic
Hi, I was trying the u3g driver in FreeBSD on RELENG_7. The previous version from the webpage seemed to work ok, but the one MFC'd causes a panic if I load the driver and attach the stick Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xc fault code = supervisor read, page not present instruction pointer = 0x20:0xc357d71f stack pointer = 0x28:0xc2fccbc0 frame pointer = 0x28:0xc2fccbf4 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 26 (irq19: uhci1) trap number = 12 panic: page fault cpuid = 0 Uptime: 2m39s Physical memory: 498 MB Dumping 42 MB: 27 11 (kgdb) bt #0 doadump () at pcpu.h:196 #1 0xc07198b7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc0719b89 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:574 #3 0xc09e495c in trap_fatal (frame=0xc2fccb80, eva=12) at /usr/src/sys/i386/i386/trap.c:939 #4 0xc09e4be0 in trap_pfault (frame=0xc2fccb80, usermode=0, eva=12) at /usr/src/sys/i386/i386/trap.c:852 #5 0xc09e558c in trap (frame=0xc2fccb80) at /usr/src/sys/i386/i386/trap.c:530 #6 0xc09c9c6b in calltrap () at /usr/src/sys/i386/i386/exception.s:159 #7 0xc357d71f in u3gstub_BBB_cb (xfer=0xc3578600, priv=0x0, err=USBD_NORMAL_COMPLETION) at /usr/src/sys/modules/u3g/../../dev/usb/u3g.c:475 #8 0xc06950d5 in usb_transfer_complete (xfer=0xc3578600) at /usr/src/sys/dev/usb/usbdi.c:979 #9 0xc06879bb in uhci_transfer_complete (xfer=0xc3578600) at /usr/src/sys/dev/usb/uhci.c:2109 #10 0xc0687b07 in uhci_idone (ii=Variable ii is not available. ) at /usr/src/sys/dev/usb/uhci.c:1449 #11 0xc068800d in uhci_softintr (v=0xc319a000) at /usr/src/sys/dev/usb/uhci.c:1324 #12 0xc0690c72 in usb_schedsoftintr (bus=0xc319a000) at /usr/src/sys/dev/usb/usb.c:844 #13 0xc0688ce3 in uhci_intr1 (sc=0xc319a000) at /usr/src/sys/dev/usb/uhci.c:1224 #14 0xc0688fad in uhci_intr (arg=0xc319a000) at /usr/src/sys/dev/usb/uhci.c:1139 #15 0xc06f781b in ithread_loop (arg=0xc31a4000) at /usr/src/sys/kern/kern_intr.c:1088 #16 0xc06f4369 in fork_exit (callout=0xc06f7660 ithread_loop, arg=0xc31a4000, frame=0xc2fccd38) at /usr/src/sys/kern/kern_fork.c:810 #17 0xc09c9ce0 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:264 (kgdb) On CURRENT, it shows and seems to work fine. Root mount waiting for: usbus1 ugen0.2: Novatel Wireless at usbus0 u3g0: Data Interface on usbus0 u3g0: Found 2 ports. 0[freebsd-current2]# usbconfig ugen0.1: OHCI root HUB nVidia at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: EHCI root HUB nVidia at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen0.2: Novatel Wireless HSUPA Modem Novatel Wireless at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen0.3: USB-Serial Controller Prolific Technology Inc. at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen0.4: Token 255.255.255.255 2.7.195 Aladdin Knowledge Systems Ltd. at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON 0[freebsd-current2]# cu -l /dev/cuaU0.0 Connected ati Manufacturer: Novatel Wireless Incorporated Model: Ovation MC950D Card Revision: 3.15.02.0-00 [2008-03-04 09:19:50] IMEI: 356846015465400 +GCAP: +CGSM,+DS,+ES OK Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: openct port and USB2
At 06:24 PM 3/20/2009, Andrew Thompson wrote: On Wed, Mar 18, 2009 at 08:04:48PM -0400, Mike Tancsa wrote: At 05:40 PM 3/18/2009, Andrew Thompson wrote: On Wed, Mar 18, 2009 at 04:15:46PM -0400, Mike Tancsa wrote: Hi, I was trying to see if OpenCT and OpenSC work under the new USB regime, but openCT doesnt compile now. Are there any tricks to get it to compile and or work ? Can you try this patch. http://people.freebsd.org/~thompsa/openct.diff Thanks! It does build now. However, not all of the bits seem to be working just yet It should be working as of r190185, please try again. It sure does!!! Thanks for fixing! ---Mike Andrew ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
openct port and USB2
Hi, I was trying to see if OpenCT and OpenSC work under the new USB regime, but openCT doesnt compile now. Are there any tricks to get it to compile and or work ? . . . mv -f .deps/libifd_la-sys-sunray.Tpo .deps/libifd_la-sys-sunray.Plo /bin/sh ../../libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include -I../../src/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -MT libifd_la-sys-solaris.lo -MD -MP -MF .deps/libifd_la-sys-solaris.Tpo -c -o libifd_la-sys-solaris.lo `test -f 'sys-solaris.c' || echo './'`sys-solaris.c cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include -I../../src/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -MT libifd_la-sys-solaris.lo -MD -MP -MF .deps/libifd_la-sys-solaris.Tpo -c sys-solaris.c -fPIC -DPIC -o .libs/libifd_la-sys-solaris.o cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include -I../../src/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -MT libifd_la-sys-solaris.lo -MD -MP -MF .deps/libifd_la-sys-solaris.Tpo -c sys-solaris.c -o libifd_la-sys-solaris.o /dev/null 21 mv -f .deps/libifd_la-sys-solaris.Tpo .deps/libifd_la-sys-solaris.Plo /bin/sh ../../libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include -I../../src/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -MT libifd_la-sys-bsd.lo -MD -MP -MF .deps/libifd_la-sys-bsd.Tpo -c -o libifd_la-sys-bsd.lo `test -f 'sys-bsd.c' || echo './'`sys-bsd.c cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/include -I../../src/include -I/usr/local/include -O2 -pipe -fno-strict-aliasing -MT libifd_la-sys-bsd.lo -MD -MP -MF .deps/libifd_la-sys-bsd.Tpo -c sys-bsd.c -fPIC -DPIC -o .libs/libifd_la-sys-bsd.o sys-bsd.c: In function 'ifd_sysdep_usb_bulk': sys-bsd.c:113: error: 'USB_SET_SHORT_XFER' undeclared (first use in this function) sys-bsd.c:113: error: (Each undeclared identifier is reported only once sys-bsd.c:113: error: for each function it appears in.) sys-bsd.c: In function 'ifd_sysdep_usb_control': sys-bsd.c:243: error: storage size of 'ctrl' isn't known sys-bsd.c:256: error: 'USBD_SHORT_XFER_OK' undeclared (first use in this function) sys-bsd.c:265: error: 'USB_SET_TIMEOUT' undeclared (first use in this function) sys-bsd.c:272: error: 'USB_DO_REQUEST' undeclared (first use in this function) sys-bsd.c: In function 'ifd_sysdep_usb_set_configuration': sys-bsd.c:291: error: 'USB_SET_CONFIG' undeclared (first use in this function) sys-bsd.c: In function 'ifd_sysdep_usb_set_interface': sys-bsd.c:312: error: 'USB_SET_ALTINTERFACE' undeclared (first use in this function) sys-bsd.c: In function 'ifd_scan_usb': sys-bsd.c:378: error: 'USB_MAX_DEVICES' undeclared (first use in this function) sys-bsd.c:379: error: storage size of 'device_info' isn't known sys-bsd.c:386: error: 'USB_DEVICEINFO' undeclared (first use in this function) gmake[3]: *** [libifd_la-sys-bsd.lo] Error 1 gmake[3]: Leaving directory `/usr/ports/security/openct/work/openct-0.6.15/src/ifd' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/security/openct/work/openct-0.6.15/src' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/security/openct/work/openct-0.6.15' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/security/openct. *** Error code 1 Stop in /usr/ports/security/openct. 1[i7]# ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: Novatel U727 not recognized
At 05:36 PM 2/26/2009, Kim Culhan wrote: u3g0: Data Interface on usbus2 u3g0: Found 4 ports. umass0: Novatel Wireless Inc. Novatel Wireless CDMA, class 0/0, rev 1.10/0.00, addr 2 on usbus2 umass0: SCSI over Bulk-Only; quirks = 0x umass0:1:0:-1: Attached to scbus1 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): NOT READY asc:3a,0 (probe0:umass-sim0:0:0:0): Medium not present (probe0:umass-sim0:0:0:0): Unretryable error da0 at umass-sim0 bus 0 target 0 lun 0 da0: Novatel MMC Storage 2.31 Removable Direct Access SCSI-2 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present If you do a camcontrol eject pass0 does /dev/cuaU* now show up ? I have a different Novatel unit where I have to do that to get it to work. umass0: Novatel Wireless Novatel Wireless HSUPA Modem, class 0/0, rev 1.10/0.00, addr 2 on uhub0 vr0: vr_stop: Rx shutdown error vr0: Using force reset command. umass0: at uhub0 port 1 (addr 2) disconnected umass0: detached ucom0: Novatel Wireless Novatel Wireless HSUPA Modem, class 0/0, rev 1.10/0.00, addr 2 on uhub0 ucom0: configured 2 serial ports (U0.%d) ---Mike -kim ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: eToken and USB2 (ugen issue?)
At 04:36 AM 2/7/2009, Hans Petter Selasky wrote: Hi Mike, The ugen devices are invisible and dynamically created. Try open /dev/ugen0.2.0.0 (control endpoint) Also you need to re-link your application with dev/usb2/include/usb2_ioctl.h Format is /dev/ugenbus.addr.ifaceindex.endpointno I recommend using libusb20 to access your USB device. See man libusb20. Hi, Thanks for the response. These are all out of the ports (openct,opensc). Are there any pointers somewhere on how to best teach old apps about the new USB2 world on FreeBSD ? ---Mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
eToken and USB2 (ugen issue?)
I was going to try out some of our apps on HEAD with USB2 kernel. dmesg shows ugen0.3: Aladdin Knowledge Systems Ltd. at usbus0 however, there is no ugen device ? 0[freebsd-current2]# ls -l /dev/u* lrwxr-xr-x 1 root wheel6 Feb 6 15:34 /dev/urandom - random crwxrwxrwx 1 root operator0, 81 Feb 6 15:34 /dev/usb 0[freebsd-current2]# where as on RELENG_7, it comes up as ugen0: Aladdin Knowledge Systems Ltd. Token 255.255.255.255 2.7.195, class 0/0, rev 1.10/1.00, addr 4 on uhub5 0[nanobsd2]# ls -l /dev/ugen0 crw-r--r-- 1 root operator - 0, 100 Feb 2 09:13 /dev/ugen0 0[nanobsd2]# which openct/opensc use to talk to the token. Is there something I need to add to the kernel ? I am using the USB2 kernel definition on AMD64 ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org
Re: eToken and USB2 (ugen issue?)
At 04:26 PM 2/6/2009, Mike Tancsa wrote: I was going to try out some of our apps on HEAD with USB2 kernel. dmesg shows ugen0.3: Aladdin Knowledge Systems Ltd. at usbus0 however, there is no ugen device ? 0[freebsd-current2]# ls -l /dev/u* lrwxr-xr-x 1 root wheel6 Feb 6 15:34 /dev/urandom - random crwxrwxrwx 1 root operator0, 81 Feb 6 15:34 /dev/usb 0[freebsd-current2]# where as on RELENG_7, it comes up as ugen0: Aladdin Knowledge Systems Ltd. Token 255.255.255.255 2.7.195, class 0/0, rev 1.10/1.00, addr 4 on uhub5 0[nanobsd2]# ls -l /dev/ugen0 crw-r--r-- 1 root operator - 0, 100 Feb 2 09:13 /dev/ugen0 0[nanobsd2]# which openct/opensc use to talk to the token. Is there something I need to add to the kernel ? I am using the USB2 kernel definition on AMD64 I turned up the debugging and dumped out the following info usbconfig -u 0 -a 2 dump_curr_config_desc ugen0.2: Token 255.255.255.255 2.7.195 Aladdin Knowledge Systems Ltd. at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0014 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x no string bmAttributes = 0x0080 bMaxPower = 0x0032 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x bAlternateSetting = 0x bNumEndpoints = 0x bInterfaceClass = 0x00ff bInterfaceSubClass = 0x bInterfaceProtocol = 0x iInterface = 0x no string 0[freebsd-current2]# usbconfig -u 0 -a 2 dump_access Global Access: root:operator 0660 ugen0.2: Token 255.255.255.255 2.7.195 Aladdin Knowledge Systems Ltd. at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON Device Access: not set Interface 0 Access: not set 0[freebsd-current2]# ugen0.2: Aladdin Knowledge Systems Ltd. at usbus0 (disconnected) ugen0.2: Genesys Logic at usbus0 ushub2: Genesys Logic USB Hub, class 9/0, rev 1.01/0.12, addr 2 on usbus0 ushub2: 4 ports with 4 removable, self powered ugen0.3: Aladdin Knowledge Systems Ltd. at usbus0 ushub2: at ushub0, port 1, addr 2 (disconnected) ugen0.3: Aladdin Knowledge Systems Ltd. at usbus0 (disconnected) ugen0.2: Genesys Logic at usbus0 (disconnected) ugen0.2: Aladdin Knowledge Systems Ltd. at usbus0 ugen_open:157: flag=0x1 ugen_open:157: flag=0x2 ugen_ioctl:1396: cmd=0x4004557e ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x4004557e ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x40125569 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x40125569 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x41705570 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x41705570 ugen_ioctl_post:2178: error=0 ugen_close:187: flag=0x1 ugen_close:201: no FIFOs ugen_close:187: flag=0x2 ugen_close:201: no FIFOs ugen_open:157: flag=0x1 ugen_open:157: flag=0x2 ugen_ioctl:1396: cmd=0x4004557e ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x4004557e ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x40125569 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x40125569 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x41705570 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x41705570 ugen_ioctl_post:2178: error=0 ugen_close:187: flag=0x1 ugen_close:201: no FIFOs ugen_close:187: flag=0x2 ugen_close:201: no FIFOs ugen_open:157: flag=0x1 ugen_open:157: flag=0x2 ugen_ioctl:1396: cmd=0x4004557e ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x4004557e ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x40125569 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x40125569 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x41705570 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x41705570 ugen_ioctl_post:2178: error=0 ugen_close:187: flag=0x1 ugen_close:201: no FIFOs ugen_close:187: flag=0x2 ugen_close:201: no FIFOs ugen_open:157: flag=0x1 ugen_open:157: flag=0x2 ugen_ioctl:1396: cmd=0x4004557e ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x4004557e ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x40125569 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x40125569 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x41705570 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x41705570 ugen_ioctl_post:2178: error=0 ugen_close:187: flag=0x1 ugen_close:201: no FIFOs ugen_close:187: flag=0x2 ugen_close:201: no FIFOs ugen_open:157: flag=0x1 ugen_open:157: flag=0x2 ugen_ioctl:1396: cmd=0x4004557e ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x4004557e ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x40125569 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x40125569 ugen_ioctl_post:2178: error=0 ugen_ioctl:1396: cmd=0x41705570 ugen_ioctl:1579: error=-3 ugen_ioctl_post:1977: cmd=0x41705570 ugen_ioctl_post:2178: error=0 ugen_close:187: flag=0x1 ugen_close:201: no FIFOs ugen_close:187: flag=0x2 ugen_close:201: no FIFOs ugen_open:157: flag
uftdi buffer size and latency
Hi,
Based on what we found in
http://lists.freebsd.org/pipermail/freebsd-current/2008-December/001052.html
I hacked up the following patch to uftdi which allows the recv/xmit
buffer size to be tuned at bootup time. This allows our app which is
low speed (1200bps), but very timing sensitive to work using a usb
serial adaptor based on the uftdi chipset. For us, adding
hint.uftdi.0.buffersize=9 to /boot/device.hints does the trick.
Is there a better way to do this ? Are there any other side effects
anyone can think of ?
--- sys/dev/usb/uftdi.c.orig2008-12-09 11:47:02.0 -0500
+++ sys/dev/usb/uftdi.c 2008-12-09 11:47:05.0 -0500
@@ -198,6 +198,7 @@
usb_interface_descriptor_t *id;
usb_endpoint_descriptor_t *ed;
int i;
+ unsigned int ivar;
usbd_status err;
struct ucom_softc *ucom = sc-sc_ucom;
DPRINTFN(10,(\nuftdi_attach: sc=%p\n, sc));
@@ -353,11 +354,27 @@
ucom-sc_portno = FTDI_PIT_SIOA;
else
ucom-sc_portno = FTDI_PIT_SIOA + id-bInterfaceNumber;
- /* bulkin, bulkout set above */
- ucom-sc_ibufsize = UFTDIIBUFSIZE;
- ucom-sc_obufsize = UFTDIOBUFSIZE - sc-sc_hdrlen;
- ucom-sc_ibufsizepad = UFTDIIBUFSIZE;
+ /* For certain low speed / timing sensitive applications
having the buffers too large causes
+ data to be stuck in the queue too long. By adding a
tuneable, users can lower the buffer
+ size to what works for their application
+*/
+
+ if (!resource_int_value(
+ uftdi, device_get_unit(ucom-sc_dev), buffersize,
ivar) (ivar sc-sc_hdrlen ivar = UFTDIIBUFSIZE) ) {
+ ucom-sc_ibufsize = ivar;
+ ucom-sc_obufsize = ivar - sc-sc_hdrlen;
+ ucom-sc_ibufsizepad = ivar;;
+ device_printf(ucom-sc_dev, Setting buffers
to %d\n,ivar);
+ }
+ else
+ {
+ ucom-sc_ibufsize = UFTDIIBUFSIZE;
+ ucom-sc_obufsize = UFTDIOBUFSIZE - sc-sc_hdrlen;
+ ucom-sc_ibufsizepad = UFTDIIBUFSIZE;
+ device_printf(ucom-sc_dev, Setting buffers
to default of %d\n,UFTDIIBUFSIZE);
+
+ }
ucom-sc_opkthdrlen = sc-sc_hdrlen;
---Mike
Mike Tancsa, tel +1 519 651 3400
Sentex Communications,[EMAIL PROTECTED]
Providing Internet since 1994www.sentex.net
Cambridge, Ontario Canada www.sentex.net/mike
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ucom serial bug?
At 05:37 PM 12/4/2008, Mike Tancsa wrote: At 05:20 PM 12/4/2008, Hans Petter Selasky wrote: On Thursday 04 December 2008, Gabor wrote: Some more twists to this. As I said if I kill off our program and restart it, it never sees carrier unless the module was reloaded. However, if I unplug the serial cable from the Windows box and re-plug it, carrier goes and comes back as expected but only as long as our software is running. If our software is not running and we unplug the serial cable from the Windows box, carrier does not come back when we start up our program with the cable plugged back in. Maybe you can try setting the MSR to zero when the modem is opened in the uftdi.c driver file. In USB2 there is also a sysctl for UFTDI debugging which you can check. Hi, In the regular USB stack, I did run it with some debugging enabled. The diff between the first run and the second run is below using Gabor's check carrier program I havent tried with debugging enabled and just pulling the serial cable out yet. I will try that tomorrow when back at the office! While the program is running and has /dev/cuaU0 open and NOT seeing carrier (when it should) its just a series of Dec 5 15:56:50 current kernel: ucomstartread: start Dec 5 15:56:50 current kernel: ucomreadcb: status = 0 Dec 5 15:56:50 current kernel: ucomreadcb: got 2 chars, tp = 0xc4d19000 Dec 5 15:56:50 current kernel: uftdi_read: sc=0xc4568d80, port=1 count=2 Dec 5 15:56:50 current kernel: ucomstartread: start with 4 ioctls in a 1 second span # grep 15:56:50 all.log | grep ioc Dec 5 15:56:50 current kernel: ucomioctl: cmd = 0x4004746a Dec 5 15:56:50 current kernel: ucomioctl: cmd = 0x4004746a Dec 5 15:56:50 current kernel: ucomioctl: cmd = 0x4004746a Dec 5 15:56:50 current kernel: ucomioctl: cmd = 0x4004746a When I go and unplug the serial cable and then plug it back in I see Dec 5 15:56:52 current kernel: ucomreadcb: status = 0 Dec 5 15:56:52 current kernel: ucomreadcb: got 2 chars, tp = 0xc4d19000 Dec 5 15:56:52 current kernel: uftdi_read: sc=0xc4568d80, port=1 count=2 Dec 5 15:56:52 current kernel: ucomstartread: start Dec 5 15:56:52 current kernel: ucomreadcb: status = 0 Dec 5 15:56:52 current kernel: ucomreadcb: got 2 chars, tp = 0xc4d19000 Dec 5 15:56:52 current kernel: uftdi_read: sc=0xc4568d80, port=1 count=2 Dec 5 15:56:52 current kernel: uftdi_read: status change msr=0x20(0x00) lsr=0x60(0x60) Dec 5 15:56:52 current kernel: uftdi_status: msr=0x20 lsr=0x60 Dec 5 15:56:52 current kernel: ucom_status_change: DCD changed to 1 Dec 5 15:56:52 current kernel: ucomstartread: start Dec 5 15:56:52 current kernel: ucomreadcb: status = 0 Dec 5 15:56:52 current kernel: ucomreadcb: got 2 chars, tp = 0xc4d19000 Dec 5 15:56:52 current kernel: uftdi_read: sc=0xc4568d80, port=1 count=2 Dec 5 15:56:52 current kernel: ucomstartread: start Dec 5 15:56:52 current kernel: ucomreadcb: status = 0 Dec 5 15:56:52 current kernel: ucomreadcb: got 2 chars, tp = 0xc4d19000 Dec 5 15:56:52 current kernel: uftdi_read: sc=0xc4568d80, port=1 count=2 Dec 5 15:56:52 current kernel: ucomstartread: start Dec 5 15:56:52 current kernel: ucomreadcb: status = 0 Dec 5 15:56:52 current kernel: ucomreadcb: got 2 chars, tp = 0xc4d19000 Dec 5 15:56:52 current kernel: uftdi_read: sc=0xc4568d80, port=1 count=2 Dec 5 15:56:52 current kernel: ucomstartread: start Dec 5 15:56:52 current kernel: ucomreadcb: status = 0 Dec 5 15:56:52 current kernel: ucomreadcb: got 2 chars, tp = 0xc4d19000 Dec 5 15:56:52 current kernel: uftdi_read: sc=0xc4568d80, port=1 count=2 Dec 5 15:56:52 current kernel: uftdi_read: status change msr=0xa0(0x20) lsr=0x60(0x60) Dec 5 15:56:52 current kernel: uftdi_status: msr=0xa0 lsr=0x60 Dec 5 15:56:52 current kernel: ucomstartread: start Dec 5 15:56:52 current kernel: ucomreadcb: status = 0 Dec 5 15:56:52 current kernel: ucomreadcb: got 2 chars, tp = 0xc4d19000 Dec 5 15:56:52 current kernel: uftdi_read: sc=0xc4568d80, port=1 count=2 Dec 5 15:56:52 current kernel: ucomstartread: start Dec 5 15:56:52 current kernel: ucomreadcb: status = 0 Dec 5 15:56:52 current kernel: ucomreadcb: got 2 chars, tp = 0xc4d19000 Dec 5 15:56:52 current kernel: uftdi_read: sc=0xc4568d80, port=1 count=2 Dec 5 15:56:52 current kernel: ucomstartread: start Dec 5 15:56:52 current kernel: ucomreadcb: status = 0 Dec 5 15:56:52 current kernel: ucomreadcb: got 2 chars, tp = 0xc4d19000 Dec 5 15:56:52 current kernel: uftdi_read: sc=0xc4568d80, port=1 count=2 Dec 5 15:56:52 current kernel: ucomstartread: start Dec 5 15:56:52 current kernel: ucomreadcb: status = 0 Dec 5 15:56:52 current kernel: ucomreadcb: got 2 chars, tp = 0xc4d19000 Dec 5 15:56:52 current kernel: uftdi_read: sc=0xc4568d80, port=1 count=2 Dec 5 15:56:52 current kernel: ucomstartread: start Dec 5 15:56:52 current kernel: ucomreadcb: status = 0 Dec 5 15:56:52 current kernel: ucomreadcb: got 2 chars, tp = 0xc4d19000 Dec 5 15:56:52 current kernel
Re: ucom serial bug?
At 02:33 PM 12/3/2008, Gabor wrote: everything works fine. When we try to use a USB to serial converter(type doesn't matter, UFTDI or Prolific) we run into problems. The first time we start up our side, everything works. The second time we don't get carrier(DCD). The other side is always running. Since we have no control Also tried with the usb2 development stack, and we never see carrier. Id Refs AddressSize Name 1 20 0xc040 9f8014 kernel (/boot/kernel/kernel) 21 0xc4b95000 3000 usb2_serial_ftdi.ko (/boot/kernel/usb2_serial_ftdi.ko) 35 0xc4b99000 36000usb2_core.ko (/boot/kernel/usb2_core.ko) 41 0xc4c56000 4000 usb2_serial.ko (/boot/kernel/usb2_serial.ko) 51 0xc4cb4000 a000 usb2_controller_uhci.ko (/boot/kernel/usb2_controller_uhci.ko) 62 0xc4cbe000 3000 usb2_controller.ko (/boot/kernel/usb2_controller.ko) 71 0xc4d5 d000 usb2_controller_ehci.ko (/boot/kernel/usb2_controller_ehci.ko) ---Mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ucom serial bug?
At 05:20 PM 12/4/2008, Hans Petter Selasky wrote: On Thursday 04 December 2008, Gabor wrote: Some more twists to this. As I said if I kill off our program and restart it, it never sees carrier unless the module was reloaded. However, if I unplug the serial cable from the Windows box and re-plug it, carrier goes and comes back as expected but only as long as our software is running. If our software is not running and we unplug the serial cable from the Windows box, carrier does not come back when we start up our program with the cable plugged back in. Maybe you can try setting the MSR to zero when the modem is opened in the uftdi.c driver file. In USB2 there is also a sysctl for UFTDI debugging which you can check. Hi, In the regular USB stack, I did run it with some debugging enabled. The diff between the first run and the second run is below using Gabor's check carrier program I havent tried with debugging enabled and just pulling the serial cable out yet. I will try that tomorrow when back at the office! In terms of setting the MSR to zero, do you mean in static int uftdi_open(void *vsc, int portno) ? First run where the program sees carrier : ucom0 on uhub3 : ucomtty_param: sc = 0xc47faa80 : ucomstopread: enter : ucomstopread: bulkin pipe NULL : uftdi_param: sc=0xc47faa80 : ucomstartread: start : ucom_dtr: onoff = 1 : uftdi_set: sc=0xc47faa80, port=1 reg=1 onoff=1 : ucom_rts: onoff = 1 : uftdi_set: sc=0xc47faa80, port=1 reg=2 onoff=1 : ucom0: ucomtty_open: tp = 0xc4c7c800 : ucom_dtr: onoff = 1 : uftdi_set: sc=0xc47faa80, port=1 reg=1 onoff=1 : ucom_rts: onoff = 1 : uftdi_set: sc=0xc47faa80, port=1 reg=2 onoff=1 : uftdi_open: sc=0xc47faa80 : uftdi_param: sc=0xc47faa80 : ucomtty_open: open pipes in = 129 out = 2 : ucomstartread: start : ucomioctl: cmd = 0x402c7413 : ucomioctl: cmd = 0x802c7414 : ucomtty_param: sc = 0xc47faa80 : ucomstopread: enter : ucomreadcb: status = 6 : ucomstopread: leave : uftdi_param: sc=0xc47faa80 : ucomstartread: start : ucomioctl: cmd = 0x8004667e : ucomioctl: cmd = 0x8004667d : ucomioctl: cmd = 0x4004746a : ucomioctl: cmd = 0x4004746a : ucomioctl: cmd = 0x8004746d : ucom_dtr: onoff = 1 : uftdi_set: sc=0xc47faa80, port=1 reg=1 onoff=1 : ucomreadcb: status = 0 : ucomreadcb: got 2 chars, tp = 0xc4c7c800 : uftdi_read: status change msr=0xb0(0x00) lsr=0x60(0x00) : uftdi_status: msr=0xb0 lsr=0x60 : ucom_status_change: about to check sc-sc_poll it is 1 : ucom_status_change: DCD changed to 1 : ucomstartread: start : ucom_rts: onoff = 1 : uftdi_set: sc=0xc47faa80, port=1 reg=2 onoff=1 : ucomioctl: cmd = 0x4004746a : ucom0: ucomtty_close : ucom_cleanup: closing pipes : ucom_shutdown : ucom_dtr: onoff = 0 : uftdi_set: sc=0xc47faa80, port=1 reg=1 onoff=0 : ucomreadcb: status = 0 : ucomreadcb: got 2 chars, tp = 0xc4c7c800 : uftdi_read: status change msr=0x00(0xb0) lsr=0x60(0x60) : uftdi_status: msr=0x00 lsr=0x60 : ucom_status_change: about to check sc-sc_poll it is 1 : ucom_status_change: DCD changed to 0 : ucomstartread: start : ucom_rts: onoff = 1 : uftdi_set: sc=0xc47faa80, port=1 reg=2 onoff=1 : ucomreadcb: status = 0 : ucomreadcb: got 2 chars, tp = 0xc4c7c800 : uftdi_read: status change msr=0xb0(0x00) lsr=0x60(0x60) : uftdi_status: msr=0xb0 lsr=0x60 : ucom_status_change: about to check sc-sc_poll it is 1 : ucom_status_change: DCD changed to 1 : ucomstartread: start : ucomreadcb: status = 6 and second run, where it does not : ucomtty_param: sc = 0xc47faa80 : ucomstopread: enter : ucomstopread: leave : uftdi_param: sc=0xc47faa80 : ucomstartread: start : ucom_dtr: onoff = 1 : uftdi_set: sc=0xc47faa80, port=1 reg=1 onoff=1 : ucom_rts: onoff = 1 : uftdi_set: sc=0xc47faa80, port=1 reg=2 onoff=1 : ucom0: ucomtty_open: tp = 0xc4c7c800 : ucom_dtr: onoff = 1 : uftdi_set: sc=0xc47faa80, port=1 reg=1 onoff=1 : ucom_rts: onoff = 1 : uftdi_set: sc=0xc47faa80, port=1 reg=2 onoff=1 : uftdi_open: sc=0xc47faa80 : uftdi_param: sc=0xc47faa80 : ucomtty_open: open pipes in = 129 out = 2 : ucomstartread: start : ucomioctl: cmd = 0x402c7413 : ucomioctl: cmd = 0x802c7414 : ucomtty_param: sc = 0xc47faa80 : ucomstopread: enter : ucomreadcb: status = 6 : ucomstopread: leave : uftdi_param: sc=0xc47faa80 : ucomstartread: start : ucomioctl: cmd = 0x8004667e : ucomioctl: cmd = 0x8004667d : ucomioctl: cmd = 0x4004746a : ucomioctl: cmd = 0x4004746a : ucomioctl: cmd = 0x8004746d : ucom_dtr: onoff = 1 : uftdi_set: sc=0xc47faa80, port=1 reg=1 onoff=1 : ucomreadcb: status = 0 : ucomreadcb: got 2 chars, tp = 0xc4c7c800 : ucomstartread: start : ucom_rts: onoff = 1 : uftdi_set: sc=0xc47faa80, port=1 reg=2 onoff=1 : ucomioctl: cmd = 0x4004746a : ucom0: ucomtty_close : ucom_cleanup: closing pipes : ucom_shutdown : ucom_dtr: onoff = 0 : uftdi_set: sc=0xc47faa80, port=1 reg=1 onoff=0 : ucomreadcb: status = 0 : ucomreadcb: got 2 chars, tp = 0xc4c7c800 : uftdi_read: status change msr=0x00(0xb0) lsr=0x60(0x60) : uftdi_status: msr=0x00 lsr=0x60 : ucomstartread: start : ucom_rts: onoff
RELENG_7 reliable USB ethernet driver?
I need to outfit some boxes with a USB ethernet adaptor. They will be running RELENG_7 and speed is not important (10/100 is fine), but reliability is. Does anyone have any recommendations ? ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,[EMAIL PROTECTED] Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RFC: ugensa(4) driver ported from NetBSD
Hi, Sorry it took so long to test again. This version now works for me with the appropriate device IDs manually added. If you commit this driver to the tree (it would be great if it were) could you also add the Sierra Wireless 875 ? ugensa0: Sierra Wireless, Incorporated Mini Card, class 0/0, rev 1.10/0.01, addr 2 on uhub0 ugensa_attach: sc = 0xc236f780 ugensa0: unexpected endpoint # usbdevs -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, OHCI root hub(0x), AMD(0x), rev 1.00 port 1 addr 2: full speed, power 500 mA, config 1, Mini Card(0x6812), Sierra Wireless, Incorporated(0x1199), rev 0.01 port 2 powered port 3 powered port 4 powered Controller /dev/usb1: addr 1: high speed, self powered, config 1, EHCI root hub(0x), AMD(0x), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered ---Mike At 05:27 AM 1/4/2008, Mario Sergio Fujikawa Ferreira wrote: Hi, I fixed the permissions. You can grab the updated version now. Regards, Mario Sergio Fujikawa Ferreira wrote: Hi, There is an updated version of the driver available at http://people.FreeBSD.org/~lioux/ugensa.tar.gz Let me know how it goes. I enabled debug mode so there should be more information this time if something goes wrong. Regards, ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RFC: ugensa(4) driver ported from NetBSD
At 03:25 PM 1/10/2008, Mike Tancsa wrote: Hi, Sorry it took so long to test again. This version now works for me with the appropriate device IDs manually added. If you commit this driver to the tree (it would be great if it were) could you also add the Sierra Wireless 875 ? Actually, upon further testing, it doesnt quite work. Some of the characters are being dropped, so I cant fire up PPP. The script fails in random places unfortunately due to missed responses. ---Mike ugensa0: Sierra Wireless, Incorporated Mini Card, class 0/0, rev 1.10/0.01, addr 2 on uhub0 ugensa_attach: sc = 0xc236f780 ugensa0: unexpected endpoint # usbdevs -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, OHCI root hub(0x), AMD(0x), rev 1.00 port 1 addr 2: full speed, power 500 mA, config 1, Mini Card(0x6812), Sierra Wireless, Incorporated(0x1199), rev 0.01 port 2 powered port 3 powered port 4 powered Controller /dev/usb1: addr 1: high speed, self powered, config 1, EHCI root hub(0x), AMD(0x), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered ---Mike At 05:27 AM 1/4/2008, Mario Sergio Fujikawa Ferreira wrote: Hi, I fixed the permissions. You can grab the updated version now. Regards, Mario Sergio Fujikawa Ferreira wrote: Hi, There is an updated version of the driver available at http://people.FreeBSD.org/~lioux/ugensa.tar.gz Let me know how it goes. I enabled debug mode so there should be more information this time if something goes wrong. Regards, ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RFC: ugensa(4) driver ported from NetBSD
At 07:31 AM 12/31/2007, Mario Sergio Fujikawa Ferreira wrote: Hi, I wrote a simple port of the NetBSD ugensa(4) driver: USB generic serial adapter http://www.daemon-systems.org/man/ugensa.4.html I would like for you to review the ported kernel module. The file can be found at Hi, I will give it a try! I have a few such devices that I have been using on FreeBSD with the driver at http://www.cs.cmu.edu/~dga/dot/fbsd_pc5220/ugencom.c It would be great if this could be part of the base of FreeBSD! ---Mike http://people.FreeBSD.org/~lioux/ugensa.tar.gz The files are as follow: - Modified kernel module for FreeBSD based on src/sys/dev/usb/uplcom.c ugensa/ugensa.c - Original NetBSD kernel module ugensa/ugensa.c.orig - Some header definitions while usbdevs is not updated ugensa/ugensa.h Unfortunally, I haven't been able to test this module since it means that I have to buy one of the supported devices. It is a chicken-n-egg problem. Nevertheless, I would like to know if I made any obvious mistakes on the module porting. Regards, -- Mario S F Ferreira - DF - Brazil - I guess this is a signature. feature, n: a documented bug | bug, n: an undocumented feature ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RFC: ugensa(4) driver ported from NetBSD
At 07:31 AM 12/31/2007, Mario Sergio Fujikawa Ferreira wrote: Hi, I wrote a simple port of the NetBSD ugensa(4) driver: USB generic serial adapter http://www.daemon-systems.org/man/ugensa.4.html I would like for you to review the ported kernel module. The file can be found at Hi, I added the defs for my Sierra 875, but the box panics up when I connect to the port # usbdevs -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, OHCI root hub(0x), AMD(0x), rev 1.00 port 1 addr 2: full speed, power 500 mA, config 1, Mini Card(0x6812), Sierra Wireless, Incorporated(0x1199), rev 0.01 ugensa0: Sierra Wireless, Incorporated Mini Card, class 0/0, rev 1.10/0.01, addr 2 on uhub0 ugensa0: unexpected endpoint Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x20:0xc04de493 stack pointer = 0x28:0xccea3974 frame pointer = 0x28:0xccea39a4 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 990 (cu) trap number = 12 panic: page fault Uptime: 2m34s Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort ---Mike http://people.FreeBSD.org/~lioux/ugensa.tar.gz The files are as follow: - Modified kernel module for FreeBSD based on src/sys/dev/usb/uplcom.c ugensa/ugensa.c - Original NetBSD kernel module ugensa/ugensa.c.orig - Some header definitions while usbdevs is not updated ugensa/ugensa.h Unfortunally, I haven't been able to test this module since it means that I have to buy one of the supported devices. It is a chicken-n-egg problem. Nevertheless, I would like to know if I made any obvious mistakes on the module porting. Regards, -- Mario S F Ferreira - DF - Brazil - I guess this is a signature. feature, n: a documented bug | bug, n: an undocumented feature ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RFC: ugensa(4) driver ported from NetBSD
At 11:11 AM 12/31/2007, Mike Tancsa wrote: At 07:31 AM 12/31/2007, Mario Sergio Fujikawa Ferreira wrote: Hi, I wrote a simple port of the NetBSD ugensa(4) driver: USB generic serial adapter http://www.daemon-systems.org/man/ugensa.4.html I would like for you to review the ported kernel module. The file can be found at Some more details Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x20:0xc04eb6d3 stack pointer = 0x28:0xcc5ae958 frame pointer = 0x28:0xcc5ae988 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 847 (cu) [thread pid 847 tid 100062 ] Stopped at usbd_open_pipe_ival+0x13: movl0x4(%eax),%eax db bt Tracing pid 847 tid 100062 td 0xc1dfc210 usbd_open_pipe_ival(c1d74390,,cc5ae9bc,c04de072,0,...) at usbd_open_pipe_ival+0x13 usbd_open_pipe(0,85,0,c1d74390,c1d7a800,...) at usbd_open_pipe+0x24 ucomopen(c1d7a800,c1d76400,0,c2346dd0,cc5ae9f4,...) at ucomopen+0xa2 ttyopen(c1d76400,7,2000,c1dfc210,0,...) at ttyopen+0x286 giant_open(c1d76400,7,2000,c1dfc210,cc5aea50,...) at giant_open+0x73 devfs_open(cc5aea8c,cc5aeb1c,c05ca5a7,c074dbe0,cc5aea8c,...) at devfs_open+0x21f VOP_OPEN_APV(c074dbe0,cc5aea8c,cc5aea84,c1dadaa0,c2346dd0,...) at VOP_OPEN_APV+0x42 vn_open_cred(cc5aeb80,cc5aec78,94c,c22ba800,c1e2a750,...) at vn_open_cred+0x487 vn_open(cc5aeb80,cc5aec78,94c,c1e2a750,c22ba800,...) at vn_open+0x33 kern_open(c1dfc210,bfbfed56,0,7,bfbfeb4c,...) at kern_open+0xc4 open(c1dfc210,cc5aecfc,c,16,cc5aed2c,...) at open+0x30 syscall(cc5aed38) at syscall+0x317 Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (5, FreeBSD ELF32, open), eip = 0x28145f1b, esp = 0xbfbfeb3c, ebp = 0xbfbfeb88 --- ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb/umass, devfs: this sucks
At 11:41 PM 12/21/2007, Mikhail Teterin wrote: Another attempt to use USB-storage with FreeBSD, another moment of hair-pulling frustration. I attach the card-reader with the media card already inserted (detection of card-insertion has not worked in a long time, if ever). Perhaps its the one card reader you are using is particularly problematic ? I have been using the multi-type cheapo reader below for some time port 6 addr 2: high speed, power 100 mA, config 1, Mass Storage Device(0x6362), Generic(0x058f), rev 1.26 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Generic USB SD Reader 1.00 Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present da1 at umass-sim0 bus 0 target 0 lun 1 da1: Generic USB CF Reader 1.01 Removable Direct Access SCSI-0 device da1: 40.000MB/s transfers da1: 976MB (2000880 512 byte sectors: 64H 32S/T 976C) da2 at umass-sim0 bus 0 target 0 lun 2 da2: Generic USB SM Reader 1.02 Removable Direct Access SCSI-0 device da2: 40.000MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present da3 at umass-sim0 bus 0 target 0 lun 3 da3: Generic USB MS Reader 1.03 Removable Direct Access SCSI-0 device da3: 40.000MB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present We go through the following steps when using it. We always plug the reader in without a card. Then we put the card in and do a cat /dev/null /dev/da1 ... or whatever the device is. Its been quite reliable this way for us. The other caveat is never to pull the card or reader when its mounted. ---Mike The disk appears: umass1: Genesys USB Reader, rev 2.00/91.38, addr 3 da6 at umass-sim1 bus 1 target 0 lun 0 da6: Generic STORAGE DEVICE 9138 Removable Direct Access SCSI-0 device da6: 40.000MB/s transfers da6: 1938MB (3970048 512 byte sectors: 255H 63S/T 247C) (da6:umass-sim1:1:0:0): AutoSense Failed But the slices (/dev/da6s1, etc.) don't appear: http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/76461 In the past, trying to mount, or otherwise read the da6 would result in the slices appearing -- an awful wart, when it works. So I try it, but it does not work: [EMAIL PROTECTED]:/home/mi (116) mount -tmsdosfs /dev/da6 /mnt ... hang ... Pressing Ctrl-T: load: 0.58 cmd: mount_msdosfs 64452 [GEOM topology] 0.00u 0.00s 0% 804k ... load: 0.47 cmd: mount_msdosfs 64452 [GEOM topology] 0.00u 0.00s 0% 804k It still hangs, and now other things hang too. top, for example, hangs on start-up: [EMAIL PROTECTED]:~ (1084) top ... hang ... Pressing Ctrl-T: load: 0.57 cmd: top 64480 [devfs] 0.00u 0.00s 0% 1652k load: 0.57 cmd: top 64480 [devfs] 0.00u 0.00s 0% 1652k load: 0.57 cmd: top 64480 [devfs] 0.00u 0.00s 0% 1652k load: 0.57 cmd: top 64480 [devfs] 0.00u 0.00s 0% 1652k No new window can be opened either -- presumably due to devfs hanging. I suspect, that anything attempting to use even the /dev/null is hanging now. So, not only the USB itself is broken, our wonderful devfs is rather creaky too -- nothing should be in an uninterruptible state like this for more than a millisecond. 25 minutes later the mount finally gave up: umass1: BBB reset failed, TIMEOUT umass1: BBB bulk-in clear stall failed, TIMEOUT umass1: BBB bulk-out clear stall failed, TIMEOUT mount_msdosfs: /dev/da6: Input/output error Things are back to normal again, but the media card is still inaccessible. I'll try to work with it using mtools -- I had some success in the pass accessing the FAT-filesystem on the media cards using mcopy, mdir, etc. I'm using 6.3-PRERELEASE as of Dec 6th, but a search for umass-related bugs http://www.freebsd.org/cgi/query-pr-summary.cgi?text=umass reveals plenty of really old problems, which don't even have a single follow-up from FreeBSD-developers. Like: http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/95037 http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/95173 http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/107848 Looks like USB is unmaintained and getting worse. Are we really shipping this as the most recent stable release? -mi ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
