Re: network/ethernet card configuration problem?
Hi,
Many thanks again to the several people who offered their advice
to help me solve my configuation problem with my
ethernet card (Simon Hales, John (?), Bolan Meek, Esko Lehtonen,
and John Pearson)! The method described below (by John Pearson)
was the first that I tried, and it worked perfectly. (Note: the card
did turn out to be a PnP card).
James Polson
> Date: Wed, 19 Jul 2000 10:47:35 +0930
> From: John Pearson <[EMAIL PROTECTED]>
> Subject: Re: network/ethernet card configuration problem?
> To:debian-user@lists.debian.org
> On Tue, Jul 18, 2000 at 12:00:46PM -0300, James Polson wrote
> > Hi,
> >
> > Thanks to all who answered my call for help! This message here is in
> > response to the one from John Pearson.
> >
> >
> > > Date: Tue, 18 Jul 2000 13:15:56 +0930
> > > From: John Pearson <[EMAIL PROTECTED]>
> > > Subject: Re: network/ethernet card configuration problem?
> > > To:debian-user@lists.debian.org
> >
> >
> > > The "correct" way to proceed depends on which version of Debian you are
> > > using (slink (2.1), potato (2.2), etc.); which is it?
> >
> > It is slink (2.1)
> >
> > >
> > > You can check if things are going to work out for you by trying the
> > > following commands as root:
> > >
> > > # lsmod
> > >
> > > This lists the driver modules currently loaded.
> > > If the "ne" or "ne2k-pci"driver is loaded then you
> > > should see it listed in the output to this command,
> > > like so:
> > > ne2k-pci4136 1
> >
> > It was not loaded!
> >
> > >
> > > Assuming it isn't loaded, try loading it by hand.
> > > If your NIC is a PCI card you should use the ne2k-pci
> > > driver, like so:
> > > # modprobe ne2k-pci
> > >
> > > PCI cards shouldn't need any extra parameters.
> > >
> > > If it's an ISA card you will need to use the ne module,
> > > and will need to pass at least the IO port as a parameter,
> > > with a command like this:
> > > # modprobe ne io=0x300 irq=10
> > >
> > > You can skip the IRQ parameter, but if you know what it is
> > > then it makes things a little more bullet-proof. If you don't
> > > know what IO address the card is using, the Windows Device Manager
> > > (under System in Control Panels) will probably tell you.
> > >
> > > If the card is a bona-fide ISA/PNP card (as opposed to a
> > > traditional ISA card) then this will fail after a cold boot, and
> > > you will need to set the card up using isapnp before you can
> > > use it under Linux.
> > >
> >
> > The full name of the card is D-Link DE220 ISA PnP -- is this
> > a bona-fide ISA/PNP adaptor?
> >
> > I tried using the command
> >
> > # modprobe ne io=0x300 irq=03(these are the proper settings)
> >
> > and it didn't complain. However, I infer from your remarks that
> > I will have to use 'isapnp'. I guess that this means I will have to
> > edit (properly!) the /etc/isapnp.conf file. I looked at the website
> >
> > http://www.roestock.demon.co.uk/isapnptools
> >
> > and it looks like I will need a line in the file like:
> >
> > (CONFIGURE EDI0119/236861364 ( ... etc.
> >
> > The code 'EDI0119' identifies the ethernet card -- but how can
> > I find what code to use for my card?
> >
> > Please let me know if there is anything else I have to know about
> > 'isapnp'.
> >
>
> OK.
>
> Firstly, some ISA/PnP cards have a "Software Configuration"
> mode that allows you to specify a configuration using their
> setup disk, rather than doing PnP configuration at run time.
> Ignore all of the ISA/PNP stuff below if your card has that
> option and you're using it; skip to the line
> "(If it isn't a PNP card, start here)" in that case.
>
> isapnp is the utility you use to set up ISA/PNP cards; there is a
> companion utility, pnpdump, that will interrogate your ISA/PNP cards
> for you.
>
> First, make asure that the card isn't in use by running
> # lsmod
>
> to list the currently loaded modules, and use
> # rmmod ne
> # rmmod 8390
>
> to unload the ne and 8390 modules if necessary ("8390" is a
> low-level module that is used by the "ne" module to talk to
> ne-compatible NICs). Chang
Re: network/ethernet card configuration problem?
On Tue, Jul 18, 2000 at 12:00:46PM -0300, James Polson wrote
> Hi,
>
> Thanks to all who answered my call for help! This message here is in
> response to the one from John Pearson.
>
>
> > Date: Tue, 18 Jul 2000 13:15:56 +0930
> > From: John Pearson <[EMAIL PROTECTED]>
> > Subject: Re: network/ethernet card configuration problem?
> > To:debian-user@lists.debian.org
>
>
> > The "correct" way to proceed depends on which version of Debian you are
> > using (slink (2.1), potato (2.2), etc.); which is it?
>
> It is slink (2.1)
>
> >
> > You can check if things are going to work out for you by trying the
> > following commands as root:
> >
> > # lsmod
> >
> > This lists the driver modules currently loaded.
> > If the "ne" or "ne2k-pci"driver is loaded then you
> > should see it listed in the output to this command,
> > like so:
> > ne2k-pci4136 1
>
> It was not loaded!
>
> >
> > Assuming it isn't loaded, try loading it by hand.
> > If your NIC is a PCI card you should use the ne2k-pci
> > driver, like so:
> > # modprobe ne2k-pci
> >
> > PCI cards shouldn't need any extra parameters.
> >
> > If it's an ISA card you will need to use the ne module,
> > and will need to pass at least the IO port as a parameter,
> > with a command like this:
> > # modprobe ne io=0x300 irq=10
> >
> > You can skip the IRQ parameter, but if you know what it is
> > then it makes things a little more bullet-proof. If you don't
> > know what IO address the card is using, the Windows Device Manager
> > (under System in Control Panels) will probably tell you.
> >
> > If the card is a bona-fide ISA/PNP card (as opposed to a
> > traditional ISA card) then this will fail after a cold boot, and
> > you will need to set the card up using isapnp before you can
> > use it under Linux.
> >
>
> The full name of the card is D-Link DE220 ISA PnP -- is this
> a bona-fide ISA/PNP adaptor?
>
> I tried using the command
>
> # modprobe ne io=0x300 irq=03(these are the proper settings)
>
> and it didn't complain. However, I infer from your remarks that
> I will have to use 'isapnp'. I guess that this means I will have to
> edit (properly!) the /etc/isapnp.conf file. I looked at the website
>
> http://www.roestock.demon.co.uk/isapnptools
>
> and it looks like I will need a line in the file like:
>
> (CONFIGURE EDI0119/236861364 ( ... etc.
>
> The code 'EDI0119' identifies the ethernet card -- but how can
> I find what code to use for my card?
>
> Please let me know if there is anything else I have to know about
> 'isapnp'.
>
OK.
Firstly, some ISA/PnP cards have a "Software Configuration"
mode that allows you to specify a configuration using their
setup disk, rather than doing PnP configuration at run time.
Ignore all of the ISA/PNP stuff below if your card has that
option and you're using it; skip to the line
"(If it isn't a PNP card, start here)" in that case.
isapnp is the utility you use to set up ISA/PNP cards; there is a
companion utility, pnpdump, that will interrogate your ISA/PNP cards
for you.
First, make asure that the card isn't in use by running
# lsmod
to list the currently loaded modules, and use
# rmmod ne
# rmmod 8390
to unload the ne and 8390 modules if necessary ("8390" is a
low-level module that is used by the "ne" module to talk to
ne-compatible NICs). Changing the ocnfiguration while the card
is in use is officially Naughty, and may hang your machine.
Run
# pnpdump > /etc/isapnp.conf.try
This should produce a template isapnp configuration file listing
your card, but with all of the lines that would actually specify
a configuration commented out.
Pnpdump is in the isapnptools package; install that package if
it isn't already on your system.
Here's an excerpt, showing a single device:
>> START of pnpdump output fragment
#
# Logical device id @[EMAIL PROTECTED]
# Device supports vendor reserved register @ 0x39
# Device supports vendor reserved register @ 0x3a
# Device supports vendor reserved register @ 0x3c
# Device supports vendor reserved register @ 0x3d
#
# Edit the entries below to uncomment out the configuration required.
# Note that only the first value of any range is given, this may be changed if
required
# Don't forget to uncomment the activate (ACT Y) when happy
(CONFIGURE CMI0001/16777472 (LD 3
# Multiple choice time, choose one only !
# Start dependent functions: priority preferred
#
Re: network/ethernet card configuration problem?
Hi, Thanks to all who answered my call for help! This message here is in response to the one from John Pearson. > Date: Tue, 18 Jul 2000 13:15:56 +0930 > From: John Pearson <[EMAIL PROTECTED]> > Subject: Re: network/ethernet card configuration problem? > To:debian-user@lists.debian.org > The "correct" way to proceed depends on which version of Debian you are > using (slink (2.1), potato (2.2), etc.); which is it? It is slink (2.1) > > You can check if things are going to work out for you by trying the > following commands as root: > > # lsmod > > This lists the driver modules currently loaded. > If the "ne" or "ne2k-pci"driver is loaded then you > should see it listed in the output to this command, > like so: > ne2k-pci4136 1 It was not loaded! > > Assuming it isn't loaded, try loading it by hand. > If your NIC is a PCI card you should use the ne2k-pci > driver, like so: > # modprobe ne2k-pci > > PCI cards shouldn't need any extra parameters. > > If it's an ISA card you will need to use the ne module, > and will need to pass at least the IO port as a parameter, > with a command like this: > # modprobe ne io=0x300 irq=10 > > You can skip the IRQ parameter, but if you know what it is > then it makes things a little more bullet-proof. If you don't > know what IO address the card is using, the Windows Device Manager > (under System in Control Panels) will probably tell you. > > If the card is a bona-fide ISA/PNP card (as opposed to a > traditional ISA card) then this will fail after a cold boot, and > you will need to set the card up using isapnp before you can > use it under Linux. > The full name of the card is D-Link DE220 ISA PnP -- is this a bona-fide ISA/PNP adaptor? I tried using the command # modprobe ne io=0x300 irq=03(these are the proper settings) and it didn't complain. However, I infer from your remarks that I will have to use 'isapnp'. I guess that this means I will have to edit (properly!) the /etc/isapnp.conf file. I looked at the website http://www.roestock.demon.co.uk/isapnptools and it looks like I will need a line in the file like: (CONFIGURE EDI0119/236861364 ( ... etc. The code 'EDI0119' identifies the ethernet card -- but how can I find what code to use for my card? Please let me know if there is anything else I have to know about 'isapnp'. > The way modules are handled changed a couple of times in older > (pre-2.1) Debian releases; you should check if the following files > exist: > /etc/modules.conf This one wasn't there! > /etc/conf.modules Present. > /etc/modutils/ (a directory) Present. > /etc/modules Present. > Get back to us when you've tried this and let us know what Debian > release you're using, and you should get some better-targeted > help. > Looking forward to it! James Polson
Re: network/ethernet card configuration problem?
On Mon, Jul 17, 2000 at 02:55:54PM -0300, James Polson wrote > Hi, > > I'm completely new to Linux, so the solution to my problem > may be trivial to all of you experienced Debian Linux users > (so I hope!). > > I'm trying to install Debian Linux (mostly with success), but > I think that I'm having problems connecting with the ethernet > card in my computer. > > The symptoms are: > > (1) A message during booting that is something like "network is > unreachable" (I don't know what log file to look for to get the > exact wording). > > (2) When I type "ifconfig -a", I should see listings for two > interfaces, "lo" and "eth0", but the second one (the ethernet > one) is not there. > > (3) Not surprisingly, telnet, ftp, etc. can't be used. > > (4) In the /var/log/syslog file, there is a message: > > cardmgr[189]: starting, version is 3.0.5 > cardmgr[189]: no sockets found! > cardmgr[189]: exiting > > I think that this problem reported is related. > These lines relate to the PCMCIA support software; if you have no PCMCIA slots (which is what the card manager seems to believe) then it isn't a problem; you can ignore these messages, or be rid of them by removing the pcmcia-* packages. > Information about my system: > > (1) I have a D-Link DE 220 card. > > (2) I have the NC2000 driver in /lib/modules/2.0.36/net > This is the appropriate driver for the card, according >to the D-Link website. > The "correct" way to proceed depends on which version of Debian you are using (slink (2.1), potato (2.2), etc.); which is it? You can check if things are going to work out for you by trying the following commands as root: # lsmod This lists the driver modules currently loaded. If the "ne" or "ne2k-pci"driver is loaded then you should see it listed in the output to this command, like so: ne2k-pci4136 1 Assuming it isn't loaded, try loading it by hand. If your NIC is a PCI card you should use the ne2k-pci driver, like so: # modprobe ne2k-pci PCI cards shouldn't need any extra parameters. If it's an ISA card you will need to use the ne module, and will need to pass at least the IO port as a parameter, with a command like this: # modprobe ne io=0x300 irq=10 You can skip the IRQ parameter, but if you know what it is then it makes things a little more bullet-proof. If you don't know what IO address the card is using, the Windows Device Manager (under System in Control Panels) will probably tell you. If the card is a bona-fide ISA/PNP card (as opposed to a traditional ISA card) then this will fail after a cold boot, and you will need to set the card up using isapnp before you can use it under Linux. The way modules are handled changed a couple of times in older (pre-2.1) Debian releases; you should check if the following files exist: /etc/modules.conf /etc/conf.modules /etc/modutils/ (a directory) /etc/modules This won't get you "on the network", but it will tell you what you need to go further. Get back to us when you've tried this and let us know what Debian release you're using, and you should get some better-targeted help. John P. -- [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.mdt.net.au/~john Debian Linux admin & support:technical services
Re: network/ethernet card configuration problem?
James Polson wrote: > > ...problems connecting with the ethernet card in my computer. > > The symptoms are: > > (1) ..."network is unreachable" ... > > (2) ..."ifconfig -a", ..."eth0", ...not there. > > ... > > Information about my system: > > (1) I have a D-Link DE 220 card. > > (2) I have the NC2000 driver in /lib/modules/2.0.36/net > This is the appropriate driver for the card, according >to the D-Link website. > > I would really appreciate it if anyone could help me with > this problem. Until it's fixed, I have to rely on Windows 95 > :( to connect to the internet. Let's see: does it look like the driver module is being loaded? Use `dmesg | more` to find out. If so, are you using a static IP, and have an entry in /etc/network/interface, such as iface eth0 inet static address LL.MM.NN.OO netmask 255.255.255.0 network LL.MM.NN.0 broadcast LL.MM.NN.255 gateway LL.MM.NN.PP ? > > Thanks, > > James Polson > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null -- [EMAIL PROTECTED] 972-729-5387 [EMAIL PROTECTED] (home phone on request) http://www.koyote.com/users/bolan RE: xmailtool http://www.koyote.com/users/bolan/xmailtool/index.html I am the "ILOVEGNU" signature virus. Just copy me to your signature. This email was infected under the terms of the GNU General Public License.
Re: network/ethernet card configuration problem?
James Polson wrote: > > Hi, > > I'm completely new to Linux, so the solution to my problem > may be trivial to all of you experienced Debian Linux users > (so I hope!). > > I'm trying to install Debian Linux (mostly with success), but > I think that I'm having problems connecting with the ethernet > card in my computer. > > The symptoms are: > > (1) A message during booting that is something like "network is > unreachable" (I don't know what log file to look for to get the > exact wording). > > (2) When I type "ifconfig -a", I should see listings for two > interfaces, "lo" and "eth0", but the second one (the ethernet > one) is not there. > > (3) Not surprisingly, telnet, ftp, etc. can't be used. > > (4) In the /var/log/syslog file, there is a message: > > cardmgr[189]: starting, version is 3.0.5 > cardmgr[189]: no sockets found! > cardmgr[189]: exiting > > I think that this problem reported is related. > > Information about my system: > > (1) I have a D-Link DE 220 card. > > (2) I have the NC2000 driver in /lib/modules/2.0.36/net > This is the appropriate driver for the card, according >to the D-Link website. > > I would really appreciate it if anyone could help me with > this problem. Until it's fixed, I have to rely on Windows 95 > :( to connect to the internet. > You need to configure eth0 and your cards kernel module (driver). >From Ethernet-HOWTO may find correct settings for the module. Then you have to put these setting to a file to /etc/modutils/ and run update-modules. You need to configure eth0 before. I am not an expert here, but configuration depends much on what you are trying to do. (For my cable modem I had to just install a debian package dhcpcd. If you are connecting to LAN or something, that's different.) Take a good look to Linux Networking-HOWTO (aka NET3-HOWTO): http://www.linux.com/howto/NET3-4-HOWTO.html Probably you can find this HOWTO from you Linux machine's /usr/doc/HOWTO directory too. NOTE: If you are completely new to Linux you should consider purhasing a good book, something like "Running Linux" from O'Reilly. Also read HOWTOs. WYSINWYG - What You See Is Never What You Get Esko Lehtonen esko dot lehtonen (a) pp dot htv dot fi
