Re: Why my USB keyboard doesn't generate scancodes?
On Wednesday 30 January 2013 09:28:14 Yuri wrote: On 01/29/2013 09:52, Hans Petter Selasky wrote: Please include dmesg from when you plug the device into the USB port. Here is the log for disconnecting and connecting again. Yuri That part looks OK. What is printed in dmesg with ukbd.debug enabled when you press a key or two. And also try NumLock. --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: Why my USB keyboard doesn't generate scancodes?
On 01/30/2013 00:33, Hans Petter Selasky wrote: What is printed in dmesg with ukbd.debug enabled when you press a key or two. And also try NumLock. I have hw.usb.ukbd.debug=15 and nothing is printed in dmesg. Based on my previous dtrace log, no key click messages reach ukbd driver at all. This is the reason nothing gets logged. This keyboard only has 2 buttons, and NumLock isn't among them. I think the buttons are supposed to be PgUp/PgDown. Yuri ___ 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: Why my USB keyboard doesn't generate scancodes?
On Wednesday 30 January 2013 09:56:21 Yuri wrote: On 01/30/2013 00:33, Hans Petter Selasky wrote: What is printed in dmesg with ukbd.debug enabled when you press a key or two. And also try NumLock. I have hw.usb.ukbd.debug=15 and nothing is printed in dmesg. Based on my previous dtrace log, no key click messages reach ukbd driver at all. This is the reason nothing gets logged. This keyboard only has 2 buttons, and NumLock isn't among them. I think the buttons are supposed to be PgUp/PgDown. Hi, I see what is going on now. Your keyboard is endpoint 0x81 and no events are reported here. Instead those key events are part of the mouse protocol, 0x82, and it is currently not supported that a mouse can generate key-events. However, it might be that those keys are mapped into some axis. Try to enable hw.usb.ums.debug=15 instead. Can you also try to dump the other HID descriptors: usbconfig -d X.Y do_request 0x81 0x06 0x2200 0 0x100 usbconfig -d X.Y do_request 0x81 0x06 0x2200 1 0x100 usbconfig -d X.Y do_request 0x81 0x06 0x2200 2 0x100 --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: Why my USB keyboard doesn't generate scancodes?
On 01/30/2013 01:10, Hans Petter Selasky wrote: On Wednesday 30 January 2013 09:56:21 Yuri wrote: On 01/30/2013 00:33, Hans Petter Selasky wrote: What is printed in dmesg with ukbd.debug enabled when you press a key or two. And also try NumLock. I have hw.usb.ukbd.debug=15 and nothing is printed in dmesg. Based on my previous dtrace log, no key click messages reach ukbd driver at all. This is the reason nothing gets logged. This keyboard only has 2 buttons, and NumLock isn't among them. I think the buttons are supposed to be PgUp/PgDown. Hi, I see what is going on now. Your keyboard is endpoint 0x81 and no events are reported here. Instead those key events are part of the mouse protocol, 0x82, and it is currently not supported that a mouse can generate key-events. However, it might be that those keys are mapped into some axis. Try to enable hw.usb.ums.debug=15 instead. Can you also try to dump the other HID descriptors: usbconfig -d X.Y do_request 0x81 0x06 0x2200 0 0x100 usbconfig -d X.Y do_request 0x81 0x06 0x2200 1 0x100 usbconfig -d X.Y do_request 0x81 0x06 0x2200 2 0x100 Here is what is printed from the keyboard click: ums_intr_callback: sc=0xfe02f497d000 actlen=5 ums_intr_callback: data = 16 00 00 27 00 00 00 00 ums_intr_callback: sc=0xfe02f497d000 actlen=5 ums_intr_callback: data = 16 00 00 00 00 00 00 00 Here are the other HID descriptors: # usbconfig -d 1.2 do_request 0x81 0x06 0x2200 0 0x100 REQUEST = 0x05 0x01 0x09 0x06 0xa1 0x01 0x05 0x08 0x19 0x01 0x29 0x03 0x15 0x00 0x25 0x01 0x75 0x01 0x95 0x03 0x91 0x02 0x95 0x05 0x91 0x01 0x05 0x07 0x1a 0xe0 0x00 0x2a 0xe7 0x00 0x95 0x08 0x81 0x02 0x75 0x08 0x95 0x01 0x81 0x01 0x19 0x00 0x2a 0x91 0x00 0x26 0xff 0x00 0x95 0x06 0x81 0x00 0xc0)%u*u* # usbconfig -d 1.2 do_request 0x81 0x06 0x2200 1 0x100 REQUEST = 0x05 0x01 0x09 0x02 0xa1 0x01 0x05 0x01 0x09 0x02 0xa1 0x02 0x85 0x1a 0x09 0x01 0xa1 0x00 0x05 0x09 0x19 0x01 0x29 0x05 0x95 0x05 0x75 0x01 0x15 0x00 0x25 0x01 0x81 0x02 0x75 0x03 0x95 0x01 0x81 0x01 0x05 0x01 0x09 0x30 0x09 0x31 0x95 0x02 0x75 0x10 0x16 0x01 0x80 0x26 0xff 0x7f 0x81 0x06 0xa1 0x02 0x85 0x12 0x09 0x48 0x95 0x01 0x75 0x02 0x15 0x00 0x25 0x01 0x35 0x01 0x45 0x04 0xb1 0x02 0x85 0x1a 0x09 0x38 0x35 0x00 0x45 0x00 0x95 0x01 0x75 0x10 0x16 0x01 0x80 0x26 0xff 0x7f 0x81 0x06 0xc0 0xa1 0x02 0x85 0x12 0x09 0x48 0x75 0x02 0x15 0x00 0x25 0x01 0x35 0x01 0x45 0x04 0xb1 0x02 0x35 0x00 0x45 0x00 0x75 0x04 0xb1 0x01 0x85 0x1a 0x05 0x0c 0x95 0x01 0x75 0x10 0x16 0x01 0x80 0x26 0xff 0x7f 0x0a 0x38 0x02 0x81 0x06 0xc0 0xc0 0xc0 0xc0 0x05 0x0c 0x09 0x01 0xa1 0x01 0x05 0x01 0x09 0x02 0xa1 0x02 0x85 0x1f 0x05 0x0c 0x0a 0x38 0x02 0x95 0x01 0x75 0x10 0x16 0x01 0x80 0x26 0xff 0x7f 0x81 0x06 0x85 0x17 0x06 0x00 0xff 0x0a 0x06 0xff 0x0a 0x0f 0xff 0x15 0x00 0x25 0x01 0x35 0x01 0x45 0x04 0x95 0x02 0x75 0x02 0xb1 0x02 0x0a 0x04 0xff 0x35 0x00 0x45 0x00 0x95 0x01 0x75 0x01 0xb1 0x02 0x75 0x03 0xb1 0x01 0xc0 0x85 0x16 0x05 0x0c 0x19 0x00 0x2a 0xff 0x03 0x95 0x01 0x75 0x10 0x15 0x00 0x26 0xff 0x03 0x81 0x00 0x06 0x00 0xff 0x1a 0x01 0xfd 0x2a 0xff 0xfd 0x15 0x01 0x26 0xff 0x00)u%u01uHu%5E85EuHu%5E5Euu88u%5Eu5Euu*u* # usbconfig -d 1.2 do_request 0x81 0x06 0x2200 2 0x100 REQUEST = 0x05 0x0c 0x09 0x01 0xa1 0x01 0x85 0x20 0x06 0x00 0xff 0x15 0x00 0x26 0xff 0x00 0x75 0x08 0x95 0x12 0x0a 0x0a 0xfa 0xb1 0x02 0x85 0x21 0x06 0x00 0xff 0x15 0x00 0x25 0x01 0x75 0x01 0x95 0x10 0x1a 0x10 0xfa 0x2a 0x1f 0xfa 0x81 0x02 0x85 0x28 0x06 0x00 0xff 0x1a 0x10 0xfa 0x2a 0x1f 0xfa 0xb1 0x02 0x85 0x22 0x06 0x00 0xff 0x15 0x00 0x26 0xff 0x00 0x75 0x08 0x95 0x1a 0x0a 0x0a 0xfa 0xb1 0x02 0x85 0x23 0x06 0x00 0xff 0x0a 0x0a 0xfa 0xb1 0x02 0x85 0x24 0x06 0x00 0xff 0x95 0x1f 0x0a 0x0a 0xfa 0xb1 0x02 0x85 0x25 0x06 0x00 0xff 0x0a 0x0a 0xfa 0xb1 0x02 0x85 0x26 0x06 0x00 0xff 0x0a 0x0a 0xfa 0xb1 0x02 0x85 0x27 0x06 0x00 0xff 0x0a 0x0a 0xfa 0x81 0x02 0x85 0x14 0x06 0x00 0xff 0x15 0x00 0x25 0x03 0x75 0x02 0x95 0x01 0x0a 0x01 0xfe 0x81 0x02 0x75 0x06 0x81 0x01 0x85 0x04 0x06 0x00 0xff 0x15 0x00 0x25 0x03 0x75 0x02 0x95 0x01 0x0a 0x01 0xfe 0x81 0x02 0x75 0x06 0x81 0x01 0xc0 0x05 0x0c 0x09 0x01 0xa1 0x01 0x85 0x07 0x05 0x0c 0x19 0x00 0x2a 0xff 0x03 0x95 0x01 0x75 0x10 0x15 0x00 0x26 0xff 0x03 0x81 0x00 0x05 0x07 0x19 0x00 0x29 0xff 0x75 0x08 0x26 0xff 0x00 0x81 0x00 0x81 0x01 0x06 0x00 0xff 0x0a 0x03 0xfe 0x0a 0x04 0xfe 0x75 0x01 0x95 0x02 0x25 0x01 0x81 0x02 0x0a 0x05 0xff 0x95 0x01 0x75 0x05 0x25 0x1f 0x81 0x02 0x75 0x01 0x81 0x01 0x1a 0x01 0xfd 0x2a 0xff 0xfd 0x15 0x01 u!%u*(*u#$%'%uu%uu*u)uu%u%u* ___ 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: Why my USB keyboard doesn't generate scancodes?
On Wednesday 30 January 2013 10:17:21 Yuri wrote: On 01/30/2013 01:10, Hans Petter Selasky wrote: On Wednesday 30 January 2013 09:56:21 Yuri wrote: On 01/30/2013 00:33, Hans Petter Selasky wrote: What is printed in dmesg with ukbd.debug enabled when you press a key or two. And also try NumLock. I have hw.usb.ukbd.debug=15 and nothing is printed in dmesg. Based on my previous dtrace log, no key click messages reach ukbd driver at all. This is the reason nothing gets logged. This keyboard only has 2 buttons, and NumLock isn't among them. I think the buttons are supposed to be PgUp/PgDown. Hi, I see what is going on now. Your keyboard is endpoint 0x81 and no events are reported here. Instead those key events are part of the mouse protocol, 0x82, and it is currently not supported that a mouse can generate key-events. However, it might be that those keys are mapped into some axis. Try to enable hw.usb.ums.debug=15 instead. Can you also try to dump the other HID descriptors: usbconfig -d X.Y do_request 0x81 0x06 0x2200 0 0x100 usbconfig -d X.Y do_request 0x81 0x06 0x2200 1 0x100 usbconfig -d X.Y do_request 0x81 0x06 0x2200 2 0x100 Here is what is printed from the keyboard click: ums_intr_callback: sc=0xfe02f497d000 actlen=5 ums_intr_callback: data = 16 00 00 27 00 00 00 00 ums_intr_callback: sc=0xfe02f497d000 actlen=5 ums_intr_callback: data = 16 00 00 00 00 00 00 00 The length was a bit too short. Can you re-run? usbconfig -d X.Y do_request 0x81 0x06 0x2200 1 0x300 --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: Why my USB keyboard doesn't generate scancodes?
On 01/30/2013 01:25, Hans Petter Selasky wrote: usbconfig -d X.Y do_request 0x81 0x06 0x2200 1 0x300 # usbconfig -d 1.2 do_request 0x81 0x06 0x2200 1 0x300 REQUEST = 0x05 0x01 0x09 0x02 0xa1 0x01 0x05 0x01 0x09 0x02 0xa1 0x02 0x85 0x1a 0x09 0x01 0xa1 0x00 0x05 0x09 0x19 0x01 0x29 0x05 0x95 0x05 0x75 0x01 0x15 0x00 0x25 0x01 0x81 0x02 0x75 0x03 0x95 0x01 0x81 0x01 0x05 0x01 0x09 0x30 0x09 0x31 0x95 0x02 0x75 0x10 0x16 0x01 0x80 0x26 0xff 0x7f 0x81 0x06 0xa1 0x02 0x85 0x12 0x09 0x48 0x95 0x01 0x75 0x02 0x15 0x00 0x25 0x01 0x35 0x01 0x45 0x04 0xb1 0x02 0x85 0x1a 0x09 0x38 0x35 0x00 0x45 0x00 0x95 0x01 0x75 0x10 0x16 0x01 0x80 0x26 0xff 0x7f 0x81 0x06 0xc0 0xa1 0x02 0x85 0x12 0x09 0x48 0x75 0x02 0x15 0x00 0x25 0x01 0x35 0x01 0x45 0x04 0xb1 0x02 0x35 0x00 0x45 0x00 0x75 0x04 0xb1 0x01 0x85 0x1a 0x05 0x0c 0x95 0x01 0x75 0x10 0x16 0x01 0x80 0x26 0xff 0x7f 0x0a 0x38 0x02 0x81 0x06 0xc0 0xc0 0xc0 0xc0 0x05 0x0c 0x09 0x01 0xa1 0x01 0x05 0x01 0x09 0x02 0xa1 0x02 0x85 0x1f 0x05 0x0c 0x0a 0x38 0x02 0x95 0x01 0x75 0x10 0x16 0x01 0x80 0x26 0xff 0x7f 0x81 0x06 0x85 0x17 0x06 0x00 0xff 0x0a 0x06 0xff 0x0a 0x0f 0xff 0x15 0x00 0x25 0x01 0x35 0x01 0x45 0x04 0x95 0x02 0x75 0x02 0xb1 0x02 0x0a 0x04 0xff 0x35 0x00 0x45 0x00 0x95 0x01 0x75 0x01 0xb1 0x02 0x75 0x03 0xb1 0x01 0xc0 0x85 0x16 0x05 0x0c 0x19 0x00 0x2a 0xff 0x03 0x95 0x01 0x75 0x10 0x15 0x00 0x26 0xff 0x03 0x81 0x00 0x06 0x00 0xff 0x1a 0x01 0xfd 0x2a 0xff 0xfd 0x15 0x01 0x26 0xff 0x00 0x75 0x08 0x81 0x00 0x81 0x01 0x85 0x1c 0x06 0x00 0xff 0x0a 0x25 0xff 0x15 0x00 0x25 0x04 0x75 0x08 0x95 0x01 0x81 0x02 0x0a 0x26 0xff 0x75 0x10 0x15 0x00 0x27 0xff 0xff 0x00 0x00 0x81 0x02 0xc0)u%u01uHu%5E85EuHu%5E5Euu88u%5Eu5Euu*u*u%%uu' ___ 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: Why my USB keyboard doesn't generate scancodes?
On Wednesday 30 January 2013 10:27:36 Yuri wrote: On 01/30/2013 01:25, Hans Petter Selasky wrote: usbconfig -d X.Y do_request 0x81 0x06 0x2200 1 0x300 Hi, Your HID descriptor is decoded like this: Report descriptor: Collection type=Application page=Generic_Desktop usage=Mouse Collection type=Logical page=Generic_Desktop usage=Mouse Collection type=Physical page=Generic_Desktop usage=Pointer Input rid=26 size=1 count=1 page=Button usage=Button_1, logical range 0..1 Input rid=26 size=1 count=1 page=Button usage=Button_2, logical range 0..1 Input rid=26 size=1 count=1 page=Button usage=Button_3, logical range 0..1 Input rid=26 size=1 count=1 page=Button usage=Button_4, logical range 0..1 Input rid=26 size=1 count=1 page=Button usage=Button_5, logical range 0..1 Input rid=26 size=3 count=1 page=0x usage=0x Const Array, logical range 0..1 Input rid=26 size=16 count=1 page=Generic_Desktop usage=X, logical range -32767..32767 Input rid=26 size=16 count=1 page=Generic_Desktop usage=Y, logical range -32767..32767 Collection type=Logical page=Generic_Desktop usage=Y Feature rid=18 size=2 count=1 page=Generic_Desktop usage=Resolution_Multiplier, logical range 0..1, physical range 1..4 Input rid=26 size=16 count=1 page=Generic_Desktop usage=Wheel, logical range -32767..32767 End collection Collection type=Logical page=Generic_Desktop usage=Wheel Feature rid=18 size=2 count=1 page=Generic_Desktop usage=Resolution_Multiplier, logical range 0..1, physical range 1..4 Feature rid=18 size=4 count=1 page=0x usage=0x Const Array, logical range 0..1 Input rid=26 size=16 count=1 page=Consumer usage=AC_Pan, logical range -32767..32767 End collection End collection End collection End collection Collection type=Application page=Consumer usage=Consumer_Control Collection type=Logical page=Generic_Desktop usage=Mouse Input rid=31 size=16 count=1 page=Consumer usage=AC_Pan, logical range -32767..32767 Feature rid=23 size=2 count=1 page=Microsoft usage=0xff06, logical range 0..1, physical range 1..4 Feature rid=23 size=2 count=1 page=Microsoft usage=0xff0f, logical range 0..1, physical range 1..4 Feature rid=23 size=1 count=1 page=Microsoft usage=0xff04, logical range 0..1 Feature rid=23 size=3 count=1 page=0x usage=0x Const Array, logical range 0..1 End collection Input rid=22 size=16 count=1 page=Consumer usage=Unassigned Array, logical range 0..1023 Input rid=22 size=8 count=1 page=Microsoft usage=0xfd01 Array, logical range 1..255 Input rid=22 size=8 count=1 page=0x usage=0x Const Array, logical range 1..255 Input rid=28 size=8 count=1 page=Microsoft usage=0xff25, logical range 0..4 Input rid=28 size=16 count=1 page=Microsoft usage=0xff26, logical range 0..65535 End collection Total input size 10 bytes Total output size 0 bytes Total feature size 2 bytes Work for you: RID=22 (0x16) is the one you are receiving. This is a microsoft specific extension to the HID class. I don't have time to look at this right now, but if you can get documentation for this HID usage, then we could map it to a mouse button at least. Else press all the buttons on your mouse while recording USB trace information. Then reverse engineer the values, make a nice table and I can implement it for you in the ums driver. --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: Plugging out Microsoft Nano Tranceiver (USB mouse) causes PS2 keyboard to cease functioning
I found the cause of this problem. Due to the bug in Xorg it unloads the keyboard driver when it gets signal from hald that keyboard is disconnected, even though there is still another keyboard that is hooked up to kbdmux. Looks like Xorg code assumes that there can only be one keyboard and isn't aware of kbdmux. This was when hald is enabled (by default), and ServerFlags section in xorg.conf looked like this: Section ServerFlags Option AllowEmptyInput yes EndSection When I changed this section to this: Section ServerFlags Option AutoAddDevices False EndSection keyboard doesn't get affected, but mouse disappears for good when unplugged and plugged back, since (I guess) Xorg ignores ums0 device errors. I filed the following PRs with Xorg: https://bugs.freedesktop.org/show_bug.cgi?id=60069 https://bugs.freedesktop.org/show_bug.cgi?id=60070 Yuri ___ 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: Plugging out Microsoft Nano Tranceiver (USB mouse) causes PS2 keyboard to cease functioning
Al 30/01/2013 12:14, En/na Yuri ha escrit: I found the cause of this problem. Due to the bug in Xorg it unloads the keyboard driver when it gets signal from hald that keyboard is disconnected, even though there is still another keyboard that is hooked up to kbdmux. Looks like Xorg code assumes that there can only be one keyboard and isn't aware of kbdmux. This was when hald is enabled (by default), and ServerFlags section in xorg.conf looked like this: Section ServerFlags Option AllowEmptyInput yes EndSection When I changed this section to this: Section ServerFlags Option AutoAddDevices False EndSection keyboard doesn't get affected, but mouse disappears for good when unplugged and plugged back, since (I guess) Xorg ignores ums0 device errors. I filed the following PRs with Xorg: https://bugs.freedesktop.org/show_bug.cgi?id=60069 https://bugs.freedesktop.org/show_bug.cgi?id=60070 Yuri ___ 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 Take a look at uhidd. I had the same problem a few time ago and because of it I switched to it. Perhaps will do fine for your setup. Regards, Gustau -- Salut i força, Gustau --- Prou top-posting : http://ca.wikipedia.org/wiki/Top-posting Stop top-posting : http://en.wikipedia.org/wiki/Posting_style O O O Gustau Pérez i Querol O O O Unitat de Gestió dels departaments O O O Matemàtica Aplicada IV i Enginyeria Telemàtica Universitat Politècnica de Catalunya Edifici C3 - Despatx S101-B UPC Campus Nord UPC C/ Jordi Girona, 1-3 08034 - Barcelona ___ 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
*****SPAM***** RE: usb/175551: Seagate 2TB USB extern hard disk have errors with freeBSD
Hello Hans Petter, thank you for your response. I want answer your questions - sorry for the late reply: 1) Does the drive have separate power connected? A: Yes 2) Have you tried using the disk at USB 2.0 by disabling USB 3.0 in the BIOS A: I used for this a very old PC, a Hewlett-Packard HP Vectra VL60 with Intel Pentium III (Copermine) 733Mhz / 256MB RAM / Mainboard D8611-60001 Board-S/N:FR02632024 / PhoenixBOIS 4.0 Release6.0.L / 1985-2000 Hewellt Packard Rev, Version: HY.01.07 (15 Jan 2002) It has no USB 3.0, nor can boot from USB. 3) Have you tried setting hw.usb.umass.throttle to 1,4 or 16, which is available in 9-stable, when options USB_DEBUG is enable. A: No - I have not known that. But I believe that my pc is more to slow than to fast. 4) The CAM layer hang you are experiencing is possibly fixed in 10-current. - fine, I will give it a try when 10-current becomes 10-release. Thank you for give me the information that it is a CAM layer hang - whatever this is. So it is not my fault. I now used another (older) external 320 GB USB hard drive. With that I get no problems (making partitions, formatting,..) With best regards, Harald Langner _ Dipl.-Ing. (FH) Harald E. Langner - Software-Developer - eMail: mailto:harald.lang...@web.de Url: http://www.swdevil.de http://www.langner.net Phone: +49 (69) 383 575 Telefax: +49 (69) 3877 8692 Mobile: +49 (179) 617 90 80 Address: Auf der Beun, No. 20 D - 65 933 Frankfurt at Main EUROPE (Germany) -Original Message- From: Hans Petter Selasky [mailto:hsela...@c2i.net] Sent: Friday, January 25, 2013 11:33 PM To: freebsd-usb@freebsd.org Cc: Harald Langner; freebsd-gnats-sub...@freebsd.org Subject: Re: usb/175551: Seagate 2TB USB extern hard disk have errors with freeBSD On Thursday 24 January 2013 23:11:48 Harald Langner wrote: Number: 175551 Category: usb Synopsis: Seagate 2TB USB extern hard disk have errors with freeBSD Confidential: no Severity: non-critical Priority: low Responsible:freebsd-usb State: open Quarter: Keywords: Date-Required: Class: sw-bug Submitter-Id: current-users Arrival-Date: Thu Jan 24 22:20:00 UTC 2013 Closed-Date: Last-Modified: Originator: Harald Langner Release:9.1 Release Organization: Environment: FreeBSD haraldlangner.de 9.1-RELEASE FreeBSD 9.1-RELEASE #0: Wed Jan 9 18:13:51 CET 2013 r...@haraldlangner.de:/usr/obj/usr/src/sys/GENERIC i386 Description: it seems to be a driver sw-bug I had tried to use an external Seagate 2 TB USB 3.0 hard disk, and want to format the third partition on it with FreeBSD. But I had have no look. So I step to the forum to get help. But no help was possible. It seems to be a hardware problem between this Seagate Plus Desktop Drive: http://www.seagate.com/external-hard-drives/desktop-hard-drives/backup -plu s-desk/ and freeBSD. The last poster in the forum http://forums.freebsd.org/showthread.php?t=36938 commend me to post a problem report - so I want to do here. I had try different things (see the post above). Everey time the USB-Disk hangs up. On Windows I got no problems with this Seagate USB drive. I have tried serval time to format a bevore created partition with freeBSD - no look: # newfs /dev/da0s3 /dev/da0s3: 267264.0MB (547356656 sectors) block size 32768, fragment size 4096 using 362 cylinder groups of 740.00MB, 23680 blks, 47360 inodes. super-block backups (for fsck -b #) at: 192, 1515712, 3031232, 4546752, 6062272, 7577792, 9093312, 10608832, 12124352, 13639872, 15155392, 16670912, 18186432, 19701952, 21217472, 22732992, 24248512, 25764032, 27279552, 28795072, 30310592, 31826112, 33341632, 34857152, 36372672, 37888192, 39403712, 40919232, 42434752, 43950272, 45465792, 46981312, 48496832, 50012352, 51527872, 53043392, 54558912, 56074432, 57589952, 59105472, 60620992, ---Here it hangs - and I have to switch of the PC. I thing I give up with this Seagte USB device. I had also created a FAT32 partition (in the 3. Partition as described in the post) with a second Windows PC. Copy some data on it and try to mount it with the freeBSD PC. # mount -t msdosfs -o large /dev/da0s3 /mnt/bckup Same Problem - it hangs: Here are the error message that cames up, when it hangs, on console: (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 c8 32 5d 28 0 0 8 0 (da0:umass-sim0:0:0:0): CAM status: CCB reques completed with an error (da0:umass-sim0:0:0:0): Retrying command ugen0.2: Seagate at usbus0 (disconnected) umass0: at uhub0, port 1, addr 2 (disconnected) (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 c8 32 5d 28 0 0 8 0 (da0:umass-sim0:0:0:0): CAM status: CCB reques completed with an error (da0:umass-sim0:0:0:0): Retrying command (da0:umass-sim0:0:0:0): READ(10). CDB: 28 0 c8 32 5d 28 0 0 8 0 (da0:umass-sim0:0:0:0):
Re: Why my USB keyboard doesn't generate scancodes?
On 01/30/2013 01:40, Hans Petter Selasky wrote: Work for you: RID=22 (0x16) is the one you are receiving. This is a microsoft specific extension to the HID class. I don't have time to look at this right now, but if you can get documentation for this HID usage, then we could map it to a mouse button at least. Else press all the buttons on your mouse while recording USB trace information. Then reverse engineer the values, make a nice table and I can implement it for you in the ums driver. So the keyboard signal comes to the mouse endpoint. One possible solution is to have a quirk in ums driver that would post the event to the corresponding ukbd instance. Since these are really the keyboard signals. Microsoft makes some of the best mice today (IMO, based on the research of what's available from all vendors). That's why I want FreeBSD to support their mice better. I will do some research, also will try to partially reverse-engineer the protocol. It might be something in their protocol that makes keyboard signals be piped into the mouse pipe. Yuri ___ 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/175703: Re: usb/175551: Seagate 2TB USB extern hard disk have errors with freeBSD
Old Synopsis: *SPAM* FW: usb/175551: Seagate 2TB USB extern hard disk have errors with freeBSD New Synopsis: Re: usb/175551: Seagate 2TB USB extern hard disk have errors with freeBSD State-Changed-From-To: open-closed State-Changed-By: linimon State-Changed-When: Thu Jan 31 07:33:49 UTC 2013 State-Changed-Why: Misfiled followup to usb/175551usb/175551usb/175551usb/175551usb/175551usb/175551usb/175551usb/175551usb/175551; content migrated. Responsible-Changed-From-To: gnats-admin-freebsd-usb Responsible-Changed-By: linimon Responsible-Changed-When: Thu Jan 31 07:33:49 UTC 2013 Responsible-Changed-Why: http://www.freebsd.org/cgi/query-pr.cgi?pr=175703 ___ 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
