From: Petter Reinholdtsen Date: Sat, 22 Jan 2011 23:19:31 +0000 (+0000) Subject: Mer tekst. X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/877b5822a9beb2f0baa286687fde8264adb05060?hp=5a1580dcf96beec8ccd4a54ac62d9168841d533b Mer tekst. --- diff --git a/blog/data/2011-01-23-hardware-info.txt b/blog/data/2011-01-23-hardware-info.txt index fad634966d..a649bf1edf 100644 --- a/blog/data/2011-01-23-hardware-info.txt +++ b/blog/data/2011-01-23-hardware-info.txt @@ -1,14 +1,18 @@ -Title: Which module is loaded for a given PCI device? +Title: Which module is loaded for a given PCI and USB device? Tags: english, debian Date: 2011-01-23 00:15 -

In the discover-data package in Debian, there is a script to report -useful information about the running hardware for use when people -report missing information. One part I find very useful when -debugging, is the part report which kernel module is loaded for a -given PCI device. To see the output, make sure discover-data is -installed and run /usr/share/bug/discover-data 3>&1. The -relevant output on one of my machines like this: +

In the +discover-data +package in Debian, there is a script to report useful information +about the running hardware for use when people report missing +information. One part of this script that I find very useful when +debugging hardware problems, is the part mapping loaded kernel module +to the PCI device it claims. It allow me to quickly see if the kernel +module I expect is driving the hardware I am struggling with. To see +the output, make sure discover-data is installed and run +/usr/share/bug/discover-data 3>&1. The relevant output on +one of my machines like this:

 loaded modules: