From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] the mysterious bios change
Date: Mon, 19 Aug 2013 11:17:01 -0700 [thread overview]
Message-ID: <CAJSxfmKXLrd3=G+DntLepOoC6BCLXKHgXWmZRQ7CHpT84P=3ZQ@mail.gmail.com> (raw)
In-Reply-To: <558b5fd4f39a7820a67adedd78f94483@coraid.com>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
it is possible that i could have built a new 9pccpuf after the initial boot
of the fs and installed it in place but had never rebooted the machine with
the new kernel; but (old age memory failings notwithstanding), i don't
think i did that.
FYI, i think i noticed that in ata compatibility mode vid/did is 8086/2920
and in ahci mode it shows 8086/2922. in the version of sources i have,
sdata.c checks for the former and sdiahci.c checks for the latter.
On Mon, Aug 19, 2013 at 9:53 AM, erik quanstrom <quanstro@labs.coraid.com>wrote:
> On Mon Aug 19 12:25:33 EDT 2013, a@9srv.net wrote:
> > Erik's explanation certainly makes sense, but here's an
> > alternative possibility. In the past, I've set up the bios on
> > a system a certain way, then accidentally written to
> > #r/nvram (which isn't really useful on a PC), and had the
> > bios reset to factory defaults. Behavior of the bios after
> > writing that file is bios-dependent, but it's easy to test.
>
> i happen to have that machine, and i have not seen that
> behavior with any version of bios up to 1.2a.
>
> perhaps we haven't written to #r/nvram.
>
> - erik
>
>
[-- Attachment #2: Type: text/html, Size: 1696 bytes --]
prev parent reply other threads:[~2013-08-19 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-18 16:40 Skip Tavakkolian
2013-08-18 17:20 ` erik quanstrom
2013-08-19 16:09 ` Anthony Sorace
2013-08-19 16:53 ` erik quanstrom
2013-08-19 18:17 ` Skip Tavakkolian [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='CAJSxfmKXLrd3=G+DntLepOoC6BCLXKHgXWmZRQ7CHpT84P=3ZQ@mail.gmail.com' \
--to=skip.tavakkolian@gmail.com \
--cc=9fans@9fans.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).