AmigaOS 4.1.6 and prism2.device (AmigaOne)

Hello folks!

I had AmigaOS 4.1.2 running on my AmigaOne XE G3 and my wireless Network card http://amigakit.leamancomputing.com/c ... ?cPath=32&products_id=158 working fine with prism2.device and WEP encryption.

However after the update it seems that my Internet conneciton is lost.

I suppose that I should chekc out with latest prism2.device:

http://www.os4depot.net/index.php?fun ... driver/network/prism2.lha

Can someone confirm this? That the older prism2.device is not working with 4.1.6 and that the new one should be used?

ps. On Os4depot.net I can not find the older prism2.device version, only the one added on 08 Jan 12 exists.

Installed the new version and now wireless works fine again! Thanks for looking!

I was watching, waiting to see what happened once you tried the new version :)

I use WPA2-AES encryption, which requires upgrading the firmware on the card within Windows.

I'm assuming you didn't do that? WEP works fine without needing to flash the ROM?

The old 1.7 version is still there under prism2_sam.lha, which is a version I modified to remove some of the reset-handler code it had, which was freezing my system when I tried to reboot. The source isn't in the archive because I didn't expect the other one to be overwritten. At the moment I still have the original archive for 1.7 if someone needs it.

Hey guys,

I recently reinstalled my Amigakit wifi card in my SAM and
I'm seeing it wont stay online for more than 30 minutes or
so. The network connection just dies, no crashes, etc...
a quick reboot brings everything back... for another ~30
minutes.

Anyone seen such a thing, have any thoughts on where to
look or have any possible solutions?

Here are a bunch of specifics: my SAM440ep is running the
latest beta system. It doesn't seem to matter if the
connection is active (open IRC, SSH shell session and
pinging the router). I started with the v1.7 driver and
I got the same thing when I switched to the v2.4 driver.
My SAM is just a few inches from my base station (right
now) and the network is "open" - no WEP/WPA. My card's
BIOS has not been updated (weren't able to get the update
software working).

Thoughts? Suggestions?

Thanks!

PJS

@pjs

Have you tried with the latest release version of OS4.1? It could be a problem with the beta.

If not, the next thing I'd suggest is upgrading the firmware on your wifi card; there are some dodgy versions that give connectivity problems. I've been using v1.8.2 successfully on my 3Com card since v2 of prism2.device was released. The recommended version is v1.7.4, but I couldn't find any reason to not go to the higher one.

heh... I did have Roadshow configured to use a fixed
IP address. Figuring that maybe the router didn't like
that with wifi, I changed to ordinary automatic DHCP and
the SAM stayed online for almost an hour and a half.

progress?

The other thing I noticed was the type of response I've
been getting from ping when I leave it running and the
connection dies:

ping: send to: no buffer space available.

What buffer?

I guess I should try booting off a public system (4.1.5)
to see if it makes any difference.

Thanks,

PJS

Well this last test seems to ice it... To me it doesn't
appear to be the OS.

I booted off a 2010 backup that predates my use of the wifi
card. I first tried to run the v2.4 driver and
WirelessManager, but that crashed. Then I tried my older
v1.7 driver and that connected fine. I connected to IRC
and starting pinging my router...

I had roughly the same results: After about 30 minutes my
SAM lost its connection. This time I was letting DHCP do
all the config, so maybe the previous luck with that was
a fluke?

This time I was gone when it crashed and the pinging ran
longer than before. I found that the failed pinging
changed its message from "no buffer space available" to
"Host is down" after a while. I guess that must reflect
Roadshow figuring out something is wrong?

Again, anyone have any more ideas?

Thanks,

PJS