DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD General

OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 21st July 2018
acampbell acampbell is offline
Real Name: Anthony Campbell
Shell Scout
 
Join Date: Sep 2014
Location: London, UK
Posts: 138
Default Kindle USB "device probem"

I posted about mounting a kindle last year but I'm starting a new thread because this is a different problem on a different desktop (Dell Optiplex 3020).

When I plug in the kindle,it seems to be recognized at first and it does charge. But I can't mount the device and there is a dmesg entry (repeated multiple times) saying there is a device problem.

Here is the relevant part of dmesg and also the output of disklabel.

dmesg:
uhidev3 at uhub0 port 5 configuration 1 interface 0 "vendor 0x1949 USB Charger" rev 2.00/2.00 addr 5
uhidev3: iclass 3/0
uhid2 at uhidev3: input=1, output=0, feature=0
uhid2 detached
uhidev3 detached
umass0 at uhub0 port 5 configuration 1 interface 0 "vendor 0x1949 Internal Storage" rev 2.00/4.01 addr 5
umass0: using SCSI over Bulk-Only
scsibus4 at umass0: 2 targets, initiator 0
scsibus4 detached
umass0 detached
uhub0: device problem, disabling port 5

disklabel:
# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: WDC WD5000AAKX-7
duid: b4afcc40682f0dc2
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 60801
total sectors: 976773168
boundstart: 64
boundend: 976768065
drivedata: 0

16 partitions:
# size offset fstype [fsize bsize cpg]
a: 2097152 64 4.2BSD 2048 16384 12958 # /
b: 8714560 2097216 swap # none
c: 976773168 0 unused
d: 8388608 10811776 4.2BSD 2048 16384 12958 # /tmp
e: 24769152 19200384 4.2BSD 2048 16384 12958 # /var
f: 4194304 43969536 4.2BSD 2048 16384 12958 # /usr
g: 2097152 48163840 4.2BSD 2048 16384 12958 # /usr/X11R6
h: 104862624 50260992 4.2BSD 2048 16384 12958 # /usr/local
i: 12594976 155123616 4.2BSD 2048 16384 12958 # /usr/obj
j: 251674272 167718592 4.2BSD 2048 16384 12958 # /home
Reply With Quote
  #2   (View Single Post)  
Old 21st July 2018
acampbell acampbell is offline
Real Name: Anthony Campbell
Shell Scout
 
Join Date: Sep 2014
Location: London, UK
Posts: 138
Default

After some more experiments, I find that I can mount a different Kindle (Paperwhite). The problem is specific to the Oasis. I'm continuing to experiment.
Reply With Quote
  #3   (View Single Post)  
Old 21st July 2018
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 7,977
Default

  1. The "device problem" message is produced by /usr/src/sys/dev/usb/uhub.c.
  2. This source code module has not been revised since release 6.2 (revision 1.90, April 2017).
  3. The message is produced when the device returns an error to the driver when the driver attempts to obtain device information and set a new device address on the bus.
  4. There is a UHUB_DEBUG flag for this source code module which could be enabled in a custom kernel.
If you don't happen to have the source code handy, here's a link to the module.
Reply With Quote
  #4   (View Single Post)  
Old 21st July 2018
acampbell acampbell is offline
Real Name: Anthony Campbell
Shell Scout
 
Join Date: Sep 2014
Location: London, UK
Posts: 138
Default

Thanks very much, Iggimi; illuminating, as usual. It was very useful to know that the module had not changed recently.

Encouraged by this, I had another go at the Oasis and found getting it to be recognised depended on the exact sequence of steps. I needed to connect the USB lead first and then to put the Kindle to sleep and wake it up again. A bit odd, but it works.
Reply With Quote
  #5   (View Single Post)  
Old 11th September 2018
acampbell acampbell is offline
Real Name: Anthony Campbell
Shell Scout
 
Join Date: Sep 2014
Location: London, UK
Posts: 138
Default

I'm coming back to this because the solution I posted last time turned out not to be the full answer. I still found both my kindles not being recognised most of the time. But I think this time I have got a solution: after I do a hard reset on the computer (turn the power off complately for about 30 sec.) the device is recognsed correctly. I've now done this several times and it seems to be reliable.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
SDL2 not working in netbsd - "no available video device" billy_bazooka Programming 8 19th September 2022 01:24 PM
Fresh installation 6.1.2 amd64 freezes in the line "root device" divel NetBSD Installation and Upgrading 2 22nd November 2013 07:11 PM
"no root device found" while installing kondziq FreeBSD Installation and Upgrading 4 29th November 2011 10:01 AM
System stops booting after "GEOM_MIRROR: Force device gm0 start due to timeout." indienick FreeBSD General 1 25th March 2010 09:46 PM
Fixed "xinit" after _7 _8, "how" here in case anyones' "X" breaks... using "nvidia" jb_daefo Guides 0 5th October 2009 09:31 PM


All times are GMT. The time now is 04:28 PM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick