Petter Reinholdtsen: Modalias strings - a practical way to map "stuff" to hardware

+ v 1D6B (device vendor) + p 0001 (device product) + d 0206 (bcddevice) + dc 09 (device class) + dsc 00 (device subclass) + dp 00 (device protocol) + ic 09 (interface class) + isc 00 (interface subclass) + ip 00 (interface protocol) +

+ bvn IBM (BIOS vendor) + bvr 1UETB6WW(1.66) (BIOS version) + bd 06/15/2005 (BIOS date) + svn IBM (system vendor) + pn 2371H4G (product name) + pvr ThinkPadX40 (product version) + rvn IBM (board vendor) + rn 2371H4G (board name) + rvr NotAvailable (board version) + cvn IBM (chassis vendor) + ct 10 (chassis type) + cvr NotAvailable (chassis version) +

+ 3 Desktop + 4 Low Profile Desktop + 5 Pizza Box + 6 Mini Tower + 7 Tower + 8 Portable + 9 Laptop + 10 Notebook + 11 Hand Held + 12 Docking Station + 13 All In One + 14 Sub Notebook + 15 Space-saving + 16 Lunch Box + 17 Main Server Chassis + 18 Expansion Chassis + 19 Sub Chassis + 20 Bus Expansion Chassis + 21 Peripheral Chassis + 22 RAID Chassis + 23 Rack Mount Chassis + 24 Sealed-case PC + 25 Multi-system + 26 CompactPCI + 27 AdvancedTCA + 28 Blade + 29 Blade Enclosing +

+ acpi:ACPI0003: + insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko + acpi:device: + FATAL: Module acpi:device: not found. + acpi:IBM0068: + insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko + insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko + insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko + insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko + acpi:IBM0071:PNP0511: + insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko + insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko + insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko + [...] +

Moved the pymissile Debian packaging to collab-maint @@ -320,7 +583,7 @@ siste mÃ¥neden.

2013

January (4)
January (5)

@@ -470,7 +733,7 @@ siste mÃ¥neden.

@@ -480,7 +743,7 @@ siste mÃ¥neden.

diff --git a/blog/data/2013-01-14-hw-autoinstall-modalias.txt b/blog/data/2013-01-14-hw-autoinstall-modalias.txt index 72db02bf47..7c03e552b4 100644 --- a/blog/data/2013-01-14-hw-autoinstall-modalias.txt +++ b/blog/data/2013-01-14-hw-autoinstall-modalias.txt @@ -1,6 +1,6 @@ Title: Modalias strings - a practical way to map "stuff" to hardware Tags: english, debian -Date: 2013-01-14 11:10 +Date: 2013-01-14 11:15

While looking into how to look up Debian packages based on hardware information, to find the packages that support a given piece of diff --git a/blog/index.html b/blog/index.html index e95802ffe6..9ea17bb146 100644 --- a/blog/index.html +++ b/blog/index.html @@ -19,6 +19,263 @@ +

Modalias strings - a practical way to map "stuff" to hardware

14th January 2013

While looking into how to look up Debian packages based on hardware +information, to find the packages that support a given piece of +hardware, I refreshed my memory regarding modalias values, and decided +to document the details. Here are my findings so far, also available +in +the +Debian Edu subversion repository: + +

Modalias decoded

+ +

This document try to explain what the different types of modalias +values stands for. It is in part based on information from +<URL: https://wiki.archlinux.org/index.php/Modalias >, +<URL: http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device >, +<URL: http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c > and +<URL: http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&view=markup >. + +

The modalias entries for a given Linux machine can be found using +this shell script:

+ +

+cat $(find /sys -name modalias) | sort -u
+

+ +

The supported modalias globs for a given kernel module can be found +using modinfo:

+ +

+% /sbin/modinfo psmouse | grep alias:
+alias:          serio:ty05pr*id*ex*
+alias:          serio:ty01pr*id*ex*
+%
+

+ +

PCI subtype

+ +

A typical PCI entry can look like this. This is an Intel Host +Bridge memory controller:

+ +

+pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00 +

+ +

This represent these values:

+ +

+ v   00008086  (vendor)
+ d   00002770  (device)
+ sv  00001028  (subvendor)
+ sd  000001AD  (subdevice)
+ bc  06        (bus class)
+ sc  00        (bus subclass)
+ i   00        (interface)
+

+ +

The vendor/device values are the same values outputted from 'lspci +-n' as 8086:2770. The bus class/subclass is also shown by lspci as +0600. The 0600 class is a host bridge. Other useful bus values are +0300 (VGA compatible card) and 0200 (Ethernet controller).

+ +

Not sure how to figure out the interface value, nor what it +means.

+ +

USB subtype

+ +

Some typical USB entries can look like this. This is an internal +USB hub in a laptop:

+ +

+usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00 +

+ +

Here is the values included in this alias:

+ +

+ v    1D6B  (device vendor)
+ p    0001  (device product)
+ d    0206  (bcddevice)
+ dc     09  (device class)
+ dsc    00  (device subclass)
+ dp     00  (device protocol)
+ ic     09  (interface class)
+ isc    00  (interface subclass)
+ ip     00  (interface protocol)
+

+ +

The 0900 device class/subclass means hub. Some times the relevant +class is in the interface class section. For a simple USB web camera, +these alias entries show up:

+ +

+usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00 +
usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00 +
usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00 +
usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00 +

+ +

Interface class 0E01 is video control, 0E02 is video streaming (aka +camera), 0101 is audio control device and 0102 is audio streaming (aka +microphone). Thus this is a camera with microphone included.

+ +

ACPI subtype

+ +

The ACPI type is used for several non-PCI/USB stuff. This is an IR +receiver in a Thinkpad X40:

+ +

+acpi:IBM0071:PNP0511: +

+ +

The values between the colons are IDs.

+ +

DMI subtype

+ +

The DMI table contain lots of information about the computer case +and model. This is an entry for a IBM Thinkpad X40, fetched from +/sys/devices/virtual/dmi/id/modalias:

+ +

+dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: +

+ +

The values present are

+ +

+ bvn  IBM            (BIOS vendor)
+ bvr  1UETB6WW(1.66) (BIOS version)
+ bd   06/15/2005     (BIOS date)
+ svn  IBM            (system vendor)
+ pn   2371H4G        (product name)
+ pvr  ThinkPadX40    (product version)
+ rvn  IBM            (board vendor)
+ rn   2371H4G        (board name)
+ rvr  NotAvailable   (board version)
+ cvn  IBM            (chassis vendor)
+ ct   10             (chassis type)
+ cvr  NotAvailable   (chassis version)
+

+ +

The chassis type 10 is Notebook. Other interesting values can be +found in the dmidecode source:

+ +

