You are not logged in.

#1 2009-07-21 18:55:45

i-legend
Member
Registered: 2009-07-21
Posts: 14

[SOLVED] Failed to initialize GEM. Falling back to classic.

Hi everyone,
This is the message i get while trying to test X hmm
Used search to find relevant topics but no luck.
Has anyone got a clue of what that means?
Thanks

Last edited by i-legend (2009-07-23 08:57:34)


"In the middle of the road of my life I awoke in the dark wood where the true way was wholly lost"
Dante Alighieri

Offline

#2 2009-07-21 19:47:29

bangkok_manouel
Member
From: indicates a starting point
Registered: 2005-02-07
Posts: 1,556

Re: [SOLVED] Failed to initialize GEM. Falling back to classic.

Offline

#3 2009-07-22 05:42:21

i-legend
Member
Registered: 2009-07-21
Posts: 14

Re: [SOLVED] Failed to initialize GEM. Falling back to classic.

I think I am using an old perhaps deprecated driver for my graphics card.
I have Intel 82845G/GL[Brookdale-G]/GE and was running/testing X with
the xf86-video-intel-legacy driver as opposed to the more 'generic' vesa.
Vesa seems to load xterm as described in the optional test guide for X(in wiki).
However I get the following upon exit:
"waiting for X server to shut down error setting MTRR (base = 0xf0000000, size =
0x000d0000, type = 1) Invalid argument (22)"

Is that a problem?
Thanks.

Last edited by i-legend (2009-07-22 05:43:13)


"In the middle of the road of my life I awoke in the dark wood where the true way was wholly lost"
Dante Alighieri

Offline

#4 2009-07-22 11:41:43

i-legend
Member
Registered: 2009-07-21
Posts: 14

Re: [SOLVED] Failed to initialize GEM. Falling back to classic.

I just finished up with GNOME and love it big_smile
I wanted to post some tips generated from my own experience:
1.  I have the Intel 82845G/GL[Brookdale-G] as indicated in my post above.
     That's a pretty old graphics card and the intel-legacy seems like a best match.
     I was getting the topic name error, "Failed to...." with it and decided to go with
     plain intel, which is documented to crash in the wiki, but it works, with my card
     nontheless. Hopefully that won't change(knocking on wood...)
2.  I kept getting the "MTRR" error again, along with "Caught signal 11 error. Server aborting"
     upon each exit out of X. But X itself was displaying normally with three windows and a clock.
     Therefore I decided to proceed with GNOME regardless and it worked. I hope it won't come
     back and haunt me but i could not find anything definitive on these errors. I think the docu-
     mentation on X errors is pretty weak btw. I never ran "Xorg -configure" just used hal and startx

We'll see how far I get with it...fingers crossed

Last edited by i-legend (2009-07-22 11:44:13)


"In the middle of the road of my life I awoke in the dark wood where the true way was wholly lost"
Dante Alighieri

Offline

#5 2009-07-22 12:27:17

mutlu_inek
Member
From: all over the place
Registered: 2006-11-18
Posts: 683

Re: [SOLVED] Failed to initialize GEM. Falling back to classic.

It should be fine. The legacy driver threw the same errors when I was using it. But you might want to give the new intel driver (2.7.99.902) in [testing] a try. The intel driver has recovered from most of the problems that the transition to GEM and DRI2 caused. The 2.8.0 final version has just been released and should hit our repos soon.

Edit: Beware, [testing] may break your system.

Last edited by mutlu_inek (2009-07-22 12:28:01)

Offline

#6 2009-07-23 08:54:23

i-legend
Member
Registered: 2009-07-21
Posts: 14

Re: [SOLVED] Failed to initialize GEM. Falling back to classic.

I wonder if vesa alone would work with this chipset.
Either way i'll look around and try to find a definitive
answer to this at some point. After all there are those
of us that have these cards.  hmm


"In the middle of the road of my life I awoke in the dark wood where the true way was wholly lost"
Dante Alighieri

Offline

#7 2009-07-23 12:37:56

mutlu_inek
Member
From: all over the place
Registered: 2006-11-18
Posts: 683

Re: [SOLVED] Failed to initialize GEM. Falling back to classic.

You shouldn't use vesa. The legacy driver is surely faster and better. That it falls back to "classic" is because it does not have GEM, which is not a problem. As I said, either use the legacy driver and ignore the messages or use the stuff in [testing] which has come a long way. If you experience problems with the new driver, please report to the freedesktop.org bug tracker. It is supposed to work.

Offline

#8 2009-07-23 12:48:28

i-legend
Member
Registered: 2009-07-21
Posts: 14

Re: [SOLVED] Failed to initialize GEM. Falling back to classic.

Yeah I get it now...vesa is just a generic module that does not load optimal configurations.
I am currently using the intel driver, not the intel-legacy and it works..should i switch back
to legacy? My only concern is that the wiki reports crashes when using intel for older chips.
Thanks


"In the middle of the road of my life I awoke in the dark wood where the true way was wholly lost"
Dante Alighieri

Offline

#9 2009-07-24 23:10:27

mutlu_inek
Member
From: all over the place
Registered: 2006-11-18
Posts: 683

Re: [SOLVED] Failed to initialize GEM. Falling back to classic.

Well, the legacy driver is only there to give people a unable X driver while intel was going through a rough phase. I experienced lots of really bad crashes with the new driver until a few months ago. This is definitely over for i915 and above chipsets and probaly for most older chipsets, too. If it works for you, there is not need for the legacy driver.

Offline

#10 2009-07-25 20:59:11

i-legend
Member
Registered: 2009-07-21
Posts: 14

Re: [SOLVED] Failed to initialize GEM. Falling back to classic.

I switched back to legacy, just to be safe. I honestly can't tell the difference.


"In the middle of the road of my life I awoke in the dark wood where the true way was wholly lost"
Dante Alighieri

Offline

Board footer

Powered by FluxBB