The problem with installing drivers for network cards ClearOS 7

Offline

ClearOS Feature Request

The problem with installing drivers for network cards ClearOS 7

Resolved

0 votes

Good afternoon.
The problem is that when you install ClearOS 7 OS sees only 1 of 3 NICs. as if nothing was thinking installed or gather after installing the OS but as it turned nenayti source, and there are RPM package from the repository modules ELrepo kmod-forsedeth and kmod-via-rnine, but fall out during installation error.

[root@serv ~]# uname -a

Linux serv.hdd-host.ru 3.10.0-229.4.2.v7.x86_64 #1 SMP Tue May 26 11:57:37 MDT 2015 x86_64 x86_64 x86_64 GNU/Linux

[root@serv ~]#

[root@serv ~]# lspci -nn | grep -i net

00:08.0 Bridge [0680]: NVIDIA Corporation MCP55 Ethernet [10de:0373] (rev a3)

01:07.0 Ethernet controller [0200]: D-Link System Inc DGE-528T Gigabit Ethernet Adapter [1186:4300] (rev 10)

01:08.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6105/VT6106S [Rhine-III] [1106:3106] (rev 8b)

[root@serv ~]#

[root@serv ~]# dmesg |grep net

[    0.005357] Initializing cgroup subsys net_cls

[    0.630833] audit: initializing netlink socket (disabled)

[    0.661882] SELinux:  Registering netfilter hooks

[    0.746958] drop_monitor: Initializing network drop monitor service

[    0.747092] Initializing XFRM netlink socket

[    1.159469] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded

[    1.159873] r8169 0000:01:07.0 (unregistered net_device): not PCI Express

[    1.207091] systemd-udevd[215]: renamed network interface eth0 to enp1s7

[    3.517554] SELinux:  Unregistering netfilter hooks

[root@serv ~]#

[root@serv ~]# yum install kmod-forcedeth

Загружены модули: clearcenter-marketplace, fastestmirror

ClearCenter Marketplace: fetching repositories...

Loading mirror speeds from cached hostfile

 * clearos: ftp.nluug.nl

 * clearos-addons: ftp.nluug.nl

 * clearos-centos: mirror.mirohost.net

 * clearos-centos-extras: mirror-pl.kielcetechnologypark.net

 * clearos-centos-fasttrack: mirror.mirohost.net

 * clearos-centos-updates: mirror.mirohost.net

 * clearos-extras: ftp.nluug.nl

 * clearos-updates: ftp.nluug.nl

 * clearos-updates-testing: ftp.nluug.nl

 * elrepo: ftp.ines.lug.ro

 * private-clearcenter-dyndns: download3.clearsdn.com:80

 * private-clearcenter-plex: download4.clearsdn.com:80

Разрешение зависимостей

--> Проверка сценария

---> Пакет kmod-forcedeth.x86_64 0:0.64-1.el7.elrepo помечен для установки

--> Обработка зависимостей: kernel(unregister_netdev) = 0x7eb952e6 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(skb_tstamp_tx) = 0x22095d00 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(skb_put) = 0x2ac95217 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(skb_clone_tx_timestamp) = 0x83433c92 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(register_netdev) = 0xd7efe2ef пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(netif_napi_add) = 0x648f1a22 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(netif_device_detach) = 0x2fa56500 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(netif_device_attach) = 0x423058c9 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(netif_carrier_on) = 0xe6d7097b пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(netif_carrier_off) = 0x3eff7be7 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(netdev_warn) = 0x2931cd0f пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(netdev_info) = 0x262e1c2b пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(napi_gro_receive) = 0xae250af1 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(napi_complete) = 0x75be4df3 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(kfree_skb) = 0x195c9f2c пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(free_netdev) = 0x708b5f0c пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(ethtool_op_get_ts_info) = 0x49c91259 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(ethtool_op_get_link) = 0xd58bf9d8 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(eth_validate_addr) = 0xdec0caf5 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(eth_type_trans) = 0xad480ea0 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(dev_kfree_skb_any) = 0x4396e9a3 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(dev_err) = 0x0d795224 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(consume_skb) = 0x95baac39 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(alloc_etherdev_mqs) = 0x906ac89f пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(_dev_info) = 0x4cce8b07 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(__netif_schedule) = 0xc4bff15e пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(__netdev_alloc_skb) = 0x2475ff29 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(__napi_schedule) = 0xd17f4c5b пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(__dynamic_netdev_dbg) = 0xd8836e80 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Обработка зависимостей: kernel(__dynamic_dev_dbg) = 0xc140ad72 пакета: kmod-forcedeth-0.64-1.el7.elrepo.x86_64

--> Проверка зависимостей окончена

