On Mon, May 24, 2010 at 12:00:14AM +0100, Ethan Grammatikidis wrote:
> Is it possible to limit the frame rate aux/vga sets? The reason I'm
> asking is:
No idea.
>> Whatever I use for monitor (vesa, vga) or vgasize, the
>> screen just turns black and the led of the monitor is blinking.
>
> I've
Is it possible to limit the frame rate aux/vga sets? The reason I'm
asking is:
On 23 May 2010, at 22:41, fr...@inua.be wrote:
Whatever I use for monitor (vesa, vga) or vgasize, the
screen just turns black and the led of the monitor is blinking.
I've had quite a lot of CRT monitors in the pa
On Sat, May 22, 2010 at 08:01:40PM -0400, erik quanstrom wrote:
> > However, when this box boots via PXE, it has the same issue... Any
> > idea what might be wrong?
>
> perhaps vgasize or monitor is unset. try
>
> vgasize=1280x1024x16# adjust as appropriate. cf. vga(8)
> monitor
On Sun, May 23, 2010 at 12:26:07PM +0100, Richard Miller wrote:
> > Apparently, /sys/lib/newuser creates an
> > "incorrect" /usr//lib/profile. In case of a terminal, it tries
> > to start rio without first configuring the vga card. Why is it like
> > that?
>
> Because /rc/bin/termrc does 'aux/vga
> Apparently, /sys/lib/newuser creates an
> "incorrect" /usr//lib/profile. In case of a terminal, it tries
> to start rio without first configuring the vga card. Why is it like
> that?
Because /rc/bin/termrc does 'aux/vga -l $vgasize'
But only if all these are true:
test -f /dev/mousectl
~ $m
On Sat, May 22, 2010 at 08:01:40PM -0400, erik quanstrom wrote:
> > However, when this box boots via PXE, it has the same issue... Any
> > idea what might be wrong?
>
> perhaps vgasize or monitor is unset. try
>
> vgasize=1280x1024x16# adjust as appropriate. cf. vga(8)
> monitor
> However, when this box boots via PXE, it has the same issue... Any
> idea what might be wrong?
perhaps vgasize or monitor is unset. try
vgasize=1280x1024x16# adjust as appropriate. cf. vga(8)
monitor=vesa
aux/vga -l $vgasize
- erik
Hello,
I tried to boot an AMD Geode LX400 system ("mini PC") using PXE but,
after logging in as a normal user, always got complaints from rio that
it couldn't open a display, more specifically: "initdisplay:
/dev/draw/new: no frame buffer".
As my cpu/auth server is running on a Via Epia ESP5000 a
