- Support, Questions and other Discussions
Wiki pages aren't effective place for discussion.
Use the mailing-lists or IRC instead. see http://www.debian.org/support
Your contributions and feedback are welcome.
Place new comments at the bottom
Add new comments, don't edit old ones
Sign your comments using @SIG@
I suggest that there could be a separate section for hardware and the Install Driver section being kept for software. At the moment all the information on this page seems to refer to cards using the MadWiFi software (including the need for module-assistant). So I would suggest under Install Driver there would be two sections (at present), one for MadWiFi and one for BCM43xx. Similarly the hardware section could be divided into devices using the Atheros chipset and devices using the Broadcom chipsets.
I think it would be a good idea if the BCM43xx information was included here rather than being on a separate page.
-- John_Talbut 2007-12-16 09:32:17
Yes, it's the natural way of a portal. When it's grow up and become too big, We can create sub portal. At this moment, I think SystemAdministration and Network are more urgent to fragment. WiFi portal is not enough too big at this moment;
-- SalokineTerata 2007-12-16 14:22:12
Should I move details from our DebianEeePC project here (mostly about Atheros 242x which is in Eee models 701, 900 and 900A) or just link to our own wiki? What about ath5k? I understand the version in 2.6.26 works on some systems already (though we will need to wait for a later release for support on these Eee PC models).
We have rt2860-source from Ralink for DebianEeePC/Model/901 hosted at eeepc.debian.net. Some non-Eee owners with this hardware may benefit. We are also looking now at rtl8187se for DebianEeePC/Model/701SD. Neither of these are yet suitable for inclusion in Debian. In the first case although the driver is open source, it embeds non-free firmware. We're hoping the rt2x00 project wil support this, but work on it is very early. In the second, none of the developers have this system yet and we haven't made packages yet. I don't know if it includes non-free firmware or not. It appears the same hardware is included in the MSI Wind netbook.
-- BenArmstrong 2008-10-11 16:33:11
Moving details about Atheros 242x here looks like a good idea.
-- FranklinPiat 2008-10-12 07:39:26
I've created rtl-wifi, which includes driver installation procedures relating to the Realtek RTL8187SE chipset.
A page about ath5k relating to supported chipsets (brief list), missing features (with respect to madwifi) and other known issues could potentially be useful to existing ath_pci users. Possibly even a "Switching from madwifi to ath5k" section as done in iwlwifi.
-- GeoffSimmons 2009-01-04 15:01:54
I consider that 1 page/module is the best compromize, to keep pages short. If multiple pages apply for a given [wifi] device, I hesitate to put the explanation on the WiFi page, or as a header on each of the alternatives pages. -- FranklinPiat 2009-01-04 16:27:44
As per BenArmstrong's suggestion, I have created rt2860sta and transferred the content of DebianEeePC/HowTo/Wifi/Rt2860 within. Apart from the leading sentence, this content was not specific to the Eee. Comments welcome. -- GeoffSimmons 2009-01-13 13:27:37
I have added more content to WiFi/HowToUse. Made the assumption that users would want to connect to a WPA-protected network (managed mode), providing common configuration examples (N-M, wpa_supplicant) accordingly. Not covered is monitor and master mode operation, which is either driver-specific (eg. Ralink devices require rt2x00 GIT for BSS master) or unsupported.
I am loathe to migrate the Ad-Hoc setup content from WiFi to here, due to its insecure nature. "iwconfig ath0 mode Ad-hoc" will not work for current MadWifi drivers anyway. I suggest this either be deleted or moved elsewhere. -- GeoffSimmons 2009-01-21 17:58:32
- Regarding the second point, I am not quite sure what should be done... since Ad-Hoc can be useful in some situation, it could be moved to another page. BTW, I wonder how much insecure it is, compared to "open" hotspots.
WiFi: The ID columns (in PCI / USB Devices sections) appear to be unnecessary now, as most driver pages have a "Supported Devices" section listing their PCI and/or USB IDs, where known.
The existing IDs (as at page revision 144) are of unsupported devices. These probably should be merged with the device name, as done for the PC Card (PCMCIA) Devices section. Thoughts? -- GeoffSimmons 2009-06-29 11:30:41
I agree for both points. -- FranklinPiat 2009-06-29 19:30:56
Removed as of revision 145. -- GeoffSimmons 2009-07-03 03:40:58
I have been working towards installing the ar5523 device software/firmware on a new installation of debian 5.04. The process looks simple enough. But in the module creation step 'm-a a-i ar5523' the process fails with over 20 errors. I have had a look at the errors, but I don't have enough background to be able to fix them. So I am reporting them here, hoping that someone can check this out and provide some fix-up. -- BrianMcConkey 2010-05-16 15:16:48
The procedure on ar5523 is specific to Squeeze (i.e. DebianTesting with the 2.6.32 kernel) and not Lenny/2.6.26, as the driver is unreleased and still in development. The patches applied by default in debian/rules/series break Linux 2.6.26 compatibility.
To resolve your specific compilation issue (as of subversion revision 26899), edit debian/rules/series and remove/comment kcompat-2.6.32.patch, remove-unused-variables.patch and kcompat-2.6.34.patch, before building the driver source package. Alternatively, use a backported Linux 2.6.32 kernel image package (available from Debian Backports) when building the driver.