No unresolved externals at all when it worked. For that matter - I have never got a program/module working when I got unresolved externals.

In case u did not know...
Unresolved externals are usually function calls that have not been located (which is the reason why the source is useful incase the people that wrote this software are making references to routines that are different for your hardware or OS). The program is therefore incomplete. If they did work, they would not be very reliable.

So its probably most likely that its happening because of the PCI 2.2 then.

Maybe. But I know the card works without PCI 2.2 (which is supposedly backwards compatible). On my same machine, my dual boot Win2K box has no probs with it. BTW - i tried to compile the latest source from minitar and got a seg fault on the module during boot up (as per their instructions, they said to reboot after installing it).

I have sent support an email, and if I sacrifice enuf goannas, dingoes and the odd drop bear, I hope I get a reply.

Well support has not responded, and I got impatient - so I got busy. For anyone else out there that is in a similar boat to me, here's what u can try (I am kicking myself that I didnt try this earlier)...

1) Unpack the source for rt2400.o. It can be downloaded from
www.minitar.com

2) Edit the makefile

3) Locate the "CFLAGS :=" section and change the value of
-march=
to suit your architecture (my wireless router is a Pentium 233MMX - or i586)

example - this is what the minitar folks supplied:
CFLAGS := -D__KERNEL__ -I$(LINUX_SRC)/include -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -DMODULE -DMODVERSIONS -include $(LINUX_SRC)/include/linux/modversions.h $(WFLAGS)

and I changed it to:
CFLAGS := -D__KERNEL__ -I$(LINUX_SRC)/include -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i586 -DMODULE -DMODVERSIONS -include $(LINUX_SRC)/include/linux/modversions.h $(WFLAGS)

4) Follow their instructions for compiling and with a bit of luck u could be working! (Well it worked for me anyway)

That goanna, dingo and drop bear is happy now I won't have sacrifice them to the gods of support

That would explain everything...thanks for that

Does anyone know how to get this thing into ad-hoc mode, as I dont have an AP. It was easy with the card under Windows, but i wouldnt even know where to start under linux.

From www.minitar.com you will find a driver pack called:
Linux Drivers (8/7/03) (4.5MB)

Even tho the included rt2400.o driver failed to work for my system, the driver pack does install a compiled binary that does work called RaConfig. The installation will want to install this in /usr/local/bin. Run this program under X. And u will find that u can set your card to ad-hoc mode. This is what I used to configure my cards which are all using WEP and ad-hoc mode.

Hope this helps.