Who's Online |
63 user(s) are online ( 41 user(s) are browsing Forums)
Members: 1
Guests: 62
rwo,
more...
|
|
|
|
Re: what wifi pci card is good for os4 ?
|
Posted on: 2017/5/28 4:13
#21
|
Just popping in
|
@kas1e
There's also my 54Mbps atheros5000.device. Although some people have had problems getting it working on certain systems, when it works it works well. See the archive for details of supported cards.
|
|
|
|
Re: Atheros WLAN driver success/failures
|
Posted on: 2013/11/14 4:03
#22
|
Just popping in
|
@Spirantho In a way it's a pity it's working for you. If it wasn't you'd be a good person to debug it Do you have any other OS4 machines you could try it in? @utri007 I got a short reply from aCube more than a month ago, saying that they would look into it. At the moment, it looks like the the best way to sort out the incompatibilities would be for someone to lend me a SAM, but I realise that that would be a significant financial undertaking.
|
|
|
|
Re: Atheros WLAN driver success/failures
|
Posted on: 2013/9/23 1:24
#23
|
Just popping in
|
Quote: pjs wrote:
FWIW, I took the atheros card to my office, plugged it into my A1-XE and it's mostly working here. This is with the v15 driver from OS4Depot.
The only drawback is that I have to cold boot and then warm boot to get the machine started with the card in, but I think this may be a problem with UBoot variables.
If this happens when the driver isn't started during boot, then you're probably right. Thanks for doing the tests.
|
|
|
|
Re: Atheros WLAN driver success/failures
|
Posted on: 2013/9/23 1:21
#24
|
Just popping in
|
Quote: yoodoo2 wrote:
I'm very keen to get wireless up and running on my SAMep, but it's in a tiny case so would need a low profile card (or preferably a USB dongle). Any ideas on which one to get? I'm happy to splash out on a couple of different ones to try out and pay for a working driver.
There should be some cards available with a low-profile bracket, but you should probably wait until the problems other SAM users have with Atheros cards are resolved. There are no USB WiFi dongles available that have Amiga drivers unfortunately.
|
|
|
|
Re: Atheros WLAN driver success/failures
|
Posted on: 2013/9/19 18:14
#25
|
Just popping in
|
Quote: pjs wrote:
Bear in mind, this isn't a SAM specific problem - the atheros driver wasn't working in my X1K either.
But the problem in the X1000 appears to be different, as it partially works for you.
|
|
|
|
Re: Atheros WLAN driver success/failures
|
Posted on: 2013/9/18 2:58
#26
|
Just popping in
|
@pjs & utri007:
Do either of you have Linux installed on your SAMs? If so, do your Atheros cards work under Linux?
Reports are welcome from anyone else too, or are there only two SAM owners with an interest in wireless networking?
|
|
|
|
Re: Amigakits's wlan card
|
Posted on: 2013/9/16 20:09
#27
|
Just popping in
|
Quote: pjs wrote:
I tried to get a PCtech friend to reflash mine, but the listed software wouldn't recognize the card.
It's sometimes important to force the use of the Linksys driver mentioned on the reflashing linked to in the driver docs. Quote: As it stands, my Amigakit card refuses to stay online for more than an hour or so and I'm hoping reflashing might help that (??).
It might help. While most of my Prism-II cards were stable both before and after reflashing, one of them was unstable beforehand, but worked perfectly after reflashing.
|
|
|
|
Re: Atheros WLAN driver success/failures
|
Posted on: 2013/9/15 18:56
#28
|
Just popping in
|
@pjs
It looks like you have the same problem as utri007. As I said to him:
Do other cards work in that PCI slot? E.g. an old RTL8139 or SoundBlaster. If so, do they get the same interrupt number? Also, what range are the interrupts for other PCI devices in?
EDIT: In general have SAM owners had any problems using other PCI cards?
|
|
|
|
Re: Atheros WLAN driver success/failures
|
Posted on: 2013/9/7 17:02
#29
|
Just popping in
|
@pjs
For initial testing, I'd recommend not enabling any TCP/IP interfaces. Just run "WirelessManager atheros5000.device VERBOSE" in a shell. If it connects, leave it running for a while to see if it's stable.
It's also important to disable WirelessManager from starting at boot if you want to test it in a shell: two copies running can cause problems.
The first driver version to try is the updated one on Aminet, before trying any debug versions.
|
|
|
|
Re: Atheros WLAN driver success/failures
|
Posted on: 2013/9/6 13:44
#30
|
Just popping in
|
Quote: utri007 wrote: I don't have anyt other cards to test :( but I tried to another PCI slot and it doesn't make difference.
Except that it seems to have changed the interrupt number to 45. Quote: That's normal when the device is not online. Quote: PS. Recoverable alert is :error : 0100000F Task : 0x5704F830 PS.. Task number is changing for every boot. I opened scout and tried to check wich task it is. There is no task for that address or at least before sanautil. Is it possible that task is wich causes that alert is atheros device itself?
That error means "bad free address". It might be a bug in SANAUtil. I wouldn't say it's related to the failure to get the driver working.
|
|
|
|
Re: Atheros WLAN driver success/failures
|
Posted on: 2013/9/5 19:39
#31
|
Just popping in
|
@utri007
Thanks. The interrupt number is as expected, but you shouldn't need to run WirelessManager for the test.
It doesn't matter whether you run WirelessManager from Startup-Sequence or Network-Startup, but it should run before the TCP/IP interfaces are brought up (with AddNetInterface I'd expect).
Do other cards work in that PCI slot? E.g. an old RTL8139 or SoundBlaster. If so, do they get the same interrupt number? Also, what range are the interrupts for other PCI devices in?
|
|
|
|
Re: Atheros WLAN driver success/failures
|
Posted on: 2013/9/5 8:56
#32
|
Just popping in
|
Quote: utri007 wrote: Has you considered to ask this from Hyperion's forum or aCube support? I could do that, I wouldn't know what to ask :(
I'm not sure I'd know what to ask either, except that it seems to be something to do with interrupts. Here's another test version that reports the interrupt number used. Don't run WirelessManager with this version; just download SanaUtil from Aminet and run as follows: sanautil -d atheros5000.device status Then please report the figure for "bad multicasts". This should be the card's interrupt number.
|
|
|
|
Re: Atheros WLAN driver success/failures
|
Posted on: 2013/9/3 8:31
#33
|
Just popping in
|
Thanks utri007. It seems that other devices are not the problem. I have another version for you and others to test. The source code can also be downloaded for anyone who wants to try hacking it (for simplicity, the HAL is only included as a binary blob for now). A good starting point would be the PCI set-up in expansion.c. To build the driver, follow these steps: 1. Copy the sana2wireless.h file to SDK:include/include_h/devices/ 2. CD to the atheros5000 dir and run this: make -f Makefile.OS4 install
|
|
|
|
Re: Atheros WLAN driver success/failures
|
Posted on: 2013/9/1 4:21
#34
|
Just popping in
|
Quote: utri007 wrote: I just opened my Sam and I can confirm, my card is DWL-G520, not a DWL-G520+
Forget that I said key_mgmt does grim reaper, it doesn't do that.
Thanks for the info. Quote: Other PCI card is Radeon 9250
I don't know if this is in response to my question about interrupt lines, but what I'm interested in knowing about is PCI devices reported in Ranger with the same interrupt line as the wireless card. This includes PCI devices integrated on the motherboard, not just real PCI cards.
|
|
|
|
Re: Atheros WLAN driver success/failures
|
Posted on: 2013/8/31 6:11
#35
|
Just popping in
|
Quote: pjs wrote:
ncafferkey, any thoughts on all this? Anything else to test? Need any more data? Or should I continue on with the game of wifi card roulette? ;)
The DWL-520+ is not an Atheros card. Spin the wheel again Quote: utri007 wrote:
There is scan_ssid=1 in settings file, does it mean it will scan chanels to find correct one?
No, it means it will connect to hidden networks, by directing the scan to a specific SSID. Maybe the hang in WirelessManager is caused by other drivers not sharing interrupts properly. What other PCI devices have the same interrupt line as the Atheros card? (In utri007's case, that's 0x32.) @utri007 & Goos Are you sure you have a DWL-G520 +? I thought those had Texas Instruments chipsets.
|
|
|
|
Re: Atheros WLAN driver success/failures
|
Posted on: 2013/7/17 7:06
#36
|
Just popping in
|
@Jurassicc & utri007
Please try with the antenna detached. Obviously it won't connect, but it would be interesting to see if the verbose output continues further without the influence of local access points.
|
|
|
|
Re: Atheros WLAN driver success/failures
|
Posted on: 2013/7/14 8:43
#37
|
Just popping in
|
Quote: ncafferkey wrote: @Jurassicc
It's strange that it doesn't work for you, because I have also tested a WPN311 in a Peg-II, albeit a G4 version. Maybe it's down to the OS version. What version are you running?
After performing seven updates to OS4.1, I now have the same OS version as you and other testers, but the driver still works fine for me. I don't know what else could be the problem. Same machine, same card, same OS version. What router do you have, and are there neighbours' wireless networks visible?
|
|
|
|
Re: Atheros WLAN driver success/failures
|
Posted on: 2013/7/9 2:18
#38
|
Just popping in
|
Quote: Jurassicc wrote: @ncafferkey
Will do. I assume it wont work in the A1200 / A4000(t) because of the missing DMA support for the Mediator. Does the atheros chipset support PIO ?
I didn't know OS4 doesn't support DMA with the Mediator. The driver should work only if DMA is supported. There is no PIO mode for the Atheros chips.
|
|
|
|
Re: Atheros WLAN driver success/failures
|
Posted on: 2013/7/8 17:45
#39
|
Just popping in
|
@Jurassicc
The verbose output you sent me is similar to what others have posted: it gets stuck after trying to send the first scanning message. The "unauthorised" messages are normal.
I notice that your signature indicates you have other OS4 machines. Do you feel like testing your wireless card in them? On my end, I'll have to upgrade the OS on my Peg-II to the latest version to see if that leads to the same results as you've seen.
|
|
|
|
Re: Atheros WLAN driver success/failures
|
Posted on: 2013/7/8 0:37
#40
|
Just popping in
|
@all Please do the following: 1. Tell me the results of running this updated DMA test program. 2. Tell me what OS version you are running, and exec version (run "Version exec.library full"). 3. Run Ranger (downloadable from OS4Depot), click on the "PCI Bus" tab, then on the entry for your wireless card, and report the contents of the Interrupt box.
|
|
|
|