nanogui: Starting Nano-X on /dev/fb1 problem
Subject:
Re: [nanogui] Starting Nano-X on /dev/fb1 problem
From:
####@####.####
Date:
15 Jul 2002 03:06:29 -0000
Message-Id: <OFD39253D7.8FB407F2-ON4A256BF7.000F09CB@jupiters.com.au>
Thanks for the reply Greg.
VTSWITCH doesn't seem to make a difference.
Below are the only options that I have enabled in my config config file
.....
OPTIMIZE = Y
MICROWIN = Y
NANOX = Y
MICROWINDEMO = Y
NANOXDEMO = Y
NANOWM = Y
HAVE_FILEIO = Y
HAVE_BMP_SUPPORT = Y
HAVE_GIF_SUPPORT = Y
HAVE_PNM_SUPPORT = Y
HAVE_XPM_SUPPORT = Y
HAVE_FREETYPE_SUPPORT = Y
ERASEMOVE = Y
UPDATEREGIONS = Y
USE_EXPOSURE = Y
FRAMEBUFFER = Y
NOMOUSE = Y
NOKBD = Y
In a bizzare twist, if I load nano-X during startup while Aurora has focus,
the switch from Aurora to vc/1 works, and everything is fine.
If I disable Aurora with the same scripts, I'm back to where I started.
BTW : Forgot to mention in first post : using Mandrake Linux 8.1 standard
distro.
Regards,
Steve.
"Greg Haerr"
<greg@censoft To: ####@####.#### ####@####.####
.com> cc:
Subject: Re: [nanogui] Starting Nano-X on /dev/fb1 problem
15/07/02
11:15 Project:
> My problem is when I start nano-X from the console using fb0, I no longer
> get screen updates for the console until nano-X is killed.
>
> The console is still active - I can type in and start new nano-X
> applications, and they appear on the LCD.
>
> When "killall nano-X" is typed to kill nano-X, my console comes back, and
I
> have a full history of what I've typed.
You might try compiling with the config option VTSWITCH=N
and see if anything different happens.
Regards,
Greg
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
####@####.####
**********************************************************************
