Community discussions

MikroTik App
 
tjburbank
just joined
Topic Author
Posts: 2
Joined: Wed Jun 09, 2004 2:23 am
Location: Preston, Idaho
Contact:

CM9 Radios not being Recognized

Thu Oct 12, 2006 8:00 pm

Has anyone found a solution to the problem where Atheros CM9 radios do not appear in the Interfaces section of RouterOS when installed in a WRAP or Routerboard?

If you go to /system resource pci and print, it will show that it is installed and seen at a hardware level, but will not appear in /interfaces wireless

I usually get it working after removing it and swapping mini-pci slots many times, and do /system resets and upgrade / downgrade the MikroTik RouterOS version, but it is very frustrating.

I notice the problem everytime I put a CM9 in a board that is already programmed, and which already has a NL-2511 radio in it. Not sure if this helps.

Currently I am having the issue with 1 WRAP board that is running 2.9.30. However I have downgraded it back to 2.9.25 and same result.

In the past, I have found that once MikroTik finds it, it will continue working, just getting it to be recognized the first time is the chore.

Your assistance is greatly apprieciated.

-TJ
 
User avatar
sergejs
MikroTik Support
MikroTik Support
Posts: 6697
Joined: Thu Mar 31, 2005 3:33 pm
Location: Riga, Latvia
Contact:

Fri Oct 13, 2006 8:53 am

Make sure that antenna's pigtail does not touch any metal part of the wireless card.
If you will have the same problem without pigtail, plug card to another board. Report back with the results.
 
jarosoup
Long time Member
Long time Member
Posts: 596
Joined: Sun Aug 22, 2004 9:02 am

Sat Oct 14, 2006 2:34 am

Upgrade the firmware on your wrap...
 
Setsquare
newbie
Posts: 40
Joined: Mon Feb 06, 2006 1:05 pm
Location: Durban, South Africa

Sun Oct 15, 2006 2:29 am

I have never had this problem with a CM9 in a WRAP. Upgrading BIOS cant hurt but this is susposed to make it detect single chip radios and the cm9 isnt single chip as far as I am aware.
 
User avatar
BrianHiggins
Forum Veteran
Forum Veteran
Posts: 720
Joined: Mon Jan 16, 2006 6:07 am
Location: Norwalk, CT
Contact:

Mon Oct 16, 2006 1:41 am

I had this happen on a 532 a few days ago... it happened when I upgraded the bios version from 1.5 to 1.14 (running 2.9.28) had to reboot it 3 times before everything started working correctly...