Centos 7 Can't see network device [SOLVED]

Issues related to configuring your network
rexorbrave
Posts: 10
Joined: 2019/04/11 08:46:27

Centos 7 Can't see network device [SOLVED]

Post by rexorbrave » 2019/04/18 18:44:15

Hi there,

So I was running an outdated version of centos 7 on my device and therefore decided to update to the newest version. However, for the other version my network device worked fine, but now it doesn't anymore (it doesn't even show up).
I tried installing the kmod-forcedeth package (which was successful, but did not resolve my issue)

Code: Select all

nmcli c
also gives me nothing...

I have been on this for over an hour, really can't figure out what the issue is.
Last edited by rexorbrave on 2019/04/20 11:00:37, edited 1 time in total.

aks
Posts: 2798
Joined: 2014/09/20 11:22:14

Re: Centos 7 Can't see network device

Post by aks » 2019/04/18 19:02:26

Assuming you are using the nvidia NIC (aka forcedeth). That was depreciated by RH quite some time ago (see https://bugs.centos.org/view.php?id=7359). I think elrepo has the module for it (see: http://elrepo.org/tiki/kmod-forcedeth).

rexorbrave
Posts: 10
Joined: 2019/04/11 08:46:27

Re: Centos 7 Can't see network device

Post by rexorbrave » 2019/04/18 19:11:40

The kmod-forcedeth was obtained from ELrepo already unfortunately.
I also tried the e100 one now, also without results. The difficulty is that the system is quite a dated one and since I cannot get my adapter to display I am unsure which one it is.

Some research on the system led me to believe that it is a VIA Fast Ethernet Adapter.
I have not been able to find the proper drivers for this I assume, since I have not gotten it to work yet...
They must be somewhere, since the last version of centos I used worked fine (If only I didn't need this one I would just go back to the old one)

Any clues?

Edit: I have since also tried to install the kernel using the rpm package from the centos website, this unfortunately let to no results at all.
Is there a way to just install all the drivers from the Centos 6.1 release which I was running before on which I had no issues?
Im so annoyed by this.

aks
Posts: 2798
Joined: 2014/09/20 11:22:14

Re: Centos 7 Can't see network device

Post by aks » 2019/04/18 19:52:47

There are many different cards that may call themselves "VIA Fast Ethernet Adapter" (i.e.: "compatible" or "clones").

Guessing at what hardware you actually have is a hiding to nowhere, there's just to many variations now.

Assuming the device is PCI connected, you could use lspci -vvv to get a better clue.

Also if it is PCI connected, you can get the ("globally") unique PCI device id by lspci -n, combine with -vv for textual information.

An example from a machine I'm using is:
00:00.0 0600: 8086:0c00 (rev 06)
Subsystem: 1043:8534
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
Latency: 0
Capabilities: [e0] Vendor Specific Information: Len=0c <?>
Kernel driver in use: hsw_uncore

That 8086:0c00 is important. 8086 is Intel (surprise!) and the 0c00 is the device id. Googling that says it's an "Intel 4th Gen DRAM controller. Also the subsystem id is important as it'll tell you more info beyond the "Intel 4th Gen DRAM controller" - i.e.: more specific information.

aks
Posts: 2798
Joined: 2014/09/20 11:22:14

Re: Centos 7 Can't see network device

Post by aks » 2019/04/18 19:53:04

You need the driver!

rexorbrave
Posts: 10
Joined: 2019/04/11 08:46:27

Re: Centos 7 Can't see network device

Post by rexorbrave » 2019/04/18 20:31:26

When trying to use the lspci -vvv command it says that this command is not available.
Any other commands I can try? Otherwise im just going to install the old version only to check my network adapter...

Thanks for the support so far :)

Edit:
Update --> Have now installed centos 6.10 on the system to check the network card.
It was a Quallcom Atheros AR2413/AR2414 - AT5005G(S) and should be covered by the kmod-ath5k...rpm from ELRepo (I assume).
[Retrieved it from: http://mirror.rc.usf.edu/compute_lock/e ... 6_64/RPMS/ ]

Tried installing the ELRepo driver, but unfortunately without succes, gave me the following errors:

Code: Select all

Failed dependencies: kernel(__ieee80211_get_channel) = ... is needed by ...
Failed dependencies: kernel(freq_reg_info) = ... is needed by ...
Failed dependencies: kernel(whipy_apply_custom_regulatory) = ... is needed by ...
So I tried installing the kernel for Centos 7 using rpm [Retrieved from: https://rpmfind.net/linux/RPM/centos/7. ... 86_64.html ]

Installed flawlessly, but afterwards when trying to install the driver, still gives me the same error...

Am I overlooking something?

Edit2:
Also tried installing the ELRepo kernel manually [Retrieved from: https://centos.pkgs.org/7/elrepo-x86_64 ... h.rpm.html ]
It installed without any issues, but unfortunately my kmod-ath5k still does not

--> Distro I am running is too new kmod-ath5k no longer supported. Trying to install centos 7.3 now, but can't find .iso

rexorbrave
Posts: 10
Joined: 2019/04/11 08:46:27

Re: Centos 7 Can't see network device

Post by rexorbrave » 2019/04/19 11:00:54

Im so F*** done.

So I reinstalled the Centos 7 version .3 this time 1611.
I got the same kmod-ath5k driver from ELRepo. kmod-ath5k-0.0-10.el7.elrepo.x86_64.rpm to be precise since kmod-ath5k-0.0-3.el7.elrepo.x86_64.rpm would not install.
It successfully installed the driver.
- I reboot
- I use nmcli --> Nothing
- I try look in the /etc/sysconfig/network-scripts/ dir --> nothing
- try to ping google.com --> nothing
- lspci does give the network adapter, but thats all, did not get any further here
- ip addr ls --> gives me lo and wlp5s1 --> There is no way to get wlp5s1 to turn on whatshowever

Im seriously running out of options here. Please if someone happens to know what the problem is, I am beyond despair

aks
Posts: 2798
Joined: 2014/09/20 11:22:14

Re: Centos 7 Can't see network device

Post by aks » 2019/04/19 17:28:45

Im seriously running out of options here. Please if someone happens to know what the problem is, I am beyond despair
Tell us what the hardware is, then we can help. What? It's now a wireless.

I'm done.

rexorbrave
Posts: 10
Joined: 2019/04/11 08:46:27

Re: Centos 7 Can't see network device

Post by rexorbrave » 2019/04/20 08:17:25

It is not supposed to be a wireless.
Ok so, its a laptop (Amilo Li 1705) therefore it has both cable and wireless in it. It is a pretty old one, I will create a list of the hardware.

Looks like I accidently installed the drivers for the wrong controller (thanks for pointing out), but my actual ethernet controller seems to be a VIA VT6102/VT6103 [Rhine-II]

And I am running Centos 7 build 1611 (3.10.0-514.e17.x86-64)

lspci output (Also included in the attachment):

Code: Select all

00:00.0 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
	Subsystem: Fujitsu Technology Solutions Device 10f7
	Flags: medium devsel
	Memory at c0000000 (32-bit, prefetchable) [disabled] [size=128M]
	Capabilities: [80] AGP version 3.5
	Capabilities: [50] Power Management version 2
	Kernel driver in use: agpgart-via

00:00.1 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
	Subsystem: Fujitsu Technology Solutions Device 10f7
	Flags: bus master, medium devsel, latency 0

00:00.2 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
	Subsystem: Fujitsu Technology Solutions Device 10f7
	Flags: bus master, medium devsel, latency 0

00:00.3 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
	Subsystem: Fujitsu Technology Solutions Device 10f7
	Flags: bus master, medium devsel, latency 0

00:00.4 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
	Subsystem: Fujitsu Technology Solutions Device 10f7
	Flags: bus master, medium devsel, latency 0

00:00.5 PIC: VIA Technologies, Inc. CN896/VN896/P4M900 I/O APIC Interrupt Controller (prog-if 20 [IO(X)-APIC])
	Subsystem: Fujitsu Technology Solutions Device 10f7
	Flags: bus master, fast devsel, latency 0

00:00.6 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Security Device
	Subsystem: Fujitsu Technology Solutions Device 10f7
	Flags: bus master, fast devsel, latency 0

00:00.7 Host bridge: VIA Technologies, Inc. CN896/VN896/P4M900 Host Bridge
	Flags: bus master, medium devsel, latency 0

00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge (prog-if 00 [Normal decode])
	Flags: bus master, 66MHz, medium devsel, latency 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	Memory behind bridge: c8000000-c8ffffff
	Prefetchable memory behind bridge: a0000000-bfffffff
	Capabilities: [70] Power Management version 2
	Kernel modules: shpchp

00:02.0 PCI bridge: VIA Technologies, Inc. CN896/VN896/P4M900 PCI to PCI Bridge Controller (rev 80) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 24
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	I/O behind bridge: 00001000-00001fff
	Memory behind bridge: 80000000-801fffff
	Prefetchable memory behind bridge: 0000000080200000-00000000803fffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [68] Power Management version 2
	Capabilities: [70] MSI: Enable- Count=1/1 Maskable+ 64bit+
	Capabilities: [88] HyperTransport: MSI Mapping Enable- Fixed+
	Capabilities: [98] Subsystem: VIA Technologies, Inc. Device c323
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel
	Capabilities: [180] Root Complex Link
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:03.0 PCI bridge: VIA Technologies, Inc. CN896/VN896/P4M900 PCI to PCI Bridge Controller (rev 80) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 25
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
	I/O behind bridge: 00007000-00007fff
	Memory behind bridge: c9000000-c90fffff
	Prefetchable memory behind bridge: 0000000080400000-00000000805fffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [68] Power Management version 2
	Capabilities: [70] MSI: Enable- Count=1/1 Maskable+ 64bit+
	Capabilities: [88] HyperTransport: MSI Mapping Enable- Fixed+
	Capabilities: [98] Subsystem: VIA Technologies, Inc. Device c323
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel
	Capabilities: [180] Root Complex Link
	Kernel driver in use: pcieport
	Kernel modules: shpchp

00:0f.0 IDE interface: VIA Technologies, Inc. VT8237A SATA 2-Port Controller (rev 80) (prog-if 8f [Master SecP SecO PriP PriO])
	Subsystem: Fujitsu Technology Solutions Device 10f7
	Flags: bus master, medium devsel, latency 64, IRQ 21
	I/O ports at 4c70 [size=8]
	I/O ports at 4c64 [size=4]
	I/O ports at 4c68 [size=8]
	I/O ports at 4c60 [size=4]
	I/O ports at 4c40 [size=16]
	I/O ports at 4400 [size=256]
	Capabilities: [c0] Power Management version 2
	Kernel driver in use: sata_via
	Kernel modules: sata_via, pata_acpi, ata_generic

00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07) (prog-if 8a [Master SecP PriP])
	Subsystem: Fujitsu Technology Solutions Device 10f7
	Flags: bus master, medium devsel, latency 64
	[virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
	[virtual] Memory at 000003f0 (type 3, non-prefetchable)
	[virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
	[virtual] Memory at 00000370 (type 3, non-prefetchable)
	I/O ports at 4c50 [size=16]
	Capabilities: [c0] Power Management version 2
	Kernel driver in use: pata_via
	Kernel modules: pata_via, pata_acpi, ata_generic

00:10.0 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev a0) (prog-if 00 [UHCI])
	Subsystem: Fujitsu Technology Solutions Device 10f7
	Flags: bus master, medium devsel, latency 64, IRQ 20
	I/O ports at 4c00 [size=32]
	Capabilities: [80] Power Management version 2
	Kernel driver in use: uhci_hcd

00:10.1 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev a0) (prog-if 00 [UHCI])
	Subsystem: Fujitsu Technology Solutions Device 10f7
	Flags: bus master, medium devsel, latency 64, IRQ 22
	I/O ports at 4c20 [size=32]
	Capabilities: [80] Power Management version 2
	Kernel driver in use: uhci_hcd

00:10.4 USB controller: VIA Technologies, Inc. USB 2.0 (rev 86) (prog-if 20 [EHCI])
	Subsystem: Fujitsu Technology Solutions Device 10f7
	Flags: bus master, medium devsel, latency 64, IRQ 21
	Memory at c9400000 (32-bit, non-prefetchable) [size=256]
	Capabilities: [80] Power Management version 2
	Kernel driver in use: ehci-pci

00:11.0 ISA bridge: VIA Technologies, Inc. VT8237A PCI to ISA Bridge
	Subsystem: VIA Technologies, Inc. VT8237A PCI to ISA Bridge
	Flags: medium devsel
	Capabilities: [c0] Power Management version 2
	Kernel modules: i2c_viapro

00:11.7 Host bridge: VIA Technologies, Inc. VT8237/8251 Ultra VLINK Controller
	Subsystem: VIA Technologies, Inc. Device 337e
	Flags: medium devsel
	Capabilities: [58] HyperTransport: Interrupt Discovery and Configuration

00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102/VT6103 [Rhine-II] (rev 7c)
	Subsystem: Fujitsu Technology Solutions Device 10f7
	Flags: bus master, medium devsel, latency 24, IRQ 9
	I/O ports at 4800 [size=256]
	Memory at c9400400 (32-bit, non-prefetchable) [size=256]
	Capabilities: [40] Power Management version 2

00:13.0 PCI bridge: VIA Technologies, Inc. VT8237A Host Bridge (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
	Memory behind bridge: c9100000-c91fffff
	Capabilities: [60] HyperTransport: MSI Mapping Enable- Fixed+
	Capabilities: [70] Subsystem: VIA Technologies, Inc. VT8237A Host Bridge
	Kernel modules: shpchp

00:13.1 PCI bridge: VIA Technologies, Inc. VT8237A PCI to PCI Bridge (prog-if 01 [Subtractive decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
	Memory behind bridge: 80600000-806fffff
	Capabilities: [60] HyperTransport: MSI Mapping Enable- Fixed+
	Capabilities: [70] Subsystem: VIA Technologies, Inc. VT8237A PCI to PCI Bridge

01:00.0 VGA compatible controller: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] (rev 01) (prog-if 00 [VGA controller])
	Subsystem: Fujitsu Technology Solutions Device 10f7
	Flags: bus master, 66MHz, medium devsel, latency 16, IRQ 9
	Memory at a0000000 (32-bit, prefetchable) [size=512M]
	Memory at c8000000 (32-bit, non-prefetchable) [size=16M]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [60] Power Management version 2
	Capabilities: [70] AGP version 2.0

04:01.0 Audio device: VIA Technologies, Inc. VT8237A/VT8251 HDA Controller (rev 10)
	Subsystem: Fujitsu Technology Solutions Device 10f7
	Flags: bus master, fast devsel, latency 0, IRQ 17
	Memory at c9100000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 2
	Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
	Capabilities: [100] Virtual Channel
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

05:01.0 Ethernet controller: Qualcomm Atheros AR2413/AR2414 Wireless Network Adapter [AR5005G(S) 802.11bg] (rev 01)
	Subsystem: Qualcomm Atheros Compex Wireless 802.11 b/g  MiniPCI Adapter, Rev A1 [WLM54G]
	Flags: bus master, medium devsel, latency 80, IRQ 10
	Memory at 80600000 (32-bit, non-prefetchable) [size=64K]
	Capabilities: [44] Power Management version 2
Thanks for sticking with me

rexorbrave
Posts: 10
Joined: 2019/04/11 08:46:27

Re: Centos 7 Can't see network device

Post by rexorbrave » 2019/04/20 10:58:14

I have found the solution thank god.
For anyone with the same problem, here is what I did (this is the only way I found to work on an offline machine since you need all dependencies)
  1. Use the lspci command to get the information on the hardware you have (I exported it to a file and place this on a usb so I could view it on a different pc)
  2. Install the exact same Centos version on a different computer on a virtual machine
  3. Connect this VM to the internet and add the ELRepo repository (see "code 1" for the required code)
  4. Install the yum plugin downloadonly (see "code 2")
  5. Now find the kmod package required for your network card (This can most often be found by googling "youradaptername centos 7 kmod")
  6. Download it to a directory instead of installing it (code 3)
  7. Move the directory to a USB device (code 4)
  8. Insert the USB into the device and do as explained in code 5
Code 1:

Code: Select all

sudo rpm --import https://www.elrepo.org/RPM-GPG-KEY-elrepo.org
sudo rpm -Uvh http://www.elrepo.org/elrepo-release-7.0-2.el7.elrepo.noarch.rpm
Code 2:

Code: Select all

yum install -y yum-plugin-downloadonly
Code 3:

Code: Select all

yum install -y --downloadonly --downloaddir=/root/package/ kmod-you-need-here
Code 4:

Code: Select all

mkdir -p media/USB #creating USB directory to mount usb to
		# Now connect a usb device (it will show sdb/sda/sdc replace the one you have in the next line)
mount -t vfat /dev/sdb1 /media/USB
mv /root/package /media/USB/package
umount /media/USB
Code 5:

Code: Select all

mkdir -p media/USB #creating USB directory to mount usb to
		# Now connect the usb device (it will show sdb/sda/sdc replace the one you have in the next line)
mount -t vfat /dev/sdb1 /media/USB
mv /media/USB/package /package
sed -i 's/enabled=1/enabled=0/' '/etc/yum/pluginconf.d/fastestmirror.conf'
cd /package/
yum install -y --disablerepo=\* *				 # Will install the kmod and dependencies
sed -i 's/enabled=0/enabled=1/' '/etc/yum/pluginconf.d/fastestmirror.conf'
reboot 			# A new boot kernel will show up, boot into this one (This is the default setting)

Post Reply