From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mark Jaffe <wizards@wizdev.net>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: MACE networking (NOT!)
Date: Mon, 26 Nov 2001 09:09:15 +0100 [thread overview]
Message-ID: <20011126080915.18485@smtp.wanadoo.fr> (raw)
In-Reply-To: <B8272394.E34C%wizards@wizdev.net>
>Hi, listas! I am engaged in a crusade to get a PowerMac 8500 with dual-604e
>card online running YellowDog 2.0. I have the 2.4.10-B0a SMP kernel
>installed, and am continually thwarted getting it into production due to
>faulty networking.
>
>The built-in networking refuses to work properly under Linux. I have no
>problems with MacOS, it operates with either a static IP (at the Co-Lo) or
>under DHCP (from an AirPort base station in the home office.) But in Linux,
>DHCP gets an IP but will not make any connection, and with the static IP at
>the Co-Lo it will perform for a few hours then become unreachable. Has this
>issue ever been seen? Is there any way to diagnose what is going on and
>resolve this problem?
>
>Mark
There are 2 things you can do:
1- Try with one CPU. The mace driver isn't really SMP safe (I can
fix that). Tell me if it helps.
2- Tell me the mace chip version (printed by the driver during boot)
and try my latest rsync tree as a "workaround" for some broken revs
was found in Darwin and I ported it to the linux driver.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-11-26 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 6:39 MACE networking (NOT!) Mark Jaffe
2001-11-26 8:09 ` Benjamin Herrenschmidt [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=20011126080915.18485@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=wizards@wizdev.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.