On Wed, Apr 23, 2008 at 10:39:19PM +0000, Sébastien Morand wrote: >> What kind of USB chip do you have on the motherboard? Try 'dmesg | grep >> ^usb' and post the output. > > $ 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: <nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0 > usb1: waiting for BIOS to give up control > usb1: timed out waiting for BIOS > usb1: EHCI version 1.0 > usb1: companion controller, 4 ports each: usb0 > usb1: <NVIDIA nForce4 USB 2.0 controller> on ehci0 > usb1: USB revision 2.0 > uhub1: <nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb1 > >> It could be a hardware problem, or a bug. > > Hardware is fine under linux (same machine) or windows on my wife's laptop (no > pb with the USB devices), so I don't think so. > >> Does anything appear in the dmesg output when you try to plug in a USB >> device? look in /var/log/messages, at the correct time. >> E.g, the following appears when I plug in a USB flash drive; > > I get this: > Apr 23 22:17:48 mellba root: Unknown USB device: vendor 0x07b4 product 0x0105 > bus uhub0
According to the file /usr/src/sys/dev/usb/usbdevs on my 7-STABLE system, this is a C-700 camera, which should be recognized. > Apr 23 22:17:48 mellba kernel: umass2: <OLYMPUS X100,D540Z,C310Z, class 0/0, > rev > 2.00/1.00, addr 2> on uhub0 And it does not seem to be recognized properly. > So My USB device has been seen and then nothing until the first message of the > next boot OK, so it goes wrong before the usb subsystem hands the camera off as a da device. This is uhub0, so it's recognized as a USB 1.0 device. Is it USB 2.0 capable > Actually it's quite funny because I have a hard disk on my da0 which > is working fine: > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: <WD 2500JB External 0108> Fixed Direct Access SCSI-0 device > da0: 40.000MB/s transfers > da0: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C) > GEOM_LABEL: Label for provider da0s1 is msdosfs/My Book. From the transfer rate I infer that this is a USB 2.0 device. It should be connected to uhub1. > User sebastien is a member if wheel, so hot plug should be working (and it > is with my usb key and my usb hard disk ... it's only my mp3 player and my > camera which make my pc hanging up). Is the mp3 player a usb 1.0 device as well? In that case the trouble is probably with the ohci driver, since the USB 2.0 devices seem to work well. > I try do disable both these services and the result is the same. > >> Seeing which of these lines appear or not makes it easier to track down >> the bug. >> >> Try to read the crashdump with the kernel debugger, as described in >> §10.2 of the FreeBSD Developers' Handbook. Obtain a so-called >> backtrace. (using the 'bt' command in the debugger). > > I can't do that. It required a built kernel, didn't it? > The handbook said to launch: > # cd /usr/obj/usr/src/sys/GENERIC > # kgdb kernel.debug /var/crash/vmcore.0 > > But ... I don't have this directory since I don't compile my kernel, so Itry > to On 7.x you should have /boot/kernel/kernel.symbols, which is the debugging kernel (/boot/kernel/kernel is the regular, stripped, kernel). > compile the generic kernel: > Here is what I read trying to build the generic kernel: > === [23\04\2008 22:09:14] [EMAIL PROTECTED]:/usr/src > # make buildkernel KERNCONF=GENERIC > "Makefile.inc1", line 1034: Malformed conditional (${MK_LIBTHR} != "no"&& > ${MK_LIBKSE} != "no") There should be a space between "no" and &&. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
pgpN8Q8jBfE0P.pgp
Description: PGP signature