On Friday, November 19, 2010 05:49:50 pm Alan Stern did opine: > On Thu, 18 Nov 2010, gene heskett wrote: > > Greetings; > > > > I plugged in my Nikon CoolPix L100 to have digikam pull the last few > > shots, and discovered that it is not showing up when plugged in and > > turned on by any new messages in the messages log. > > > > dmesg changes for every run if I wait 2 seconds between re-runs, and > > this is also logged in the syslog as: > > > > Nov 18 20:38:29 coyote klogd: ohci_hcd 0000:00:02.0: urb ebe7e000 path > > 9 ep1in 93120000 cc 9 --> status -121 Nov 18 20:38:31 coyote klogd: > > ohci_hcd 0000:00:02.0: urb e8be6080 path 9 ep1in 92120000 cc 9 --> > > status -121 > > ... > > > Then I had a session of minicom running to a older machine, using port > > /dev/ttyS0, but after the reboot, that is also non-functional. > > > > This is the same 2.6.36 kernel that has been running fine since it was > > announced, but this was the first time I had tried to access my camera > > on this kernel so this has likely been so for a couple of weeks now. > > > > The distro is a 32 bit pclos, up to date (except tar, 1.24 breaks > > amanda) just before the reboot. > > > > Does this ring any bells with anybody? Most of the rest of the usb > > stuff seems to be there according to a lsusb: > > > > Does this ring any bells for anyone? > > It could be a hardware problem. > > Here's what you should do. For testing purposes, unplug as many of > your other USB devices as you can. Then collect a usbmon trace (see > Documentation/usb/usbmon.txt) showing what happens when you plug in the > Nikon and try to use it. > > Alan Stern I believe I may have found it Alan, I had a targus unpowered USB-2.0 hub, plugged into the mobo's breakout socket, with the camera cable and one of those universal card readers sharing that hub. When neither showed up, and nothing was noted when I unplugged it was the Aha! moment. It has worked great for about 4 years, originally bought to expand my lappy when I was out of pocket 1000 miles away. The error being logged every two seconds was coming from Nut's upsd, and a rebuild of the kernel to include usbdevfs so I could use usbview to troubleshoot, and a reboot to it fixed that, now the syslog and messages logs track each other nicely. Looks like I should hold services for the hub, say a few semi-complementary words about how it was a good servant for 3 or 4 years and then bin it. ;-) Then test a powered 7 port on that socket just for grins. That had the un-expected side effect of restoring /dev/ttyS0 to normal so I can use minicom on it again, something that 2 reboots before had not managed. NDI how that should be connected to a usb failure though unless there is a break in the tachyon field someplace. I should ask Data to run a sub-space scan I suppose. I think I've been watching too much Star Trek TNG in the wee hours. :-) Thanks Alan. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Might as well be frank, monsieur. It would take a miracle to get you out of Casablanca and the Germans have outlawed miracles. -- Casablanca -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
