Bug 122992 - [umass] [patch] MotoROKR Z6 Phone not recognised by umass as USB disk.
Summary: [umass] [patch] MotoROKR Z6 Phone not recognised by umass as USB disk.
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: usb (show other bugs)
Version: 6.1-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-usb mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-22 17:40 UTC by Charles Neubauer
Modified: 2018-01-03 05:16 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Charles Neubauer 2008-04-22 17:40:00 UTC
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.

Fix: 

The GNU/Linux guys have a patch.  Check out Gentoo in particular.
How-To-Repeat: Connect a MotoROKR Z6 phone to a FreeBSD system using the provided cable.
Comment 1 Marcin Cieslak 2008-04-22 19:07:35 UTC
The bug mentioned is this:

http://bugs.gentoo.org/attachment.cgi?id=145870

It would be nice if you could provide your real email address - without 
feedback we will need to close this bug as invalid.

-- 
               << Marcin Cieslak // saper@system.pl >>
Comment 2 Charles Neubauer 2008-04-27 13:39:44 UTC
Marcin Cieslak <saper@SYSTEM.PL> said:

> It would be nice if you could provide your real email address - without 
> feedback we will need to close this bug as invalid.

O.K.  This is my e-mail address.  What can be done about the bug?  
Upgrading FreeBSD is currently not an option for me.

-- 
gemellus@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org
Comment 3 Marcin Cieslak 2008-04-27 15:45:38 UTC
Can you install misc/udesc_dump port and attach the output once the 
phone is connected?

-- 
               << Marcin Cieslak // saper@system.pl >>
Comment 4 gemellus2 2008-05-31 15:51:17 UTC
Installing udesc_dump doesn't help.  It gives the single line output:

/dev/ugen0: No such file

Please note that the system console lists a

umass0: Motorola USB...

line, i.e., a umass0 line is attached, not a ugen0.  However, the pseudo-SCSI devices do not appear.
Comment 5 okrg 2008-07-30 09:45:37 UTC
I got the same problem under 7.0-RELEASE.

From dmesg:

Jul 30 08:53:26 kws kernel: usb0: <UHCI (generic) USB controller> on uhci0
Jul 30 08:53:26 kws kernel: usb0: USB revision 1.0
Jul 30 08:53:26 kws kernel: uhub0: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
Jul 30 08:53:26 kws kernel: usb1: <UHCI (generic) USB controller> on uhci1
Jul 30 08:53:26 kws kernel: usb1: USB revision 1.0
Jul 30 08:53:26 kws kernel: uhub1: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
Jul 30 08:53:26 kws kernel: usb2: <UHCI (generic) USB controller> on uhci2
Jul 30 08:53:26 kws kernel: usb2: USB revision 1.0
Jul 30 08:53:26 kws kernel: uhub2: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2
Jul 30 08:53:26 kws kernel: usb3: <UHCI (generic) USB controller> on uhci3
Jul 30 08:53:26 kws kernel: usb3: USB revision 1.0
Jul 30 08:53:26 kws kernel: uhub3: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb3
Jul 30 08:53:26 kws kernel: usb4: EHCI version 1.0
Jul 30 08:53:26 kws kernel: usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
Jul 30 08:53:26 kws kernel: usb4: <Intel 82801GB/R (ICH7) USB 2.0 controller> on ehci0
Jul 30 08:53:26 kws kernel: usb4: USB revision 2.0
Jul 30 08:53:26 kws kernel: uhub4: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb4

After Z6 connecting I see following:

ul 30 09:24:09 kws kernel: umass0: <Motorola Inc. MS, class 0/0, rev 2.00/1.01, addr 2> on uhub4
Jul 30 09:24:09 kws kernel: umass0:0:0:-1: Attached to scbus0
Jul 30 09:24:09 kws root: Unknown USB device: vendor 0x22b8 product 0x6426 bus uhub4

kws# usbdevs -vd
Controller /dev/usb0:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00
  uhub0
 port 1 powered
 port 2 powered
Controller /dev/usb1:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00
  uhub1
 port 1 powered
 port 2 powered
Controller /dev/usb2:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00
  uhub2
 port 1 powered
 port 2 powered
Controller /dev/usb3:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00
  uhub3
 port 1 powered
 port 2 powered
Controller /dev/usb4:
addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), Intel(0x0000), rev 1.00
  uhub4
 port 1 powered
 port 2 powered
 port 3 addr 2: high speed, power 500 mA, config 1, MS(0x6426), Motorola Inc.(0x22b8), rev 1.01
   umass0
 port 4 powered
 port 5 powered
 port 6 powered
 port 7 powered
 port 8 powered

