Dean, I’ve inserted a couple of questions (in italics) for clarification so that I will know I’m following your directions correctly. Thanks, bosdad.
I will check this out and report.
Thanks.
bosdad
Thanks for noting that the device name had changed.
bosdad
*Bosdad: If it does bring up the link do I go to this next command? Or do I try this next one no matter what happens with the first command? *
Just let us know if that brinks up the link ie LEDs lit up, and confirmed with ethtool or hwinfo commands regarding link status.
*Bosdad: How to set to 1000Mbps? Change the first command from "...100 duplex..." to "...1000 duplex...?" And what if that doesn't work? Do the original command with "...100 duplex..." to get back to where we were?*
Just see if you can get it working at 100Mbps FD for the moment.
Apples and oranges; apples and oranges. Yes, exactly!
Dean, this simple revelation is why you and Malcolm and others are the list gurus. You see the obvious that we mere mortals overlook.
It never occurred to me to look at my wife’s NIC. I just assumed hers was a plug-in (add-on), but it’s on-board. So not the same hardware at all.
I will post more information following this. I have run some of your commands and will report on the results.
Apples and oranges… sheesh!
Thanks. I sincerely apologize for allowing a false assumption to perpetuate.
bosdad
Dean, in response to the command <sudo ethtool -s enp1s8 speed 100 duplex full autoneg off> the green lights on the new NIC did come on. The link was detected. Here is the output.
62: None 00.0: 10701 Ethernet
[Created at net.125]
Unique ID: I5YJ.ndpeucax6V1
Parent ID: dRHR.oxSyVMMObW1
SysFS ID: /class/net/enp1s8
SysFS Device Link: /devices/pci0000:00/0000:00:08.0/0000:01:08.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "r8169"
Driver Modules: "r8169"
Device File: enp1s8
HW Address: c4:e9:84:02:a7:bf
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #40 (Ethernet controller)
I then used the command and this was the output:
gil@DB1:~> sudo ethtool enp1s8
root's password:
Settings for enp1s8:
Supported ports: TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000033 (51)
drv probe ifdown ifup
Link detected: yes
I then looked at the configuration of the new NIC in Yast and everything appeared to be normal. But despite the green lights being illuminated I still had no internet connection through the new card.
I then tried the command but that came back as “command not found.” 
So I manually restarted the computer. But when the monitor displayed the login screen the green lights on the NIC went out – just as before. And I had no internet. The new NIC seemingly was acting exactly the same as before despite the command that had turned on the green lights (at least until the computer was restarted).
So I swapped the cable back to the on-board NIC and restarted the computer in order to get internet so I could reply here.
Some additional information just to fill out your Sunday reading (or is it already Monday in New Zealand?)
Here are the outputs of my onboard and new NIC using the hwinfo command, followed by the output of my wife’s on-board NIC.
bosdad’s computer (new NIC)
62: None 00.0: 10701 Ethernet
[Created at net.125]
Unique ID: I5YJ.ndpeucax6V1
Parent ID: dRHR.oxSyVMMObW1
SysFS ID: /class/net/enp1s8
SysFS Device Link: /devices/pci0000:00/0000:00:08.0/0000:01:08.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "r8169"
Driver Modules: "r8169"
Device File: enp1s8
HW Address: c4:e9:84:02:a7:bf
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #40 (Ethernet controller)
**On-board NIC
**
63: None 00.0: 10701 Ethernet
[Created at net.125]
Unique ID: PoaU.ndpeucax6V1
Parent ID: djmT.sxAE5GATkLA
SysFS ID: /class/net/enp0s10
SysFS Device Link: /devices/pci0000:00/0000:00:0a.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "forcedeth"
Driver Modules: "forcedeth"
Device File: enp0s10
HW Address: 00:30:67:30:c4:0c
Link detected: yes
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #38 (Ethernet controller)
bosdad’s wife’s computer
76: None 00.0: 10701 Ethernet
[Created at net.126]
Unique ID: usDW.ndpeucax6V1
Parent ID: rBUF.5rbhBgx50x4
SysFS ID: /class/net/eth0
SysFS Device Link: /devices/pci0000:00/0000:00:09.0/0000:03:00.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "r8169"
Driver Modules: "r8169"
Device File: eth0
HW Address: 90:2b:34:98:f6:eb
Permanent HW Address: 90:2b:34:98:f6:eb
Link detected: yes
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #39 (Ethernet controller)
Dean, I don’t know if any of that is of any value, but I feel as if I’m sinking in quicksand and throwing out any bits of information I can find.
I really appreciate all the time and thought everyone has put into this. I am eternally optimistic that a solution is there to be found.
bosdad
That’s a good result.
I then looked at the configuration of the new NIC in Yast and everything appeared to be normal. But despite the green lights being illuminated I still had no internet connection through the new card.
I then tried the command but that came back as “command not found.”
My bad. That command should have been
sudo systemctl restart network
You may need to configure the card using YaST > System > Network Settings > Overview as described previously. The restart the network.service and see if the internet connection comes up.
Some additional information just to fill out your Sunday reading (or is it already Monday in New Zealand?)
Yes Monday here 
Dean, sadly no luck. After the first two commands the green lights were illuminated on the new NIC. I checked the NIC configuration and as best I can tell it’s correct. Except for identity of the card it appears to be the same as for the on-board card.
But then as soon as I pressed “enter” with <sudo systemctl restart network> in the command line the green lights went out, there was no output reported in the konsole, and the computer did nothing (at least nothing obvious anyway).
No internet service.
I manually restarted the computer but the green lights did not come on. NIC was as before – no lights; no signal; no internet.
So I plugged back into the onboard card and restarted the computer (to restore internet service) and report this latest news to you.
Thanks.
bosdad
Time to throw it in the bin and buy a NIC that works I think… >:)
Hi
Do you have a PCIe slot?
I have a dual port one, plus the on-board NIC and all use the r8169 driver without issues.
06:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller [10ec:8168]
Kernel driver in use: r8169
Kernel modules: r8169
07:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller [10ec:8168]
Kernel driver in use: r8169
Kernel modules: r8169
08:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [10ec:8136] (rev 05)
Subsystem: Hewlett-Packard Company Pavilion p6774 [103c:2ab1]
Kernel driver in use: r8169
Kernel modules: r8169
This is on openSUSE Leap 42.1 though.
I do wonder since it is 13.2 that it may really need the r8168 kernel module…
I note the chipsets are different than the OP’s… not sure if that makes a difference here though.
I was wondering if worth a shot to try using a later kernel from
http://download.opensuse.org/repositories/Kernel:/stable/standard/
Dean, in order to stay on SuSE 13.2 I agree. There is just a gremlin in the works here that refuses to reveal itself.
But I refer back to something I asked several posts back about upgrading to 42.2. I wrote then:
*
3) I have been very reluctant to upgrade from 13.2 as I am so comfortable using it and really don’t want to go to Plasma. But if I really do need to upgrade to Leap in order to get this NIC to process the internet speed I’m paying for can I upgrade to 42.2 without disturbing all of my working files on the computer? For example, I use Claws-Mail. Will all of my mail still be in the same place and time-stamped the same if I do an upgrade rather than a clean install of the operating system and then copying back all of my files from a backup drive?
If I can do a really simple upgrade to 42.2 without having to jump through a lot of hoops to find and restore my working files then maybe that’s the way to go rather than trying to get the NIC to work with 13.2, or having someone write a special driver which would only be good for so long as eventually I will have to upgrade to Leap.*
So after backing up my home directory to an external hard drive, can I put a 42.2 installation disk into the drive and tell it to “upgrade?” Will it then just replace 13.2 with the 42.2 operating system in the same three partitions (/ home and swap) and will 42.2 then seamlessly integrate with my home directory still left on the computer? (I suspect that the home directory will contain a bunch of 13.2 links that may not play nice if I just “upgrade” to 42.2, but maybe I’m imagining a problem that won’t happen?)
Or should I do a clean install of 42.2 – formatting the entire drive, repartitioning for 42.2, and then copying back my home directory’s working files (documents, claws-mail, photos, etc.)?
I really think the best solution is to get off 13.2 and onto Leap 42.2. I’m just looking for the easiest way to be able to preserve my working files, if possible without having to restore from an external hard drive since their locations in 42.2 may not be the same as in 13.2.
Thank you.
bosdad
It’s definitely driver related - there are numerous threads/bug reports reporting similar behaviour (with link auto negotiation). What’s not clear to me is if it was ever resolved or not.
But I refer back to something I asked several posts back about upgrading to 42.2. I wrote then:
- I have been very reluctant to upgrade from 13.2 as I am so comfortable using it and really don’t want to go to Plasma. But if I really do need to upgrade to Leap in order to get this NIC to process the internet speed I’m paying for can I upgrade to 42.2 without disturbing all of my working files on the computer? For example, I use Claws-Mail. Will all of my mail still be in the same place and time-stamped the same if I do an upgrade rather than a clean install of the operating system and then copying back all of my files from a backup drive?
I did answer briefly in post #14. It’s always a good idea to back up any important data first. (The email time stamps are in the emails itself so they should be preserved, as with any other emaill client.)
If I can do a really simple upgrade to 42.2 without having to jump through a lot of hoops to find and restore my working files then maybe that’s the way to go rather than trying to get the NIC to work with 13.2, or having someone write a special driver which would only be good for so long as eventually I will have to upgrade to Leap.
As I mentioned before that is not a realistic option. It’s a specialised craft, and bug reports are what would be required to get it fixed (by people already involved with the driver development). It may already be fixed in later kernels.
Or should I do a clean install of 42.2 – formatting the entire drive, repartitioning for 42.2, and then copying back my home directory’s working files (documents, claws-mail, photos, etc.)?
I really think the best solution is to get off 13.2 and onto Leap 42.2. I’m just looking for the easiest way to be able to preserve my working files, if possible without having to restore from an external hard drive since their locations in 42.2 may not be the same as in 13.2.
It’s your choice to make (clean install vs upgrade). I recently opted for an upgrade (13.2 to Leap 42.2) on a laptop that went without a hitch. I did it by updating the OSS and Non-OSS repos appropriately, disabling all other third-party repos then ‘zypper dup’ as outlined here
https://en.opensuse.org/SDB:System_upgrade
An example of upgrading to Leap 42.1 from 13.2 (but the same applies for 13.2—>42.2)
http://www.2daygeek.com/upgrade-opensuse-from-13-2-to-opensuse-leap-42-1/#
I recommend trying a Live distro first. Get that from GeckoLinux
http://geckolinux.github.io/#download
If that works you can proceed with upgrading whether by clean install or upgrading insitu.
Ah…deep sigh.:\ Dean, I think you are right.
Monday no success. Today no success. You would think the following simple steps should cause the NIC to work:
- power down and unplug the CAT5 from the onboard NIC
- insert the new NIC
- boot to setup and disable the onboard NIC in the BIOS
- save changes and the system restarts
- connect the CAT5 cable to the new NIC as the system is restarting
- sign in to the desktop, wait to see if the Network Manager detects and configures the new NIC as the system default “wired connection.”
Well, unfortunately the green lights still don’t illuminate when following these simple steps, and while a card is detected in the slot the Network Manager won’t configure it.
I hate to leave things hanging unresolved but I think I am going to put this “on hold” for now – until upgrading my system to Leap – lest I drag you folks ever deeper down this hole into Alice’s Wonderland.
Thanks very much to you, Dean, and to Malcolm for the time and effort, and for the profound wisdom you’ve shared on this challenge that seems to have no happy solution. As you mentioned in another post others have experienced the same problem but there appears to be no documented fix.
So I’ll be back when I’m running Leap on this pooter and we’ll see what happens.
bosdad
Just to clarify - It’s not configurable because no link is detected due to a driver issue with this chipset. There should be no need to disable the onboard NIC either. Linux (or any other OS for that matter) can cope with multiple ethernet devices concurrently.
Thanks very much to you, Dean, and to Malcolm for the time and effort, and for the profound wisdom you’ve shared on this challenge that seems to have no happy solution. As you mentioned in another post others have experienced the same problem but there appears to be no documented fix.
So I’ll be back when I’m running Leap on this pooter and we’ll see what happens.
Happy to have walked with you on this, unfortunately with no resolution. Hopefully, resolved when you try a newer kernel.