X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/5a1580dcf96beec8ccd4a54ac62d9168841d533b..532e635f576c887287fc778ed5c90e46c625082b:/blog/data/2011-01-23-hardware-info.txt diff --git a/blog/data/2011-01-23-hardware-info.txt b/blog/data/2011-01-23-hardware-info.txt index fad634966d..0872e6affe 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 +Date: 2011-01-23 00:20 -
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: @@ -37,7 +41,7 @@ if [ -d /sys/bus/pci/devices/ ] ; then module=`cd $address/driver/module ; pwd -P | xargs basename` if grep -q "^$module " /proc/modules ; then address=$(echo $address |sed s/0000://) - id=`lspci -n -s $address | tail -n 1 | awk '{print $3}'` + id=`lspci -n -s $address | tail -n 1 | awk '{print $3}'` echo "$id $module" fi fi