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-pci 4136 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