+  3 Desktop
+  4 Low Profile Desktop
+  5 Pizza Box
+  6 Mini Tower
+  7 Tower
+  8 Portable
+  9 Laptop
+ 10 Notebook
+ 11 Hand Held
+ 12 Docking Station
+ 13 All In One
+ 14 Sub Notebook
+ 15 Space-saving
+ 16 Lunch Box
+ 17 Main Server Chassis
+ 18 Expansion Chassis
+ 19 Sub Chassis
+ 20 Bus Expansion Chassis
+ 21 Peripheral Chassis
+ 22 RAID Chassis
+ 23 Rack Mount Chassis
+ 24 Sealed-case PC
+ 25 Multi-system
+ 26 CompactPCI
+ 27 AdvancedTCA
+ 28 Blade
+ 29 Blade Enclosing
+

+ +

The chassis type values are not always accurately set in the DMI +table. For example my home server is a tower, but the DMI modalias +claim it is a desktop.

+ +

SerIO subtype

+ +

This type is used for PS/2 mouse plugs. One example is from my +test machine:

+ +

+serio:ty01pr00id00ex00 +

+ +

The values present are

+ +

+  ty  01  (type)
+  pr  00  (prototype)
+  id  00  (id)
+  ex  00  (extra)
+

+ +

This type is supported by the psmouse driver. I am not sure what +the valid values are.

+ +

Other subtypes

+ +

There are heaps of other modalias subtypes according to +file2alias.c. There is the rest of the list from that source: amba, +ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp, +mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio, +vmbus, x86cpu and zorro. I did not spend time documenting all of +these, as they do not seem relevant for my intended use with mapping +hardware to packages when new stuff is inserted during run time.

+ +

Looking up kernel modules using modalias values

+ +

To check which kernel modules provide support for a given modalias, +one can use the following shell script:

+ +

+  for id in $(cat $(find /sys -name modalias)|sort -u); do \
+    echo "$id" ; \
+    /sbin/modprobe --show-depends "$id"|sed 's/^/  /' ; \
+  done
+

+ +

The output can look like this (only the first few entries as the +list is very long on my test machine):

+ +

+  acpi:ACPI0003:
+    insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko 
+  acpi:device:
+  FATAL: Module acpi:device: not found.
+  acpi:IBM0068:
+    insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko 
+    insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko 
+    insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko 
+    insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko 
+  acpi:IBM0071:PNP0511:
+    insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko 
+    insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko 
+    insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko 
+  [...]
+

+ +

If you want to help implementing a system to let us propose what +packages to install when new hardware is plugged into a Debian +machine, please send me an email or talk to me on +#debian-devel.

+ + + Tags: debian, english. + + +

Moved the pymissile Debian packaging to collab-maint

10th January 2013

@@ -602,45 +859,6 @@ for the organisations I am involved in.

61 kommuner lenker nÃ¥ til FiksGataMi fra sine nettsider

11th December 2012

For noen dager siden omfavnet nok en kommune NUUGs -FiksGataMi. Med 61 kommuner -som lenker til FiksGataMi fra sine hjemmesider er Â«markedsandelenÂ» 14% -(av 429 kommuner). Siden -siste -oppdatering i november har kommunene Re og VÃ¥gsÃ¸y kommet til og -slÃ¥r fÃ¸lge med kommunene Askim, AskÃ¸y, Audnedal, Aure, Balestrand, -BÃ¦rum, Eide, Farsund, Flekkefjord, Folldal, Gran, Grue, Hadsel, -Halden, Halsa, Hamar, HobÃ¸l, HoltÃ¥len, HÃ¦gebostad, HÃ¸yanger, -Kongsberg, Kristiansund, Kvinesdal, Kviteseid, Levanger, Lindesnes, -Luster, Lyngdal, LÃ¸ten, Mandal, Marnardal, Moss, Namsos, Nissedal, -Nordreisa, Randaberg, Rindal, Sel, Sirdal, Skiptvet, Sortland, -Spydeberg, Stange, StjÃ¸rdal, Stord, SÃ¸gne, SÃ¸r-Odal, Tolga, Trysil, -Tynset, TysvÃ¦r, Ullensvang Herad, Utsira, Vennesla, Verdal, VÃ¥gan, -VÃ¥gÃ¥, VÃ¥ler og Ãseral. Oppdatert liste er tilgjengelig fra -NUUGs -wiki. Kartet er dog ikke oppdatert med de siste kommunene.

- -

Kanskje du bÃ¸r hÃ¸re med din kommune om de vil bli mer aktive -brukere av FiksGataMi? Se -en -tidligere bloggpost med tips om hvordan det kan gjÃ¸res.

- -

I snitt rapporteres det nÃ¥ via FiksGataMi ca. 60 meldinger fra -innbyggerne i uka om feil pÃ¥ offentlig infrastruktur.

- - - Tags: fiksgatami, norsk. - - -

@@ -652,7 +870,7 @@ innbyggerne i uka om feil pÃ¥ offentlig infrastruktur.

2013

January (4)
January (5)

@@ -802,7 +1020,7 @@ innbyggerne i uka om feil pÃ¥ offentlig infrastruktur.

@@ -812,7 +1030,7 @@ innbyggerne i uka om feil pÃ¥ offentlig infrastruktur.

