From: Purple_Q <bitpusher2600@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Netbook Install Help
Date: Thu, 25 Feb 2010 13:37:32 +0000 [thread overview]
Message-ID: <8f1d1573-b43c-48d5-b182-ef4ef223d71d@k41g2000yqm.googlegroups.com> (raw)
In-Reply-To: <3a0c32c9406fd0a0ac1b4470be1302f8@ladd.quanstro.net>
Oops. My own trigger finger, sorry.
Yeah, the drive is just fine if set in the bios to ahci, but plan9
can't see it. If I set it to IDE, plan9 can see it but it gives BSD
the errors you see in the image. Weird.
On Feb 25, 7:28Â am, quans...@quanstro.net (erik quanstrom) wrote:
> On Thu Feb 25 07:19:14 EST 2010, quans...@quanstro.net wrote:
>
> > On Thu Feb 25 06:29:21 EST 2010, bitpusher2...@gmail.com wrote:
> > > Hmm, might be slightly above my head (I don't know what a node is).
> > > That aside, the boot loader fires up fine, and it makes it to what I
> > > believe is near the end of the boot sequence in fact. ad0 is my hard
> > > disk;
> > > queuevonqu.com/bsderr.jpg
>
> > that's not plan 9, but it looks like a drive failure.
>
> too quick on the trigger finger. Â i think i understand
> correctly that the same drive works fine if the southbridge
> is in ide mode. Â in that case, i'm not sure what's going on.
> the drive is identifying correctly, but read/write commands
> fail. Â if we assume that this kernel uses interrupts to identify
> the drive, then the problem isn't interrupts, it's that the
> read/write commands are failing. Â that really does look
> like drive failure, and i'd be pretty surprised if the drive
> worked in ide mode.
>
> - erik
next prev parent reply other threads:[~2010-02-25 13:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52d0fffa-513e-4ff4-855b-955a93794b07@c10g2000vbr.googlegroups.co>
2010-02-22 17:40 ` erik quanstrom
2010-02-23 16:17 ` Purple_Q
2010-02-23 16:24 ` erik quanstrom
2010-02-23 16:27 ` erik quanstrom
2010-02-23 17:50 ` Purple_Q
2010-02-24 10:10 ` Purple_Q
2010-02-24 13:06 ` erik quanstrom
2010-02-24 14:46 ` Purple_Q
2010-02-24 15:55 ` erik quanstrom
2010-02-24 16:58 ` Purple_Q
[not found] ` <1de0a12e-51f4-4b41-b49e-085c5705f734@z11g2000yqz.googlegroups.co>
2010-02-24 19:01 ` erik quanstrom
2010-02-25 9:39 ` Purple_Q
2010-02-25 10:13 ` John Stalker
2010-02-25 11:27 ` Purple_Q
2010-02-25 12:18 ` erik quanstrom
2010-02-25 12:24 ` erik quanstrom
2010-02-25 13:37 ` Purple_Q
2010-02-25 18:21 ` hiro
2010-02-25 13:37 ` Purple_Q [this message]
2010-02-22 9:57 Purple_Q
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=8f1d1573-b43c-48d5-b182-ef4ef223d71d@k41g2000yqm.googlegroups.com \
--to=bitpusher2600@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).