nanogui@linuxhacker.org

One thing that might be useful to know....when I ran
"landmine" on the ATI 3D Rage Pro card using 0301, the
whole screen became very dim!!


- This seems like you might be running in 16bpp
or something rather than 8bpp.  I use an ATI Rage
card for Microwindows development, and it works
great in 8, 24, and 32bpp, but the palette is too
light for 16bpp, and the screen is quite dim.

- You need the fbset program, which allows you to
change the resolutions of your screen at runtime.
You can search the net for it, if you can't
find it, I'll post it on the Microwindows ftp
site.

- Also, you probably need to try first running
in the brain-dead VGA 16 color mode, since
that's the ONLY mode that supported by all
PC's when running in fb mode.  This mode
can be forced by turning off support for
any card-specific fb mode in the kernel
and recompiling, rebooting...  Make sure
you check dmesg to see if you're running
the vga16 fb driver.

Anyone out there who actually managed to get
Microwindows running using the Framebuffer option? :)

- Oh yes.  That's the only option I use.  The problem
is in your kernel config, most definitely.

Regards,

Greg



Could someone please tell me how I might be able to
solve this problem? I'm getting kinda desperate! :)

Regards,
Supriyo

--- Alex Holden <alex@linuxhacker.org> wrote: > On
Tue, 5 Dec 2000, Tasnim Ahmed wrote:
> > # gpm -R -t imps2
> 
> Just to clarify this, you need to run gpm in
> repeater mode by starting it
> with the -R flag. This causes it to write mouse data
> in mouse-systems
> format (regardless of the kind of mouse) to a fifo
> at /dev/gpmdata whilst
> in graphics mode. There is a problem with this in
> that the mouse-systems
> format doesn't include any wheel data, so in order
> to use the wheel under
> X, you need to use the native X mouse driver in
> IMPS/2 mode. But if you're
> already running gpm in repeater mode, it will also
> try to read /dev/psaux
> when in graphics mode (at the same time as X) and
> the mouse data will be
> corrupted. So if you use gpm in repeater mode and
> tell X to use
> /dev/gpmdata you can't use the wheel, and if you use
> gpm in non repeater
> mode and tell X to use /dev/psaux you can't use
> Nano-X in framebuffer mode
> without restarting gpm. Long term, we should really
> write our own mouse
> drivers- the gpm code is a mess anyway, plus a
> typical embedded system
> wouldn't use it so it's a waste of resources
> (memory, flash or disk 
> space, and processor time). We'll also need to do it
> to get wheel support.
> 
> -- 
> ------- Alex Holden -------
> http://www.linuxhacker.org/
>  http://www.robogeeks.org/
> 


__________________________________________________
Do You Yahoo!?
Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com.sg/

---------------------------------------------------------------------
To unsubscribe, e-mail: nanogui-unsubscribe@linuxhacker.org
For additional commands, e-mail: nanogui-help@linuxhacker.org