Re: [SLE] setup of D-Link ISA network card DE-220PCT
At 18:49 4/04/01 +0100, Chris Reeves wrote:
It's been so long... I used the DOS utility on at least one of them. For the past however many months I've been using append parameters with the kernel to specify IO and IRQs for both cards. The new 2.4.3 kernel which I installed yesterday uses ISAPNP on one of the cards and I have to manually set up the other, but I'll sort that later (shouldn't be too much trouble).
OK, I found the DOS utility. I used it to disable the plug and play on this card. I tried to setup the card. It seems to work with a fixed IP ("seems" is because I didn't configure the route) but not with DHCP: it doesn't get its IP address. Any idea how to solve that? You say that the kernel 2.4.3 uses ISAPNP. Same as 2.4.2 or something new about that? If it is the same, how am I supposed to use that? Thank you! Patrick
Patriiiiiiiiiick wrote:
At 18:49 4/04/01 +0100, Chris Reeves wrote:
It's been so long... I used the DOS utility on at least one of them. For the past however many months I've been using append parameters with the kernel to specify IO and IRQs for both cards. The new 2.4.3 kernel which I installed yesterday uses ISAPNP on one of the cards and I have to manually set up the other, but I'll sort that later (shouldn't be too much trouble).
OK, I found the DOS utility. I used it to disable the plug and play on this card. I tried to setup the card. It seems to work with a fixed IP ("seems" is because I didn't configure the route) but not with DHCP: it doesn't get its IP address. Any idea how to solve that?
You say that the kernel 2.4.3 uses ISAPNP. Same as 2.4.2 or something new about that? If it is the same, how am I supposed to use that?
Probably the same as kernel 2.4.2 (it's just that the 2.2.14 kernel that I was using previously didn't spew out messages about ISAPNP). If I were, I'd leave the ISAPNP bit alone. If you've got the manual setup utility, give the card a fixed IO address and IRQ, and just use those as parameter when you load the network card module, e.g.: modprobe ne io=0x300 irq=3 for a card at IO 300 and with IRQ 3. Hope that helps, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
At 09:13 6/04/01 +0100, Chris Reeves wrote:
Patriiiiiiiiiick wrote:
At 18:49 4/04/01 +0100, Chris Reeves wrote:
It's been so long... I used the DOS utility on at least one of them. For the past however many months I've been using append parameters with the kernel to specify IO and IRQs for both cards. The new 2.4.3 kernel which I installed yesterday uses ISAPNP on one of the cards and I have to manually set up the other, but I'll sort that later (shouldn't be too much trouble).
OK, I found the DOS utility. I used it to disable the plug and play on this card. I tried to setup the card. It seems to work with a fixed IP ("seems" is because I didn't configure the route) but not with DHCP: it doesn't get its IP address. Any idea how to solve that?
You say that the kernel 2.4.3 uses ISAPNP. Same as 2.4.2 or something new about that? If it is the same, how am I supposed to use that?
Probably the same as kernel 2.4.2 (it's just that the 2.2.14 kernel that I was using previously didn't spew out messages about ISAPNP).
If I were, I'd leave the ISAPNP bit alone. If you've got the manual setup utility, give the card a fixed IO address and IRQ, and just use those as parameter when you load the network card module, e.g.: modprobe ne io=0x300 irq=3 for a card at IO 300 and with IRQ 3.
It's what I did, but the DHCP didn't seem to want to give the card its IP address. I will go and try again but if you have another idea...?? Also, I saw at boot up time that some process was still trying to load the tulip module when I though I had disabled it. I didn't find the same messages in the "messages" file in var/log/... Where should it be then? And where should I go to disable it totally? Thanks again! Patrick
Patriiiiiiiiiick wrote:
At 09:13 6/04/01 +0100, Chris Reeves wrote:
If I were, I'd leave the ISAPNP bit alone. If you've got the manual setup utility, give the card a fixed IO address and IRQ, and just use those as parameter when you load the network card module, e.g.: modprobe ne io=0x300 irq=3 for a card at IO 300 and with IRQ 3.
It's what I did, but the DHCP didn't seem to want to give the card its IP address. I will go and try again but if you have another idea...??
Unfortunately not. The DHCP server may be set up to only give IPs to cards with specific MAC addresses. If your card doesn't have one of these MAC addresses, it won't be offered an address. You could try posting any error messages you get to the list.
Also, I saw at boot up time that some process was still trying to load the tulip module when I though I had disabled it. I didn't find the same messages in the "messages" file in var/log/... Where should it be then? And where should I go to disable it totally?
Check /etc/init.d/boot.local (for 7.1) or /sbin/init.d/boot.local (for <= 7.0). Also check /etc/modules.conf for lines like: alias eth0 tulip and check /etc/lilo.conf for append parameters possibly specifying tulip (although I don't think this is possible). Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
At 17:54 6/04/01 +0100, Chris Reeves wrote:
Patriiiiiiiiiick wrote:
At 09:13 6/04/01 +0100, Chris Reeves wrote:
If I were, I'd leave the ISAPNP bit alone. If you've got the manual setup utility, give the card a fixed IO address and IRQ, and just use those as parameter when you load the network card module, e.g.: modprobe ne io=0x300 irq=3 for a card at IO 300 and with IRQ 3.
It's what I did, but the DHCP didn't seem to want to give the card its IP address. I will go and try again but if you have another idea...??
Unfortunately not. The DHCP server may be set up to only give IPs to cards with specific MAC addresses. If your card doesn't have one of these MAC addresses, it won't be offered an address. You could try posting any error messages you get to the list.
OK, I did it. I think that there were many problems at the same time. Maybe the windows system that had not released the IP. And also, sometimes, I forgot to write the "0x" in "0x300". Maybe something alse too.
Also, I saw at boot up time that some process was still trying to load the tulip module when I though I had disabled it. I didn't find the same messages in the "messages" file in var/log/... Where should it be then? And where should I go to disable it totally?
Check /etc/init.d/boot.local (for 7.1) or /sbin/init.d/boot.local (for <= 7.0). Also check /etc/modules.conf for lines like: alias eth0 tulip
I found some of those but there is still another one remaining... Where?
and check /etc/lilo.conf for append parameters possibly specifying tulip (although I don't think this is possible).
No there was none. Thank you for the continuous help! Patrick
participants (2)
-
Chris Reeves -
Patriiiiiiiiiick