Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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?
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.
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.
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.
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?