Summary Files Commits Branches @commit @diff @stats
path: root / src / tutorials / fix-no-frame-buffer-plan9 / index.du
diff options
context:
space:
mode:
Commit6a84efc70706da6a8a15394dcbbf90eaa7198cb1 (patch)
Author
 Syndamia <kamen@syndamia.com>
2025-07-24 21:12:39 +0300
Committer
 Syndamia <kamen@syndamia.com>
2025-07-24 21:12:39 +0300
Files4cbc8d0891685d88c9fd55125f8d8b2460d71d6c /src/tutorials/fix-no-frame-buffer-plan9/index.du
syndamia.com-6a84efc70706da6a8a15394dcbbf90eaa7198cb1.tar
syndamia.com-6a84efc70706da6a8a15394dcbbf90eaa7198cb1.tar.gz
syndamia.com-6a84efc70706da6a8a15394dcbbf90eaa7198cb1.zip
Parentd8ab2f2019034aad3bdc5083aa80f4e43c57f774 (diff)
feat(tutorials): Converted half of the tutorials into dunbar
1 files changed, 94 insertions, 0 deletions
-rw-r--r--src/tutorials/fix-no-frame-buffer-plan9/index.du94
diff --git a/src/tutorials/fix-no-frame-buffer-plan9/index.du b/src/tutorials/fix-no-frame-buffer-plan9/index.du
new file mode 100644
index 0000000..bce1cd9
--- /dev/null
+++ b/src/tutorials/fix-no-frame-buffer-plan9/index.du
@@ -0,0 +1,94 @@
+# Fix "No frame buffer" error in Plan 9
+
+'define expected-reading 3 min
+'define created 30 July 2022
+'define edited 30 July 2022
+[$pagenav]
+
+Let's say you installed [url https://en.wikipedia.org/wiki/Plan_9_from_Bell_Labs Plan 9 by Bell Labs] on a QEMU/KVM virtual machine by just following the prompts and entering defaults. In certain cases, you might find your install booting to a shell with the errors:
+
+```
+aux/vga: inportl(0xc100): permission denied
+rio: can't open display: initdisplay: /dev/draw/new: no frame buffer
+init: rc exit status: rio 31: display open
+
+[image ./img/boot-prompt-no-frame-buffer-error.png ]
+
+For some reason, on certain configurations, the `[xga]` (`[vga]`) monitor type does not work when booting into Plan 9, even though it works fine during install. The fix is to adjust monitor settings to `[vesa]`:
+
+:ordered
+1. In the shell prompt enter
+
+ ```
+aux/vga -m vesa -l
+
+ You should get a cursor and a cleared prompt.
+
+ .p [image ./img/manual-prompt.png ]
+
+2. In this "new" shell prompt, enter
+
+ ```
+rio
+
+ You should now get a grey background with the cursor in it.
+
+ .p [image ./img/manual-rio.png ]
+
+ .p
+ .bulleted
+ - You are now in a graphical environment, so technically you can stop here. The other steps are for configuring it so you wont ever have that problem again.
+
+3. Create a new window (refer to the bullet point for instructions). Enter
+
+ ```
+9fat:
+
+ and afterwards
+
+ ```
+sam /n/9fat/plan9.ini
+
+ this is the configuration file we will be changing.
+
+ .p [image ./img/rio-9fat-commands.png ]
+
+ .p
+ .bulleted
+ - How to make a window: right click, hold, hover over "New" and release the right click. Now right click somewhere in the top left, hold, drag to somewhere in bottom right, release.
+
+4. Now we will be editing the config file with sam, a line editor. Click the green-backgrounded box, the cursor should appear.
+ First select our file:
+
+ ```
+b /n/9fat/plan9.ini
+
+ and click the green-backgrounded box.
+ Then replace `[xga]` with `[vesa]`:
+
+ ```
+, x/xga/ s/xga/vesa
+
+ and click the green-backgrounded box again. We're almost done here, enter `[w]`, wait a bit, and finally enter `[q]`.
+
+ :p
+ :bulleted
+ - If you want to check whether the file was properly saved, feel free to run
+
+ ```
+cat /n/9fat/plan9.ini
+
+ and check that monitor is equal to vesa (you can scroll with the arrow keys, or with left and right mouse buttons, acting as up and down).
+
+ .p [image ./img/rio-plan9ini-cat.png ]
+
+ - The first command opens the `[plan9.ini]` file for editing, and the second command, finds every line that contains `[xga]` (there should probably be only one) and on each matching line replaces `[xga]` with `[vesa]`. Refer to the [url https://p9f.org/sys/doc/sam/sam.html docs] for more information.
+
+
+
+5. That's it, all we have to do is halt our file system with `[fshalt]` (or type out the command in the [url https://9p.io/wiki/plan9/Installing_Plan_9_on_Qemu/ Qemu installation guide]) and Force Reset the virtual machine.
+
+
+The next time you boot into Plan 9 and into your user, the graphical environment should load fine. Enjoy Plan 9!
+
+[image ./img/rio-default-login.png ]