Can you recommend a custom firmware that has source available that is compatible with this unit?
I cannot find many people mentioning this device specifically.
It would be nice to play with adding simple features.

Thanks for your tips

Edit: Since this post I have found this firmware to work well.
http://mgb111.pradnik.net/
I have not tried compiling my own since then. possibly in the future if I find time.Thanks again for the help.

I am trying to figure out what type of file that initrd from the image is.
The 'file' command in linux doesn't recognize it. it just calls it data.
Sometimes squashfs files are called that but my unsquashfs version doesn't recognize it. it just says "Can't find a SQUASHFS superblock on rootfs"

Anyone have any idea how to access the root filesystem stored in the image?

Thank you very much!
Your advice did the trick Schufti. My device boots up to the original (updated) firmware.
And that information is very much appreciated chimbo! I am sure I will be trying that out next time I run into trouble.

PS, The mini-pci slot does not have the slot soldered on to it. Could I use the usb ports and a usb device?

I have an Airlink101 ANAS350 that seems to be similar to the forums topic hardware.

The first thing I did when I got it was gain access to the command prompt (method as mentioned here -->http://forum.openwrt.org/viewtopic.php?id=16269)and dump the firmware to a file. ie. 'cat /dev/mtd0 > firmware.bin'
Then I upgraded to the latest firmware on the airlink101 support site. Then I gained access to the telnet again and dumped the new firmware to a file aswell.

Then I went looking for the GPL sources to the firmware.
Unfortunatly The only thing Airlink101 released is what looks to me to be the toolchain. link-->  http://www.airlink101.com/gpl/anas350/

Eventually I found some sources that were for a similar product. (I don't exactly remember, i think it was from here --> http://mgb111.pradnik.net/)
I followed the instructions to create a firmware and then flashed it via the web interface.
The web interface accepted it and flashed it to the device.
After that he device seemed to boot fine but I could not find it on the network.
To my embarrassment I did not enable the code that enables and sets up the network interfaces and the IP address. (at least I hope thats all it is)

Anyway the recovery loader shows up so I think I may have a chance to get it going again.
But the problem is I cannot get the tftp server to accept any firmwares. after entering the tftp command it finishes up within 10 seconds, Nowhere near the 55 seconds it mentions in the wiki.
So that problem makes me thing it may be a branding problem. I cannot figure out which brand would the device be now? would it be the brand set by the firmware I created? (MGB111) or the brand of the original firmware? Which I think may be ALK_RUS021. because when you run the program that airlink gives you it decompresses these files to your users temp folder;
ALK_RUS021toQueen.bin.tmp
ANAS350_400a7.EXE.tmp
boot_400a7v2.BIN.tmp
itrd_400a7v2.BIN.tmp
rnel_400a7v2.BIN.tmp
tftp_400a7v2.BIN.tmp
WDPMM2-2203.BIN.tmp


or would it be the brand of a machine that uses the queen header?(as that one file seems to convert the ALK_RUS021 to queen?)

Thanks for reading my post. After all that I have built a unbuffered jtag and soldered a pin header onto the board in preperation of what may need to be done.
the test done with the multimeter as described on the jtag page suggest that i do not have the pull up resister needed to enable jtag on my device. can anyone with this device shed any light on this topic?