Seit kurzem funktioniert WLAN bei meiner 7390 nicht mehr. Ich habe gerade ein neues Image importiert (FRITZ!OS 05.20-freetz-devel-8871). Folgende Einträge im Syslog findet man direkt nach versuchter Aktivierung:
Sieht das nach einem Hardware-Problem aus oder kann das etwas mit Freetz zu tun haben?
Hier noch das /var/tmp/wland_support.log
Code:
Apr 3 23:36:03 fritz kern.info kernel: [wlan_eeprom] calibration data blocks found = 2
Apr 3 23:36:03 fritz kern.info kernel: [wlan_eeprom] Got calibration data version 255 for instance #1
Apr 3 23:36:03 fritz kern.info kernel: [wlan_eeprom] Using complete eeprom from flash
Apr 3 23:36:03 fritz kern.info kernel: [wlan_eeprom] Got calibration data version 255 for instance #2
Apr 3 23:36:03 fritz kern.info kernel: [wlan_eeprom] Using complete eeprom from flash
Apr 3 23:36:06 fritz kern.info kernel: ath_hal: 0.9.17.1 (AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2316, RF2317, REGOPS_FUNC, WRITE_EEPROM, 11D)
Apr 3 23:36:06 fritz kern.info kernel: ath_rate_atheros: Copyright (c) 2001-2005 Atheros Communications, Inc, All Rights Reserved
Apr 3 23:36:06 fritz kern.info kernel: ath_spectral: Version 2.0.0
Apr 3 23:36:06 fritz kern.info kernel: Copyright (c) 2005-2009 Atheros Communications, Inc. All Rights Reserved
Apr 3 23:36:06 fritz kern.info kernel: SPECTRAL module built on Feb 24 2012 13:42:08
Apr 3 23:36:06 fritz kern.info kernel: ath_dfs: Version 2.0.0
Apr 3 23:36:06 fritz kern.info kernel: Copyright (c) 2005-2006 Atheros Communications, Inc. All Rights Reserved
Apr 3 23:36:07 fritz kern.info kernel: ath_dev: Copyright (c) 2001-2007 Atheros Communications, Inc, All Rights Reserved
Apr 3 23:36:11 fritz kern.info kernel: ath_pci: 9.2.0_U7.717 (Atheros/multi-bss)
Apr 3 23:36:11 fritz kern.warn kernel: PCI: Enabling device 0000:00:01.0 (0000 -> 0002)
Apr 3 23:36:11 fritz kern.debug kernel: PCI: Setting latency timer of device 0000:00:01.0 to 64
Apr 3 23:36:11 fritz kern.warn kernel: ath_dev_attach: unable to attach hardware; HAL status 3
Apr 3 23:36:11 fritz kern.warn kernel: PCI: Enabling device 0000:00:02.0 (0000 -> 0002)
Apr 3 23:36:11 fritz kern.debug kernel: PCI: Setting latency timer of device 0000:00:02.0 to 64
Apr 3 23:36:11 fritz kern.warn kernel: ath_dev_attach: unable to attach hardware; HAL status 3Sieht das nach einem Hardware-Problem aus oder kann das etwas mit Freetz zu tun haben?
Hier noch das /var/tmp/wland_support.log
Code:
WLAND:[00829]:23:36.01:error: unknown symbol: event_control
WLAND:[00829]:23:36.01:error: unknown symbol: night_time_control_auto_update
WLAND:[00829]:23:36.01:error: unknown symbol: feature_wlan_coexistence
WLAND:[00829]:23:36.02:config_mgr_phy_params_fix(97): master_set is 0x00000003 (config #2)
WLAND:[00829]:23:36.02:config_mgr_phy_params_fix(117): master role #2 is not STA(1)
WLAND:[00829]:23:36.02:config_mgr_phy_params_fix(117): master role #1 is not STA(1)
WLAND:[00829]:23:36.02:config_mgr_wps_params_fix(177): parameter 'wps_enable' set to '0' in role #9
WLAND:[00829]:23:36.02:config_mgr_wps_params_fix(177): parameter 'wps_enable' set to '0' in role #8
WLAND:[00829]:23:36.02:config_mgr_wps_params_fix(177): parameter 'wps_enable' set to '0' in role #7
WLAND:[00829]:23:36.02:config_mgr_wps_params_fix(177): parameter 'wps_enable' set to '0' in role #6
WLAND:[00829]:23:36.02:config_mgr_wps_params_fix(177): parameter 'wps_enable' set to '0' in role #5
WLAND:[00829]:23:36.02:config_mgr_wps_params_fix(177): parameter 'wps_enable' set to '0' in role #4
WLAND:[00829]:23:36.02:config_mgr_wps_params_fix(177): parameter 'wps_enable' set to '0' in role #3
WLAND:[00829]:23:36.22:cfg_mgr_changes_apply: apply configuration failed, status 0x80000001
