Of course module-assistant is a good method... but not for everybody.
The average Debian user doesn't compile his own kernel. Therefore he has
the right to claim for a module already compiled for his kernel.
I don't know what you are saying about the ATI blob. I just want to
compile the package already in Debian : fglrx-kernel-src
Lennart Sorensen a écrit :
On Sun, Apr 20, 2008 at 05:11:30AM +0200, Bertrand Marc wrote:
Package: wnpp
Severity: wishlist
Owner: Bertrand Marc <[EMAIL PROTECTED]>
* Package name : fglrx-kernel-modules
Version : 1:8-4-1
Upstream Author : ATI/AMD
* URL : http://ati.amd.com/support/drivers/linux/linux-radeon.html
* License : restricted
Description : fglrx (ATI driver) kernel module build against the last
kernel
It is a simple package that provide the fglrx kernel module compiled for
the last 2.6 kernel found in Debian. It compiles fglrx-kernel-src. There
would be no need of module-assistant to get (proprietary) 3D
acceleration working.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
module-assistant is a very good method, and lets a user easily compile
modules for a custom made kernel.
What exactly does ATI's 50MB blob do that is somehow better? Does it
generate debian packages and isntall them? Does it respect the correct
locations to install files?
