From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Date: Sun, 19 Apr 2009 09:01:40 +0800 Message-ID: From: Jim Habegger To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=0015175cb606e3ea8a0467ddf499 Subject: [9fans] Adventures of a home user Topicbox-Message-UUID: e81f5e94-ead4-11e9-9d60-3106f5b1d025 --0015175cb606e3ea8a0467ddf499 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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. --0015175cb606e3ea8a0467ddf499 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 binari= es 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 l= earn 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 cou= ld get it working in QEMU in my Ubuntu Intrepid Ibex system.

That was another story.

Challenge 1: Framebuffer

<= blockquote style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt = 0pt 0pt 0.8ex; padding-left: 1ex;" class=3D"gmail_quote">root@Satellite:~# = qemu -hda Plan9.qcow.img -cdrom plan9.iso -boot d

=A0=A0=A0=A0 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D|=A0 DirectFB 1.0.1=A0 |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=A0=A0=A0=A0=A0=A0=A0=A0=A0 (c) 2001-2007= =A0 The DirectFB Organization (directfb.org= )
=A0=A0=A0=A0=A0=A0=A0=A0=A0 (c) 2000-2004=A0 Convergence (integrat= ed media) GmbH
=A0=A0=A0=A0=A0=A0=A0 -----------------------------------------------------= -------

(*) DirectFB/Core: Single Application Core. (2008-09-12 19:5= 9)
(!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' = failed
=A0=A0=A0 --> No such file or directory
(!) DirectFB/FBDev: Error ope= ning framebuffer device!
(!) DirectFB/FBDev: Use 'fbdev' option = or set FRAMEBUFFER environment variable.
(!) DirectFB/Core: Could not in= itialize 'system' core!
=A0=A0=A0 --> Initialization error!
Could not initialize SDL - exitin= g

Winning response: VGA kernel option in the Ubuntu boo= t menu

Challenge 2: Scrambled keyboard

Winning respons= e:

qemu -hda Pla= n9.qcow.img -cdrom plan9.iso -boot d -k en-us

Challe= nge 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 m= uch smaller, so it wasn't using all the available space on the Ubuntu d= isplay.

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 a= nd 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 f= rom QEMU.

Challenge 6: How to use kqemu.

I see this me= ssage 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 Ib= ex, and if so how to activate it. When I installed Plan 9, it took more tha= n an hour to format 2GB.
--0015175cb606e3ea8a0467ddf499--