Current problem reports assigned to freebsd-usb@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o usb/165815 usbadd k3772z 3g modem support o usb/165163 usb[keyboard] The USB RF keyboard and mouse become non-re o usb/164058 usbLexar 8GB USB flash drive doesn't work by default o usb/163328 usb[usb] Support for Atheros USB abgn devices o kern/163091 usb[panic] Fatal trap 12: page fault while in kernel mode o usb/162306 usbusb devices cant get address asignation, no memories, o usb/162054 usbusbdump just hangs on 9.0-RC1 f usb/161793 usbpoor EHCI usb2 i/o performance o usb/160436 usbucom wedges machine on parity error ? o usb/160299 usbMicroSDHC-to-USB adapters do not work in FreeBSD 8.x o usb/160192 usb[install] Installation from USB-Stick doesn't find the o usb/159274 usbUSB 3.0 Etron EJ168A does not work. f usb/159191 usb[fusefs-ntfs] write on fusefs-ntfs mounted partition r o usb/157376 usbLaCie USB disk not recognized o usb/157074 usb[boot] [usb8] vfs_mountroot_ask is called when no usb o usb/156898 usb[keyboard] usb keyboard does not work while boot (ps2 f usb/156735 usbNeed Quirk for Goflex USB Disk Drives o usb/156725 usbUSB stack stall cause complete system input loss o usb/156596 usb[ehci] Extremely high interrupt rate on ehci/uhci IRQ1 o usb/156000 usbrum(4) Fatal trap 18: integer divide fault while in ke f usb/155996 usbNanoBSD not booted as Disk o usb/155784 usbProblem with Transcend StoreJet 25M3 (2AJ1) on Asus M2 o usb/154506 usb[umass] Copying dir with large files makes FreeBSD loa o usb/154192 usb[umass] In Garmin Oregon GPS, only the first umass dev o i386/153851 usb[keyboard] keyboard issues on new Intel Mother boards. o usb/153703 usb[keyboard] My USB keyboard can not be used in 8-STABLE o usb/153609 usb[zyd] [panic] kernel: Fatal trap 12: page fault while o usb/153149 usb[umass] USB stick quirk regression [regression] o usb/152075 usb[usb8] [ehci] [request] Add quirk for CS5536 USB o usb/150892 usb[zyd] Whenever network contacted in any shape, way or o usb/150189 usb[run] [usb8] [patch] if_run appears to corrupt IP traf p usb/149764 usb[u3g] [patch] usbdevs update: Huawei K3765 3G modem o usb/149283 usb[uftdi] avrdude unable to talk to Arduino board (via u o usb/149162 usb[ural] ASUS WL-167g doesn't work in 8.1 (continue of 1 s usb/148702 usb[usb8] [request] IO DATA USB-RSAQ5 support on FreeBSD- o usb/148080 usbusbconfig(8) sometimes does not turn off the device o usb/147516 usb[umass] [usb67] kernel unable to deal with Olympus USB o i386/147475 usb[install] FreeBSD 8.x does not install on ASUS K8N4-E o usb/146840 usb[hang] FreeBSD 7.2 / 7.3 / 8.0 hang at startup after e o usb/146153 usb[axe] [usb8] Hosts in network doesn't receive any pack f usb/146054 usb[urtw] [usb8] urtw driver potentially out of date f usb/145513 usb[usb8] New USB stack: no new devices after forced usb p usb/145455 usb[usb8] [patch] USB debug support cannot be disabled o usb/145415 usb[umass] [usb8] USB card reader does not create slices a usb/145184 usbGENERIC can't mount root from USB on Asus EEE o usb/145165 usb[keyboard] [usb8] ukbd_set_leds_callback: error=USB_ER f kern/144938 usb[keyboard] [boot] Boot Failure with Apple (MB869LL/A) o usb/144387 usb[run] [panic] if_run panic o usb/144043 usb[umass] [usb8] USB DLT tape drive throws random errors a usb/143790 usb[boot] [cam] can not boot from usb hdd f usb/143620 usb[cdce] [usb8] the module if_cdce doesn't support my Op f usb/143294 usb[usb8] copying process stops at some time (10 - 50 sec o usb/143286 usb[ukbd] [usb8] [boot] boot failures on RELENG_8 system p usb/143186 usb[usbdevs] [usb8] [patch] add USB device IDs for Google a usb/143139 usb[umass] [usb8] [patch] Quirk for Century EX35SW4_SB4 J p usb/143045 usb[umass] [usb8] [patch] mounting Fujitsu 2600Z camera d o usb/142991 usb[uftdi] [usb67] [patch] Patch to add Crystalfontz 533 f usb/142989 usb[usb8] canon eos 50D attaches but detaches after few s f usb/142957 usb[umass] [usb8] [patch] patch for USB disk SYNCHRONIZE o usb/142719 usb[urtw] [usb8] AirLive WL-1600USB (RTL8187L chipset) fa o usb/142713 usb
Re: Impact of changes made to umass.c at r232358
On Friday 06 April 2012 18:19:10 Terence Telkamp wrote: One thing I forgot to mention is that I have a machine in the kernel debugger after the panic, so I can capture more information if any would be helpful. -Original Message- From: owner-freebsd-...@freebsd.org [mailto:owner-freebsd-...@freebsd.org] On Behalf Of Terence Telkamp Sent: Friday, April 06, 2012 11:17 AM To: freebsd-usb@freebsd.org Subject: Impact of changes made to umass.c at r232358 I am seeing a kernel panic in FreeBSD 8.1, which is reproduced after physically attaching and detaching a USB device several times. The kernel debugger shows that the panic happens in camisr where the cam_sim and its associated mutex are clearly destroyed. sim-refcount is 0, sim-softc is 1 (UMASS_GONE), and the sim-mtx is destroyed (mtx_lock = 6). This looks very similar to FreeBSD PR kern/153514, which is unfortunately unresolved. http://www.freebsd.org/cgi/query-pr.cgi?pr=153514 Is it possible that the changes made to umass.c at r232358 might fix this issue? Hi, I need to see the backtrace. The revision you mention fixes a detach panic issue. Current issues are happening inside CAM layer, and that is outside of USB. If you search this list for usbconfig and umass, you will find some e-mails describing how you can stress test umass attach/detach. --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
Re: uhub_reattach_port: could not allocate new device
On Friday 06 April 2012 23:50:07 Xavier wrote: Hi to all, I attach an external USB Drive into a connector on the side of the computer ( not USB hub ). DMESG(8) only say: ugen4.8: Unknown at usbus4 (disconnected) uhub_reattach_port: could not allocate new device I'm running FreeBSD 9.0-RELEASE Can somebody help me ? Hi, Is your drive self powered? Try also: sysctl hw.usb.ehci.no_hs=1 --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
Re: wacom and x11 and webcamd
Hans Petter Selasky wrote: On Thursday 29 March 2012 23:20:43 Denver Hull wrote: Hans Petter Selasky wrote: On Saturday 24 March 2012 18:14:41 Denver Hull wrote: Hello, I discovered this when I saw an update to input-wacom at freshports.org. I've installed cuse4bsd, the new input-wacom, and the latest webcamd: cuse4bsd-kmod-0.1.23 input-wacom-40.0.11.1 webcamd-3.2.0.2 I believe I've followed all the instructions properly, and when I start webcamd, everything seems to be correct: Attached ugen1.2[0] to cuse unit 0 Creating /dev/input/event0 According to dmesg, ugen1.2 is the correct device (I have a Bamboo Pen): ugen1.2:Wacom Co.,Ltd. at usbus1 The /dev/input/event0 node is indeed created. However, when I start X, I get the following: (EE) stylus: Wacom X driver can't grab event device (Bad address) (EE) eraser: Wacom X driver can't grab event device (Bad address) (EE) cursor: Wacom X driver can't grab event device (Bad address) (EE) pad: Wacom X driver can't grab event device (Bad address) (EE) touch: Wacom X driver can't grab event device (Bad address) Protocol not supported by server The last line repeats indefinitely, and X never finishes starting up. The system I'm trying this on is 8.3-PRERELEASE. I had tried this quickly a while ago on 8.2-STABLE with similar results. Does anyone have any ideas about what might be wrong? Hi, I think the wacom has two interfaces. So you need to do two instances of webcamd, using -i 0 and -i 1 . Else search google for webcamd-3.4.0.1 --HPS My Bamboo Pen is working fine now. I installed your latest version, webcamd-3.4.0.1, and that takes care of getting webcamd started properly. It's still necessary to make sure moused doesn't attach to the tablet. I'm not sure what the best way is to do that, but for now I've adjusted /etc/devd.conf so only the first ums device gets attached. Thanks Hans, this is great. I wish I had one or two other devices I could try. Hi, To avoid ums attach, see usbconfig dump_quirk_names | grep UMS. --HPS I don't get anything with that command on my 8.2-STABLE system. Is that something that will work on 9 but not 8? Thanks, Denver ___ 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: wacom and x11 and webcamd
On Monday 09 April 2012 19:59:17 Denver Hull wrote: Hans Petter Selasky wrote: On Thursday 29 March 2012 23:20:43 Denver Hull wrote: Hans Petter Selasky wrote: On Saturday 24 March 2012 18:14:41 Denver Hull wrote: Hello, I discovered this when I saw an update to input-wacom at freshports.org. I've installed cuse4bsd, the new input-wacom, and the latest webcamd: cuse4bsd-kmod-0.1.23 input-wacom-40.0.11.1 webcamd-3.2.0.2 I believe I've followed all the instructions properly, and when I start webcamd, everything seems to be correct: Attached ugen1.2[0] to cuse unit 0 Creating /dev/input/event0 According to dmesg, ugen1.2 is the correct device (I have a Bamboo Pen): ugen1.2:Wacom Co.,Ltd. at usbus1 The /dev/input/event0 node is indeed created. However, when I start X, I get the following: (EE) stylus: Wacom X driver can't grab event device (Bad address) (EE) eraser: Wacom X driver can't grab event device (Bad address) (EE) cursor: Wacom X driver can't grab event device (Bad address) (EE) pad: Wacom X driver can't grab event device (Bad address) (EE) touch: Wacom X driver can't grab event device (Bad address) Protocol not supported by server The last line repeats indefinitely, and X never finishes starting up. The system I'm trying this on is 8.3-PRERELEASE. I had tried this quickly a while ago on 8.2-STABLE with similar results. Does anyone have any ideas about what might be wrong? Hi, I think the wacom has two interfaces. So you need to do two instances of webcamd, using -i 0 and -i 1 . Else search google for webcamd-3.4.0.1 --HPS My Bamboo Pen is working fine now. I installed your latest version, webcamd-3.4.0.1, and that takes care of getting webcamd started properly. It's still necessary to make sure moused doesn't attach to the tablet. I'm not sure what the best way is to do that, but for now I've adjusted /etc/devd.conf so only the first ums device gets attached. Thanks Hans, this is great. I wish I had one or two other devices I could try. Hi, To avoid ums attach, see usbconfig dump_quirk_names | grep UMS. --HPS I don't get anything with that command on my 8.2-STABLE system. Is that something that will work on 9 but not 8? Did you kldload usb_quirk ? --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
Re: wacom and x11 and webcamd
Hans Petter Selasky wrote: On Monday 09 April 2012 19:59:17 Denver Hull wrote: Hans Petter Selasky wrote: On Thursday 29 March 2012 23:20:43 Denver Hull wrote: Hans Petter Selasky wrote: On Saturday 24 March 2012 18:14:41 Denver Hull wrote: Hello, I discovered this when I saw an update to input-wacom at freshports.org. I've installed cuse4bsd, the new input-wacom, and the latest webcamd: cuse4bsd-kmod-0.1.23 input-wacom-40.0.11.1 webcamd-3.2.0.2 I believe I've followed all the instructions properly, and when I start webcamd, everything seems to be correct: Attached ugen1.2[0] to cuse unit 0 Creating /dev/input/event0 According to dmesg, ugen1.2 is the correct device (I have a Bamboo Pen): ugen1.2:Wacom Co.,Ltd.at usbus1 The /dev/input/event0 node is indeed created. However, when I start X, I get the following: (EE) stylus: Wacom X driver can't grab event device (Bad address) (EE) eraser: Wacom X driver can't grab event device (Bad address) (EE) cursor: Wacom X driver can't grab event device (Bad address) (EE) pad: Wacom X driver can't grab event device (Bad address) (EE) touch: Wacom X driver can't grab event device (Bad address) Protocol not supported by server The last line repeats indefinitely, and X never finishes starting up. The system I'm trying this on is 8.3-PRERELEASE. I had tried this quickly a while ago on 8.2-STABLE with similar results. Does anyone have any ideas about what might be wrong? Hi, I think the wacom has two interfaces. So you need to do two instances of webcamd, using -i 0 and -i 1 . Else search google for webcamd-3.4.0.1 --HPS My Bamboo Pen is working fine now. I installed your latest version, webcamd-3.4.0.1, and that takes care of getting webcamd started properly. It's still necessary to make sure moused doesn't attach to the tablet. I'm not sure what the best way is to do that, but for now I've adjusted /etc/devd.conf so only the first ums device gets attached. Thanks Hans, this is great. I wish I had one or two other devices I could try. Hi, To avoid ums attach, see usbconfig dump_quirk_names | grep UMS. --HPS I don't get anything with that command on my 8.2-STABLE system. Is that something that will work on 9 but not 8? Did you kldload usb_quirk ? --HPS Well, that reports kldload: can't load usb_quirk: File exists, but usb_quirk isn't listed in kldstat. The man page for usb_quirk(4) doesn't show anything for UMS. However, everything listed in the man page is reported by usbconfig dump_quirk_names. Or at least it looks that way. I didn't do a line by line check. I checked my kernel conf file, and there's no device usb_quirk line, and it's not in loader.conf, so I'm not sure where it's coming from. In my experience that kldload error usually just means it's compiled in. But it's not listed in my kernel conf file. So that's kind of a mystery. Thanks, Denver ___ 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: wacom and x11 and webcamd
Hans Petter Selasky wrote: On Monday 09 April 2012 21:28:02 Denver Hull wrote: Hans Petter Selasky wrote: On Monday 09 April 2012 19:59:17 Denver Hull wrote: Hans Petter Selasky wrote: On Thursday 29 March 2012 23:20:43 Denver Hull wrote: Hans Petter Selasky wrote: On Saturday 24 March 2012 18:14:41 Denver Hull wrote: Hello, I discovered this when I saw an update to input-wacom at freshports.org. I've installed cuse4bsd, the new input-wacom, and the latest webcamd: cuse4bsd-kmod-0.1.23 input-wacom-40.0.11.1 webcamd-3.2.0.2 I believe I've followed all the instructions properly, and when I start webcamd, everything seems to be correct: Attached ugen1.2[0] to cuse unit 0 Creating /dev/input/event0 According to dmesg, ugen1.2 is the correct device (I have a Bamboo Pen): ugen1.2:Wacom Co.,Ltd. at usbus1 The /dev/input/event0 node is indeed created. However, when I start X, I get the following: (EE) stylus: Wacom X driver can't grab event device (Bad address) (EE) eraser: Wacom X driver can't grab event device (Bad address) (EE) cursor: Wacom X driver can't grab event device (Bad address) (EE) pad: Wacom X driver can't grab event device (Bad address) (EE) touch: Wacom X driver can't grab event device (Bad address) Protocol not supported by server The last line repeats indefinitely, and X never finishes starting up. The system I'm trying this on is 8.3-PRERELEASE. I had tried this quickly a while ago on 8.2-STABLE with similar results. Does anyone have any ideas about what might be wrong? Hi, I think the wacom has two interfaces. So you need to do two instances of webcamd, using -i 0 and -i 1 . Else search google for webcamd-3.4.0.1 --HPS My Bamboo Pen is working fine now. I installed your latest version, webcamd-3.4.0.1, and that takes care of getting webcamd started properly. It's still necessary to make sure moused doesn't attach to the tablet. I'm not sure what the best way is to do that, but for now I've adjusted /etc/devd.conf so only the first ums device gets attached. Thanks Hans, this is great. I wish I had one or two other devices I could try. Hi, To avoid ums attach, see usbconfig dump_quirk_names | grep UMS. --HPS I don't get anything with that command on my 8.2-STABLE system. Is that something that will work on 9 but not 8? Did you kldload usb_quirk ? --HPS Well, that reports kldload: can't load usb_quirk: File exists, but usb_quirk isn't listed in kldstat. The man page for usb_quirk(4) doesn't show anything for UMS. However, everything listed in the man page is reported by usbconfig dump_quirk_names. Or at least it looks that way. I didn't do a line by line check. I checked my kernel conf file, and there's no device usb_quirk line, and it's not in loader.conf, so I'm not sure where it's coming from. In my experience that kldload error usually just means it's compiled in. But it's not listed in my kernel conf file. So that's kind of a mystery. Did you run the usbconfig command like root ? --HPS Yes. ___ 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: wacom and x11 and webcamd
Hans Petter Selasky wrote: On Monday 09 April 2012 21:41:30 Denver Hull wrote: Hans Petter Selasky wrote: Did you run the usbconfig command like root ? --HPS Yes. Hi, It looks like we currently don't have a quirk for UMS, like the following. Adding one such though would be trivial. UQ_HID_IGNORE UQ_KBD_IGNORE --HPS Ok, so until we do have one, I'll continue to use devd.conf to specify the exact device for moused. Thanks, Denver ___ 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
