Re: [arch-general] [arch-dev-public] [signoff] kernel26 2.6.26-1 and related module packages
On Mon, Jul 21, 2008 at 10:56:15PM +0200, Thomas Bächler wrote:
- madwifi is broken. Do we still need it? AFAIK, all chipsets should now be supported by ath5k by now. Can a madwifi user please look at this (Aaron, Dan?)
My card doesn't work with ath5k, i've tested module from 2.6.25 and now 2.6.26 from testing. ,----[ lspci ] | Atheros Communications, Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01) `---- It's a PCMCIA card. Vendor: TP-Link TL-WN610G I cannot see any networks during scanning (iwlist). ,----[ log after insert card ] | Jul 23 00:50:37 tuxlap pccard: CardBus card inserted into slot 1 | Jul 23 00:50:37 tuxlap ath5k_pci 0000:06:00.0: enabling device (0000 -> 0002) | Jul 23 00:50:37 tuxlap ACPI: PCI Interrupt 0000:06:00.0[A] -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11 | Jul 23 00:50:37 tuxlap ath5k_pci 0000:06:00.0: registered as 'phy1' | Jul 23 00:50:37 tuxlap phy1: Selected rate control algorithm 'pid' | Jul 23 00:50:37 tuxlap ath5k phy1: Atheros AR2414 chip found (MAC: 0x79, PHY: 0x45) `---- ifconfig wlan0 up (works after ~5 tries) iwlist wlan0 scan shows no networks (no problem with madwifi) During iwlist scan log is flooded with: ,----[ /var/log/everything.log ] | Jul 23 00:51:54 tuxlap ath5k phy1: noise floor calibration timeout (2432MHz) | Jul 23 00:51:54 tuxlap ath5k phy1: ath5k_chan_set: unable to reset channel (2432 Mhz) | Jul 23 00:51:54 tuxlap wlan0: failed to set freq to 2432 MHz for scan | Jul 23 00:51:54 tuxlap ath5k phy1: noise floor calibration timeout (2437MHz) | Jul 23 00:51:54 tuxlap ath5k phy1: ath5k_chan_set: unable to reset channel (2437 Mhz) | Jul 23 00:51:54 tuxlap wlan0: failed to set freq to 2437 MHz for scan | Jul 23 00:51:54 tuxlap wlan0: failed to set freq to 2442 MHz for scan | Jul 23 00:51:54 tuxlap wlan0: failed to set freq to 2447 MHz for scan | Jul 23 00:51:54 tuxlap wlan0: failed to set freq to 2452 MHz for scan | Jul 23 00:51:55 tuxlap wlan0: failed to set freq to 2457 MHz for scan | Jul 23 00:51:55 tuxlap wlan0: failed to set freq to 2462 MHz for scan | Jul 23 00:51:55 tuxlap wlan0: failed to restore operational channel after scan | Jul 23 00:51:59 tuxlap __ratelimit: 12 messages suppressed | Jul 23 00:51:59 tuxlap ath5k phy1: noise floor calibration timeout (2412MHz) | Jul 23 00:52:07 tuxlap ath5k phy1: noise floor calibration timeout (2417MHz) | Jul 23 00:52:07 tuxlap wlan0: failed to set freq to 2417 MHz for scan | ... and so on `---- Same log messages if trying wpa_supplicant Providing further packages for madwifi seems difficult with >=2.6.26, or see you any chance? Should i file a bugreport (arch or madwifi or LKML)? Searching a little with "ath5k_chan_set: unable to reset channel" i saw more users which maybe similar problems, ex. http://madwifi.org/ticket/808 (Little confusing...) and this in our forum could be similar: http://bbs.archlinux.org/viewtopic.php?id=52049 Regards Gerhard -- Kernel panic: Could not determine whether bit was one, zero or sqrt(1/PI)... (J.K. in d-u-g)
On Wed, Jul 23, 2008 at 01:36:14AM +0200, Gerhard Brauer wrote:
On Mon, Jul 21, 2008 at 10:56:15PM +0200, Thomas Bächler wrote:
- madwifi is broken. Do we still need it? AFAIK, all chipsets should now be supported by ath5k by now. Can a madwifi user please look at this (Aaron, Dan?)
My card doesn't work with ath5k, i've tested module from 2.6.25 and now 2.6.26 from testing.
,----[ lspci ] | Atheros Communications, Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01) `----
The AR5007EG card still doesn't work with the standard ath5k or MadWifi. That 5212 sometimes turns out to need the same driver. I have a page on it, (though your card sounds like another card) more Fedora specific but also works for Arch at http://home.nyc.rr.com/computertaijutsu/rhwireless.html#5007 Though I haven't seen a PCMCIA card with that chipset, I do know that the driver has sometimes fixed things for folks having problems with the 5212 cards, so I really don't know. At worst, you'll lose some time, it can easily be uninstalled if it doesn't work. -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Giles: (scoffs) Magic! Magic's all balderdash and chicanery. I'm afraid we don't know a bloody thing. (everyone looking at him) Except I seem to be British, don't I? Uh, and a man. With ... glasses. (removes glasses) Well, that narrows it down considerably.
On Tue, Jul 22, 2008 at 08:32:42PM -0400, Scott wrote:
On Wed, Jul 23, 2008 at 01:36:14AM +0200, Gerhard Brauer wrote:
My card doesn't work with ath5k, i've tested module from 2.6.25 and now 2.6.26 from testing.
,----[ lspci ] | Atheros Communications, Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01) `----
The AR5007EG card still doesn't work with the standard ath5k or MadWifi. That 5212 sometimes turns out to need the same driver.
I have a page on it, (though your card sounds like another card) more Fedora specific but also works for Arch at http://home.nyc.rr.com/computertaijutsu/rhwireless.html#5007
Thanks for the info, but i have no problems with arch stock-kernels and madwifi. Works like a charm. Only the new ath5k foss module doesn't work - would be for me a stopper not to upgrade to 2.6.26. I've found the homepage: http://wireless.kernel.org/en/users/Drivers/ath5k Seems there is a lot of work to do ;-) I don't understand currently why madwifi (broken?) is gone and this young project replace it. At the moment i check out their testing git, i found some commits that sound like my problem...maybe... Regards Gerhard -- OOP? Frueher haben wir die Fehler selbst programmiert, heute werden sie vererbt.
On Wed, Jul 23, 2008 at 01:36:14AM +0200, Gerhard Brauer wrote:
Providing further packages for madwifi seems difficult with >=2.6.26, or see you any chance?
Ok, i found a solution/patch for madwifi, this works now under 2.6.26. With ath5k i compiled latest wireless-compat and git version, first gives me same errors as above, git version a kernel trap. I will deal this on ath5k-ML or bugtracker. Regards Gerhard -- Kernel panic: Could not determine whether bit was one, zero or sqrt(1/PI)... (J.K. in d-u-g)
participants (2)
-
Gerhard Brauer
-
Scott