Re: USB
On Monday 12 March 2007 00:36, Rick Mullis wrote: > /usr/src/sys/sys/systm.h They defined msleep() like this: +#definemsleep(chan, mtx, pri, wmesg, timo) \ + _sleep((chan), &(mtx)->mtx_object, (pri), (wmesg), (timo)) Arg. Well, I think the new _sleep() has the same problem like the old one. It doesn't take Giant as a sleeping mutex argument. Try definition msleep() like this in /sys/dev/usb/usb_port.h: #undef msleep #define msleep(i,m,p,w,t) _sleep(i,(((m) == &Giant) ? NULL : &(m)->mtx_object),p,w,t) --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB error
On Monday 12 March 2007 00:15, Rick Mullis wrote: > Hi Hans, > > I have been using and testing your new usb and today I have been getting an > error. First of all I am using amd64 with the Intel DG965RY mainboard, dou > core 2 prcessor with 4 gb of ram. After discussing a problem with you, you > recommended I insert NULL in all of the files that have bus_setup_intr > which ended up being 3 files "ehci_pci.c, ohci_pci.c and uhci_pci.c" and > that fixed the problem until today when I svn the latest src from you and > the latest 7-current src and recompiled. Below is the last few lines before > error. > > cc -c -O -pipe -march=nocona -std=c99 -g -Wall -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline -Wcast-qual -Wundef -fformat-extensions -nostdinc -I- -I. > -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL > -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common > -finline-limit=8000 --param inline-unit-growth=100 --param > large-function-growth=1000 -mcmodel=kernel -mno-red-zone -mfpmath=387 > -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float > -fno-asynchronous-unwind-tables -ffreestanding -Werror > /usr/src/sys/dev/uart/uart_tty.c > cc -c -O -pipe -march=nocona -std=c99 -g -Wall -Wredundant-decls > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Winline -Wcast-qual -Wundef -fformat-extensions -nostdinc -I- -I. > -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL > -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common > -finline-limit=8000 --param inline-unit-growth=100 --param > large-function-growth=1000 -mcmodel=kernel -mno-red-zone -mfpmath=387 > -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float > -fno-asynchronous-unwind-tables -ffreestanding -Werror > /usr/src/sys/dev/usb/ehci.c > *** Error code 1 > Did you do things in this order: 1) cvsup 2) svn update 3) make S=../src package 4) make install 5) build new kernel --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "[EMAIL PROTECTED]"
USB error
Hi Hans, I have been using and testing your new usb and today I have been getting an error. First of all I am using amd64 with the Intel DG965RY mainboard, dou core 2 prcessor with 4 gb of ram. After discussing a problem with you, you recommended I insert NULL in all of the files that have bus_setup_intr which ended up being 3 files "ehci_pci.c, ohci_pci.c and uhci_pci.c" and that fixed the problem until today when I svn the latest src from you and the latest 7-current src and recompiled. Below is the last few lines before error. cc -c -O -pipe -march=nocona -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -fformat-extensions -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /usr/src/sys/dev/uart/uart_tty.c cc -c -O -pipe -march=nocona -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -fformat-extensions -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /usr/src/sys/dev/usb/ehci.c *** Error code 1 Stop in /usr/obj/usr/src/sys/MAIN. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Any and all help is, as always, greatly appreciated. Thanks, Rick ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with USB devices connecting to UHCI instead of EHCI
> From: Hans Petter Selasky <[EMAIL PROTECTED]> > Date: Sun, 11 Mar 2007 19:25:14 +0100 > > On Sunday 11 March 2007 02:04, Kevin Oberman wrote: > > If I load umass after plugging in a disk or flash fob, it will be > > connected as a UHCI device. If I load umass and then connect the device, > > it is properly connected as EHCI. When connected as a UHCI device, it is > > too slow to be useful. > > > > Looks like a race condition as the EHCI is the last USB device probed. I > > suspect that the disk is already connected to a UHCI device before an > > EHCI device is found. > > > > uhci0: port > > 0x1800-0x181f irq 11 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] > > uhci0: [ITHREAD] > > usb0: on uhci0 > > usb0: USB revision 1.0 > > uhub0: on usb0 > > uhub0: 2 ports with 2 removable, self powered > > uhci1: port > > 0x1820-0x183f irq 11 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] > > uhci1: [ITHREAD] > > usb1: on uhci1 > > usb1: USB revision 1.0 > > uhub1: on usb1 > > uhub1: 2 ports with 2 removable, self powered > > uhci2: port > > 0x1840-0x185f irq 11 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] > > uhci2: [ITHREAD] > > usb2: on uhci2 > > usb2: USB revision 1.0 > > uhub2: on usb2 > > uhub2: 2 ports with 2 removable, self powered > > uhci3: port > > 0x1860-0x187f irq 11 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] > > uhci3: [ITHREAD] > > usb3: on uhci3 > > usb3: USB revision 1.0 > > uhub3: on usb3 > > uhub3: 2 ports with 2 removable, self powered > > ehci0: mem 0xb000-0xb3ff > > irq 11 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] > > ehci0: [ITHREAD] > > usb4: EHCI version 1.0 > > usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 > > usb4: on ehci0 > > usb4: USB revision 2.0 > > uhub4: on usb4 > > uhub4: 8 ports with 8 removable, self powered > > > > Any idea if this is fixable? Not a huge problem, but an annoying > > one. Will the new USB system (hopefully coming soon) deal with this? > > It might have something to do with the probe order. Did you try the new USB > stack. I recommend you install it on 6-stable, because on 7-current it needs > some small patches to compile, due to some changes in the kernel API lately. Yes, I suspect the probe order is significant, but the only system I use USB devices on is my laptop and I really don't want to roll it back to stable. I can continue to work around it until you have a set of current patches for me to try. I'm really anxious to try out the new stack as I am hoping it will make USB behave better in terma of power management on my laptop. That's why i don't build USB into my kernel, but just load it when I need it. I don't normally read usb@, so I may drop you a note in a couple of weeks to see if the stack has been updated for current. Thanks! -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgp67M6s7ux5Z.pgp Description: PGP signature
Re: Problems with USB devices connecting to UHCI instead of EHCI
On Sunday 11 March 2007 21:19, Kevin Oberman wrote: > > From: Hans Petter Selasky <[EMAIL PROTECTED]> > > Date: Sun, 11 Mar 2007 19:25:14 +0100 > > > > On Sunday 11 March 2007 02:04, Kevin Oberman wrote: > > > If I load umass after plugging in a disk or flash fob, it will be > > > connected as a UHCI device. If I load umass and then connect the > > > device, it is properly connected as EHCI. When connected as a UHCI > > > device, it is too slow to be useful. > > > > > > Looks like a race condition as the EHCI is the last USB device probed. > > > I suspect that the disk is already connected to a UHCI device before an > > > EHCI device is found. > > > > > > uhci0: port > > > 0x1800-0x181f irq 11 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] > > > uhci0: [ITHREAD] > > > usb0: on uhci0 > > > usb0: USB revision 1.0 > > > uhub0: on usb0 > > > uhub0: 2 ports with 2 removable, self powered > > > uhci1: port > > > 0x1820-0x183f irq 11 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] > > > uhci1: [ITHREAD] > > > usb1: on uhci1 > > > usb1: USB revision 1.0 > > > uhub1: on usb1 > > > uhub1: 2 ports with 2 removable, self powered > > > uhci2: port > > > 0x1840-0x185f irq 11 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] > > > uhci2: [ITHREAD] > > > usb2: on uhci2 > > > usb2: USB revision 1.0 > > > uhub2: on usb2 > > > uhub2: 2 ports with 2 removable, self powered > > > uhci3: port > > > 0x1860-0x187f irq 11 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] > > > uhci3: [ITHREAD] > > > usb3: on uhci3 > > > usb3: USB revision 1.0 > > > uhub3: on usb3 > > > uhub3: 2 ports with 2 removable, self powered > > > ehci0: mem > > > 0xb000-0xb3ff irq 11 at device 29.7 on pci0 ehci0: > > > [GIANT-LOCKED] > > > ehci0: [ITHREAD] > > > usb4: EHCI version 1.0 > > > usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 > > > usb4: on ehci0 > > > usb4: USB revision 2.0 > > > uhub4: on usb4 > > > uhub4: 8 ports with 8 removable, self powered > > > > > > Any idea if this is fixable? Not a huge problem, but an annoying > > > one. Will the new USB system (hopefully coming soon) deal with this? > > > > It might have something to do with the probe order. Did you try the new > > USB stack. I recommend you install it on 6-stable, because on 7-current > > it needs some small patches to compile, due to some changes in the kernel > > API lately. > > Yes, I suspect the probe order is significant, but the only system I use > USB devices on is my laptop and I really don't want to roll it back to > stable. > > I can continue to work around it until you have a set of current patches > for me to try. I'm really anxious to try out the new stack as I am > hoping it will make USB behave better in terma of power management on my > laptop. That's why i don't build USB into my kernel, but just load it > when I need it. > > I don't normally read usb@, so I may drop you a note in a couple of > weeks to see if the stack has been updated for current. > If you install the SVN version of my USB stack, and you are running the latest 7-CURRENT, then you need to patch the following by hand: Insert a NULL argument, to all bus_setup_intr() functions you find under /sys/dev/usb/, like shown below ? error = bus_setup_intr(dev, sc->sc_irq_res, INTR_TYPE_TTY, - si_intr, sc, &ih); + NULL, si_intr, sc, &ih); That's it. Then it should compile. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[PATCH] Support for various CDMA-2000 USB-modems (Please, consider to commit)
Good day.
Some time ago i had post this as PR 109838
(http://www.freebsd.org/cgi/query-pr.cgi?pr=usb/109838)
but there is some problem: when i try to see it, i getting "No PRs
Matched Query" response all of the time, so i decide to post it here.
When we connecting any of this USB-modems/mobile phones (all of them
uses USB-to-COM interface cable):
- Pantech-Curitel HX-550C
- Pantech-Curitel HX-570B
- Pantech-Curitel HX-575B
- C-MOTECH CNU-550
- Ubiquam U-100
- Ubiquam U-105
- Ubiquam U-200
- RWT FCT-CDMA
and load all the needed modules (ucom/umodem/uplcom), we don't get nor
/dev/ttyU0, nor /dev/cuaU0. So, we can't dialing and get to internet.
All that we have it's a messages from kernel like this:
kernel: ucom0: data interface 1, has CM over data, has break
So, i've add quirks [UQ_ASSUME_CM_OVER_DATA] for all of this
phones/modems and it works well.
How to test:
1. Apply the patch attached
# cp usb_modems.patch /sys/dev/usb/
# cd /sys/dev/usb/
# patch < usb_modems.patch
2. Then rebuild kernel
# cd /usr/src
# make buildkernel && make installkernel && shutdown -r now
3. After reboot, plug in one of those modems.
4. Load needed kernel modules according table located on
http://happy-nation.by.ru/freebsd/cdma2000_modems_eng.pdf (ucom and
umodem are most common) - at this stage you will see that ttyU0 and
cuaU0 appeared in /dev.
5. Create /etc/ppp/ppp.conf like this (it was taken from
http://www.lissyara.su/?id=1311):
# cat /etc/ppp/ppp.conf
default:
set log Phase Chat LCP IPCP CCP tun command
disable pred1 deflate deflate24 protocomp acfcomp shortseq vj
deny pred1 deflate deflate24 protocomp acfcomp shortseq vj
set speed 115200
set timeout 160
enable dns
skylink:
set device /dev/ttyU0
set phone \#777
set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \
\"\" AT OK-AT-OK ATE1Q0 OK \
\\dATDT\\T TIMEOUT 40 CONNECT"
set login
set authname mobile
set authkey internet
set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0
add default HISADDR
6. Try to dial
# ppp -ddial skylink
That is all.
Please cc me in the response, because i don't subscribed on freebsd-usb@
--- /sys/dev/usb/usbdevs Wed Feb 14 19:57:15 2007
+++ usbdevs Thu Feb 22 01:20:57 2007
@@ -518,6 +518,7 @@
vendor IMAGINATION 0x149a Imagination Technologies
vendor CONCEPTRONIC 0x14b2 Conceptronic
vendor SILICONPORTALS 0x1527 Silicon Portals
+vendor UBIQUAM 0x1529 UBIQUAM Co., Ltd.
vendor PNY 0x154b PNY
vendor SOHOWARE 0x15e8 SOHOware
vendor UMAX 0x1606 UMAX
@@ -770,7 +771,8 @@
product CHICONY KB8933 0x0001 KB-8933 keyboard
/* CMOTECH products */
-product CMOTECH CDMAMODEM 0x5141 CMOTECH CDMA Technologies USB modem
+product CMOTECH CNU510 0x5141 CMOTECH CDMA Technologies USB modem
+product CMOTECH CNU550 0x5543 CDMA 2000 1xRTT/1xEVDO USB modem
/* Compaq products */
product COMPAQ PJB100 0x504a Personal Jukebox PJB100
@@ -806,6 +808,8 @@
product CTX EX1300 0x Ex1300 hub
/* Curitel products */
+product CURITEL HX550C 0x1101 CDMA 2000 1xRTT USB modem (HX-550C)
+product CURITEL HX57XB 0x2101 CDMA 2000 1xRTT USB modem (HX-570/575B)
product CURITEL PC5740 0x3701 Broadband wireless modem
/* Cypress Semiconductor products */
@@ -1444,6 +1448,7 @@
product PUTERCOM UPA100 0x047e USB-1284 BRIDGE
/* Qualcomm products */
+product QUALCOMM RWT_FCT0x3100 RWT FCT-CDMA 2000 1xRTT modem
product QUALCOMM CDMA_MSM 0x3196 CDMA Technologies MSM modem
product QUALCOMM2 CDMA_MSM 0x6000 CDMA Technologies MSM phone
@@ -1652,6 +1657,9 @@
/* TwinMOS */
product TWINMOS MDIV 0x1325 Memory Disk IV
+
+/* Ubiquam products */
+product UBIQUAM UALL 0x3100 CDMA 1xRTT USB Modem (U-100/105/200/300)
/* Ultima products */
product ULTIMA 1200UBPLUS 0x4002 1200 UB Plus scanner
--- /sys/dev/usb/usb_quirks.c Mon Jan 22 17:57:30 2007
+++ usb_quirks.c Thu Feb 22 01:17:08 2007
@@ -80,7 +80,12 @@
{ USB_VENDOR_SILICONPORTALS, USB_PRODUCT_SILICONPORTALS_YAPPHONE,
0x100, { UQ_AU_INP_ASYNC }},
{ USB_VENDOR_LOGITECH, USB_PRODUCT_LOGITECH_UN53B, ANY, { UQ_NO_STRINGS }},
- { USB_VENDOR_CMOTECH, USB_PRODUCT_CMOTECH_CDMAMODEM, ANY, { UQ_ASSUME_CM_OVER_DATA }},
+ { USB_VENDOR_CMOTECH, USB_PRODUCT_CMOTECH_CNU510, ANY, { UQ_ASSUME_CM_OVER_DATA }},
+ { USB_VENDOR_CMOTECH, USB_PRODUCT_CMOTECH_CNU550, ANY, { UQ_ASSUME_CM_OVER_DATA }},
+ { USB_VENDOR_CURITEL, USB_PRODUCT_CURITEL_HX550C, ANY, { UQ_ASSUME_CM_OVER_DATA }},
+ { USB_VENDOR_CURITEL, USB_PRODUCT_CURITEL_HX57XB, ANY, { UQ_ASSUME_CM_OVER_DATA }},
+ { USB_VENDOR_UBIQUAM, USB_PRODUCT_UBIQUAM_UALL, ANY, { UQ_ASSUME_CM_OVER_DATA }},
+ { USB_VENDOR_QUALCOMM, USB_PRODUCT_QUALCOMM_RWT_FCT, ANY, { UQ_ASSUME_CM_OVER_DATA }},
/* XXX These should have a revision number, but I don't know what they are. */
{ USB_VENDOR_HP, USB_PRODUCT_HP_895C, ANY, { UQ_BROKEN_BIDIR }},
{ USB_VENDOR_HP, USB_PRODUCT_HP_880C, ANY, { UQ_BROKEN_BIDIR }}
Re: Problems with USB devices connecting to UHCI instead of EHCI
On Sunday 11 March 2007 02:04, Kevin Oberman wrote: > If I load umass after plugging in a disk or flash fob, it will be > connected as a UHCI device. If I load umass and then connect the device, > it is properly connected as EHCI. When connected as a UHCI device, it is > too slow to be useful. > > Looks like a race condition as the EHCI is the last USB device probed. I > suspect that the disk is already connected to a UHCI device before an > EHCI device is found. > > uhci0: port > 0x1800-0x181f irq 11 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] > uhci0: [ITHREAD] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: on usb0 > uhub0: 2 ports with 2 removable, self powered > uhci1: port > 0x1820-0x183f irq 11 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] > uhci1: [ITHREAD] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: on usb1 > uhub1: 2 ports with 2 removable, self powered > uhci2: port > 0x1840-0x185f irq 11 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] > uhci2: [ITHREAD] > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: on usb2 > uhub2: 2 ports with 2 removable, self powered > uhci3: port > 0x1860-0x187f irq 11 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] > uhci3: [ITHREAD] > usb3: on uhci3 > usb3: USB revision 1.0 > uhub3: on usb3 > uhub3: 2 ports with 2 removable, self powered > ehci0: mem 0xb000-0xb3ff > irq 11 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] > ehci0: [ITHREAD] > usb4: EHCI version 1.0 > usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 > usb4: on ehci0 > usb4: USB revision 2.0 > uhub4: on usb4 > uhub4: 8 ports with 8 removable, self powered > > Any idea if this is fixable? Not a huge problem, but an annoying > one. Will the new USB system (hopefully coming soon) deal with this? It might have something to do with the probe order. Did you try the new USB stack. I recommend you install it on 6-stable, because on 7-current it needs some small patches to compile, due to some changes in the kernel API lately. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "[EMAIL PROTECTED]"
usb/110197: Sony PSP umass device does not detach from EHCI port
>Number: 110197 >Category: usb >Synopsis: Sony PSP umass device does not detach from EHCI port >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-usb >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Mar 11 18:20:03 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Calle Englund >Release:FreeBSD 6.2-STABLE i386 >Organization: >Environment: System: FreeBSD aftermath.home.discord.bofh.se 6.2-STABLE FreeBSD 6.2-STABLE #3: Fri Mar 9 19:02:51 CET 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AFTERMATH i386 The problem was also seen in at least FreeBSD 6.1 % cat /sys/i386/conf/AFTERMATH.diff --- GENERIC Fri Dec 29 18:34:50 2006 +++ AFTERMATH Fri Mar 9 17:01:15 2007 @@ -69,6 +69,7 @@ # ATA and ATAPI devices device ata +device atapicam device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives uhci0: port 0x48c0-0x48df irq 10 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x48e0-0x48ff irq 5 at d evice 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x4c00-0x4c1f irq 5 at d evice 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xa000-0xa3ff i rq 5 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered >Description: When a Sony Playstation Portable is detached from an EHCI USB port, the associated device tree lingers and that USB port is unresponsive until a device has been plugged into another USB port. Then the detach of the original PSP umass device tree occurs and the port again responds to devices being plugged into it. >How-To-Repeat: *** Enter USB Connection in PSP. PSP: Connect a USB cable. *** Plug PSP into USB port. PSP: USB Mode New lines in dmesg: umass0: Sony PSP Type A, rev 2.00/1.00, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 958MB (1963008 512 byte sectors: 64H 32S/T 958C) % usbdevs -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 powered port 2 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 powered port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x), Intel(0x), rev 1.00 port 1 powered port 2 addr 2: full speed, self powered, config 1, Bluetooth by hp(0x0086), ACTIONTEC(0x049f), rev 8.02 Controller /dev/usb3: addr 1: high speed, self powered, config 1, EHCI root hub(0x), Intel(0x), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered port 5 addr 2: high speed, self powered, config 1, PSP Type A(0x01c8), Sony(0x054c), rev 1.00 port 6 powered *** Unplug PSP from USB port. PSP: Connect a USB cable. Nothing new in dmesg. % usbdevs -v ... Controller /dev/usb3: addr 1: high speed, self powered, config 1, EHCI root hub(0x), Intel(0x), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered port 5 addr 2: high speed, self powered, config 1, product 0x01c8(0x01c8), vendor 0x054c(0x054c), rev 1.00 port 6 powered The port still reports a device present, but the Product/Vendor codes are not translated to text anymore. *** Plug PSP back into the same USB port. PSP: USB Mode Nothing new in dmesg. % usbdevs -v ... Controller /dev/usb3: addr 1: high speed, self powered, config 1, EHCI root hub(0x), Intel(0x), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered port 5 addr 2: high speed, self powered, config 1, product 0x01c8(0x01c8), vendor 0x054c(0x054c), rev 1.00 port 6 powered *** Unplug PSP and plug back into another USB port. PSP: Connect a USB cable. PSP: USB Mode. New lines in dmesg: umass1: Sony PSP Type A, rev 2.00/1.00, addr 3 umass0: at uhub3 port 5 (addr 2) disconnected <<< (da0:umass-sim0:0:0:0): lost device <<< (da0:umass-sim0:0:0:0): removing device entry <<< umass0: detached <<< da0 at umass-sim1 bus 1 target 0 lun 0 da0: Removable Direct Access S
Re: CanoScan N650U / xsane /FreeBSD 6.2-CURRENT
On Fri, Mar 09, 2007 at 02:52:33PM -0600, [EMAIL PROTECTED] wrote: > I am trying to get a Cannon CanoScan N 650U working on FreeBSD 6.2-CURRENT. > > The scanner SEEMS to be seen, but normal VS root shows a difference. > > As a mortal User: > > $ sane-find-scanner -q > found USB scanner (UNKNOWN vendor and product) at device /dev/uscanner0 > > > As root > lap# sane-find-scanner -q > found USB scanner (vendor=0x04a9, product=0x2206) at /dev/uscanner0 > lap# scanimage -L > > No scanners were identified. If you were expecting something different, > check that the scanner is plugged in, turned on and detected by the > sane-find-scanner tool (if appropriate). Please read the documentation > > > lap# kldstat > Id Refs AddressSize Name > 1 17 0xc040 714dc4 kernel > 22 0xc0b15000 22c48sound.ko > 31 0xc0b38000 9958 snd_uaudio.ko > 41 0xc0b42000 598bcacpi.ko > 52 0xc376b000 9000 ibcs2.ko > 61 0xc3776000 3000 ibcs2_coff.ko > 72 0xc3779000 16000linux.ko > 81 0xc39df000 3000 daemon_saver.ko > 91 0xc3dea000 6000 linprocfs.ko > lap# > > Xsane configs > > $ grep -v ^# /usr/local/etc/sane.d/plustek.conf | grep -v option > device /dev/uscanner0 > usb 0x04a9 0x2206 > $ grep plustek /usr/local/etc/sane.d/dll.conf > plustek > #plustek_pp > $ You should read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/scanners.html -- Marc ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "[EMAIL PROTECTED]"
