9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Nick Owens <mischief@9.offblast.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] dual boot
Date: Sat, 24 May 2014 05:01:28 -0700	[thread overview]
Message-ID: <20140524120128.GN3763@iota.offblast.org> (raw)
In-Reply-To: <CAA6Yd9XiHH84zamk3F95WWLjJOb1cmgLgbtv8VyYq-ZAxhCw3A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1689 bytes --]

On Sat, May 24, 2014 at 05:03:07PM +0530, Ramakrishnan Muthukrishnan wrote:
> On Sat, May 24, 2014 at 12:17 PM, Ramakrishnan Muthukrishnan
> <vu3rdd@gmail.com> wrote:
> > On Sat, May 24, 2014 at 12:13 PM, Ramakrishnan Muthukrishnan
> > <vu3rdd@gmail.com> wrote:
> >> I downloaded the usbinstamd64 image from the 9atom webpage and booted
> >> it up. First, I tried amd64 (selection 0), in a second or so, some
> >> text went past the screen quickly and the machine rebooted. I then
> >> tried selection 1 (386pae), that booted up but quickly halted with
> >> this:
> >>
> >> Plan 9
> >> E820: ....
> >> ...
> >> apic: 6 machs started; flat mode vectors
> >> winbont ffff.ff hw fff8
> >>   no capabilities
> >> panic: kernel fault: no user process pc=f0162415 addr=0x000000a8
> >> panic: kernel fault: no user process pc=f0162415 addr=0x000000a8
> >> dumpstack disabled
> >> cpu0: exiting
> >> cpu0: spurious interrupt 39, last 0
> >>
> >> and it hangs there.
> >
> > The mother board is ASUS M4A89GTD PRO/USB3.
> >
> > <http://www.asus.com/Motherboards/M4A89GTD_PROUSB3/>
> 
> Also for the record, I also tried the Labs plan9 usb image. That
> didn't go past a few initial prints either. I didn't note them down
> but it was different from the ones reported above with 9atom and
> failed much earlier.
> 
> -- 
>   Ramakrishnan
> 

it appears this motherboard is using usb 3 aka xhci. i don't know for
certain but i don't think any plan 9 (fork or not-a-fork) has xhci
support. looking through the archive, there was talk of xhci about a
year ago.

try disabling usb 3.0 in the bios setting and see if it makes progress
when booting from usb.


[-- Attachment #2: Type: application/pgp-signature, Size: 851 bytes --]

  reply	other threads:[~2014-05-24 12:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 12:40 Ramakrishnan Muthukrishnan
2014-05-23 12:47 ` erik quanstrom
2014-05-23 12:51 ` Jacob Todd
2014-05-24  6:43   ` Ramakrishnan Muthukrishnan
2014-05-24  6:47     ` Ramakrishnan Muthukrishnan
2014-05-24 11:33       ` Ramakrishnan Muthukrishnan
2014-05-24 12:01         ` Nick Owens [this message]
2014-05-24 12:13           ` Ramakrishnan Muthukrishnan
2014-05-24 14:34     ` erik quanstrom
2014-05-25  5:11       ` Ramakrishnan Muthukrishnan
2014-05-25  5:28         ` Ramakrishnan Muthukrishnan
2014-05-25  5:37         ` erik quanstrom
2014-05-25  8:09           ` Ramakrishnan Muthukrishnan
2014-05-25  9:08             ` Ramakrishnan Muthukrishnan
2014-05-25 17:25               ` Brian L. Stuart
2014-05-25 17:51                 ` Ramakrishnan Muthukrishnan
2014-05-25 23:05                   ` Brian L. Stuart
2014-05-25 21:49             ` erik quanstrom
2014-05-26 10:37               ` Ramakrishnan Muthukrishnan
2014-05-26 12:49                 ` erik quanstrom
2014-05-24 14:35     ` erik quanstrom
2014-05-25  5:12       ` Ramakrishnan Muthukrishnan

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=20140524120128.GN3763@iota.offblast.org \
    --to=mischief@9.offblast.org \
    --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).