Re: Fujitsu P2000 (2110) USB Problem

On Saturday 24 August 2002 05:47 pm, Gordon Burditt,Here,11,817 249-4898 
wrote:
> >  I am having a problem getting any sort of USB device to work with my 
Fujitsu 
> >P2000 notebook.  The USB works correctly in window 2000 so I know that the 
> >hardware is ok.
> >  The problem is that I can plug in a USB device ie. a floppy drive and a 
> >little kernel message appears notifying me that it is plugged in, but then 
I 
> >am not able to mount it.  Then I try my USB Visor.  Plug it in press the 
> >button, device message shows up, but can't communicate with the device.  
Not 
> >being one to give up I recompiled my kernel for rio mp3 player support.  
> >installed rioutil and tryed again.  Plug it in, device shows up as rio0, 
but 
> >when I try to query information from it: rioutil -i.  It just hangs and I 
> >have to [ctl]-c it.
> >   I've pasted my dmesg below.  Is there anything else that I can send that 
> >would help?  I don't have any problems with coding if it comes to that.  
> >Thanks.
> 
> >umass0: NEC NEC USB UF000x, rev 1.10/1.21, addr 2
> >da0 at umass-sim0 bus 0 target 0 lun 0
> >da0: <NEC USB UF000x 1.21> Removable Direct Access SCSI-0 device
> >da0: 20KB/s transfers
> >da0: 1MB (2880 512 byte sectors: 2H 18S/T 80C)
> >umass0: Unsupported UFI command 0x08, 6 byte command should have been 
> >converted
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> This error suggests that you need the following line in /etc/sysctl.conf:
> kern.cam.da.no_6_byte=1
> (then reboot, or run sysctl -w kern.cam.da.no_6_byte=1  .)
> 
> It may not solve all your problems, but it did solve some I was
> having with flash card readers and solid-state USB disks.
> 
> 
> >da0: reading primary partition table: error reading fsbn 0
> >umass0: Unsupported UFI command 0x35
> >(da0:umass-sim0:0:0:0): Synchronize cache failed, status == 0x6, scsi 
status 
> >== 0x0
> 
> 						Gordon L. Burditt
> 
> 

Thanks, that worked for the floppy drive.  I can mount that fine now.  But I 
am still having problems with my USB devices.  From further testing I was 
able to figure out that after a reboot the first device that you plug in and 
it's first query for information seem to work fine.
1) Insert the USB floppy drive and mount it
2) I can read/write whatever just fine.
3) Unmount then disconnect it.
4) Insert the drive again and it is recongnized, but fails to create 
communicate with the device.
NOTE: If I kill the usbd, and restart it at this point I get a message 
/dev/usb: Device busy.
5) Try attaching other device, but nothing is recognized.
Now when I try with the Rio600 MP3 player the following happens, I have 
inserted  usb kernel debug messages at the point they appeared:
1) Insert rio, and it's recognized.
Aug 24 21:26:40 littleguy /kernel: uhub_explore: status change hub=1 port=2
Aug 24 21:26:40 littleguy /kernel: usbd_new_device bus=0xc09da000 port=2 
depth=1 lowspeed=0
Aug 24 21:26:40 littleguy /kernel: usbd_new_device: adding unit addr=2, 
rev=100, class=0, subclass=0, protocol=0, maxpacket=16, len=18, ls=0
Aug 24 21:26:40 littleguy /kernel: usbd_new_device: new dev (addr 2), 
dev=0xc1019600, parent=0xc0e7e280
Aug 24 21:26:40 littleguy /kernel: usbd_probe_and_attach: trying device 
specific drivers
Aug 24 21:26:40 littleguy /kernel: usbd_probe_and_attach: no device specific 
driver found
Aug 24 21:26:40 littleguy /kernel: usbd_probe_and_attach: looping over 1 
configurations
Aug 24 21:26:40 littleguy /kernel: usbd_set_config_index: (addr 2) attr=0x40, 
selfpowered=1, power=0
Aug 24 21:26:40 littleguy /kernel: usbd_set_config_index: set config 1
Aug 24 21:26:40 littleguy /kernel: urio0: Diamond Multimedia Diamond 
Multimedia  Digital Audio Player, rev 1.00/1.00, addr 2
2) Run "rioutil -i" to view device stats:
littleguy# rioutil -i
Name: Rio 600
Volume: 8
Repeat: Off
Equilizer: Rap
Backlight: 2 secs
Programmed to Playlist: 0
Firmware Version: 1.56
Memory units: 1
Memory unit 0: Internal Flash Memory
Free: 5.6 MB (32.0 MB Total)
Used: 26.3 MB in 6 files
[#########################################         ] 82.3 %
Total Time: 00:19:04
3) Run "rioutil -i" again to view the stats again, this and subsequent times I 
get garbage for the first part only:
littleguy# rioutil -i
Name: ÷ó¿¿
Volume: 1
Repeat: Off
Equilizer: (null)
Backlight: (null)
Programmed to Playlist: 40
Firmware Version: 240.98
Memory units: 1
Memory unit 0: Internal Flash Memory
Free: 5.6 MB (32.0 MB Total)
Used: 26.3 MB in 0 files
[#########################################         ] 82.3 %
Total Time: 00:00:00
4) Unplug device.
Aug 24 21:34:54 littleguy /kernel: uhub_explore: C_PORT_ENABLED
Aug 24 21:34:54 littleguy /kernel: uhub_explore: device addr=2 disappeared on 
port 2
Aug 24 21:35:04 littleguy /kernel: urio0: at uhub0 port 2 (addr 2) 
disconnected
Aug 24 21:35:04 littleguy /kernel: urio0: disconnected
Aug 24 21:35:04 littleguy /kernel: urio0: detached
5) Plugin in device again, and it's not recognized.
Aug 24 21:35:20 littleguy /kernel: uhub_explore: status change hub=1 port=2
Aug 24 21:35:20 littleguy /kernel: usbd_new_device bus=0xc09da000 port=2 
depth=1 lowspeed=0
6) Unplug device
Aug 24 21:35:36 littleguy /kernel: usbd_new_device: addr=2, getting first desc 
failed
Aug 24 21:35:36 littleguy /kernel: usbd_remove_device: 0xc1019600
Aug 24 21:35:36 littleguy /kernel: uhub_explore: usb_new_device failed, 
error=TIMEOUT
Aug 24 21:35:36 littleguy /kernel: uhub0: device problem, disabling port 2

-- 
Anish Mistry


To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-mobile" in the body of the message