diff --git a/blog/index.rss b/blog/index.rss index 13cebea5c8..df56b115cf 100644 --- a/blog/index.rss +++ b/blog/index.rss @@ -6,6 +6,257 @@ http://people.skolelinux.org/pere/blog/ + + Modalias strings - a practical way to map "stuff" to hardware + http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html + http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html + Mon, 14 Jan 2013 11:10:00 +0100 + While looking into how to look up Debian packages based on hardware +information, to find the packages that support a given piece of +hardware, I refreshed my memory regarding modalias values, and decided +to document the details. Here are my findings so far, also available +in +<a href="http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/">the +Debian Edu subversion repository</a>: + +Modalias decoded + +This document try to explain what the different types of modalias +values stands for. It is in part based on information from +<URL: <a href="https://wiki.archlinux.org/index.php/Modalias">https://wiki.archlinux.org/index.php/Modalias</a> >, +<URL: <a href="http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device">http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device</a> >, +<URL: <a href="http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c">http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c</a> > and +<URL: <a href="http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&view=markup">http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&view=markup</a> >. + +The modalias entries for a given Linux machine can be found using +this shell script: + +<pre> +cat $(find /sys -name modalias) | sort -u +</pre> + +The supported modalias globs for a given kernel module can be found +using modinfo: + +<pre> +% /sbin/modinfo psmouse | grep alias: +alias: serio:ty05pr*id*ex* +alias: serio:ty01pr*id*ex* +% +</pre> + +PCI subtype + +A typical PCI entry can look like this. This is an Intel Host +Bridge memory controller: + +<blockquote> +pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00 +</blockquote> + +This represent these values: + +<pre> + v 00008086 (vendor) + d 00002770 (device) + sv 00001028 (subvendor) + sd 000001AD (subdevice) + bc 06 (bus class) + sc 00 (bus subclass) + i 00 (interface) +</pre> + +The vendor/device values are the same values outputted from 'lspci +-n' as 8086:2770. The bus class/subclass is also shown by lspci as +0600. The 0600 class is a host bridge. Other useful bus values are +0300 (VGA compatible card) and 0200 (Ethernet controller). + +Not sure how to figure out the interface value, nor what it +means. + +USB subtype + +Some typical USB entries can look like this. This is an internal +USB hub in a laptop: + +<blockquote> +usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00 +</blockquote> + +Here is the values included in this alias: + +<pre> + v 1D6B (device vendor) + p 0001 (device product) + d 0206 (bcddevice) + dc 09 (device class) + dsc 00 (device subclass) + dp 00 (device protocol) + ic 09 (interface class) + isc 00 (interface subclass) + ip 00 (interface protocol) +</pre> + +The 0900 device class/subclass means hub. Some times the relevant +class is in the interface class section. For a simple USB web camera, +these alias entries show up: + +<blockquote> +usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00 + usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00 + usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00 + usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00 +</blockquote> + +Interface class 0E01 is video control, 0E02 is video streaming (aka +camera), 0101 is audio control device and 0102 is audio streaming (aka +microphone). Thus this is a camera with microphone included. + +ACPI subtype + +The ACPI type is used for several non-PCI/USB stuff. This is an IR +receiver in a Thinkpad X40: + +<blockquote> +acpi:IBM0071:PNP0511: +</blockquote> + +The values between the colons are IDs. + +DMI subtype + +The DMI table contain lots of information about the computer case +and model. This is an entry for a IBM Thinkpad X40, fetched from +/sys/devices/virtual/dmi/id/modalias: + +<blockquote> +dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: +</blockquote> + +The values present are + +<pre> + bvn IBM (BIOS vendor) + bvr 1UETB6WW(1.66) (BIOS version) + bd 06/15/2005 (BIOS date) + svn IBM (system vendor) + pn 2371H4G (product name) + pvr ThinkPadX40 (product version) + rvn IBM (board vendor) + rn 2371H4G (board name) + rvr NotAvailable (board version) + cvn IBM (chassis vendor) + ct 10 (chassis type) + cvr NotAvailable (chassis version) +</pre> + +The chassis type 10 is Notebook. Other interesting values can be +found in the dmidecode source: + +<pre> + 3 Desktop + 4 Low Profile Desktop + 5 Pizza Box + 6 Mini Tower + 7 Tower + 8 Portable + 9 Laptop + 10 Notebook + 11 Hand Held + 12 Docking Station + 13 All In One + 14 Sub Notebook + 15 Space-saving + 16 Lunch Box + 17 Main Server Chassis + 18 Expansion Chassis + 19 Sub Chassis + 20 Bus Expansion Chassis + 21 Peripheral Chassis + 22 RAID Chassis + 23 Rack Mount Chassis + 24 Sealed-case PC + 25 Multi-system + 26 CompactPCI + 27 AdvancedTCA + 28 Blade + 29 Blade Enclosing +</pre> + +The chassis type values are not always accurately set in the DMI +table. For example my home server is a tower, but the DMI modalias +claim it is a desktop. + +SerIO subtype + +This type is used for PS/2 mouse plugs. One example is from my +test machine: + +<blockquote> +serio:ty01pr00id00ex00 +</blockquote> + +The values present are + +<pre> + ty 01 (type) + pr 00 (prototype) + id 00 (id) + ex 00 (extra) +</pre> + +This type is supported by the psmouse driver. I am not sure what +the valid values are. + +Other subtypes + +There are heaps of other modalias subtypes according to +file2alias.c. There is the rest of the list from that source: amba, +ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp, +mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio, +vmbus, x86cpu and zorro. I did not spend time documenting all of +these, as they do not seem relevant for my intended use with mapping +hardware to packages when new stuff is inserted during run time. + +Looking up kernel modules using modalias values + +To check which kernel modules provide support for a given modalias, +one can use the following shell script: + +<pre> + for id in $(cat $(find /sys -name modalias)|sort -u); do \ + echo "$id" ; \ + /sbin/modprobe --show-depends "$id"|sed 's/^/ /' ; \ + done +</pre> + +The output can look like this (only the first few entries as the +list is very long on my test machine): + +<pre> + acpi:ACPI0003: + insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko + acpi:device: + FATAL: Module acpi:device: not found. + acpi:IBM0068: + insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko + insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko + insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko + insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko + acpi:IBM0071:PNP0511: + insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko + insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko + insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko + [...] +</pre> + +If you want to help implementing a system to let us propose what +packages to install when new hardware is plugged into a Debian +machine, please send me an email or talk to me on +<a href="irc://irc.debian.org/%23debian-devel">#debian-devel</a>. + + + Moved the pymissile Debian packaging to collab-maint http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html @@ -535,38 +786,5 @@ for the organisations I am involved in. - - 61 kommuner lenker nÃ¥ til FiksGataMi fra sine nettsider - http://people.skolelinux.org/pere/blog/61_kommuner_lenker_n__til_FiksGataMi_fra_sine_nettsider.html - http://people.skolelinux.org/pere/blog/61_kommuner_lenker_n__til_FiksGataMi_fra_sine_nettsider.html - Tue, 11 Dec 2012 23:55:00 +0100 - For noen dager siden omfavnet nok en kommune NUUGs -<a href="http://www.fiksgatami.no/">FiksGataMi</a>. Med 61 kommuner -som lenker til FiksGataMi fra sine hjemmesider er Â«markedsandelenÂ» 14% -(av 429 kommuner). Siden -<a href="http://people.skolelinux.org/pere/blog/59_kommuner_omfavner_n__FiksGataMi.html">siste -oppdatering i november</a> har kommunene Re og VÃ¥gsÃ¸y kommet til og -slÃ¥r fÃ¸lge med kommunene Askim, AskÃ¸y, Audnedal, Aure, Balestrand, -BÃ¦rum, Eide, Farsund, Flekkefjord, Folldal, Gran, Grue, Hadsel, -Halden, Halsa, Hamar, HobÃ¸l, HoltÃ¥len, HÃ¦gebostad, HÃ¸yanger, -Kongsberg, Kristiansund, Kvinesdal, Kviteseid, Levanger, Lindesnes, -Luster, Lyngdal, LÃ¸ten, Mandal, Marnardal, Moss, Namsos, Nissedal, -Nordreisa, Randaberg, Rindal, Sel, Sirdal, Skiptvet, Sortland, -Spydeberg, Stange, StjÃ¸rdal, Stord, SÃ¸gne, SÃ¸r-Odal, Tolga, Trysil, -Tynset, TysvÃ¦r, Ullensvang Herad, Utsira, Vennesla, Verdal, VÃ¥gan, -VÃ¥gÃ¥, VÃ¥ler og Ãseral. Oppdatert liste er tilgjengelig fra -<a href="http://wiki.nuug.no/grupper/fiksgatami/positivemottakere">NUUGs -wiki</a>. Kartet er dog ikke oppdatert med de siste kommunene. - -Kanskje du bÃ¸r hÃ¸re med din kommune om de vil bli mer aktive -brukere av FiksGataMi? Se -<a href="http://people.skolelinux.org/pere/blog/40_kommuner_lenker_n__til_FiksGataMi_fra_sine_nettsider___gj_r_din_.html">en -tidligere bloggpost</a> med tips om hvordan det kan gjÃ¸res. - -I snitt rapporteres det nÃ¥ via FiksGataMi ca. 60 meldinger fra -innbyggerne i uka om feil pÃ¥ offentlig infrastruktur. - - - diff --git a/blog/jXplorer__a_very_nice_LDAP_GUI.html b/blog/jXplorer__a_very_nice_LDAP_GUI.html index 698f15245e..ac3fc48f76 100644 --- a/blog/jXplorer__a_very_nice_LDAP_GUI.html +++ b/blog/jXplorer__a_very_nice_LDAP_GUI.html @@ -54,7 +54,7 @@ and remove the failing query. Nothing big, but very annoying.

