this is driving me nuts: i have EXACTLY the same image written via dd to USB Stick:

SanDisk Ultra USB 3.0 32GB SDCZ48-032G

it works with Model: BM171026162B 

     but with Model: BM160825364B

it gives me this error that leads nowhere?

"device descriptor error read 64 error -110 -71 unable to enumerate usb device - device not accepting address"

enter image description here

for details: http://linux-workshops.de/ideal-linux-stick/

am i assuming this is a "defect" or change in hardware of the stick that makes it unusable?

is the missing module: ehci-orion the problem?

does it need to be compiled into the kernel? (i guess)


  • Can you do a binary comparison of full drive images? One of the sticks can be faulty. And the downvoter is a troll. – ajeh May 20 '18 at 0:41
  • Thanks for your help - as you can see on this picture - i have 4 sticks (two of each model-version) and 2 sticks work 2 sticks fail: linux-workshops.de/wp-content/uploads/2018/05/… (Model: BM171026162B works, Model: BM160825364B comes with the error seen in the black and white screenshot) – canoodle May 21 '18 at 21:01
  • this stick does not work: lsusb -v|grep San Bus 003 Device 006: ID 0781:5581 SanDisk Corp. Ultra idVendor 0x0781 SanDisk Corp. iManufacturer 1 SanDisk lsusb -v -d 0781:5581 2c2 < Bus 003 Device 008: ID 0781:5581 SanDisk Corp. Ultra --- > Bus 003 Device 009: ID 0781:5581 SanDisk Corp. Ultra 16c16 < iSerial 3 4C530001220830110261 --- > iSerial 3 4C530001181014123401 84c84 < Device Status: 0x0000 --- > Device Status: 0x000c 85a86,87 > U1 Enabled > U2 Enabled – canoodle May 22 '18 at 13:40
  • update: the version/model (fake SanDisk?) BM160825364B does not work. BM171026162B works! BM161125735B works! BM180126162B WORKS TOO! – canoodle Jul 23 '18 at 16:56

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.