If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Forgot to check the directory created in /tmp first though, so maybe I'll invest a few minutes at some time to see what exactly it's trying to do...
OK. I gave it one last shot, and noticed this time that it was apparently trying to create a file in tmp, pkg_build.out but there was already one left over from when I tried an earlier build with the owner of root.
Removing that pkg_build.out allowed it to build ok this time.
2 more comments,
Ubuntu 9.10 x86-64
catalyst 10.4 as built via above rules script edit.
My LCD brightness control has gone completely wonky from just semi-f'ed up. (Before 10.4 the 2nd setting from none in the brightness popup actually seemed to be the lowest brightness setting while the lower 2 became progressively brighter, i.e. 1 up from none was brighter than 2 up, and brightness all the way "down"(no bar) was brighter than 1 "up". Now my brightness control just flops all over the place, from nothing to what looks like about 5 then to 2, then to 4, etc... best way to describe I guess would be highlighted segments of the brightness popup feedback indicator...)
2. "Failed to execute child process "amdxdg-su" (No such file or directory)"
CCC is back to shipping w/o AMD's little superuser script or whatever it was again. It's been like this for several releases now, and I just remember to try it again since I kept my own gksudo startup workaround from the last time...
Well with the hotfix mentioned by etreus you will only have got a build fix, that's not that same what you get when you update the complete packageing which i do in my script. For testing my script has a -u switch that will always fetch the packaging from the phorogit zip file. Usually i embedd the needed patches inside the script so that download is not needed for tested driver releases. Its needed to do that when the packages change - which definitely happens from time to time.
Upon looking at the brightness setting indicator, I believe that the jumping around of the bar may be that it's actually indicating the correct brightness level now although it some how was shifted between 9.04 -> 9.10 Ubuntu dist upgrade... (I noticed that it jumped from a higher setting to a lower(indicator) which seemed to be roughly correct from screen "brightness" by eyeball...)
On a semi-related note they "forgot" to sign the 10.4 drivers for Windows, and they fail an integrity check. i.e. They're just as capable of f'ing up the Windows release as they are the linux release...