kws# camcontrol devlist -v
scbus0 on umass-sim0 bus 0:

So, umass0 line and scbus0 are attached but no daX devices.
Comment 6 okrg 2008-08-14 07:56:32 UTC
This bug also described in 

http://linux.derkeiler.com/Mailing-Lists/Kernel/2008-03/msg04505.html

I tried to apply quirks:

--- usbdevs.orig	2008-01-08 01:12:45.000000000 +0200
+++ usbdevs	2008-07-30 13:55:59.000000000 +0300
@@ -1695,6 +1695,7 @@
 product MOTOROLA2 E398		0x4810	E398 Mobile Phone
 product MOTOROLA2 USBLAN	0x600c	USBLAN
 product MOTOROLA2 USBLAN2	0x6027	USBLAN
+product MOTOROLA2 MS		0x6426	MS
 
 /* MultiTech products */
 product MULTITECH ATLAS		0xf101	MT5634ZBA-USB modem

--- umass.c.orig	2007-07-05 08:26:08.000000000 +0300
+++ umass.c	2008-08-06 15:00:00.000000000 +0300
@@ -544,6 +544,10 @@
 	  UMASS_PROTO_SCSI | UMASS_PROTO_BBB,
 	  FORCE_SHORT_INQUIRY | NO_INQUIRY_EVPD | NO_GETMAXLUN
 	},
+	{ USB_VENDOR_MOTOROLA2, USB_PRODUCT_MOTOROLA2_MS, RID_WILDCARD,
+	  UMASS_PROTO_SCSI | UMASS_PROTO_BBB,
+	  NO_INQUIRY | READ_CAPACITY_OFFBY1
+	},
 	{ USB_VENDOR_MSYSTEMS, USB_PRODUCT_MSYSTEMS_DISKONKEY, RID_WILDCARD,
 	  UMASS_PROTO_SCSI | UMASS_PROTO_BBB,
 	  IGNORE_RESIDUE | NO_GETMAXLUN | RS_NO_CLEAR_UA

I get following messages:

Aug  6 15:51:26 kws kernel: pass1 at umass-sim0 bus 0 target 0 lun 1
Aug  6 15:51:26 kws kernel: (da0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR
Aug  6 15:51:26 kws kernel: (da0:umass-sim0:0:0:0): Retrying Command
Aug  6 15:51:26 kws kernel: (da0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR
Aug  6 15:51:26 kws kernel: (da0:umass-sim0:0:0:0): Retrying Command
Aug  6 15:51:26 kws kernel: (da0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR
Aug  6 15:51:26 kws kernel: (da0:umass-sim0:0:0:0): Retrying Command
Aug  6 15:51:26 kws kernel: (da0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR
Aug  6 15:51:26 kws kernel: (da0:umass-sim0:0:0:0): Retrying Command
Aug  6 15:51:26 kws kernel: (da0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR
Aug  6 15:51:26 kws kernel: (da0:umass-sim0:0:0:0): error 5
Aug  6 15:51:26 kws kernel: (da0:umass-sim0:0:0:0): Retries Exausted
Aug  6 15:51:26 kws kernel: (da0:umass-sim0:0:0:0): removing device entry
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): Request completed with CAM_REQ_CMP_ERR
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): Retrying Command
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): Request completed with CAM_REQ_CMP_ERR
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): Retrying Command
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): Request completed with CAM_REQ_CMP_ERR
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): Retrying Command
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): Request completed with CAM_REQ_CMP_ERR
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): Retrying Command
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): Request completed with CAM_REQ_CMP_ERR
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): error 5
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): Retries Exausted
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): got CAM status 0x4
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): fatal error, failed to attach to device
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): lost device
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): Request completed with CAM_REQ_CMP_ERR
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): Retrying Command
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): Request completed with CAM_REQ_CMP_ERR
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): Retrying Command
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): Request completed with CAM_REQ_CMP_ERR
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): Retrying Command
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): Request completed with CAM_REQ_CMP_ERR
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): Retrying Command
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): Request completed with CAM_REQ_CMP_ERR
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): error 5
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): Retries Exausted
Aug  6 15:51:26 kws kernel: (da1:umass-sim0:0:0:1): removing device entry

After unplugging my phone seems connected to PC until reboot.
Unfortunately I have not any idea about BULK_IGNORE_TAG porting
Comment 7 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:56 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped