The de4x5 module works. Gives funny message in dmesg but it does work.
Many thanks for all the help.
Patrick Kirk
On Thu, 28 Oct 1999, Patrick Kirk wrote:
: Hi guys,
:
: You may remember I lost my second NIC when I upgraded from 2.0.36 to 2.2.13.
: I asked for urls and set off to rtfm.
:
: Perhaps the problem is that I need to pass ether arguments via lilo along
: these lines:
:
: boot=/dev/hda1
[0x6301].
Does this look right?
Thanks in advance.
Patrick
- Original Message -
From: Patrick Kirk <[EMAIL PROTECTED]>
To:
Sent: Tuesday, October 26, 1999 12:34 PM
Subject: Can't get seconf NIC to work
> Hi all,
>
> Effortless is one word I wouldn't use to des
Only the first NIC is autodetected, for a second card, you need to add
a boot parameter (if compiled into the kernel) or a line in
/etc/conf.modules (if a compiled as a module). This is explained in
section 3.2 of the Ethernet-HOWTO (in Debian's doc-linux-text package or at
http://metalab.unc.edu/
Does anyone have a URL on how to get a second NIC to work under kernel 2.2.13?
The modules directory only has dummy.o in it. What is it I have missed? The
family are getting aggrieved that what was supposed tp be an upgrade seems to
have removed all net access for the PCs on the private IPs.
So how can I get the second NIC to work? This is getting urgent now as I
will have people using the system later.
Patrick
did u try to compile the NIC driver static into the kernel, i got 2
machines that use tulip(although on 2.0.36) and i try to avoid modules at
all costs. the only thing that get modularized for me are stuff thats 3rd
party and not included w/the kernel. if its a server, there are modules
out there
Hi all,
Effortless is one word I wouldn't use to describe the move to the 2.2
kernel. Can anyone suggest why lsmod shows nothing, why I can't load the
tulip module or what I need to do to add a route for 10.
Thanks in advance.
enterprise:~# cat /proc/modules
enterprise:~# route add -net 10.0.0.
8 matches
Mail list logo