2013

January (4)
January (5)

@@ -204,7 +204,7 @@ and remove the failing query. Nothing big, but very annoying.

@@ -214,7 +214,7 @@ and remove the failing query. Nothing big, but very annoying.

diff --git a/blog/sitemap.xml b/blog/sitemap.xml index c3c3a5c20f..ecac6312ce 100644 --- a/blog/sitemap.xml +++ b/blog/sitemap.xml @@ -1140,6 +1140,11 @@ 0.50 weekly + + http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html + 0.50 + weekly + http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html 0.50 diff --git a/blog/systemd__an_interesting_alternative_to_upstart.html b/blog/systemd__an_interesting_alternative_to_upstart.html index a31b4281b9..1a45bcd2a9 100644 --- a/blog/systemd__an_interesting_alternative_to_upstart.html +++ b/blog/systemd__an_interesting_alternative_to_upstart.html @@ -72,7 +72,7 @@ with parallel booting enabled by default.

2013

January (4)
January (5)

@@ -222,7 +222,7 @@ with parallel booting enabled by default.

@@ -232,7 +232,7 @@ with parallel booting enabled by default.

diff --git a/blog/tags/3d-printer/index.html b/blog/tags/3d-printer/index.html index 108c989ba7..cd247776b2 100644 --- a/blog/tags/3d-printer/index.html +++ b/blog/tags/3d-printer/index.html @@ -606,7 +606,7 @@ hÃ¥per det ikke gÃ¥r tapt pÃ¥ samme vis.

2013

January (4)
January (5)

@@ -756,7 +756,7 @@ hÃ¥per det ikke gÃ¥r tapt pÃ¥ samme vis.

@@ -766,7 +766,7 @@ hÃ¥per det ikke gÃ¥r tapt pÃ¥ samme vis.

diff --git a/blog/tags/amiga/index.html b/blog/tags/amiga/index.html index c6e8b322ca..876698a35c 100644 --- a/blog/tags/amiga/index.html +++ b/blog/tags/amiga/index.html @@ -60,7 +60,7 @@ pakke. Kanskje Aros kunne vÃ¦rt interessant for et NUUG-foredrag?

2013

January (4)
January (5)

@@ -210,7 +210,7 @@ pakke. Kanskje Aros kunne vÃ¦rt interessant for et NUUG-foredrag?

@@ -220,7 +220,7 @@ pakke. Kanskje Aros kunne vÃ¦rt interessant for et NUUG-foredrag?

diff --git a/blog/tags/aros/index.html b/blog/tags/aros/index.html index 677d72ad55..2d1dd9cbe3 100644 --- a/blog/tags/aros/index.html +++ b/blog/tags/aros/index.html @@ -60,7 +60,7 @@ pakke. Kanskje Aros kunne vÃ¦rt interessant for et NUUG-foredrag?

2013

January (4)
January (5)

@@ -210,7 +210,7 @@ pakke. Kanskje Aros kunne vÃ¦rt interessant for et NUUG-foredrag?

@@ -220,7 +220,7 @@ pakke. Kanskje Aros kunne vÃ¦rt interessant for et NUUG-foredrag?

diff --git a/blog/tags/bankid/index.html b/blog/tags/bankid/index.html index 0d34012714..456d44e150 100644 --- a/blog/tags/bankid/index.html +++ b/blog/tags/bankid/index.html @@ -466,7 +466,7 @@ til BankID-modellen.

2013

January (4)
January (5)

@@ -616,7 +616,7 @@ til BankID-modellen.

@@ -626,7 +626,7 @@ til BankID-modellen.

diff --git a/blog/tags/bitcoin/index.html b/blog/tags/bitcoin/index.html index 14540dd267..b050c084f3 100644 --- a/blog/tags/bitcoin/index.html +++ b/blog/tags/bitcoin/index.html @@ -370,7 +370,7 @@ donations to the address

2013

January (4)
January (5)

@@ -520,7 +520,7 @@ donations to the address

@@ -530,7 +530,7 @@ donations to the address

diff --git a/blog/tags/bootsystem/index.html b/blog/tags/bootsystem/index.html index b8c6142db5..654da74765 100644 --- a/blog/tags/bootsystem/index.html +++ b/blog/tags/bootsystem/index.html @@ -767,7 +767,7 @@ insserv'. Will need to test if that work. :)

2013

January (4)
January (5)

@@ -917,7 +917,7 @@ insserv'. Will need to test if that work. :)

@@ -927,7 +927,7 @@ insserv'. Will need to test if that work. :)

diff --git a/blog/tags/bsa/index.html b/blog/tags/bsa/index.html index 2d5dc3151b..f02673fc29 100644 --- a/blog/tags/bsa/index.html +++ b/blog/tags/bsa/index.html @@ -148,7 +148,7 @@ pÃ¥ Slashdot.

2013

January (4)
January (5)

@@ -298,7 +298,7 @@ pÃ¥ Slashdot.

@@ -308,7 +308,7 @@ pÃ¥ Slashdot.

