Re: Howto: ATI Mobility Beryl/XGL FGLRX in Edgy
Update
Well that was pretty scary. It consistently showed the problem after about 10 different restarts, so I figured it wasn't going to fix itself anytime soon.
Now I know practically nothing about linux, but making the copy of the fglrx.ko seemed to cause a problem. And when I reinstalled the new modules it was still there. So I decided to run
Code:
sudo rm /lib/modules/`uname -r`/misc/fglrx.ko
and then reinstall the modules once more.
After restarting back into Gnome again the problem was still there and my windows were acting funky. So I booted into Fail Safe Gnome and the CPU problem disappeared. Next I tried booting into XGL and the problem wasn't there. Finally I booted into regular Gnome again and it disappeared this time. Weird. I'll post back when I understand this more.
Update 2
Well it looks like I was very wrong. Restarting into either Gnome or XGL still gives me the error. It only works when I first log into Fail-Safe Gnome. That's when I get an error about the gnome-settings-daemon which I have set to automatically run at login. This daemon is probably whats using all the CPU up and not showing any trace at all. This seems to be a big problem that several people have...and I still don't know of a solution. I'm going to keep messing around with my settings until I catch a break.
Re: Howto: ATI Mobility Beryl/XGL FGLRX in Edgy
Quote:
Originally Posted by
NTolerance
I must be putting that in the wrong place because it outright disables my keyboard once Xgl loads. Is this supposed to go in /usr/local/bin/startxgl.sh ?
Thanks.
Re: Howto: ATI Mobility Beryl/XGL FGLRX in Edgy
When I Restart my X session all I have is a blank spot where "XGL" should be do I do some thing worng?
I currently running Edgy Kubuntu I have every thing else installed
Beryl, FGLRX, Emerald, I check Adept & is show "XGL" installed.
What I think happened is I ****** up on the scripting some where ](*,)
Can any one give more details on the scripting part sorry I'm a bit of a noob to Bash scripting.
If you can help me out can I get some links to help me learn more about Bash & scripting in Bash? :mrgreen:
Re: Howto: ATI Mobility Beryl/XGL FGLRX in Edgy
Quote:
Originally Posted by
zasf
I see that you're using a older version of fglrx, you should try the latest one, they're improving the driver even if very slowly
He shouldn't update if his card is old:
As of driver version 8.29.6 support for the following products is no longer included:
* Radeon® 8500/9000/9100/9200/9250
* Mobility™ Radeon® 9000/9100/9200
* Radeon® IGP 9000/9100/9200
Re: Howto: ATI Mobility Beryl/XGL FGLRX in Edgy
Hi all.
I followed this good guide, starting from the beryl installation,
because I've already had the fglrx working fine.
I can start Xgl whit its session,
but when I launch beryl-manager
I keep an error, and I loose the bars on my windows
svetj@svetlap:~$ beryl-manager
svetj@svetlap:~$ XGL Present
compiz: Couldn't load plugin 'gconf'
This is the ouput of fglrxinfo:
svetj@svetlap:~$ fglrxinfo
Xlib: extension "XFree86-DRI" missing on display ":1.0".
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY/RADEON 9000 DDR Generic
OpenGL version string: 1.3.1091 (X4.3.0-8.28.8)
Is that right?
Where am I wrong?
Thanks a lot
Re: Howto: ATI Mobility Beryl/XGL FGLRX in Edgy
Odelay:
Removing the module like that was correct. Now go into your "/etc/X11/xorg.conf" and change the "fglrx" to "ati". Now boot into normal gnome and make sure that beryl-manager is not starting.
A question: how do you know cpu is 100% if no process is running at 90-100% in top or system monitor? Remember, you may have to click View->All Processes in system monitor in order to see what is running. Also try sorting on memory.
Re: Howto: ATI Mobility Beryl/XGL FGLRX in Edgy
Hey. This is for the people that have the beryl-manager problem causing the cpu to go to 100%.
First, I would start by uninstalling beryl and emerald (I just used synaptic to remove them). Go into terminal and issue
Now remove the setting files and extras you see.
Do the same for emerald
Now once you have everything uninstalled, I would follow this **(http://wiki.cchtml.com/index.php/XGL-Ubuntu) guide once you have fglrx up and running (to check, issue fglrxinfo). Before restarting though, you have to make a messy script to fix the CPU problem. This is taken from http://forum.beryl-project.org/topic...itlebar-blinks
Make the script
Code:
sudo gedit /usr/local/bin/start-xgl.sh
Add this to the script
Code:
cat /usr/local/bin/start-xgl
#!/bin/sh
beryl-manager &
killall emerald
emerald &
Go to Prefs>Sessions>StartUp and add "sh /usr/local/bin/start-xgl.sh"
There's probably a better way to do the script thing (maybe making it an exec) but this worked for me at least.
** The only reason I mention the other guide is for consistency with what I did. I imagine you can just follow this guide, make sure gnome-sessions-daemon is a startup item, and do the script thing.
Re: Howto: ATI Mobility Beryl/XGL FGLRX in Edgy
Worked for me :D
Haha I'm going to convince some ppl to get linux with this ;)
Only downside: makes my computer buggy when in xgl :(
But other then that : pwns vista ;)
Big thnx
Re: Howto: ATI Mobility Beryl/XGL FGLRX in Edgy
Quote:
Originally Posted by
svetj
Hi all.
I followed this good guide, starting from the beryl installation,
because I've already had the fglrx working fine.
I can start Xgl whit its session,
but when I launch beryl-manager
I keep an error, and I loose the bars on my windows
svetj@svetlap:~$ beryl-manager
svetj@svetlap:~$ XGL Present
compiz: Couldn't load plugin 'gconf'
This is the ouput of fglrxinfo:
svetj@svetlap:~$ fglrxinfo
Xlib: extension "XFree86-DRI" missing on display ":1.0".
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY/RADEON 9000 DDR Generic
OpenGL version string: 1.3.1091 (X4.3.0-8.28.8)
Is that right?
Where am I wrong?
Thanks a lot
DO you have any compiz package installed? If you have any then remove it first.
Re: Howto: ATI Mobility Beryl/XGL FGLRX in Edgy
I read at the official Edgy/ATI/Beryl Guide that having fglrxinfo spit back problems with direct rendering is normal. I get the exact same output as svetj...but I don't have the beryl-manager problem anymore (see my above post).
Right now everything seems to be working. It feels a little unstable and I'm not entirely convinced my computer won't come crumbling apart after the million and one things I did to get Edgy working. I guess this is what beta-testing feels like. The way I see it, we're all just making sure Feisty will be the best yet. ;)