From: arisawa <arisawa@ar.aichi-u.ac.jp>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9pccpu: can't open /dev/sdXX/nvram
Date: Wed, 15 May 2013 18:56:17 +0900 [thread overview]
Message-ID: <DA602C1F-5A0B-48A7-A93D-130854454167@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <6436ed69830a1193bf7566be810e705b@ladd.quanstro.net>
Hello,
I retried cpu kernel with only usb flash drive.
this time I have finally succeeded in automatic start service.
the kernel is based on 9front.
MB is GA-G31M-S2L.
the MB is old model and very slow in polling usb even if I set
*acpi=1
in plan9.ini.
my nvram setting is
nvram=/dev/sdU6.0/nvram
and we must find the value 6.0 by experiment:
first, without nobootprompt and then
nobootprompt=tcp
I have not good result for bell-labs version.
thanks all.
On 2013/05/14, at 8:06, erik quanstrom <quanstro@quanstro.net> wrote:
> On Mon May 13 17:33:12 EDT 2013, arisawa@ar.aichi-u.ac.jp wrote:
>> Hello,
>>
>> not yet with usb.
>> my current solution is "sdcard with sata adapter" only for NVRAM.
>> I will be happy if someone have a solution that uses usb flash drive only.
>
> it looks to me that the problem is the fact that intrenable() doesn't
> find the interrupts for usb. polling might be slow enough to trip
> up the arbitrary delays in the boot process.
>
> that is, it looks like the mp table is incorrect.
>
> have you tried a kernel with more support for acpi? i believe you
> may be able to try on recent 9atom kernels, (http://ftp.9atom.org/other/9paecpu)
> with the following two addition to your .ini file
> *acpi=1
>
> this is really cinap's work. i only suggest 9atom as it may be easier
> to test in your environment.
>
> good luck.
>
> - erik
>
next prev parent reply other threads:[~2013-05-15 9:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-28 3:30 arisawa
2012-07-28 8:19 ` David du Colombier
2012-07-28 13:41 ` arisawa
2012-07-28 14:33 ` David du Colombier
2012-07-29 7:30 ` arisawa
2012-07-29 9:43 ` Richard Miller
2012-07-29 11:45 ` arisawa
2012-07-29 14:16 ` Richard Miller
2012-07-29 22:49 ` arisawa
2012-07-30 9:19 ` arisawa
2012-07-30 14:46 ` erik quanstrom
2012-07-30 20:45 ` cinap_lenrek
2012-08-17 2:15 ` arisawa
2012-08-17 3:27 ` cinap_lenrek
2013-05-13 16:37 ` Skip Tavakkolian
2013-05-13 21:32 ` arisawa
2013-05-13 21:53 ` Matthew Veety
2013-05-13 23:06 ` erik quanstrom
2013-05-15 9:56 ` arisawa [this message]
2013-05-15 20:56 ` arisawa
2013-05-15 21:18 ` erik quanstrom
2013-05-16 0:16 ` arisawa
2013-05-16 1:25 ` erik quanstrom
2013-05-16 13:44 ` kernel panic
2013-05-17 12:36 ` arisawa
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=DA602C1F-5A0B-48A7-A93D-130854454167@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--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).