diff --git a/blog/tags/debian edu/index.html b/blog/tags/debian edu/index.html index ce5ff50e08..fc953d3b54 100644 --- a/blog/tags/debian edu/index.html +++ b/blog/tags/debian edu/index.html @@ -10578,7 +10578,7 @@ be the only one fitting our needs. :/

2013

January (4)
January (5)

@@ -10728,7 +10728,7 @@ be the only one fitting our needs. :/

@@ -10738,7 +10738,7 @@ be the only one fitting our needs. :/

diff --git a/blog/tags/debian/debian.rss b/blog/tags/debian/debian.rss index d8af9754e0..392ad7f7ed 100644 --- a/blog/tags/debian/debian.rss +++ b/blog/tags/debian/debian.rss @@ -6,6 +6,257 @@ http://people.skolelinux.org/pere/blog/ + + Modalias strings - a practical way to map "stuff" to hardware + http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html + http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html + Mon, 14 Jan 2013 11:10:00 +0100 + While looking into how to look up Debian packages based on hardware +information, to find the packages that support a given piece of +hardware, I refreshed my memory regarding modalias values, and decided +to document the details. Here are my findings so far, also available +in +<a href="http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/">the +Debian Edu subversion repository</a>: + +Modalias decoded + +This document try to explain what the different types of modalias +values stands for. It is in part based on information from +<URL: <a href="https://wiki.archlinux.org/index.php/Modalias">https://wiki.archlinux.org/index.php/Modalias</a> >, +<URL: <a href="http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device">http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device</a> >, +<URL: <a href="http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c">http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c</a> > and +<URL: <a href="http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&view=markup">http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&view=markup</a> >. + +The modalias entries for a given Linux machine can be found using +this shell script: + +<pre> +cat $(find /sys -name modalias) | sort -u +</pre> + +The supported modalias globs for a given kernel module can be found +using modinfo: + +<pre> +% /sbin/modinfo psmouse | grep alias: +alias: serio:ty05pr*id*ex* +alias: serio:ty01pr*id*ex* +% +</pre> + +PCI subtype + +A typical PCI entry can look like this. This is an Intel Host +Bridge memory controller: + +<blockquote> +pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00 +</blockquote> + +This represent these values: + +<pre> + v 00008086 (vendor) + d 00002770 (device) + sv 00001028 (subvendor) + sd 000001AD (subdevice) + bc 06 (bus class) + sc 00 (bus subclass) + i 00 (interface) +</pre> + +The vendor/device values are the same values outputted from 'lspci +-n' as 8086:2770. The bus class/subclass is also shown by lspci as +0600. The 0600 class is a host bridge. Other useful bus values are +0300 (VGA compatible card) and 0200 (Ethernet controller). + +Not sure how to figure out the interface value, nor what it +means. + +USB subtype + +Some typical USB entries can look like this. This is an internal +USB hub in a laptop: + +<blockquote> +usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00 +</blockquote> + +Here is the values included in this alias: + +<pre> + v 1D6B (device vendor) + p 0001 (device product) + d 0206 (bcddevice) + dc 09 (device class) + dsc 00 (device subclass) + dp 00 (device protocol) + ic 09 (interface class) + isc 00 (interface subclass) + ip 00 (interface protocol) +</pre> + +The 0900 device class/subclass means hub. Some times the relevant +class is in the interface class section. For a simple USB web camera, +these alias entries show up: + +<blockquote> +usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00 + usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00 + usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00 + usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00 +</blockquote> + +Interface class 0E01 is video control, 0E02 is video streaming (aka +camera), 0101 is audio control device and 0102 is audio streaming (aka +microphone). Thus this is a camera with microphone included. + +ACPI subtype + +The ACPI type is used for several non-PCI/USB stuff. This is an IR +receiver in a Thinkpad X40: + +<blockquote> +acpi:IBM0071:PNP0511: +</blockquote> + +The values between the colons are IDs. + +DMI subtype + +The DMI table contain lots of information about the computer case +and model. This is an entry for a IBM Thinkpad X40, fetched from +/sys/devices/virtual/dmi/id/modalias: + +<blockquote> +dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: +</blockquote> + +The values present are + +<pre> + bvn IBM (BIOS vendor) + bvr 1UETB6WW(1.66) (BIOS version) + bd 06/15/2005 (BIOS date) + svn IBM (system vendor) + pn 2371H4G (product name) + pvr ThinkPadX40 (product version) + rvn IBM (board vendor) + rn 2371H4G (board name) + rvr NotAvailable (board version) + cvn IBM (chassis vendor) + ct 10 (chassis type) + cvr NotAvailable (chassis version) +</pre> + +The chassis type 10 is Notebook. Other interesting values can be +found in the dmidecode source: + +<pre> + 3 Desktop + 4 Low Profile Desktop + 5 Pizza Box + 6 Mini Tower + 7 Tower + 8 Portable + 9 Laptop + 10 Notebook + 11 Hand Held + 12 Docking Station + 13 All In One + 14 Sub Notebook + 15 Space-saving + 16 Lunch Box + 17 Main Server Chassis + 18 Expansion Chassis + 19 Sub Chassis + 20 Bus Expansion Chassis + 21 Peripheral Chassis + 22 RAID Chassis + 23 Rack Mount Chassis + 24 Sealed-case PC + 25 Multi-system + 26 CompactPCI + 27 AdvancedTCA + 28 Blade + 29 Blade Enclosing +</pre> + +The chassis type values are not always accurately set in the DMI +table. For example my home server is a tower, but the DMI modalias +claim it is a desktop. + +SerIO subtype + +This type is used for PS/2 mouse plugs. One example is from my +test machine: + +<blockquote> +serio:ty01pr00id00ex00 +</blockquote> + +The values present are + +<pre> + ty 01 (type) + pr 00 (prototype) + id 00 (id) + ex 00 (extra) +</pre> + +This type is supported by the psmouse driver. I am not sure what +the valid values are. + +Other subtypes + +There are heaps of other modalias subtypes according to +file2alias.c. There is the rest of the list from that source: amba, +ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp, +mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio, +vmbus, x86cpu and zorro. I did not spend time documenting all of +these, as they do not seem relevant for my intended use with mapping +hardware to packages when new stuff is inserted during run time. + +Looking up kernel modules using modalias values + +To check which kernel modules provide support for a given modalias, +one can use the following shell script: + +<pre> + for id in $(cat $(find /sys -name modalias)|sort -u); do \ + echo "$id" ; \ + /sbin/modprobe --show-depends "$id"|sed 's/^/ /' ; \ + done +</pre> + +The output can look like this (only the first few entries as the +list is very long on my test machine): + +<pre> + acpi:ACPI0003: + insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko + acpi:device: + FATAL: Module acpi:device: not found. + acpi:IBM0068: + insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko + insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko + insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko + insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko + acpi:IBM0071:PNP0511: + insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko + insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko + insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko + [...] +</pre> + +If you want to help implementing a system to let us propose what +packages to install when new hardware is plugged into a Debian +machine, please send me an email or talk to me on +<a href="irc://irc.debian.org/%23debian-devel">#debian-devel</a>. + + + Moved the pymissile Debian packaging to collab-maint http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html diff --git a/blog/tags/debian/index.html b/blog/tags/debian/index.html index 757d508684..f5659563c7 100644 --- a/blog/tags/debian/index.html +++ b/blog/tags/debian/index.html @@ -20,6 +20,269 @@

