diff options
1 files changed, 18 insertions, 17 deletions
| -rw-r--r-- | src/blog/fix-no-frame-buffer-plan9/index.du | 35 |
diff --git a/src/blog/fix-no-frame-buffer-plan9/index.du b/src/blog/fix-no-frame-buffer-plan9/index.du index 8d63c0b..fe21454 100644 --- a/src/blog/fix-no-frame-buffer-plan9/index.du +++ b/src/blog/fix-no-frame-buffer-plan9/index.du @@ -1,20 +1,20 @@ -# Fix "No frame buffer" error in Plan 9 +'def title Fix 'No frame buffer' error in Plan 9 +'def desc Installing Plan 9 by Bell Labs on QEMU/KVM might give an initdisplay error. To fix it, you'll need to change the monitor type from xga to vesa. -'define expected-reading 3 min -'define created 30 July 2022 -'define edited 30 July 2022 -[$pagenav] +# {title} -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: +{pagenav 3 min;30 July 2022;30 July 2022} + +Let's say you installed {url Plan 9 by Bell Labs;https://en.wikipedia.org/wiki/Plan_9_from_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] +{img ./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`]: +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 @@ -22,9 +22,10 @@ For some reason, on certain configurations, the [`xga`] ([`vga`]) monitor type d ``` aux/vga -m vesa -l + .p You should get a cursor and a cleared prompt. - [image ./img/manual-prompt.png] + {img ./img/manual-prompt.png} 2. In this "new" shell prompt, enter @@ -33,7 +34,7 @@ rio You should now get a grey background with the cursor in it. - [image ./img/manual-rio.png] + {img ./img/manual-rio.png} .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. @@ -50,7 +51,7 @@ sam /n/9fat/plan9.ini this is the configuration file we will be changing. - [image ./img/rio-9fat-commands.png] + {img ./img/rio-9fat-commands.png} .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. @@ -62,12 +63,12 @@ sam /n/9fat/plan9.ini b /n/9fat/plan9.ini and click the green-backgrounded box. - Then replace [`xga`] with [`vesa`]: + 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`]. + and click the green-backgrounded box again. We're almost done here, enter {` w}, wait a bit, and finally enter {` q}. :unordered - If you want to check whether the file was properly saved, feel free to run @@ -77,14 +78,14 @@ 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). - [image ./img/rio-plan9ini-cat.png] + {img ./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. + - 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 docs;https://p9f.org/sys/doc/sam/sam.html} 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. +5. That's it, all we have to do is halt our file system with {` fshalt} (or type out the command in the {url Qemu installation guide;https://9p.io/wiki/plan9/Installing_Plan_9_on_Qemu/}) 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] +{img ./img/rio-default-login.png} |