I had the same on a nforce4 mobo,
Turned out the kernel was compiled with firewire network support and
eth0 was my firewire interface

On 5/24/06, Gordon Gallup <[EMAIL PROTECTED]> wrote:
Greetings again,  Thanks to all who responded.  I will now tell the
rest of the story:  I would have no problem leaving the D-Link NIC in,
but the resulting system after compilation still does not like the
forcedeth, cannot seem to detect the D-Link as eth1, and, hence, does
not load its 'stge'  driver (produced for Linux by D-Link).  The
result---no network.  Has anyone seen this?
GAG


On 5/24/06, Neil Stone <[EMAIL PROTECTED]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Kirby Walborn wrote:
> > Adam James wrote:
> >
> >>> As far as I can remember, it worked fine for me with
> >>> `install-amd64-minimal-2006.0.iso'. I'm afraid I can't confirm this as
> >>> it died not so long ago.
> >>>
> >>> --Adam
> >
> > I will confirm that it worked fine for me on the minimal amd64 cd also.
> > --
> >
> > Kirby
>
> Worked for me, but that was a 2005.0 minimal CD...
>
> - --
> Neil Stone
>
> Systems Administrator
> FlashTek UK
>
> - -----BEGIN GEEK CODE BLOCK-----
> Version: 3.1
> GIT d+(++) s: a-(?) C++++(--) UL++++$ P+ L+++ E- W+++ N+
> o+ w--- O M PS+ Y+ PGP++ t+ 5+ X+ R+ tv+ b- DI++ D+++ G
> e h--- r+++ y++++(**)
> - -----END GEEK CODE BLOCK-----
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFEdLD4z3Av8JKgzxQRAh0GAJ9lCmMX1Wn57zioYjs+F24eCjGDGgCeJzCs
> u1sSk5QShfzXHWXBa+qu9JA=
> =JwSg
> -----END PGP SIGNATURE-----
> --
> [email protected] mailing list
>
>

--
[email protected] mailing list


--
[email protected] mailing list

Reply via email to