Entries tagged "debian".

+ Modalias strings - a practical way to map "stuff" to hardware +

+ 14th January 2013 +

Modalias decoded

+ +

The modalias entries for a given Linux machine can be found using +this shell script:

+ +

+cat $(find /sys -name modalias) | sort -u
+

+ +

The supported modalias globs for a given kernel module can be found +using modinfo:

+ +

+% /sbin/modinfo psmouse | grep alias:
+alias:          serio:ty05pr*id*ex*
+alias:          serio:ty01pr*id*ex*
+%
+

+ +

PCI subtype

+ +

A typical PCI entry can look like this. This is an Intel Host +Bridge memory controller:

+ +

+pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00 +

+ +

This represent these values:

+ +

+ v   00008086  (vendor)
+ d   00002770  (device)
+ sv  00001028  (subvendor)
+ sd  000001AD  (subdevice)
+ bc  06        (bus class)
+ sc  00        (bus subclass)
+ i   00        (interface)
+

+ +

Not sure how to figure out the interface value, nor what it +means.

+ +

USB subtype

+ +

Some typical USB entries can look like this. This is an internal +USB hub in a laptop:

+ +

+usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00 +

+ +

Here is the values included in this alias:

+ +

+ v    1D6B  (device vendor)
+ p    0001  (device product)
+ d    0206  (bcddevice)
+ dc     09  (device class)
+ dsc    00  (device subclass)
+ dp     00  (device protocol)
+ ic     09  (interface class)
+ isc    00  (interface subclass)
+ ip     00  (interface protocol)
+

+ +

The 0900 device class/subclass means hub. Some times the relevant +class is in the interface class section. For a simple USB web camera, +these alias entries show up:

+ +

+usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00 +
usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00 +
usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00 +
usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00 +

+ +

ACPI subtype

+ +

The ACPI type is used for several non-PCI/USB stuff. This is an IR +receiver in a Thinkpad X40:

+ +

+acpi:IBM0071:PNP0511: +

+ +

The values between the colons are IDs.

+ +

DMI subtype

+ +

The DMI table contain lots of information about the computer case +and model. This is an entry for a IBM Thinkpad X40, fetched from +/sys/devices/virtual/dmi/id/modalias:

+ +

+dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: +

+ +

The values present are

+ +

+ bvn  IBM            (BIOS vendor)
+ bvr  1UETB6WW(1.66) (BIOS version)
+ bd   06/15/2005     (BIOS date)
+ svn  IBM            (system vendor)
+ pn   2371H4G        (product name)
+ pvr  ThinkPadX40    (product version)
+ rvn  IBM            (board vendor)
+ rn   2371H4G        (board name)
+ rvr  NotAvailable   (board version)
+ cvn  IBM            (chassis vendor)
+ ct   10             (chassis type)
+ cvr  NotAvailable   (chassis version)
+

+ +

The chassis type 10 is Notebook. Other interesting values can be +found in the dmidecode source:

+ +

+  3 Desktop
+  4 Low Profile Desktop
+  5 Pizza Box
+  6 Mini Tower
+  7 Tower
+  8 Portable
+  9 Laptop
+ 10 Notebook
+ 11 Hand Held
+ 12 Docking Station
+ 13 All In One
+ 14 Sub Notebook
+ 15 Space-saving
+ 16 Lunch Box
+ 17 Main Server Chassis
+ 18 Expansion Chassis
+ 19 Sub Chassis
+ 20 Bus Expansion Chassis
+ 21 Peripheral Chassis
+ 22 RAID Chassis
+ 23 Rack Mount Chassis
+ 24 Sealed-case PC
+ 25 Multi-system
+ 26 CompactPCI
+ 27 AdvancedTCA
+ 28 Blade
+ 29 Blade Enclosing
+

+ +

The chassis type values are not always accurately set in the DMI +table. For example my home server is a tower, but the DMI modalias +claim it is a desktop.

+ +

SerIO subtype

+ +

This type is used for PS/2 mouse plugs. One example is from my +test machine:

+ +

+serio:ty01pr00id00ex00 +

+ +

The values present are

+ +

+  ty  01  (type)
+  pr  00  (prototype)
+  id  00  (id)
+  ex  00  (extra)
+

+ +

This type is supported by the psmouse driver. I am not sure what +the valid values are.

+ +

Other subtypes

+ +

Looking up kernel modules using modalias values

+ +

To check which kernel modules provide support for a given modalias, +one can use the following shell script:

+ +

+  for id in $(cat $(find /sys -name modalias)|sort -u); do \
+    echo "$id" ; \
+    /sbin/modprobe --show-depends "$id"|sed 's/^/  /' ; \
+  done
+

+ +

The output can look like this (only the first few entries as the +list is very long on my test machine):

+ +

+  acpi:ACPI0003:
+    insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko 
+  acpi:device:
+  FATAL: Module acpi:device: not found.
+  acpi:IBM0068:
+    insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko 
+    insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko 
+    insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko 
+    insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko 
+  acpi:IBM0071:PNP0511:
+    insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko 
+    insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko 
+    insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko 
+  [...]
+

+ +

If you want to help implementing a system to let us propose what +packages to install when new hardware is plugged into a Debian +machine, please send me an email or talk to me on +#debian-devel.

+ +

+ + + Tags: debian, english. + + +

Moved the pymissile Debian packaging to collab-maint @@ -4723,7 +4986,7 @@ be the only one fitting our needs. :/

2013

January (4)
January (5)

@@ -4873,7 +5136,7 @@ be the only one fitting our needs. :/

@@ -4883,7 +5146,7 @@ be the only one fitting our needs. :/

diff --git a/blog/tags/digistan/index.html b/blog/tags/digistan/index.html index 892ff270e9..0c9ce20828 100644 --- a/blog/tags/digistan/index.html +++ b/blog/tags/digistan/index.html @@ -1168,7 +1168,7 @@ produkter basert pÃ¥ standarden.

2013

January (4)
January (5)

@@ -1318,7 +1318,7 @@ produkter basert pÃ¥ standarden.

@@ -1328,7 +1328,7 @@ produkter basert pÃ¥ standarden.

