1 <!DOCTYPE html PUBLIC
"-//W3C//DTD XHTML 1.0 Strict//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3 <html xmlns=
"http://www.w3.org/1999/xhtml" dir=
"ltr">
5 <meta http-equiv=
"Content-Type" content=
"text/html;charset=utf-8" />
6 <title>Petter Reinholdtsen
</title>
7 <link rel=
"stylesheet" type=
"text/css" media=
"screen" href=
"http://people.skolelinux.org/pere/blog/style.css" />
8 <link rel=
"stylesheet" type=
"text/css" media=
"screen" href=
"http://people.skolelinux.org/pere/blog/vim.css" />
9 <link rel=
"alternate" title=
"RSS Feed" href=
"http://people.skolelinux.org/pere/blog/index.rss" type=
"application/rss+xml" />
14 <a href=
"http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen
</a>
23 <div class=
"title"><a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html">Welcome to the world, Isenkram!
</a></div>
24 <div class=
"date">22nd January
2013</div>
25 <div class=
"body"><p>Yesterday, I
26 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html">asked
27 for testers
</a> for my prototype for making Debian better at handling
28 pluggable hardware devices, which I
29 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html">set
30 out to create
</a> earlier this month. Several valuable testers showed
31 up, and caused me to really want to to open up the development to more
32 people. But before I did this, I want to come up with a sensible name
33 for this project. Today I finally decided on a new name, and I have
34 renamed the project from hw-support-handler to this new name. In the
35 process, I moved the source to git and made it available as a
36 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git">collab-maint
</a>
37 repository in Debian. The new name? It is
<strong>Isenkram
</strong>.
38 To fetch and build the latest version of the source, use
</p>
41 git clone git://anonscm.debian.org/collab-maint/isenkram.git
42 cd isenkram && git-buildpackage
45 <p>I have not yet adjusted all files to use the new name yet. If you
46 want to hack on the source or improve the package, please go ahead.
47 But please talk to me first on IRC or via email before you do major
48 changes, to make sure we do not step on each others toes. :)
</p>
50 <p>If you wonder what 'isenkram' is, it is a Norwegian word for iron
51 stuff, typically meaning tools, nails, screws, etc. Typical hardware
52 stuff, in other words. I've been told it is the Norwegian variant of
53 the German word eisenkram, for those that are familiar with that
59 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>.
64 <div class=
"padding"></div>
67 <div class=
"title"><a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html">First prototype ready making hardware easier to use in Debian
</a></div>
68 <div class=
"date">21st January
2013</div>
69 <div class=
"body"><p>Early this month I set out to try to
70 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html">improve
71 the Debian support for pluggable hardware devices
</a>. Now my
72 prototype is working, and it is ready for a larger audience. To test
74 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/">source
75 from the Debian Edu subversion repository
</a>, build and install the
76 package. You might have to log out and in again activate the
79 <p>The design is simple:
</p>
83 <li>Add desktop entry in /usr/share/autostart/ causing a program
84 hw-support-handlerd to start when the user log in.
</li>
86 <li>This program listen for kernel events about new hardware (directly
87 from the kernel like udev does), not using HAL dbus events as I
90 <li>When new hardware is inserted, look up the hardware modalias in
91 the APT database, a database
92 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup">available
93 via HTTP
</a> and a database available as part of the package.
</li>
95 <li>If a package is mapped to the hardware in question, the package
96 isn't installed yet and this is the first time the hardware was
97 plugged in, show a desktop notification suggesting to install the
98 package or packages.
</li>
100 <li>If the user click on the 'install package now' button, ask
101 aptdaemon via the PackageKit API to install the requrired package.
</li>
103 <li>aptdaemon ask for root password or sudo password, and install the
104 package while showing progress information in a window.
</li>
108 <p>I still need to come up with a better name for the system. Here
109 are some screen shots showing the prototype in action. First the
110 notification, then the password request, and finally the request to
111 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p>
113 <p><img src=
"http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png">
114 <br><img src=
"http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png">
115 <br><img src=
"http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png">
116 <br><img src=
"http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png">
117 <br><img src=
"http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-5-installing-details.png" width=
"70%"></p>
119 <p>The prototype still need to be improved with longer timeouts, but
120 is already useful. The database of hardware to package mappings also
121 need more work. It is currently compatible with the Ubuntu way of
122 storing such information in the package control file, but could be
123 changed to use other formats instead or in addition to the current
124 method. I've dropped the use of discover for this mapping, as the
125 modalias approach is more flexible and easier to use on Linux as long
126 as the Linux kernel expose its modalias strings directly.
</p>
128 <p><strong>Update
2013-
01-
21 16:
50</strong>: Due to popular demand,
129 here is the command required to check out and build the source: Use
131 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
132 hw-support-handler; debuild
</tt>'. If you lack debuild, install the
133 devscripts package.
</p>
138 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>.
143 <div class=
"padding"></div>
146 <div class=
"title"><a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html">Thank you Thinkpad X41, for your long and trustworthy service
</a></div>
147 <div class=
"date">19th January
2013</div>
148 <div class=
"body"><p>This Christmas my trusty old laptop died. It died quietly and
149 suddenly in bed. With a quiet whimper, it went completely quiet and
150 black. The power button was no longer able to turn it on. It was a
151 IBM Thinkpad X41, and the best laptop I ever had. Better than both
152 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
153 Compaq I had before that. Now I need to find a replacement. To keep
154 going during Christmas, I moved the one year old SSD disk to my old
155 X40 where it fitted (only one I had left that could use it), but it is
156 not a durable solution.
158 <p>My laptop needs are fairly modest. This is my wishlist from when I
159 got a new one more than
10 years ago. It still holds true.:)
</p>
163 <li>Lightweight (around
1 kg) and small volume (preferably smaller
165 <li>Robust, it will be in my backpack every day.
</li>
166 <li>Three button mouse and a mouse pin instead of touch pad.
</li>
167 <li>Long battery life time. Preferable a week.
</li>
168 <li>Internal WIFI network card.
</li>
169 <li>Internal Twisted Pair network card.
</li>
170 <li>Some USB slots (
2-
3 is plenty)
</li>
171 <li>Good keyboard - similar to the Thinkpad.
</li>
172 <li>Video resolution at least
1024x768, with size around
12" (A4 paper
174 <li>Hardware supported by Debian Stable, ie the default kernel and
176 <li>Quiet, preferably fan free (or at least not using the fan most of
181 <p>You will notice that there are no RAM and CPU requirements in the
182 list. The reason is simply that the specifications on laptops the
183 last
10-
15 years have been sufficient for my needs, and I have to look
184 at other features to choose my laptop. But are there still made as
185 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
186 robust, and Thinkpads seem to be heading in the wrong direction since
187 Lenovo took over. But I've been told that X220 and X1 Carbon might
190 <p>Perhaps I should rethink my needs, and look for a pad with an
191 external keyboard? I'll have to check the
192 <a href=
"http://www.linux-laptop.net/">Linux Laptops site
</a> for
193 well-supported laptops, or perhaps just buy one preinstalled from one
194 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/">Linux
195 Pre-loaded site
</a>.
</p>
200 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>.
205 <div class=
"padding"></div>
208 <div class=
"title"><a href=
"http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html">How to find a browser plugin supporting a given MIME type
</a></div>
209 <div class=
"date">18th January
2013</div>
210 <div class=
"body"><p>Some times I try to figure out which Iceweasel browser plugin to
211 install to get support for a given MIME type. Thanks to
212 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins">specifications
213 done by Ubuntu
</a> and Mozilla, it is possible to do this in Debian.
214 Unfortunately, not very many packages provide the needed meta
215 information, Anyway, here is a small script to look up all browser
216 plugin packages announcing ther MIME support using this specification:
</p>
222 def pkgs_handling_mimetype(mimetype):
227 version = pkg.candidate
229 version = pkg.installed
232 record = version.record
233 if not record.has_key('Npp-MimeType'):
235 mime_types = record['Npp-MimeType'].split(',')
237 t = t.rstrip().strip()
239 thepkgs.append(pkg.name)
241 mimetype = "audio/ogg"
242 if
1 < len(sys.argv):
243 mimetype = sys.argv[
1]
244 print "Browser plugin packages supporting %s:" % mimetype
245 for pkg in pkgs_handling_mimetype(mimetype):
249 <p>It can be used like this to look up a given MIME type:
</p>
252 % ./apt-find-browserplug-for-mimetype
253 Browser plugin packages supporting audio/ogg:
255 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
256 Browser plugin packages supporting application/x-shockwave-flash:
261 <p>In Ubuntu this mechanism is combined with support in the browser
262 itself to query for plugins and propose to install the needed
263 packages. It would be great if Debian supported such feature too. Is
264 anyone working on adding it?
</p>
266 <p><strong>Update
2013-
01-
18 14:
20</strong>: The Debian BTS
267 request for icweasel support for this feature is
268 <a href=
"http://bugs.debian.org/484010">#
484010</a> from
2008 (and
269 <a href=
"http://bugs.debian.org/698426">#
698426</a> from today). Lack
270 of manpower and wish for a different design is the reason thus feature
271 is not yet in iceweasel from Debian.
</p>
276 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>.
281 <div class=
"padding"></div>
284 <div class=
"title"><a href=
"http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html">What is the most supported MIME type in Debian?
</a></div>
285 <div class=
"date">16th January
2013</div>
286 <div class=
"body"><p>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal">DEP-
11
287 proposal to add AppStream information to the Debian archive
</a>, is a
288 proposal to make it possible for a Desktop application to propose to
289 the user some package to install to gain support for a given MIME
290 type, font, library etc. that is currently missing. With such
291 mechanism in place, it would be possible for the desktop to
292 automatically propose and install leocad if some LDraw file is
293 downloaded by the browser.
</p>
295 <p>To get some idea about the current content of the archive, I decided
296 to write a simple program to extract all .desktop files from the
297 Debian archive and look up the claimed MIME support there. The result
299 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest">Skolelinux FTP
300 site
</a>. Using the collected information, it become possible to
301 answer the question in the title. Here are the
20 most supported MIME
302 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
303 The complete list is available from the link above.
</p>
305 <p><strong>Debian Stable:
</strong></p>
309 ----- -----------------------
332 <p><strong>Debian Testing:
</strong></p>
336 ----- -----------------------
359 <p><strong>Debian Unstable:
</strong></p>
363 ----- -----------------------
386 <p>I am told that PackageKit can provide an API to access the kind of
387 information mentioned in DEP-
11. I have not yet had time to look at
388 it, but hope the PackageKit people in Debian are on top of these
391 <p><strong>Update
2013-
01-
16 13:
35</strong>: Updated numbers after
392 discovering a typo in my script.
</p>
397 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>.
402 <div class=
"padding"></div>
405 <div class=
"title"><a href=
"http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html">Using modalias info to find packages handling my hardware
</a></div>
406 <div class=
"date">15th January
2013</div>
407 <div class=
"body"><p>Yesterday, I wrote about the
408 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html">modalias
409 values provided by the Linux kernel
</a> following my hope for
410 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html">better
411 dongle support in Debian
</a>. Using this knowledge, I have tested how
412 modalias values attached to package names can be used to map packages
413 to hardware. This allow the system to look up and suggest relevant
414 packages when I plug in some new hardware into my machine, and replace
415 discover and discover-data as the database used to map hardware to
418 <p>I create a modaliases file with entries like the following,
419 containing package name, kernel module name (if relevant, otherwise
420 the package name) and globs matching the relevant hardware
424 Package: package-name
425 <br>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p>
428 <p>It is fairly trivial to write code to find the relevant packages
429 for a given modalias value using this file.
</p>
431 <p>An entry like this would suggest the video and picture application
432 cheese for many USB web cameras (interface bus class
0E01):
</p>
436 <br>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p>
439 <p>An entry like this would suggest the pcmciautils package when a
440 CardBus bridge (bus class
0607) PCI device is present:
</p>
444 <br>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
447 <p>An entry like this would suggest the package colorhug-client when
448 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p>
451 Package: colorhug-client
452 <br>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p>
455 <p>I believe the format is compatible with the format of the Packages
456 file in the Debian archive. Ubuntu already uses their Packages file
457 to store their mappings from packages to hardware.
</p>
459 <p>By adding a XB-Modaliases: header in debian/control, any .deb can
460 announce the hardware it support in a way my prototype understand.
461 This allow those publishing packages in an APT source outside the
462 Debian archive as well as those backporting packages to make sure the
463 hardware mapping are included in the package meta information. I've
464 tested such header in the pymissile package, and its modalias mapping
465 is working as it should with my prototype. It even made it to Ubuntu
468 <p>To test if it was possible to look up supported hardware using only
469 the shell tools available in the Debian installer, I wrote a shell
470 implementation of the lookup code. The idea is to create files for
471 each modalias and let the shell do the matching. Please check out and
473 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co">hw-support-lookup
</a>
474 shell script. It run without any extra dependencies and fetch the
475 hardware mappings from the Debian archive and the subversion
476 repository where I currently work on my prototype.
</p>
478 <p>When I use it on a machine with a yubikey inserted, it suggest to
479 install yubikey-personalization:
</p>
482 % ./hw-support-lookup
483 <br>yubikey-personalization
487 <p>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
488 propose to install the pcmciautils package:
</p>
491 % ./hw-support-lookup
496 <p>If you know of any hardware-package mapping that should be added to
497 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co">my
498 database
</a>, please tell me about it.
</p>
500 <p>It could be possible to generate several of the mappings between
501 packages and hardware. One source would be to look at packages with
502 kernel modules, ie packages with *.ko files in /lib/modules/, and
503 extract their modalias information. Another would be to look at
504 packages with udev rules, ie packages with files in
505 /lib/udev/rules.d/, and extract their vendor/model information to
506 generate a modalias matching rule. I have not tested any of these to
509 <p>If you want to help implementing a system to let us propose what
510 packages to install when new hardware is plugged into a Debian
511 machine, please send me an email or talk to me on
512 <a href=
"irc://irc.debian.org/%23debian-devel">#debian-devel
</a>.
</p>
517 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>.
522 <div class=
"padding"></div>
525 <div class=
"title"><a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html">Modalias strings - a practical way to map "stuff" to hardware
</a></div>
526 <div class=
"date">14th January
2013</div>
527 <div class=
"body"><p>While looking into how to look up Debian packages based on hardware
528 information, to find the packages that support a given piece of
529 hardware, I refreshed my memory regarding modalias values, and decided
530 to document the details. Here are my findings so far, also available
532 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/">the
533 Debian Edu subversion repository
</a>:
535 <p><strong>Modalias decoded
</strong></p>
537 <p>This document try to explain what the different types of modalias
538 values stands for. It is in part based on information from
539 <URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias">https://wiki.archlinux.org/index.php/Modalias
</a> >,
540 <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> >,
541 <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
542 <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> >.
544 <p>The modalias entries for a given Linux machine can be found using
545 this shell script:
</p>
548 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
551 <p>The supported modalias globs for a given kernel module can be found
555 % /sbin/modinfo psmouse | grep alias:
556 alias: serio:ty05pr*id*ex*
557 alias: serio:ty01pr*id*ex*
561 <p><strong>PCI subtype
</strong></p>
563 <p>A typical PCI entry can look like this. This is an Intel Host
564 Bridge memory controller:
</p>
567 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
570 <p>This represent these values:
</p>
575 sv
00001028 (subvendor)
576 sd
000001AD (subdevice)
582 <p>The vendor/device values are the same values outputted from 'lspci
583 -n' as
8086:
2770. The bus class/subclass is also shown by lspci as
584 0600. The
0600 class is a host bridge. Other useful bus values are
585 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p>
587 <p>Not sure how to figure out the interface value, nor what it
590 <p><strong>USB subtype
</strong></p>
592 <p>Some typical USB entries can look like this. This is an internal
593 USB hub in a laptop:
</p>
596 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
599 <p>Here is the values included in this alias:
</p>
602 v
1D6B (device vendor)
603 p
0001 (device product)
606 dsc
00 (device subclass)
607 dp
00 (device protocol)
608 ic
09 (interface class)
609 isc
00 (interface subclass)
610 ip
00 (interface protocol)
613 <p>The
0900 device class/subclass means hub. Some times the relevant
614 class is in the interface class section. For a simple USB web camera,
615 these alias entries show up:
</p>
618 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
619 <br>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
620 <br>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
621 <br>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
624 <p>Interface class
0E01 is video control,
0E02 is video streaming (aka
625 camera),
0101 is audio control device and
0102 is audio streaming (aka
626 microphone). Thus this is a camera with microphone included.
</p>
628 <p><strong>ACPI subtype
</strong></p>
630 <p>The ACPI type is used for several non-PCI/USB stuff. This is an IR
631 receiver in a Thinkpad X40:
</p>
634 acpi:IBM0071:PNP0511:
637 <p>The values between the colons are IDs.
</p>
639 <p><strong>DMI subtype
</strong></p>
641 <p>The DMI table contain lots of information about the computer case
642 and model. This is an entry for a IBM Thinkpad X40, fetched from
643 /sys/devices/virtual/dmi/id/modalias:
</p>
646 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
649 <p>The values present are
</p>
652 bvn IBM (BIOS vendor)
653 bvr
1UETB
6WW(
1.66) (BIOS version)
654 bd
06/
15/
2005 (BIOS date)
655 svn IBM (system vendor)
656 pn
2371H4G (product name)
657 pvr ThinkPadX40 (product version)
658 rvn IBM (board vendor)
659 rn
2371H4G (board name)
660 rvr NotAvailable (board version)
661 cvn IBM (chassis vendor)
663 cvr NotAvailable (chassis version)
666 <p>The chassis type
10 is Notebook. Other interesting values can be
667 found in the dmidecode source:
</p>
671 4 Low Profile Desktop
684 17 Main Server Chassis
687 20 Bus Expansion Chassis
688 21 Peripheral Chassis
690 23 Rack Mount Chassis
699 <p>The chassis type values are not always accurately set in the DMI
700 table. For example my home server is a tower, but the DMI modalias
701 claim it is a desktop.
</p>
703 <p><strong>SerIO subtype
</strong></p>
705 <p>This type is used for PS/
2 mouse plugs. One example is from my
709 serio:ty01pr00id00ex00
712 <p>The values present are
</p>
721 <p>This type is supported by the psmouse driver. I am not sure what
722 the valid values are.
</p>
724 <p><strong>Other subtypes
</strong></p>
726 <p>There are heaps of other modalias subtypes according to
727 file2alias.c. There is the rest of the list from that source: amba,
728 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
729 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
730 vmbus, x86cpu and zorro. I did not spend time documenting all of
731 these, as they do not seem relevant for my intended use with mapping
732 hardware to packages when new stuff is inserted during run time.
</p>
734 <p><strong>Looking up kernel modules using modalias values
</strong></p>
736 <p>To check which kernel modules provide support for a given modalias,
737 one can use the following shell script:
</p>
740 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
742 /sbin/modprobe --show-depends "$id"|sed 's/^/ /' ; \
746 <p>The output can look like this (only the first few entries as the
747 list is very long on my test machine):
</p>
751 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
753 FATAL: Module acpi:device: not found.
755 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
756 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
757 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
758 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
759 acpi:IBM0071:PNP0511:
760 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
761 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
762 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
766 <p>If you want to help implementing a system to let us propose what
767 packages to install when new hardware is plugged into a Debian
768 machine, please send me an email or talk to me on
769 <a href=
"irc://irc.debian.org/%23debian-devel">#debian-devel
</a>.
</p>
771 <p><strong>Update
2013-
01-
15:
</strong> Rewrite "cat $(find ...)" to
772 "find ... -print0 | xargs -
0 cat" to make sure it handle directories
773 in /sys/ with space in them.
</p>
778 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>.
783 <div class=
"padding"></div>
786 <div class=
"title"><a href=
"http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html">Moved the pymissile Debian packaging to collab-maint
</a></div>
787 <div class=
"date">10th January
2013</div>
788 <div class=
"body"><p>As part of my investigation on how to improve the support in Debian
789 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
790 Launcher and updated the Debian package
791 <a href=
"http://packages.qa.debian.org/pymissile">pymissile
</a> to make
792 sure udev will fix the device permissions when it is plugged in. I
793 also added a "Modaliases" header to test it in the Debian archive and
794 hopefully make the package be proposed by jockey in Ubuntu when a user
795 plug in his rocket launcher. In the process I moved the source to a
796 git repository under collab-maint, to make it easier for any DD to
797 contribute.
<a href=
"http://code.google.com/p/pymissile/">Upstream
</a>
798 is not very active, but the software still work for me even after five
799 years of relative silence. The new git repository is not listed in
800 the uploaded package yet, because I want to test the other changes a
801 bit more before I upload the new version. If you want to check out
802 the new version with a .desktop file included, visit the
803 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git">gitweb
804 view
</a> or use "
<tt>git clone
805 git://anonscm.debian.org/collab-maint/pymissile.git
</tt>".</p>
810 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian
">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english
">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/robot
">robot</a>.
815 <div class="padding
"></div>
818 <div class="title
"><a href="http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">Lets make hardware dongles easier to use in Debian</a></div>
819 <div class="date
"> 9th January 2013</div>
820 <div class="body
"><p>One thing that annoys me with Debian and Linux distributions in
821 general, is that there is a great package management system with the
822 ability to automatically install software packages by downloading them
823 from the distribution mirrors, but no way to get it to automatically
824 install the packages I need to use the hardware I plug into my
825 machine. Even if the package to use it is easily available from the
826 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
827 suggest to automatically install the python-nxt, nbc and t2n packages
828 I need to talk to it. When I plug in a Yubikey, it could propose the
829 yubikey-personalization package. The information required to do this
830 is available, but no-one have pulled all the pieces together.</p>
832 <p>Some years ago, I proposed to
833 <a href="http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
834 the discover subsystem to implement this</a>. The idea is fairly
839 <li>Add a desktop entry in /usr/share/autostart/ pointing to a program
840 starting when a user log in.</li>
842 <li>Set this program up to listen for kernel events emitted when new
843 hardware is inserted into the computer.</li>
845 <li>When new hardware is inserted, look up the hardware ID in a
846 database mapping to packages, and take note of any non-installed
849 <li>Show a message to the user proposing to install the discovered
850 package, and make it easy to install it.</li>
854 <p>I am not sure what the best way to implement this is, but my
855 initial idea was to use dbus events to discover new hardware, the
856 discover database to find packages and
857 <a href="http://www.packagekit.org/
">PackageKit</a> to install
860 <p>Yesterday, I found time to try to implement this idea, and the
861 draft package is now checked into
862 <a href="http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
863 Debian Edu subversion repository</a>. In the process, I updated the
864 <a href="http://packages.qa.debian.org/d/discover-data.html
">discover-data</a>
865 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
866 the relevant packages in Debian, and uploaded a new version
867 2.2013.01.09 to unstable. I also discovered that the current
868 <a href="http://packages.qa.debian.org/d/discover.html
">discover</a>
869 package in Debian no longer discovered any USB devices, because
870 /proc/bus/usb/devices is no longer present. I ported it to use
871 libusb as a fall back option to get it working. The fixed package
872 version 2.1.2-6 is now in experimental (didn't upload it to unstable
873 because of the freeze).</p>
875 <p>With this prototype in place, I can insert my Yubikey, and get this
876 desktop notification to show up (only once, the first time it is
879 <p align="center
"><img src="http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p>
881 <p>For this prototype to be really useful, some way to automatically
882 install the proposed packages by pressing the "Please install
883 program(s)" button should to be implemented.
</p>
885 <p>If this idea seem useful to you, and you want to help make it
886 happen, please help me update the discover-data database with mappings
887 from hardware to Debian packages. Check if 'discover-pkginstall -l'
888 list the package you would like to have installed when a given
889 hardware device is inserted into your computer, and report bugs using
890 reportbug if it isn't. Or, if you know of a better way to provide
891 such mapping, please let me know.
</p>
893 <p>This prototype need more work, and there are several questions that
894 should be considered before it is ready for production use. Is dbus
895 the correct way to detect new hardware? At the moment I look for HAL
896 dbus events on the system bus, because that is the events I could see
897 on my Debian Squeeze KDE desktop. Are there better events to use?
898 How should the user be notified? Is the desktop notification
899 mechanism the best option, or should the background daemon raise a
900 popup instead? How should packages be installed? When should they
901 not be installed?
</p>
903 <p>If you want to help getting such feature implemented in Debian,
904 please send me an email. :)
</p>
909 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>.
914 <div class=
"padding"></div>
917 <div class=
"title"><a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html">New IRC channel for LEGO designers using Debian
</a></div>
918 <div class=
"date"> 2nd January
2013</div>
919 <div class=
"body"><p>During Christmas, I have worked a bit on the Debian support for
920 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx">LEGO Mindstorm
921 NXT
</a>. My son and I have played a bit with my NXT set, and I
922 discovered I had to build all the tools myself because none were
923 already in Debian Squeeze. If Debian support for LEGO is something
924 you care about, please join me on the IRC channel
925 <a href=
"irc://irc.debian.org/%23debian-lego">#debian-lego
</a> (server
926 irc.debian.org). There is a lot that could be done to improve the
927 Debian support for LEGO designers. For example both CAD software
928 and Mindstorm compilers are missing. :)
</p>
930 <p>Update
2012-
01-
03: A
931 <a href=
"http://wiki.debian.org/LegoDesigners">project page
</a>
932 including links to Lego related packages is now available.
</p>
937 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/robot">robot
</a>.
942 <div class=
"padding"></div>
944 <p style=
"text-align: right;"><a href=
"index.rss"><img src=
"http://people.skolelinux.org/pere/blog/xml.gif" alt=
"RSS feed" width=
"36" height=
"14" /></a></p>
955 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/01/">January (
11)
</a></li>
962 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/01/">January (
7)
</a></li>
964 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/02/">February (
10)
</a></li>
966 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/03/">March (
17)
</a></li>
968 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/04/">April (
12)
</a></li>
970 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/05/">May (
12)
</a></li>
972 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/06/">June (
20)
</a></li>
974 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/07/">July (
17)
</a></li>
976 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/08/">August (
6)
</a></li>
978 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/09/">September (
9)
</a></li>
980 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/10/">October (
17)
</a></li>
982 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/11/">November (
10)
</a></li>
984 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/12/">December (
7)
</a></li>
991 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/01/">January (
16)
</a></li>
993 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/02/">February (
6)
</a></li>
995 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/03/">March (
6)
</a></li>
997 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/04/">April (
7)
</a></li>
999 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/05/">May (
3)
</a></li>
1001 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/06/">June (
2)
</a></li>
1003 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/07/">July (
7)
</a></li>
1005 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/08/">August (
6)
</a></li>
1007 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/09/">September (
4)
</a></li>
1009 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/10/">October (
2)
</a></li>
1011 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/11/">November (
3)
</a></li>
1013 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/12/">December (
1)
</a></li>
1020 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/01/">January (
2)
</a></li>
1022 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/02/">February (
1)
</a></li>
1024 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/03/">March (
3)
</a></li>
1026 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/04/">April (
3)
</a></li>
1028 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/05/">May (
9)
</a></li>
1030 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/06/">June (
14)
</a></li>
1032 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/07/">July (
12)
</a></li>
1034 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/08/">August (
13)
</a></li>
1036 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/09/">September (
7)
</a></li>
1038 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/10/">October (
9)
</a></li>
1040 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/11/">November (
13)
</a></li>
1042 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/12/">December (
12)
</a></li>
1049 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/01/">January (
8)
</a></li>
1051 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/02/">February (
8)
</a></li>
1053 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/03/">March (
12)
</a></li>
1055 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/04/">April (
10)
</a></li>
1057 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/05/">May (
9)
</a></li>
1059 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/06/">June (
3)
</a></li>
1061 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/07/">July (
4)
</a></li>
1063 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/08/">August (
3)
</a></li>
1065 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/09/">September (
1)
</a></li>
1067 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/10/">October (
2)
</a></li>
1069 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/11/">November (
3)
</a></li>
1071 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/12/">December (
3)
</a></li>
1078 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2008/11/">November (
5)
</a></li>
1080 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2008/12/">December (
7)
</a></li>
1091 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (
13)
</a></li>
1093 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/amiga">amiga (
1)
</a></li>
1095 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/aros">aros (
1)
</a></li>
1097 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bankid">bankid (
4)
</a></li>
1099 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (
5)
</a></li>
1101 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (
12)
</a></li>
1103 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bsa">bsa (
2)
</a></li>
1105 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian (
69)
</a></li>
1107 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (
118)
</a></li>
1109 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/digistan">digistan (
9)
</a></li>
1111 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/docbook">docbook (
7)
</a></li>
1113 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (
4)
</a></li>
1115 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/english">english (
175)
</a></li>
1117 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (
21)
</a></li>
1119 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (
12)
</a></li>
1121 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (
10)
</a></li>
1123 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (
9)
</a></li>
1125 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/intervju">intervju (
32)
</a></li>
1127 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/kart">kart (
17)
</a></li>
1129 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/ldap">ldap (
8)
</a></li>
1131 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/lenker">lenker (
6)
</a></li>
1133 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (
1)
</a></li>
1135 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (
25)
</a></li>
1137 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/norsk">norsk (
219)
</a></li>
1139 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/nuug">nuug (
148)
</a></li>
1141 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (
6)
</a></li>
1143 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/open311">open311 (
2)
</a></li>
1145 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (
41)
</a></li>
1147 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/personvern">personvern (
61)
</a></li>
1149 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/raid">raid (
1)
</a></li>
1151 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/reprap">reprap (
11)
</a></li>
1153 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/rfid">rfid (
2)
</a></li>
1155 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/robot">robot (
6)
</a></li>
1157 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/rss">rss (
1)
</a></li>
1159 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/ruter">ruter (
4)
</a></li>
1161 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (
2)
</a></li>
1163 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (
28)
</a></li>
1165 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (
4)
</a></li>
1167 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (
4)
</a></li>
1169 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/standard">standard (
39)
</a></li>
1171 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (
3)
</a></li>
1173 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (
5)
</a></li>
1175 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (
12)
</a></li>
1177 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (
1)
</a></li>
1179 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/valg">valg (
7)
</a></li>
1181 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/video">video (
35)
</a></li>
1183 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (
4)
</a></li>
1185 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/web">web (
26)
</a></li>
1191 <p style=
"text-align: right">
1192 Created by
<a href=
"http://steve.org.uk/Software/chronicle">Chronicle v4.4
</a>