Re: usb device not recognised

2009-06-08 Thread Wojciech Puchar


sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled

and, later:

...
GEOM_LABEL: Label ufsid/4a259f5253bef8ae removed.
uhub2: port 2 reset failed
uhub2: port 2 reset failed
uhub2: port 2 reset failed
uhub2: port 2 reset failed
uhub2: port 2 reset failed
uhub2: port 2 reset failed
uhub2: port 2 reset failed
uhub2: port 2 reset failed
uhub2: port 2 reset failed
uhub2: port 2 reset failed
uhub2: port 2 reset failed


already here is a problem, not with device but usb controller/hub support.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: usb device not recognised

2009-06-07 Thread jdbca

   On Sáb Jun 6 14:42 , Wojciech Puch= ar sent:

  When the TL= -C300 is plugged in after boot, it produces the
 following console report:-= /span
 
  umass1: on uh= ub2
  (probe0:umass-sim1:1:0:0): TEST UNIT READY= . CDB: 0 0 0 0 0 0
  (probe0:umass-sim1:1:0:0): CAM Status: SCS= I Status Error
  (probe0:umass-sim1:1:0:0): SCSI Status: Ch= eck Condition
  (probe0:umass-sim1:1:0:0): NOT READY asc:3= a,0
  (probe0:umass-sim1:1:0:0): Medium not pres= ent
  (probe0:umass-sim1:1:0:0): Unretryable err= or
  da0 at umass-sim1 bus 1 target 0 lun 0
  da0: Removable Direct Access SCSI-0 device
  da0: 40.000MB/s transfers
  da0: 1900MB (3892224 512 byte sectors: 255= H 63S/T 242C)
 
 doesn't look like too big blocksize problem...
  but fails to create /dev/da0. Also, when i= t is plugged in, no
 other usb devices are recognised.
 
  Unplugging produces this:-
 
  umass1: at uhub2 port 2 (addr 2) disconnec= ted
  (da0:umass-sim1:1:0:0): Synchronize cache = failed, status ==
 0x39, scsi status == 0x0
  (da0:umass-sim1:1:0:0): lost device  (da0:umass-sim1:1:0:0): 
removing device en= try
  umass1: detached
 If it's Synchronize cache failed problem, then adding entry in
 umass.c will fix it, as with my olympus FE-20
 But it's rather not main problem. maybe some other quirk?
 look at possible quirks
 Many thanks for putting me on the right track.
 I played around with the quirks and found that it needs both these
 to creat= e the
 device and make it mountable:-
 NO_TEST_UNIT_READY | NO_SYNCHRONIZE_CACHE
 Works fine now
 Thanks
 _

   Área de Clientes Clix – Toda a gestão dos seus
   serviÃ= §os online!
   http://cliente.clix.pt/. ___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: usb device not recognised

2009-06-07 Thread Wojciech Puchar


  I played around with the quirks and found that it needs both these to 
create the
  device and make it mountable:-
  NO_TEST_UNIT_READY | NO_SYNCHRONIZE_CACHE

  Works fine now


please make patch with diff -u

diff -u usbdevs.orig usbdevs /tmp/patch.txt
diff -u umass.c.orig umass.c /tmp/patch.txt

and do sent-pr (by sent-pr program or FreeBSD webpage), describe a 
problem and attach /tmp/patch.txt


so maintainers can put this in FreeBSD sources.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: usb device not recognised

2009-06-07 Thread Reed Loefgren

Wojciech Puchar wrote:


  I played around with the quirks and found that it needs both 
these to create the

  device and make it mountable:-
  NO_TEST_UNIT_READY | NO_SYNCHRONIZE_CACHE

  Works fine now


please make patch with diff -u

diff -u usbdevs.orig usbdevs /tmp/patch.txt
diff -u umass.c.orig umass.c /tmp/patch.txt

and do sent-pr (by sent-pr program or FreeBSD webpage), describe a 
problem and attach /tmp/patch.txt


so maintainers can put this in FreeBSD sources.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to 
freebsd-questions-unsubscr...@freebsd.org


I just saw this post and need a link to the thread and a definition of 
the term played around with the quirks. I have a just-re-installed 
7.2-RELEASE system (a bad SCSI cable trashed the original geom mirror 
install) and dmesg mentions at boot:


sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled

and, later:

...
GEOM_LABEL: Label ufsid/4a259f5253bef8ae removed.
uhub2: port 2 reset failed
uhub2: port 2 reset failed
uhub2: port 2 reset failed
uhub2: port 2 reset failed
uhub2: port 2 reset failed
uhub2: port 2 reset failed
uhub2: port 2 reset failed
uhub2: port 2 reset failed
uhub2: port 2 reset failed
uhub2: port 2 reset failed
uhub2: port 2 reset failed


If I plug in a Lexar usb key I get:

