OpenVZ Forum


Home » General » Support » *SOLVED* OpenVZ: No driver for NIC RTL8111/8168B [solved]
Re: *SOLVED* OpenVZ: No driver for NIC RTL8111/8168B [solved] [message #39298 is a reply to message #25385] Sat, 03 April 2010 20:42 Go to previous messageGo to previous message
abdicar is currently offline  abdicar
Messages: 17
Registered: April 2010
Junior Member
Quote:
[root@22491 ~]# wget http://www.abdicar.com/r8168-8.018.00.tar.bz2
--2010-04-03 22:32:06-- http://www.abdicar.com/r8168-8.018.00.tar.bz2
Resolving www.abdicar.com... 200.50.226.5
Connecting to www.abdicar.com|200.50.226.5|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 49160 (48K) [application/x-bzip2]
Saving to: `r8168-8.018.00.tar.bz2'

100%[======================================================= ============================================================ =========== >] 49,160 --.-K/s in 0.04s

2010-04-03 22:32:06 (1.15 MB/s) - `r8168-8.018.00.tar.bz2' saved [49160/49160]

[root@22491 ~]# tar xvfz r8168-8.018.00.tar.bz2

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error exit delayed from previous errors
[root@22491 ~]# tar xvz r8168-8.018.00.tar.bz2

[4]+ Stopped tar xvz r8168-8.018.00.tar.bz2
[root@22491 ~]# ls
lspci lspci_ovz r8168-8.018.00.tar.bz2
[root@22491 ~]# tar -xjvf r8168-8.018.00.tar.bz2
r8168-8.018.00/
r8168-8.018.00/Makefile
r8168-8.018.00/README
r8168-8.018.00/src/
r8168-8.018.00/src/rtl_eeprom.h
r8168-8.018.00/src/Makefile
r8168-8.018.00/src/r8168_asf.c
r8168-8.018.00/src/r8168.h
r8168-8.018.00/src/rtl_eeprom.c
r8168-8.018.00/src/r8168_asf.h
r8168-8.018.00/src/rtltool.h
r8168-8.018.00/src/r8168_n.c
r8168-8.018.00/src/Makefile_linux24x
r8168-8.018.00/autorun.sh
[root@22491 ~]# cd r8168-8.018.00/
[root@22491 r8168-8.018.00]# ls
autorun.sh Makefile README src
[root@22491 r8168-8.018.00]# nano README
[root@22491 r8168-8.018.00]#

[root@22491 r8168-8.018.00]# ./autorun.sh

Check old driver and unload it.
rmmod r8169
Build the module and install
/root/r8168-8.018.00/src/r8168_n.c: In function ârtl8168_tx_clearâ:
/root/r8168-8.018.00/src/r8168_n.c:8073: warning: unused variable âdevâ
Backup r8169.ko
rename r8169.ko to r8169.bak
Depending module. Please wait.
load module r8168
Completed.
[root@22491 r8168-8.018.00]#
[root@22491 r8168-8.018.00]# mii-tool
eth0: negotiated 10baseT-FD, link ok
[root@22491 r8168-8.018.00]# service network restart
Shutting down interface eth0: [ OK ]
Shutting down interface venet0: Shutting down interface venet0:
[ OK ]
Shutting down loopback interface: [ OK ]
Disabling IPv4 packet forwarding: net.ipv4.ip_forward = 0
[ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface venet0: Bringing up interface venet0:
Configuring interface venet0:
net.ipv4.conf.venet0.send_redirects = 0
[ OK ]
[root@22491 r8168-8.018.00]# service vz restart
Shutting down CT 101
Bringing down interface venet0: [ OK ]
Stopping OpenVZ: [ OK ]
Starting OpenVZ: [ OK ]
Bringing up interface venet0: [ OK ]
Configuring interface venet0: [ OK ]
Starting CT 101: [ OK ]
[root@22491 r8168-8.018.00]#


So, now test again from the container...

Quote:
[root@22491 r8168-8.018.00]# vzctl enter 101
entered into CT 101
[root@ns01 /]# ping yahoo.com

[1]+ Stopped ping yahoo.com
[root@ns01 /]# host yahoo.com

[2]+ Stopped host yahoo.com
[root@ns01 /]# mii-tool
SIOCGMIIPHY on 'eth0' failed: Operation not permitted
SIOCGMIIPHY on 'eth1' failed: Operation not permitted
SIOCGMIIPHY on 'eth2' failed: Operation not permitted
SIOCGMIIPHY on 'eth3' failed: Operation not permitted
SIOCGMIIPHY on 'eth4' failed: Operation not permitted
SIOCGMIIPHY on 'eth5' failed: Operation not permitted
SIOCGMIIPHY on 'eth6' failed: Operation not permitted
SIOCGMIIPHY on 'eth7' failed: Operation not permitted
no MII interfaces found
[root@ns01 /]# ifconfig /all
/all: error fetching interface information: Device not found
[root@ns01 /]# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:165 (165.0 b)

venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:x.73.100.179 P-t-P:x.73.100.179 Bcast:x.73.100.179 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1

[root@ns01 /]#


The correct netmask of the IP is .248, it is normal that the VPS load it on .255?

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Delete VPS on Source Hardware Node + VZMigrate
Next Topic: Afanasyev faced problem with iptable_nat
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Tue Nov 04 03:58:41 GMT 2025

Total time taken to generate the page: 0.11643 seconds
Powered by FUDforum Powered by Virtuozzo Containers