Very Computer

I'm in need of some help for this problem.
I'm using a network device which seems to be using


doesn't seem to support building a custom kernel because the make program
just isn't there. So I installed the required software from the cd set to
support it.

After building a kernel that DOES support my ethernet adapter, the dhclient
thingy still can't configure my device for DHCP, probably because it can't
find it.

I don't have this problem with any other distro: I already went with RedHat,
Gentoo, SuSe.

I really need help

Hi Steven,

Quote:> After building a kernel that DOES support my ethernet adapter, the dhclient
> thingy still can't configure my device for DHCP, probably because it can't
> find it.

Did you set the "<*> packet socket" option in "networking options" while
configuring the kernel ? AFAIK this is needed for using the dhcp-client.

Joern

Steven Jacobs schrieb:

Quote:> After building a kernel that DOES support my ethernet adapter, the dhclient
> thingy still can't configure my device for DHCP, probably because it can't
> find it.

Which module do you use? RTL-8029 is supported in the n2k-pci module. Then set
up /etc/networking/interfaces and enable DHCP-Support in kernel.

auto eth0
iface eth0 inetd dhcp

janek

--
"Macht korrumpiert. Absolute Macht korrumpiert absolut."
  - Stefan Heym -

I guess it's a ISA device ?

I had the same problem today with a 8019 chipset. The solution was to
manually set the I/O-address and IRQ number with the jumpers on my device,
and disabling PnP. Then I used the 'ne' driver for network adapters and used
the manually configured I/O and IRQ as input parameters. That worked for me.
Ofcourse you have to select an I/O and IRQ that are not used by other
devices.

Ronni

AFAIK no distro's include networking support compiled "into" the kernel,
then do however supply a full set of kernel modules to support most all
network cards.
The 8029 is "NE compatable".

Your card like mine uses the ne2k-pci driver, so to load your driver you
would need the following in /etc/modules.conf

alias eth0 ne2k-pci

A simple command as;

modprobe ne2k-pci

Should load the module, the command 'ifconfig -a' should now show some
info on eth0 even tho it is not initialised, you should now be able to
issue the command, 'dhcpcd &' and get a lease providing your cable is
properly connected and you have payed your isp's bill.

Someone else said in another mail;

I guess it's a ISA device ?

It is not its a PCI device, you do not need to give params to modprobe or
insmod to tell it where to find a PCI card.

The 8019 = ISA driver "ne"
         8029 = PCI driver "ne2k-pci"
         8139 = PCI driver "8139too" used to be rtl8139 now depricated.

See http://www.scyld.com/networking
 for full details.

Quote:

> After building a kernel that DOES support my ethernet adapter, the
> dhclient thingy still can't configure my device for DHCP, probably
> because it can't find it.

Mentioned the possable need for "socket packet" in your kernel, if i
recall correctly it is not used by dhcp(cd), however it is good advise to
have it either compiled into your kernel or compiled as a module as many
networking programs use it to communicate with your network card itself.

I would if i were you use your distribution installed kernel when trying
to get your card to work, it will save you a lot of time i can assure
you.

Quote:

> I don't have this problem with any other distro: I already went with
> RedHat, Gentoo, SuSe.

I do not use debian myself, i do however have a friend who does, he has
an old 8029 card i gave him and it worked no problem on his machine.

Quote:

> I really need help

I hope i have not missed anything out, if so give me a shout.

--
Regards Richard

http://people.zeelandnet.nl/pa3gcu/

ACK.

Quote:> I would if i were you use your distribution installed kernel when trying
> to get your card to work, it will save you a lot of time i can assure
> you.

Of course, it is always simpler with distro-supplied default kernels.

Quote:

> > I don't have this problem with any other distro: I already went with
> > RedHat, Gentoo, SuSe.

Yes, for ex. SuSE don't compile neither server nor client
against packet socket. I recently noticed this, too.

Quote:> I do not use debian myself, i do however have a friend who does, he has
> an old 8029 card i gave him and it worked no problem on his machine.

Yep, the NIC driver module itself has been around for years.
As configuring for a _static_ IP doesn't necessarily need the
packet socket (in Debian, that is), this will work even with
a custom kernel without that particular option.

Alternatively, (if you don't want to reinstall your distro's
default kernel, nor recompile a custom one) you might as
well use "pump" as a dhcp-client. Works fine for me in Woody
with a custom kernel without packet socket driver...

Juergen