Jun  7 19:27:24 bimbo kernel: uhub2: port 2 reset failed
Jun  7 19:27:56 bimbo last message repeated 30 times

The port number varies depending on which USB jack I have the cable 
plugged in to. My Canon Powershot A630 fails as well. As a probably 
unrelated aside, when trying to initialize and then talk to a serial 
interfaced temperature monitoring device, I get:


bimbo [103] [7:30pm] [/export/digitemp-3.4.0]$ ./digitemp_DS9097U -i 
-s/dev/cuad0

DigiTemp v3.4.0 Copyright 1996-2005 by Brian C. Lane
GNU Public License v2.0 - http://www.digitemp.com
Error 5: DS2480B Adapter Not Detected
Error 10: Read COM Failed
Error 10: Read COM Failed
Error 10: Read COM Failed
Error 10: Read COM Failed
Error 10: Read COM Failed
Error 10: Read COM Failed
Error 10: Read COM Failed
Error 10: Read COM Failed
Error 10: Read COM Failed

My point here is that all of this worked properly before the reinstall. 
The only difference was that the earlier 7.2 install was an upgraded 7.1 
install which was itself once 7.0. The new install is from the 7.2 
Release CD. It fails using GENERIC as well as my kernel. CPU is an AMD 
X3 720 black on an Asus M4A79T motherboard running i386.


This too might help somebody:

bimbo [106] [7:40pm] [/export/digitemp-3.4.0]$ dmesg | grep usb
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: OHCI (generic) USB controller on ohci0
usb0: USB revision 1.0
uhub0: ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0
usb1: OHCI version 1.0, legacy support
usb1: SMM does not respond, resetting
usb1: OHCI (generic) USB controller on ohci1
usb1: USB revision 1.0
uhub1: ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb1
usb2: EHCI version 1.0
usb2: companion controllers, 3 ports each: usb0 usb1
usb2: EHCI (generic) USB 2.0 controller on ehci0
usb2: USB revision 2.0
uhub2: ATI EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb2
usb3: OHCI version 1.0, legacy support
usb3: SMM does not respond, resetting
usb3: OHCI (generic) USB controller on ohci2
usb3: USB revision 1.0
uhub3: ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb3
usb4: OHCI version 1.0, legacy support
usb4: SMM does not respond, resetting
usb4: OHCI (generic) USB controller on ohci3
usb4: USB revision 1.0
uhub4: ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb4
usb5: EHCI version 1.0
usb5: companion controllers, 3 ports each: usb3 usb4
usb5: EHCI (generic) USB 2.0 controller on ehci1
usb5: USB revision 2.0
uhub5: ATI EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb5
usb6: OHCI version 1.0, legacy support
usb6: SMM does not respond, resetting
usb6: OHCI (generic) USB controller on ohci4
usb6: USB revision 1.0
uhub6: ATI OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb6
bimbo [107] [7:40pm] [/export/digitemp-3.4.0]$

Apologies for the shotgun, I'm pretty tired and frustrated.

r

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


usb device not recognised

2009-06-06 Thread jdbca
I have a Teclast TL-C300 usb media player which works fine with Slackware 12.2 
and Windows XP, but is not properly recognised by 
FreeBSD.
I have other usb devices, eg camera, which all work fine, so I am guessing that 
my config is OK, although I do see errors with 
these devices too.
According to kerneltrap, another Teclast device needed a patch in Linux to 
reduced the data transfer block size to make it work, 
so perhaps it needs a quirk for FreeBSD too.
Does anybody have experience of this device or recognise the symptoms?

I am running FreeBSD 7.2 and I am up to date with stable.

I have these entires in the kernel which are probably relevant:-
device  scbus
device  da
device  cd
device  pass
device  ses
device  atapicam
device  uhci
device  ohci
device  ehci
device  usb
device  ugen
device  uhid
device  ukbd
device  ulpt
device  umass
device  ums

If the TL-C300 is present at boot, boot freezes when it probes the device but 
resumes if the device is removed.

When the TL-C300 is plugged in after boot, it produces the following console 
report:-

