[opensuse-factory] Atheros 2413 no longer works after zypper dup
Bug #646788 opened. A friend dictated this over the phone as he now has no connection - we're in the UK. He tested with a 11.2 laptop and got a connection. From dmesg ============ ATH: eeprom regdomain: 0x809c ATH: eeprom indicates we should expect a Country Code ATH: doing eeprom Country -> regdomain map search ATH: Country maps to regdomain Code: 0x52 ATH: Country A2 being used : CN ATH: regdomain used: 0x52 phy0: selected rate control algorithm minstrel ATH5K phy0: Atheros AR2413 chip found (mac: 0x78,phy:0x45) cfg80211: calling CRDA for country: CN ADRCONF (netdev_up): wlan0: link is not ready ============= Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thu, Oct 14, 2010 at 6:02 PM, Sid Boyce
Bug #646788 opened.
A friend dictated this over the phone as he now has no connection - we're in the UK. He tested with a 11.2 laptop and got a connection. From dmesg ATH5K phy0: Atheros AR2413 chip found (mac: 0x78,phy:0x45)
ath5k does not support the AR2413. You have to use the older madwifi module. You also have to unload the ath5k module before loading the madwifi. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 15/10/10 00:15, Larry Stotler wrote:
On Thu, Oct 14, 2010 at 6:02 PM, Sid Boyce
wrote: Bug #646788 opened.
A friend dictated this over the phone as he now has no connection - we're in the UK. He tested with a 11.2 laptop and got a connection. From dmesg ATH5K phy0: Atheros AR2413 chip found (mac: 0x78,phy:0x45)
ath5k does not support the AR2413. You have to use the older madwifi module. You also have to unload the ath5k module before loading the madwifi.
Hmmmmmmmm ..... he said it was working fine until he did zypper dup, so it must have overwrote his previous setup. I've been trying to call him to find out if he had been using madwifi. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Friday 15 Oct 2010 00:15:51 Larry Stotler wrote:
On Thu, Oct 14, 2010 at 6:02 PM, Sid Boyce
wrote: Bug #646788 opened.
A friend dictated this over the phone as he now has no connection - we're in the UK. He tested with a 11.2 laptop and got a connection. From dmesg ATH5K phy0: Atheros AR2413 chip found (mac: 0x78,phy:0x45)
ath5k does not support the AR2413. You have to use the older madwifi module. You also have to unload the ath5k module before loading the madwifi.
Right i am the person with the problem the ath5k driver seems to support the chipset in question very well and has done for best part of 12 months without problems this all started after i did an "zypper up" not "zypper dup" as reported by Sid it seems it is a yast failure to correctly configure the networking as i have connected from the command line instantly using the ath5k driver Pete . -- Powered by openSUSE 11.3 (x86_64) Kernel: 2.6.34.7-0.3-desktop KDE Development Platform: 4.4.4 (KDE 4.4.4) "release 3" 18:04 up 11:02, 4 users, load average: 1.68, 1.13, 0.92 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Fri, Oct 15, 2010 at 1:09 PM, Peter Nikolic
Right i am the person with the problem the ath5k driver seems to support the chipset in question very well and has done for best part of 12 months without problems this all started after i did an "zypper up" not "zypper dup" as reported by Sid it seems it is a yast failure to correctly configure the networking as i have connected from the command line instantly using the ath5k driver
Ok, I was mistaken. They must have added support at some point. I remember that was the case in 11.0. Sorry. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Fri, Oct 15, 2010 at 1:09 PM, Peter Nikolic
wrote: Right i am the person with the problem the ath5k driver seems to support the chipset in question very well and has done for best part of 12 months without problems this all started after i did an "zypper up" not "zypper dup" as reported by Sid it seems it is a yast failure to correctly configure the networking as i have connected from the command line instantly using the ath5k driver
Ok, I was mistaken. They must have added support at some point. I remember that was the case in 11.0.
Sorry.
On Friday 15 Oct 2010 22:35:02 Larry Stotler wrote: thats ok no problem ... Pete . -- Powered by openSUSE 11.3 (x86_64) Kernel: 2.6.34.7-0.4-desktop KDE Development Platform: 4.4.4 (KDE 4.4.4) "release 3" 22:43 up 2:24, 4 users, load average: 0.73, 0.53, 0.50 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (3)
-
Larry Stotler
-
Peter Nikolic
-
Sid Boyce