termrc and aux/realemu

termrc and aux/realemu

[kokamoto]

Please rewrite the /rc/bin/termrc to load aux/realemu, 
enen if we have
monitor=vesa
vgasize=...x...x..
lines in the plan9.ini file.

Kenji

Re: [9front] termrc and aux/realemu

[Nick Owens]

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

kenji,

termrc does call aux/realemu at line 107.

		@{
			rfork n
			if(~ $monitor vesa)
				aux/realemu
			aux/vga -l $vgasize
		}

what is the problem with it?

On Thu, Aug 14, 2014 at 10:40:59AM +0900, kokamoto@hera.eonet.ne.jp wrote:
> Please rewrite the /rc/bin/termrc to load aux/realemu, 
> enen if we have
> monitor=vesa
> vgasize=...x...x..
> lines in the plan9.ini file.
> 
> Kenji
> 

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: [9front] termrc and aux/realemu

[kokamoto]

I don't like shell script, so this is from my experience.

 termrc does call aux/realemu at line 107.
> 
> 		@{
> 			rfork n
> 			if(~ $monitor vesa)
> 				aux/realemu
> 			aux/vga -l $vgasize
> 		}
> 
> what is the problem with it?

This is called only when vga and vgasize are set to be
asked?
I had to write aux/realemu line expricitly in
/cfg/xxx/termrc file.

Have you tested it when you have
monitor=vesa
vgasize=...x...x..?

Kenji

Re: [9front] termrc and aux/realemu

[Nick Owens]

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

On Fri, Aug 15, 2014 at 09:10:35AM +0900, kokamoto@hera.eonet.ne.jp wrote:
> This is called only when vga and vgasize are set to be
> asked?
> I had to write aux/realemu line expricitly in
> /cfg/xxx/termrc file.
> 
> Have you tested it when you have
> monitor=vesa
> vgasize=...x...x..?
> 
> Kenji
> 

in my thinkpad X301 plan9.ini is:

monitor=vesa
vgasize=1440x900x32

it works. when i tcpboot to my fileserver, rio starts automatically.

working as intended :-)

do you get any messages on the console when aux/realemu doesn't run?


[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: [9front] termrc and aux/realemu

[sl]

> I don't like shell script, so this is from my experience.
> 
>  termrc does call aux/realemu at line 107.
> > 
> > 		@{
> > 			rfork n
> > 			if(~ $monitor vesa)
> > 				aux/realemu
> > 			aux/vga -l $vgasize
> > 		}
> > 
> > what is the problem with it?
> 
> This is called only when vga and vgasize are set to be
> asked?
> I had to write aux/realemu line expricitly in
> /cfg/xxx/termrc file.
> 
> Have you tested it when you have
> monitor=vesa
> vgasize=...x...x..?

I think we may be misunderstanding what your situation is. The language
is too ambiguous. Can you please:

1.) describe what you did
2.) describe what you expected to happen
3.) describe what actually happened

Thanks!

sl

Re: [9front] termrc and aux/realemu

[kokamoto]

> I think we may be misunderstanding what your situation is. The language
> is too ambiguous. Can you please:
> 
> 1.) describe what you did
> 2.) describe what you expected to happen
> 3.) describe what actually happened

Ok.
my /rc/bin/termrc is the same as distribution.
My termrc.local has only one line of
TIMESYNCARGS=(-n ntp.jst.mfeed.ad.jp)

/cfg/pxe/xxxxx file is as follows:
#saturn C2D machine
bootfile=/386/9pcf
bootargs=tcp
fs=192.168.11.5
auth=192.168.11.5
mouseport=ps2intellimouse
monitor=vesa
#monitor=s2231wA
#vgasize=1024x768x16
vgasize=1400x1050x16
#vgasize=1680x1050x32
#vgasize=1600x1200x32

and /cfg/saturn/termrc has a line of
#!/bin/rc
aux/realemu

Re: [9front] termrc and aux/realemu

[kokamoto]

> I think we may be misunderstanding what your situation is. The language
> is too ambiguous. Can you please:
> 
> 1.) describe what you did
> 2.) describe what you expected to happen
> 3.) describe what actually happened

Ok.
my /rc/bin/termrc is the same as distribution.
My termrc.local has only one line of
TIMESYNCARGS=(-n ntp.jst.mfeed.ad.jp)

/cfg/pxe/xxxxx file is as follows:
#saturn C2D machine
bootfile=/386/9pcf
bootargs=tcp
fs=192.168.11.5
auth=192.168.11.5
mouseport=ps2intellimouse
monitor=vesa
#monitor=s2231wA
#vgasize=1024x768x16
vgasize=1400x1050x16
#vgasize=1680x1050x32
#vgasize=1600x1200x32

and /cfg/saturn/termrc has a line of
#!/bin/rc
aux/realemu

If I don't have the last file, it bootup with no problem.
However there is no /dev/realmode file.
To have this file I have to have the last file.

Is this Ok?

Kenji

Re: [9front] termrc and aux/realemu

[cinap_lenrek]

