9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Revo L80
Date: Wed,  9 Jul 2014 17:55:08 -0400	[thread overview]
Message-ID: <de43e3ed031336674e21bca869dbfbb8@ladd.quanstro.net> (raw)
In-Reply-To: <CAGMcHPoXg4CNyAWHN_tAZQusfMdYoAjx7PQ6TmncAA2uC9=y=A@mail.gmail.com>

On Wed Jul  9 16:10:16 EDT 2014, riddler876@gmail.com wrote:
> I've been looking into it a bit more today. It actually seems to be quite stuck.
>
> I get as far as the 'live usb' boot, with glenda, rio, acme etc
> starting up. The "plan 9 install" screen and its live log are there.
> While working through the install the only disk appears to be
> /dev/sdu0. This is ~4GB in size and is the USB stick.
> The PC HDD does not seem the be listed in /dev; there is however a
> /dev/sdU0, but this seems to be a duplicate of /dev/sdu0 (based on ls
> -l showing the exact same size and the PC HDD should be much bigger
> than 4GB).

sdU0.0 is provided directly by usb/disk.  usb/disk does not do partitioning,
so it is remounted with the sd loopback driver (sdloop(3)).  this is what you
see as sdu0.

the pc hard drive would be listed as /dev/sdE? where ? in [0..f], assuming that
your machine uses ahci.  the output of /dev/sdctl would be useful, otherwise
you can use sos/sos (see sos(8)).

> Took a look at /dev/kmesg and there is only only three lines that look
> relevant that I've put in at the end of this email. I can attach more
> of it if required.
>
> I attempted running sos/sos but some files appear to be missing. It
> says it can not find bin/aux/cpuid, bin/aux/dmi, bin/bzip2.
> The /tmp/sos.mkfs.bz2 file is created, but empty.

i wonder if the fact that syscall(1) was broken by the nsec thing caused fewer
programs to be built than normal.  this is fixed in the current image.

i would recommend doing the following
	@{cd /sys/src/cmd/aux; mk install}
	@{cd /sys/src/cmd/bzip2; mk install}

and running sos again.

really want you're interested in is the full output of /dev/kmesg, and
/dev/sdctl.

> I suspect it's more likely I've unknowingly missed a step somewhere
> rather than the bin directory is actually missing files.
>
> ----/dev/kmesg output snippet----
> #A0: hda; mem fffffe00f7e30000 irq 4
> #A0: hda: coded #0, vendor 10ec0662, rev 00100300
> #A0: hda: coded #c, vendor 80862806, rev 00100000
>
> Any help appreciated!

this is cool, and expected.

- erik



  reply	other threads:[~2014-07-09 21:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-05 21:39 Riddler
2014-07-07 16:09 ` erik quanstrom
2014-07-07 22:07   ` Riddler
2014-07-08  0:21     ` erik quanstrom
2014-07-09 20:08       ` Riddler
2014-07-09 21:55         ` erik quanstrom [this message]
2014-07-10 12:51           ` Riddler
2014-07-10 15:57             ` erik quanstrom
2014-07-10 16:18               ` Riddler
2014-07-10 16:30                 ` erik quanstrom
2014-07-10 17:11                   ` Riddler
2014-07-10 19:03                     ` erik quanstrom
2014-07-14 10:52                       ` Riddler

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=de43e3ed031336674e21bca869dbfbb8@ladd.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).