Re: Can't get network to work
From: Kent West (westk_at_acu.edu)
Date: 11/30/04
- Previous message: Rogério Brito: "Re: All mozilla-based browsers crash on some sites"
- In reply to: Michelle: "Can't get network to work"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 30 Nov 2004 07:44:40 -0600 To: debian-user@lists.debian.org
Michelle wrote:
> Problem:
> On a fresh install of Debian 3.0r3 Woody (2.2.20-idepci kernel) off the
> .iso from the server, the neworking doesn't work. I'm on an AMD Athlon
> with a 21140-based on-board ethernet chip (lspci and WinXP both say so)
<snip>
> SO I KNOW IT CAN WORK.
>
> HOWEVER, after booting, eth0 is only configured for a 192.168 address,
> NOT what the dhcp in my dsl modem should be giving it. I run ifup eth0
> and I get a series of "SIOCSIFADDR: No such device" errors. Ditto if I
> run dhclient directly.
<snip>
> Again, more research, and I am told to type, "modprobe tulip". Ok, now
> there is no error. (apparently, insprobe pci_scan and then insprobe
> tulip does the same thing)
>
> I type, "ifdown eth0" and then "ifup eth0", and nope, still the same
> SIOCSIFADDR errors.
>
> I added 'alias /dev/eth0 tulip' in the /etc/modutils/aliasas file and
> then ran update-modules. /etc/modules.conf has this entry. Reboot,
> and same problems.
>
> During boot, it appears to find the nework card just fine (tulip.o comes
> up, and lspci gives all the details about the card). Also, the
> SIOCSIFADDR messages are repeated there as the dhcp tries to come up.
> Then during modprobe in boot it says "Can't locate module eth0:0",
> with a bunch of IO types errors (all-caps).
>
For networking in Debian, you need to be concerned with four basic things:
1) Inserting the correct module - "modprobe tulip" should do this on a
boot-by-boot basis. Adding "tulip" to "/etc/modules" should allow the
system to handle this step automatically.
2) Your "/etc/network/interfaces" file needs to be correctly configured
for static/dhcp. "man interfaces" will give you more info; Ron's
suggestion is accurate for DHCP.
3a) If using dhcp, you need to install a dhcp client, such as "aptitude
install dhcp-client" or similar.
3b) If using static, you need to configure "/etc/resolv.conf".
4) [Re]start networking. "/etc/init.d/networking restart".
As I've never had to add anything to "/etc/modutils/aliases" for a first
ethernet card (and am not quite familiar with it), I'd first try
removing that entry you made and then add "tulip" to "/etc/modules" and
then reboot.
-- Kent -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
- Previous message: Rogério Brito: "Re: All mozilla-based browsers crash on some sites"
- In reply to: Michelle: "Can't get network to work"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
