USB Problems
Hello list! I have an external HDD connected with usb from dmesg i get this umass0: Generic External, class 0/0, rev 2.00/2.10, addr 4 on usbus5 umass0: SCSI over Bulk-Only; quirks = 0x4000 umass0:7:0:-1: Attached to scbus7 da0 at umass-sim0 bus 0 scbus7 target 0 lun 0 da0: Generic External 2.10 Fixed Direct Access SCSI-4 device da0: 40.000MB/s transfers da0: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C) df -hi say this Filesystem SizeUsed Avail Capacity iused ifree %iused Mounted on /dev/da0.eli 916G385G531G42% 53k 61M0% /usr/home/bernt/usbdisk dmesg pid 83024 (dd), uid 1001 inumber 2 on /usr/home/bernt/usbdisk: out of inodes softdep_waitidle: Failed to flush worklist for 0xff0008ab82f0 What is going on? I can cd to the disk but not copy to or from the disc. A reboot fix the problem but I think it should not be that way. umount -f /dev/da0.eli umount: unmount of /usr/home/bernt/usbdisk failed: Device busy geli stop /dev/da0.eli geli: No such device: /dev/da0.eli ls -l /dev/da* crw-r- 1 root operator0, 176 15 Apr 01:10 /dev/da0 ___ 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
Can't install 7.0-RC3 on dell dimension 3100 (usb problems)
Hello, I am unable to boot (and much less install) FreeBSD on a Dell Dimension3100 computer, apparently due to some usb problems. here's the error message snip sio0: configured irq 4 not in bitmap of probed irqs sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs sio0: port may not be enabled sio0: at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio0: [ITHREAD] sio1: configured irq 3 not in bitmap of probed irqs sio1: port may not be enabled usb1: controller halted uhub1: device problem (IOERROR) disabling port 1 snip then the system continues to boot normally and I am greeted by sysinstall. However the keyboard (and all other usb devices) no longer functions, rendering the system unusable. I tried to install 7.0-RC3 but this problem seems to affects other versions as well. I found an unsolved PR from 2006 (!) in which several users have reported similar issues: http://www.freebsd.org/cgi/query-pr.cgi?pr=100746 Is there some way to fix this? Thanks in advance for your help. Pak _ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
7.0 RC2 usb problems
I just installed 7.0 RC2 on a brand new Dell - dual processor dual core Intel (so four processors), and I'm losing the keyboard and mouse after taking certain actions. For example, I started setting up X (Xorg --configure) and then launched it (X -config /root/xorg.conf-new), and when I get to the GUI the mouse and keyboard are gone. Sometimes I can restore functionality by unplugging the devices and then plugging them back in. This is happening in the console as well, not just in the GUI. I've fetched the latest sources using cvsup. Will rebuilding the kernel solve this problem? Is this a known issue? usbhidctl shows ums0, ums1, ukbd0 and ukbd1 to be busy. [EMAIL PROTECTED] ~]# usbhidctl -a -f /dev/ums0 usbhidctl: /dev/ums0: Device busy [EMAIL PROTECTED] ~]# usbhidctl -a -f /dev/ums1 usbhidctl: /dev/ums1: Device busy [EMAIL PROTECTED] ~]# usbhidctl -a -f /dev/ukbd ukbd0 ukbd1 [EMAIL PROTECTED] ~]# usbhidctl -a -f /dev/ukbd0 usbhidctl: /dev/ukbd0: Device busy [EMAIL PROTECTED] ~]# usbhidctl -a -f /dev/ukbd1 usbhidctl: /dev/ukbd1: Device busy This is what I see after unplugging both devices and plugging them in to different usb receptacles. usbdevs addr 1: UHCI root hub, Intel addr 2: product 0x2105, vendor 0x413c addr 3: product 0x4d15, vendor 0x0461 addr 1: UHCI root hub, Intel addr 1: EHCI root hub, Intel addr 1: UHCI root hub, Intel addr 1: UHCI root hub, Intel addr 1: UHCI root hub, Intel addr 3: product 0x2105, vendor 0x413c addr 2: product 0x4d15, vendor 0x0461 addr 1: EHCI root hub, Intel FreeBSD utd65257.utdallas.edu 7.0-RC2-p1 FreeBSD 7.0-RC2-p1 #0: Tue Feb 12 22:23:33 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 grep usb /var/run/dmesg.boot usb0: UHCI (generic) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0 usb1: UHCI (generic) USB controller on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb1 usb2: waiting for BIOS to give up control usb2: EHCI version 1.0 usb2: wrong number of companions (3 != 2) usb2: companion controllers, 2 ports each: usb0 usb1 usb2: EHCI (generic) USB 2.0 controller on ehci0 usb2: USB revision 2.0 uhub2: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb2 usb3: UHCI (generic) USB controller on uhci2 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb3 usb4: UHCI (generic) USB controller on uhci3 usb4: USB revision 1.0 uhub4: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb4 usb5: UHCI (generic) USB controller on uhci4 usb5: USB revision 1.0 uhub5: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb5 usb6: waiting for BIOS to give up control usb6: timed out waiting for BIOS usb6: EHCI version 1.0 usb6: companion controllers, 2 ports each: usb3 usb4 usb5 usb6: EHCI (generic) USB 2.0 controller on ehci1 usb6: USB revision 2.0 uhub6: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb6 Any clues or help would be appreciated. -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB Problems with Scanjet 3400c
On Wed, Nov 16, 2005 at 11:05:56AM +0100, Blue Raccoon wrote: Roland, Joe, According to the SANE site their backend should provide 'complete' support. NIASH is required, but since 'niash' is an entry in the SANE config file I assume it is incorporated. My apologies; but I'll have to plead ignorance at this point...I simply don't know how to address this. Blue, you may wish to query the freebsd-multimedia list, if you have not already; you could also try the sane lists, and I think it would be advisable to ask the maintainer of the sane-backends on FreeBSD what he (or she) thinks. The Makefile for sane-backends has an address for [EMAIL PROTECTED]; I don't know that he is the current maintainer, but I'd bet someone on the multimedia list will know who is currently handling that port. Best of luck, Joe -- .sig is .tired. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB Problems with Scanjet 3400c
I have to be honest: this OS has made me appreciate XP a bit more. I spent a couple of nights on my sound card, even more on the 8 buttons of my mouse, another night on the printer, this afternoon on the usb stick and way too much time on the scanner. I think I will save the NVIDIA drivers for Christmas and simply give the camera a miss (after I have checked out gphoto). If there is anyone @ freebsd-questions with a working Scanjet 3400c I certainly would like to hear about it. Joe, Roland - Thanks for your help. If I ever figure it out you'll be the first to know. - Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
USB Problems with Scanjet 3400c
Hi, I am VERY new to FreeBSD and am having serious problems setting up my HP Scanjet 3400c. I installed the SANE back-end and it cannot find any scanners. I don't think SANE is to blame though, because the dmesg command shows (among other things) this: uscanner0: Hew product 0x0405, rev 1.00/0.00, addr 2 uscanner0: setting config no failed device_attach: uscanner0 attach returned 6 uhub0: port 2, set config at addr 2 failed uhub0: device problem (STALLED), disabling port 2 There is no point in loading the scanner from the command line, because 'kldload uscanner' brings up: kldload: can't load uscanner: File exists I compiled a kernel (just to see if I could), but the GENERIC kernel also chokes on the scanner. I did include device usb device uhci device ohci device uscanner in my kernel though. I am running FreeBSD 6.0 (release) on a 4 year old PC (900 Mhz Pentium). And the scanner is fine, by the way (No problems with XP). I don't have a clue and would appreciate it if someone could help me out here, or point me in the right direction. thanks in advance, Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB Problems with Scanjet 3400c, from: freebsd-questions Digest, Vol 113, Issue 7
On Tue, Nov 15, 2005 at 04:46:10PM +, [EMAIL PROTECTED] wrote: 20. USB Problems with Scanjet 3400c (Blue Raccoon) -- Message: 20 Date: Tue, 15 Nov 2005 15:35:53 +0100 From: Blue Raccoon [EMAIL PROTECTED] Subject: USB Problems with Scanjet 3400c To: freebsd-questions@freebsd.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii Hi, I am VERY new to FreeBSD and am having serious problems setting up my HP Scanjet 3400c. I installed the SANE back-end and it cannot find any scanners. So I take it the above means that sane-find-scanner returns no information on your scanner, and scanimage -L will also fail? (BTW: you may need some sort of frontend AKA GUI; something like the Sane Project's frontend, or XSane's frontend). I just checked /usr/local/etc/sane.d/ and there seems to be no backend for this scanner, IFF the backend for this model of 3400 is sane-niash[1]. In dll.conf, there is a line for niash; I suggest trying to put this after the niash in the dll.conf file: :/dev/uscanner0 so that you have this line: niash::/dev/uscanner0 then reboot, to see if it works. You can read about it in the man page for dll.conf, sane-dll. I think this might work, as there is an entry in /usr/local/lib/sane/: ~ $: grep -i niash /usr/local/lib/sane/* Binary file /usr/local/lib/sane/libsane-niash.so matches Binary file /usr/local/lib/sane/libsane-niash.so.1 matches But I dont' know, since my HP is a 2200C. I don't think SANE is to blame though, because the dmesg command shows (among other things) this: uscanner0: Hew product 0x0405, rev 1.00/0.00, addr 2 uscanner0: setting config no failed device_attach: uscanner0 attach returned 6 uhub0: port 2, set config at addr 2 failed uhub0: device problem (STALLED), disabling port 2 And you know that your USB port works, because you use XP on this machine, correct? There is no point in loading the scanner from the command line, because 'kldload uscanner' brings up: kldload: can't load uscanner: File exists You will also need to set up device bits, in /etc/devfs.conf: #Scanner permuscanner0 the perms you wish to have, like 0660 or 0666 I compiled a kernel (just to see if I could), but the GENERIC kernel also chokes on the scanner. I did include device usb device uhci device ohci device uscanner That should be all you need. in my kernel though. I am running FreeBSD 6.0 (release) on a 4 year old PC (900 Mhz Pentium). And the scanner is fine, by the way (No problems with XP). I suggest here: http://xsane.org/ and here: http://www.sane-project.org/. [1] The Sane Project indicates that it is new; so perhaps that backend has not yet made it into the distribution? I don't know... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB Problems with Scanjet 3400c
Joe, Thanks for your tips. On Tuesday 15 November 2005 18:37, Joe Altman wrote: I suggest trying to put this after the niash in the dll.conf file: :/dev/uscanner0 I did, but it makes no difference. And you know that your USB port works, because you use XP on this machine, correct? Correct. You will also need to set up device bits, in /etc/devfs.conf: #Scanner permuscanner0 the perms you wish to have, like 0660 or 0666 Perms I wish to have? I'm afraid that means nothing to me. I suggest here: http://xsane.org/ and here: http://www.sane-project.org/. They have a patch (source code) that can alter the SANE source to become Scanjet3400c compatible. I may have to look into that, but I also found this in the patch documentation: before trying to make your scanner work, call: $ less /proc/bus/usb/devices if your scanning device is not listed by name, you probably have a 3400C or 4300C and difficulties with the kernel-usb. The forum will give you information, how to change the kernel code, to make your scanner work. My /proc/ is totally empty. It is not clear what forum they are referring to. Even more frightening is this, in the SANE documentation: To get your scanner detected by the uscanner driver, it may be necessary to add its vendor and device ids to the kernel and recompile. Use MAKEDEV to generate the /dev/uscanner* files if they are not already there. Use sane-find-scanner to find your scanner and edit your backend's configuration file appropriately. ** Good point, since I have no /dev/uscanner* - but I have no MAKEDEV command either! And there are more lines I simply do not understand: ** If you want to use libusb, your scanner should *not* be claimed by the uscanner driver. Make sure, that /dev/ugen* and /dev/usb* devices are available. Use /dev/MAKEDEV to create them, if necessary. ** I come straight from Windows XP. Perhaps I bit off a bit more than I can chew... Can this be solved by a newbie? thanks again, -Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB Problems with Scanjet 3400c
On Tue, Nov 15, 2005 at 09:00:41PM +0100, Blue Raccoon wrote: Joe, Thanks for your tips. On Tuesday 15 November 2005 18:37, Joe Altman wrote: I suggest trying to put this after the niash in the dll.conf file: :/dev/uscanner0 I did, but it makes no difference. You should verify that /usr/local/etc/sane.d/dll.conf has the line niash in it. You cut put a line like usb /dev/uscanner0 in /usr/local/etc/sane.d/niash.conf You will also need to set up device bits, in /etc/devfs.conf: #Scanner permuscanner0 the perms you wish to have, like 0660 or 0666 Perms I wish to have? I'm afraid that means nothing to me. SANE communicates with the scanner by reading and writing from a special file in the /dev directory. Normally, only the root user has write access to these files. You need to set up /etc/devfs.rules (not /etc/devfs.conf) for hotpluggable devices like USB. The most simple solution would be to have the following in /etc/devfs.rules: [devrules=10] add path 'uscanner*' mode 0666 You'll also have to activate the ruleset 'devrules' by putting the following line in /etc/rc.conf: devfs_system_ruleset=devrules Iy that's done, you should either reboot the machine, or run the command '/etc/rc.d/devfs restart' as root (with the scanner unplugged). It that is done, and you plug in the scanner, a device file /dev/uscanner0 should appear that everybody can use. They have a patch (source code) that can alter the SANE source to become Scanjet3400c compatible. I may have to look into that, but I also found this in the patch documentation: before trying to make your scanner work, call: $ less /proc/bus/usb/devices if your scanning device is not listed by name, you probably have a 3400C or 4300C and difficulties with the kernel-usb. The forum will give you information, how to change the kernel code, to make your scanner work. My /proc/ is totally empty. This is about the /proc filesystem in Linux. Good point, since I have no /dev/uscanner* - but I have no MAKEDEV command either! And there are more lines I simply do not understand: Again, this is Linux specific. FreeBSD 5.x and 6.0 don't have a MAKEDEV command anymore, because they make device files automatically when a device is available. I come straight from Windows XP. Perhaps I bit off a bit more than I can chew... Can this be solved by a newbie? Try the things I have suggested above, plug in the scanner and run sane-find-scanner. Roland -- R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt pgpUu3M8l9lW0.pgp Description: PGP signature
Re: USB Problems with Scanjet 3400c
Roland, Thanks for your help, but... You should verify that /usr/local/etc/sane.d/dll.conf has the line niash It does. I removed the addition you suggested earlier. You cut put a line like usb /dev/uscanner0 in /usr/local/etc/sane.d/niash.conf I did (had to create the file). The most simple solution would be to have the following in /etc/devfs.rules: [devrules=10] add path 'uscanner*' mode 0666 You'll also have to activate the ruleset 'devrules' by putting the following line in /etc/rc.conf: devfs_system_ruleset=devrules I did (had to create devfs.rules). Then I rebooted, plugged the scanner in and got this: uscanner0: vendor 0x03f0 product 0x045, rev 1.00/0.00, addr 2 uscanner0: setting config no failed device_attach: uscanner0 attach returned 6 uhub0: port 2, set config at addr 2 failed uhub0: device problem (STALLED), disabling port 2 Which is almost identical to the boot-errors I had before (the first line is slightly different). Needless to say SANE still can't find the device. What can I say? 'Helaas'? - Jay ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB Problems with Scanjet 3400c
On Tue, Nov 15, 2005 at 09:25:12PM +0100, Roland Smith wrote: You should verify that /usr/local/etc/sane.d/dll.conf has the line niash in it. It did exist on my 5.4 machinebut then: You cut put a line like usb /dev/uscanner0 in /usr/local/etc/sane.d/niash.conf Roland, do you know if niash.conf is in, and/or unique to, the 6.x release? I do not see it on my 5.4 machine. Since sane is a port, I don't think it would be in one release, but not another. It is a new sane backend, so perhaps it is not yet in the ports tree, somehow? Here is pkg-plist from sane-backends on 5.4: etc/sane.d/ma1509.conf etc/sane.d/matsushita.conf etc/sane.d/microtek.conf etc/sane.d/microtek2.conf etc/sane.d/mustek.conf etc/sane.d/mustek_usb.conf etc/sane.d/nec.conf etc/sane.d/net.conf etc/sane.d/pie.conf etc/sane.d/plustek.conf And the sane page: http://www.sane-project.org/sane-backends.html#S-NIASH From: http://sourceforge.net/projects/hp3300backend About HP3300c SANE backend This project is about writing a Linux SANE backend for the HP3300c USB color scanner. Support for other scanners with very similar chipsets, like the HP3400c, HP4300c and the Agfa Touch is also planned. Operating System: All BSD Platforms (FreeBSD/NetBSD/OpenBSD/Apple Mac OS X), All POSIX (Linux/BSD/UNIX-like OSes), FreeBSD, Linux, NetBSD, OpenBSD License: GNU General Public License (GPL) Is it perhaps sufficient to create the niash.conf file? I wonder, because some of the conf files look like they may have aspects that are necessary for the correct functioning of the scanner. I come straight from Windows XP. Perhaps I bit off a bit more than I can chew... Can this be solved by a newbie? Raccoon...I think it can be solved; but it may depend on whether or not there is a backend; or, perhaps, if the dll.conf file entry is sufficient. I do not know which, if either, is the case. -- .sig is .tired. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB Problems with Scanjet 3400c
On Tue, Nov 15, 2005 at 10:52:07PM +0100, Blue Raccoon wrote: Then I rebooted, plugged the scanner in and got this: I missed that at first reading. :-/ uscanner0: vendor 0x03f0 product 0x045, rev 1.00/0.00, addr 2 Are you sure about these numbers? The product number should be four digits. According to /usr/src/sys/dev/usb/usbdevs, the product number should be 0x0405. uscanner0: setting config no failed device_attach: uscanner0 attach returned 6 Reading through the USB code, there are different failures that can cause this error. The failure originates in the function usbd_set_config_no (from usb_subr.c) called in uscanner.c. From there on the possible code paths branch out. If you could rebuild the kernel with 'options USB_DEBUG' it would generate more verbose messages, that would make it easier to follow the code path. uhub0: port 2, set config at addr 2 failed uhub0: device problem (STALLED), disabling port 2 Which is almost identical to the boot-errors I had before (the first line is slightly different). Needless to say SANE still can't find the device. What can I say? 'Helaas'? Inderdaad ;-) Roland -- R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt pgp9lg0FOXKqU.pgp Description: PGP signature
Re: USB Problems with Scanjet 3400c
On Tue, Nov 15, 2005 at 05:08:54PM -0500, Joe Altman wrote: On Tue, Nov 15, 2005 at 09:25:12PM +0100, Roland Smith wrote: You should verify that /usr/local/etc/sane.d/dll.conf has the line niash in it. It did exist on my 5.4 machinebut then: You cut put a line like usb /dev/uscanner0 in /usr/local/etc/sane.d/niash.conf Roland, do you know if niash.conf is in, and/or unique to, the 6.x release? I do not see it on my 5.4 machine. Since sane is a port, I don't think it would be in one release, but not another. It is a new sane backend, so perhaps it is not yet in the ports tree, somehow? Could be. The site for the driver said it had been merged into sane, but not into which version. snip Is it perhaps sufficient to create the niash.conf file? I wonder, because some of the conf files look like they may have aspects that are necessary for the correct functioning of the scanner. I missed something in reading the original mail. The fault occurs in the FreeBSD driver code, and prevents the creation of a uscanner device. Maybe the device is USB 2.0 only and needs the ehci driver? Otherwise building a kernel with 'options USB_DEBUG' might give a clearer picture of what's happening. Roland -- R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text. public key: http://www.xs4all.nl/~rsmith/pubkey.txt pgpK1gSEPhUt8.pgp Description: PGP signature
Re: iPod USB problems
On Ons, Mar 23, 2005 at 11:59:35pm +0100, Ulf Magnusson wrote: I'm trying to get FreeBSD to see my iPod filesystem. I stumbled across this howto, http://www.osxhax.com/archives/09.html, that outlines the procedure when using firewire. Unfortunately, my board doesn't support fireware, and so I have to use USB. The iPod is detected at boot, as can be seen in the log: * This section takes a long time to complete * (probe0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR (probe0:umass-sim0:0:0:0): Retrying Command (probe0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR (probe0:umass-sim0:0:0:0): Retrying Command (probe0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR (probe0:umass-sim0:0:0:0): Retrying Command * End of section * GEOM: new disk da0 ioapic0: routing intpin 1 (ISA IRQ 1) to cluster 0 ioapic0: routing intpin 3 (ISA IRQ 3) to cluster 0 ioapic0: routing intpin 4 (ISA IRQ 4) to cluster 0 ioapic0: routing intpin 6 (ISA IRQ 6) to cluster 0 ioapic0: routing intpin 7 (ISA IRQ 7) to cluster 0 ioapic0: routing intpin 8 (ISA IRQ 8) to cluster 0 ioapic0: routing intpin 9 (ISA IRQ 9) to cluster 0 ioapic0: routing intpin 13 (ISA IRQ 13) to cluster 0 ioapic0: routing intpin 14 (ISA IRQ 14) to cluster 0 ioapic0: routing intpin 15 (ISA IRQ 15) to cluster 0 ioapic0: routing intpin 16 (PCI IRQ 16) to cluster 0 ioapic0: routing intpin 18 (PCI IRQ 18) to cluster 0 ioapic0: routing intpin 21 (PCI IRQ 21) to cluster 0 ioapic0: routing intpin 22 (PCI IRQ 22) to cluster 0 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Apple iPod 1.62 Removable Direct Access SCSI-0 device da0: Serial Number JQ5040KTPS9 da0: 1.000MB/s transfers da0: 19073MB (39063024 512 byte sectors: 255H 63S/T 2431C) The marked section takes several minutes to complete. I thought I'd try mounting da0 as is done in the tutorial, the fstab entry being, /dev/da0 /ipod msdos rw,noauto 0 0 , but it fails with the error message msdosfs: /dev/da0: Invalid argument. I get no other da0* /dev entries. The boot message for the USB port to which I attached the iPod (which is a USB 2.0 port) might also be helpful, so I'll include it: 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 does the last line mean FreeBSD isn't correctly detecting USB 2.0 on the port? I'm running FreeBSD 5.3-RELEASE, using a Epox nForce2 motherboard. Help appreciated as always. I added the EHCI driver, and now my ports are correctly being identified as USB 2.0 . Relevant (as far as I could tell) boot messages follow: ohci0: OHCI (generic) USB controller mem 0xe4001000-0xe4001fff irq 22 at device 2.0 on pci0 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xe4001000 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 SNIP umass0: Apple iPod, rev 2.00/0.01, addr 3 umass0:0:0:-1: Attached to scbus0 ohci1: OHCI (generic) USB controller mem 0xe4004000-0xe4004fff irq 21 at device 2.1 on pci0 ohci1: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xe4004000 ohci1: [GIANT-LOCKED] SNIP ehci0: EHCI (generic) USB 2.0 controller mem 0xe4005000-0xe40050ff irq 20 at device 2.2 on pci0 ehci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0xe4005000 ehci0: [GIANT-LOCKED] SNIP ehci_pci_attach: companion usb0 ehci_pci_attach: companion usb1 usb2: EHCI version 1.0 usb2: companion controllers, 4 ports each: usb0 usb1 usb2: EHCI (generic) USB 2.0 controller on ehci0 usb2: USB revision 2.0 SNIP umass1: Apple iPod, rev 2.00/0.01, addr 2 umass1:1:1:-1: Attached to scbus1 pcib1: ACPI PCI-PCI bridge at device 8.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode0xd000-0xdfff pcib1: memory decode 0xe200-0xe3ff pcib1: prefetched decode 0xfff0-0xf SNIP GEOM: new disk ad0 [0] f:80 typ:165 s(CHS):0/0/17 e(CHS):1023/133/36 s:16 l:78164624 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 SNIP umass0: at uhub0 port 2 (addr 3) disconnected umass0: detached (probe0:umass-sim0:0:0:0): CAM Status 0x39 (probe0:umass-sim0:0:0:0): Retrying Command (probe0:umass-sim0:0:0:0): CAM Status 0x39 (probe0:umass-sim0:0:0:0): Retrying Command (probe0:umass-sim0:0:0:0): CAM Status 0x39 (probe0:umass-sim0:0:0:0): Retrying Command (probe0:umass-sim0:0:0:0): CAM Status 0x39 (probe0:umass-sim0:0:0:0): Retrying Command (probe0:umass-sim0:0:0:0): error 5 (probe0:umass-sim0:0:0:0): Retries Exhausted (probe1:umass-sim1:1:0:0): Request completed with CAM_REQ_CMP_ERR (probe1:umass-sim1:1:0:0): Retrying Command GEOM: new disk da0 SNIP da0 at umass-sim1 bus 1 target 0 lun 0 da0: Apple iPod 1.62 Removable Direct Access SCSI-0 device da0: Serial Number JQ5040KTPS9 da0: 1.000MB/s
Re: iPod USB problems
On Thursday 24 March 2005 13:47, Ulf Magnusson wrote: da0 at umass-sim1 bus 1 target 0 lun 0 da0: Apple iPod 1.62 Removable Direct Access SCSI-0 device da0: Serial Number JQ5040KTPS9 da0: 1.000MB/s transfers da0: 19073MB (39063024 512 byte sectors: 255H 63S/T 2431C) I still have the same problem though; only da0 shows up in /dev , and it still can't be mounted. camcontrol devlist now lists my iPod as, btw, have you done a simple: ls -sald /dev/da0* ? I'm working on this right now, and I found the 'pod at /dev/da0s2 However, the pod is having issues. If I boot the pod from the machine when down, it's recognized and everything is fine. However, if I try to connect after I'm up, I get the umass device but not the da0 device. Just weird. P. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iPod USB problems
On Tor, Mar 24, 2005 at 03:22:43pm -0500, Paul J. Pathiakis wrote: On Thursday 24 March 2005 13:47, Ulf Magnusson wrote: da0 at umass-sim1 bus 1 target 0 lun 0 da0: Apple iPod 1.62 Removable Direct Access SCSI-0 device da0: Serial Number JQ5040KTPS9 da0: 1.000MB/s transfers da0: 19073MB (39063024 512 byte sectors: 255H 63S/T 2431C) I still have the same problem though; only da0 shows up in /dev , and it still can't be mounted. camcontrol devlist now lists my iPod as, btw, have you done a simple: ls -sald /dev/da0* ? I'm working on this right now, and I found the 'pod at /dev/da0s2 However, the pod is having issues. If I boot the pod from the machine when down, it's recognized and everything is fine. However, if I try to connect after I'm up, I get the umass device but not the da0 device. Just weird. P. Yes, all I have is the /dev/da0 device. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iPod USB problems
Yes, all I have is the /dev/da0 device. ___ Well, first off, I'm not getting those CAM retry errors... second, I noticed this: da0: 1.000MB/s transfers da0: 19073MB (39063024 512 byte sectors: 255H 63S/T 2431C) I still have the same problem though; only da0 shows up in /dev , and it still can't be mounted. camcontrol devlist now lists my iPod as, snip message camcontrol: cam_open_btl: no passthrough device found at 1:0:0. Perhaps I've just misunderstood what camcontrol eject expects. What SCSI options are in your kernel? (I'm REALLY reaching here, just trying to help...) I noticed that it says no passthrough device, I have no idea, but, I have the fully SCSI device set in my kernel, including the passthrough device, pass. If you do, then, I guess we just have to believe it's having trouble talking to the device and due to the trouble, it's not detecting the passthrough device because it never negotiated the SCSI target correctly. # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass# Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) P. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
iPod USB problems
I'm trying to get FreeBSD to see my iPod filesystem. I stumbled across this howto, http://www.osxhax.com/archives/09.html, that outlines the procedure when using firewire. Unfortunately, my board doesn't support fireware, and so I have to use USB. The iPod is detected at boot, as can be seen in the log: * This section takes a long time to complete * (probe0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR (probe0:umass-sim0:0:0:0): Retrying Command (probe0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR (probe0:umass-sim0:0:0:0): Retrying Command (probe0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR (probe0:umass-sim0:0:0:0): Retrying Command * End of section * GEOM: new disk da0 ioapic0: routing intpin 1 (ISA IRQ 1) to cluster 0 ioapic0: routing intpin 3 (ISA IRQ 3) to cluster 0 ioapic0: routing intpin 4 (ISA IRQ 4) to cluster 0 ioapic0: routing intpin 6 (ISA IRQ 6) to cluster 0 ioapic0: routing intpin 7 (ISA IRQ 7) to cluster 0 ioapic0: routing intpin 8 (ISA IRQ 8) to cluster 0 ioapic0: routing intpin 9 (ISA IRQ 9) to cluster 0 ioapic0: routing intpin 13 (ISA IRQ 13) to cluster 0 ioapic0: routing intpin 14 (ISA IRQ 14) to cluster 0 ioapic0: routing intpin 15 (ISA IRQ 15) to cluster 0 ioapic0: routing intpin 16 (PCI IRQ 16) to cluster 0 ioapic0: routing intpin 18 (PCI IRQ 18) to cluster 0 ioapic0: routing intpin 21 (PCI IRQ 21) to cluster 0 ioapic0: routing intpin 22 (PCI IRQ 22) to cluster 0 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Apple iPod 1.62 Removable Direct Access SCSI-0 device da0: Serial Number JQ5040KTPS9 da0: 1.000MB/s transfers da0: 19073MB (39063024 512 byte sectors: 255H 63S/T 2431C) The marked section takes several minutes to complete. I thought I'd try mounting da0 as is done in the tutorial, the fstab entry being, /dev/da0/ipod msdos rw,noauto 0 0 , but it fails with the error message msdosfs: /dev/da0: Invalid argument. I get no other da0* /dev entries. The boot message for the USB port to which I attached the iPod (which is a USB 2.0 port) might also be helpful, so I'll include it: 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 does the last line mean FreeBSD isn't correctly detecting USB 2.0 on the port? I'm running FreeBSD 5.3-RELEASE, using a Epox nForce2 motherboard. Help appreciated as always. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
iPod USB problems
Ulf Magnusson writes: 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 does the last line mean FreeBSD isn't correctly detecting USB 2.0 on the port? As I remember it: a) USB 2.0 requires the EHCI driver b) the EHCI driver, while much improved over previous versions, is still not 100% ready for prime time. (You should search the list archives for more information,) Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
4.10 USB problems
I've been using 4.10 and the EHCI driver, for an external hard drive, for several months and just recently a USB-related problem has started. When the drive is plugged in it is properly recognized by umass, etc. However, attempting to mount the drive results in /kernel: umass0: BBB reset failed, TIMEOUT being logged to dmesg, and mount: /dev/da0s1e: Device not configured Someone suggested that perhaps the problem is having both ehci and uhci in the kernel. This seemed unlikely, since they've both been there all along and it worked. But I was wondering about the need for both the UHCI driver and the EHCI driver. (see dmesg output below) On my system, the startup shows usb0 through usb3 as being uhci, and usb4 as uhci. I think it also shows usb0-3 being grabbed be EHCI, am I reading that right? Still, I have had to run usbd with -f /dev/usb4 for it to notice the hard drives when they're attached. FWIW, The usbd.conf is the standard-issue one. Is it possible that some USB ports are being grabbed by UHCI and some are being grabbed by EHCI? Would rebuilding the kernel without UHCI cause all of the ports to be EHCI? The ports and harddrives are all USB2 anyway, so USB1 compatibility is not necessary. uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0xff80-0xff9f irq 11 at device 29.0 on pci0 usb0: Intel 82801EB (ICH5) USB controller USB-A 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: Intel 82801EB (ICH5) USB controller USB-B port 0xff60-0xff7f irq 10 at device 29.1 on pci0 usb1: Intel 82801EB (ICH5) USB controller USB-B 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: Intel 82801EB (ICH5) USB controller USB-C port 0xff40-0xff5f irq 9 at device 29.2 on pci0 usb2: Intel 82801EB (ICH5) USB controller USB-C 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 uhci3: Intel 82801EB (ICH5) USB controller USB-D port 0xff20-0xff3f irq 11 at device 29.3 on pci0 usb3: Intel 82801EB (ICH5) USB controller USB-D on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: EHCI (generic) USB 2.0 controller mem 0xffa80800-0xffa80bff irq 5 at device 29.7 on pci0 ehci_pci_attach: companion usb0 ehci_pci_attach: companion usb1 ehci_pci_attach: companion usb2 ehci_pci_attach: companion usb3 usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: EHCI (generic) USB 2.0 controller on ehci0 usb4: USB revision 2.0 uhub4: (0x8086) EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered __ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
4.10, USB problems
For several months I've been using an external USB hard drive, under 4.10 and the EHCI driver. It's worked perfectly for months. As of a month ago, when I swapped the drive for another one, the drive has not worked properly. A few days ago, my employer went on-site (the server is colocated) to swap the drive. The new drive had the same problem, and rebooting the server did not correct the problem. It was also reported that the last time he unplugged the drive (the fs on the drive was not mounted) the system crashed; he has since not plugged in the drive. Now the details... dmesg shows that it found a mass storage device and properly identifies it, and usbdevs also reports the drive; however, attempting to mount the drive causes mount: /dev/da0s1e: Device not configured and the message umass0: BBB reset failed, TIMEOUT appears in the dmesg. The external drive uses device usb4, since usb0 through usb3 are reported as USB1. It was suggested that having both the USB1 (uhci) and USB2 (ehci) driver may be causing confusion in the kernel. I find this unlikely, though, since it's been working for months. Any thoughts or troubleshooting tips? __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
USB problems
I am trying to install a all in one lexmark printer onto my computer, everything is correctly plugged in but the computer just cannot detect it. I know that it is not a problem with the installation disk or printer. Ithink that it may be a problem with my computer system. thanks Ieshia ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
USB problems after upgrading from 4.9 to 4.10
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, After an upgrade from 4.9 to 4.10 the following messages appear during bootup: uhci0: VIA 83C572 USB controller port 0x9800-0x981f irq 5 at device 17.2 on pci0 usb0: VIA 83C572 USB controller on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: port error, restarting port 1 uhub0: port error, giving up port 1 uhub0: port error, restarting port 2 uhub0: port error, giving up port 2 uhci1: VIA 83C572 USB controller port 0x9400-0x941f irq 5 at device 17.3 on pci0 usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub1: port error, restarting port 1 uhub1: port error, giving up port 1 uhub1: port error, restarting port 2 uhub1: port error, giving up port 2 uhci2: VIA 83C572 USB controller port 0x9000-0x901f irq 5 at device 17.4 on pci0 usb2: VIA 83C572 USB controller on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhub2: port error, restarting port 1 uhub2: port error, giving up port 1 uhub2: port error, restarting port 2 uhub2: port error, giving up port 2 orm0: Option ROM at iomem 0xcc000-0xc on isa0 Specifically I, - - rm -rf /usr/obj/ (I actually forgot to do this the first time, but redid everything with this included) - - make buildworld - - make buildkernel KERNCONF=copy of kernel config from 4.9 - - make installkernel KERNCONF=copy of kernel config from 4.9 - - reboot to single user mode - - mergemaster -p - - make installworld - - mergemaster (asked me to do a makedev, which I did). I also took a look in the BIOS and the only relevant option I found was USB Legacy Support. It was set to Auto. I changed it to Disable, but same result. I've included the kernel configuration file below. Thanks, Joey machine i386 cpu I686_CPU identACADIA_MINGRONE_ORG-2004-06-20 maxusers0 options INET#InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options UFS_DIRHASH #Improve performance on big directories options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE#Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM options SYSVSEM options SYSVMSG options SHMMAXPGS=65536 options SEMMNI=40 options SEMMNS=240 options SEMUME=40 options SEMMNU=120 options P1003_1B#Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM#Rate limit bad replies options KBD_INSTALL_CDEV# install a CDEV entry in /dev #options AHC_REG_PRETTY_PRINT # Print register bitfields in debug output. Adds ~128k to driver. #options AHD_REG_PRETTY_PRINT # Print register bitfields in debug output. Adds ~215k to driver. options USER_LDT# used by JAVA options CPU_ENABLE_SSE # used by DVD options CPU_FASTER_5X86_FPU # for mplayer options CPU_ATHLON_SSE_HACK # for mplayer device isa #device eisa device pci device agp # support several AGP chipsets # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 # ATA and ATAPI devices #device ata0 at isa? port IO_WD1 irq 14 #device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering device atapicam # emulate ATAPI devices as SCSI ditto via CAM device scbus#base SCSI code device cd #SCSI CD-ROMs device pass #CAM passthrough driver # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0
Re: USB problems after upgrading from 4.9 to 4.10
On Mon, Jun 21, 2004 at 12:31:02PM -0300, Joey Mingrone wrote: After an upgrade from 4.9 to 4.10 the following messages appear during bootup: uhci0: VIA 83C572 USB controller port 0x9800-0x981f irq 5 at device 17.2 on pci0 usb0: VIA 83C572 USB controller on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: port error, restarting port 1 uhub0: port error, giving up port 1 uhub0: port error, restarting port 2 uhub0: port error, giving up port 2 uhci1: VIA 83C572 USB controller port 0x9400-0x941f irq 5 at device 17.3 on pci0 usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub1: port error, restarting port 1 uhub1: port error, giving up port 1 uhub1: port error, restarting port 2 uhub1: port error, giving up port 2 uhci2: VIA 83C572 USB controller port 0x9000-0x901f irq 5 at device 17.4 on pci0 usb2: VIA 83C572 USB controller on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhub2: port error, restarting port 1 uhub2: port error, giving up port 1 uhub2: port error, restarting port 2 uhub2: port error, giving up port 2 orm0: Option ROM at iomem 0xcc000-0xc on isa0 I believe this is actually a bug in 4.10-RELEASE. It was fixed in 4.10-STABLE a week or so ago. As far as I know. it's actually harmless -- the USB hubs work OK despite the alarming output. See: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/uhub.c?rev=1.21.2.9content-type=text/x-cvsweb-markupsortby=dateonly_with_tag=RELENG_4 Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpqsdyVqnl2X.pgp Description: PGP signature
USB Problems
I've just installed a PCI USB card into my FreeBSD server and it appears it's not going to work. It also seems (?) to only be a USB 1.0 card (d'oh!). I've just rebuilt the kernel and added USB support. Any cloobats? (Googled, but couldn't find anything relevant). uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xd800-0xd81f irq 9 at device 7.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller 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: UHCI (generic) USB controller port 0xce00-0xce1f irq 9 at device 11.0 on pci0 usb1: UHCI (generic) USB controller on uhci1 usb1: USB revision 1.0 uhub1: (0x0106) UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub1: device problem, disabling port 1 uhub1: device problem, disabling port 2 usb1: host system error usb1: host controller halted - http://www.bangrocks.com/ - http://www.auspug.org/ http://www.ZigZagSoft.com/ - PalmOS Software and Palm Games Programming forum ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
USB problems
Hi :) I'm running FreeBSD-5.2.1-p5 and I'm having a problem with USB. Basically, I have 2 USB ports on my box: - on one there's a USB2 harddrive (running in USB1.1 compat mode; I did not compile ehci into the kernel because I was having kernel panic on boot) - on the other, there's an USB hub connected (with 3 devices connected to the hub) After some time (usually around 12 to 24h), the devices on the USB hub are not accessible anymore and I have to unplugg then replugg the hub power switch again for the devices to work. This does _not_ happen when I unplugg the USB harddrive (I unplugged it for like a week and had no problem). Note that _all_ my devices have a power switch. So my questions would be: - do you know where this problem could come from ? - do you have any idea how I could maybe send some data to the USB port to keep it alive ? Thanks in advance. Regards, -- Antoine Jacoutot [EMAIL PROTECTED] http://www.lphp.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB problems
After some time (usually around 12 to 24h), the devices on the USB hub are not accessible anymore and I have to unplugg then replugg the hub power switch again for the devices to work. This does _not_ happen when I unplugg the USB harddrive (I unplugged it for like a week and had no problem). How does your Wired memory behave during the time of intensive USB traffic? If my bet is right, you're suffering from the usb driver memory leak as outlined in these PRs: originally in the 4.x branch: http://www.freebsd.org/cgi/query-pr.cgi?pr=31659 and still not solved in the 5.x branch: http://www.freebsd.org/cgi/query-pr.cgi?pr=66324 Andre __ Do you Yahoo!? Yahoo! Movies - Buy advance tickets for 'Shrek 2' http://movies.yahoo.com/showtimes/movie?mid=1808405861 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB problems
Selon andre post [EMAIL PROTECTED]: How does your Wired memory behave during the time of intensive USB traffic? Well, when scanning for exemple, it starts at 112M Wired up to 114M Wired... so I guess this is ok. If my bet is right, you're suffering from the usb driver memory leak as outlined in these PRs: originally in the 4.x branch: http://www.freebsd.org/cgi/query-pr.cgi?pr=31659 and still not solved in the 5.x branch: http://www.freebsd.org/cgi/query-pr.cgi?pr=66324 Thanks. I hope this is the case since it looks like it will be resolved soon. Antoine ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
uhci0 / usb problems: Could not setup irq, 22
Hello world, I admit it. I'm a FreeBSD developer with a question. I got a brand new shiny supermicro P4SCT board which has an intel USB chip and thus needs the uhci (as opposed to ohci) driver. My mouse (logitech first/pilot wheel mouse) is an usb mouse. It does not work (it worked in my old ASUS A7N8X with ohci). I think I have traced it down to this part in dmesg indicating a failed attach: [EMAIL PROTECTED]:~ $ dmesg|grep uhci uhci0: UHCI (generic) USB controller port 0xc400-0xc41f irq 9 at device 29.0 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0xc400 uhci0: Could not setup irq, 22 device_probe_and_attach: uhci0 attach returned 6 uhci0: UHCI (generic) USB controller port 0xc000-0xc01f irq 11 at device 29.1 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0xc000 uhci0: [GIANT-LOCKED] usb0: UHCI (generic) USB controller on uhci0 uhci1: UHCI (generic) USB controller port 0xc400-0xc41f irq 9 at device 29.0 on pci0 uhci1: Could not setup irq, 22 device_probe_and_attach: uhci1 attach returned 6 uhci0: UHCI (generic) USB controller port 0xc400-0xc41f irq 9 at device 29.0 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0xc400 uhci0: Could not setup irq, 22 device_probe_and_attach: uhci0 attach returned 6 uhci0: UHCI (generic) USB controller port 0xc000-0xc01f irq 11 at device 29.1 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0xc000 uhci0: [GIANT-LOCKED] usb0: UHCI (generic) USB controller on uhci0 uhci1: UHCI (generic) USB controller port 0xc400-0xc41f irq 9 at device 29.0 on pci0 uhci1: Could not setup irq, 22 device_probe_and_attach: uhci1 attach returned 6 Does anyone know how to remedy the situation and get a successful attach? Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 4.9 USB problems
Hi, I'm running FreeBSD 4.9-STABLE on my IBM T23 Thinkpad. USB devices only work if they were connected when the system booted. If I plug in a USB mouse or a USB flash drive after the machine has booted, they don't appear. /var/log/messages doesn't even mention the device being plugged in. Also, if I put the laptop to sleep any USB devices are gone until I reboot. I keep trying new 5.x releases, and the USB problem doesn't occour, but I can't use 5.x because my network card (fxp) won't work and fxp0: device timeout is the reason. I'm including my rc.conf, dmesg output and my kernel config. If anyone can provide some insight I'd really appreciate it. Thanks, Ken Ebling rc.conf: hostname=laptop.deevil.org ifconfig_fxp0=inet 192.168.0.3 netmask 255.255.255.0 defaultrouter=192.168.0.1 apm_enable=YES linux_enable=YES pccard_enable=YES portmap_enable=YES sshd_enable=YES usbd_enable=YES keybell=NO kern_securelevel_enable=NO sendmail_enable=NO sendmail_submit_enable=YES moused_port=/dev/psm0 moused_type=auto moused_enable=YES dmesg output: Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.9-STABLE #7: Sat Feb 28 16:46:25 EST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LAPTOP Timecounter i8254 frequency 1193182 Hz CPU: Intel(R) Pentium(R) III Mobile CPU 866MHz (865.93-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6b1 Stepping = 1 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,C MOV,PAT,PSE36,MMX,FXSR,SSE real memory = 267845632 (261568K bytes) avail memory = 256741376 (250724K bytes) Preloaded elf kernel kernel at 0xc03d2000. netsmb_dev: loaded Pentium Pro MTRR support enabled Using $PIR table, 14 entries at 0xc00fdeb0 apm0: APM BIOS on motherboard apm0: found APM BIOS v1.2, connected at v1.2 npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 agp0: Intel 82830 host to AGP bridge mem 0xd000-0xdfff at device 0.0 on pci0 pcib1: PCI to PCI bridge (vendor=8086 device=3576) at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: S3 model 8c2e graphics accelerator at 0.0 irq 11 uhci0: Intel 82801CA/CAM (ICH3) USB controller USB-A port 0x1800-0x181f irq 11 at device 29.0 on pci0 usb0: Intel 82801CA/CAM (ICH3) USB controller USB-A 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: Intel 82801CA/CAM (ICH3) USB controller USB-B port 0x1820-0x183f irq 11 at device 29.1 on pci0 usb1: Intel 82801CA/CAM (ICH3) USB controller USB-B 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 ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/13.00, addr 2, iclass 3/1 ums0: 4 buttons and Z dir. uhci2: Intel 82801CA/CAM (ICH3) USB controller USB-C port 0x1840-0x185f irq 11 at device 29.2 on pci0 usb2: Intel 82801CA/CAM (ICH3) USB controller USB-C 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 pcib2: PCI to PCI bridge (vendor=8086 device=2448) at device 30.0 on pci0 pci2: PCI bus on pcib2 pcic0: TI PCI-1420 PCI-CardBus Bridge mem 0x5000-0x5fff irq 11 at device 0.0 on pci2 pcic0: TI12XX PCI Config Reg: [speaker enable][pwr save][CSC serial isa irq] pccard0: PC Card 16-bit bus (classic) on pcic0 pcic1: TI PCI-1420 PCI-CardBus Bridge mem 0x5100-0x51000fff irq 5 at device 0.1 on pci2 pcic1: TI12XX PCI Config Reg: [speaker enable][pwr save][CSC serial isa irq] pccard1: PC Card 16-bit bus (classic) on pcic1 pci2: unknown card (vendor=0x11c1, dev=0x0449) at 2.0 irq 11 fxp0: Intel 82801CAM (ICH3) Pro/100 VE Ethernet port 0x6400-0x643f mem 0xc020-0xc0200fff irq 11 at device 8.0 on pci2 fxp0: Ethernet address 00:d0:59:33:0c:53 inphy0: i82562ET 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: PCI to ISA bridge (vendor=8086 device=248c) at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH3 ATA100 controller port 0x1860-0x186f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ichsmb0: Intel 82801CA (ICH3) SMBus controller port 0x1880-0x189f irq 5 at device 31.3 on pci0 smbus0: System Management Bus on ichsmb0 smb0: SMBus general purpose I/O on smbus0 pcm0: Intel ICH3 (82801CA) port 0x18c0-0x18ff,0x1c00-0x1cff irq 5 at device 31.5 on pci0 pcm0: Cirrus Logic CS4299 AC97 Codec eisa0: EISA bus on motherboard eisa0: unknown card @[EMAIL PROTECTED] (0x0100) at slot 1 orm0: Option ROMs at iomem 0xc-0xcdfff,0xce000-0xcefff,0xcf000-0xc,0xdc000 -0xd,0xe-0xe on isa0 pmtimer0 on
Asus A7V8X-X USB problems
Anyone else having these errors? Is there a way to fix it? uname -a: FreeBSD localhost.bsd-unix.org 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Tue Oct 14 07:18:13 MST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CASPER i386 dmesg: uhci0: VIA 83C572 USB controller port 0xd000-0xd01f irq 6 at device 16.0 on pci0 usb0: VIA 83C572 USB controller on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: port error, restarting port 1 uhub0: port error, giving up port 1 uhub0: port error, restarting port 2 uhub0: port error, giving up port 2 uhci1: VIA 83C572 USB controller port 0xb800-0xb81f irq 6 at device 16.1 on pci0 usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub1: port error, restarting port 1 uhub1: port error, giving up port 1 uhub1: port error, restarting port 2 uhub1: port error, giving up port 2 uhci2: VIA 83C572 USB controller port 0xb400-0xb41f irq 6 at device 16.2 on pci0 usb2: VIA 83C572 USB controller on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhub2: port error, restarting port 1 uhub2: port error, giving up port 1 uhub2: port error, restarting port 2 uhub2: port error, giving up port 2 ehci0: EHCI (generic) USB 2.0 controller mem 0xe480-0xe48000ff irq 6 at device 16.3 on pci0 ehci_pci_attach: companion usb0 ehci_pci_attach: companion usb1 ehci_pci_attach: companion usb2 usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: EHCI (generic) USB 2.0 controller on ehci0 usb3: USB revision 2.0 uhub3: (0x1106) EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
