Mailinglist Archive: opensuse (4600 mails)
| < Previous | Next > |
Re: [SLE] USB and camera hotplugging
- From: Matt Jurcich <mattj@xxxxxxxxxxx>
- Date: Fri, 30 Jan 2004 09:28:26 -0600
- Message-id: <401A781A.7080002@xxxxxxxxxxx>
Yeah, I hear you there.
Any suggestions (from anyone) on how to manually stop and start the usb subsystem? I found these commands but have had only limited success:
sudo rmmod usb-uhci ehci-hcd hid
sudo modprobe usb-uhci hid
I believe it's supposed to unload the module for USB and then reload it in the second command. I still had to reboot to connect a USB mouse to my laptop this morning. :(
Thanks much!
-m
David L Moss wrote:
Any suggestions (from anyone) on how to manually stop and start the usb subsystem? I found these commands but have had only limited success:
sudo rmmod usb-uhci ehci-hcd hid
sudo modprobe usb-uhci hid
I believe it's supposed to unload the module for USB and then reload it in the second command. I still had to reboot to connect a USB mouse to my laptop this morning. :(
Thanks much!
-m
David L Moss wrote:
On Thursday 29 January 2004 09:32, Matt Jurcich wrote:
Hey,
Any resolutions to this issue? I have this problem with all my USB
devices--camera, palm pilot, usb keychain drive, usb mouse. I have
resorted to rebooting with the device plugged in on start up for it to
work with virtually any degree of success.
And I agree, I get a beep or other indication the computer knows the
device is plugged in. It seems as it's SUSE that takes it's time to
decide to use the new device........
Thanks much!
This is another case of something in Suse linux 9.0 that worked for awhile, quit working and nothing I do fixes it. I have compact flash readers, usb thumb drives, and external hard drives that worked for a while then stopped never to work again. My mouse, keyboard, palm pilot and Jpilot are the only usb devices that conistantly work although sometimes with a lot of research and time to get the right modules to load. My external card readers are paperwieghts now.
Hotplugging seems to be a work in progress that will not consistantly perform.
DLM
-m
Paul W. Abrahams wrote:
On Wednesday 28 January 2004 5:02 pm, Tom Nielsen wrote:
I've noticed that even though the camera doesn't appear right away onWhere is that beep coming from? Not the camera, I assume, since you said
the desktop, it's still active. I use digikam with my camera. I plug it
in, wait for the beep, turn it on, start Digikam, then connect to the
camera...taking about 5 seconds. As soon as digikam picks up the camera
and connects, I get the icon on my desktop.
the camera isn't yet turned on. And is there a significant delay for
Digikam (which I use also) to pick up the camera?
I've tried doing what you did. Plug in the camera, turn it on and waitWould you conclude that having Digikam running speeds up the response
for the icon to appear. Took quite a long time. To me it doesn't matter
since I use digikam all the time.
time, then?
Thanks for the info though. Also, I don't have any fstab entries for theHow does the camera show up on your desktop? Depending on whether I have
camera either.
an fstab entry, it shows up either as "sdb1" or "camera".
Paul Abrahams
| < Previous | Next > |