From: "Jamie" <darkshad@home.com>
To: "EricMarts" <martser@turtle.mine.nu>
Cc: "Jeff Garzik" <jgarzik@mandrakesoft.com>,
<becker@webserv.gsfc.nasa.gov>, <jam@McQuil.com>,
<hendriks@lanl.gov>, <jgolds@resilience.com>,
<sdegler@degler.net>, <tulip-users@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>,
"Anders Hedborg" <ahe@systemkoreograferna.com>
Subject: Tulip Drivers Problem in 2.4.xx Kernel
Date: Tue, 6 Nov 2001 14:12:15 -0500 [thread overview]
Message-ID: <002001c166f6$f3396f20$0300a8c0@theburbs.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111061043240.4321-100000@turtle.mine.nu>
To get it to work on Slackware 8 I had to go to the website he listed bellow
and download the drivers and use the stable drivers from the website he
listed bellow it was the only way to get it to work.
Jamie
----- Original Message -----
From: "EricMarts" <martser@turtle.mine.nu>
To: "Jamie" <darkshad@home.com>
Cc: "Jeff Garzik" <jgarzik@mandrakesoft.com>;
<becker@webserv.gsfc.nasa.gov>; <jam@McQuil.com>; <hendriks@lanl.gov>;
<jgolds@resilience.com>; <sdegler@degler.net>;
<tulip-users@lists.sourceforge.net>; <linux-kernel@vger.kernel.org>; "Anders
Hedborg" <ahe@systemkoreograferna.com>
Sent: Tuesday, November 06, 2001 11:50 AM
Subject: Re: Tulip Drivers Problem in 2.4.xx Kernel
All,
Donald Becker had given be some pointers.
I had problems on Windows 95 as well.
Here is what I came up with ... in terms of the system.
The old HP Pavalion uses a Intel motherboard and the
Intel bios (with HP logo etc..)
The PCI is only 2.0? compliant and the card is meant for
2.1 systems..
The on board sounnd and graphics was a pain. Not a like I could
just pull out the graphics or sound PCI card to free up
resources.
Windows wanted to use PCI Steering -- I couldn't get it turned
off (IRQ sharing with the onboard video card..)
Long story short....
I was able to through a Netgear ISA card in assign the IRQ iomem
address via the DOS config tool (writes EEPROM?), and cfdisk, and install
RH 7.0
Does the PCI 2.0 - PCI 2.1 make a difference.
Do I have a chance here to get PCI card up and running?
Thanks,
Eric
On Mon, 5 Nov 2001, Jamie wrote:
> Ok Jeff thanks I will definately give that a try I have never tried the
> dec4x5 drivers I will see if it works
> for my NIC.
>
> Thanks,
>
> Jamie
>
> ----- Original Message -----
> From: "Jeff Garzik" <jgarzik@mandrakesoft.com>
> To: "Jamie" <darkshad@home.com>
> Cc: <becker@webserv.gsfc.nasa.gov>; <jam@McQuil.com>; <hendriks@lanl.gov>;
> <jgolds@resilience.com>; <sdegler@degler.net>;
> <tulip-users@lists.sourceforge.net>; <linux-kernel@vger.kernel.org>;
"Anders
> Hedborg" <ahe@systemkoreograferna.com>
> Sent: Monday, November 05, 2001 7:07 PM
> Subject: Re: Tulip Drivers Problem in 2.4.xx Kernel
>
>
> Currently there is a bug in 2.4.x-current tulip drivers that prevents
> 21041 from initializing correctly. Until then you can use the 'de4x5'
> driver or download the latest stable version on the tulip web page:
> http://sourceforge.net/projects/tulip/
> --
> Jeff Garzik | Only so many songs can be sung
> Building 1024 | with two lips, two lungs, and one tongue.
> MandrakeSoft | - nomeansno
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
> _______________________________________________
> Tulip-users mailing list
> Tulip-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tulip-users
>
next prev parent reply other threads:[~2001-11-06 19:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-05 23:56 Tulip Drivers Problem in 2.4.xx Kernel Jamie
2001-11-06 0:07 ` Jeff Garzik
2001-11-06 1:29 ` Jamie
2001-11-06 16:50 ` EricMarts
2001-11-06 19:12 ` Jamie [this message]
2001-11-06 19:17 ` EricMarts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002001c166f6$f3396f20$0300a8c0@theburbs.com' \
--to=darkshad@home.com \
--cc=ahe@systemkoreograferna.com \
--cc=becker@webserv.gsfc.nasa.gov \
--cc=hendriks@lanl.gov \
--cc=jam@McQuil.com \
--cc=jgarzik@mandrakesoft.com \
--cc=jgolds@resilience.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martser@turtle.mine.nu \
--cc=sdegler@degler.net \
--cc=tulip-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.