OS2 World Community Forum

OS/2, eCS & ArcaOS - Technical => Networking => Topic started by: Paul Smedley on January 19, 2014, 09:09:59 am

Title: e1000e driver - test updates
Post by: Paul Smedley on January 19, 2014, 09:09:59 am
Hi All,

I've done some updates to the multimac e1000e driver to update the linux kernel version it is based on.

At this time, I have three fourfive test versions available.

To test:
1) backup the existing \ibmcom\mac\e1000e.os2
2) replace with one in the test zips.

URLs for test builds:
http://smedley.id.au/tmp/e1000e-3.4.77.zip
http://smedley.id.au/tmp/e1000e-3.6.11.zip
http://smedley.id.au/tmp/e1000e-3.8.13.zip
http://smedley.id.au/tmp/e1000e-3.10.27.zip
http://smedley.id.au/tmp/e1000e-3.12.8.zip

Note these have been lightly tested on a Thinkpad T60 only.  Lightly tested basically means ensure the machine boots, gets an IP using dhcp, and can connect to a website.

YMMV.

Intent is to try and get this up to the latest kernel code and get the changes included in the multimac source code, and to learn a bit about how multimac works.

Cheers,

Paul.
Title: Re: e1000e driver - test updates
Post by: Sigurd Fastenrath on January 19, 2014, 02:28:36 pm
If not now - when else?  8)

I just donated some bucks to Paul to support his ongoing work here with OS/2 and eComstation. I am just writing this to encourage others to do the same  ::)

I will test the new Intel driver during the week.

Thanks Paul and keep going!!  ;)
Title: Re: e1000e driver - test updates
Post by: Doug Bissett on January 19, 2014, 10:14:34 pm
Quote
At this time, I have three fourfive test versions available.

Thanks Paul. I am wondering what you are basing the version numbers on? It seems that Multimac, from Mensys, was just using a sequential number. I am guessing that you are using the Linux version number (but it would be nice to know).

Testing will commence shortly...
Title: Re: e1000e driver - test updates
Post by: Dave Yeo on January 19, 2014, 10:50:08 pm
I have
Code: [Select]
Vendor 8086h Intel Corporation
 Device 104Ah 82566DM Gigabit Network Connection

Quickly testing all your builds seem to work the same as the official driver unluckily.
I have IRQ problems with the driver, under Warp V4 it only works if I disable sound and the PATA interface (dvd burner), otherwise can not bind to tcp/ip and under eCS it only seems to work if I power off the system when rebooting otherwise it receives but does not transmit.
I'll test more on eCS including moving some large files later.
Title: Re: e1000e driver - test updates
Post by: Doug Bissett on January 20, 2014, 12:11:15 am
Well, a quick test (they boot, dhcp works, and I can browse the internet) works for all of them on my Lenovo ThinkPad T510, which always worked well with the Multimac Intel driver.

Intel 82577LM Gigabit Network Connection [8086:10EA]
Code: [Select]
Vendor 8086h Intel Corporation
 Device 10EAh 82577LM Gigabit Network Connection
 Command 0107h (I/O Access, Memory Access, BusMaster, System Errors)
 Status 0010h (Has Capabilities List, Fast Timing)
 Revision 06h, Header Type 00h, Bus Latency Timer 00h
 Self test 00h (Self test not supported)
 PCI Class Network, type Ethernet
 Subsystem ID 215317AAh Unknown
 Subsystem Vendor 17AAh Lenovo
 Address 0 is a Memory Address (0-4GiB) : F2600000h
 Address 1 is a Memory Address (0-4GiB) : F2625000h
 Address 2 is an I/O Port : 1820h
 System IRQ 20, INT# A
 New Capabilities List Present:
   Power Management Capability, Version 1.1
     Does not support low power State D1 or D2
     Supports PME# signalling from mode(s) D0, D3hot, D3cold
     PME# signalling is currently disabled
     3.3v AUX Current required : 0 mA (Self powered)
     Current Power State : D0 (Device operational, no power saving)
       700 mW D0 power consume
       700 mW D0 power dissipate
       200 mW D3 power consume
       200 mW D3 power dissipate
         0 mW common logic power consume
   Message Signalled Interrupt Capability
     MSI is disabled
     MSI function can generate 64-bit addresses
   Unknown Capability (Code 13h)!!

