Network not working [message #21357] |
Fri, 05 October 2007 16:42 |
ugob
Messages: 271 Registered: March 2007
|
Senior Member |
|
|
Hi,
I have a dedicated server in a datacenter, and when I try to boot with openvz kernel, I loose network. I have asked the datacenter personnel to reboot in a stock Centos4 kernel, and I'm waiting for it to come back up.
I think the network card might not be supported. I think it is a marvell chipset. As soon as the server is up, I can provide info.
What should I look for? lspci output? dmesg output? lsmod?
Regards,
Ugo
Please read the manual before asking questions:
http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf
Please have a look at the wiki before asking questions:
http://wiki.openvz.org/Main_Page
|
|
|
|
Re: Network not working [message #21361 is a reply to message #21357] |
Fri, 05 October 2007 17:15 |
ugob
Messages: 271 Registered: March 2007
|
Senior Member |
|
|
lspci:
01:0d.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)
dmesg:
eth0: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter
PrefPort:A RlmtMode:Check Link State
lsmod:
sk98lin 144553 1
Weird, here I found someone using openvz kernel with this card:
http://www.nabble.com/cmnd_abort-issues-in-wb-mode-t3095315. html
I've also seen that a sky2 kernel module may be used with this kind of card.
In /var/log/messages:
Oct 5 12:38:08 server kernel: NET: Registered protocol family 10
Oct 5 12:38:08 server kernel: IPv6 over IPv4 tunneling driver
Oct 5 12:40:52 server syslogd 1.4.1: restart.
Oct 5 12:40:52 server syslog: syslogd startup succeeded
Oct 5 12:40:52 server kernel: klogd 1.4.1, log source = /proc/kmsg started.
Oct 5 12:40:52 server kernel: Linux version 2.6.9-55.0.9.ELsmp (mockbuild@builder6.centos.org) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-8)) #1 SMP Thu Sep 27 18:27:41 EDT 2007
Oct 5 12:40:52 server kernel: BIOS-provided physical RAM map:
Oct 5 12:37:59 server ifup: sk98lin device eth0 does not seem to be present, delaying initialization.
Oct 5 12:38:05 server kernel: PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
Oct 5 12:37:58 server kudzu: Run '/usr/sbin/kudzu' from the command line to re-detect.
I can give root access via PM to an openvz developper.
Please read the manual before asking questions:
http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf
Please have a look at the wiki before asking questions:
http://wiki.openvz.org/Main_Page
|
|
|
Re: Network not working [message #21362 is a reply to message #21361] |
Fri, 05 October 2007 17:17 |
ugob
Messages: 271 Registered: March 2007
|
Senior Member |
|
|
[root@server ~]# lspci -nn
00:00.0 Class 0600: 8086:2570 (rev 02)
00:02.0 Class 0300: 8086:2572 (rev 02)
00:1d.0 Class 0c03: 8086:24d2 (rev 02)
00:1d.1 Class 0c03: 8086:24d4 (rev 02)
00:1d.2 Class 0c03: 8086:24d7 (rev 02)
00:1d.3 Class 0c03: 8086:24de (rev 02)
00:1d.7 Class 0c03: 8086:24dd (rev 02)
00:1e.0 Class 0604: 8086:244e (rev c2)
00:1f.0 Class 0601: 8086:24d0 (rev 02)
00:1f.1 Class 0101: 8086:24db (rev 02)
00:1f.5 Class 0401: 8086:24d5 (rev 02)
01:0d.0 Class 0200: 11ab:4320 (rev 13)
Please read the manual before asking questions:
http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf
Please have a look at the wiki before asking questions:
http://wiki.openvz.org/Main_Page
|
|
|
|
|
Re: Network not working [message #21365 is a reply to message #21364] |
Fri, 05 October 2007 18:34 |
ugob
Messages: 271 Registered: March 2007
|
Senior Member |
|
|
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
01:0d.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)
===================
[root@server ~]# ll /etc/sysconfig/network-scripts/ifcfg*
-rw-r--r-- 1 root root 68 Jun 20 11:49 /etc/sysconfig/network-scripts/ifcfg-eth0
-rw-r--r-- 1 root root 254 Jun 20 2001 /etc/sysconfig/network-scripts/ifcfg-lo
Would you like to have acces to the machine?
Please read the manual before asking questions:
http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf
Please have a look at the wiki before asking questions:
http://wiki.openvz.org/Main_Page
|
|
|
Re: Network not working [message #21620 is a reply to message #21361] |
Fri, 12 October 2007 10:42 |
khorenko
Messages: 533 Registered: January 2006 Location: Moscow, Russia
|
Senior Member |
|
|
Hello Ugo,
most probably i know the reason of the network disappearance.
The key thing here is:
> lsmod:
> sk98lin 144553 1
2.6.9-x kernels support your NIC with sk98lin driver, while this driver was obsoleted in 2.6.18-x (and not compiled).
In 2.6.18-x kernels skge driver supportd your NIC, so please try to edit /etc/modprobe.conf and replace alias eth0 from 'sk98lin' to 'skge'.
P.S. please note, that after this action the network won't start up automatically on stock CentOS4 kernel.
To check if skge works ok with your NIC, just 'modprobe skge' while running 2.6.18. eth0 should appear.
If you want to be able to boot both CentOS4 stock kernel (2.6.9) and OpenVZ kernel (2.6.18), you can try to hack /etc/init.d/network sctipt, adding 'modprobe skge' line at the very begginng of it.
Hope this helps.
--
Konstantin.
If your problem is solved - please, report it!
It's even more important than reporting the problem itself...
|
|
|
|
|