OpenVZ Forum


Home » General » Support » Dell Dimension 4300 - NIC module dmfe missing
Dell Dimension 4300 - NIC module dmfe missing [message #487] Fri, 09 December 2005 19:22 Go to next message
dowdle is currently offline  dowdle
Messages: 261
Registered: December 2005
Location: Bozeman, Montana
Senior Member
Installed on an existing FC4 Hardware Host. When booting into the openvz kernel I get an error message when it tries to bring up the network.

My stock FC4 kernel loads the dmfe module for the NIC:
(from /etc/modprobe.conf)
alias eth0 dmfe

lspci | grep Ethernet
02:09.0 Ethernet controller: Davicom Semiconductor, Inc. 21x4x DEC-Tulip compatible 10/100 Ethernet (rev 31)

Stock kernel has
/lib/modules/2.6.14-1.1644_FC4/kernel/drivers/net/tulip/dmfe .ko while it is missing from openvz kernel.

I know that OpenVZ has many drivers compiled into the kernel rather than as modules but this doesn't seem to be the case for this NIC.

I'd attempt to compile my own kernel but given the complexity of the process, I'm wondering if there is a technical reason it is missing... or if it can eventually be incorporated into OpenVZ stable kernel??

I got OpenVZ working on another machine just fine (with the exception of the sound device)... and am really impressed.



--
TYL, Scott Dowdle
Belgrade, Montana, USA

[Updated on: Fri, 09 December 2005 23:35]

Report message to a moderator

Re: Dell Dimension 4300 - NIC module dmfe missing [message #490 is a reply to message #487] Sat, 10 December 2005 00:39 Go to previous messageGo to next message
dowdle is currently offline  dowdle
Messages: 261
Registered: December 2005
Location: Bozeman, Montana
Senior Member
A little more info:

In dmesg of stock kernel:
eth0: Davicom DM9102 at pci0000:02:09.0, 00:80:ad:78:c4:ff, irq 11
[...]
dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)

From Virtuozzo Hardware Compatibility page:
http://www.virtuozzo.com/en/products/virtuozzo/hcl/network/
Davicom DM9102/DM9102A 21x4x DEC-Tulip compatible 10/100 Ethernet Adapter 0x9100

So, perhaps I'm doing something wrong? Suggestions?

I loaded the tulip module by hand and it did bring up the interface, but it didn't work. I could ping IP addresses (not names although resolv.conf is fine) but no application protocols seemed to work. Lost on this one.


--
TYL, Scott Dowdle
Belgrade, Montana, USA
Re: Dell Dimension 4300 - NIC module dmfe missing [message #497 is a reply to message #490] Mon, 12 December 2005 09:58 Go to previous messageGo to next message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member

What is the version of OpenVZ kernel you are using?

Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png
Re: Dell Dimension 4300 - NIC module dmfe missing [message #498 is a reply to message #490] Mon, 12 December 2005 11:42 Go to previous messageGo to next message
vaverin is currently offline  vaverin
Messages: 708
Registered: September 2005
Senior Member
Hello Dowdie,

we support this hardware by tulip driver.

you need to replace alias in /etc/modprobe.conf
alias eth0 tulip

I hope it resloves this issue.

If you want we can add the compilation of dmfe module into our next kernels. Could you please confirm that you really need it and you are able to test it.

thank you,
Vasily Averin
Re: Dell Dimension 4300 - NIC module dmfe missing [message #500 is a reply to message #498] Mon, 12 December 2005 16:01 Go to previous messageGo to next message
dowdle is currently offline  dowdle
Messages: 261
Registered: December 2005
Location: Bozeman, Montana
Senior Member
The kernel I'm using the latest/greatest (at time of writing):
2.6.8-022stab050.1

Ok, followed your advice and tulip driver seems to be working... especially since I turned off iptables on the hardware host.

Thanks for your assistance.


--
TYL, Scott Dowdle
Belgrade, Montana, USA
Re: Dell Dimension 4300 - NIC module dmfe missing [message #502 is a reply to message #500] Mon, 12 December 2005 16:05 Go to previous message
kir is currently offline  kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia
Senior Member

As for iptables, the reason is stateful rules - you need to remove them from config (/etc/sysconfig/iptables). Quoting the FAQ:

Quote:

Q. My node is unaccessible through the network after reboot...

A. You need to check your firewall rules. The problem is that default stateful firewall rules are not available on the host system. To make this functionality available, load the ip_conntrack module with the additional parameter "ip_conntrack_enable_ve0=1". However, this method is highly not recommended because tracking all the connection on the host system lead to performance degradation, more memory usage and also may lead to the total server inaccessibility due to reaching of the overall connection limit.


Kir Kolyshkin
http://static.openvz.org/userbars/openvz-developer.png

[Updated on: Mon, 12 December 2005 16:05]

Report message to a moderator

Previous Topic: Samba
Next Topic: vzpkgcache
Goto Forum:
  


Current Time: Fri Jul 25 15:11:31 GMT 2025

Total time taken to generate the page: 0.26567 seconds