nanogui: Problem running demos when using Framebuffer option
Subject:
Re: Problem running demos when using Framebuffer option
From:
Jordan Crouse ####@####.####
Date:
6 Dec 2000 18:01:15 -0000
Message-Id: <3A2E7F44.8E7B2479@censoft.com>
Which binary in particular, or is it all of them?
Supriyo Chatterjea wrote:
>
> I was trying to run the demos in the
> /microwindows/src/bin/ directory.
>
> I'm using a Dell Dimension...PII 300
> using the nVidia RIVA TNT2 M64 card...
> Also tried it on a Dell Optiplex PII 400...using a ATI
> 3D Rage Pro card...
>
> similar problems with both PCs...
>
> -Supriyo
> u
> --- "Gray, Tim" ####@####.#### wrote: >
> Yes, I have the framebuffer option running. It's on
> > my target platform that
> > is using the dreaded mediaGX processor
> > (video/audio/io/everything in the
> > processor-- YUCK) but it is working.
> >
> > I used the config.fb and modified it for my hardware
> > platform slightly I
> > think I changed one setting I'll diff it later and
> > let you know.
> >
> > as for your VGA setting I had the opposite problem,
> > I had to use the
> > decimal instead of the 0301 to get framebuffer to
> > work. What demo is
> > failing on you? I'll try it here and see if it
> > fails on my setup also.
> >
> >
> >
> > -----Original Message-----
> > From: Supriyo Chatterjea
> > ####@####.####
> > Sent: Wednesday, December 06, 2000 11:15 AM
> > To: ####@####.####
> > Subject: Re: Problem running demos when using
> > Framebuffer option
> >
> >
> > Hi all,
> >
> > I was really hoping I wouldn't be having to send
> > this
> > mail with all the help that you ppl have
> > given...alas...the problem just refuses to go!!!! :)
> >
> > Like I said earlier on...my Framebuffer has been set
> > up properly (I can see the penguin during booting
> > up).
> > And I'm not getting any error messages when I try to
> > run any of the Microwindows demos.
> >
> > But the problem is (and this is THE only one right
> > now!) everytime I try to run a certain demo, the
> > upper
> > portion of the screen just goes blank or starts
> > flickering in a weird manner. At times the mouse
> > dies
> > as well...but Tasnim's trick:
> >
> > # /etc/init.d/gpm stop
> > # gpm -R -t ms
> >
> > takes care of the mouse issue.
> >
> > I've tried the whole procedure on another computer
> > as
> > well (since I was thiking that probably my nVidia
> > RIVA
> > TNT2 M64 is not compatible with VESA 2.0). This
> > second
> > computer has an ATI 3D Rage Pro card...I used the
> > usual vesab drivers however....and got the same
> > results. I'm gonna try the atyfb driver tomorrow to
> > see if that works. Any idea if that might be the
> > problem?
> >
> > 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!!
> >
> > I also tried Tasnim's suggestion of using config.fb
> > instead of config....but that didn't help either!
> > And
> > his other suggestion about using 789 instead of 0301
> > didn't work as well...somehow it doesn't accept 789
> > as
> > a valid VESA mode.
> >
> > Anyone out there who actually managed to get
> > Microwindows running using the Framebuffer option?
> > :)
> >
> > Could someone please tell me how I might be able to
> > solve this problem? I'm getting kinda desperate! :)
> >
> > Regards,
> > Supriyo
> >
> > --- Alex Holden ####@####.#### 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:
> > ####@####.####
> > For additional commands, e-mail:
> > ####@####.####
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > ####@####.####
> > For additional commands, e-mail:
> > ####@####.####
> >
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Mail - Free email you can access from anywhere!
> http://mail.yahoo.com.sg/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
