BTW, I did a fresh install of Mandrake 8.0 tonight and tried aging the
startx from console and low-and-behold it things work again. not the way
I'd like them 'casue for my workstation i like the graphical login but at
least I can play quake III so I'll stick with 8.0 from here on out!
--
/****************************************************************************/
/ /
/ John Kloian III Chief Technology Officer /
/ OpNIX, Inc. http://opnix.com /
/ /
/ .Innovating Internet Intelligence. /
/ /
/****************************************************************************/
On Tue, 1 May 2001, Will wrote:
>After a little more testing, I found that GDM doesn't cause a crash on
>mode-switch, so if you have Gnome installed, you can still have a graphical
>login. Maybe this bug is an interaction between the Voodoo3 driver and KDM?
>
>A related bug - I changed /etc/sysconfig/desktop from "KDE" to "Gnome", and
>my login manager did not change. No luck setting it to "GNOME" either, so I
>added the line "preferred=gdm" at line 38 of /etc/X11/prefdm. Hard-coding
>the login manager is hardly the optimum solution, but it works for me.
>
>
>On Tuesday 01 May 2001 23:37, Francisco Alcaraz Ariza wrote:
>> Guillaume, Will Reinhart ,another user of Mandarke 8.0 with a Voodoo3 3000,
>> has made a very interesting discover; I has started in text mode (console
>> mode) and runing then startx the problem of full screen has dissapeared.
>>
>> I have tested that and actually works (full screen in Clanbomber, Pingus,
>> Pinguin command, Gltron, Tuxracer, Quake III.... ^_^ ; so perhaps the
>problem
>> is not exactly the DRI in XFree86 4.0.2 and 4.0.3 in a computer using
>Voodo3
>> 3000; it is possible that the graphical login (kdm?) is having conflict in
>> this equipments.
>>
>> What do you think? and what can we do (I actually like the graphical
>login!).
>> Is there any way to start in a different graphical login to test that?
>>
>> Thanks for your attention, yours sincerely
>>
>>
>>
>> ----------------------------------
>> Francisco Alcaraz
>> Murcia (Spain)
>>
>> El Mar 01 May 2001 15:26, escribiste:
>> > Not a real fix, but running "startx" from the console instead of booting
>> > directly into X seems to work around the problem. I was able to play
>> > tuxracer in fullscreen mode without crashing now.
>> >
>> > On Monday 30 April 2001 17:44, John Kloian III wrote:
>> > > You're right. This is what I've done thus far to try to isolate the
>> > > problem:
>> > >
>> > >
>> > > Problem:
>> > >
>> > > When changing resolutions X server crashes and restarts. when loading
>> > > Quak3 xserver crashes and restarts. when loading Chroimium in windowed
>> > > mode everything works fine including DRI, when Chromium is switched to
>> > > fullscreen mode, X server crashes and restarts.
>> > >
>> > > Tests made:
>> > >
>> > > 1. Switched card with another known good Voodoo3. Same problem.
>> > >
>> > > 2. Commented our Load "DRI" from /etc/X11/XF86Config-4. Can switch
>> > > resolutions without X server crashing, however Quake runs EXTRMEMLY slow
>> > > becasue there is no DRI device to use.
>> > >
>> > > 3. Remove DRI comment and problem returns
>> > >
>> > > 4. Comment Load "GLX" from XF86Config-4. Problem persists.
>> > >
>> > > This may not be the best troubleshooting in the world, but it convinced
>> > > me that the DRI in X 4.0.3 is what was causing my problems.
>> > >
>> > > Not to say that DRI is not working, because Chromium will work in
>> > > windowed mode. More specifically I think the problem is that changing
>> > > resolutions while using DRI is what is casuing the crash. This can be
>> > > seen from step 2 above. what do you think?
>> > >
>> > > --
>>
>>
>
>