I am assuming that e1000e-3.12.8.zip is the newest version. I left it installed, and I am doing a backup, using RSync to another machine. About 600 MB later, it seems to be okay, although the speed seems to be slow (1200 KB/s) compared to the "official" driver, which seems to go faster (6000 KB/s). That is still slow compared to what the NVIDIA Multimac driver (on the other end) does (20,000 KB/s). A gigabit network should be able to do about 30,000 KB/s. All measurements are done by IPMON. I will leave it installed, for now.

Thanks...
Title: Re: e1000e driver - test updates
Post by: Paul Smedley on January 20, 2014, 02:20:33 am
Quote
At this time, I have three fourfive test versions available.

Thanks Paul. I am wondering what you are basing the version numbers on? It seems that Multimac, from Mensys, was just using a sequential number. I am guessing that you are using the Linux version number (but it would be nice to know).

Testing will commence shortly...

Correct - version is based on the linux kernel code it came from
Title: Re: e1000e driver - test updates
Post by: Paul Smedley on January 20, 2014, 02:23:10 am
I have
Code: [Select]
Vendor 8086h Intel Corporation
 Device 104Ah 82566DM Gigabit Network Connection

Quickly testing all your builds seem to work the same as the official driver unluckily.
I have IRQ problems with the driver, under Warp V4 it only works if I disable sound and the PATA interface (dvd burner), otherwise can not bind to tcp/ip and under eCS it only seems to work if I power off the system when rebooting otherwise it receives but does not transmit.
I'll test more on eCS including moving some large files later.

By the time I got to kernel 3.12.x, I worked out I was potentially missing some updates. I need to do some more exploring, but it appears that e1000hw.c (part of the multimac source), incorporates code that was originally in a source file called netdev.c from the e1000e kernel code. Bumping the version of some of this code may help as well. No outlook yet on when I may get time to do this.

I will hopefully also have some updated to the R8169 driver soon too. I have the 3.10.x code compiling but I have no hardware I can test with.
Title: Re: e1000e driver - test updates
Post by: Doug Bissett on January 20, 2014, 07:58:18 am
Quote
I will hopefully also have some updated to the R8169 driver soon too. I have the 3.10.x code compiling but I have no hardware I can test with.

Paul. Because of the potential to disable the Realtek devices, with a defective driver, I will suggest that you start off by limiting access to the test files. It took about 6 tries for David to create a Realtek driver that would not disable a couple of my NICs. When they become disabled, a complete power off (pull the plug, and remove the main battery, if it is a laptop) is required to enable the device again (windows cannot enable it, but I have heard that Linux can). The part that gets disabled, is the cable interface (effectively like pulling the cable). Otherwise, it works normally. The first thing that an uninformed user is going to think is that the driver damaged their NIC. Fortunately, that isn't the case, but...

I know about the problem, and how to recover, if the problem occurs. I think you have my e-mail address.
Title: Re: e1000e driver - test updates
Post by: Paul Smedley on January 20, 2014, 09:23:27 am
Quote
I will hopefully also have some updated to the R8169 driver soon too. I have the 3.10.x code compiling but I have no hardware I can test with.

Paul. Because of the potential to disable the Realtek devices, with a defective driver, I will suggest that you start off by limiting access to the test files. It took about 6 tries for David to create a Realtek driver that would not disable a couple of my NICs. When they become disabled, a complete power off (pull the plug, and remove the main battery, if it is a laptop) is required to enable the device again (windows cannot enable it, but I have heard that Linux can). The part that gets disabled, is the cable interface (effectively like pulling the cable). Otherwise, it works normally. The first thing that an uninformed user is going to think is that the driver damaged their NIC. Fortunately, that isn't the case, but...

I know about the problem, and how to recover, if the problem occurs. I think you have my e-mail address.

