From: Petter Reinholdtsen Date: Fri, 27 Jan 2012 22:28:49 +0000 (+0000) Subject: Ny post. X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/d443d5780bc376a9465bb19cf0f3a1c684a12e66?ds=inline Ny post. --- diff --git a/blog/data/2012-01-27-skolelinux.txt b/blog/data/2012-01-27-skolelinux.txt index ef76eb2b56..18ed549200 100644 --- a/blog/data/2012-01-27-skolelinux.txt +++ b/blog/data/2012-01-27-skolelinux.txt @@ -1,50 +1,53 @@ Title: Handling non-free firmware in Debian Edu/Squeeze Tags: english, debian edu -Date: 2012-01-27 16:00 +Date: 2012-01-27 23:30 -

With non-free hardware, one need non-free firmware. This is a sad -fact of todays computers. In the next version of -Debian Edu / Skolelinux based on -Squeeze, we provide several scripts to make this easier to handle. -The common use case I run into is laptops with wireless network cards -needing non-free firmware, but there are other situations too.

+

With some computer hardware, one need non-free firmware blobs. +This is the sad fact of todays computers. In the next version of +Debian Edu / Skolelinux based +on Squeeze, we provide several scripts and modifications to make +firmware blobs easier to handle. The common use case I run into is a +laptop with a wireless network card requiring non-free firmware to +work, but there are other use cases as well.

-

First and foremost, we provide ISO images for DVD and CD with all -firmware packages in Debian included, to ensure debian-installer find -and can install it during installation. This take care firmware for -network devices used by the installer when installing from from local -media.

+

First and foremost, Debian Edu provide ISO images for DVD and CD +with all firmware packages in the Debian sections main and non-free +included, to ensure debian-installer find and can install all of them +during installation. This take care firmware for network devices used +by the installer when installing from from local media. But for +example multimedia devices are not activated in the installer and are +not taken care of by this.

-

Next, one might need other firmware blobs for non-network devices. -For these we provide a script +

For non-network devices, we provide the script /usr/share/debian-edu-config/tools/auto-addfirmware which -search through the dmesg output for requests for extra firmware, look -up the firmware files in the Contents-ARCH.gz files available in the -package repository, and install the packages providing the requested -firmware file(s). I have proposed to do something similar in -debian-installer (BTS report +search through the dmesg output for drivers requesting extra +firmware. The firmware file name is looked up in the Contents-ARCH.gz +file available in the package repository, and the packages providing +the requested firmware file(s) is installed. I have proposed to do +something similar in debian-installer (BTS report #655507), to allow PXE -installs of Debian to handle firmware installation with less manual -labour.

+installs of Debian to handle firmware installation better. Run the +script as root from the command line to fetch and install the needed +firmware packages.

Debian Edu provide PXE installation of Debian out of the box, and because some machines need firmware to get their network cards -working, the initrd some times need extra firmware included to be able -to install at all. To fill the PXE installation initrd with extra -firmware, the +working, the installation initrd some times need extra firmware +included to be able to install at all. To fill the PXE installation +initrd with extra firmware, the /usr/share/debian-edu-config/tools/pxe-addfirmware script is -provided.

+provided. Again, just run it as root on the command line to fill the +PXE initrd with firmware packages.

Last, some LTSP clients might also need firmware to get their network cards working. For this, /usr/share/debian-edu-config/tools/ltsp-addfirmware is -provided to update the LTSP initrd with firmware blobs.

+provided to update the LTSP initrd with firmware blobs. It is used +the same way as the other firmware related tools.

-

At the moment, we do not run any of these during installation, to -make the local administrator aware that they are using hardware that -need non-free files to function. We do not know if this is acceptable -to the administrator or not, and thus leave it as their choice to add -firmware or not.

+

At the moment, we do not run any of these during installation. We +do not know if this is acceptable for the local administrator to use +non-free software, and it is their choice.

We plan to release beta3 this weekend. You might want to give it a try.