From: Roger Luethi <rl@hellgate.ch>
To: "Kenneth Aafløy" <lists@kenneth.aafloy.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] Via-Rhine WOL vs PXE Boot
Date: Fri, 17 Sep 2004 22:34:58 +0200 [thread overview]
Message-ID: <20040917203458.GA12779@k3.hellgate.ch> (raw)
In-Reply-To: <200409172154.36550.lists@kenneth.aafloy.net>
On Fri, 17 Sep 2004 21:54:36 +0200, Kenneth Aafløy wrote:
> In recent kernels I have been having trouble booting from a LAN with the built
> in PXE firmware in my Via Epia M10k board. This will never happen after a
> cold-boot. But do accur after the first reboot or power-down/power-up cycle.
> When this occurs the PXE firmware exits with no error, as at least a
> unplugged wire (from cold-boot) will yield an error message with the
> unchanged driver. Cold-boot refers to complete power separation from the
> motherboard.
>
> I've traced this down to a specific change in the via-rhine ethernet driver:
[...]
The patch you are referring to contains very little code that affects chip
programming without user intervention (e.g. calling ethtool ioctls). There
is one notable exception: The patch introduces rhine_shutdown which is
called at shutdown (well, duh!). I suppose you can make the problem go away
if you comment out parts of said function. I'd start at the bottom with the
D3 call.
Roger
next prev parent reply other threads:[~2004-09-17 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-17 19:54 [BUG] Via-Rhine WOL vs PXE Boot Kenneth Aafløy
2004-09-17 20:34 ` Roger Luethi [this message]
2004-09-17 22:01 ` Kenneth Aafløy
2004-09-18 6:13 ` Roger Luethi
2004-09-19 12:52 ` Kenneth Aafløy
2004-09-19 13:15 ` Roger Luethi
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=20040917203458.GA12779@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@kenneth.aafloy.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.