Hi Celtichboy
No, using ath_pci that runs standard on UNR 9.04. After fiddling with madwifi last time, it also only working for a day or two, I reinstalled and only uncommented the blacklist thingie to get wireless working.
Now after many days of wireless happiness things have gone south again, without warning and preperation...
Thoought this might shed some light: (to someone who has a little more insight than I)
Code:
dmesg|grep ath
[ 3.140789] device-mapper: multipath: version 1.0.5 loaded
[ 3.140795] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 6.987023] ath5k_pci 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 6.987057] ath5k_pci 0000:03:00.0: setting latency timer to 64
[ 6.987176] ath5k_pci 0000:03:00.0: registered as 'phy0'
[ 7.183531] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
[ 7.185254] ath_hal: module license 'Proprietary' taints kernel.
[ 7.189896] ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
[ 7.304934] ath_pci: 0.9.4
[ 162.986424] ath5k phy0: unsupported jumbo
[ 640.195496] ath5k phy0: unsupported jumbo
[ 942.840962] ath5k phy0: unsupported jumbo
[ 1013.312626] ath5k_pci 0000:03:00.0: PCI INT A disabled
[ 1014.320790] ath5k_pci 0000:03:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10b)
[ 1014.320835] ath5k_pci 0000:03:00.0: restoring config space at offset 0x4 (was 0x4, writing 0x75200004)
[ 1014.320847] ath5k_pci 0000:03:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x20)
[ 1014.320862] ath5k_pci 0000:03:00.0: restoring config space at offset 0x1 (was 0x100000, writing 0x100007)
[ 1014.336159] ath5k_pci 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Bookmarks