diff --git a/blog/tags/docbook/index.html b/blog/tags/docbook/index.html index a65e1b6a9e..98401fcc6d 100644 --- a/blog/tags/docbook/index.html +++ b/blog/tags/docbook/index.html @@ -459,7 +459,7 @@ slik at du kan oppdatere direkte.

2013

January (4)
January (5)

@@ -609,7 +609,7 @@ slik at du kan oppdatere direkte.

@@ -619,7 +619,7 @@ slik at du kan oppdatere direkte.

diff --git a/blog/tags/drivstoffpriser/index.html b/blog/tags/drivstoffpriser/index.html index d4ed7ad616..2f14566b8d 100644 --- a/blog/tags/drivstoffpriser/index.html +++ b/blog/tags/drivstoffpriser/index.html @@ -489,7 +489,7 @@ en liste med stasjoner pÃ¥ samme format som PriserVedStasjoner.

2013

January (4)
January (5)

@@ -639,7 +639,7 @@ en liste med stasjoner pÃ¥ samme format som PriserVedStasjoner.

@@ -649,7 +649,7 @@ en liste med stasjoner pÃ¥ samme format som PriserVedStasjoner.

diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss index 8aa0804d0b..1282509281 100644 --- a/blog/tags/english/english.rss +++ b/blog/tags/english/english.rss @@ -6,6 +6,257 @@ http://people.skolelinux.org/pere/blog/ + + Modalias strings - a practical way to map "stuff" to hardware + http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html + http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html + Mon, 14 Jan 2013 11:10:00 +0100 + While looking into how to look up Debian packages based on hardware +information, to find the packages that support a given piece of +hardware, I refreshed my memory regarding modalias values, and decided +to document the details. Here are my findings so far, also available +in +<a href="http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/">the +Debian Edu subversion repository</a>: + +Modalias decoded + +This document try to explain what the different types of modalias +values stands for. It is in part based on information from +<URL: <a href="https://wiki.archlinux.org/index.php/Modalias">https://wiki.archlinux.org/index.php/Modalias</a> >, +<URL: <a href="http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device">http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device</a> >, +<URL: <a href="http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c">http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c</a> > and +<URL: <a href="http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&view=markup">http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&view=markup</a> >. + +The modalias entries for a given Linux machine can be found using +this shell script: + +<pre> +cat $(find /sys -name modalias) | sort -u +</pre> + +The supported modalias globs for a given kernel module can be found +using modinfo: + +<pre> +% /sbin/modinfo psmouse | grep alias: +alias: serio:ty05pr*id*ex* +alias: serio:ty01pr*id*ex* +% +</pre> + +PCI subtype + +A typical PCI entry can look like this. This is an Intel Host +Bridge memory controller: + +<blockquote> +pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00 +</blockquote> + +This represent these values: + +<pre> + v 00008086 (vendor) + d 00002770 (device) + sv 00001028 (subvendor) + sd 000001AD (subdevice) + bc 06 (bus class) + sc 00 (bus subclass) + i 00 (interface) +</pre> + +The vendor/device values are the same values outputted from 'lspci +-n' as 8086:2770. The bus class/subclass is also shown by lspci as +0600. The 0600 class is a host bridge. Other useful bus values are +0300 (VGA compatible card) and 0200 (Ethernet controller). + +Not sure how to figure out the interface value, nor what it +means. + +USB subtype + +Some typical USB entries can look like this. This is an internal +USB hub in a laptop: + +<blockquote> +usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00 +</blockquote> + +Here is the values included in this alias: + +<pre> + v 1D6B (device vendor) + p 0001 (device product) + d 0206 (bcddevice) + dc 09 (device class) + dsc 00 (device subclass) + dp 00 (device protocol) + ic 09 (interface class) + isc 00 (interface subclass) + ip 00 (interface protocol) +</pre> + +The 0900 device class/subclass means hub. Some times the relevant +class is in the interface class section. For a simple USB web camera, +these alias entries show up: + +<blockquote> +usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00 + usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00 + usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00 + usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00 +</blockquote> + +Interface class 0E01 is video control, 0E02 is video streaming (aka +camera), 0101 is audio control device and 0102 is audio streaming (aka +microphone). Thus this is a camera with microphone included. + +ACPI subtype + +The ACPI type is used for several non-PCI/USB stuff. This is an IR +receiver in a Thinkpad X40: + +<blockquote> +acpi:IBM0071:PNP0511: +</blockquote> + +The values between the colons are IDs. + +DMI subtype + +The DMI table contain lots of information about the computer case +and model. This is an entry for a IBM Thinkpad X40, fetched from +/sys/devices/virtual/dmi/id/modalias: + +<blockquote> +dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: +</blockquote> + +The values present are + +<pre> + bvn IBM (BIOS vendor) + bvr 1UETB6WW(1.66) (BIOS version) + bd 06/15/2005 (BIOS date) + svn IBM (system vendor) + pn 2371H4G (product name) + pvr ThinkPadX40 (product version) + rvn IBM (board vendor) + rn 2371H4G (board name) + rvr NotAvailable (board version) + cvn IBM (chassis vendor) + ct 10 (chassis type) + cvr NotAvailable (chassis version) +</pre> + +The chassis type 10 is Notebook. Other interesting values can be +found in the dmidecode source: + +<pre> + 3 Desktop + 4 Low Profile Desktop + 5 Pizza Box + 6 Mini Tower + 7 Tower + 8 Portable + 9 Laptop + 10 Notebook + 11 Hand Held + 12 Docking Station + 13 All In One + 14 Sub Notebook + 15 Space-saving + 16 Lunch Box + 17 Main Server Chassis + 18 Expansion Chassis + 19 Sub Chassis + 20 Bus Expansion Chassis + 21 Peripheral Chassis + 22 RAID Chassis + 23 Rack Mount Chassis + 24 Sealed-case PC + 25 Multi-system + 26 CompactPCI + 27 AdvancedTCA + 28 Blade + 29 Blade Enclosing +</pre> + +The chassis type values are not always accurately set in the DMI +table. For example my home server is a tower, but the DMI modalias +claim it is a desktop. + +SerIO subtype + +This type is used for PS/2 mouse plugs. One example is from my +test machine: + +<blockquote> +serio:ty01pr00id00ex00 +</blockquote> + +The values present are + +<pre> + ty 01 (type) + pr 00 (prototype) + id 00 (id) + ex 00 (extra) +</pre> + +This type is supported by the psmouse driver. I am not sure what +the valid values are. + +Other subtypes + +There are heaps of other modalias subtypes according to +file2alias.c. There is the rest of the list from that source: amba, +ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp, +mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio, +vmbus, x86cpu and zorro. I did not spend time documenting all of +these, as they do not seem relevant for my intended use with mapping +hardware to packages when new stuff is inserted during run time. + +Looking up kernel modules using modalias values + +To check which kernel modules provide support for a given modalias, +one can use the following shell script: + +<pre> + for id in $(cat $(find /sys -name modalias)|sort -u); do \ + echo "$id" ; \ + /sbin/modprobe --show-depends "$id"|sed 's/^/ /' ; \ + done +</pre> + +The output can look like this (only the first few entries as the +list is very long on my test machine): + +<pre> + acpi:ACPI0003: + insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko + acpi:device: + FATAL: Module acpi:device: not found. + acpi:IBM0068: + insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko + insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko + insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko + insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko + acpi:IBM0071:PNP0511: + insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko + insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko + insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko + [...] +</pre> + +If you want to help implementing a system to let us propose what +packages to install when new hardware is plugged into a Debian +machine, please send me an email or talk to me on +<a href="irc://irc.debian.org/%23debian-devel">#debian-devel</a>. + + + Moved the pymissile Debian packaging to collab-maint http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html diff --git a/blog/tags/english/index.html b/blog/tags/english/index.html index d2bd8076aa..a2f15d1a62 100644 --- a/blog/tags/english/index.html +++ b/blog/tags/english/index.html @@ -20,6 +20,269 @@

