Madwifi-hal for Atheros 5k cards under Linux

[Fate]

I actually wound up not having to blacklist any modules for this. I just went into Ubuntu's "Restricted Drivers" tool and disabled the stock modules from there. Maybe that accomplishes the same thing, I haven't checked.

Anyway, it's worth a mention that you'll have to run "make install" every time you upgrade kernels (or do some judicious copying of modules around) so you'd best keep your madwifi source code around. Ubuntu updated itself to the 2.6.27-9 kernel last night and my wireless magically stopped working. Re-doing "make install" and rebooting brought it back.

[coroner]

Originally Posted by Fate

Anyway, it's worth a mention that you'll have to run "make install" every time you upgrade kernels (or do some judicious copying of modules around) so you'd best keep your madwifi source code around.

This is why I like any distribution's build system, especially Fedora's.
With SRPMS, I don't really have to do anything, per kernel, in fact I can script rpmbuild to rebuild my modules as soon as bootstrap occurs on a new kernel, no I don't mean when I hit X windows and after opening a terminal, I mean when the modules try to get loaded out of the kernel tree, and don't exist because it's a new kernel, compilation happens through rpmbuild, then rpm inserts the package, and the modules are tried to reload.. and I never hit a desktop with a broken module set. It's nearly transparent.

Now you may ask, well doesn't that take too much time though during bootstrap, who wanrts to sit there and wait for a module set compilation right at bootstrap? Nobody probably, who wants to hit a desktop with no modules that aren't already there? Nobody probably.

While this is not how Fedora is currently set up stock, it might be something to look into soon for RAWHIDE or F11. Other distributions might look into it also. I think it would take the fun out of fucking off with my Linux system and building modules, but it isn't something that is mandatory, and unless you have akmods installed, this won't happen.. nothing is mandatory in Linux. This is where akmods are going I believe currently.

[Prometheum]

Originally Posted by coroner

This is why I like any distribution's build system, especially Fedora's.
With SRPMS, I don't really have to do anything, per kernel, in fact I can script rpmbuild to rebuild my modules as soon as bootstrap occurs on a new kernel, no I don't mean when I hit X windows and after opening a terminal, I mean when the modules try to get loaded out of the kernel tree, and don't exist because it's a new kernel, compilation happens through rpmbuild, then rpm inserts the package, and the modules are tried to reload.. and I never hit a desktop with a broken module set. It's nearly transparent.

Now you may ask, well doesn't that take too much time though during bootstrap, who wanrts to sit there and wait for a module set compilation right at bootstrap? Nobody probably, who wants to hit a desktop with no modules that aren't already there? Nobody probably.

While this is not how Fedora is currently set up stock, it might be something to look into soon for RAWHIDE or F11. Other distributions might look into it also. I think it would take the fun out of fucking off with my Linux system and building modules, but it isn't something that is mandatory, and unless you have akmods installed, this won't happen.. nothing is mandatory in Linux. This is where akmods are going I believe currently.

dkms is superior, rpm is for the nubs

[coroner]

Just so anyone reading is curious about DKMS and AKMODS, these are the project pages for the two:

DKMS
http://linux.dell.com/dkms/

AKMODS:
http://rpmfusion.org/Packaging/KernelModules/Akmods

Oh and Pr0, straight from the AKMODS website:

This is similar to dkms, but has one important benefit: one only needs to maintain a single kmod spec file which can be used both in the repos buildsystem and on the clients systems if needed.

Apparently DKMS is not used by any large distribution's build systems.
AKMODS is a Fedora buildsystem tool, for any distribution which uses rpm/rpmbuild and for client machines if you so choose.

[Prometheum]

Originally Posted by coroner

Just so anyone reading is curious about DKMS and AKMODS, these are the project pages for the two:

DKMS
http://linux.dell.com/dkms/

AKMODS:
http://rpmfusion.org/Packaging/KernelModules/Akmods

Oh and Pr0, straight from the AKMODS website:


Apparently DKMS is not used by any large distribution's build systems.
AKMODS is a Fedora buildsystem tool, for any distribution which uses rpm/rpmbuild and for client machines if you so choose.

Ubuntu uses DKMS. And using only one file isn't an upside: that means packages can't install their own files that have parts of the global configuration that pertain to that package.

[Longhorner]

oh right.... right i just started typing at random and hoped that it would work ....no im not that stupid

i went to the root terminal

typed the first line of code and if i remember correctly it could not find the source

i ignored that and moved on to the next line of code and of course svn was not a valid command.

[Prometheum]

Originally Posted by Longhorner

oh right.... right i just started typing at random and hoped that it would work ....no im not that stupid

i went to the root terminal

typed the first line of code and if i remember correctly it could not find the source

i ignored that and moved on to the next line of code and of course svn was not a valid command.

Oops, you'd have to install subversion. I'll add that.

However, linux-source is indeed a valid package, at least in 8.10. Try looking on packages.ubuntu.com for the package for another version, if it is different (I don't think it is, though if it is, it's likely linux-source-generic).

[coroner]

Originally Posted by Prometheum

Ubuntu uses DKMS. And using only one file isn't an upside: that means packages can't install their own files that have parts of the global configuration that pertain to that package.

I'm not sure what you mean here, AKMODS and DKMS only deal with kernel modules as packages, but the single file statement in my post states you need only one configuration file for the build system on RedHat's server and on your own machine.. if you're building packages for anyone's system, including your own opf course.. I'm not sure how DKMS differs, but all RPM packages have the ability to install configuration files that are globally part of that package, and ANY package if you so choose.. however that is out of the bounds of proper packaging.. I'm not sure what you mean but if you can elaborate please do so.

[Prometheum]

Originally Posted by coroner

I'm not sure what you mean here, AKMODS and DKMS only deal with kernel modules as packages, but the single file statement in my post states you need only one configuration file for the build system on RedHat's server and on your own machine.. if you're building packages for anyone's system, including your own opf course.. I'm not sure how DKMS differs, but all RPM packages have the ability to install configuration files that are globally part of that package, and ANY package if you so choose.. however that is out of the bounds of proper packaging.. I'm not sure what you mean but if you can elaborate please do so.

Then I misunderstood.

[Draven]

Hey guys new to this but i ran into a problem in the steps prometheum listed on the previous page. when I run the command { sudo tee -a /etc/modprobe.d/blacklist } in terminal my terminal does nothing not even an error? any ideas on this.

thanx for all help...