nanogui: Compiling nano-X (SVGAlib) under Linux Mandrake 8
Subject:
Re: [nanogui] Compiling nano-X (SVGAlib) under Linux Mandrake 8
From:
David Douthitt ####@####.####
Date:
29 Jun 2001 15:26:38 -0000
Message-Id: <3B3C9019.D1C5854E@mailbag.com>
Jordan Crouse wrote:
> In this situation, it means that the value that was passed in to KDGKBMODE
> was invalid - most likely because /dev/tty doesn't really handle the
> KDGKBMODE command. Thats because /dev/tty is a odd device - It is the
> standard device that use used to read the keyboard, but traditionally it is
> just linked another keyboard device (usually /dev/console). My assumption
> is that since /dev/tty is a true device on your system and not a link to a
> more common keyboard device, you are having these problems.
I tried it, now I get this:
$ bin/nano-X
KDSETLED: Operation not permitted
KDSKBMODE: Operation not permitted
Cannot initialise keyboard
$
Then something occurred to me, and I think this may be relevant....
On the 2.4.3 system, I was using a vnc rxvt terminal to attempt running
microwin. On the 2.2.16 system, I was using a slogin into the system to
do the same thing.
I tried running bin/nano-X by itself (a mistake??) on the system console
of the 2.4.3 system and then switched to a second virtual terminal.
Then switched back and was stuck (no mouse movement either). I killed
it from an X terminal, and now I can't switch virtual terms and have no
shell on that tty ( /dev/tty1 ).
Looks like its time to reboot - it needed it anyway :-)
More things I've noticed:
I selected SERMOUSE (serial mouse?) but perhaps I should have selected
PS2MOUSE - only where is that? I'm not using gpm in the target
environment...
Also, should I have selected TTYKBD instead of SCANKBD? Or should I use
PIPEKBD? There's no description of which is what.
