OpenVZ Forum: Support » *SOLVED* Hardware Drivers

Home » General » Support » *SOLVED* Hardware Drivers

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

*SOLVED* Hardware Drivers [message #6030]

Thu, 07 September 2006 03:05

tiggerific
Messages: 8
Registered: September 2006

Junior Member

Hi there,

I'm just getting started with OpenVZ and unfortunately I haven't been able to get very far at all Sad

I have followed the installation instructions and got the kernel installed, but I'm not able to boot into the VZ kernel due to a hardware configuration issue.

Here is the relevant info from the messages log:

8139cp: pci dev 0000:02:01.0 (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
Sep 5 20:01:12 server kudzu: Hardware configuration timed out.
Sep 5 20:01:18 server kernel: 8139cp: Try the "8139too" driver instead.

Bear with me as I have no idea when it comes to hardware config on Linux (pretty good with software though).

Anyway, is this issue something within the kernel that I can resolve or is it something my host needs to provide?

Any pointers as to where to head would be really appreciated.

Thanks in advance.

Tigger.

[Updated on: Thu, 07 September 2006 09:45] by Moderator

Report message to a moderator

Re: Hardware Drivers [message #6033 is a reply to message #6030]

Thu, 07 September 2006 05:29

Vasily Tarasov
Messages: 1345
Registered: January 2006

Senior Member

Hello,

Is the problem in this _message_ only?
I mean, can you normally _work_ on this node or
you do you have some problems with it?

Tanks!

Report message to a moderator

Re: Hardware Drivers [message #6035 is a reply to message #6033]

Thu, 07 September 2006 05:47

tiggerific
Messages: 8
Registered: September 2006

Junior Member

I purchased this server "bare-bones" with CentOS 4.x installed so that I could configure it for OpenVZ. As far as "working" it's booting and giving me network access, etc. when using the original kernel.

When I try to boot to the OpenVZ kernel, the network is failing because the Ethernet device drivers aren't being loaded.

My biggest problem is that I've tried to set the original kernel as the fallback in my grub.conf, but grub doesn't seem to think that the OpenVZ kernel has failed - seeing that it does absolutely everything except get the network started. Hence, it sits there running with no network access and I have to call in support to reboot to the original kernel every time.

So, that's as far as I have got - ordered a server, installed the OpenVZ kernel - and then.... nothing Wink

Report message to a moderator

Re: Hardware Drivers [message #6036 is a reply to message #6035]

Thu, 07 September 2006 06:02

Vasily Tarasov
Messages: 1345
Registered: January 2006

Senior Member

OK =)
According to your post, you have network device 10ec:8139.
This device is serviced by driver 8139too. In OpenVZ kernel from
RPM this driver is compiled as a module.
So try to load this manually (using modprobe) and (re)start network sevice again (something like "service network (re)start" on CentOS, I don't rememeber quite...). After that network should be available. If so - we've found the root of the problem. =)

And the only thing you have to do - make this module loadable on startup.

HTH!

Report message to a moderator

Re: Hardware Drivers [message #6037 is a reply to message #6036]

Thu, 07 September 2006 06:18

tiggerific
Messages: 8
Registered: September 2006

Junior Member

Well now I'm going to show how little knowledge I have when it comes to kernels and hardware ...

1. I do know how to restart the network, this is not a problem.
2. If I can't get access to the network whenever the kernel I want is loaded, then I can't actually test your theory (I only have SSH access).
3. I've never used modprobe and have no idea how to use it.
4. From my looking around, I also believe this is the problem that the correct module isn't loaded - but the only time it isn't loaded appears to be when the OpenVZ kernel is booted. Is there something missing from my kernel config or something that is in the other configs, that will make sure this module will load.

I have looked through various .config files and such and found where the 8139TOO module is enabled but I can't tell whether it's right or not, so I haven't touched anything there.

Thanks so much for your help so far.

Report message to a moderator

Re: Hardware Drivers [message #6038 is a reply to message #6037]

Thu, 07 September 2006 06:40

Vasily Tarasov
Messages: 1345
Registered: January 2006

Senior Member

Ok. I get it Smile

Please post her content of the file /etc/modprobe.conf.

Thanks.

Report message to a moderator

Re: Hardware Drivers [message #6039 is a reply to message #6038]

Thu, 07 September 2006 06:45

tiggerific
Messages: 8
Registered: September 2006

Junior Member

Just so there's no confusion... this is the currently loaded kernel:

2.6.17.5-HN-2.3-P4 #1 SMP Sat Jul 15 09:55:04 EDT 2006 i686 i686 i386 GNU/Linux

And here's the contents of modprobe.conf

alias eth1 8139too

(which looks good to me!)

What's next?

Report message to a moderator

Re: Hardware Drivers [message #6040 is a reply to message #6039]

Thu, 07 September 2006 07:00

Vasily Tarasov
Messages: 1345
Registered: January 2006

Senior Member

Do you have two interfaces?! Shocked

Why don't you say early! Smile

post `lspci` and `lapci -n` output here, please.

Thanks.

P.S. If you have two interfaces, then, probably they are detected in different order by OpenVZ kernel and by your current kernel.
BTW, what OpenVZ kernel do you use?

Report message to a moderator

Re: Hardware Drivers [message #6042 is a reply to message #6040]

Thu, 07 September 2006 07:25

tiggerific
Messages: 8
Registered: September 2006

Junior Member

Um... I dunno Confused

Told you hardware wasn't my thing.

lspci:

[root@server etc]# lspci
00:00.0 Host bridge: Intel Corporation 82845 845 (Brookdale) Chipset Host Bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 82845 845 (Brookdale) Chipset AGP Bridge (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 12)
00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 12)
00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 (rev 12)
00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus (rev 12)
02:00.0 VGA compatible controller: S3 Inc. 86c764/765 [Trio32/64/64V+]
02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

lapci:
[root@server etc]# lapci -n
-bash: lapci: command not found

Kernel I'm "trying" to load is:
vmlinuz-2.6.8-022stab078.14-smp

Thanks again.

Report message to a moderator

Re: Hardware Drivers [message #6044 is a reply to message #6042]

Thu, 07 September 2006 07:36

Vasily Tarasov
Messages: 1345
Registered: January 2006

Senior Member

According to lspci, seems, that there is only one network device on your node... (btw, I meant `lspci -n`, not `lapci -n`, so sorry for missprint Rolling Eyes

)

If only one interface presents, then why "eth1" in modprobe.conf then?.. (not "eth0"). Ok, I hope the last step of out small investigation. Smile

Post here `ifconfig -a` output. You can replace IP addresses by x.x.x.x for security purposes.

Thanks.

P.S. Is it free for you to reboot the remote node? I mean, if we'll do an experiment and it won't succeded - is it ok?

Report message to a moderator

Re: Hardware Drivers [message #6046 is a reply to message #6044]

Thu, 07 September 2006 08:54

tiggerific
Messages: 8
Registered: September 2006

Junior Member

[root@server etc]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:50:FC:B5:21:92
inet addr:66.x.x.x Bcast:66.x.x.x
Mask:255.255.255.240
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:35281 errors:0 dropped:0 overruns:0 frame:0
TX packets:27044 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2769520 (2.6 MiB) TX bytes:2753155 (2.6 MiB)
Interrupt:16 Base address:0xc000

gre0 Link encap:UNSPEC HWaddr 00-00-00-00-EF-B7-27-2D-00-00-00-00-00-00-00-00
NOARP MTU:1476 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)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:34 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5329 (5.2 KiB) TX bytes:5329 (5.2 KiB)

tunl0 Link encap:IPIP Tunnel HWaddr
NOARP MTU:1480 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)
====================

reboots are free - just have to wait for support

and if you want me to reboot into another kernel - perhaps you can remind how to set it up to do it once, then revert to the default?

Thanks again.

Report message to a moderator