Skip to main content

gnome-shell useless with nouveau driver


Running rawhide 20090924 from desktop system, I test gnome-shell to explore its features (seems Activities name is inspired from Sugar interface. Very disappointing because the shell needs hardware acceleration i.e 3D support. Even Sugar interface did a much better job despite its simple look. Picture speaks itself.

Comments

Jens Petersen said…
I filed this bug recently (works great for me on intel...). I should probably ask the X guys about - and not completely sure if it is gnome-shell or mutter.
ulrik said…
Are lots of users going to be left out of Gnome 3.0? Worse still, developers, which means that there will be less people to improve gnome in the future..

Anyway, I can't get this to work on my ATI 9200 something (r200 driver) on a PowerPC, at all, even less than you are showing. It runs in Xypher(sp?) with a yellow tint however, and very quick and snappy. Have you tried that?
Xephyr to be correct. Perhaps that is the xserver used to run gnome-shell. I am a bit surprised your ATI 9200 won't work.

On a bright side, gnome-shell is a preview and not default yet. Gnome team should make at least usable without 3D driver unless they want users to run proprietary Nvidia driver.
Kevin Kofler said…
Try KDE 4 (KWin + Plasma) instead, you can even get compositing and desktop effects without 3D acceleration that way! (Pick "XRender" from the advanced options.) And Plasma also works without compositing/effects.

I kinda hope this issue will get many people to switch to KDE. ;-p
Current issue with KDE4, at least in Fedora, is the multiple dependicy to bundle media, games. Say I do not want to install Amarok, nor Kaffeine, is it possible to do those?
I have tried KDE4 on Rawhide and enable XRender. The desktop is different from Fedora Leonidas (semi-transparent panel). At least, plasma is useable without 3D and can work with Xrender. I might write another blog on that part.
Kevin Kofler said…
The kde-desktop comps group contains a lot of optional stuff as "default" because it's the only way we have to drag KDE apps in (almost all the other comps groups default to GNOME apps, sadly). So we make kde-desktop be basically the complete KDE packageset and a few popular third-party KDE applications.

Just installing kdebase-workspace and kdebase and their dependencies should give you a minimal KDE installation.

Popular posts from this blog

Getting ready for Vanlug

Busy weekend. I just took a break for making a presentation of Fedora Core 6 and Fedora Project for Vancouver Linux Users Group which will debut on November 20, 2006. A local computer store was kind enough to give me a laptop for the demonstration of Fedora Core 6 (Zod) live spin and Sugar interface from OLPC Project. Should you be interested to view that event and live near Vancouver, here is the address .

Detailing the installation of AMD OpenCL rpm for Fedora

Revisiting the previous blog and freshly reinstalling Fedora Design Suite due to a busted boot, I look at the official guideline from AMD Driver for Red Hat Enterprise Linux 7.2 and write a way to improve the process of installing on Fedora 29 in this example. Extracting the tarball contains the following: amdgpu-install amdgpu-pro-install symlink to amdgpu doc folder repodata folder RPMS folder containing rpm package Executing the command ./amdgpu-install -opencl=pal --headless sadly failed on Fedora on that line: ./amdgpu-install -y --opencl=pal --headless Last metadata expiration check: 0:30:51 ago on Mon 19 Nov 2018 07:13:43 PM PST. No match for argument: amdgpu Upon closer look, the script failed to created a temporary repository on /var/opt/amdgpu-pro-local probably explaining why amdgpu metapackage name failed to display. Someone should investigate and provide a fix. At least, we find out Fedora support is available but unofficial. Due to its design, Gnome

No network on Fedora 9 x86_64 follow up

Following my post related to NetworkManager . I have found out about the workaround. If you have x86_64 system with 4GB support enabled, you should disable it in order to make NetworkManager work. I am not sure if that bug affects other distributions so, possibly the bug may be related to the x86_64 kernel. Let see if my theory can be verified.