From: "Dead2" <dead2@circlestorm.org>
To: <linux-kernel@vger.kernel.org>, "Jeff Garzik" <jgarzik@mandrakesoft.com>
Subject: Re: Asus CUV-266-D vs Intel NIC (also MSI-6321)
Date: Thu, 25 Oct 2001 12:39:42 +0200 [thread overview]
Message-ID: <00e601c15d41$5ad32910$6ac0ecd5@dead2> (raw)
In-Reply-To: <Pine.LNX.4.33.0110241605020.12884-100000@oceanic.wsisiz.edu.pl> <20011025112752.A4795@suse.de> <007101c15d3a$c6ae90e0$6ac0ecd5@dead2> <009901c15d3e$71e96040$6ac0ecd5@dead2>
Ooopss...
I have to excuse my error.. I said I used the tulip driver, but I don't.
When I said 'tulip', i meant the 'eepro100' driver.
When I said 'intel', i meant the 'e100' driver
Sorry for any confusion..
-=Dead2=-
Jeff: 'de4x5' didn't work. Not so strange I guess.. =/
----- Original Message -----
From: "Dead2" <dead2@circlestorm.org>
To: <linux-kernel@vger.kernel.org>
Sent: 25 October, 2001 12:18 PM
Subject: Re: Asus CUV-266-D vs Intel NIC (also MSI-6321)
> Tested now with another motherboard with the same results.
>
> MSI 6321 Pro 1.0
>
> Both these motherboards use VIA dual-cpu chipsets.
>
> Same results with 2.4.13-Pre6 on both motherboards.
> I'm running out of ideas now..
>
> -=Dead2=-
>
> ----- Original Message -----
> From: "Dead2" <dead2@circlestorm.org>
> To: <linux-kernel@vger.kernel.org>
> Sent: 25 October, 2001 11:52 AM
> Subject: Asus CUV-266-D vs Intel NIC
>
>
> > I have an Asus CUV266-d motherboard, and want to use my Intel NIC's..
> >
> > 2.4.10 & 2.4.12 hangs while "Setting up routing"
> > No error messages appear.
> >
> > 2.4.x(4 maybe?) has both officail Intel drivers and the tulip drivers.
> > When loading the tulip, it hangs just like with todays kernels.
> > When loading the Intel driver, everything works just fine for a short
> > while..
> > 20-40seconds I guess.. Then the computer hangs.
> >
> > When not loading any NIC drivers, everything works just fine.
> >
> > The NIC's i've tried are named "Intel(R) PRO/100+ Dual Port Server
> Adapter"
> > Have also tried a "Intel(R) PRO/100+ Adapter"
> >
> > Any ideas of what to test?
> > I have the latest bios and have tried just about all bios settings.
> > 'noapic' doesn't help.
> >
> > -=Dead2=-
> >
> >
> > -
> > 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/
>
>
> -
> 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/
prev parent reply other threads:[~2001-10-25 10:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 14:13 Two suggestions (loop and owner's of linux tree) Lukasz Trabinski
2001-10-24 14:21 ` Dumitru Ciobarcianu
2001-10-24 14:38 ` Lukasz Trabinski
2001-10-24 14:48 ` Miquel van Smoorenburg
2001-10-24 14:57 ` James Sutherland
2001-10-24 15:04 ` Lukasz Trabinski
2001-10-25 9:27 ` Jens Axboe
2001-10-25 9:52 ` Asus CUV-266-D vs Intel NIC Dead2
2001-10-25 10:18 ` Asus CUV-266-D vs Intel NIC (also MSI-6321) Dead2
2001-10-25 10:39 ` Dead2 [this message]
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='00e601c15d41$5ad32910$6ac0ecd5@dead2' \
--to=dead2@circlestorm.org \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox