DecChip 21041 and Kernel 2.6 issue

[Joni]

Hi!

 

I have an ethernet adapter called Decchip 21041 and I have serious problems with it. I have istalled Mandrake 10 several times and ONLY with kernel 2.4 I get the Internet work.

 

Both 2.4 and 2.6 kernels indentify the card, but only 2.4 lets me to internet. I have got the internet work with 2.4 like this:

 

I set up the internet as "LAN" and auto IP ( I have DHCP ). This I did in the Wizard which helped me to set up my network.

 

However I did the very same thing with 2.6 Kernel, but it didint work. I tried all the other options in the wizard, like ppoe. But nothing helped. The card identified but no acces to the net.

 

The module is tulip already after installation on MDK, but doesnt help.

 

And when I go to console ( and shutted down the xfree ) and when I type that command which "gets" the IP, the whole pc crahses!

 

I have tried this mostly with mandrake 10 and 10.1 official, but still issue with 2.6 kernel. Can you help me with my problem? :unsure:

[devries]

https://mandrivausers.org/index.php?showtopic=15646&hl=tulip

 

Thanks to JH brewer

 

for Users of the popualr tulip NIC's (also called dec tulip)

 

 

QUOTE 

for the Tulip it lists Module: de2104x

rather than tulip. So I edited my /etc/modprobe.conf file and where it said

alias eth1 tulip I changed it to alias eth1 de2104x

and then did modprobe de2104x

after which ifup eth1 worked! 

 

 

JH Brewer had two NIC's with eth0 being a 3com and the eth1 tulip not recognised after upgrading from 9.2 to 10.....

 

If you just have one NIC and its eth0 then obviously

 

CODE 

 

alias eth0 de2104x

[Joni]

I checked harddrake and it says next:

 

Decchip 21041 Tulip Pass 3

 

väylä: PCI

väylä PCI #: 0

PCI laite: 11

PCI toiminto #: 0

Valmistajan tunnus: 4113

Laitetunnus: 20

Valmistajan alitunniste: 65535

Laitteen alitunniste: 65535

Moduuli: de2104x

 

 

 

 

I'm sorry it's finnish, but it says that module is de2104x.

[devries]

And what does your /etc/modprobe.conf say? Have you changed alias etc(x) tulip to alias eth(x) de2104x?

[Joni]

And what does your /etc/modprobe.conf say? Have you changed alias etc(x) tulip to alias eth(x) de2104x?

<{POST_SNAPBACK}>

 

Sorry for the delay. I'm ogint to install MDK 10.1 Official with 2.6 kernel and I set it up as LAN. I'll check that modprobe file as soon as I get it installed and I'll copy it here.

[Joni]

Hi again.

My modprobe.conf says:

 

alias eth0 de2104x

 

 

But still no working :(

[devries]

Open a console, login as root and type: lsmod | grep de2104x. You should see, hopefully, nothing. Then type: modprobe de2104x and ifup eth0.

[Joni]

Open a console, login as root and type: lsmod | grep de2104x. You should see, hopefully, nothing. Then type: modprobe de2104x and ifup eth0.

<{POST_SNAPBACK}>

 

I went to a console and I typed as a root:

 

lsmod | grep de2104x

 

but i get this: bash: Ismod: command not found

 

But still I typed:

 

ifup eth0

 

and i got this:

 

Determining IP information for eth0.......

 

 

--> and after a few moment I got this right after that " determining...":

 

/sbin/ifup: line 466: 5190 Hangup

 

/etc/init.d/tmdns reload >/dev/null 2>&1

 

 

 

 

 

I copied that fast on a paper and wrote that here. In that text above shouldnt be any spelling mistakes. I wrote that quite similarly that i got it to my console.

Edited July 4, 2005 by Joni

[devries]

It's lsmod and not Ismod :)

 

 

Google says tmdns has something to do with zeroconf. You don't need that. In the MCC leave everything blank that has to do with zeroconf.

[Joni]

It's lsmod and not Ismod :)

 

 

Google says tmdns has something to do with zeroconf. You don't need that. In the MCC leave everything blank that has to do with zeroconf.

<{POST_SNAPBACK}>

 

Oh, what a newbie mistake

 

Well, now I wrote that "lsmod" right, but I got this right after lsmod | grep de2104x:

 

de2104x 18208 0

 

 

You said earlier that there shouldnt read anything after the lsmod. Still I continued typing modprobe de2104x and ifup eth0, but still comes that "determining IP information..." and that "error" after that which I wrote earlier and no acces to net :unsure:

Edited July 4, 2005 by Joni