After installing 9.1, I see that the nic is recognized durring bootup, but
don't see where it is initalized and I have no network conectivity. Where
do I start in trouble shooting this. I know the card and cabling to the
switch are good, as they were working with the 9.0 Version prior to the
fresh install.

thanks.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Feb 16, 2004 at 02:59:25PM PST, Sport wrote
in article <hXbYb.97859$IF6.2796146@ursa-nb00s0.nbnet.nb.ca>:

> After installing 9.1, I see that the nic is recognized durring bootup, but
> don't see where it is initalized and I have no network conectivity. Where
> do I start in trouble shooting this. I know the card and cabling to the
> switch are good, as they were working with the 9.0 Version prior to the
> fresh install.

run `netconfig`


Jurgen.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAMUyT1ucXIiwNwbURAhEwAJ0UQhDfSXbqPbqaShxuRn m7V4WgTQCgm84H
thKDZHkYWw6z7gOaMngHc0Y=
=KM64
-----END PGP SIGNATURE-----

I have done this, and it does not change the situation.

"Jurgen Philippaerts" <jurgen@see.my.pgp.key> wrote in message
news:20040216230501.GA4669@anubis.is.traumatized.o rg...
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Mon, Feb 16, 2004 at 02:59:25PM PST, Sport wrote
> in article <hXbYb.97859$IF6.2796146@ursa-nb00s0.nbnet.nb.ca>:
>
> > After installing 9.1, I see that the nic is recognized durring bootup,
but
> > don't see where it is initalized and I have no network conectivity.
Where
> > do I start in trouble shooting this. I know the card and cabling to the
> > switch are good, as they were working with the 9.0 Version prior to the
> > fresh install.
>
> run `netconfig`
>
>
> Jurgen.
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.2 (GNU/Linux)
>
> iD8DBQFAMUyT1ucXIiwNwbURAhEwAJ0UQhDfSXbqPbqaShxuRn m7V4WgTQCgm84H
> thKDZHkYWw6z7gOaMngHc0Y=
> =KM64
> -----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Feb 16, 2004 at 03:13:57PM PST, Sport wrote
in article <V8cYb.97876$IF6.2796798@ursa-nb00s0.nbnet.nb.ca>:

> I have done this, and it does not change the situation.


> > > don't see where it is initalized and I have no network conectivity.
> Where
> > > do I start in trouble shooting this. I know the card and cabling to the

> > run `netconfig`

what NIC do you have ?
what driver is being used ?
what did you configure using netconfig ? static ? dhcp ?
what is the output of `ifconfig eth0`
what is the output of `netstat -rn`

don't keep us guessing, supply information we can work with.

ps: try not to top-post.


Jurgen.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAMVEO1ucXIiwNwbURAvg4AKDrhmSJ12gW67wAyPsZWt lcLqYr4gCg0MK/
NzNuheoI+5pUb9phLa7LX8M=
=4seZ
-----END PGP SIGNATURE-----

- 3com 3c509b
- not sure where to get the driver info
- using the netconfig, set the host and domain name, and dhcp.
- I did a modprobe 3c509, and the nic is up and working. If I reboot things
are down again.


"Sport" <sport9155@hotmail.com> wrote in message
news:hXbYb.97859$IF6.2796146@ursa-nb00s0.nbnet.nb.ca...
> After installing 9.1, I see that the nic is recognized durring bootup, but
> don't see where it is initalized and I have no network conectivity. Where
> do I start in trouble shooting this. I know the card and cabling to the
> switch are good, as they were working with the 9.0 Version prior to the
> fresh install.
>
> thanks.
>
>

On Mon, 16 Feb 2004 23:55:40 +0000, Sport wrote:

[ Stop top-posting, it's annoying! ]

> - 3com 3c509b
> - not sure where to get the driver info

dmesg

> - using the netconfig, set the host and domain name, and dhcp.
> - I did a modprobe 3c509, and the nic is up and working. If I reboot things
> are down again.

Make the appropriate lines in /etc/rc.d/rc.modules look like this:

# 3com 3c509 and 3c579:
/sbin/modprobe 3c509

--
-Menno.

"Menno Duursma" <menno@desktop.lan> wrote in message
newsan.2004.02.16.23.47.21.929307@desktop.lan...
> On Mon, 16 Feb 2004 23:55:40 +0000, Sport wrote:
>
> [ Stop top-posting, it's annoying! ]
>
> > - 3com 3c509b
> > - not sure where to get the driver info
>
> dmesg
>
> > - using the netconfig, set the host and domain name, and dhcp.
> > - I did a modprobe 3c509, and the nic is up and working. If I reboot
things
> > are down again.
>
> Make the appropriate lines in /etc/rc.d/rc.modules look like this:
>
> # 3com 3c509 and 3c579:
> /sbin/modprobe 3c509
>
> --
> -Menno.
>

This worked. Strange that the setup prob didn't configure this at install.

Thanks

On Tue, 17 Feb 2004 00:36:17 +0000, Sport wrote:
> "Menno Duursma" <menno@desktop.lan> wrote in message
>> On Mon, 16 Feb 2004 23:55:40 +0000, Sport wrote:
....
>> > - I did a modprobe 3c509, and the nic is up and working. If I reboot
> things
>> > are down again.
>>
>> Make the appropriate lines in /etc/rc.d/rc.modules look like this:
>>
>> # 3com 3c509 and 3c579:
>> /sbin/modprobe 3c509

> This worked.

Nice.

> Strange that the setup prob didn't configure this at install.

Hmn, dunno why that is, i'd expected it to find that one.

> Thanks

Thank Jurgen instead / two .
(You posted relevant info on his advice not mine)...

--
-Menno.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2004-02-17, Sport <sport9155@hotmail.com> wrote:
>
>> On Mon, 16 Feb 2004 23:55:40 +0000, Sport wrote:
>> > - 3com 3c509b
>
> This worked. Strange that the setup prob didn't configure this at install.

IIRC the 3c509 is an ISA card; ISA cards aren't usually probed, as doing
so allegedly causes problems and/or doesn't work correctly. So in
Slackware, at least, it's up to the admin to uncomment the appropriate
line in rc.modules; for PCI cards I believe rc.netdevice is usually
configured correctly.

- --keith

- --
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://wombat.san-francisco.ca.us/cgi-bin/fom

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAMZZ6hVcNCxZ5ID8RAr2hAKCWzAJnHg5bq20JATx6Vv kLsTv7tgCgnftV
hjfTgOyH/2Sv2DUzhENDdbg=
=AE92
-----END PGP SIGNATURE-----

"Keith Keller" <kkeller-usenet@wombat.san-francisco.ca.us> wrote in message
news:sp4s0c.bhn.ln@goaway.wombat.san-francisco.ca.us...
> On 2004-02-17, Sport <sport9155@hotmail.com> wrote:
> IIRC the 3c509 is an ISA card; ISA cards aren't usually probed, as doing
> so allegedly causes problems and/or doesn't work correctly. So in
> Slackware, at least, it's up to the admin to uncomment the appropriate
> line in rc.modules; for PCI cards I believe rc.netdevice is usually
> configured correctly.
>
> - --keith

I found a gotcha here - The probing turned up only eth1, an
ADMtek Comet rev 17, (tulip) and stopped probing, so it didn't
get the builtin sis900.
So I copied
#/sbin/modprobe sis900
from rc.modules, and left it commented out in rc.modules,
and my rc.netdevice looks like this:
/sbin/modprobe sis900
/sbin/modprobe tulip

I kinda logicked that it would assign the first one to eth0,
and so on. I added the sis900 to rc.netdevice rather than
putting them both into rc.modules because, well, the automagical
thingie in setup put /sbin/modprobe tulip there, and rc.modules
executes it anyway. They're kind of grouped by function, that
way.

Now I'm wondering where's the best place to start dhcpd and
ip masquerading. Probably last, around when it starts sendmail.

Cheers!
Rich