- <title>Modalias strings - a practical way to map "stuff" to hardware</title>
- <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
- <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
- <description><p>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>:
-
-<p><strong>Modalias decoded</strong></p>
-
-<p>This document try to explain what the different types of modalias
-values stands for. It is in part based on information from
-&lt;URL: <a href="https://wiki.archlinux.org/index.php/Modalias">https://wiki.archlinux.org/index.php/Modalias</a> &gt;,
-&lt;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> &gt;,
-&lt;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> &gt; and
-&lt;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> &gt;.
-
-<p>The modalias entries for a given Linux machine can be found using
-this shell script:</p>
-
-<pre>
-find /sys -name modalias -print0 | xargs -0 cat | sort -u
-</pre>
-
-<p>The supported modalias globs for a given kernel module can be found
-using modinfo:</p>
-
-<pre>
-% /sbin/modinfo psmouse | grep alias:
-alias: serio:ty05pr*id*ex*
-alias: serio:ty01pr*id*ex*
-%
-</pre>
-
-<p><strong>PCI subtype</strong></p>
-
-<p>A typical PCI entry can look like this. This is an Intel Host
-Bridge memory controller:</p>
-
-<p><blockquote>
-pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
-</blockquote></p>
-
-<p>This represent these values:</p>
-
-<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>
-
-<p>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).</p>
-
-<p>Not sure how to figure out the interface value, nor what it
-means.</p>
-
-<p><strong>USB subtype</strong></p>
-
-<p>Some typical USB entries can look like this. This is an internal
-USB hub in a laptop:</p>
-
-<p><blockquote>
-usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
-</blockquote></p>
-
-<p>Here is the values included in this alias:</p>
-
-<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>
-
-<p>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:</p>
-
-<p><blockquote>
-usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
-<br>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
-<br>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
-<br>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
-</blockquote></p>
-
-<p>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.</p>
-
-<p><strong>ACPI subtype</strong></p>
-
-<p>The ACPI type is used for several non-PCI/USB stuff. This is an IR
-receiver in a Thinkpad X40:</p>
-
-<p><blockquote>
-acpi:IBM0071:PNP0511:
-</blockquote></p>
-
-<p>The values between the colons are IDs.</p>
-
-<p><strong>DMI subtype</strong></p>
-
-<p>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:</p>
-
-<p><blockquote>
-dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
-</blockquote></p>
-
-<p>The values present are</p>
-
-<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>
-
-<p>The chassis type 10 is Notebook. Other interesting values can be
-found in the dmidecode source:</p>
-
-<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>
-
-<p>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.</p>
-
-<p><strong>SerIO subtype</strong></p>
-
-<p>This type is used for PS/2 mouse plugs. One example is from my
-test machine:</p>
-
-<p><blockquote>
-serio:ty01pr00id00ex00
-</blockquote></p>
-
-<p>The values present are</p>
-
-<pre>
- ty 01 (type)
- pr 00 (prototype)
- id 00 (id)
- ex 00 (extra)
-</pre>
-
-<p>This type is supported by the psmouse driver. I am not sure what
-the valid values are.</p>
-
-<p><strong>Other subtypes</strong></p>
-
-<p>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.</p>
-
-<p><strong>Looking up kernel modules using modalias values</strong></p>
-
-<p>To check which kernel modules provide support for a given modalias,
-one can use the following shell script:</p>
-
-<pre>
- for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
- echo "$id" ; \
- /sbin/modprobe --show-depends "$id"|sed 's/^/ /' ; \
- done
-</pre>
-
-<p>The output can look like this (only the first few entries as the
-list is very long on my test machine):</p>
-
-<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>
-
-<p>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>.</p>
-
-<p><strong>Update 2013-01-15:</strong> Rewrite "cat $(find ...)" to
-"find ... -print0 | xargs -0 cat" to make sure it handle directories
-in /sys/ with space in them.</p>
+ <title>Debian, the Linux distribution of choice for LEGO designers?</title>
+ <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
+ <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
+ <description><P>In January,
+<a href="http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html">I
+announced a</a> new <a href="irc://irc.debian.org/%23debian-lego">IRC
+channel #debian-lego</a>, for those of us in the Debian and Linux
+community interested in <a href="http://www.lego.com/">LEGO</a>, the
+marvellous construction system from Denmark. We also created
+<a href="http://wiki.debian.org/LegoDesigners">a wiki page</a> to have
+a place to take notes and write down our plans and hopes. And several
+people showed up to help. I was very happy to see the effect of my
+call. Since the small start, we have a debtags tag
+<a href="http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego">hardware::hobby:lego</a>
+tag for LEGO related packages, and now count 10 packages related to
+LEGO and <a href="http://mindstorms.lego.com/">Mindstorms</a>:</p>
+
+<p><table>
+<tr><td><a href="http://packages.qa.debian.org/brickos">brickos</a></td><td>alternative OS for LEGO Mindstorms RCX. Supports development in C/C++</td></tr>
+<tr><td><a href="http://packages.qa.debian.org/leocad">leocad</a></td><td>virtual brick CAD software</td></tr>
+<tr><td><a href="http://packages.qa.debian.org/libnxt">libnxt</a></td><td>utility library for talking to the LEGO Mindstorms NX</td></tr>
+<tr><td><a href="http://packages.qa.debian.org/lnpd">lnpd</a></td><td>daemon for LNP communication with BrickOS</td></tr>
+<tr><td><a href="http://packages.qa.debian.org/nbc">nbc</a></td><td>compiler for LEGO Mindstorms NXT bricks</td></tr>
+<tr><td><a href="http://packages.qa.debian.org/nqc">nqc</a></td><td>Not Quite C compiler for LEGO Mindstorms RCX</td></tr>
+<tr><td><a href="http://packages.qa.debian.org/python-nxt">python-nxt</a></td><td>python driver/interface/wrapper for the Lego Mindstorms NXT robot</td></tr>
+<tr><td><a href="http://packages.qa.debian.org/python-nxt-filer">python-nxt-filer</a></td><td>simple GUI to manage files on a LEGO Mindstorms NXT</td></tr>
+<tr><td><a href="http://packages.qa.debian.org/scratch">scratch</a></td><td>easy to use programming environment for ages 8 and up</td></tr>
+<tr><td><a href="http://packages.qa.debian.org/t2n">t2n</a></td><td>simple command-line tool for Lego NXT</td></tr>
+</table></p>
+
+<p>Some of these are available in Wheezy, and all but one are
+currently available in Jessie/testing. leocad is so far only
+available in experimental.</p>
+
+<p>If you care about LEGO in Debian, please join us on IRC and help
+adding the rest of the great free software tools available on Linux
+for LEGO designers.</p>
+</description>
+ </item>
+
+ <item>
+ <title>Narvik sparer minst 9 millioner på å bruke Skolelinux</title>
+ <link>http://people.skolelinux.org/pere/blog/Narvik_sparer_minst_9_millioner_p____bruke_Skolelinux.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Narvik_sparer_minst_9_millioner_p____bruke_Skolelinux.html</guid>
+ <pubDate>Fri, 10 May 2013 18:30:00 +0200</pubDate>
+ <description><p>I fjor sommer ble jeg
+<a href="http://people.skolelinux.org/pere/blog/Gladoppslag_om_Skolelinux_i_avisen_Fremover.html">gledelig
+overrasket</a> over et oppslag i avisen Fremover om Narvik kommunes
+bruk av <a href="http://www.skolelinux.org/">Skolelinux</a>. Oppslaget
+var basert på et notat som besvarte spørsmål fra ordfører Tor Nysæter
+og rådgiver for skolesektoren, Petter Falkbu, om bruken av Skolelinux
+i Narvikskolene og konstnaden ved å gå over til Windows. For litt
+over en uke siden siden fikk jeg endelig bedt kommunen om å få innsyn
+i dette notatet, og det ble oversendt på epost tirsdag. Jeg fikk
+<a href="http://www.nuug.no/pub/offentliginnsyn/from-Narvik-kommune/2013-04-29-09:12-skolelinux-notat/PetterFalkbuogwindowsfornarvikskolen%20(L)351310.pdf">lagt
+ut notatet</a> samme dag, og fikk i dag sjekket postlista til Narvik,
+der jeg fant notatet som
+<a href="https://www.narvik.kommune.no/innsyn.aspx?response=arkivsak_detaljer&arkivsakid=2013001023&scripturi=/innsyn.aspx&skin=infolink&Mid1=301&">sak
+2013/1023</a>.</p>
+
+<p>Notatet forteller at Narvik ville måtte betalt minst 9 millioner
+for å gå over til Windows på skolene. I tillegg dokumenterer notatet
+at læreplanens krav oppfylles uten problemer ved bruk av Skolelinux.
+Jeg anbefaler alle å lese de 10 sidene med gode argumenter for å kutte
+unødige utgifter på IT i skoleverket. :)</p>