Hi Doug, check your email for links to r8169 built with 3.10.x and 3.12.x kernel code.
Title: Re: e1000e driver - test updates
Post by: Doug Bissett on January 20, 2014, 05:19:29 pm
Quote
Hi Doug, check your email for links to r8169 built with 3.10.x and 3.12.x kernel code.

Both versions work okay. I am using the r8169-3.12.8 version to post this, so I guess it is okay to release it.

Thank you...
Title: Re: e1000e driver - test updates
Post by: Paul Smedley on January 20, 2014, 08:41:57 pm
Quote
Hi Doug, check your email for links to r8169 built with 3.10.x and 3.12.x kernel code.

Both versions work okay. I am using the r8169-3.12.8 version to post this, so I guess it is okay to release it.

Thank you...

For others:
A couple of test drops:

http://smedley.id.au/tmp/r8169-3.10.27.zip
http://smedley.id.au/tmp/r8169-3.12.8.zip

Version numbers are based on the kernel code level per e1000e drivers.
Title: Re: e1000e driver - test updates
Post by: David McKenna on January 21, 2014, 12:00:21 am
Paul,

  I am running the 3.12 versions of both the Intel and Realtek drivers with no problems... the Intel on my file server and the Realtek on my internet machine. Thanks for updating them! I'll post if any problem comes up, but they seem to perform as well as the original versions (I've copied a couple hundred GB of data back and forth with no issues).
Title: Re: e1000e driver - test updates
Post by: Paul Smedley on January 21, 2014, 02:21:42 am
Hey David,

  I am running the 3.12 versions of both the Intel and Realtek drivers with no problems... the Intel on my file server and the Realtek on my internet machine. Thanks for updating them! I'll post if any problem comes up, but they seem to perform as well as the original versions (I've copied a couple hundred GB of data back and forth with no issues).

Thanks for the feedback! Next step will be to investigate a new wired chipset - most likely atheros or broadcom based on feedback from users.

Cheers,

Paul.
Title: Re: e1000e driver - test updates
Post by: Doug Bissett on January 21, 2014, 04:28:29 am
I am currently doing an RSync copy between my main machine (Asus M3A78-EM motherboard, with quad core Phenom processor), using r8169-3.12.8, and my Lenovo ThinkPad T510, which is using e1000e-3.12.8. The speed is maxing out at 1200 KB/s (according to IPMON). This is extremely SLOW, for a 1G network. I need to do more analysis, but I think it is BOTH drivers that are SLOW.
Title: Re: e1000e driver - test updates
Post by: Doug Bissett on January 21, 2014, 06:40:00 am
I am currently doing an RSync copy between my main machine (Asus M3A78-EM motherboard, with quad core Phenom processor), using r8169-3.12.8, and my Lenovo ThinkPad T510, which is using e1000e-3.12.8. The speed is maxing out at 1200 KB/s (according to IPMON). This is extremely SLOW, for a 1G network. I need to do more analysis, but I think it is BOTH drivers that are SLOW.

Okay, this is what I found, so far:

r8169-3.12.8 runs at about the same speed as the "official" r8169-0.3.1 version does. About 7800 KB/s (IPMON), when my NVIDIA NIC is at the other end (I have seen it run at more then 20,000 KB/s). That is still way too slow, but Realtek NICs are known to be slow, on all platforms. Something needs to be fixed, but the problem seems to be unrelated to what you did.

e1000e-3.12.8 and e1000e-3.10.27, on the other hand, run at about 1200 KB/s. EXTREMELY slow. The "official" e1000e-0.2.3 version runs at about 12,000 KB/s. I then tried e1000e-3.8.13, and it is running at about 12,000 KB/s. So, there is some sort of problem that showed up in e1000e-3.10.27, that makes it run very slow. I don't have time to test e1000e-3.4.77 and e1000e-3.6.11 tonight (or tomorrow, until later in the day). I will stay with e1000e-3.8.13, until I have more time to play with this. 12,000 KB/s is still pretty slow for a 1 Gb network, but it is usable.
Title: Re: e1000e driver - test updates
Post by: David McKenna on January 22, 2014, 02:47:02 am
Doug,

  After reading your post, I decided to check the speed of my setup. My SAMBA server has an Intel NIC running the 3.12 driver, and my client has a Realtek NIC running the 3.12 driver and connecting to SAMBA shares using IBM LAN logon. The two are connected thru a Gigabit switch. The share shows up as drive 'N:' on the client. From the client, if I move a folder with ~6GB of data either way (to or from the server) using the WPS by <shift>-drag and drop, I easily get over 30000 KB/s speeds (sometimes spiking to 42000). However, unexpectedly if I use FM/2 to do it, I only get at most 15000KB/s. What do you get for speed readings if you use the WPS to just perform a move from one machine to the other?
