Why is it that everytime I compile the kernel I end up with no NIC? I
have only taken out the ones I know for a fact won't work with my
card. Like HP PCLAN, AMD PCNET, etc. However, I've left support for
90% of the cards out there. It was working fine before I recompiled.

I'm recompiling again now with support for every card chosen. We will
see what happens. It is compiled into the kernel, not a module.

This is Slack 10 on a older 350mhz machine.

Any ideas.

Thanks

Note: without taking the casae off, I can't remember the eact card,
but the NEC or Ether Express used to work fine for it.

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

In alt.os.linux.slackware, John Q dared to utter,
> Why is it that everytime I compile the kernel I end up with no NIC?

Because you don't include support for it somehow. Perhaps you left it
as a module and forgot to make the modules?

> I
> have only taken out the ones I know for a fact won't work with my
> card.

Well instead of that, why don't you find out which one is used by your
card and only include that one? Just run lsmod on a working kernel and
see what modules are being used. Shouldn't be too hard to deduce which
one is your NIC by rmmod'ing them one at a time. :-)

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCoefhvgVcFKpJf4gRAuJ/AKCAUJHunwiSmkgiqSJ6Win0j7BgpgCg1wnJ
mbDUg3Kv147vjGLCEvWccR0=
=jF8F
-----END PGP SIGNATURE-----

John Q <john@q.com> wrote:
> I'm recompiling again now with support for every card chosen. We will
> see what happens. It is compiled into the kernel, not a module.

You cannot get a working kernel with ALL network cards built-in, some
of them are mutually INcompatible. You have to make them into modules
or just include "the one you're using" inside the kernel.
--
************************************************** ******************
** Eef Hartman, Delft University of Technology, dept. EWI/TW **
** e-mail: E.J.M.Hartman@math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
************************************************** ******************

On Sat, 04 Jun 2005 19:50:35 +0200, Eef Hartman <E.J.M.Hartman@math.tudelft.nl> wrote:

> John Q <john@q.com> wrote:
> > I'm recompiling again now with support for every card chosen. We will
> > see what happens. It is compiled into the kernel, not a module.
>
> You cannot get a working kernel with ALL network cards built-in, some
> of them are mutually INcompatible. You have to make them into modules
> or just include "the one you're using" inside the kernel.

Seconded, I only compile in NICs on mobo, modular for removable or
multiple NICs, due to detection order issues, for one, plus some
things work better as modules.

--Grant.

On Sat, 04 Jun 2005 12:31:28 -0400, John Q <john@q.com> wrote:

>Why is it that everytime I compile the kernel I end up with no NIC? I
>have only taken out the ones I know for a fact won't work with my
>card. Like HP PCLAN, AMD PCNET, etc. However, I've left support for
>90% of the cards out there. It was working fine before I recompiled.
>
>I'm recompiling again now with support for every card chosen. We will
>see what happens. It is compiled into the kernel, not a module.
>
>This is Slack 10 on a older 350mhz machine.
>
>Any ideas.
>
>Thanks
>
>Note: without taking the casae off, I can't remember the eact card,
>but the NEC or Ether Express used to work fine for it.


Followup. Here's what I did the third time around. I left the section
for NIC cards as it was when I installed Slack, and only took out
other sections, i.e. firewire, pcmcia, etc, etc. After compiling,
still no NIC - or sound card now for that matter. On my old 166 box I
never had this problem.

Thanks for any input.

Oh, by the way, it is a Dlink DFE 530TX NIC.

On Tue, 07 Jun 2005 20:43:20 -0400, John Q wrote:

> Oh, by the way, it is a Dlink DFE 530TX NIC.

if im not mistaking, that is not a single nic. it has like, a billion
revisions. i have one, tried it, no workie, had a 3com lying around, and
no time to waste. probably will try it again around 2.6.18

On Tue, 07 Jun 2005 20:43:20 -0400, John Q <john@q.com> wrote:
>
Which kernel?
>
> Oh, by the way, it is a Dlink DFE 530TX NIC.

