It does work, however, kernelpolling has a lot of timings that should be tweaked to the appropriate platform/cpu performance. m0n0 aims at slow hardware and has an image for each platform which makes it possible to supply different sets for different hardware. As  pfsense has only a general image supplying different optimizations is not that easy (unless we add some kind of pulldown menu with different optimizations or even a tweak page). This is something we already have discussed and even  tested different settings with a wrap (see http://wiki.pfsense.com/wikka.php?wakka=Tuning ) and might appear in a version after 1.0.

Sorry about that but I didn't check this thread for a while. My box specs are in my signature. I have reflashed my box with 0.97 and all seems fine right now. Maybe a CF card issue. Gotta buy a Sandisk instead of this cheap stuff… Cheers

update, I swap the 580TX to 570TX, and it boots and detect fine.. strange  ??? Maybe my 580TX is faulty

Actually I started one of the "other" topics.  I never did find out what the problem was.  And the problem I was having then is different.  As the blink wasn't random flashes it was at a specific interval of about 2 seconds.  This can be anywhere from less than a second to flashing very rapidly even when nothing is connected. I fixed the problem last time by starting fresh with a new version.  I guess I could try that again. I was just posting incase someone else had experienced this.  I've gone on holiday for a month and a half so I can't get back to fix/diagnose it anymore unfortunatly.  Was worth a try.

good to hear :)

@cybrsrce: Will there ever be support for AXE? ALTQ-capability of the driver itself is an driver issue. You would have to ask the drivermaintainer for that.

Hya Karl :D, Thanks for clarifying this for us ;). Oh I almost forgot: welcome to the forum  ;D Cheers

@hoba: Packagesupport might be split in 2 sorts of packages (suitable for all platforms / suitable for embedded builds). Sexy  8) @hoba: This definitely won't make it in 1.0 though. No worries, we wouldn't want to postpone 1.0 just because of that ;). Cheers

Most Atheros based cards are good. Wistron Neweb CM-9 cards work fine. (minipci) Senao 5354 MP PLUS ARIES2 4G (minipci) Dlink DWL-AG530/AG520 (PCI) 3com 3CRDAG675 (PCI) In general you can refer to this list: http://www.madwifi.org/wiki/Compatibility since the freebsd HAL and the MadWiFi HAL is the same. (cards reported working on madwifi-ng might not work !!) But forget about pcmcia/cardbus cards, they might work on linux and not on freebsd and vice versa.

Nevermind, I removed the PCI Card and Reseated it.  Everything is working now.

Via epia boards ? There are a lot of platforms out there. Problem is to support all this we need to cross compile a bunch of versions. For now your best bet will be a via epia board if you are looking for some performance while still keeping it small. Or you could have a look at the nexcom boxes. www.nexcom.com.tw

@Jesse7: The other endpoint is my DSL router.  So I guess it needs to be in half duplex mode.  Thanks hoba very helpful. Generally ADSL modem routers use half duplex.  Mine does as well.

Thanks. Is pretty much what I thought.  I did do some reading around before posting, I was just hoping someone maybe had a workaround. I am happy for it to be shapped.

I replaced the image with 0.92 and it now see the wireless ath0.. Thanks guys. If you still need the dmesg on this new release, let me know. Richard @lsf: Get the newest version (0.92), it has a newer HAL/driver for ath. And it should support that card. Also add all the dmesg lines regarding ath. And a pciconfg -vl from the shell would be nice.

Soon.  We have a smaller version but we are working out the builder scripts issues.