You are not logged in.
for me with catalyst 9.2, at launch of gdm i put my login et password, and it return back always to gdm, anyone can help me?
Offline
hi all,
made some x86_64 PKGBUILDs for catalyst, catalyst-utils and lib32-catalyst-utils.
get them from here:
www.nakamura-gebiet.de/scripts/catalyst-9.2-1-lib64.src.tar.gz
www.nakamura-gebiet.de/scripts/catalyst-utils-9.2-2-lib64.src.tar.gz
www.nakamura-gebiet.de/scripts/lib32-catalyst-utils-9.2-1-lib64.src.tar.gz
/usr/lib64 looks now like this:
catalyst-utils /usr/lib64/
catalyst-utils /usr/lib64/dri
catalyst-utils /usr/lib64/libAMDXvBA.cap
catalyst-utils /usr/lib64/libAMDXvBA.so.1.0
catalyst-utils /usr/lib64/libGL.so
catalyst-utils /usr/lib64/libGL.so.1
catalyst-utils /usr/lib64/libGL.so.1.2
catalyst-utils /usr/lib64/libXvBAW.so.1.0
catalyst-utils /usr/lib64/libatiadlxx.so
catalyst-utils /usr/lib64/libfglrx_dm.so.1
catalyst-utils /usr/lib64/libfglrx_dm.so.1.0
catalyst-utils /usr/lib64/libfglrx_gamma.so.1
catalyst-utils /usr/lib64/libfglrx_gamma.so.1.0
catalyst-utils /usr/lib64/libfglrx_pp.so.1
catalyst-utils /usr/lib64/libfglrx_pp.so.1.0
catalyst-utils /usr/lib64/libfglrx_tvout.so.1
catalyst-utils /usr/lib64/libfglrx_tvout.so.1.0
precautionary, i have symlinked all /usr/lib entries to /usr/lib64 (except the xorg modules - i do not know if this is necessary). here everything works ok so far.
vlad
Last edited by DonVla (2009-02-24 18:47:02)
Offline
Thank you DonVla.
Of course, now that someone's posted something, I've just now found the tool for downloading PKGBUILDs from the repo (in yaourt).
Edit: got a similar error to what letroll got, except replace gdm with kdm. Rolled back to 8.12 for now. How did they manage to break 64-bit support?
Last edited by aaaantoine (2009-02-25 21:38:15)
Offline
For GDM users:
In /usr/local/bin/catalyst-gdm:
#!/bin/sh
modprobe -r fglrx
modprobe fglrx
gdm -nodaemon
killall X &> /dev/null
sleep 3
killall -9 X &> /dev/null
modprobe -r fglrx
modprobe fglrx
Make this file executable.
In /etc/gdm/custom.conf, add AlwaysRestartServer=false under [daemon].
In /etc/gdm/PostSession/Default, add the line killall gdm-binary before exit 0.
In /etc/inittab, change x:5:respawn:/usr/sbin/gdm -nodaemon to x:5:respawn:/usr/local/bin/catalyst-gdm, comment out id:3:initdefault: to id:5:initdefault:. If you have GDM in the DAEMONS line of /etc/rc.conf remove it.
Last edited by Wintervenom (2009-02-26 09:01:54)
Offline
now with catalyst 9.2 (i686), in repo "extra", my server X run!
but always without direct rendering....
glx ==>
glxinfo
name of display: :0.0
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Xlib: extension "Generic Event Extension" missing on display ":0.0".
Erreur de segmentation
Offline
http://www.phoronix.com/scan.php?page=n … &px=NzEwMg
Let's see where it goes.
Offline
I am curious, is anyone succesful in setting Radeon HD 4850 working with RadeonHD driver and KDE 4.2 effects using OpenGL. I am able to turn on KDE 4.2 effects only with XRender, but what about OpenGL? Is anyone successful?
Offline
http://www.phoronix.com/scan.php?page=n … &px=NzEwMg
Let's see where it goes.
Yeah! we are famous!
Now seriously, I liked how Phoronix, and Michael specially, dealt with the news. Sure, he ommited some things to make it look more dramatic, but well, the site needs to keep the drama built up.
Offline
This news has prompted me to switch to xf86-video-ati.
Offline
I'm screwed until xf86-video-ati 6.12 or the first version of Catalyst to support XServer 1.6.
Last edited by Wintervenom (2009-03-02 03:05:25)
Offline
http://www.phoronix.com/scan.php?page=n … &px=NzEwMg
Let's see where it goes.
My crystal ball says: http://bbs.archlinux.org/viewforum.php?id=48
There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums. That is why we avoid it. -- ewaller (arch linux forum moderator)
Offline
I'm screwed until xf86-video-ati 6.12 or the first version of Catalyst to support XServer 1.6.
xf86-video-ati supports Xorg-server 1.6.
[flamelab@flamepc ~]$ pacman -Q | grep xf86-video-ati && pacman -Q | grep xorg-server
xf86-video-ati-git 20090226-1
xorg-server 1.6.0-1
Offline
2 month ago I put in my 2 PC 2 ATI HD3450.
Since this time I only have problems.
- 2D/3D Performance (VS Nvidia FX5600 before) are not really good
- Bug when I logout/login on my x86_64 system
- Difficult to use testing and latest xorg
Enough. I bought today an Nvidia 6600 GT 256 mo. Cheap, better h264 decompression and it work.
Sorry ATI.
PS: I tried xf86-video-ati and radeon but I have a lot of difficulty to read heavy mp4 video (720p) with it VS catalyst.
Last edited by Shaika-Dzari (2009-03-02 17:27:12)
Shaika-Dzari
http://www.4nakama.net
Offline
2 month ago I put in my 2 PC 2 ATI HD3450.
Since this time I only have problems.
- 2D/3D Performance (VS Nvidia FX5600 before) are not really good
- Bug when I logout/login on my x86_64 system
- Difficult to use testing and latest xorgEnough. I bought today an Nvidia 6600 GT 256 mo. Cheap, better h264 decompression and it work.
Sorry ATI.PS: I tried xf86-video-ati and radeon but I have a lot of difficulty to read heavy mp4 video (720p) with it VS catalyst.
No kidding. My next video chip will likely be either Intel or Nvidia.
Although a Radeon HD 4650 for $60 looks mighty fine... NO! FOUL TEMPTRESS!
Offline
LOL...
As I've said before though, watch out. The RadeonHD open-source driver is supported somewhat by AMD, and I bet either next year or the year after at the latest AMD will be preferred over NVIDIA (unless they pull a surprise move and open-source their drivers). As for Intel... if they have something in your price range, spring for it. They have kick-ass open-source support.
Offline
Just switched to radeonhd on my working station. Work great
Shaika-Dzari
http://www.4nakama.net
Offline
LOL...
As I've said before though, watch out. The RadeonHD open-source driver is supported somewhat by AMD, and I bet either next year or the year after at the latest AMD will be preferred over NVIDIA (unless they pull a surprise move and open-source their drivers).
Well yeah... But the problem is, that's not the case now. If it takes a year or two for AMD to become the preferred driver, I would still have gotten my money's worth if I were using NVIDIA up to that point.
Offline
Agreed.
Offline
I just read discussion on phoronix, it's very good idea to remove binary drivers from the main repository ([extra] IIRC), probably you just want to remove catalyst but not nvidia, well... I use xf86-video-ati anyway, just would be nice if maintainer would update xf86-video-ati more often, because usually I need to rebuild it myself.
Offline
hi all,
made some x86_64 PKGBUILDs for catalyst, catalyst-utils and lib32-catalyst-utils.
get them from here:
www.nakamura-gebiet.de/scripts/catalyst-9.2-1-lib64.src.tar.gz
www.nakamura-gebiet.de/scripts/catalyst-utils-9.2-2-lib64.src.tar.gz
www.nakamura-gebiet.de/scripts/lib32-catalyst-utils-9.2-1-lib64.src.tar.gz/usr/lib64 looks now like this:
catalyst-utils /usr/lib64/ catalyst-utils /usr/lib64/dri catalyst-utils /usr/lib64/libAMDXvBA.cap catalyst-utils /usr/lib64/libAMDXvBA.so.1.0 catalyst-utils /usr/lib64/libGL.so catalyst-utils /usr/lib64/libGL.so.1 catalyst-utils /usr/lib64/libGL.so.1.2 catalyst-utils /usr/lib64/libXvBAW.so.1.0 catalyst-utils /usr/lib64/libatiadlxx.so catalyst-utils /usr/lib64/libfglrx_dm.so.1 catalyst-utils /usr/lib64/libfglrx_dm.so.1.0 catalyst-utils /usr/lib64/libfglrx_gamma.so.1 catalyst-utils /usr/lib64/libfglrx_gamma.so.1.0 catalyst-utils /usr/lib64/libfglrx_pp.so.1 catalyst-utils /usr/lib64/libfglrx_pp.so.1.0 catalyst-utils /usr/lib64/libfglrx_tvout.so.1 catalyst-utils /usr/lib64/libfglrx_tvout.so.1.0
precautionary, i have symlinked all /usr/lib entries to /usr/lib64 (except the xorg modules - i do not know if this is necessary). here everything works ok so far.
vlad
Hi!
Why not putting there PKGBUILDS into AUR? Or maybe the packages could be added to community Repo.
I like it very much. It is working fine on my HD3200 (780G). Anyway there has to be an additional lib32 pkg for the Catalyst because AMD says:
32-Bit packages must be installed for 64-Bit Linux drivers to install or work.
So the "old" way with pure x64 pkgs is not working with AMD's "new" way of Driver submitting...
greetings from Germany
Last edited by exmethix (2009-03-05 11:12:45)
My Stuff (selfhosted / not 24h online)
Offline
this changes from release to release if you need to have 32bit libs or not :S
I'll keep the current working drivers in extra until we move new Xorg from testing. When AMD won't come up with a new working version that allows Xorg 1.6 and usage without /usr/lib64 we will remove the catalyst packages from the official repos. Then they may come up again in AUR or later in the community repo if a TU is interested. Sadly our community won't have access to the AMD beta mailing list. But anyways it's quiet useless...
Offline
Thank you DonVla
I trust Microsoft about as far as I can comfortably spit a dead rat.
Cinnamon is a wonderful desktop
"Faith is the substance of things hoped for, the evidence of things not seen."
Offline
When AMD won't come up with a new working version that allows Xorg 1.6 and usage without /usr/lib64 we will remove the catalyst packages from the official repos.
dumb question: but only the x86_64 packages? i mean because of the xorg 1.6 incompatibility..
Sadly our community won't have access to the AMD beta mailing list. But anyways it's quiet useless...
stupid AMD!
Offline
AndyRTR wrote:When AMD won't come up with a new working version that allows Xorg 1.6 and usage without /usr/lib64 we will remove the catalyst packages from the official repos.
dumb question: but only the x86_64 packages? i mean because of the xorg 1.6 incompatibility..
The i686 package isn't compatible with xorg server 1.6 so it will be removed as well.
Offline
The i686 package isn't compatible with xorg server 1.6 so it will be removed as well.
is there a TU willing to take care of the catalyst packages?
Offline