Ошибка: Пакет: kmod-forcedeth-0.64-1.el7.elrepo.x86_64 (elrepo)

            Необходимо: kernel(skb_tstamp_tx) = 0x22095d00

            Установлено: kernel-3.10.0-123.13.2.v7.x86_64 (@anaconda/7.0beta1)

                kernel(skb_tstamp_tx) = 0x2cb8d918

            Установлено: kernel-3.10.0-229.4.2.v7.x86_64 (@clearos-updates-testing)

                kernel(skb_tstamp_tx) = 0x3f4798da

            Установлено: kernel-debug-3.10.0-229.4.2.v7.x86_64 (@clearos-updates-testing)

                kernel(skb_tstamp_tx) = 0x06d00384

            Доступно: kernel-debug-3.10.0-123.13.2.v7.x86_64 (clearos)

                kernel(skb_tstamp_tx) = 0xab42c6a1

Ошибка: Пакет: kmod-forcedeth-0.64-1.el7.elrepo.x86_64 (elrepo)

            Необходимо: kernel(unregister_netdev) = 0x7eb952e6

            Установлено: kernel-3.10.0-123.13.2.v7.x86_64 (@anaconda/7.0beta1)

                kernel(unregister_netdev) = 0xb192aa82

            Установлено: kernel-3.10.0-229.4.2.v7.x86_64 (@clearos-updates-testing)

                kernel(unregister_netdev) = 0xee4f6bdb

            Установлено: kernel-debug-3.10.0-229.4.2.v7.x86_64 (@clearos-updates-testing)

                kernel(unregister_netdev) = 0xaaab737f

            Доступно: kernel-debug-3.10.0-123.13.2.v7.x86_64 (clearos)

                kernel(unregister_netdev) = 0x122ca9b6

Ошибка: Пакет: kmod-forcedeth-0.64-1.el7.elrepo.x86_64 (elrepo)

            Необходимо: kernel(__dynamic_netdev_dbg) = 0xd8836e80

            Установлено: kernel-3.10.0-123.13.2.v7.x86_64 (@anaconda/7.0beta1)

                kernel(__dynamic_netdev_dbg) = 0xd4013e17

            Установлено: kernel-3.10.0-229.4.2.v7.x86_64 (@clearos-updates-testing)

                kernel(__dynamic_netdev_dbg) = 0xfa0c349b

            Установлено: kernel-debug-3.10.0-229.4.2.v7.x86_64 (@clearos-updates-testing)

                kernel(__dynamic_netdev_dbg) = 0x6b8c340e

            Доступно: kernel-debug-3.10.0-123.13.2.v7.x86_64 (clearos)

                kernel(__dynamic_netdev_dbg) = 0x5bf60671

Ошибка: Пакет: kmod-forcedeth-0.64-1.el7.elrepo.x86_64 (elrepo)

            Необходимо: kernel(skb_clone_tx_timestamp) = 0x83433c92

            Установлено: kernel-3.10.0-123.13.2.v7.x86_64 (@anaconda/7.0beta1)

                kernel(skb_clone_tx_timestamp) = 0x9d8ea671

            Установлено: kernel-3.10.0-229.4.2.v7.x86_64 (@clearos-updates-testing)

                kernel(skb_clone_tx_timestamp) = 0xc8de65ef

            Установлено: kernel-debug-3.10.0-229.4.2.v7.x86_64 (@clearos-updates-testing)

                kernel(skb_clone_tx_timestamp) = 0x8636059d

            Доступно: kernel-debug-3.10.0-123.13.2.v7.x86_64 (clearos)

                kernel(skb_clone_tx_timestamp) = 0xe00fea91

In Installation

Monday, June 01 2015, 11:02 AM

Share this post:

Responses (3)

Accepted Answer
Nick Howitt

Offline
Wednesday, June 17 2015, 06:20 AM - #Permalink
Resolved

0 votes

Unless it has changed in ClearOS7, you cannot use the compiled kmod binaries directly from Elrepo. You need to recompile the scr.rpm against your kernel.
The reply is currently minimized Show
Accepted Answer

Rodrigo Nunes

Offline
Monday, November 23 2015, 02:14 PM - #Permalink
Resolved

0 votes

I'm having exactly the same problem.

With past editions of ClearOS all my NICs were working perfectly, on ClearOS 7, however, two of them disappeared.

I tried googling for the procedure on compiling the thing above, but I didn't find anything on that.
Could you describe it or point us in the right direction?

Thanks.
The reply is currently minimized Show
Accepted Answer
Nick Howitt

Offline
Monday, November 23 2015, 06:20 PM - #Permalink
Resolved

0 votes

You'll need to identify the drivers you need. Can you start with an "lspci -k | grep Eth -A 3". If you are going to compile your own drivers then it is possibly best to set up a development environment[/code] and probably the directory structure under your build user as set out in [url=https://www.clearos.com/clearfoundation/development/clearos/content:en_us:dev_development_environment_reference]this doc under your rpmbuild directory. You probably don't need to install the editor as you already have vi (yuck!) and nano (better) if you need one at the command line or you can edit from WinSCP.
The reply is currently minimized Show

Your Reply

Please login to post a reply

You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.

Community Forums

ClearOS Portal

ClearVM Platform

ClearVM 2 Platform

Forums