On Sat, 13 Mar 2010 00:09:13 +0100 Florian Kulzer <florian.kulzer+deb...@icfo.es> wrote:
... > The kernel seems to use the information in > > /lib/modules/$(uname -r)/modules.alias > > to decide which module(s) to try for a given device. AFAIK, this > information is generated/updated by running depmod, which is handled > automatically if you install a Debian kernel package or if you use > module-assistant/DKMS to handle additional modules. ... > That is also how I understand the process. Some of the entries in > modules.alias are straightforward vendor/device-ID pairs, while others > use wildcards for these values and rely on capabilities such as "a modem > of class X, subclass Y that understands protocol Z". The module then > often uses dedicated diagnostic code to find out if it really supports > that particular device. Syslog/dmesg should reveal which modules the > kernel tried in response to a USB hotplug event and if there were any > problems. Modprobing the module with a higher debug level (if that > option is available) should provide additional clues. This looks like useful stuff to know - thanks. Celejar -- foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100313201200.b4e08e8c.cele...@gmail.com
