From: Jens Staal <staal1978@gmail.com>
To: 9front@googlegroups.com
Subject: Re: difference cdrom boot and 9fat boot?
Date: Tue, 31 May 2011 19:16:02 +0200 [thread overview]
Message-ID: <BANLkTikTXJBFzbwjZsjmSPDZrk-3QV-krQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=43N=VOCD-Fs5V5sdGwr2mwWsROw@mail.gmail.com>
By the way: I also made a note of the stuff printed just before it
stops booting:
8M memory: 6M kernel data 1M user 39M swap
6: bzfs killed: out of memory
boot: can't exec /bin/rc '/bin/rc' does not exist
2011/5/31 Jens Staal <staal1978@gmail.com>:
> It does print e820 parameters when booting from disk: lots of zeroes
> (I had to boot several times to check this... passes by very fast) and
> ends with 9f800
>
> If it is 9bootfat I must have had extremely bad luck since also 9atom
> had exactly the same issue.
> If it is Grub (which would not surprise me...), it is strange that the
> official Plan9 9pcf could boot...
>
> I am starting to wonder if I should aim for a native install of the
> official Plan9, then pull the broadcom driver from the 9front CD and
> update from there.... Probably this would be faster than figuring this
> out :)
>
> About IRC: I will try as soon as I get home from work (IRC blocked
> from the work network)
>
> Thanks for all the help!
>
> Cheers
> Jens
>
> 2011/5/31 <cinap_lenrek@gmx.de>:
>> the 9boot bootloader prints all parametrs that it will pass
>> to the kernel.
>> so does it print any e820= lines when booting from disk?
>> 9bootfat?
>> if not, there are 2 possibilities... 9bootfat was not rebuild
>> in that iso, or when booting from disk the bios or some side
>> effect from grub disables the e820 scan.
>>
>> 3) you are not using 9bootfat at all... maybe because the pbs
>> was not updated and what loads 9pcf is some stale version of
>> 9load that was installed on the fat before.
>>
>> you can come to irc on freenode.net in the channel #cat-v and
>> we help you trouble shooting this issue if you want.
>>
>> --
>> cinap
>>
>
next prev parent reply other threads:[~2011-05-31 17:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 5:42 staalmannen
2011-05-31 9:39 ` cinap_lenrek
2011-06-02 4:52 ` Uriel
2011-05-31 9:43 ` cinap_lenrek
2011-05-31 14:27 ` Jens Staal
2011-05-31 16:36 ` cinap_lenrek
2011-05-31 17:14 ` Jens Staal
2011-05-31 17:16 ` Jens Staal [this message]
2011-05-31 17:19 ` cinap_lenrek
2011-05-31 17:43 ` Julius Schmidt
2011-05-31 17:57 ` cinap_lenrek
2011-05-31 19:49 ` Jens Staal
2011-05-31 21:21 ` cinap_lenrek
2011-06-01 4:22 ` Jens Staal
2011-06-01 6:05 ` Jens Staal
2011-06-01 15:52 ` Jens Staal
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=BANLkTikTXJBFzbwjZsjmSPDZrk-3QV-krQ@mail.gmail.com \
--to=staal1978@gmail.com \
--cc=9front@googlegroups.com \
/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).