kenji, why do you need /dev/realmode file? the file is only used
when setting up graphics with the vesa driver which is done in
termrc. the reason you do not see the file is because termrc
*intentionally* forks the namespace and runs aux/realemu
and aux/vga in that namespace. so we wont clutter /dev
with slow userspace fileservers. it also doesnt start
realemu when you'r not using vesa. this is all intentional.

why do you need /dev/realmode file? why do you not just
set monitor=vesa and vgasize= variable to set graphics mode?
do you wish to set up graphics later in your own scripts?
in that case, you can just run aux/realemu yourself there
before running aux/vga. what are you trying todo?

--
cinap

Re: [9front] termrc and aux/realemu

[kokamoto]

> the reason you do not see the file is because termrc
> *intentionally* forks the namespace and runs aux/realemu
> and aux/vga in that namespace. so we wont clutter /dev
> with slow userspace fileservers. it also doesnt start
> realemu when you'r not using vesa. this is all intentional.

Ok, I got you intentionaly did so. Then,
I don't undestand why /dev/realmode makes the system slow.

> why do you need /dev/realmode file? why do you not just
> set monitor=vesa and vgasize= variable to set graphics mode?
> do you wish to set up graphics later in your own scripts?
> in that case, you can just run aux/realemu yourself there
> before running aux/vga. what are you trying todo?

Why we need to separate this.
You don't want user mode device should not appear in /dev?
We couldn't have /dev/realmode anytime?

If it's not good, we should make aux/vga do it automatically.
I'm wrong?

Kenji

Re: [9front] termrc and aux/realemu

[kokamoto]

> conflating aux/vga with realemu isnt right in my opinion.
> realemu can be used in many different ways and is not limited
> to running vesa bios code (see comload) and aux/vga has no
> need to depend on it directly.

Thanks cinap for kind explanation.

Kenji

Re: [9front] termrc and aux/realemu

[cinap_lenrek]

every video mode is special. aux/vga does special stuff for
every one of them like mapping mmio registers from named
hardware segments or reading/writing special control files
of the kernel half driver. vesa works with doing vesa bios
calls. /dev/realmode was initially provided by the kernel,
by doing a mode switch to realmode and executing the code.

with realemu /dev/realmode is provided by userspace fileserver
which binds over /dev and hides the kernel mode /dev/realmode
files.

these days, 9front has no kernel mode /dev/realmode anymore
as realemu works good enougth and realmode isnt even available
in 64 bit kernel. the modularity remains. this is good for
debugging, as you can run realemu with tracing modes
that let you see what io ports are read and written by
the video bios code. also, mounting and unmounting lets
us make snapshots of the bios memory areas to rerun tests
from a defined state the video bios memory. (theres the
vbt program and scripts to try to bruteforce hidden video
modes that uses this).

conflating aux/vga with realemu isnt right in my opinion.
realemu can be used in many different ways and is not limited
to running vesa bios code (see comload) and aux/vga has no
need to depend on it directly.

--
cinap

Re: [9front] termrc and aux/realemu

[kokamoto]

> All you need to do in this case is start realemu again before running aux/vga.
> This is all explained in the realemu(8) man page.

then, my question is why the vesa mode is special as compared
to other vga devices?   If aux/vga can do this automatically,
we don't need to bother with it...

Kenji

Re: [9front] termrc and aux/realemu

[sl]

> I don't like shell script, however, I think I kew this.
> Why you don't need /dev/realmode?

Well, consider the problem /dev/realmode is solving. How many times in an
average session do you need to interrogate your VESA BIOS? As cinap explained,
there is no reason to keep it around after graphics are initialized.


> I had to set up which mode is supported by my AMD card,
> then, I did
> aux/vga -i
> then, I was said there is no /dev/realmode...

All you need to do in this case is start realemu again before running aux/vga.
This is all explained in the realemu(8) man page.

sl

Re: [9front] termrc and aux/realemu

[kokamoto]

> The realemu program did run (this is why graphics mode succeeded
> in running) but the /dev/realmode file is not in your namespace.
> The default /rc/bin/termrc does this:
> 
> 		@{
> 			rfork n
> 			if(~ $monitor vesa)
> 				aux/realemu
> 			aux/vga -l $vgasize
> 		}
> 
> which forks a new namespace before running realemu. Your
> /cfg/saturn/termrc is running another copy of realemu without
> forking the namespace, so you still see /dev/realmode everywhere
> in your environment after rio is started.

I don't like shell script, however, I think I kew this.
Why you don't need /dev/realmode?
I had to set up which mode is supported by my AMD card,
then, I did
aux/vga -i
then, I was said there is no /dev/realmode...

Kenji

Re: [9front] termrc and aux/realemu

[sl]

> If I don't have the last file, it bootup with no problem.
> However there is no /dev/realmode file.
> To have this file I have to have the last file.

The realemu program did run (this is why graphics mode succeeded
in running) but the /dev/realmode file is not in your namespace.
The default /rc/bin/termrc does this:

		@{
			rfork n
			if(~ $monitor vesa)
				aux/realemu
			aux/vga -l $vgasize
		}

which forks a new namespace before running realemu. Your
/cfg/saturn/termrc is running another copy of realemu without
forking the namespace, so you still see /dev/realmode everywhere
in your environment after rio is started.

sl