[ums][patch] mouse wheel doesn't work on -STABLE after recent update
Hello,
my IntelliMouse Explorer 4.0 wheel stops working after recent update. Rolling
back ums.c to the previous (1.96.2.1) version fixes the problem.
I think, there is a typo in the latest version of ums.c: HUG_Z is verified
twice instead of HUG_TWHEEL in previous version. The following patch seems
working for me:
diff -u ums.c.orig ums.c
--- ums.c.orig 2008-04-15 11:09:02.0 +0400
+++ ums.c 2008-04-22 09:53:12.0 +0400
@@ -313,7 +313,7 @@
}
}
} else if (hid_locate(desc, size, HID_USAGE2(HUP_GENERIC_DESKTOP,
-HUG_Z),
+HUG_TWHEEL),
hid_input, sc-sc_loc_z, flags)) {
if ((flags MOUSE_FLAGS_MASK) != MOUSE_FLAGS) {
printf(\n%s: Z report 0x%04x not supported\n,
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to [EMAIL PROTECTED]
usb/122992: MotoROKR Z6 Phone not recognised by umass as USB disk.
Number: 122992 Category: usb Synopsis: MotoROKR Z6 Phone not recognised by umass as USB disk. Confidential: no Severity: non-critical Priority: medium Responsible:freebsd-usb State: open Quarter: Keywords: Date-Required: Class: sw-bug Submitter-Id: current-users Arrival-Date: Tue Apr 22 16:40:00 UTC 2008 Closed-Date: Last-Modified: Originator: Anonymous Release:6.1-RELEASE Organization: Environment: Description: The Z6 has a USB-Disk mode that exposes its memory and microSD card as USB Drives. This mode works on Microsoft Windows XP. However it does not work on FreeBSD. There, it is detected and listed to the system console, but the pseudo-SCSI devices do not appear. How-To-Repeat: Connect a MotoROKR Z6 phone to a FreeBSD system using the provided cable. Fix: The GNU/Linux guys have a patch. Check out Gentoo in particular. Release-Note: Audit-Trail: Unformatted: ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb/122992: MotoROKR Z6 Phone not recognised by umass as USB disk.
The following reply was made to PR usb/122992; it has been noted by GNATS. From: Marcin Cieslak [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Cc: Subject: Re: usb/122992: MotoROKR Z6 Phone not recognised by umass as USB disk. Date: Tue, 22 Apr 2008 20:07:35 +0200 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --enig35202659B68540ED1FB4BDF5 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: quoted-printable The bug mentioned is this: http://bugs.gentoo.org/attachment.cgi?id=3D145870 It would be nice if you could provide your real email address - without=20 feedback we will need to close this bug as invalid. --=20 Marcin Cieslak // [EMAIL PROTECTED] --enig35202659B68540ED1FB4BDF5 Content-Type: application/pgp-signature; name=signature.asc Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename=signature.asc -BEGIN PGP SIGNATURE- iQCVAwUBSA4paj2W2v2wY27ZAQP3nAP/TbmIqdGnAUQDP7J35+z3pmir/XfUngL8 +dIkZjb7B7GRnvL5KLt/nP59n07YtAzT7amydXot8743E50eCND74jS2ecsd1v3n vjMts9M3CPfArxtLpzj/u+XSgR2JSOqGwYOpwGKUww4TLN+03bGhTRDXkJgdwVGJ d8giz6DAdPQ= =rS6B -END PGP SIGNATURE- --enig35202659B68540ED1FB4BDF5-- ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
issue with umass plugged-in during boot up
This is sort of a follow up to the issue of kernel panic when a system is booted with umass device plugged in. Cursory point: I remember having the issue myself when I loaded scsi_low and cam as modules. I blamed it on sg being present in cam.ko, but I have no facts. After I added scsi devices to kernel (sans sg) I stopped having the panics. BTW, I use RELENG_7, i386, UP. Anyway, I see a different issue with booting while a umass device is connected. First issue was that k3b hasn't found my two cd/atapicam devices. Then I executed camcontrol rescan all, it failed with EINVAL. camcontrol reset all - the same error. ktrace showed that the error came from ioctl on xpt device. I rebooted without the umass device and everything went back to normal. I'll try to do more debugging later. -- Andriy Gapon ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: issue with umass plugged-in during boot up
on 22/04/2008 23:16 Andriy Gapon said the following: BTW, I use RELENG_7, i386, UP. Anyway, I see a different issue with booting while a umass device is connected. First issue was that k3b hasn't found my two cd/atapicam devices. Then I executed camcontrol rescan all, it failed with EINVAL. camcontrol reset all - the same error. ktrace showed that the error came from ioctl on xpt device. I rebooted without the umass device and everything went back to normal. I'll try to do more debugging later. Here is a complete and correct scenario with more details. Original boot: uhci1: VIA 83C572 USB controller port 0xbc00-0xbc1f irq 7 at device 12.0 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: VIA 83C572 USB controller port 0xc000-0xc01f irq 10 at device 12.1 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: VIA 83C572 USB controller on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb2 uhub2: 2 ports with 2 removable, self powered ehci0: VIA VT6202 USB 2.0 controller mem 0xe7005000-0xe70050ff irq 11 at device 12.2 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb1 usb2 usb3: VIA VT6202 USB 2.0 controller on ehci0 usb3: USB revision 2.0 uhub3: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb3 uhub3: 4 ports with 4 removable, self powered umass0: Prolific Technology Inc. Mass Storage Device, class 0/0, rev 2.00/1.00, addr 2 on uhub3 ... unknown: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01 da0 at umass-sim0 bus 0 target 0 lun 0 da0: WDC WD40 00AAKS-00YGA0 12.0 Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) cam_periph_alloc: attempt to re-allocate valid device pass2 rejected passasync: Unable to attach new device due to status 0x6: CCB request was invalid cam_periph_alloc: attempt to re-allocate valid device cd2 rejected cdasync: Unable to attach new device due to status 0x6 cd2 at ata1 bus 0 target 0 lun 0 cd2: HL-DT-ST DVDRAM GSA-4163B A105 Removable CD-ROM SCSI-0 device cd2: 3.300MB/s transfers cd2: cd present [2236704 x 2048 byte records] unknown: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cam_periph_alloc: attempt to re-allocate valid device pass1 rejected passasync: Unable to attach new device due to status 0x6: CCB request was invalid cd1 at ata0 bus 0 target 0 lun 0 cd1: LITE-ON LTR-40125W WS03 Removable CD-ROM SCSI-0 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present After boot I cane execute all camcontrol commands without any problems. Here is output of camcontrol devlist -v: scbus0 on umass-sim0 bus 0: WDC WD40 00AAKS-00YGA0 12.0 at scbus0 target 0 lun 0 (da0,pass0) scbus1 on ata0 bus 0: LITE-ON LTR-40125W WS03 at scbus1 target 0 lun 0 (cd1,pass1) at scbus1 target -1 lun -1 () scbus2 on ata1 bus 0: HL-DT-ST DVDRAM GSA-4163B A105 at scbus2 target 0 lun 0 (pass2,cd2) at scbus2 target -1 lun -1 () scbus3 on ata2 bus 0: at scbus3 target -1 lun -1 () scbus4 on ata3 bus 0: at scbus4 target -1 lun -1 () scbus-1 on xpt0 bus 0: at scbus-1 target -1 lun -1 (xpt0) Then I detach the umass disk: umass0: at uhub3 port 2 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry GEOM_LABEL: Label ufs/extstuff removed. GEOM_LABEL: Label ufs/extbackup removed. umass0: detached And here is new output of camcontrol devlist -v: scbus1 on ata0 bus 0: LITE-ON LTR-40125W WS03 at scbus1 target 0 lun 0 (cd1,pass1) at scbus1 target -1 lun -1 () scbus2 on ata1 bus 0: HL-DT-ST DVDRAM GSA-4163B A105 at scbus2 target 0 lun 0 (pass2,cd2) at scbus2 target -1 lun -1 () scbus3 on ata2 bus 0: at scbus3 target -1 lun -1 () scbus4 on ata3 bus 0: at scbus4 target -1 lun -1 () scbus-1 on xpt0 bus 0: at scbus-1 target -1 lun -1 (xpt0) After that camcontrol commands referring to all (rescan and reset) fail with EINVAL. ktrace shows that EINVAL comes from ioctl CAMIOCOMMAND on xpt0 device. My clumsy ddb debugging shows that the error is produced somewhere in xptioctl-xpt_find_bus. It seems that xpt might be unhappy about scbus0/pass0 going away. Maybe this is because in all/-1 case camcontrol sends ccb with path_id (implicitly) set to zero and xptioctl performs xpt_find_bus for all ioctl commands (including XPT_DEV_MATCH)? I.e. see case of bus=-1 in
Re: Soekris 4826 USB failure on FreeBSD 7.0
Wow, this turns out to be much worse than I thought...I've tracked down the problem to the commit of the new physical memory allocator at Sat Jun 16 04:57:05 2007 UTC. Before that, no kern/122380; after that, kern/122380 applies. Any ideas where to go from here? Thanks, Geoff On Mon, Apr 21, 2008 at 12:29:38PM -0600, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Geoffrey Mainland [EMAIL PROTECTED] writes: : I have a number of Soekris 4826 boards with USB thumb drives attached : that happily run FreeBSD 6.0. However, when I try to get them to run : FreeBSD 7, the thumb drives stop working. A PR was recently filed by : someone with a similar issue: kern/122380 (I see the same failure as in : the PR). Looks like something changed in the USB stack from 6 to 7...any : ideas where to look or how I can go about solving this? Lots of cosmetic changes, lots of other changes that were for the better, lots and lots of quirks. I'm guessing something got quirked, or there was a bug fix that caused us to die. As to tracking it down, I'd suggest a binary search between 7.0-release and where RELENG_6 was branched. Not ideal, but that's the likeliest way to cope. Warner ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb/122905: [ubsa] [patch] add Huawei E220 to ubsa
The following reply was made to PR usb/122905; it has been noted by GNATS.
From: Per olof Ljungmark [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Cc:
Subject: Re: usb/122905: [ubsa] [patch] add Huawei E220 to ubsa
Date: Wed, 23 Apr 2008 01:21:41 +0200
This is a multi-part message in MIME format.
--030008040502080503020600
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Just an addendum, the following works very good for me on 7-STABLE.
Changes to ubsa.c and usbdevs are very similar.
In the original patch the PR says Huawei E220 but the pactes says E200B
which I do not completely understand.
--030008040502080503020600
Content-Type: text/plain;
name=patch-usbdevs
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename=patch-usbdevs
--- usbdevs2008-04-12 13:23:21.0 +0200
+++ usbdevs-patched2008-04-23 00:39:29.0 +0200
@@ -1387,6 +1387,7 @@
/* HUAWEI products */
product HUAWEI MOBILE 0x1001 Huawei Mobile
+product HUAWEI E220 0x1003 Huawei E220 HSDPA USB Modem
/* HUAWEI 3com products */
product HUAWEI3COM WUB320G0x0009 Aolynk WUB320g
--030008040502080503020600
Content-Type: text/plain;
name=patch-usb_subr.c
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename=patch-usb_subr.c
--- usb_subr.c 2007-06-30 22:18:44.0 +0200
+++ usb_subr.c-patched 2008-04-23 00:39:29.0 +0200
@@ -526,6 +526,19 @@
}
static usbd_status
+usbd_set_feature(usbd_device_handle dev, int feature)
+{
+ usb_device_request_t req;
+
+ req.bmRequestType = UT_WRITE;
+ req.bRequest = UR_SET_FEATURE;
+ USETW(req.wValue, 1);
+ USETW(req.wIndex, feature);
+ USETW(req.wLength, 0);
+ return (usbd_do_request(dev, req, 0));
+}
+
+static usbd_status
usbd_set_config(usbd_device_handle dev, int conf)
{
usb_device_request_t req;
@@ -995,7 +1008,14 @@
* We just did not find any drivers, that's all. The device is
* fully operational and not harming anyone.
*/
+
DPRINTF((usbd_probe_and_attach: generic attach failed\n));
+
+ if (dev-quirks-uq_flags UQ_FEATURE2) {
+ printf(%s: Enabling feature UHF_PORT_SUSPEND\n,
device_get_nameunit(parent));
+ usbd_set_feature(dev, UHF_PORT_SUSPEND);
+ }
+
return (USBD_NORMAL_COMPLETION);
}
--030008040502080503020600
Content-Type: text/plain;
name=patch-usb_quirks.h
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename=patch-usb_quirks.h
--- usb_quirks.h 2007-06-29 23:07:41.0 +0200
+++ usb_quirks.h-patched 2008-04-23 00:39:29.0 +0200
@@ -52,6 +52,7 @@
#define UQ_AU_NO_FRAC 0x0400 /* don't adjust for fractional samples */
#define UQ_AU_INP_ASYNC 0x0800 /* input is async despite claim of
adaptive */
#define UQ_BROKEN_BIDIR 0x2000 /* printer has broken bidir mode */
+#define UQ_FEATURE2 0x4000 /* requires the enabling of feature 2 */
#define UQ_OPEN_CLEARSTALL 0x04000 /* device needs clear endpoint stall */
#define UQ_HID_IGNORE 0x8000 /* device should be ignored by hid class */
#define UQ_KBD_IGNORE 0x00018000 /* device should be ignored by both kbd and
hid class */
--030008040502080503020600
Content-Type: text/plain;
name=patch-usb_quirks.c
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename=patch-usb_quirks.c
--- usb_quirks.c 2008-04-20 10:52:13.0 +0200
+++ usb_quirks.c-patched 2008-04-23 00:39:29.0 +0200
@@ -112,6 +112,8 @@
ANY, { UQ_KBD_IGNORE }},
{ USB_VENDOR_METAGEEK, USB_PRODUCT_METAGEEK_WISPY24X,
ANY, { UQ_KBD_IGNORE }},
+ { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E220,
+ ANY, { UQ_FEATURE2 }},
{ 0, 0, 0, { 0 } }
};
--030008040502080503020600
Content-Type: text/plain;
name=patch-ubsa.c
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename=patch-ubsa.c
--- ubsa.c 2008-04-12 13:23:21.0 +0200
+++ ubsa.c-patched 2008-04-23 00:39:29.0 +0200
@@ -236,6 +236,8 @@
{ USB_VENDOR_OPTION, USB_PRODUCT_OPTION_GT3GPLUS },
/* Huawei Mobile */
{ USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_MOBILE },
+ /* Huawei Mobile E220 */
+ { USB_VENDOR_HUAWEI, USB_PRODUCT_HUAWEI_E220 },
/* Qualcomm, Inc. ZTE CDMA */
{ USB_VENDOR_QUALCOMMINC, USB_PRODUCT_QUALCOMMINC_CDMA_MSM },
{ 0, 0 }
--030008040502080503020600--
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to [EMAIL PROTECTED]
