Video mode problem after installation on QEMU
Artem Novikov
During installation I chose 1024x768x24 vesa mode, and all was OK. But
after reboot and logged under glenda, I have blank screen, also the
same result after
aux/vga -m vesa -l 1024x768x24
Any suggestion?
Ethan Grammatikidis
Not a useful suggestion, just a note to anyone who who has a little
time and knows anything about the boot and installation processes
that this needs fixing. This is the 4th or 5th time a first-time
installer has had this trouble in the last week or two.
erik quanstrom
try a 16 bit mode.
- erik
Venkatesh Srinivas
-- vs
Artem Novikov
On 23 ноя, 21:45, m...@acm.jhu.edu (Venkatesh Srinivas) wrote:
> Use -vga std at the qemu command line. All of the modes work okay then.
>
> -- vs
Thanks for the replies.
1. -vga std/vmware options on QEMU have no effect
2. bit mode change has no effect too (only "artefact line" on top of
blank screen change its color)
3. during installation or booting from CD all works perfect....
erik quanstrom
> 1. -vga std/vmware options on QEMU have no effect
> 2. bit mode change has no effect too (only "artefact line" on top of
> blank screen change its color)
> 3. during installation or booting from CD all works perfect....
ok, then assuming it's not kernel build differences,
you have all the variables at your disposal:
/n/sources/plan9/sys/lib/dist/pc/plan9.ini.cd
look for differences with your .ini. i thought the install
usually set *nomp=1, but if it's unset, that'd be my first
bet. otherwise, the video mode must be differently
set when you boot from cd.
- erik
Artem Novikov
differences are found
*nomp=1
*nobiosload=1
*nodumpstack=1
2. After installing the monitor = ask and vgasize = ask, was loaded
into the default mode 640x480x8 (xga)
3. vga, vesa does not work
4. Maybe there is some difference in the kernels?
plan9.ini.cd
bootfile=sdD0!cdboot!9pcflop.gz
plan9.ini
bootfile=sdC0!9fat!9pcf
Lucio De Re
> Date: Thu, 25 Nov 2010 09:46:15 GMT
> From: Artem Novikov <novi...@gmail.com>
> To: 9f...@9fans.net
> Subject: Re: [9fans] Video mode problem after installation on QEMU
>
> On 24 ноя, 20:52, quans...@quanstro.net (erik quanstrom) wrote:
> 1. I compared the files plan9.ini.cd and plan9.ini, and no significant
> differences are found
>
> *nomp=1
This one has far-reaching effects. I presume it is not set in the
installed system? Erik actually pointed that out in his message.
> *nobiosload=1
> *nodumpstack=1
>
> 2. After installing the monitor = ask and vgasize = ask, was loaded
> into the default mode 640x480x8 (xga)
> 3. vga, vesa does not work
> 4. Maybe there is some difference in the kernels?
>
> plan9.ini.cd
> bootfile=sdD0!cdboot!9pcflop.gz
>
> plan9.ini
> bootfile=sdC0!9fat!9pcf
>
Not likely, they are derived from the same code base. If differences
can be identified, they should probably be eliminated. But it's hard
to look. The real difference is the inclusion of a RAMdisk in pcflop,
if memory serves.
++L
Artem Novikov
On 25 ноя, 17:12, lu...@proxima.alt.za (Lucio De Re) wrote:
> On Thu, Nov 25, 2010 at 09:46:15AM +0000, Artem Novikov wrote:
> > Date: Thu, 25 Nov 2010 09:46:15 GMT
> > To: 9f...@9fans.net
> > Subject: Re: [9fans] Video mode problem after installation on QEMU
>
> > On 24 ноя, 20:52, quans...@quanstro.net (erik quanstrom) wrote:
> > 1. I compared the files plan9.ini.cd and plan9.ini, and no significant
> > differences are found
>
> > *nomp=1
>
> This one has far-reaching effects. I presume it is not set in the
> installed system? Erik actually pointed that out in his message.
>
> > *nobiosload=1
> > *nodumpstack=1
>
> > 2. After installing the monitor = ask and vgasize = ask, was loaded
> > into the default mode 640x480x8 (xga)
> > 3. vga, vesa does not work
> > 4. Maybe there is some difference in the kernels?
>
> > plan9.ini.cd
> > bootfile=sdD0!cdboot!9pcflop.gz
>
> > plan9.ini
> > bootfile=sdC0!9fat!9pcf
>
> Not likely, they are derived from the same code base. If differences
> can be identified, they should probably be eliminated. But it's hard
> to look. The real difference is the inclusion of a RAMdisk in pcflop,
> if memory serves.
>
> ++L
1. *nomp=1 set by default after installation
2. --- plan9.ini.cd
[menu]
menuitem=install, Install Plan 9 from this CD
menuitem=cdboot, Boot Plan 9 from this CD
[common]
*nomp=1
*nobiosload=1
*nodumpstack=1
partition=new
mouseport=ask
monitor=ask
vgasize=ask
dmamode=ask
adisk=/dev/sdD0/cdboot
cdboot=yes
[install]
nobootprompt=local!/boot/bzroot
bootfile=sdD0!cdboot!9pcflop.gz
[cdboot]
bootargs=local!#S/sdD0/data
bootfile=sdD0!cdboot!9pccd.gz
--- plan9.ini (after installation)
bootfile=sdC0!9fat!9pcf
bootargs=local!#S/sdC0/fossil
bootdisk=local!#S/sdC0/fossil
*nobiosload=1
*nodumpstack=1
*nomp=1
dmamode=ask
partition=new
mouseport=ps2
monitor=vesa
vgasize=1024x768x24
Lucio De Re
>
> 1. *nomp=1 set by default after installation
> 2. --- plan9.ini.cd
>
My approach would be to try to build 9pcf from sources as at the same
date as 9pcflop.gz, probably build both and see how closely they match
what gets installed. After that, it's binary division to find where
things went wrong, I suppose. I'd offer to do it, but I know I'd never
keep my promise :-(
++L
Artem Novikov
I found workaround. After installation need rebuild terminal kernel
'pcf', and replace installed, after that all seems works fine. Maybe
need modify CD installation image?
Thanks.