umass1: RockChip ROCK MP3, class 0/0, rev 2.00/0.00, addr 2 on uhub2
(probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 
(probe0:umass-sim1:1:0:0): CAM Status: SCSI Status Error
(probe0:umass-sim1:1:0:0): SCSI Status: Check Condition
(probe0:umass-sim1:1:0:0): NOT READY asc:3a,0
(probe0:umass-sim1:1:0:0): Medium not present
(probe0:umass-sim1:1:0:0): Unretryable error
da0 at umass-sim1 bus 1 target 0 lun 0
da0: Teclast Digital  Player 1.00 Removable Direct Access SCSI-0 device 
da0: 40.000MB/s transfers
da0: 1900MB (3892224 512 byte sectors: 255H 63S/T 242C)

but fails to create /dev/da0. Also, when it is plugged in, no other usb devices 
are recognised.

Unplugging produces this:-

umass1: at uhub2 port 2 (addr 2) disconnected
(da0:umass-sim1:1:0:0): Synchronize cache failed, status == 0x39, scsi status 
== 0x0
(da0:umass-sim1:1:0:0): lost device
(da0:umass-sim1:1:0:0): removing device entry
umass1: detached

By contrast, when I plug in the camera, I get this report which also contains 
errors, but it does create the /dev entries and is 
mountable:-

umass1: DV USB Device, class 0/0, rev 1.10/1.00, addr 2 on uhub0
da0 at umass-sim1 bus 1 target 0 lun 0
da0: DV USB Device 1.00 Removable Direct Access SCSI-0 device 
da0: 1.000MB/s transfers
da0: 31MB (64000 512 byte sectors: 64H 32S/T 31C)
(probe0:umass-sim1:1:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0 
(probe0:umass-sim1:1:0:1): CAM Status: SCSI Status Error
(probe0:umass-sim1:1:0:1): SCSI Status: Check Condition
(probe0:umass-sim1:1:0:1): NOT READY asc:3a,0
(probe0:umass-sim1:1:0:1): Medium not present
(probe0:umass-sim1:1:0:1): Unretryable error
da1 at umass-sim1 bus 1 target 0 lun 1
da1: DV USB Device 1.00 Removable Direct Access SCSI-0 device 
da1: 1.000MB/s transfers
da1: Attempt to query device size failed: NOT READY, Medium not present

unplug camera:-

umass1: at uhub0 port 2 (addr 2) disconnected
(da0:umass-sim1:1:0:0): lost device
(da0:umass-sim1:1:0:0): removing device entry
(da1:umass-sim1:1:0:1): lost device
(da1:umass-sim1:1:0:1): removing device entry
umass1: detached

Cheers

DuncanB
 
Área de Clientes Clix – Toda a gestão dos seus serviços online! 
http://cliente.clix.pt/. ___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: usb device not recognised

2009-06-06 Thread Wojciech Puchar

When the TL-C300 is plugged in after boot, it produces the following console 
report:-

umass1: RockChip ROCK MP3, class 0/0, rev 2.00/0.00, addr 2 on uhub2
(probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe0:umass-sim1:1:0:0): CAM Status: SCSI Status Error
(probe0:umass-sim1:1:0:0): SCSI Status: Check Condition
(probe0:umass-sim1:1:0:0): NOT READY asc:3a,0
(probe0:umass-sim1:1:0:0): Medium not present
(probe0:umass-sim1:1:0:0): Unretryable error
da0 at umass-sim1 bus 1 target 0 lun 0
da0: Teclast Digital  Player 1.00 Removable Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: 1900MB (3892224 512 byte sectors: 255H 63S/T 242C)



doesn't look like too big blocksize problem...


but fails to create /dev/da0. Also, when it is plugged in, no other usb devices 
are recognised.

Unplugging produces this:-

umass1: at uhub2 port 2 (addr 2) disconnected
(da0:umass-sim1:1:0:0): Synchronize cache failed, status == 0x39, scsi status 
== 0x0
(da0:umass-sim1:1:0:0): lost device
(da0:umass-sim1:1:0:0): removing device entry
umass1: detached


If it's Synchronize cache failed problem, then adding entry in umass.c 
will fix it, as with my olympus FE-20


But it's rather not main problem. maybe some other quirk?
look at possible quirks
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: usb device not recognised

2009-06-06 Thread Wojciech Puchar

(probe0:umass-sim1:1:0:0): NOT READY asc:3a,0
(probe0:umass-sim1:1:0:0): Medium not present
(probe0:umass-sim1:1:0:0): Unretryable error
da0 at umass-sim1 bus 1 target 0 lun 0
da0: Teclast Digital  Player 1.00 Removable Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: 1900MB (3892224 512 byte sectors: 255H 63S/T 242C)

but fails to create /dev/da0. Also, when it is plugged in, no other usb devices 
are recognised.


maybe:

#   define NO_TEST_UNIT_READY   0x0001


try:

editing /usr/src/sys/dev/usb/usbdevs

and add definition for your device.

you may use usbdevs -v command to look at numbers:

 port 2 addr 2: full speed, power 500 mA, config 1, HUAWEI Mobile(0x1001),
 ^^^
product
HUAWEI Technologies(0x12d1), rev 0.00
^^
producer.


then edit umass.c and add new table entry like that:

{ USB_VENDOR_YOURVENDOR, USB_PRODUCT_YOURPRODUCT, RID_WILDCARD,
  UMASS_PROTO_SCSI | UMASS_PROTO_BBB,
  YOURQUIRKS
},


then compile the kernel, or maybe just umass module if it's not in 
your kernel. then check


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org