Re: the GGI-over-/dev/fb blues
Do the mouse events work in the GGI applications (the monitest uses the mouse in the Flatpanel test for example) ? no, they don't. O.K. - the mouse is incorrectly cofigured somewhere. Presumably in the svgalib config files that are as well read by LibGGI. I tried Jon's suggestion and set the GGI_FBDEV_OPTIONS to -novt. No. That will not help. It effectively disables Linux-specific support for some inputs. 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... Yes. This is the expected behaviour. This is done in $(prefix)/etc/ggi/input/linux-mouse, as documented in lib/libgii/doc/inputs.txt . hmm. The file linux-mouse didn't even exist. Yes. This is on purpose, as it normally autodetects, if no file is given. I created it and tried a couple of different devices. XF86Config contains the protocol 'PS/2', the mouse is a LogiTech. O.K. - if it is a PS/2 mouse, it should work with the ps/2 driver. So I tried both, ps2 and mmanps2 (as suggested by the docs). My linux-mouse file now contains one line: mmanps2 Still no success. Um - you read the docs to the end, did you ? It expects -- snip mouse ps2 mdev /dev/psaux -- snip to be in the file. The latter entry can probably be pointed to /dev/mouse, given a proper symlink. Also, I tried to install the kgi module, without success. The virtual consoles (beside the one running X) become essentially unreadable. Though the graphic card was correctly detected. What card ? Maybe this is an unstable driver. the configure tool reports: 'ATI Mach64 GT (Rage II) found. Using VGA driver' That means, that the card can be detected, but only the VGA driver is available for it, which is pretty much useless for something like Berlin. Try using either the kernel-provided ATI-fb driver (it doesn't state explicitly, though, if the Rage II is supported), or the kernel-provided VESA driver. If that doesn't work, you can still resort to XFree-DGA in order to get a fullscreen-demo for Berlin. CU, ANdy -- = Andreas Beck| Email : [EMAIL PROTECTED] =
Getting there, Was: the GGI-over-/dev/fb blues
Andreas Beck wrote: Um - you read the docs to the end, did you ? It expects -- snip mouse ps2 mdev /dev/psaux -- snip to be in the file. The latter entry can probably be pointed to /dev/mouse, given a proper symlink. I did read the docs, yet it was not obvious that the file should look like the above. Anyway, I did it, then I changed read permissions for /dev/psaux, et voila ! Now a question: when I move the mouse, the queue will fill up rapidly with events. I'd like to be able to 'compress' them, i.e. to only process the last move event from a series. Such a series of course needs to be contigous, i.e. as soon as there is a click or other event, I need to stop compressing since the current mouse position may matter. It would be nice to have such a GGI (GII) function. The simples would be a function which lets me inspect the next event without removing it from the queue, such that I can do the rest myself. Best regards, Stefan PS: it starts to be much fun ! ___ Stefan Seefeld Departement de Physique Universite de Montreal email: [EMAIL PROTECTED] ___ ...ich hab' noch einen Koffer in Berlin...
Re: the GGI-over-/dev/fb blues
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. If mouse doesn't work for the ggi demos, it probably isn't configured correctly. This is done in $(prefix)/etc/ggi/input/linux-mouse, as documented in lib/libgii/doc/inputs.txt . hmm. The file linux-mouse didn't even exist. I created it and tried a couple of different devices. XF86Config contains the protocol 'PS/2', the mouse is a LogiTech. So I tried both, ps2 and mmanps2 (as suggested by the docs). My linux-mouse file now contains one line: mmanps2 Still no success. What is your /dev/mouse linked to? Does GPM work? Also, I tried to install the kgi module, without success. The virtual consoles (beside the one running X) become essentially unreadable. Though the graphic card was correctly detected. What card ? Maybe this is an unstable driver. the configure tool reports: '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. Jon --- 'Cloning and the reprogramming of DNA is the first serious step in becoming one with God.' - Scientist G. Richard Seed
the GGI-over-/dev/fb blues
hi, I'm once again trying to run berlin-over-fb. Therefor I installed a new snapshot of GGI. Some comments: the install stops in libwmh, it seems you didn't update some changes you did elsewhere (the new module loading stuff ?). Anyway, since I don't need libwmh, I just proceeded. I have the usual vesa stuff installed with the kernel, so I can use the GGI demo applications. It seems to work fine. Running berlin I can't seem to get any mouse events. To start a client, I switch to the X console. Switching back, I get the client drawn (the renderer I use is libart based with a memory visual, then copying to /dev/fb). However, the background isn't cleared. Instead, I still see a 'snapshot' of my X desktop. Can anybody help ? Also, I tried to install the kgi module, without success. The virtual consoles (beside the one running X) become essentially unreadable. Though the graphic card was correctly detected. Thanks, Stefan ___ Stefan Seefeld Departement de Physique Universite de Montreal email: [EMAIL PROTECTED] ___ ...ich hab' noch einen Koffer in Berlin...
