module nvnet not working

[pixelxeno]

Hello,

I got a brand new shuttle, the SN41G2, with a nforce2 chipset inside, and everything is working really nice and fine under linux expect the network. I'm running a debian and here what I get:

With the bare 2.4.18-bf kernel shipped with the debian system, I get the message "PCI: Setting latency timer of device 00:04.0 to 64" when I modprobe nvnet, then if I try to ifconfig eth0 up the device, the kernel goes panic inside the syscall of ifconfig. Further call to ifconfig or rmmod nvnet does freeze.

Then I tried to compile both a 2.4.20 and 2.4.21-pre7 kernel, and there the module loads perfectly, I can ifconfig eth0 up the nvnet adapter, but it simply doesn't work. If I try to send packets thru the interface, the little led behind the machine doesn't blink. And of course, ifconfig shows that packets are emitted, but no packet at all are received. And things like ethereal shows that nothing goes out the interface (with ethereal running on another computer linked to the shuttle) nor in (with ethereal running on the shuttle, hence the kernel actually thinks it sends the packets, so I can see them)

So, well, what should I do? It seems that this bug was not already reported (I went through the forum, and I didn't see any message like mine)

I'm actually running the shuttle under linux with a third party PCI network card which is not a good solution for me since I've got only one PCI slot in the shuttle :rolleyes: So I really would like the nvnet driver to be working :)

[pixelxeno]

Ok, my bad, I did mistaken with some bits in my installation of the driver, it is working now ;-)

But I'll stick around this forum to help out a bit if I can. See you!

[elforro]

Hey, i had the same problem with my SN41G2 and Debian woody !!! ... can you tell me how did you solve the problem ?? Please, I don't want to switch to RedHat !

Thanks !

[pixelxeno]

In fact, I was using a custom kernel 2.4.21-pre7, and since there is firewire in the machine, I enabled the thing for it, and thus, it created an eth0 for that. My nvnet device was eth1. So, it should work perfectly with a 2.4.21 kernel.

[elforro]

mmm ... ok, I'll test with a 2.4.21 kernel ... I'm not sure to understand everything about the firewire (your firewire is used as eth0 ?) but I gona try it ... thanks ! :)

[pixelxeno]

Using a simple cable, you can link two computer directly with firewire ports. The linux ethernet-over-firewire driver supports that, and thus, build an ethernet device over the line.

[elforro]

:(

it does not seem to work for me ... maybe I'm doing something bad ... the kernel works well, the nvnet module compile and loads fine, I can ping machines over internet but I can't connect to them ! can you send me your kernel .config file ?

[pixelxeno]

If you CAN ping machines on the net, then it's allright! You only have to finish configuring your network! Just verify your /etc/resolv.conf is well defined and does contain a valid nameserver.

[elforro]

it's strange ... I can ping a domain like www.google.com but I can't connect to the website ! idem for all the FTP servers I've tried ... I can't figure where is the clue !!

:(

[elforro]

Please, this problem is eating all my time !! I can't get a proper network configuration, but I suspect a kernel issue ... can you send me a .config kernel file ?

[leibold]

Try building a kernel without ACPI, or turn off ACPI on the boot commandline. At least that works for me on the ASUS A7N8X.

[elforro]

thanks for your response :) but unfortunatly it didn't change anything ... and I can't figure if it's the nvnet module which works bad or my linux configuration. I have a debian laptop in the same network, with the same configuration, and it works perfectly...

[elforro]

AAARGGHH !!

It's a real nightmare !!

:banghead:

I've whipped off my debian and installed a RedHat 9.0 (kernel 2.4.20) ... I compiled and installed the nvnet module: perfect, no errors, everything is detected with the "redhat-config-network" tool.

Now,
I ping my gateway: ok
I ping other computers in my network : ok
I ping www.google.fr : ok
I do "telnet www.google.fr 80" : nothing ! it hangs ! and it do the same thing with an internal webserver !!!

:argh:

what's going on with these packets ???

Rem: I have WinXP on the SN41G2 who works perfectly, a debian laptop in the same network who also works perfectly, so I don't suspect my gateway, the cables, etc...

[petterl]

I have exactly the same problems with two Asus A7N8X-VM computers. One has RedHat 9 installed and the other Gentoo.
With the newest driverpackage on both (On The gentoo-mashine it is installed from tar.gz and on RedHat from the srpm).

nvnet loads ok, and ping to other ips work fine, but ssh, wget, samba or anything else won't work.

Please help! :confused:

[elforro]

yes, it's the same for me ... I feel less alone now !

:D

I've tried various kernels (2.4.18, 2.4.20, 2.4.21) and it's always the same thing. I can select a static IP in my network or request it with DHCP, it works. But when I want to use other services (HTTP, ssh, FTP...), it doesn't work. As I said in the last post, I've also tried changing my linux debian to a linux redhat with no results.

Maybe a BIOS option to (de)activate ?

[petterl]

I can't get it to work at all.

Can we expect any updates to the nvnet-driver anytime soon?

[Unicorn]

Greetings!

To sum it up - same story here... Soltek SL-75FRN2-LR, nForce2, Slackware 9.0, 2.4.21 release, driver ... well, the last one available from the site. Module compiles OK, installs and loads OK, interface goes UP... And then - ICMP works, but no UDP or TCP passes through it... I can't get it.

[mergl]

my first attempt was to install Win2K on the
A7N8X-VM. After having installed the network driver the first dhcp request was ok, so the machine
got its IP-address, but anything else was not
working, Not even a ping was possible.

The second attempt was to install RedHat 9.
After having build the nvnet module from source,
I was able to configure the network. Ping works
and any host-lookup, but nothing else.

Edmund

[elforro]

Well, with my configuration, the driver worked out of the box with windows XP... Check in the network connections if you have something called "network MAC bridge" or anything like that (I'm running windows in french)

[mergl]

MAC bridge sounds firewire related.
The Asus A7N8X-VM does not support
firewire.
On machines with firewire XP installs
per default a bridge between firewire and
ethernet.

Edmund

[petterl]

I have no Firewire briging enabled, so that is not my problem.
It looks like we are sereral people with the same problem now...

[elforro]

yes, the same problem but without a solution ... I've tried with various BIOS options in my motherboard but it didn't changed anything ...

[Linuxfan]

hi, same story here :mad:

just bought a new computer, amd 2.5GHz + Asus A7N8X-X and can't get working the nvnet driver, also under Windows XP. I've tried all the suggestions (no ACPI, ethtool, etc) but still can't connect to my peer notebook, any idea ? should I need to buy another nic ..?

Thanks.
JC.

[hardraid]

I have same problem on SL-75FRN2L (RedHat 7.3 2.4.18_3)
It is ping (ICMP package) but no any IP-stack based packeges (IP, TCP, UDP)

[Linuxfan]

Regarding my previous post, it was my fault, not nvidia's nvnet driver, I was having a problem related with one of my RJ45 connectors... :D

Now my nvnet nic is working flawlessly.