Request for testers – new madwifi snapshot

Using the Atheros card sent to me by latexer, I was finally able to put some work into getting proper madwifi support in Gentoo Linux. I have created ebuilds for a new SVN snapshot (r1328-20051120) of both madwifi-driver and madwifi-tools and cleaned up the ebuilds somewhat.

Madwifi-tools now installs an udev rules file for automatically running wlanconfig when a new device is added. The prior preup()/postup() solution didn’t work properly with wpa_supplicant, which can take the interface down/up in the background.

Speaking of wpa_supplicant; I have also made a new revision of the wpa_supplicant-0.4.7 ebuild to reenable madwifi support. I have tested this against an access point using WPA-PSK TKIP, and it Works For Me ™. Now I just need to figure out why my Atheros card wont connect to an AP on channel 13 – `iwlist ath0 channel` shows channel 13 just fine…

Anyways, I’d really like some testers for the new madwifi-driver, madwifi-tools and wpa_supplicant ebuilds before I stick them into portage. They can be found in my portage overlay – both positive and negative feedback will be appreciated, just post a comment or contact me on IRC.

New hardware received

Yay! Pete was kind enough to send me two IEEE 802.11 CardBus cards all the way from the U.S.: an Atheros AR5212 based Proxim card and a PrismGT ISL3890 based Netgear card. These will be of great help when testing wpa_supplicant and hostapd, both packages which should have support for either of these cards.

Of course, I will also look into providing more up-to-date (and hopefully better, which shouldn’t be too hard taken the last couple of versions into consideration ;) ) ebuilds for both madwifi-driver and prism54 – and try to solve all the fuzz we recently had with madwifi support under Gentoo.

A big thank you to latexer for making this possible! :)

Update: also a big thanks to SuperLag for sponsoring the Prism54 card to latexer in the first place ;)

Wish list: GPS receiver

The mobile herd has traditionally been the maintainer of GPS (as in Global Positioning System) related packages in Gentoo Portage, but unfortunately, no one in the mobile herd currently has access to a GPS receiver to test with.

About five months ago I opened a meta-bug (#90848) for keeping track of all the GPS related bug reports and enhancement requests currently in our Bugzilla – before I reassigned them all to the maintainer-{wanted,needed} aliases. I also had a position for GPS packages mantainer added to our staffing needs page and notified the gentoo-dev@ mailing list of us being short of a GPS maintainer.

To this point, nobody has stepped up to take the position of GPS maintainer, so I’d like to put out a wish list for a GPS receiver (preferably a Garmin GPS with USB connection) so that I can maintain these packages myself.

Should you wish to donate such a device to me, please contact me.

How to irritate a Gentoo developer

Here’s a good way to irritate a Gentoo developer:

* Read on a mailing list that some driver was just released in a new version
* Wait 20 minutes
* File a bug report about Gentoo not having the newest version of the driver available in portage

Come on – developers read the mailing lists as well. For this particular project I even work closely with upstream on fixing bugs and providing patches, and anybody following the project closely would know this. New versions have always been added to portage within hours, if not minutes, after the release.

Rule of thumb for all those impatient end-users out there: Part of being a Gentoo maintainer of a package in portage is to watch for new releases, and update the existing ebuilds for these. If a new version of a package hasn’t made it into portage within a week of it’s public announcement, please file an enhancement request.

New kernel source: sys-kernel/suspend2-sources

Today sys-kernel/suspend2-sources, which has been living in my portage overlay for many months, finally made it’s way into Gentoo portage. The new kernel sources consists of genpatches and Software Suspend 2 and is targetted for laptop users who needs better suspend-to-disk support than the current in-kernel implementation of software suspend.

On a side note, Nigel Cunningham submitted the Software Suspend 2 patches to LKML for inclusion earlier today. Hopefully sys-kernel/suspend2-sources will be short-lived…

The future is here: pcmciautils

The needed changes to the in-kernel PCMCIA subsystem for allowing hotplug to handle 16bit PCMCIA cards was merged into linux-2.6.13-rc1 – and I have just added sys-apps/pcmciautils to portage, finally closing bug #84234. A big thank you to Dominik Brodowski for the initial ebuild – and for the package itself.

If you want to try out this cool new feature, you’ll have to unmerge pcmcia-cs and emerge pcmciautils – and if your card needs a CIS override you should set USE=”cis”.

Please report all bugs to Gentoo Bugzilla.

Version bump: sys-apps/pcmcia-cs-3.2.8

I have just added sys-apps/pcmcia-cs-3.2.8 and the split out sys-apps/pcmcia-cs-modules-3.2.8 to portage – please test and report any bugs to bugzilla. Hopefully this will be the last major release of pcmcia-cs – next up: pcmciautils.

To clarify:

  • If you are using linux-2.4.x you should disable the in-kernel CONFIG_PCMCIA drivers but enable support for the needed sub-systems such as CONFIG_NET_RADIO and use the modules from sys-apps/pcmcia-cs-modules – and the user-space utils from sys-apps/pcmcia-cs.
  • If you are using linux-2.6.x you should use the in-kernel PCMCIA drivers along with the user-space utilities from sys-apps/pcmcia-cs.
  • When linux-2.6.13-preX is out you should consider switching to the yet-to-be-added pcmciautils, deprecating sys-apps/pcmcia-cs all together.