alexatkin wrote:
Because it says packets 0 which would implies it hasnt even tried to connect. I DID include "SetPrism2Defaults SSID LCARS" in user-startup just to be sure, it didnt seem to make any difference. This card is DEINFATELY in the MAC allowed list on the Access Point and works fine in my laptop. Strangely another prism2 card I have isnt being detected by the A1200 at all, although that one could have developed a fault as part of the card is snapped (but seemingly just one side of the onboard antenna and the leds light up).
The card can associate with the access point without the packets sent/received stats being affected. However, if you ran sanautil after the interface is suppposed to be online, Last Start should show a time.
It seems to me that prism2.device isnt initialising the card properly. If I do "sanautil device prism2.device online" I get:
OnLine command failed -- Error: Bad state
WireError: Unit is not configured
If I do "sanautil device prism2.device config" and then the above, I get the same error. If I do "sanautil device prism2.device config address=[the cards mac address]", it still does the same. Clearly the card ISNT initialising, but im not sure what is failing or what I can do about it.
This is a limitation of sanautil. After you configure the card with sanautil, sanautil closes the driver and exits, and the card becomes unconfigured again. The only way around this is to keep the driver open, eg. by stopping "sanautil status" before it finishes by typing in the shell window.
If it was Linux I would check the syslog but Amiga? Is there any way to get more debug information out of AmiTCP?
Anothing thing is the Reset patch seems to be working as I tested with it disabled in user-startup and the card didnt fire up until I plugged it in AFTER booting then. Incidentally, do you need CardPatch AND CardReset? CardReset mentioned needing CardPatch but it didnt say anything more than that. I dont think its related to the problem though, I have both listed in user-startup and card is clearly initialising on some level, just not for AmiTCP.
Is it possibly something stupid like I need a newer version of setpatch? Other libraries AmiTCP depends on? This IS just a basic WB3.1 install. I think I might try softbooting kickstart 3.1 and see if it makes any difference, but I will have barely any RAM left then for testing.
[edit] Kickstart 3.1 did not make any difference whatsoever. :cry:
I think the problem is in the configuration of AmiTCP. It gives the error "no such interface", but I think it would say something like "can't open device" if there were a problem with the driver.
In my AmiTCP configuration, I use the number in the interface name in interfaces, so I'd have:
wlan0 dev=devs:networks/prism2.device
My actual line is:
eth1 DEV=DEVS:networks/prism2.device UNIT=0
Are you sure it isn't something silly like the AMITCP assign pointing to the wrong place? You could use SnoopDOS to check for problems opening libraies or files.
