9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Jens Staal <staal1978@gmail.com>
To: 9front@googlegroups.com
Subject: Re: difference cdrom boot and 9fat boot?
Date: Wed, 1 Jun 2011 17:52:03 +0200	[thread overview]
Message-ID: <BANLkTi=Z-femqunCCaUP55BTZ6QckmtVtg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=hu4Jr0LLtNc+oX=S82iMM26k7iQ@mail.gmail.com>

SOLVED!

This is both embarrasing and a bit surprising, but I think your
hypothesis of "contamination" from previous plan9 installation at the
same partition somehow was right.

When I tried reinstalling before I usually just deleted all the plan9
partitions in the installation. Now I removed the partition in Linux,
formatted the empty space in a new partition and deleted that one too.

After installing on this patch of empty space, the 9Front boots just
fine. I am extremely surprised and none the wiser.

On the bright side: now I might be able to play with stuff that I at
least can hope to begin to understand (or at least where I can get
hold of the errors ;) )

2011/6/1 Jens Staal <staal1978@gmail.com>:
> I checked again and it is indeed as you said.
> From the cdboot you got e820= (numbers) as the first line visible on screen
> from the 9fat boot it is only the e820: (numbers) after a couple of
> other lines (so probably kernel output).
>
> I guess it may then be something weird with my 9bootfat. I will pull
> another iso and copy that 9bootfat over and see what happens.
>
> I also (naively) just tried to define
> e820=(numbers)
> in plan9.ini circumvent whatever is wrong, but that did not work. Are
> you aware of some kind of similar option?
>
> 2011/6/1 Jens Staal <staal1978@gmail.com>:
>> Sorry about messing up. I did indeed block the boot by entering the
>> prompt for each boot option and these were the things I could see....
>>
>> 2011/5/31  <cinap_lenrek@gmx.de>:
>>> this is not the output! it cant be...
>>> 9bootfat prints in exactly the same form as 9bootiso... it never
>>> prints something like "e820:" and the hex values are alawys
>>> 16 hex digits. its the same code after all, the 9bootfat/9bootiso
>>> and 9bootpxe differ only in ther start() functions!
>>>
>>> what is this?
>>>
>>> cdboot:
>>> "e820: 0000000000000000 000000000009f800 0000000000100000 000000007fed0000"
>>>
>>> the numbers there at least look right, but it should really be:
>>>
>>> "e820=0000000000000000 000000000009f800 0000000000100000 000000007fed0000"
>>>
>>> this one completly puzzles me... 16bit formating? wtf?
>>>
>>> 9fat:
>>> "e820: 0000 0000 0009 f800 memory"
>>>
>>> the "memory" there indicates that this is printed by the kernel i guess?
>>>
>>> but what i wanted for like 3 mails is the output of 9bootfats e820 scan!
>>> what does it print for e832=? you said it produces e820= output? what is
>>> it?
>>>
>>> did you got to the > prompt with 9bootfat?
>>>
>>> this all makes no sense!
>>>
>>> :-(
>>>
>>> --
>>> cinap
>>>
>>
>

      reply	other threads:[~2011-06-01 15:52 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
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 [this message]

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='BANLkTi=Z-femqunCCaUP55BTZ6QckmtVtg@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).