9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Suggestion: Programming Tutorial for /sys/doc
Date: Fri,  2 Nov 2007 14:00:13 -0400	[thread overview]
Message-ID: <e20f98b290a88867446d7b542823a308@quanstro.net> (raw)
In-Reply-To: <8aef47ed8a0ff383045c0f3a16c71712@plan9.bell-labs.com>

> The new 9load works on all the machines I was able to test it on,
> including booting from USB flash disks and SATA disks, in AHCI and
> non-AHCI modes.  The only way it's going to work for more people is if
> the community at large uses it and helps me to understand why it
> doesn't work on particular machines.

i think the new 9load is a good idea and it's nice to have more booting
options.

the problem is no actual testing is going on.  when folks can't get
the livecd booting, that's pretty much the end of the road for them.
there are very limited debugging options and there is very little 
useful information gained from the failure.

> Although the BIOS booting code is generating the most error messages,
> the panics are likely due to interactions with AHCI.

i believe none of machines with reported failures in the past day
have ahci support.  (qemu, nforce 55)  also, the machines seem to
be failing when accessing the cdrom which should be accessable in
legacy mode.

anyway, what is the answer for folks who are having problems with
the current livecd?

- erik


  reply	other threads:[~2007-11-02 18:00 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-01 20:11 Pietro Gagliardi
2007-11-01 20:23 ` don bailey
2007-11-01 20:47 ` Anthony Sorace
2007-11-01 21:00   ` Pietro Gagliardi
2007-11-01 21:22     ` Federico Benavento
2007-11-02 13:10       ` Iruata Souza
2007-11-02 13:34         ` David Leimbach
2007-11-02 13:39           ` erik quanstrom
2007-11-02 16:44             ` geoff
2007-11-02 18:00               ` erik quanstrom [this message]
2007-11-02 19:34                 ` geoff
2007-11-02 20:57                   ` David Leimbach
2007-11-03  2:44                 ` Gorka Guardiola
2007-11-03  8:49                   ` Sander van Dijk
2007-11-03 15:24                     ` Eldanen
2007-11-03 21:43                       ` erik quanstrom
2007-11-03 23:40                         ` Eldanen
2007-11-06 14:39                         ` [9fans] Font Michaelian Ennis
2007-11-06 14:46                           ` Anant Narayanan
2007-11-06 14:50                             ` erik quanstrom
2007-11-07 18:12                               ` Michaelian Ennis
2007-11-06 14:56                           ` Martin Neubauer
2007-11-05 11:59                     ` [9fans] Suggestion: Programming Tutorial for /sys/doc Gorka Guardiola
2007-11-02 18:09             ` David Leimbach
2007-11-02 18:47         ` Pietro Gagliardi
2007-11-02 20:11           ` Iruata Souza
2007-11-02 18:52         ` Pietro Gagliardi
2007-11-01 21:27     ` Uriel
2007-11-02  1:44     ` Anthony Sorace
2007-11-02  7:53       ` Uriel
2007-11-01 21:24 ` ISHWAR RATTAN
2007-11-02  3:07 ` Joel C. Salomon
2007-11-02  8:19 ` fernanbolando
2007-11-02 10:03   ` roger peppe
2007-11-02 13:07     ` Eric Van Hensbergen
2007-11-02 12:42   ` erik quanstrom
2007-11-02 15:39 ` Douglas A. Gwyn
2007-11-02 19:12 ` Anant Narayanan
2007-11-02 19:44   ` Pietro Gagliardi

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=e20f98b290a88867446d7b542823a308@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    /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).