...and shipping costs drop if you buy multiple cards.
Hear ye, Hear ye!of the very last MCA cards.
There's a new dream team on the block.
That may be you, your favorite PS/2 and your IBM 10/100 Mbps Ethernet Adapter (9-K)!
After weeks and months of reverse and forward engineering, we now have drivers for this very late manufactured, 32-bit Micro Channel 100 Mbps capable Ethernet Adapter type 9-K, code name "San Remo", that IBM released only for the RS/6000 series as one
For 30 years there were no drivers outside of AIX, IBM's proprietary Unix operating system.
Today you may start running it in Windows 95, probably also 98, and Linux 2.2!
Get your copy here:
http://www.holzapfel.biz/8F62/sanremo-win9x.zip https://github.com/holzachr/sanremo-linux
Please note that those are considered beta drivers, and may not be perfect yet.
They were tested on Windows 95 B OSR2 and Debian 2.2 on a souped-up PC 750. I would love to hear your personal feedback on a true Micro Channel system.
This was a joint effort of Ryan Alswede and me.
Enjoy! š
I'm prompting for how much shipping "and handling" costs can be reduced for multiple adapters...
. A 9595 will not achieve this. As soon as a GUI
comes into play, the 90MHz Pentium will go to its knees.Why? It's a DMA enabled card.
Ryan
Hear ye, Hear ye!of the very last MCA cards.
There's a new dream team on the block.
That may be you, your favorite PS/2 and your IBM 10/100 Mbps Ethernet Adapter (9-K)!
After weeks and months of reverse and forward engineering, we now have drivers for this very late manufactured, 32-bit Micro Channel 100 Mbps capable Ethernet Adapter type 9-K, code name "San Remo", that IBM released only for the RS/6000 series as one
For 30 years there were no drivers outside of AIX, IBM's proprietary Unix operating system.
Today you may start running it in Windows 95, probably also 98, and Linux 2.2!
Get your copy here:
http://www.holzapfel.biz/8F62/sanremo-win9x.zip https://github.com/holzachr/sanremo-linux
Please note that those are considered beta drivers, and may not be perfect yet.
They were tested on Windows 95 B OSR2 and Debian 2.2 on a souped-up PC 750. I would love to hear your personal feedback on a true Micro Channel system.
This was a joint effort of Ryan Alswede and me.
Enjoy! š
On Tuesday, November 21, 2023 at 11:38:07āÆAM UTC-5, Christian Holzapfel wrote:one of the very last MCA cards.
Hear ye, Hear ye!
There's a new dream team on the block.
That may be you, your favorite PS/2 and your IBM 10/100 Mbps Ethernet Adapter (9-K)!
After weeks and months of reverse and forward engineering, we now have drivers for this very late manufactured, 32-bit Micro Channel 100 Mbps capable Ethernet Adapter type 9-K, code name "San Remo", that IBM released only for the RS/6000 series as
Nice, thank you, Christian!For 30 years there were no drivers outside of AIX, IBM's proprietary Unix operating system.I bought one and will give it a try on a Reply TurboProcessor. Nice work!
Today you may start running it in Windows 95, probably also 98, and Linux 2.2!
Get your copy here:
http://www.holzapfel.biz/8F62/sanremo-win9x.zip https://github.com/holzachr/sanremo-linux
Please note that those are considered beta drivers, and may not be perfect yet.
They were tested on Windows 95 B OSR2 and Debian 2.2 on a souped-up PC 750. I would love to hear your personal feedback on a true Micro Channel system.
This was a joint effort of Ryan Alswede and me.
Enjoy! š
-Lionel
I hope it works for all of you without any headaches.favorite environments:
If you would like to benchmark it (honestly, I would like you to benchmark it!), I've created a zip file containing matching versions of the netio benchmark for Win32, Linux, OS/2 and AIX that should enable most of us testing the adapters in our
http://www.holzapfel.biz/8F62/netio132-ibm.zip
Just start one executable on a connected powerful computer with the "-s" parameter to start a server, then run the executable on the Micro Channel machine using the "-t <server-ip>" command line argument.
On Wednesday, November 29, 2023 at 2:33:49āÆPM UTC-5, Christian Holzapfel wrote:favorite environments:
I hope it works for all of you without any headaches.
If you would like to benchmark it (honestly, I would like you to benchmark it!), I've created a zip file containing matching versions of the netio benchmark for Win32, Linux, OS/2 and AIX that should enable most of us testing the adapters in our
http://www.holzapfel.biz/8F62/netio132-ibm.zip
Just start one executable on a connected powerful computer with the "-s" parameter to start a server, then run the executable on the Micro Channel machine using the "-t <server-ip>" command line argument.What are the chances of a DOS driver?
ZuluSCSI RP2040Gotek Floppy Drive 435 MCU w/ Rotary Encoder OLED
Nakamichi MJ-5.16
3C529-TP Etherlink III --------------------------------------------------------------------------------------------------
TCP server listening.
TCP connection established ...
Receiving from client, packet size 1k ... 928.40 KByte/s
Sending to client, packet size 1k ... 804.07 KByte/s
Receiving from client, packet size 2k ... 942.55 KByte/s
Sending to client, packet size 2k ... 832.55 KByte/s
Receiving from client, packet size 4k ... 873.69 KByte/s
Sending to client, packet size 4k ... 832.20 KByte/s
Receiving from client, packet size 8k ... 814.47 KByte/s
Sending to client, packet size 8k ... 844.32 KByte/s
Receiving from client, packet size 16k ... 832.46 KByte/s
Sending to client, packet size 16k ... 840.34 KByte/s
Receiving from client, packet size 32k ... 830.54 KByte/s
Sending to client, packet size 32k ... 787.97 KByte/s
Done.
10/100 Mbps Ethernet (9-K) --------------------------------------------------------------------------------------------------
TCP server listening.
TCP connection established ...
Receiving from client, packet size 1k ... 1149.31 KByte/s
Sending to client, packet size 1k ... 1410.54 KByte/s
Receiving from client, packet size 2k ... 1381.70 KByte/s
Sending to client, packet size 2k ... 1651.40 KByte/s
Receiving from client, packet size 4k ... 1904.52 KByte/s
Sending to client, packet size 4k ... 1810.20 KByte/s
Receiving from client, packet size 8k ... 1971.34 KByte/s
Sending to client, packet size 8k ... 1892.09 KByte/s
Receiving from client, packet size 16k ... 2193.67 KByte/s
Sending to client, packet size 16k ... 1944.85 KByte/s
Receiving from client, packet size 32k ... 2267.23 KByte/s
Sending to client, packet size 32k ... 1952.12 KByte/s
Done.
Gods below, that looks like the 9-K is doing FDX with the 10Mb section. lharr...@gmail.com wrote:
3C529-TP Etherlink III --------------------------------------------------------------------------------------------------
TCP server listening.
TCP connection established ...
Receiving from client, packet size 1k ... 928.40 KByte/s
Sending to client, packet size 1k ... 804.07 KByte/s
Receiving from client, packet size 2k ... 942.55 KByte/s
Sending to client, packet size 2k ... 832.55 KByte/s
Receiving from client, packet size 4k ... 873.69 KByte/s
Sending to client, packet size 4k ... 832.20 KByte/s
Receiving from client, packet size 8k ... 814.47 KByte/s
Sending to client, packet size 8k ... 844.32 KByte/s
Receiving from client, packet size 16k ... 832.46 KByte/s
Sending to client, packet size 16k ... 840.34 KByte/s
Receiving from client, packet size 32k ... 830.54 KByte/s
Sending to client, packet size 32k ... 787.97 KByte/s
Done.
10/100 Mbps Ethernet (9-K) --------------------------------------------------------------------------------------------------
TCP server listening.
TCP connection established ...
Receiving from client, packet size 1k ... 1149.31 KByte/s
Sending to client, packet size 1k ... 1410.54 KByte/s
Receiving from client, packet size 2k ... 1381.70 KByte/s
Sending to client, packet size 2k ... 1651.40 KByte/s
Receiving from client, packet size 4k ... 1904.52 KByte/s
Sending to client, packet size 4k ... 1810.20 KByte/s
Receiving from client, packet size 8k ... 1971.34 KByte/s
Sending to client, packet size 8k ... 1892.09 KByte/s
Receiving from client, packet size 16k ... 2193.67 KByte/s
Sending to client, packet size 16k ... 1944.85 KByte/s
Receiving from client, packet size 32k ... 2267.23 KByte/s
Sending to client, packet size 32k ... 1952.12 KByte/s
Done.
So my switch shows 100MB FDX, I did the test again with sysmon showing CPU usage in Windows 95 and it's 100% CPU with the 9-K. I am pretty sure I'm just maxing the CPU at this point in terms of top end speeds.
Model 9576i (Lacuna)
AMD X5 @ 133 MHz
64 MB RAM
No L2 cache:-(
Windows 95
Burst Mode Rx+Tx
Netio 1.32
Packet size 1k bytes: 1193.33 KByte/s Tx, 936.21 KByte/s Rx.
Packet size 2k bytes: 1290.28 KByte/s Tx, 1114.61 KByte/s Rx.
Packet size 4k bytes: 1389.92 KByte/s Tx, 1575.54 KByte/s Rx.
Packet size 8k bytes: 1741.82 KByte/s Tx, 1541.64 KByte/s Rx.
Packet size 16k bytes: 1969.17 KByte/s Tx, 1173.42 KByte/s Rx.
Packet size 32k bytes: 1934.02 KByte/s Tx, 1874.79 KByte/s Rx.
That the Lacuna and Reply perform so low is disappointing, but maybe there's a reason why IBM did not sell this adapter to PS/2 users - or maybe we will find a magic switch to make the card operate faster.
Here a few benchmarks from my systems:
Model 6886 (PC 750)
AMD K6-III @ 400 MHz
192 MB RAM
Windows 95
Burst Mode Rx+Tx
Netio 1.32
Packet size 1k bytes: 4751.55 KByte/s Tx, 4547.97 KByte/s Rx.
Packet size 2k bytes: 6082.19 KByte/s Tx, 4748.86 KByte/s Rx.
Packet size 4k bytes: 6772.06 KByte/s Tx, 5595.94 KByte/s Rx.
Packet size 8k bytes: 7378.91 KByte/s Tx, 5575.82 KByte/s Rx.
Packet size 16k bytes: 7996.92 KByte/s Tx, 6135.80 KByte/s Rx.
Packet size 32k bytes: 8226.20 KByte/s Tx, 6186.44 KByte/s Rx.
Model 9576i (Lacuna)
AMD X5 @ 133 MHz
64 MB RAM
No L2 cache :-(
Windows 95
Burst Mode Rx+Tx
Netio 1.32
Packet size 1k bytes: 1193.33 KByte/s Tx, 936.21 KByte/s Rx.
Packet size 2k bytes: 1290.28 KByte/s Tx, 1114.61 KByte/s Rx.
Packet size 4k bytes: 1389.92 KByte/s Tx, 1575.54 KByte/s Rx.
Packet size 8k bytes: 1741.82 KByte/s Tx, 1541.64 KByte/s Rx.
Packet size 16k bytes: 1969.17 KByte/s Tx, 1173.42 KByte/s Rx.
Packet size 32k bytes: 1934.02 KByte/s Tx, 1874.79 KByte/s Rx.
Model 7013-59H (RS/6000)
POWER2 @ 67 MHz
1,25 GB RAM
1 MB L2 cache
AIX 4.3.3 (IBM's driver)
Netio 1.32
Packet size 1k bytes: 5113.53 KByte/s Tx, 6395.88 KByte/s Rx.
Packet size 2k bytes: 6059.71 KByte/s Tx, 7318.23 KByte/s Rx.
Packet size 4k bytes: 7213.85 KByte/s Tx, 7667.44 KByte/s Rx.
Packet size 8k bytes: 7877.74 KByte/s Tx, 8501.13 KByte/s Rx.
Packet size 16k bytes: 8819.90 KByte/s Tx, 8811.09 KByte/s Rx.
Packet size 32k bytes: 8627.93 KByte/s Tx, 9067.06 KByte/s Rx.
Model 7006-42T (RS/6000)
PowerPC @ 120 MHz
192 MB RAM
0.5 MB L2 cache
AIX 4.3.3 (IBM's driver)
Netio 1.32
Packet size 1k bytes: 2558.84 KByte/s Tx, 619.03 KByte/s Rx.
Packet size 2k bytes: 2754.74 KByte/s Tx, 1297.03 KByte/s Rx.
Packet size 4k bytes: 3340.64 KByte/s Tx, 3816.94 KByte/s Rx.
Packet size 8k bytes: 4013.11 KByte/s Tx, 3763.10 KByte/s Rx.
Packet size 16k bytes: 4551.11 KByte/s Tx, 3802.62 KByte/s Rx.
Packet size 32k bytes: 4562.02 KByte/s Tx, 4275.55 KByte/s Rx.
What's interesting is the mixed performance on the RS/6000 systems. The later mid-range workstation machine with a faster CPU performs worse than the early 1992 high-performance server class system. I assume, the 7013 was built specifically for high-throughput and low-latency applications.
That the Lacuna and Reply perform so low is disappointing, but maybe there's a reason why IBM did not sell this adapter to PS/2 users - or maybe we will find a magic switch to make the card operate faster.
Am 21.11.23 um 17:38 schrieb Christian Holzapfel:
Hear ye, Hear ye!
There's a new dream team on the block.
That may be you, your favorite PS/2 and your IBM 10/100 Mbps Ethernet
Adapter (9-K)!
After weeks and months of reverse and forward engineering, we now have
drivers for this very late manufactured, 32-bit Micro Channel 100 Mbps
capable Ethernet Adapter type 9-K, code name "San Remo", that IBM
released only for the RS/6000 series as one of the very last MCA cards.
For 30 years there were no drivers outside of AIX, IBM's proprietary
Unix operating system.
Today you may start running it in Windows 95, probably also 98, and
Linux 2.2!
Get your copy here:
http://www.holzapfel.biz/8F62/sanremo-win9x.zip
https://github.com/holzachr/sanremo-linux
Please note that those are considered beta drivers, and may not be
perfect yet.
They were tested on Windows 95 B OSR2 and Debian 2.2 on a souped-up PC
750. I would love to hear your personal feedback on a true Micro
Channel system.
This was a joint effort of Ryan Alswede and me.
Enjoy! š
Cool stuff, will definitely try it out on a 9595 or server 520 and
report back. If only I had a little more time to play around with MCA ...
The problem with using a 9-K in an Intel system is the processor load.
On a 7030-3BT I have about 4.5MB throughput with a comparatively
sluggish AIXwindows. A 9595 will not achieve this. As soon as a GUI
comes into play, the 90MHz Pentium will go to its knees.
In any case, thank you for your work, which I greatly appreciate!
Wolfgang
256 MB RAM
Model 9595 (Server 95)
Pentium 90 MHz
256 MB RAM
Windows 95C
sanremo driver first release
Netio 1.32
Packet sizeĀ 1k bytes:Ā 2003.55 KByte/s Tx,Ā 2474,76 KByte/s Rx.
Packet sizeĀ 2k bytes:Ā 2842,76 KByte/s Tx,Ā 2988,59 KByte/s Rx.
Packet sizeĀ 4k bytes:Ā 3416,27 KByte/s Tx,Ā 3265,17 KByte/s Rx.
Packet sizeĀ 8k bytes:Ā 4255,07 KByte/s Tx,Ā 3328,77 KByte/s Rx.
Packet size 16k bytes:Ā 4730,52 KByte/s Tx,Ā 3286,24 KByte/s Rx.
Packet size 32k bytes:Ā 4570,87 KByte/s Tx,Ā 3137,11 KByte/s Rx.
Model 9595 (Server 95)
Pentium 90 MHz
256 MB RAM
Windows 95C
sanremo driver first release
Netio 1.32
Packet size 1k bytes: 2003.55 KByte/s Tx, 2474,76 KByte/s Rx.
Packet size 2k bytes: 2842,76 KByte/s Tx, 2988,59 KByte/s Rx.
Packet size 4k bytes: 3416,27 KByte/s Tx, 3265,17 KByte/s Rx.
Packet size 8k bytes: 4255,07 KByte/s Tx, 3328,77 KByte/s Rx.
Packet size 16k bytes: 4730,52 KByte/s Tx, 3286,24 KByte/s Rx.
Packet size 32k bytes: 4570,87 KByte/s Tx, 3137,11 KByte/s Rx.
Model 9595 (Server 95)
Pentium 90 MHz
256 MB RAM
Windows 95C
sanremo driver first release
Netio 1.32
Packet sizeĀ 1k bytes:Ā 2003.55 KByte/s Tx,Ā 2474,76 KByte/s Rx.
Packet sizeĀ 2k bytes:Ā 2842,76 KByte/s Tx,Ā 2988,59 KByte/s Rx.
Packet sizeĀ 4k bytes:Ā 3416,27 KByte/s Tx,Ā 3265,17 KByte/s Rx.
Packet sizeĀ 8k bytes:Ā 4255,07 KByte/s Tx,Ā 3328,77 KByte/s Rx.
Packet size 16k bytes:Ā 4730,52 KByte/s Tx,Ā 3286,24 KByte/s Rx.
Packet size 32k bytes:Ā 4570,87 KByte/s Tx,Ā 3137,11 KByte/s Rx.
With your driver, the 9-K is three to four times faster than the Etherstreamer MC32, which was up to now the fastest Ethernet adapter for
the IBM PS/2. The system remains responsive even if Sysinternal's
process explorer claims 100% CPU utilization.
Well done!
Will try your Linux driver with Slackware 11 and the second release of
your W95 driver as soon as possible.
Wolfgang
On Sunday, December 3, 2023 at 7:12:51āÆAM UTC-5, Christian Holzapfel wrote:
lharr...@gmail.com wrote:
What are the chances of a DOS driver?The leaked sources for the original PCnet DOS packet driver are around.
They are plain x86 Assembly, processed by
# MAKE Version 3.6
# TASM Version 3.1
# TLINK Version 5.1
Generally, the places such a driver needs modification to work with our 9-K are well known to Ryan and me and properly documented now - but I'm not that fluent in Assembly (yet).
Furthermore, the DOS driver is working in 16-bit mode only, while the 9-K ASIC and also the PCnet chip in our case need some 32 bit addressing.
So it's a little more to it, but generally doable.
Maybe in the boring, gray start of next year I could look into it.
If someone else is willing to pick that up, I'm happy to help :-)
I've been pretty decent writing code for c# and such, but not sure if I could pick this up and be useful. I'd have to start reading about it and see.
As far as the 9x driver, I have been unable to get the updated driver working at all. Even with a fresh install of Windows 95. I'll get an IP but can't ping the gateway, the reply times out. I didn't change any of the default settings of the driver... I think the buffer or whatever was set to RX + TX. This weekend has been bit busier than I expected and I have to run so.. not sure how much I can play with it more this weekend. Also... with the fresh install, the 32bit driver for my BusLogic card
Anyway, with the fresh install, performance was a tad better. I truly think the reply board is slow in general. The 486 Overdrive 100mhz and Kingston TurboChip also both score about the same as the POD83... which is 20% slower than any rando boardout there that can take these chips. I've had a few others with the Reply board get the same results. Not sure why.
TCP connection established ...
Receiving from client, packet size 1k ... 1267.69 KByte/s
Sending to client, packet size 1k ... 1425.52 KByte/s
Receiving from client, packet size 2k ... 1583.88 KByte/s
Sending to client, packet size 2k ... 1693.53 KByte/s
Receiving from client, packet size 4k ... 2123.17 KByte/s
Sending to client, packet size 4k ... 1846.58 KByte/s
Receiving from client, packet size 8k ... 2132.16 KByte/s
Sending to client, packet size 8k ... 1903.23 KByte/s
Receiving from client, packet size 16k ... 2304.99 KByte/s
Sending to client, packet size 16k ... 1941.89 KByte/s
Receiving from client, packet size 32k ... 2434.78 KByte/s
Sending to client, packet size 32k ... 1929.03 KByte/s
Would be cool to see what the ASIC parameters are on your AIX server for the fields we aren't able to infer their meanings. Maybe a project for next year when your time allows.There might be some parameters in IBM's original AIX driver that they adjusted inside the ASIC
So from the hardware point of view, the only difference is that in the 9-K case, the hardware access is tunneled through the PC 750's PCI-to-MCA bridge, and then through the 9-K's MCA-to-PCI ASIC bridge.
Wolfgang Gehl schrieb am Mittwoch, 6. Dezember 2023 um 23:48:51 UTC+1:
My guess is a timing problem in the PCI-to-MCA bridge. May I ask you for
another test run? The PC 750 supports a PCI bus clock of 50MHz. I could
imagine that the MCA bus would cope much better with this than with the
66MHz bus clock.
With a 50 MHz base clock instead of 66, the adapter tops out at ~6700 k/sec:
NETIO - Network Throughput Benchmark, Version 1.7
(C) 1997-1999 Kai Uwe Rommel
TCP/IP connection established.
1k packets: 5326 k/sec
2k packets: 6079 k/sec
4k packets: 6273 k/sec
8k packets: 6648 k/sec
16k packets: 6755 k/sec
32k packets: 6680 k/sec
I guess the PCI clock is always BaseClock/2 on my system.
Wish I had a datasheet for the PC 750 clock chip, IMI SC471...
Cool stuff, will definitely try it out on a 9595 or server 520 and
report back. If only I had a little more time to play around with MCA ...
Wolfgang Gehl schrieb am Dienstag, 16. Januar 2024 um 00:26:09 UTC+1:
Looks like I need help. Is there a solution to this or do I have to go
back to Slackware 8 (Kernel 2.2.19)?
Wolfgang
The patch and C-file won't work with a 2.4 Kernel out of the box.
I already started porting the sanremo.c to 2.4, but it's not final yet, I have no patch and corrupted my 2.4 Linux partition >.<
I can send it to you for further testing. It's not fully cleaned up, but should compile and give a connection.
Interestingly, the 2.4 Kernel seems to tackle some performance issues: It now seems to hand the network subsystem buffers straight down to the card for DMA.
Seems to only profit in one direction, and degrade in the other.
This is what I measured on an 8595 with Pentium 200, Kernel 2.2:
NETIO - Network Throughput Benchmark, Version 1.7
(C) 1997-1999 Kai Uwe Rommel
TCP/IP connection established.
1k packets: 6726 k/sec
2k packets: 8456 k/sec
4k packets: 8741 k/sec
8k packets: 8680 k/sec
16k packets: 8586 k/sec
32k packets: 7974 k/sec
NETIO - Network Throughput Benchmark, Version 1.7
(C) 1997-1999 Kai Uwe Rommel
TCP/IP connection established.
1k packets: 6196 k/sec
2k packets: 6175 k/sec
4k packets: 6237 k/sec
8k packets: 6250 k/sec
16k packets: 6240 k/sec
32k packets: 6172 k/sec
And on the same system with a Kernel 2.4:
NETIO - Network Throughput Benchmark, Version 1.7
(C) 1997-1999 Kai Uwe Rommel
TCP/IP connection established.
1k packets: 7415 k/sec
2k packets: 7485 k/sec
4k packets: 7809 k/sec
8k packets: 7793 k/sec
16k packets: 7689 k/sec
32k packets: 7199 k/sec
NETIO - Network Throughput Benchmark, Version 1.7
(C) 1997-1999 Kai Uwe Rommel
TCP/IP connection established.
1k packets: 6949 k/sec
2k packets: 6900 k/sec
4k packets: 6903 k/sec
8k packets: 6900 k/sec
16k packets: 6910 k/sec
32k packets: 6886 k/sec
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 399 |
Nodes: | 16 (2 / 14) |
Uptime: | 98:33:59 |
Calls: | 8,363 |
Calls today: | 2 |
Files: | 13,162 |
Messages: | 5,897,721 |