9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jim Habegger <jimhabegger@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Adventures of a home user
Date: Sun, 19 Apr 2009 09:01:40 +0800	[thread overview]
Message-ID: <ea634cc80904181801j2f6912a2u362fdf626c209a73@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3106 bytes --]

I haven't responded yet to all the info and ideas in my earlier thread,
because I've been trying to get Plan 9 working in QEMU.

First, I tried using 9vx. I found these instructions at
http://swtch.com/9vx/ :

9vx-0.12.tar.bz2 is a binary distribution
> containing a minimal plan 9 tree and binaries for
> freebsd, linux, and os x.
>
> download, unpack, and then
>
> cd 9vx-0.12
> ./9vx.Linux -u glenda
>
> (or 9vx.FreeBSD or 9vx.OSX)
>

To my surprise, it really was as simple as that!

At least, I get the same windows that I got when I had Plan 9 installed in
its own partition. I haven't tried to actually do anything with it yet. I
did learn that I have to press buttons 1 and 3 together, instead of shift-3,
to simulate button 2. Before exploring Plan 9 in 9vx, I wanted to see if I
could get it working in QEMU in my Ubuntu Intrepid Ibex system.

That was another story.

*Challenge 1*: Framebuffer

root@Satellite:~# qemu -hda Plan9.qcow.img -cdrom plan9.iso -boot d
>
>      =======================|  DirectFB 1.0.1  |=======================
>           (c) 2001-2007  The DirectFB Organization (directfb.org)
>           (c) 2000-2004  Convergence (integrated media) GmbH
>         ------------------------------------------------------------
>
> (*) DirectFB/Core: Single Application Core. (2008-09-12 19:59)
> (!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
>     --> No such file or directory
> (!) DirectFB/FBDev: Error opening framebuffer device!
> (!) DirectFB/FBDev: Use 'fbdev' option or set FRAMEBUFFER environment
> variable.
> (!) DirectFB/Core: Could not initialize 'system' core!
>     --> Initialization error!
> Could not initialize SDL - exiting
>

Winning response: VGA kernel option in the Ubuntu boot menu

*Challenge 2*: Scrambled keyboard

Winning response:

qemu -hda Plan9.qcow.img -cdrom plan9.iso -boot d -k en-us
>

*Challenge 3*: Plan 9 hanging up

Winning response: I wait a few seconds before responding to each prompt when
Plan 9 is starting up.

*Challenge 4*: Display size

My Ubuntu display is 1024x768. The default size of the Plan 9 display is
much smaller, so it wasn't using all the available space on the Ubuntu
display.

Winning response: I re-installed Plan 9, changing the dimensions at the
prompt. I haven't learned yet how to change them from within Plan 9.

*Challenge 5*: How to exit from QEMU

I haven't found anything in the man pages that works for me. I can go back
to the console and do ctrl-c, but I don't like doing that.

Current response:

qemu -hda Plan9.qcow.img -cdrom plan9.iso -boot d -k en-us -no-reboot
>

Now, when I do "fshalt -r" in Plan 9, it exits from QEMU.

*Challenge 6*: How to use kqemu.

I see this message when I run qemu:

Could not open '/dev/kqemu' - QEMU acceleration layer not activated: No such
> file or directory
>

I've done some research, but I'm still confused about whether kqemu is
included in Intrepid Ibex, and if so how to activate it. When I installed
Plan 9, it took more than an hour to format 2GB.

[-- Attachment #2: Type: text/html, Size: 4112 bytes --]

             reply	other threads:[~2009-04-19  1:01 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19  1:01 Jim Habegger [this message]
2009-04-19  1:05 ` john
2009-04-19  1:08 ` erik quanstrom
2009-04-19 10:15 ` yy
2009-04-19 14:16 ` Jim Habegger
2009-04-19 14:34   ` erik quanstrom
2009-04-19 14:43   ` Anthony Sorace
2009-04-19 15:37   ` Jim Habegger
2009-04-20 10:42     ` Balwinder S Dheeman
2009-04-21  7:55       ` Jim Habegger
2009-04-21 22:03         ` blstuart
2009-04-20  5:01 ` Jim Habegger
2009-04-20  5:13   ` andrey mirtchovski
2009-04-20  5:38     ` André Günther
2009-04-20  5:22   ` Federico G. Benavento
2009-04-20  7:14 ` Jim Habegger
2009-04-21  3:38 ` Jim Habegger
2009-04-21  5:14   ` john
2009-04-21  7:05   ` Federico G. Benavento
2009-04-21  3:52 ` Jim Habegger
2009-04-21  3:55   ` Jim Habegger
2009-04-21 12:06     ` erik quanstrom
2009-04-21 22:13       ` blstuart
2009-04-21  6:02 ` Jim Habegger
2009-04-21  6:31   ` Anthony Sorace
2009-04-21  6:59     ` Jim Habegger
2009-04-21  9:10 ` Jim Habegger
2009-04-21 11:26   ` erik quanstrom
2009-04-21 15:26   ` john
2009-04-21 15:34     ` erik quanstrom
2009-04-21 20:01 ` Jim Habegger
2009-04-21 21:28   ` Karin Willers
2009-04-21 22:23   ` blstuart
2009-04-22  0:29     ` john
2009-04-22  1:07       ` Jim Habegger
2009-04-23  9:12 ` Jim Habegger
2009-04-23 10:23   ` Eris Discordia
2009-04-23 15:55     ` maht

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