9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ramakrishnan Muthukrishnan <vu3rdd@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] dual boot
Date: Sun, 25 May 2014 13:39:10 +0530	[thread overview]
Message-ID: <CAA6Yd9W3yoDMLKyASV47HDv_VYXk2eRsB6pAbYzq6OLxeyjARQ@mail.gmail.com> (raw)
In-Reply-To: <d7d85f4b5d30c2be1f9f231bb3894ea1@brasstown.quanstro.net>

On Sun, May 25, 2014 at 11:07 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>> Yes, I typed them by hand. Sorry about the error.
>>
>> >> panic: kernel fault: no user process pc=0xf0162415 addr=0x000000a8
>> >> panic: kernel fault: no user process pc=0xf0162415 addr=0x000000a8
>> >
>> > there is a new TEST image @ http://ftp.9atom.org/other/+usbinstamd64.bz2
>> > i have not had a chance to try it myself, but the crash seems obvious enough.
>>
>> Thanks. I just tried it and indeed, with the pae kernel, it gets me
>> into the installer. At some point, I mistakenly selected ("arches to
>> install" as amd64, well I really wanted to install amd64 but perhaps
>> the kernel has not been rebuilt for amd64 I guess.
>>
>> Now, it proceeds to "build full set of amd64 executables?" which I
>> selected "yes". I then get a build error:
>>
>> 8c -FTVw s_tolower.c
>> s_rdinstack.c:13 not a function
>> s_rdinstack.c:13 syntax error, last name: Sinstack
>> mk: 8c -FTVw s_rdinstack.c  : exit status=rc 594: 8c 604: error
>> mk: date for (i  ...  : exit status=rc 509: rc 563: mk 565: error
>> halt system? (yes, no, skip)[no default]
>
> oops.  sorry.  my fault.  fixed.
>
>> I am going to try installing a 386 system instead (after sending out
>> this email).
>>
>> Also the amd64 kernel still didn't boot. When I selected amd64
>> (selection 0), it just printed something that I couldn't read and
>> rebooted the system.
>
> if this is an amd (not intel) system, i may have applied a band-aid for this.

Using your new image, I confirm that your fixes are working. I could
boot and install the system with arch as amd64.

In the "configure vga resolution? (yes, no, skip)[no]: I selected "yes".

It proceeded to show me a list of resolutions (8 different options).
Since my monitor has the highest resolution of 1920x1080, I selected
that. Next it asked for "image depth[no default]" where I typed in 16.
But it kept looking there, whatever I keyed in. If I proceed with "no
default", I see that the PLAN9.INI file in the 9fat partition (which I
mounted with 9fat: command) has the resolution set as "1920x1080xno
default". So, after installation, I got dropped into a text console,
probably because of this error.

Also if I opted to create a user name (called "ram") for me during
installation. But I don't see the lib/* files under /usr/ram. I see a
few files under /usr/glenda. Aren't some of these boilerplate init
files copied to the user home directory during installation?

Thanks again. Doing another installation now, but without opting for a
vga resolution during installation time to see if I can get rid of the
"no default" thing in the plan9.ini file. I will change that file
later after the installation to pick the right resolution.

--
  Ramakrishnan



  reply	other threads:[~2014-05-25  8:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 12:40 Ramakrishnan Muthukrishnan
2014-05-23 12:47 ` erik quanstrom
2014-05-23 12:51 ` Jacob Todd
2014-05-24  6:43   ` Ramakrishnan Muthukrishnan
2014-05-24  6:47     ` Ramakrishnan Muthukrishnan
2014-05-24 11:33       ` Ramakrishnan Muthukrishnan
2014-05-24 12:01         ` Nick Owens
2014-05-24 12:13           ` Ramakrishnan Muthukrishnan
2014-05-24 14:34     ` erik quanstrom
2014-05-25  5:11       ` Ramakrishnan Muthukrishnan
2014-05-25  5:28         ` Ramakrishnan Muthukrishnan
2014-05-25  5:37         ` erik quanstrom
2014-05-25  8:09           ` Ramakrishnan Muthukrishnan [this message]
2014-05-25  9:08             ` Ramakrishnan Muthukrishnan
2014-05-25 17:25               ` Brian L. Stuart
2014-05-25 17:51                 ` Ramakrishnan Muthukrishnan
2014-05-25 23:05                   ` Brian L. Stuart
2014-05-25 21:49             ` erik quanstrom
2014-05-26 10:37               ` Ramakrishnan Muthukrishnan
2014-05-26 12:49                 ` erik quanstrom
2014-05-24 14:35     ` erik quanstrom
2014-05-25  5:12       ` Ramakrishnan Muthukrishnan

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=CAA6Yd9W3yoDMLKyASV47HDv_VYXk2eRsB6pAbYzq6OLxeyjARQ@mail.gmail.com \
    --to=vu3rdd@gmail.com \
    --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).