Title: Re: e1000e driver - test updates
Post by: Doug Bissett on January 22, 2014, 04:57:48 am
Doug,

  After reading your post, I decided to check the speed of my setup. My SAMBA server has an Intel NIC running the 3.12 driver, and my client has a Realtek NIC running the 3.12 driver and connecting to SAMBA shares using IBM LAN logon. The two are connected thru a Gigabit switch. The share shows up as drive 'N:' on the client. From the client, if I move a folder with ~6GB of data either way (to or from the server) using the WPS by <shift>-drag and drop, I easily get over 30000 KB/s speeds (sometimes spiking to 42000). However, unexpectedly if I use FM/2 to do it, I only get at most 15000KB/s. What do you get for speed readings if you use the WPS to just perform a move from one machine to the other?

When I was looking at it, I was using the WPS to copy files, and I was using the IPMON widget to measure the speed (with a file big enough to stabilize the counts for a while). I see similar speeds when using RSYNC to copy files.

Do you have any parameters set for the driver? I don't.

There is a proper tool to measure speeds, but I haven't used it for a few years. AH, there it is: http://hobbes.nmsu.edu/download/pub/os2/util/network/netio126.zip (http://hobbes.nmsu.edu/download/pub/os2/util/network/netio126.zip). That should eliminate some guesswork, but the speed changes that I am seeing, are significant enough that fine details are not needed.

I just checked in here, to see if anything has changed, since my last post, before I try the other two Intel drivers.

One thing that I will try (if it will work), is to put an Intel NIC into my main machine (effectively replacing one of the Realtek NICs, which is on the motherboard), to see what difference that makes.

Interesting: I just discovered that I had a CAT 5 cable on the Intel NIC. I replaced it with a CAT 5e cable, and now it runs slower (9500 KB/s). Then, I hooked it to the switch (where the "server" is connected), with a CAT 5e cable, and it is now peaking out at about 13,000 KB/s. Still using the e1000e-3.8.13 driver.

I am not sure what CAT number the cable on the "server" is. It is only about 2 feet long, and connects to the switch.

I need to do more work.   :-\
Title: Re: e1000e driver - test updates
Post by: Doug Bissett on January 22, 2014, 05:41:05 am
More interesting: I tried e1000e-3.6.11. It works about the same as e1000e-3.8.13. Then, I tried e1000e-3.4.77, and it is running at about 13,800 KB/s.

Okay, start over. I put the "official" e1000e-0.2.3 driver back in. It seems to be a little more erratic, bouncing between 12,500 and 13,900 KB/s.

e1000e-3.12.8 is still running at about 1200 KB/s.

So, the winner is e1000e-3.4.77. Yes, it is still running at about 13,800 KB/s.

I don't think the cables will make much difference. The longest is about 10 feet, and they are all CAT 5e, except the one that just got replaced. Beside that, the first set of tests were done with the same hardware (including cables), and the second set of tests was done with a slightly different set of hardware. The results are pretty much the same.

Now, I am curious to see if the Intel NIC will work in my main machine.   :)
Title: Re: e1000e driver - test updates
Post by: Doug Bissett on January 22, 2014, 07:03:17 am
Even more interesting:

I found the main cause of slow network activity. I have played with VirtualBox in eCS, for years. The problem is caused by the TAP driver (which I had forgotten about). After removing that, I am seeing 35,000 KB/s to 40,000 KB/s with my Realtek NIC (r8169-3.12.8), and 35,000 KB/s to 45,000 KB/s with my Intel NIC (e1000e-3.4.77). I would call that a significant performance hit.   :'(

More testing to do tomorrow...

I did try the Intel NIC in my main machine, but it doesn't work. PCI.EXE can't "see" it. I don't know if that is because my motherboard is broken, or just too old to recognize the card. I know that the card works in another machine.
Title: Re: e1000e driver - test updates
Post by: Paul Smedley on January 22, 2014, 09:25:14 am
I did some testing here with 3.12.8 downloading a roughly 1gb file from my local web server with gigabit connections.

From my T60 running eCS 2.2, I saw download speeds of 15.3 MB/second using the 3.12.8 driver

With the last official driver, I saw download speeds of15.5 MB/second

From my desktop machine running Ubuntu 13.10 and a realtek nic, I saw download speeds of 18.6 MB/second on the same file.

So OS/2 driver is around 20% slower than linux on this testcase, but no difference here between the official builds and my builds.
Title: Re: e1000e driver - test updates
Post by: Doug Bissett on January 22, 2014, 09:05:51 pm
I probably should note, that all of my previous tests have been done by uploading to the server, using a ziped file that is about 350 GB.

I don't know, yet, what is going on. I removed the TAP driver, which was, obviously, making a huge difference, but today, I am seeing completely different numbers (in the 100 mbs range), for no apparent reason.

More, if I can figure this out...
Title: Re: e1000e driver - test updates
Post by: Doug Bissett on January 23, 2014, 04:28:35 am
Well, I haven't figured it out, but something is seriously broken in the Intel driver (even the "official" one). From what I can tell, sometimes it detects that it should run at 1000 mbs, and sometimes it seems to run at 100 mbs (my switch indicates the speed). I can boot to windows, and it always runs at 1000 mbs. Then, I tried adding "MODE=1000FULL", to force it to use 1000 mbs. Wrong, it then runs at 26 KB/s. Sometimes, upload will go at 30,000 KB/s, and download will go at 7,800 KB/s. Sometimes, it is the other way around. Most of the time, it runs at 7800 KB/s, in both directions.

I am obviously missing something. I am going to shut it down, and try again tomorrow.
Title: Re: e1000e driver - test updates
Post by: Dave Yeo on January 23, 2014, 05:36:40 am
Try disabling whatever you can get away with. Easiest to do it in the BIOS. The Intel driver, at least here, doesn't seem to like sharing IRQs, as in IRQA or IRQB etc.
Title: Re: e1000e driver - test updates
Post by: David McKenna on January 24, 2014, 04:30:50 am
Doug,

  Usually there are lights on the ethernet plug that indicate the speed the NIC detects it can connect to the hub/switch/router it is attached to. Is the indicated speed changing from time to time? Maybe the NIC is detecting its connection differently each time...
Title: Re: e1000e driver - test updates
Post by: Doug Bissett on January 24, 2014, 07:04:27 am
Quote
Easiest to do it in the BIOS.

There isn't much to work with in the Lenovo ThinkPad T510 BIOS.

Quote
Is the indicated speed changing from time to time? Maybe the NIC is detecting its connection differently each time

It doesn't seem to be that simple. Using the "official" e1000e 0.2.3, NETSTAT -N always shows "speed 1000000000  bits/sec" (even when connected to a 100 mbs switch, which probably means it is meaningless).  There is a green LED on the T510, that indicates that it is connected, but it doesn't indicate the speed. It looks the same if I plug it into a 100 mbs hub. However, if I plug it into my Gb switch, I can tell what speed it connects at by the LEDs on the switch. I haven't seen it show anything but 1000 mbs, except when the machine is powered off (which is normal). Right now, if I copy from the "server" (download), it is running at about 7000 KB/s. Copying to the "server" runs at about 15,000 KB/s. I see the same hardware do 60,000 KB/s, in both directions, when running windows (measured at the "server", using IPMON). The "server" is running Multimac for NVIDIA, and it keeps up with windows, in both directions. A few days ago, after I got the TAP driver out of the picture, I was seeing 45,000 KB/s in both directions, using the "official" driver, or e1000e-3.4.77, from Paul. I haven't been able to duplicate that, since then.

Using /MAXCPU=1 or /VW on the PSD line doesn't change anything.

Now, I tried RXCHAIN = "YES" in PROTOCOL.INI, download is still about 7000 KB/s but upload is bouncing from 15,000 KB/s to 43,000 KB/s.

Okay, so I got a new CAT6 cable. If anything it is slightly slower in both directions.

If I try from the "server" end, I am seeing both directions bouncing between 7,000 KB/s and 15,000 KB/s.

FWIW, the Realtek driver, in my main machine, is showing similar numbers, and IPMON, at both ends, is showing the same numbers, so I have no reason to think that it is wrong.

Enough, for now...
Title: Re: e1000e driver - test updates
Post by: Paul Smedley on January 24, 2014, 07:30:43 am
I'll try and review the NIC initialisation code tonight/this weekend and see if there are any changes I should port over from the linux init code
Title: Re: e1000e driver - test updates
Post by: Doug Bissett on January 24, 2014, 05:54:38 pm
I'll try and review the NIC initialisation code tonight/this weekend and see if there are any changes I should port over from the linux init code

I think it is more likely the interrupt handling code that might be doing it, but that is just a guess.

I have Linux Mint (Ubuntu) installed on a USB thumb drive, It claims that the e1000e version is 3.11.0.12. Copying from my "server", I am seeing about 40,000 KB/s. Copying to my "server", I am seeing about 17,000 KB/s. These numbers might be restricted because the local storage medium is USB 2.0.

So it would appear that the Linux code is probably okay. It also appears that the Multimac NVIDIA code works as it should. However, the Intel, and Realtek, drivers are showing similar speed problems, which points to something that is common between them.

Thanks for looking. Obviously, I wasn't paying much attention to the way these things were operating, although I knew that it was slower than in windows. Now that I do some serious comparison, Multimac (except for the NVIDIA version), is extremely slow. I guess I was just happy that they worked, at all.
Title: Re: e1000e driver - test updates
Post by: mike on January 26, 2014, 01:29:38 pm
Hi All,

I've done some updates to the multimac e1000e driver to update the linux kernel version it is based on.

At this time, I have three fourfive test versions available.

To test:
1) backup the existing \ibmcom\mac\e1000e.os2
2) replace with one in the test zips.

URLs for test builds:
http://smedley.id.au/tmp/e1000e-3.4.77.zip
http://smedley.id.au/tmp/e1000e-3.6.11.zip
http://smedley.id.au/tmp/e1000e-3.8.13.zip
http://smedley.id.au/tmp/e1000e-3.10.27.zip
http://smedley.id.au/tmp/e1000e-3.12.8.zip

Note these have been lightly tested on a Thinkpad T60 only.  Lightly tested basically means ensure the machine boots, gets an IP using dhcp, and can connect to a website.

YMMV.

Intent is to try and get this up to the latest kernel code and get the changes included in the multimac source code, and to learn a bit about how multimac works.

Cheers,

Paul.


hello paul,
thanks for the update on the multimac drivers! The lan adapter has the device id of 8086:153A i tried all drivers, esp. the one in e1000e-3.12.8.zip but lantran.log always reports "E1000E No supported hardware was found."

mike



Title: Re: e1000e driver - test updates
Post by: Doug Bissett on January 26, 2014, 06:25:16 pm
Quote
thanks for the update on the multimac drivers! The lan adapter has the device id of 8086:153A i tried all drivers, esp. the one in e1000e-3.12.8.zip but lantran.log always reports "E1000E No supported hardware was found."

I may be wrong, but try the E1000 driver with that device. It should be listed as "Intel(R) PRO/1000 Network Connection".
Title: Re: e1000e driver - test updates
Post by: Paul Smedley on January 26, 2014, 10:11:51 pm
thanks for the update on the multimac drivers! The lan adapter has the device id of 8086:153A i tried all drivers, esp. the one in e1000e-3.12.8.zip but lantran.log always reports "E1000E No supported hardware was found."

Looks like this is an I217-LM chipset?

The pci ID's were missing in e1000hw.c - I've added them now so it may work.

http://smedley.id.au/tmp/e1000e-3.12.8-20140127.zip

Title: Re: e1000e driver - test updates
Post by: Doug Bissett on January 27, 2014, 06:02:23 am
After a bit of discussion in the GENMAC mail list, I dug out http://hobbes.nmsu.edu/download/pub/os2/util/network/netio126.zip (http://hobbes.nmsu.edu/download/pub/os2/util/network/netio126.zip), and gave it a shot. Some surprising numbers:

To make a story short, the TCP tests all showed good numbers (near, or over 100,000 KB/s). The UDP tests choked badly, usually not even getting off the ground. I think the NVIDIA NIC is working, but Intel, and Realtek, are not doing well.
Title: Re: e1000e driver - test updates
Post by: Doug Bissett on February 18, 2014, 12:53:13 am
I finally got back to this. I updated to the new versions of Multimac, now available in the eCS betazone.

First, I used NETIO126 to test between two windows machines. The numbers for TCP were about 60% of what I see in eCS, but UDP has no problems.

Then, while testing between windows, and eCS, I started getting messages that I was out of buffers, on the NVIDIA machine (using NETIO126.EXE -t -u -s). After some investigation, I found a suggestion that I could add "/mbuf:512 /gdt:256 /mem:3600" to the DEVICE=C:\MPTN\PROTOCOL\SOCKETSK.SYS line, in CONFIG.SYS. NETSTAT -M did not really indicate a problem on any of my systems, except the NVIDIA machine, where it seems that the spare buffers were not plentiful. Anyway, I added the suggested line to all of my systems, except the NVIDIA, and I added "/mbuf:1024 /gdt:512 /mem:7000" to it. Now, there are lots of buffers, and memory usage really hasn't gone up very much. Side effects are still to be determined. NETIO126 performance has not changed however, although it appears that I am no longer running out of buffers. I think the numbers that I am using are too big, but I don't know of any reason to reduce them.

I should probably explain that the NVIDIA machine is an Asus A8N-SLI motherboard, with 3 GB of memory. I use it as a NAS device, and have RSYNC, SAMBA, WEB/2, WEASEL, and Peter M's FTP sever running. I rarely use WEB/2 or the FTP server. I am using eCS 2.1 for testing.

At the moment, I am not sure if all of the MULTIMAC drivers are broken, or if NETIO126 in eCS is broken (the NVIDIA machine does fail, just not as badly as the others). TCP seems to work fine, but UDP doesn't work very well, if at all. I see the same problem between eCS and windows, that I see between two eCS machines. I do not see the UDP problem between two windows machines.
Title: Re: e1000e driver - test updates
Post by: Martin Iturbide on February 27, 2014, 02:25:42 am
Hi.
I tried this driver: http://smedley.id.au/tmp/e1000e-3.12.8-20140127.zip
with the wired Intel I217-V (Clarkville V) network adapter.

Sadly, it does not get recognized on boot. It says that the driver could not be loaded and press enter to continue the boot.

LANTRAN.log gives me this:

Quote
IBM OS/2 LANMSGDD [05/21/04] 6.00 is loaded and operational.
IBM OS/2 TCPBEUI 6.00.0
TCPBEUI: Using a 32-bit data segment.
Installing NETWKSTA.200 Version 6.0. IBM LAN Redirector ( May 25, 2005)

IBM OS/2 NETBIOS 4.0
Adapter 0 has 123 NCBs, 96 sessions, and 6 names available to NETBIOS applications.
NETBIOS 4.0 is loaded and operational.
E1000E NDIS device driver @#Mensys BV:0.2.4#@##1## 26 Jan 2014 11:52:31     ECS8533211::::4::SVN@@Intel PRO/1000 PCIe MAC Driver
E1000E Hardware detected: Intel I217-V.
IBM LANVDD is loaded and operational.
IBM OS/2 LAN Netbind
PRO0025: An error occurred when the program tried to bind TCPIP_NIF to E1000E_NIF.
TCPBEUI: Logical adapter 0 is trying to bind to TCP/IP interface lan0.
LT00141: Errors occurred while attempting to initialize TCPBEUI.


Am I missing something?