Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: mikep on June 25, 2007, 12:24:13 PM
-
Hi
With my A1200 Subway clockport USB controller
i recently tested two different USB to LAN adapter.
One is levelone 10/100, the other is Eyetech/Noname 10/100,
both have Pegasus/Pegasus II chipsets.
What really does surprise me, was the extreme slow transfer
rates of these adapters. Both had a transferrate of about
4 to 5 kilobytes/sec .
Is this normal for usb to lan adapters on A1200 subway controller card ?
All tests were made both with AmiTCP4 and MiamiDX.
System is OS3.9, BPPC 603e/210-060/50, BVPPC.
Hope someone does have some hints for me to that subject.
-
Although I haven't tested such adapters It may be a good idea to check out that you have set the network to the same mode: full duplex/half duplex 10/100 etc...
I know that Subway may be slow but I don't think that is normal. I would bet that you have your PC in full duplex or half duplex and your miggy in the opposite mode.
-
Hi, crumb
Indeed, that was one of my first thoughts. But my network
is a 10/100mbit autosensing, fullduplex one, USB_to_LAN COntroller have been configured via Trident in various ways (first AUTONEGOTIATE, then preset with 100Mb FD, then 10Mb FD, the 100Mb HD, then 10Mb HD).
But nothing led to a higher transfer rate, always about 4 to 5 KB/s - curious .
-
im getting 40-50kB/s on a4000/060 with thylacine card.
slow as hell :-D
-
I remember with subway I too was getting 4-5kb/s with a 060/50 csppc... I will test with algorPRO now , I have the same dongle as Chain :-D
-
mikep wrote:
Hi
With my A1200 Subway clockport USB controller
i recently tested two different USB to LAN adapter.
One is levelone 10/100, the other is Eyetech/Noname 10/100,
both have Pegasus/Pegasus II chipsets.
What really does surprise me, was the extreme slow transfer
rates of these adapters. Both had a transferrate of about
4 to 5 kilobytes/sec .
Is this normal for usb to lan adapters on A1200 subway controller card ?
All tests were made both with AmiTCP4 and MiamiDX.
System is OS3.9, BPPC 603e/210-060/50, BVPPC.
Hope someone does have some hints for me to that subject.
Maybe original A1200 clockport is (very)(too) slow...
Its slowness is not perceived for a mouse, but for a network it is not the same rate...
-
> What really does surprise me, was the extreme slow transfer
> rates of these adapters. Both had a transferrate of about
4 to 5 kilobytes/sec .
No, that's not normal. Although I didn't test all new drivers on the old Highway and/or Subway cards, I wouldn't see why the driver should perform that bad. On the Algor, I had transfer rates of about 400KB/sec with MiamiDX.
-
Yesterday evening i did some further testing.
First, tried both LAN adapter with windowsxp -> adapter are ok, transferrates are normal (very high) -> this means the adapter hardware has no defect.
Second, connecting a USB memory stick to the Subway gives a transfer rate of about 410 KB/s, so the clockport itsself is not the bottleneck.
Third, tried PCMCIA-Card 3c589 network with MiamiDX and AmiTCP. All ok, which means TCP/IP-stack is ok, transferrate was about 320 KB/s .
So, perhaps a software problem with the usbpegasus.device ?
Any hints in what i can do to solve this problem are highly welcome .
-
cmon, no one here who can help, or had the same problem and possibly solved it ??
or give some advice with which tools i can inspect,debug,monitor the network, the usbdevice, ... in order to get hints about the problem ?
Any help would greatly be appreciated
-
due to lots or work, I could not test the algorPRO, but the subway/kickflash combo had similar extremelly low speed as yours...
-
Could you test the adapter under MOS? Perhaps the device driver is not fully compatible with the 68K OS.
Have you tried running the tests with WarpOS disabled (just removing the Warp libraries temporarily) to see if it still works fully under 68K only conditions?
-
as a sidenote, the kickflash/subway combo does not work for me in MOS... the 4000 freezes when I get it online...
-
sadly i cant test it under MorphOS, because i dont have a MOS installation on my machine, hmmm - i think, should be worth giving it a try. Will report what happens as soon as i get familiar with MOS (never did use it up to now).
Disable WarpOS - ok, will do a test drive and report the results
Thanks
-
> Any help would greatly be appreciated
Unfortunately, I didn't have the time to refit my subway/highway yet to do some tests.
The very low rate rather sounds to me as if packets get lost or are somehow delayed. Using a raw tcp monitor on both sides of the connection (e.g. MiamiTCPDump) could give some insight what happens there. Also, try ping to see if packets get lost, with varying ping packet sizes.
-
Now i did some further testing:
WarpOS has been completely deinstalled/disabled, so i have now a native 68K environment, but the effects are the same - very low transfer rates.
I monitored the transfer between Amiga and PC by just inspecting the NET LED indicator. Its curious, but as soon as AmiFTP got connected to PC (i do see the welcome message from ftp-server), AmiFTP needs really lot of time to PWD, LIST, CWD into the ftpserver. It really, really takes a very long time to get the filelist (COMMAND ls or LIST).
The NET LED indicator on my USB-LAN adapter shows a strange behaviour - just before a download gets startet (but slow), Amiga tries for about one minute to contact ftp-server, i can see the LED flashing really often (about 50 times) but nothing happens, no answer from PC, then suddenly transfer starts, but very slow.
Sadly, i cant test it with MOS, because the downloadable PoseidonMOS Package from www.platon42.de does not contain the class drivers for USB-LAN adapter.
-
Are there huge log files being generated somewhere? Had that problem with Samba, connection was so slow that it timed out quite a bit. Disabled logging in Miami AND Samba and it got a lot better. Switched to AmiTCP and it flew along :) Haven't tried the USB driver though - is there a chance it's getting caught up with some other hardware? Is it the only device on your clockport? Are there more USB devices plugged in at the same time?
-
ok, seems to me, that i have to go into deep discovery now, will do ping tests and monitoring tests and report it back later.
BTW:
the poseidon guide tells something about connection timeouts and/or dead device in case someone has no valid license
i bougth my Subway from Vesalia, i am using poseidon v3.6 and Trident tells me that i have a OEM license for Subway controller. Also Trident prefs sometimes tells me in its window: "PoPo kicks ass" - whats this ?
Do i have a correct license ?
-
Logging is completely disabled, no log files at all. dont know whether it interferes with other hardware - how can i test this ?
I only have Subway card on my clockport (its an A1200). Its not the only device on Subway, my Mouse is in port 2, network adapter is on port 1 of Subway controller.
By way of trial i should remove the mouse and see what happens ?
-
Now, things are getting a bit clearer now.
I did some testing with Miamiping with options -f (ping flood) and varying packet sizes. Following some stats:
Paket Transfer Packet
size rate loss
(bytes) (KB) (%)
128 37 0
512 104 0
1024 166 0
1200 175 0
1400 198 0
1472 203 0
>1472 6 100
So, as soon as packet sizes is greater than 1472, transfer rate drops to about 6KB/s and packet loss rate is 100 %.
What does this mean in terms of my FTP-Transferrate problem.
Some further tests. I did install Samba, called smbclient, connected to the PC, then with the get command i retrieved a big file (20MB of size). PacketMonitor tells that transferrate is now about 220 KB/sec, thats really good.
But as soon as i try to connect to my PC with FTP, transfer rate drops down that bad. If i use the same FTP-Client with my PCMCIA-Network-Card, then all is ok and transferrate is about 310KB/sec - only with Subway-Card rate drops down.
Does Subway-Stack have a problem with packetsize of 1500 ?
-
You need to set the maxx packet size on the pc to below this then at a guess. I really cant remeber the dos command for this. Someone will know
-
Hmmm - ok, that would be a solution, but not very user friendly. And - as i said in the other posts, as soon as i use
(on amiga side) my PCMCIA Network card, with all other parts left the same (MiamiDX Stack, ATC) it does work perfectly, the only part thats got exchanged is the hardware device (USB Subway).
So why should i change max packet size on PC side. ok - if i can find out how to to that, i will give it a try.
Further notes.
Within MiamiDX config, i can query the Sana-II Parameters from usbpegasus.device, it gives me a MTU of 1500. I just tested to change this value to 1400 and save configuration, then restarted all - but doesnt help, same effect as before.
I dont think that subway card gets informed about changed MTU value. Is it allowed at all to change this parameter ?
-
MTU thats the one. Though you will need to set this on your router as well. I know its not very user friendly, but shouldnt really effect your overall system performance, and if it solves the problem then happy days.
I know on my system it all set to 1500
-
Ok - then this evening i will try this out and report back if it suceeded.
BTW:
how gets subway, miami, USB-Lan-adapter the info about changed MTU value on - lets say - the router ? sorry, im not so deeply familiar on low level network protocols.
But the best place to change this in a transparent way, should be on Amigaside in setting the SANA parameter for the device - and as i said i presume that the USB-LAN-adapter doesnt get informed about the changed MTU-value (how can i test this ?)
-
With SUBWAY you have *always* a valid license for Poseidon, as E3B delivers an OEM key. Only the version of Poseidon can make a difference: older SUBWAYs have a V2.x license, with OEM upgrade path to V3.x (partly paid by E3B), newer SUBWAYs have a V3.x license included.
Michael
-
Ok - now changed MTU values (router, and amiga) - but no effect, always get extreme slow transfer rate with ftp.
BTW, setting MTU via MiamiDX SANA-II parameter settings page does in fact work. Calling MiamiNetStat tells me the actual values for MTU for each device.
Inspecting the data transfer with MiamiTCPDump also gave no insight. No package losses are reported, instead during ftp data transmission only about 4 packets/sec are sent from amiga to pc and back.
Why so less ? I think someone is delaying packet transfer.
To Summarize all of that.
- Using USB-LAN adapter work with samba, there i get over 200 KB/sec
- Using it with FTP doesn not work, transfer rate is about 5 KB/sec
- Setting MTU values does work, but has no effect on bad FTP-Transfer rates
- Using FTP, Samba, Telnet with my TCP/IP-Stack but with 3com PCMCIA-Card does work great, about 300 KB/sec and more
So, what else can i check now to get USB-LAN-Adapter to work properly ?
-
Try a different FTP client/server on the Amiga side?
It could be a problem which is specific to that FTP client + LAN adapter combo.
Regards
Rich
-
I tried various ftp clients:
- AmiTradeCenter
- AmFTP
- AmiFTP
- SimpleFTP
- mFTP
- MiamiFTP
but whichever i use, the effect is always the same.
I did some more tests. i said, with samba using smbclient and the builtin get command i get over 200 KB/sec. Yesterday i installed smbfs/smb-handler, and what shall i say. Using smbfs/smb-handler gives me suddenly the same bad transferrates than ftp. This is really curious.
Greetings,Mike
-
Today I had the time to do some testing (and in the progress fry my Subway USB :-( ).
Apparently, the later Asix-Chipsets have the ability to send multiple packets in one USB transfer (up to 2K of packets, hence: 1500+548 max) and the class did not cater for this. I have fixed this now, and the updated class is available on request until I release the next Poseidon update.
-
Wow!
Thanks for the update.
-
Hi
That sounds quite good, can you send me the update. Will test it and report back, if my problems are gone or not.