On Sun, 25 Feb 2001, Peter Jay Salzman wrote:
>james, the tulip driver is problematic.
>
>we've had cards at our installfests that required the tulip.c driver from
>the 2.4.* kernels.
Also look at Donald Becker's company's site (Becker wrote most of the
linux networking software)
http://www.scyl
Many thanks to all who responded; I got the new kernel compiled
and installed with the FA-310TX specific driver, and it's now up
and running.
I look forward to having an easy-to-maintain system... ;^)
best,
Jim Wiggs
On Sun, 25 Feb 2001, Peter Jay Salzman wrote:
> hi james,
>
> yes, th
also sprach Peter Jay Salzman (on Sun, 25 Feb 2001 07:02:06PM -0800):
> as far as debian goes, i can understand your frustration. however, i'll
> tell you this much. i've used redhat, suse and debian extensively. when it
> comes to:
>
> updating your system
> recovering from a Reall
hi james,
yes, the most commonly used pci drivers are the 3com vortex/boomerang,
the dec tulip and the intel etherexpress pro 100.
the problem is that there's a register on these cards, the general purpose
register (CSR12) which are programmable by the vendor. they all do it a
bit differently.
as86 is part of package bin86
Pascal
[EMAIL PROTECTED]
On Sunday 25 February 2001 20:40, James K. Wiggs wrote:
> Peter,
>
>Thanks for the info. I find it sort of astonishing that there
> are problems with the tulip driver. This has to be probably the
> most commonly used driver other than
Peter,
Thanks for the info. I find it sort of astonishing that there
are problems with the tulip driver. This has to be probably the
most commonly used driver other than the ne2k. I've been using
these NetGear cards in most of my boxes for about three years and
never had *any* problems wit
Nope, it's a PCI card. It's getting configured at IRQ 9, and
looking at /proc/pci and /proc/interrupts it's clear there are no
IRQ conflicts.
On Sun, 25 Feb 2001, MaD dUCK wrote:
> it doesn't happen to be an ISA card, does it? i.e. do you have to
> worry about IRQ's ? if so, you need to comp
also sprach Peter Jay Salzman (on Sun, 25 Feb 2001 05:49:01PM -0800):
> On Sun 25 Feb 01, 8:43 PM, MaD dUCK said:
> > it doesn't happen to be an ISA card, does it? i.e. do you have to
> > worry about IRQ's ? if so, you need to compile a module
> huh?? why??
> why not pass a kernel argument to s
On Sun 25 Feb 01, 8:43 PM, MaD dUCK said:
> it doesn't happen to be an ISA card, does it? i.e. do you have to
> worry about IRQ's ? if so, you need to compile a module
huh?? why??
why not pass a kernel argument to set up the IRQ? you can do that with the
append directive with lilo.
> or hac
it doesn't happen to be an ISA card, does it? i.e. do you have to
worry about IRQ's ? if so, you need to compile a module or hack the
kernel sources.
martin
[greetings from the heart of the sun]# echo [EMAIL PROTECTED]:1:[EMAIL
PROTECTED]@@@.net
--
windows nt crashed.
i am the blue screen of de
james, the tulip driver is problematic.
we've had cards at our installfests that required the tulip.c driver from
the 2.4.* kernels.
can you ping the card's IP?
what does /var/log/messages say?
why don't you recompile the kernel and turn off Lite-On 82c168 PNIC.
compile it as a module or somethi
Folks,
I'm finding it impossible to get networking functional on the
box I've just installed 2.2r2 on. This is not an exotic setup, and
I've successfully installed several other distros on it at one time
or another, but the Debian install has been a complete wash.
Why does my NetGear FA-
12 matches
Mail list logo