May not mean anything to kernel, what does lspci call NIC?

Plus there is a seriously important networking section to get
right too. Read <Help> for each doubtful option and pick the
'if unsure, say Y|N' option.

In general, removable cards should have their drivers compiled
as modules. I can point you at some canned configs, but take
them with a grain of salt, each optimised for particular hardware,
may require startup script changes: http://scatter.mine.nu/test/

--Grant.

On Tue, 07 Jun 2005 20:43:20 -0400, John Q wrote:

> On Sat, 04 Jun 2005 12:31:28 -0400, John Q <john@q.com> wrote:
>
>>Why is it that everytime I compile the kernel I end up with no NIC? I
>>have only taken out the ones I know for a fact won't work with my
>>card. Like HP PCLAN, AMD PCNET, etc. However, I've left support for
>>90% of the cards out there. It was working fine before I recompiled.
>>
>>I'm recompiling again now with support for every card chosen. We will
>>see what happens. It is compiled into the kernel, not a module.
>>
>>This is Slack 10 on a older 350mhz machine.
>>
>>Any ideas.
>>
>>Thanks
>>
>>Note: without taking the casae off, I can't remember the eact card,
>>but the NEC or Ether Express used to work fine for it.
>
>
> Followup. Here's what I did the third time around. I left the section
> for NIC cards as it was when I installed Slack, and only took out
> other sections, i.e. firewire, pcmcia, etc, etc. After compiling,
> still no NIC - or sound card now for that matter. On my old 166 box I
> never had this problem.
>
> Thanks for any input.
>
> Oh, by the way, it is a Dlink DFE 530TX NIC.

Hello,
I also have a DLink DFE 530-TX and kernel 2.4.26. You should enable the
following options :
CONFIG_NET_PCI=y
CONFIG_VIA_RHINE=y
CONFIG_VIA_RHINE_MMIO=y

to see your card.

I suggest you deactivate all other drivers you don't need.

Success
Laurent

I recompiled again, following the how-to - and now I have my NIC, but
in the process I've lost my USB mouse and Sound. Upon searching for
this problem I found many, many others with the same problem - after
compiling, no NIC, no mouse, and no sound - this can't be a
conincidence - is there some issue going on here. Any help is
appreciated. Note that the sound modules are loading and as far as I
can tell everyting looks fine, but alsa says it can't find it. It's an
older SB 16 Vibra.

Any help is appreciated.

On Sat, 04 Jun 2005 12:31:28 -0400, John Q <john@q.com> wrote:

>Why is it that everytime I compile the kernel I end up with no NIC? I
>have only taken out the ones I know for a fact won't work with my
>card. Like HP PCLAN, AMD PCNET, etc. However, I've left support for
>90% of the cards out there. It was working fine before I recompiled.
>
>I'm recompiling again now with support for every card chosen. We will
>see what happens. It is compiled into the kernel, not a module.
>
>This is Slack 10 on a older 350mhz machine.
>
>Any ideas.
>
>Thanks
>
>Note: without taking the casae off, I can't remember the eact card,
>but the NEC or Ether Express used to work fine for it.

On 2005-06-19, John Q <john@q.com> wrote:

> I recompiled again, following the how-to - and now I have my NIC, but
> in the process I've lost my USB mouse and Sound. Upon searching for
> this problem I found many, many others with the same problem - after
> compiling, no NIC, no mouse, and no sound - this can't be a
> conincidence - is there some issue going on here. Any help is
> appreciated. Note that the sound modules are loading and as far as I
> can tell everyting looks fine, but alsa says it can't find it. It's an
> older SB 16 Vibra.
>
> Any help is appreciated.

Can't help much except to suggest you might want to check the following
sites for an answer....you might find something helpful

-- a very large collection of current mailing list achieves, there's a
kernel list there.

marc.theaimsgroups.com

--also maybe

www.kernel-traffic.org

or www.kernel.org (the change logs might provide some info)

ken