> I tried several times last week to subscribe to various ggi/kgi mailing
> lists without sucess
Hmm - most of the kludge.org stuff seems dead - but it isn't used much
anyway. Please try the [EMAIL PROTECTED] .
IIRC subscriptions go through [EMAIL PROTECTED] . But detailed
instructions should be on the website.
Forget about the kludge.org lists. We set them up due to popular demand to
split stuff, but then almost noone subscribed to the right lists so most
traffic is still on ggi-develop.
> I have done countless mail subscriptions before elsewhere without any
> problems so I am inclined to think you automatic mail deamon doesn't like
> me.
The mail you got from the kludge.org list manager seems in deed weird.
> If you can bypass the system and get me on the lists anyway then please
> do so.
No, sorry. For eskimo.com you can ask [EMAIL PROTECTED], who is the list
manager.
> Yes I catted files to the dev/fb and dev/fb0 files and got screeds of
> garbage on the screen.
How did it look like ? Graphics garbge or text garbage ? I.e. simply colored
dots or strange colored characters ?
> I have also done intensive tests around the stars demo using lots of
> different environment options... It tends to crash very reliably on the
> ggiOpen command and the last ggi debug (255 level) message is "L /vtswitch:
> Using VT 1" (or VT 2 if chosen). Then the screen locks and only responds to
> the q key which clears the screen entirely but the system remains fully dead
> with no response even to magic key combo's.
That is strange. As you say "q" kind of works, this indicates that the demo
is in deed running. Please note, that the stars demo usually looks very
dark. If you have bright surroundings, you might not even notice that there
actually are stars moving around. The standard demo we usually use for
testing stuff is demo.c - it is designed to test as much features as
possible.
> I will try to take this further, I am still fairly new to ggi and even linux
> so I would appreciate any further help you can pass on.
Please run the "demo" demo and save away GGI_DEBUG=255 output (it comes out
on stderr, so use 2>bla to redirect it to a file) and in another run strace
output (also on stderr) and send them along. Would give a clue where stuff
crashes.
A common thing to happen was problems with restoring keyboard-mode. If you
have SAK enabled, you might try the SAK-r sequence and then eventually try
to shut down stuff "blindly", if the video subsystem also has problems.
Another trick to try in that case might be to run the demo from mc (without
being root). This will cause the program to be unable to set the keyboard
to raw mode and thus fall back to using the stdin method.
CU, ANdy
--
= Andreas Beck | Email : <[EMAIL PROTECTED]> =
