LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Reply
 
Search this Thread
Old 06-16-2008, 09:23 AM   #1
knobby67
Member
 
Registered: Mar 2006
Posts: 546

Rep: Reputation: 42
proc/bus/usb/devices no driver


Hi all,
I've been trying to get a USB device to auto start at boot, basically it won't start till it's unplugged and replugged in. I've found that proc/bus/usb/devices shows the device but shows no driver, when I unplug and replug it in it appears, driver usbtouchscreen. The kernel module is already mounted according to lsmod, rmmod and modprobe again won't link the driver with the devices only unplugging seems to work.
So is there a way I can link a device from proc/bus/usb/devices to a kernel module?
Thanks.
 
Old 06-16-2008, 04:37 PM   #2
wartstew
Member
 
Registered: Apr 2002
Location: Albuquerque, NM USA
Distribution: Slackware, Ubuntu, Debian, Maemo
Posts: 464

Rep: Reputation: 30
I'm mostly posting to auto-subscribe to this thread in case someone has some real information on this.

I too have had this sort of problem with various "hot pluggable" devices, not just USB ones. As I update my computer, sometimes things start working, sometimes they stop. I do know that there recently has been a migration from an older "hot-plug" system to a newer "udev" one. As with all things Linux, this is a work-in-progress thing.

So to start with what device specifically are you have trouble with? What Linux distribution are you using (please include the version and the output of a "uname -r" shell command)? This information will help us figure out what "hot plugging" system you are actually using and then how to move forward on fixing it.
 
Old 06-17-2008, 05:14 AM   #3
knobby67
Member
 
Registered: Mar 2006
Posts: 546

Original Poster
Rep: Reputation: 42
Hi its Debian Etch, 3m/microtouch touchscreen, 2.18 kernel. It's Udev system.
 
Old 06-17-2008, 09:50 AM   #4
JZL240I-U
Senior Member
 
Registered: Apr 2003
Location: Germany
Distribution: openSuSE 13.1 / 12.3_64-KDE, Ubuntu 14.04, Fedora 20, Mint 17, Chakra
Posts: 3,686

Rep: Reputation: Disabled
Quote:
Originally Posted by wartstew View Post
I'm mostly posting to auto-subscribe ....
Huh? Autosubscribe? What's that then? Could you please clarify, I'm most curious what that feature of LQ might be.
 
Old 06-17-2008, 03:57 PM   #5
wartstew
Member
 
Registered: Apr 2002
Location: Albuquerque, NM USA
Distribution: Slackware, Ubuntu, Debian, Maemo
Posts: 464

Rep: Reputation: 30
Quote:
Originally Posted by JZL240I-U View Post
Huh? Autosubscribe? What's that then? Could you please clarify, I'm most curious what that feature of LQ might be.
When I actually post something to a thread, it starts emailing me any activity that happens on this thread for awhile. I guess I set this up in my profile here at LQ some years back. There might be a better way to achieve the same results, but I haven't taken the time to look.

Oh and back to the thread: Yes Etch does seem to have a fairly early udev version (as in Linux 2.6.18 is pretty old these days), and I'll bet the bootup "init" scripts weren't completely compatible with it. I've got some machines that are kept up pretty close to Debian Sid, some with very current custom-compiled kernels too. Things seem to be better on some of these, especially with help from up-to-date version of KDE and GNOME that seem to know what to do with various udev events. Debian Lenny might be out early this Fall if you can wait that long.

In the meanwhile, since the problem is actually in the init scripts, you might have to learn how to hack into the existing init scripts on Etch to make the thing work for you. Sometimes it just a matter of timing so you can try moving support initialization until sometime later in the boot sequence, or as a kludge, just doing it again, perhaps just before you need it such as just before X (IE GDM/KDM/XDM) starts up. Hopefully you'll then only need this hack until you upgrade to the newer Debian in a few months. Normally I like to avoid doing these kind of things to a Debian system because you then have to fight it during future updates. However with Etch, there probably won't be many new updates in this area so it won't be much of a fight.
 
Old 06-18-2008, 05:12 AM   #6
Trickie
Member
 
Registered: Sep 2004
Posts: 38

Rep: Reputation: 23
I think that it's more likely to be udev and the udev rules. For an excellent howto on writing your own udev rules look here:-

http://reactivated.net/writing_udev_rules.html

And for a really clear description of how udev works look here:-

http://www.linuxfromscratch.org/lfs/...er07/udev.html

Hope this helps.

Richard
 
Old 06-18-2008, 11:46 AM   #7
vineesh K.K
LQ Newbie
 
Registered: Nov 2007
Posts: 4

Rep: Reputation: 3
this link might be useful..
ttp://w3.linux-magazine.com/issue/71/Extending_Hotplugging_on_Debian.pdf

this explain how the hotplug implemented in debian
 
Old 06-18-2008, 12:11 PM   #8
jiml8
Senior Member
 
Registered: Sep 2003
Posts: 3,171

Rep: Reputation: 115Reputation: 115
I am not running debian, but I did find a workaround for my rather similar problems.

Seems like haldaemon was being started fairly early in the startup, and seems that something loaded after that was causing a problem with haldaemon, and a resulting failure in udev.

I "solved" the problem by restarting haldaemon right at the end of the startup procedures. I didn't remove the initial startup because I thought that might cause other things to break, but restarting it at the end solved my various udev issues.

Something to try, anyway.
 
Old 06-19-2008, 04:43 AM   #9
knobby67
Member
 
Registered: Mar 2006
Posts: 546

Original Poster
Rep: Reputation: 42
thanks everyone, I've tried all the ideas, stop hal several different UDEV rules, but none work.
However I did find while testing all the above that I think there is an error with the KO, when I start usbtouchscreen (or it starts automatically ) with the touchscreen plugged in it starts but reports an -12 error, when I start it with no touchscreen it starts ok, then I plug in the screen its ok. I think that's why at boot with it plugged in doesn't work but plugging unplugging does. It's as if the "hello" handshake can't sync unless the driver is running before the device is plugged in? Is this possble and if it is is it a kernel driver problem?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Webcam: lsusb shows nothing and no /proc/bus/usb/devices stevesk Linux - Hardware 8 08-02-2006 04:03 AM
where is /proc/bus/usb/devices???? mrchaos Linux - Software 4 12-04-2005 11:26 PM
MDK 10.2: No USB at all (/proc/bus/usb/devices missing) shrodi Mandriva 5 07-01-2005 12:28 PM
question on /proc/bus/usb/devices file ryan_a_hH Linux - Hardware 2 01-21-2005 02:49 PM
/proc/bus/usb/devices missing shellcode Linux - General 11 02-24-2004 11:15 PM


All times are GMT -5. The time now is 03:56 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration