Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!spool.mu.edu!news.sol.net!newspump.sol.net!uniserve!n2van.istar!van.istar!ott.istar!istar.net!winternet.com!nntp.primenet.com!news.cais.net!bofh.dot!news.mathworks.com!tank.news.pipex.net!pipex!dispatch.news.demon.net!demon!awfulhak.demon.co.uk!awfulhak.demon.co.uk!not-for-mail
From: brian@awfulhak.demon.co.uk (Brian Somers)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: learning freebsd...
Date: 1 Jun 1996 00:22:31 +0100
Organization: Coverform Ltd.
Lines: 34
Message-ID: <4onuvn$lt@anorak.coverform.lan>
References: <31A4F111.3AD@ahoynet.com> <31A6ACD6.696F@www.play-hookey.com>
NNTP-Posting-Host: anorak.coverform.lan
X-NNTP-Posting-Host: awfulhak.demon.co.uk
X-Newsreader: TIN [version 1.2 PL2]
Ken Bigelow (kbigelow@www.play-hookey.com) wrote:
: kevin graham wrote:
: > on another note, i also have had no luck getting the ethernet card
: > clicking... its setup at 300h/irq10 both phyically and in the os, with
: > (a presumable) ip address of 192.168.0.1 ... no luck at all on pinging
: > into or out of the thing.... once again... could someone spin me towards
: > the right corner?
: > I'd need more info on what you're trying to access it with; the whole
: network can affect this. For example, is your ethernet cable properly
: terminated at both ends?
Does the kernel probe it correctly ? You should see something like
ed0: at 0x300-0x31f irq 10 maddr 0xcc000 msize 16384 on isa
ed0: address xx:xx:xx:xx:xx:xx, type SMC8216/SMC8216C (16 bit)
when you run dmesg. If this is the case, have you run ifconfig ? This
is usually run at system boot time and is configured in the /etc/sysconfig
file. Try typing 'ifconfig -a'. You should see something like
ed0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 10.0.1.1 netmask 0xffffff00 broadcast 10.0.1.255
The 'ed0' bit varies depending on the network card's device driver in both
cases. If you don't see the first message from 'dmesg', the card/kernel
aren't configured correctly. If you don't see the second, your interface
isn't configured correctly. If you do see both, your ping machine isn't
working correctly.
Good luck....
--
Brian <brian@awfulhak.demon.co.uk>
Don't _EVER_ lose your sense of humour....