From: "H. Peter Anvin" <hpa@zytor.com>
To: Alex Owen <r.alex.owen@gmail.com>
Cc: linux-kernel@vger.kernel.org, c-d.hailfinger.kernel.2004@gmx.net,
aabdulla@nvidia.com
Subject: Re: forcedeth net driver: reverse mac address after pxe boot
Date: Wed, 04 Oct 2006 09:50:07 -0700 [thread overview]
Message-ID: <4523E63F.4050805@zytor.com> (raw)
In-Reply-To: <55c223960610040919u221deffei5a5b6c37cfc8eb5a@mail.gmail.com>
Alex Owen wrote:
>
> This is obviously causes me a problem with automated installs started
> via PXE boot as the installed cannot DHCP as the MAC address is wrong.
>
I have a forcedeth system (ASUS A8N-E) which can't use either the Linux
driver *or* the standard Windows driver *at all* after booting PXE and
then exiting the PXE stack for local boot.
> The obvious fix for this is to try and read the MAC address from the
> canonical location... ie where is the source of the address writen
> into the controlers registers at power on? But do we know where that
> may be?
>
> The other solution would be unconditionally reset the controler to
> it's power on state then use the current logic? can we reset the
> controller via software?
> There does seem to be an nv_mac_reset function... and this does seem
> to be called if the card has a capability DEV_HAS_POWER_CONTROL but it
> is called in nv_open() while the MAC is read in nv_probe().
Doing a proper reset of the hardware would be the right thing, assuming
that this is safe/possible to do.
-hpa
next prev parent reply other threads:[~2006-10-04 16:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 16:19 forcedeth net driver: reverse mac address after pxe boot Alex Owen
2006-10-04 16:50 ` H. Peter Anvin [this message]
2006-10-04 17:30 ` Alan Cox
2006-10-04 18:06 ` Ayaz Abdulla
2006-10-20 17:33 ` Alex Owen
2006-10-05 14:28 ` Denis Vlasenko
2006-10-05 14:44 ` John W. Linville
2006-10-05 18:35 ` Carl-Daniel Hailfinger
2006-10-05 19:31 ` John W. Linville
2006-10-05 19:45 ` Ayaz Abdulla
2006-10-06 14:37 ` Alex Owen
2006-10-06 17:29 ` Ayaz Abdulla
2006-10-06 19:11 ` John W. Linville
2006-10-06 21:02 ` Ayaz Abdulla
2006-10-05 19:45 ` Andrew de Quincey
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=4523E63F.4050805@zytor.com \
--to=hpa@zytor.com \
--cc=aabdulla@nvidia.com \
--cc=c-d.hailfinger.kernel.2004@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=r.alex.owen@gmail.com \
/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