Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

Ticket #1172 (new defect)

Opened 15 years ago

Last modified 14 years ago

interface is not brought up from ifconfig

Reported by: darkmage@sabayonlinux.org Assigned to: dwhedon
Priority: major Milestone:
Component: dadwifi Version: dadwifi-branch
Keywords: Cc:
Patch is attached: 0 Pending:

Description (Last modified by mrenzmann)

Using dadwifi revision 2167 with the lastest version of wireless-dev 2.6.21-r1 doesn't let the ifconfig bring up the interface, nor it is recognized by networkmanager, the card is an ubiquiti scr, I'll attach both lspci and dmesg of when I insert the card in:

lspci:
00:00.0 Host bridge: nVidia Corporation nForce3 Host Bridge (rev a4)
00:01.0 ISA bridge: nVidia Corporation nForce3 LPC Bridge (rev f6)
00:01.1 SMBus: nVidia Corporation nForce3 SMBus (rev a4)
00:02.0 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
00:02.1 USB Controller: nVidia Corporation nForce3 USB 1.1 (rev a5)
00:02.2 USB Controller: nVidia Corporation nForce3 USB 2.0 (rev a2)
00:06.0 Multimedia audio controller: nVidia Corporation nForce3 Audio (rev a2)
00:06.1 Modem: nVidia Corporation nForce3 Audio (rev a2)
00:08.0 IDE interface: nVidia Corporation nForce3 IDE (rev a5)
00:0a.0 PCI bridge: nVidia Corporation nForce3 PCI Bridge (rev a2)
00:0b.0 PCI bridge: nVidia Corporation nForce3 AGP Bridge (rev a4)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)
02:01.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ac)
02:01.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev ac)
02:01.2 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev 04)
02:02.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)
04:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)

dmesg:
[  174.259778] pccard: CardBus card inserted into slot 1
[  174.283246] ath_hal: module license 'Proprietary' taints kernel.
[  174.284724] ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
[  174.286926] ath_pci: 0.9.4.5-dadwifi (svn r2166)
[  174.287511] PCI: Enabling device 0000:04:00.0 (0000 -> 0002)
[  174.287571] ACPI: PCI Interrupt 0000:04:00.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
[  174.508574] wmaster0: Selected rate control algorithm 'simple'
[  174.509816] wiphy1: mac 5.9 phy 4.3 radio 3.6
[  174.509826] wiphy1: Use hw queue 8 for CAB traffic
[  174.509828] wiphy1: Use hw queue 9 for beacons
[  174.509832] wiphy1: Atheros 5212: mem=0xf9600000, irq=11
[  177.771440] wlan0_rename: starting scan
[  178.105848] wlan0_rename: scan completed
[  180.038531] wiphy1: unable to reset hardware: '' (HAL status 0) (freq 0 flags 0x0)

the last line is when I try to bring up the interface with #ifconfig wlan0

I've also tried dadwifi-openhal and I have the same problem

if you need anything else let me know...

Luca Palermo Sabayonlinux development

Change History

03/01/07 11:20:56 changed by mrenzmann

  • description changed.

dadwifi and dadwifi-openhal are currently broken. See also this posting from proski on madwifi-devel.

03/01/07 11:35:59 changed by darkmage@sabayonlinux.org

actually it has been fixed, and currently works with any wifi card except atheros, I've been testing until now, just look at the post from Pavel Roskin | 23 Feb 04:33, the post you showed is rather old, look at the new one http: //blog.gmane.org/gmane.linux.drivers.madwifi.devel

04/08/07 11:44:21 changed by genstef

any progress here? The bug is still present with current svn and -rc5-mm4 for me.

(follow-up: ↓ 6 ) 04/08/07 18:39:13 changed by proski

A workaround is to set channel to a valid value before bringing the interface up. I believe the complete fix would require significant changes to the channel mapping code.

04/21/07 09:46:03 changed by darkmage@sabayonlinux.org

yes the workaround works, but it's still unusable and not recognized under networkmanager, I think a proper hal description is missing so to list it under wifi card list, it's really a pity...I can say that it works far better than the normal madwifi-ng driver, which in my case keeps on looping channels without locking on one of them in case of low SNR, while this one locks immediately and stay stable

(in reply to: ↑ 4 ) 09/14/07 09:44:03 changed by darkmage@sabayonlinux.org

is it posssible to set up channel 1 inside the driver as a startup parameter on default when the driver is modprobed, it won't change anything and the workaround would be included inside the driver

Replying to proski:

A workaround is to set channel to a valid value before bringing the interface up. I believe the complete fix would require significant changes to the channel mapping code.