On Mon, Mar 22, 2004 at 10:28:24PM -0800, Paul Johnson wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> [EMAIL PROTECTED] writes:
> > The current distribution has four tulip drivers named tulip,
> > old_tulip, ng_tulip, and tulip_scyld. Can anyone provide
> > information on the differ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
> The current distribution has four tulip drivers named tulip,
> old_tulip, ng_tulip, and tulip_scyld. Can anyone provide
> information on the differences that characterize these drivers?
1. RTFM. The Linux Kernel documenta
The current distribution has four tulip drivers named tulip, old_tulip, ng_tulip, and
tulip_scyld. Can anyone provide information on the differences that characterize
these drivers?
> Content-Type: text/plain
>
> debian-user-digest Digest Volume 2004 : Issue 973
>
>
When install kernel-image-2.6.*, apt don't make initrd.img automatically,you
should usr mkinitrd to build a initrd.img, and edit your lilo.conf if you use
lilo, or run 'update-grub' if you use grub
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
Brian Walker wrote:
Kent West wrote:
[initrd.img] should be in /boot. It should have been installed
automatically.
Indeed it is - many thank for the reference. But ls -l shows that
there is no symlink to the initrd.img. Should there be one? This is
where the apt-get called a problem, and see
for the tulip driver is
built-into the standard 2.4 kernels.
So, just "apt-get install kernel-image-2.4.24-686" (or whatever
kernel version you want -- "apt-cache search kernel-image-2.4" will
show you a list of available versions). After the reboot into the new
kernel, y
driver is
built-into the standard 2.4 kernels.
So, just "apt-get install kernel-image-2.4.24-686" (or whatever
kernel version you want -- "apt-cache search kernel-image-2.4" will
show you a list of available versions). After the reboot into the new
kernel, you may find that
Kent West wrote:
Robert Packer wrote:
I am a complete newbie to this and don't have a clue how to compile a
kernel(I'm reading up, but still...), so is it possible to make the
2.4 kernel work with a nic card that needs a tulip driver? It works
fine with the 2.2.20 kernel but if possibl
Robert Packer wrote:
I am a complete newbie to this and don't have a clue how to compile a
kernel(I'm reading up, but still...), so is it possible to make the
2.4 kernel work with a nic card that needs a tulip driver? It works
fine with the 2.2.20 kernel but if possible I'd like to
I am a complete newbie to this and don't have a clue how to compile a
kernel(I'm reading up, but still...), so is it possible to make the
2.4 kernel work with a nic card that needs a tulip driver? It works
fine with the 2.2.20 kernel but if possible I'd like to use the latest
kerne
hey, just another idea for ya, have you tried using the bf24 series
boot floppies? they're based on a different kernel alltogether.
sean
msg18559/pgp0.pgp
Description: PGP signature
, otherwise i spose i could just
install woody w/o network support, and burn a copy of
the latest kernel on cd, mount it and upgrade the
kernel and hope that works. Just think its odd that
this is the only time ive ever had problems with the
tulip driver.
--- Todd Collins <[EMAIL PROTECTED]> wrote:
&g
dudahhh said:
> Secondly, when i ran potato, i always updated the
> kernel to 2.4.18, and ive never had any problems.
>
> So, ive determined theres just something wrong with
> that tulip driver with woody, i do see there is an
> updated one at ftp://ftp.scyld.com/pub/network/tul
have a LNE100TX Linksys card, which states uses the
Tulip driver, and it has used it on potato, and also
when ive played with rh, slack, and mandrake
After searching around i found out the tulip version
from potato is to be tulip.c:v0.89K.1 3/16/99, and
that woody comes bundeled with 0.9.15
Is there
running Virtual PC under MacOS 9. My Debian install under that uses
the same Tulip driver with the same chipset. However, it is showing up
as PCI based (Not ISA PNP, which it sounds like you are). The driver
autodetects it as IRQ 11, and it works fine.
--
Debian - http://www.debian.org/
Li
Hello
I am trying to run Potato on my Win98se machine
using Connectix Virtual PC and everything is working even X with one major
exception. My network connection is not.
Virtual PC uses emulated hardware.
s3 trio 32/64 4m video
sb16 sound
DEC 21041 network card (supposedly at IRQ 1
but con
kage?
From: dman <[EMAIL PROTECTED]>
To: debian-user@lists.debian.org
Subject: Re: tulip driver woes
Date: Sat, 30 Mar 2002 00:21:54 -0600
On Fri, Mar 29, 2002 at 10:04:06PM -0800, Kapil Khosla wrote:
| Hi,
| I have a DEC 21145 which uses a tulip driver, I do install via the
| net and a
On Fri, Mar 29, 2002 at 10:04:06PM -0800, Kapil Khosla wrote:
| Hi,
| I have a DEC 21145 which uses a tulip driver, I do install via the
| net and am having problems with the driver/card.
|
| When I configure the driver modules, it says INSTALLATION SUCCEEDED
| , but when I configure the network
Hi,
I have a DEC 21145 which uses a tulip driver, I do install via the net and am
having problems with the driver/card.
When I configure the driver modules, it says INSTALLATION SUCCEEDED , but when
I configure the network, it fails to detect my DHCP connection.
DO you know how to solve the
I checked again this morning and I have a Accton
EN2242 NIC card.. So I asume that I still use the
tulip.o driver.
Thanks for the response.
Don
--- David Raleigh Arnold <[EMAIL PROTECTED]> wrote:
> Just in case my former got lost in the sauce, if you
> have a
> netgear card, your driver is prob
Just in case my former got lost in the sauce, if you have a
netgear card, your driver is probably ng_tulip rather than
tulip.
Information is not knowledge. Belief is not truth.
Indoctrination is not teaching. Tradition is not
Guess what? If you have a netgear card, you probably want a ng_tulip
driver instead of a tulip driver. I just found this out when I compiled
a new kernel. Don't be mad, I didn't know either. :-)
--
||/ Peace, understanding, health and happiness to all beings! ||
|-K ars sine scie
those and still nothing. At this point I
was really frustrated and figured I'd go about this
from a different perspective. I installed a Distro
(Mandrake 8.0) that I knew that the tulip driver
worked in and was going to try and load Debian, but
leave the pcmcia stuff.. I'm not sure if I can
I did a lsmod and it was not listed so I assumed that
it was not installed... So I did not set it up. I'll
chceck it out.
--- David Raleigh Arnold <[EMAIL PROTECTED]> wrote:
> I get tons every time I boot up, but it works fine.
> Does yours work?
>
>
-
I get tons every time I boot up, but it works fine. Does yours work?
Information is not knowledge. Belief is not truth.
Indoctrination is not teaching. Tradition is not evidence.
David Raleigh Arnold [EMAIL PROTE
Hi all
I have installed Potato 2.2.r2 on my HP Pavilion
N5450 Laptop and this system uses a Accton en2242 nic
card that uses the tulip driver. I know that I've
seen this discussed on this list but I am unable to
find it. I have downloaded the drivers for the card
and did a cp pci-s
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
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
te
On Sun 25 Feb 01, 6:40 PM, James K. Wiggs said:
>
> 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
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 dr
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* pro
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
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-
I have two versions of the LRP built (OK one is
actually coyote linux, but based on LRP and debian).
One is using a 2.0.36 kernel, the other 2.2.14. The
led's on the tulip nic's (dec 21041 chips) light and
flash under the 2.0 kernel, but are dark under the 2.2
kernel. However, both systems run O
you share with me how you got
> it running?
>
> I am running 2.0.30 on a ppro 200.
>
> Thanks in advance!
>
> -Ian
Try the latest tulip driver from:
http://cesdis.gsfc.nasa.gov/linux/drivers/tulip.html
I have found that it works significantly better than the one in the
>I am having no luck getting a new ethernet card up. I just installed a
>new card with a DEC "tulip" chip and I can't get it working. Does anyone
>have a "tulip" card working? If so, could you share with me how you got
>it running?
compile the tulip dri
Hi-
I am having no luck getting a new ethernet card up. I just installed a
new card with a DEC "tulip" chip and I can't get it working. Does anyone
have a "tulip" card working? If so, could you share with me how you got
it running?
I am running 2.0.30 on a ppro 200.
Thanks in advance!
-Ian
42 matches
Mail list logo
