Hi!
Upgraded 1.0.0 -> 1.0.2 today.
Under X everything looks ok, but fb looks broken.
I have a G200, so I get “Matrox hardware acceleration!”
Running my own program gives a segmentation violation (thats german
"Speicherzugriffsfehler" in english, or ? 
where do I set english errors
in Suse …? )
I’m quite sure I forgot locking the surface somewhere…
Trying to run testvidinfo from the demo programs gives
"Couldn’t initialize SDL: Unable to open mouse"
Both with und without gpm.
/dev/mouse is rwxrwxrwx
Changing to root, running testvidinfo again, works.
Now SDL can initialise the mouse?, strange …
So I try to run my own program as root…
And get a solid black screen.
Even after program exit.
Have to blindly type reboot.
So I guess Matrox hardware accel is not working on my G200, some way to
disable that and get back to software mode ?
I don’t need mouse at all, is there some way to completely deactivate
that subsystem ?
I’m downgrading to 1.0.0 now…
Some other things:
The mailings list archives are quite large now, you make the phone company
happy… Please split it up. (No, ml subscribing is not an option)
I still fail to crosscompile SDL with cygwin, guess someone with more
knowledge auf configure and Windows libs has to come along and create
proper configurations for the SDL build process, I’m giving up.
Regards,
Martin
Under X everything looks ok, but fb looks broken.
I have a G200, so I get “Matrox hardware acceleration!”
Running my own program gives a segmentation violation (thats german
“Speicherzugriffsfehler” in english, or ? 
where do I set english errors
in Suse …? )
I’m quite sure I forgot locking the surface somewhere…
This is probably the problem.
Trying to run testvidinfo from the demo programs gives
“Couldn’t initialize SDL: Unable to open mouse”
Both with und without gpm.
/dev/mouse is rwxrwxrwx
Changing to root, running testvidinfo again, works.
Now SDL can initialise the mouse?, strange …
What type of mouse do you have?
What are the permissions on /dev/psaux?
So I try to run my own program as root…
And get a solid black screen.
Even after program exit.
Have to blindly type reboot.
Does this happen with the included test programs?
So I guess Matrox hardware accel is not working on my G200, some way to
disable that and get back to software mode ?
I will add an environment variable to the next release.
I don’t need mouse at all, is there some way to completely deactivate
that subsystem ?
I will add an environment variable to the next release.
The mailings list archives are quite large now, you make the phone company
happy… Please split it up. (No, ml subscribing is not an option)
Try the newsgroup:
news://news.lokigames.com/loki.open-source.sdl
I still fail to crosscompile SDL with cygwin, guess someone with more
knowledge auf configure and Windows libs has to come along and create
proper configurations for the SDL build process, I’m giving up.
Check out:
http://www.devolution.com/~slouken/SDL/Xmingw32/
See ya!
-Sam Lantinga (slouken at devolution.com)
Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec
Sam Lantinga wrote:
Trying to run testvidinfo from the demo programs gives
"Couldn’t initialize SDL: Unable to open mouse"
Both with und without gpm.
/dev/mouse is rwxrwxrwx
Changing to root, running testvidinfo again, works.
Now SDL can initialise the mouse?, strange …
What type of mouse do you have?
What are the permissions on /dev/psaux?
3 button logitech connected via serial com1 via ms protocol
thus gpm is started with
/usr/sbin/gpm -t ms -m /dev/mouse
ls -la /dev/mouse gives
lrwxrwxrwx root root /dev/mouse -> /dev/ttyS0
ls -la /dev/psaux gives
crw-rw-r-- root root /dev/psaux
this is how Suse installed my mouse
So I try to run my own program as root…
And get a solid black screen.
Even after program exit.
Have to blindly type reboot.
Does this happen with the included test programs?
yes, tried graywin
gives a 100% white screen on run and black screen on exit
blind reboot…
So I guess Matrox hardware accel is not working on my G200, some way to
disable that and get back to software mode ?
I will add an environment variable to the next release.
tnx
I don’t need mouse at all, is there some way to completely deactivate
that subsystem ?
I will add an environment variable to the next release.
how about a configure option, too ? 
The mailings list archives are quite large now, you make the phone company
happy… Please split it up. (No, ml subscribing is not an option)
Try the newsgroup:
news://news.lokigames.com/loki.open-source.sdl
I may not be visible from the header, this was posted via the newsgateway.
Loading the html archive list or the newsreader reading 1700+
article headlines, either way it’s the same waste of bandwidth.
This list cannot grow forever, sooner or later you have to split it up,
why not do it now ?
I still fail to crosscompile SDL with cygwin, guess someone with more
knowledge auf configure and Windows libs has to come along and create
proper configurations for the SDL build process, I’m giving up.
Check out:
http://www.devolution.com/~slouken/SDL/Xmingw32/
I know of the mingw way, but I need the cygwin unix emulation. Porting the
main code from cygwin to mingw would be more work than writing my own
graphics lib for win… 
Regards,
Martin
Running my own program gives a segmentation violation (thats german
"Speicherzugriffsfehler" in english, or ?
Yep.
where do I set english errors in Suse …? )
There might be an environment-variable LANG or LANGUAGE or somesuch,
unset this or setting it to en might help.
I’m quite sure I forgot locking the surface somewhere…
Trying to run testvidinfo from the demo programs gives
"Couldn’t initialize SDL: Unable to open mouse"
Both with und without gpm.
/dev/mouse is rwxrwxrwx
Changing to root, running testvidinfo again, works.
Now SDL can initialise the mouse?, strange …
So I try to run my own program as root…
And get a solid black screen.
Even after program exit.
Have to blindly type reboot.
Is that X now ? If so it might be that you have some broken screen-modes
defined which are not normaly used and therefore make no problems.
This happened to me, SDL switched to the most apropriate looking mode, but
it did not work => black screen. Test all your modes with ctrl,alt,+/- to
see if they normaly work.
Hope that helps,
robOn Mon, Jan 24, 2000 at 01:19:52PM +0000, Martin Pirker wrote:
So I try to run my own program as root…
And get a solid black screen.
Even after program exit.
Have to blindly type reboot.
Is that X now ? If so it might be that you have some broken screen-modes
defined which are not normaly used and therefore make no problems.
This happened to me, SDL switched to the most apropriate looking mode, but
it did not work => black screen. Test all your modes with ctrl,alt,+/- to
see if they normaly work.
This was a bug in SDL. It is fixed in SDL 1.0.3, to be released tomorrow.
See ya!
-Sam Lantinga (slouken at devolution.com)
Lead Programmer, Loki Entertainment Software–
“Any sufficiently advanced bug is indistinguishable from a feature”
– Rich Kulawiec
Sam Lantinga wrote:
This was a bug in SDL. It is fixed in SDL 1.0.3, to be released tomorrow.
FYI: I just now tried 1.0.2 (devel runtime) on Win2k RC2 in VMware
1.1.2. My game now runs! (Of course, it doesn’t really do anything yet.
But it looks the same as in Linux.)–
Marc A. Lepage
Software Developer
Molecular Mining Corporation
http://www.molecularmining.com/