From: Rene Engelhard <rene@rene-engelhard.de>
To: linux-kernel@vger.kernel.org, debian-alpha@lists.debian.org
Subject: RealTek NIC on alpha?
Date: Wed, 11 Jun 2003 11:19:11 +0200 [thread overview]
Message-ID: <20030611091910.GD801@rene-engelhard.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]
Hi,
as my "normal" PC just died and I strongly need it as a router I thought
about adding this functionality to my alpha (digital AlphaStation 500
333 Mhz).
So I got a RealTek NIC from my i386 machine and put in into my alpha
hoping that would work (it would told me this should).
After installing the NIC the boot outputs
"
SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256).
CSLIP: code copyright 1989 Regents of the University of California.
loop: loaded (max 8 devices)
Linux Tulip driver version 0.9.15-pre12 (Aug 9, 2002)
eth0: Digital DC21040 Tulip rev 36 at 0x9800, 00:00:F8:23:30:83, IRQ 29.
8139too Fast Ethernet driver 0.9.2
"
and does not do anything after that.
This was from 2.4.21-rc7, I tried 2.2.25 before and there was a similar
problem:
"
SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256).
CSLIP: code copyright 1989 Regents of the University of California.
tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov
eth0: Digital DC21040 Tulip rev 36 at 0x9000, 00:00:F8:23:30:83, IRQ 29.
eth1: region already allocated at 0x9000.
"
.. and halts too doing nothing...
Any advice? Do I need some boot parameters?
Regards,
René
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-06-11 9:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 9:19 Rene Engelhard [this message]
2003-06-11 9:27 ` Marc Zyngier
2003-06-11 12:16 ` Måns Rullgård
2003-06-11 14:42 ` Compatible Hardware (Was: Re: RealTek NIC on alpha?) Marc Giger
2003-06-11 14:45 ` Jeff Garzik
2003-06-11 22:19 ` Michal Jaegermann
2003-06-11 14:07 ` RealTek NIC on alpha? Rene Engelhard
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=20030611091910.GD801@rene-engelhard.de \
--to=rene@rene-engelhard.de \
--cc=debian-alpha@lists.debian.org \
--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
all inboxes | Powered by JetHome®