You are not logged in.
You can identify the file with something like:
dirname $(xauth info | awk '/Authority file/{print $3}')
if ran as the current user. But it will not work, as authatieventsd.sh is invoked with root privileges.
This might do the trick :
#!/bin/bash
usersList=$(cat /etc/passwd | grep "/home" |cut -d: -f1)
activeUsersList=$(users)
for currentUser in $usersList
do
for currentActiveUser in $activeUsersList
do
if [ "$currentUser" = "$currentActiveUser" ]
then
echo "Do something with /home/$currentActiveUser/.Xauthority"
fi
done
done
Last edited by siavashserver (2012-10-07 18:30:16)
Offline
Sorry for the slow response, guys. But regarding the fglrx module not rebuilding, I can confirm the problem can also be fixed by reinstalling the catalyst-dkms, which will rebuild the driver again. And if you are correct in saying that even after enabling dkms.service and it does not rebuild, then it is either a problem with dkms or the actual catalyst driver registering with dkms. A way to rule out dkms is if anyone here uses virtualbox and the driver for it rebuilt with the new kernel update.
Offline
Sorry for the slow response, guys. But regarding the fglrx module not rebuilding, I can confirm the problem can also be fixed by reinstalling the catalyst-dkms, which will rebuild the driver again. And if you are correct in saying that even after enabling dkms.service and it does not rebuild, then it is either a problem with dkms or the actual catalyst driver registering with dkms. A way to rule out dkms is if anyone here uses virtualbox and the driver for it rebuilt with the new kernel update.
From what i've noticed (tested), first you need to enable dkms service file (through rc.conf(deprecated)) with systemctl enable dkms.service, then systemctl start dkms.service.
The module will be automaticly built when you install the package catalyst-dkms, then on kernel update the fglrx module will be rebuilt when you restart your computer. Perhaps you will have to reboot your computer for the newly built module to be loaded (perhaps a 'modprobe fglrx' will be enough).
Offline
Great job lordheavy and Unia for working on both fglrx and wiki! Cleanup was really needed and i'm sure we all here appreciate you work! Nice!
I must to admit that i forgot about atieventsd completelly, i was testing it only when i became catalyst's maintainer (3 years ago) but it was useless on my hd4850.
IIRC then it wasn't working well also on laptops, kinda buggy often caused cpu to work on 100%. So i just forgot about it...
Today situation could be different - maybe it will work better on laptops? - i cannot test it though, but anyway i have a question:@lordheavy:
can i borrow your atieventsd.service?siavashserver wrote:Probably offtopic, but atieventsd.service and /usr/lib/modprobe.d/catalyst.conf are missing from legacy 12.6 drivers.
Not offtop at all
/usr/lib/modules-load.d/catalyst.conf is in the repo for some time (like month...), but not with all packages, soon i will propagate it.sudo modprobe fglrx ERROR: could not insert 'fglrx': Exec format error
i have updated catalyst and catalyst-lts to work with new kernels (3.5.5 and -44)
Unia wrote:I think the Catalyst-DKMS package is not doing what it should. Lordheavy, can you shed some light on this? (also, an echo telling users to enable the dkms.service if using systemd would be handy in the .install file)
There isn't too much info about dkms on arch wiki.
Important question is: "When fglrx will be rebuilt?". If i will reboot my pc after installing kernel will fglrx module be loaded?
When im looking at systemd it's like a stream, like a river - hard to stop, is it possible for dkms to stop this river and kindly build fglrx before starting X, or dkms will build module sooner - ie before reboot, while shutdown? Or is there a risk that X won't start or will start in vesa?
You can take it, but it doesn't work properly; i don't even know it atieventd really work properly........
For dkms:
http://linux.dell.com/dkms/manpage.html
Have you got an url for a catalyst package that should work with xorg-server-1.13 ? So i could update catalyst for the community-testing repo.
Offline
With kernel 3.6 and mesa 9.0 (both in testing repo) i have opengl 3 now, and my hd6790 is enough faster to handle kwin effects using low power profile. I will not use catalyst anymore.
Excuse my poor English.
Offline
You can take it, but it doesn't work properly; i don't even know it atieventd really work properly........
ok, thanks
Have you got an url for a catalyst package that should work with xorg-server-1.13 ? So i could update catalyst for the community-testing repo.
catalyst-test@AUR : https://aur.archlinux.org/packages.php?ID=34773
In a few steps:
ubuntu's source: https://launchpad.net/ubuntu/quantal/+s … rig.tar.gz
Simple dirs rotation:
build() {
## Unpack archive
# /bin/sh ./amd-driver-installer-12-9-beta-x86.x86_64.run --extract archive_files
mkdir common
mv etc lib usr common
mkdir archive_files
mv arch common xpic xpic_64a archive_files
}
And you are ready to build using our old methods.
On free time i will also look at those *eventsd
Edit: just jumped into [testing] and catalyst-test is working fine on it's xserv 1.13
strange it wasn't working on precompiled xorg-server-dev and xorg-server-git, it did compile without errors, without [testing] though hmm... oh nevermind
@lordheavy:
i guess that you can safely put this ubuntu's fglrx into [community-testing]! Let the testing period begin ;P
Last edited by Vi0L0 (2012-10-09 09:02:16)
Offline
catalyst 12.9beta from ubuntu pushed in the testing repos
Offline
spirtbrat wrote:You can identify the file with something like:
dirname $(xauth info | awk '/Authority file/{print $3}')
if ran as the current user. But it will not work, as authatieventsd.sh is invoked with root privileges.
This might do the trick :
#!/bin/bash usersList=$(cat /etc/passwd | grep "/home" |cut -d: -f1) activeUsersList=$(users) for currentUser in $usersList do for currentActiveUser in $activeUsersList do if [ "$currentUser" = "$currentActiveUser" ] then echo "Do something with /home/$currentActiveUser/.Xauthority" fi done done
This unfortunatelly won't work because it will show also users connected via ie. ssh, not only those with X...
But i just performed quick research and found that GDM is creating two dirs inside /var/run/gdm/ , one dir to auth gdm and one to auth logged user, if i'm right gdm's entry for /etc/ati/authatieventsd.sh should look somewhat like:
# Check gdm
GDM_AUTH_FILE= /var/run/gdm/auth-for-gdm-*/database
if [ -e $GDM_AUTH_FILE ]; then
SERVER_AUTH_FILE=$GDM_AUTH_FILE
DISP_SEARCH_STRING="unix$1"
return 0
fi
I cannot test it atm, i will be able to perform tests tomorrow - it's just simple "FYI" that could be usefull
Last edited by Vi0L0 (2012-10-09 19:36:11)
Offline
Just tested it and it works.
Xauth returns something like this:
atieventsd[21292]: xauth: file /tmp/atievntX.fSq1W8 does not exist
But it seems to be a notice, not an error, because:
$ sudo xauth -f /tmp/atievntX.fSq1W8 list
sterminal/unix:0 MIT-MAGIC-COOKIE-1 c07802e6712e91d997e7dbcde17eea6d
$
Offline
Thanks for pushing updates into catalyst-hd234k repo too Vi0L0. I can confirm same notice/warning like spirtbrat.
Offline
I have ati mobitlity radeon 4500/5100 series card and i want to install the proprietary drivers for the card as the opensource ones cause overheating.Now i installed the catalyst-total-hd234k 12.6-5 driver from aur and i am able to run catalyst control center.But the starnge thing is now my cpu usage goes 70 -80 percent while playing 1080p.So i assume that the fglrx driver is not functioning properly ,also fglrxinfo gave this output
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 139 (ATIFGLEXTENSION)
Minor opcode of failed request: 66 ()
Serial number of failed request: 13
Current serial number in output stream: 13
So whats the isuue, should i manualy load the modules ? I am new to arch ,, forgive me for my ignorance.
EDIT:Also modprobe fglrx gives FATAL: Module fglrx not found.
Last edited by Diadara (2012-10-12 16:53:35)
Offline
Are you sure that you compiled everything correctly? Try using the unofficial repositories by Vi0L0, that should work.
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
i guess something went wrong as there is no fglrx module, amdccc was installed though and the there were no errors,i will try the unofficial repo then
Offline
I generally find the repositories (be it official or unofficial) easier than compiling myself. That is, if you use the stock kernel.
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
I just did a -Syu there was a new kernel upgrade and wala the build hook kicked in and fgrlx suddenly appears.Dont understand what happend the first time though.And my system temperature dropped by 10 degrees.
Problem solved.
Offline
Catalyst seamlessly work also with some non-stock kernel: the catalyst-daemon package works like a charm for me with both pae and ck kernels.
@Diadara: you can rebuild the module at any time by running catalyst_build_module. See the wiki for more info.
Offline
I just updated to 12.9 (from [community]), and I got this in my terminal:
Error! Could not locate dkms.conf file.
File: does not exist.
Is this something that needs to be fixed?
Last edited by Unia (2012-10-13 14:40:51)
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
I just updated to 12.9 (from [community]), and I got this in my terminal:
Error! Could not locate dkms.conf file. File: does not exist.
Is this something that needs to be fixed?
.install file is a bit wrong, but the real culprit is a bug in pacman that should be fixed in a next release.
This will be fixed when pacman will be fixed :-)
Currently it let orphaned files on your harddrive,
https://bugs.archlinux.org/task/31902
https://bugs.archlinux.org/task/29731
OK, pushed a package with a fixed install file.
Last edited by lordheavy (2012-10-13 14:55:31)
Offline
^ Great, thanks for the quick fix!
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
Hey guys, I'm using a Radeon HD 4650, and have been using the catalyst-hd234k repo with it pretty much since that repo appeared. But today I'm getting this with my -Syu -
error: failed to prepare transaction (could not satisfy dependencies)
:: Starting full system upgrade...
:: catalyst-utils: requires xorg-server<1.13.0
Is it safe to upgrade Xorg now? I've been frozen on 1.12.4-1 because of a recommendation that my frozen Catalyst version won't work with anything higher.
Does this mean I'm getting a new Catalyst too, or just that the older one now supports a newer Xorg?
Figured I'd ask before I un-freeze any of my packages!
"Some humans would do anything to see if it was possible to do it. If you put a large switch in some cave somewhere, with a sign on it saying "End-of-the-World Switch. PLEASE DO NOT TOUCH", the paint wouldn't even have time to dry."
Offline
I updated and it broke my system, so i don't think it's safe.
Offline
Unofficial repositories have not been updated yet. Catalyst 12.9 supposedly supports Xorg 1.13, I don't know if this is official or through patches.
Once the unofficial repositories get updated, you can use Xorg 1.13. For now, just either hold back the required Xorg packages, or use [xorg112] repository:
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
Yeah adding that repo let me upgrade. I actually thought I remembered using that repo but it must've been the 111 one. Added it to pacman.conf and today's updates are going in, thanks
"Some humans would do anything to see if it was possible to do it. If you put a large switch in some cave somewhere, with a sign on it saying "End-of-the-World Switch. PLEASE DO NOT TOUCH", the paint wouldn't even have time to dry."
Offline
Unofficial repositories have not been updated yet. Catalyst 12.9 supposedly supports Xorg 1.13, I don't know if this is official or through patches.
Once the unofficial repositories get updated, you can use Xorg 1.13. For now, just either hold back the required Xorg packages, or use [xorg112] repository:
Unfortunatelly there's no catalyst legacy driver whith xserv 1.13 support.
So named "12.9" is ubuntu's "special" driver (for ubuntu 12.10) and it's official (from AMD).
For hd 2 3 4 xxx users there's only one solution atm : [xorg112] + [catalyst-hd234k] (eventually blocking update through pacman.conf + AUR's catalyst-total-hd234k)
Last edited by Vi0L0 (2012-10-13 21:46:02)
Offline
Do we know if Legacy will be updated to work with Xorg 1.13?
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline