OS/2, eCS & ArcaOS - Technical > Networking

e1000e driver - test updates

<< < (2/7) > >>

Paul Smedley:

--- Quote from: Doug Bissett on January 19, 2014, 10:14:34 pm ---
--- Quote ---At this time, I have three fourfive test versions available.
--- End quote ---

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...

--- End quote ---

Correct - version is based on the linux kernel code it came from

Paul Smedley:

--- Quote from: Dave Yeo on January 19, 2014, 10:50:08 pm ---I have

--- Code: --- Vendor 8086h Intel Corporation
 Device 104Ah 82566DM Gigabit Network Connection

--- End code ---

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.

--- End quote ---

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.

Doug Bissett:

--- 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.
--- End quote ---

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.

Paul Smedley:

--- Quote from: 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.
--- End quote ---

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.

--- End quote ---

Hi Doug, check your email for links to r8169 built with 3.10.x and 3.12.x kernel code.

Doug Bissett:

--- Quote ---Hi Doug, check your email for links to r8169 built with 3.10.x and 3.12.x kernel code.
--- End quote ---

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...

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version