Driver Testing
From ArchWiki
Contents |
HOWTO: Become an Arch Linux Tester for drivers/modules and related hardware
Modules are an odd beast. They are specific to a kernel, and tend to do a lot of things that only someone intimate with the hardware can really tell you. Due to this, it's generally MORE important to test hardware drivers than other packages. In addition, testing is harder for the developers because not everyone has all the hardware needed.
We (Arch Linux, that is) will be implementing a clear path for people to test modules before release, so we can at least get a "looks like it works" nod from those. What we'd like to do is gather a set of TUs and Developers for right now. When we figure out a workable system we will be able to pull in members of the community who have the hardware and are willing to take some time out of their day to test new packages.
How will this work?
The idea isn't really fully fleshed out right now. In theory though, testers will sign up for a given module/package and will receive emails when a new version hits the CVS repos (and most likely in [testing] as well). It may be pretty informal, but testers should probably respond as soon as possible to the maintainer of the package.
For the purpose of email filtering, let's layout a format for responses:
Subject: [arch-testing] package-name success
or
Subject: [arch-testing] package-name failure
Comments and all that should be in the email body, but keeping this information in the subject will help maintainers (a) filter testing emails and (b) see the status at a quick glance.
Alright, how can I help?
- New User <email@foo.bar>
- module1: hardware name or comment
- module2: hardware name or comment
- module3: hardware name or comment
Using the format above, please list your name, email, and hardware/modules you are willing to test.
Please note: it's best if you only add modules you use, not modules you *can* use, unless you're willing to spend time testing on each new release.
Tester info
- Aaron Griffin <aaron@archlinux.org>
- madwifi: Atheros AR5112 (?)
- ndiswrapper: Atheros AR5112 (?) and Broadcom BCM43??
- bcm43xx: Broadcom BCM43??
- catalyst: ATI X1300 (or X1400?)
- nvidia: GeForce 6600 GT
- ivtv: Hauppauge (something?)
- Travis Willard <travis@archlinux.org>
- catalyst: Radeon HD2400 Pro
- Zhukov Pavel <gelios@gmail.com>
- ipw3945: Intel ipw3945
- xf86-video-intel: Intel GMA 950
- Jaroslaw Swierczynski <swiergot@aur.archlinux.org>
- lirc: Remote control on serial port
- nvidia-96xx: GeForce3 Ti 200
- Roman Kyrylych <roman@archlinux.org>
- nvidia: GeForce 8600 GT
- xf86-video-nv: GeForce 8600 GT
- Alexander Baldeck <alexander@archlinux.org>
- nvidia: GeForce 6600 GS
- xf86-video-nv: GeForce 6600 GS
- xf86-video-ati: ATI Rage (mach64)
- xf86-video-via: VIA VT8623 [Apollo CLE266] integrated CastleRock
- Scott Horowitz <stonecrest@gmail.com>
- xf86-video-intel: Intel i830
- madwifi: TL-WN560G mini pci card
- Dan McGee <dan@archlinux.org>
- nvidia-96xx: GeForce4 MX 440
- zd1211-firmware: some cheap wireless adapter
- Jacek Poplawski <jacekpoplawski@gmail.com>
- xf86-video-ati: Radeon 9800 Pro (R300, AGP) / Radeon X550 (R300, PCI-E)
- Indrek Ardel <fps.intz@gmail.com>
- nvidia: GeForce 8800 GTS
- Janar Plinkner <jaxx14@msn.com>
- nvidia: GeForce 8800 GT
- Eric Belanger <eric@archlinux.org>
- nvidia: GeForce 7900 GS
- xf86-video-i810: Intel 855GM