"Jon M. Taylor" wrote:
>
> On Thu, 18 May 2000, Stefan Seefeld wrote:
>
> > Andreas Beck wrote:
> >
> > > Do the mouse events work in the GGI applications (the monitest uses the
> > > mouse in the Flatpanel test for example) ?
> >
> > no, they don't. I tried Jon's suggestion and set the GGI_FBDEV_OPTIONS to
> > -novt. This screwed things up even more, i.e. now the application doesn't
> > react to events at all and I get a terminal writing over the application...
>
> Sorry about that. I guess you'll need to turn on GGI_DEBUG=255,
> do whatever you need to do to get debugging output from Berlin, and run it
> on the console. Make sure to redirect the output to a file, including
> STDERR. Once it has frozen, use the magic SysRq key alt-prtscrn-r to turn
> off RAW mode so you can once again switch VCs. Switch to another VC,
> login and kill the berlin process(es), and send us the compressed logs.
ok, will do. By the way, I can switch between VC's. Keyboard seems to work.
> What is your /dev/mouse linked to? Does GPM work?
lrwxrwxrwx 1 root root 5 Jan 7 13:38 /dev/mouse -> psaux
> > 'ATI Mach64 GT (Rage II) found. Using VGA driver'
>
> The kgicon VGA driver has problems, and I don't know if the ATI
> driver ever worked. I think there is a kernel ATI driver (aty128fb) which
> you can use and which works better than the kgicon driver.
right. I installed vesa fb support into the kernel and it works fine.
I only installed kgi because I hoped it would help and because the kgi module
is asked for in one of the configuration files. I commented it out now...
Stefan
_______________________________________________________
Stefan Seefeld
Departement de Physique
Universite de Montreal
email: [EMAIL PROTECTED]
_______________________________________________________
...ich hab' noch einen Koffer in Berlin...