Entries tagged "english".

+ Modalias strings - a practical way to map "stuff" to hardware +

+ 14th January 2013 +

Modalias decoded

+ +

The modalias entries for a given Linux machine can be found using +this shell script:

+ +

+cat $(find /sys -name modalias) | sort -u
+

+ +

The supported modalias globs for a given kernel module can be found +using modinfo:

+ +

+% /sbin/modinfo psmouse | grep alias:
+alias:          serio:ty05pr*id*ex*
+alias:          serio:ty01pr*id*ex*
+%
+

+ +

PCI subtype

+ +

A typical PCI entry can look like this. This is an Intel Host +Bridge memory controller:

+ +

+pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00 +

+ +

This represent these values:

+ +

+ v   00008086  (vendor)
+ d   00002770  (device)
+ sv  00001028  (subvendor)
+ sd  000001AD  (subdevice)
+ bc  06        (bus class)
+ sc  00        (bus subclass)
+ i   00        (interface)
+

+ +

Not sure how to figure out the interface value, nor what it +means.

+ +

USB subtype

+ +

Some typical USB entries can look like this. This is an internal +USB hub in a laptop:

+ +

+usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00 +

+ +

Here is the values included in this alias:

+ +

+ v    1D6B  (device vendor)
+ p    0001  (device product)
+ d    0206  (bcddevice)
+ dc     09  (device class)
+ dsc    00  (device subclass)
+ dp     00  (device protocol)
+ ic     09  (interface class)
+ isc    00  (interface subclass)
+ ip     00  (interface protocol)
+

+ +

The 0900 device class/subclass means hub. Some times the relevant +class is in the interface class section. For a simple USB web camera, +these alias entries show up:

+ +

+usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00 +
usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00 +
usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00 +
usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00 +

+ +

ACPI subtype

+ +

The ACPI type is used for several non-PCI/USB stuff. This is an IR +receiver in a Thinkpad X40:

+ +

+acpi:IBM0071:PNP0511: +

+ +

The values between the colons are IDs.

+ +

DMI subtype

+ +

The DMI table contain lots of information about the computer case +and model. This is an entry for a IBM Thinkpad X40, fetched from +/sys/devices/virtual/dmi/id/modalias:

+ +

+dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: +

+ +

The values present are

+ +

+ bvn  IBM            (BIOS vendor)
+ bvr  1UETB6WW(1.66) (BIOS version)
+ bd   06/15/2005     (BIOS date)
+ svn  IBM            (system vendor)
+ pn   2371H4G        (product name)
+ pvr  ThinkPadX40    (product version)
+ rvn  IBM            (board vendor)
+ rn   2371H4G        (board name)
+ rvr  NotAvailable   (board version)
+ cvn  IBM            (chassis vendor)
+ ct   10             (chassis type)
+ cvr  NotAvailable   (chassis version)
+

+ +

The chassis type 10 is Notebook. Other interesting values can be +found in the dmidecode source:

+ +

+  3 Desktop
+  4 Low Profile Desktop
+  5 Pizza Box
+  6 Mini Tower
+  7 Tower
+  8 Portable
+  9 Laptop
+ 10 Notebook
+ 11 Hand Held
+ 12 Docking Station
+ 13 All In One
+ 14 Sub Notebook
+ 15 Space-saving
+ 16 Lunch Box
+ 17 Main Server Chassis
+ 18 Expansion Chassis
+ 19 Sub Chassis
+ 20 Bus Expansion Chassis
+ 21 Peripheral Chassis
+ 22 RAID Chassis
+ 23 Rack Mount Chassis
+ 24 Sealed-case PC
+ 25 Multi-system
+ 26 CompactPCI
+ 27 AdvancedTCA
+ 28 Blade
+ 29 Blade Enclosing
+

+ +

The chassis type values are not always accurately set in the DMI +table. For example my home server is a tower, but the DMI modalias +claim it is a desktop.

+ +

SerIO subtype

+ +

This type is used for PS/2 mouse plugs. One example is from my +test machine:

+ +

+serio:ty01pr00id00ex00 +

+ +

The values present are

+ +

+  ty  01  (type)
+  pr  00  (prototype)
+  id  00  (id)
+  ex  00  (extra)
+

+ +

This type is supported by the psmouse driver. I am not sure what +the valid values are.

+ +

Other subtypes

+ +

Looking up kernel modules using modalias values

+ +

To check which kernel modules provide support for a given modalias, +one can use the following shell script:

+ +

+  for id in $(cat $(find /sys -name modalias)|sort -u); do \
+    echo "$id" ; \
+    /sbin/modprobe --show-depends "$id"|sed 's/^/  /' ; \
+  done
+

+ +

The output can look like this (only the first few entries as the +list is very long on my test machine):

+ +

+  acpi:ACPI0003:
+    insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko 
+  acpi:device:
+  FATAL: Module acpi:device: not found.
+  acpi:IBM0068:
+    insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko 
+    insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko 
+    insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko 
+    insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko 
+  acpi:IBM0071:PNP0511:
+    insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko 
+    insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko 
+    insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko 
+  [...]
+

+ +

If you want to help implementing a system to let us propose what +packages to install when new hardware is plugged into a Debian +machine, please send me an email or talk to me on +#debian-devel.

+ +

+ + + Tags: debian, english. + + +

Moved the pymissile Debian packaging to collab-maint @@ -12704,7 +12967,7 @@ be the only one fitting our needs. :/

2013