Slashdot Mirror

← Back to Stories (view on slashdot.org)

Intel Begins Support for Debian

Posted by CowboyNeal on from the coming-around dept.

An anonymous reader writes "An Intel Software Architect announced on the Debian mailing list yesterday that Intel has begun supporting Intel devices on Debian sarge for their extensive reseller channel. This covers the D845, D865 and D915 chipsets and was done to meet customer demand. They've posted drivers as well as the various distributions supported by the chip maker (Debian, Mandriva, Novell and Red Hat). Looks like the pure open source distributions are finally getting the attention of the big players!"

4 of 33 comments (clear)

  1. Re:No debs on the site yet.. by topside420 · · Score: 4, Informative
    Then how am I doing this?

    # dpkg -i sk98lin-8.13-1-deb3.1-2.6.8-2-386.i386.deb
    Select ing previously deselected package sk98lin.
    (Reading database ... 84296 files and directories currently installed.)
    Unpacking sk98lin (from sk98lin-8.13-1-deb3.1-2.6.8-2-386.i386.deb) ...
    Setting up sk98lin (8.13-1) ...
    running depmod

    The kernel this binary deb was installed against is 2.6.8/i386, Debian 3.1.

    The actual download is pretty silly. You download a tar.gz file. This unzips into a total of 1 file (so why the .tar?). The format? ISO. To mount this, just use `mount -o loop file.iso /mount/point`

    Here's a general feel for the unusual install.

    blaze:~/intel# ls
    INTEL(R)_QSK_VER_1_3_DEBIAN.TAR.GZ
    blaze:~/in tel# tar -zxvf INTEL\(R\)_QSK_VER_1_3_DEBIAN.TAR.GZ
    Intel_Quick_ Start_Kit_v1_3_Debian.ISO
    blaze:~/intel# mount -o loop Intel_Quick_Start_Kit_v1_3_Debian.ISO /cdrom
    blaze:~/intel# cd /cdrom
    blaze:/cdrom# ls
    autorun autorun.inf docs drivers install license.txt
    blaze:/cdrom# cd drivers/
    blaze:/cdrom/drivers# ls
    Debian sources
    blaze:/cdrom/drivers# cd Debian/
    blaze:/cdrom/drivers/Debian# ls
    DEB_3.1
    blaze:/cdrom/drivers/Debian# cd DEB_3.1/
    blaze:/cdrom/drivers/Debian/DEB_3.1# ls
    audio graphics network
    blaze:/cdrom/drivers/Debian/DEB_3.1# cd network/
    blaze:/cdrom/drivers/Debian/DEB_3.1/netw ork# ls
    e100 e1000 sk98lin
    blaze:/cdrom/drivers/Debian/DEB_3.1/netwo rk# cd e100
    blaze:/cdrom/drivers/Debian/DEB_3.1/network/ e100# ls
    blaze:/cdrom/drivers/Debian/DEB_3.1/network/e1 00# cd ..
    blaze:/cdrom/drivers/Debian/DEB_3.1/network# cd sk98lin/
    blaze:/cdrom/drivers/Debian/DEB_3.1/netw ork/sk98lin# ls
    md5sum.txt sk98lin-8.13-1-deb3.1-2.6.8-2-386.i386.deb

    blaz e:/cdrom/drivers/Debian/DEB_3.1/network/sk98lin# md5sum sk98lin-8.13-1-deb3.1-2.6.8-2-386.i386.deb; cat md5sum.txt
    2a0e928efb100ac903033b5904c57261 sk98lin-8.13-1-deb3.1-2.6.8-2-386.i386.deb
    2a0e92 8efb100ac903033b5904c57261 sk98lin-8.13-1-deb3.1-2.6.8-2-386.i386.deb

    blaz e:/cdrom/drivers/Debian/DEB_3.1/network/sk98lin# dpkg -i sk98lin-8.13-1-deb3
  2. Re:Intel supports open source? by anarxia · · Score: 5, Informative

    From the email:
    "All the drivers of course include source and have been released under the GPL. They have also already been submitted upstream ( kernel.org, alsa.org , x.org) and can be downloaded at intel.com/go/linux."

  3. Re:No debs on the site yet.. by G-Licious! · · Score: 3, Informative

    The main diff is that Linux doesn't really have a self executing compression. (and if it does exists, face it... tar is much more common).

    Makeself. It's used in the Loki installer, and thus in lots of commercial software.

    Besides that, grandparents point was that a .tar is a non-compressed archive, and the actual compression happens in .gz. Gzip can only compress one file, meaning that if you want to compress multiple files, you'll have to compress a tar archive of those files. But in this case, there is only one file. So they could've (should've?) skipped the tar step and just gzip it.

  4. Re:No debs on the site yet.. by G-Licious! · · Score: 3, Informative

    I'm not sure I understand why you say that gzip can only compress one file.

    From the manual:

    gzip reduces the size of the named files using Lempel-Ziv coding (LZ77). Whenever possible, each file is replaced by one with the extension `.gz', while keeping the same ownership modes, access and modification times.

    Or from Wikipedia:

    The gzip file format holds a single compressed file. On Unix systems, compressed archives are typically created by rolling collections of files into a tar archive, and then compressing that archive with gzip. The final .tar.gz or .tgz file is usually called a "compressed tarball."

    Giving gzip multiple files will simply compress each of those files, instead of compressing them together inside a single archive.