Tertiary firmware load problem for Netgear MA311 AP

Hi, everyone:
I want to make the card working at AP mode.
The card works well at Ad-hoc mode. Here is the kernel messages:
 
Sep 12 14:52:04 BobLinuxWorkstation kernel: PCI: Found IRQ 9 for device 
0000:01:07.0
Sep 12 14:52:04 BobLinuxWorkstation kernel: PCI: Sharing IRQ 9 with 0000:00:
01.0
Sep 12 14:52:04 BobLinuxWorkstation kernel: A Prism2.5 PCI device found, 
phymem:0xfafff000, irq:9, mem:0xd087e000
Sep 12 14:52:06 BobLinuxWorkstation kernel: PDA Read from 0x007f0000 in NV 
space.
Sep 12 14:52:06 BobLinuxWorkstation kernel: PDA Read from 0x007f0000 in NV 
space.
Sep 12 14:52:06 BobLinuxWorkstation kernel: Writing 2590 bytes to ram 
@0x7e0000
Sep 12 14:52:06 BobLinuxWorkstation kernel: Writing 2268 bytes to ram 
@0x7e0b00
Sep 12 14:52:06 BobLinuxWorkstation kernel: Writing 2 bytes to ram @0x7e17fe
Sep 12 14:52:08 BobLinuxWorkstation kernel: Writing 4096 bytes to ram 
@0x7e17fe
Sep 12 14:52:08 BobLinuxWorkstation kernel: Writing 4096 bytes to ram 
@0x7e27fe
Sep 12 14:52:08 BobLinuxWorkstation kernel: Writing 4096 bytes to ram 
@0x7e37fe
Sep 12 14:52:08 BobLinuxWorkstation kernel: Writing 4096 bytes to ram 
@0x7e47fe
Sep 12 14:52:08 BobLinuxWorkstation kernel: Writing 4096 bytes to ram 
@0x7e57fe
Sep 12 14:52:08 BobLinuxWorkstation kernel: Writing 4096 bytes to ram 
@0x7e67fe
Sep 12 14:52:08 BobLinuxWorkstation kernel: Writing 4096 bytes to ram 
@0x7e77fe
Sep 12 14:52:08 BobLinuxWorkstation kernel: Writing 4096 bytes to ram 
@0x7e87fe
Sep 12 14:52:08 BobLinuxWorkstation kernel: Writing 4096 bytes to ram 
@0x7e97fe
Sep 12 14:52:08 BobLinuxWorkstation kernel: Writing 4096 bytes to ram 
@0x7ea7fe
Sep 12 14:52:08 BobLinuxWorkstation kernel: Writing 4096 bytes to ram 
@0x7eb7fe
Sep 12 14:52:08 BobLinuxWorkstation kernel: Writing 4096 bytes to ram 
@0x7ec7fe
Sep 12 14:52:08 BobLinuxWorkstation kernel: Writing 4096 bytes to ram 
@0x7ed7fe
Sep 12 14:52:08 BobLinuxWorkstation kernel: Writing 686 bytes to ram 
@0x7ee7fe
Sep 12 14:52:08 BobLinuxWorkstation kernel: Writing 4096 bytes to ram 
@0x7f0800
Sep 12 14:52:08 BobLinuxWorkstation kernel: Writing 3282 bytes to ram 
@0x7fe000
Sep 12 14:52:08 BobLinuxWorkstation kernel: ident: nic h/w: id=0x8013 1.0.0
Sep 12 14:52:08 BobLinuxWorkstation kernel: ident: pri f/w: id=0x15 1.1.4
Sep 12 14:52:08 BobLinuxWorkstation kernel: ident: sta f/w: id=0x1f 1.8.4
Sep 12 14:52:08 BobLinuxWorkstation kernel: 
MFI:SUP:role=0x00:id=0x01:var=0x01:b/t=1/1Sep 12 14:52:08 
BobLinuxWorkstation kernel: CFI:SUP:role=0x00:id=0x02:var=0x02:b/t=1/1Sep 12 
14:52:08 BobLinuxWorkstation kernel: 
PRI:SUP:role=0x00:id=0x03:var=0x01:b/t=4/5Sep 12 14:52:08 
BobLinuxWorkstation kernel: STA:SUP:role=0x00:id=0x04:var=0x01:b/t=1/15
Sep 12 14:52:08 BobLinuxWorkstation kernel: 
PRI-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
Sep 12 14:52:08 BobLinuxWorkstation kernel: 
STA-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
Sep 12 14:52:08 BobLinuxWorkstation kernel: 
STA-MFI:ACT:role=0x01:id=0x01:var=0x01:b/t=1/1
Sep 12 14:52:08 BobLinuxWorkstation kernel: Prism2 card SN: 99SA01000000
Sep 12 14:52:08 BobLinuxWorkstation kernel: p80211knetdev_hard_start_xmit: 
Tx attempt prior to association, frame dropped.

I recompiled the driver with the tf010102.hex tertiary firmware, and after 
installing drivers, there are a prism2_tf.hex file in /etc/wlan.But it when 
I reloaded driver, the file seems not being accessed during the process and 
the kernel debug information is just as the above.

And then I mannually used prism2dl command, but I get following lines:

Couldn't fetch PRI-SUP info
Reading S-record file prism2_tf.hex...
NIC ID: 0x8013 v1.0.0
MFI ID: 0x1 v1 1->1
CFI ID: 0x2 v2 1->1
PRI ID: 0 v0 0->0
Version: ID 0x14b 1.1.2
Compat: Role 0x1 Id 0x1 v1 1->1
Compat: Role 0x1 Id 0x2 v2 1->1
Compat: Role 0x1 Id 0x3 v1 2->2
Seq: 0
Platform: ID 0x800a 1.0.0
Platform: ID 0x800b 1.0.0
Platform: ID 0x800c 1.0.0
Platform: ID 0x800d 1.0.0
Platform: ID 0x8012 1.0.0
Platform: ID 0x8013 1.0.0
Platform: ID 0x8014 1.0.0
Platform: ID 0x8016 1.0.0
Platform: ID 0x8017 1.0.0
Platform: ID 0x8018 1.0.0
Platform: ID 0x801a 1.0.0
Platform: ID 0x801b 1.0.0
Platform: ID 0x801c 1.0.0

prism2dl: finished. 
What 's problem? How can I make the tertiary firmware loaded automatically?
 Any suggestion? Please give me a light.

_______________________________________________
Linux-wlan-user mailing list
[email protected]
http://lists.linux-wlan.com/mailman/listinfo/linux-wlan-user