Jaunty + Catalyst 8.12 ?
I just noticed that Ubuntu has created 8.12 packages for Jaunty. Anyone have success with those?
FYI, Jaunty uses kernel 2.6.28 so if you needed this kernel for other reasons it might be easier to just install Jaunty rather than trying to bludgeon Intrepid into using 2.6.28 along with fglrx. That assumes that the Jaunty 8.12 fglrx packages are indeed usable.
No they're not. The fglrx packages install without any problems, but the X server won't start because of ABI incompatibilities. That makes no sense. Since all the X components are packaged by the same folks as the fglrx packages why make the latter available if they don't work with the rest of Jaunty? Note these are the binary packages I'm referring to, not their source.
This isn't really a driver problem, but a Jaunty packaging problem.
Bottom line is that at this point in time there appears to be no usable 8.12 fglrx driver that yields accelerated 2D. I've tried Debian Lenny, Ubuntu Intrepid, and Ubuntu Jaunty. Only the stock Intrepid fglrx driver works and with great mediocrity at that. Furthermore it is tied to the 2.6.27 kernel. Please don't tell me how great the 8.12 fglrx driver works on your system unless your video card is a 4850 and your provided recipe has been corroborated by someone else. I've spent the last 3 weeks on this crapola and it's getting old. Anyone interested in buying a 4850? :-)
Last edited by nbi1; 01-20-2009 at 01:41 PM.
I'll start the bidding at 30% of what you paid for it, with free international shipping
I'm pretty sure the reason it doesn't work on Jaunty is because of the Xserver/Xorg level. I'm running the prerelease 9.2 and it still doesn't have a "x750"/"x750_64a" in the build directory, and it probably won't until xorg 7.5 is actually released. Jaunty is still using a prerelease xorg.
9.2?
You have the 9.2 beta? We don't even have 9.1 yet! I'm thinking we will have it by tomorrow, but I also doubt it will work on Jaunty.
9.2, on the other hand, damn well better work on Jaunty.
damn, even 9.2 beta doesn't work with jaunty?
hope it doesn't take them as much as it did to support xorg 7.4 ... it was really ridiculous...
even though fglrx has reached a not-sucking-so-much state, the time they take to fix bugs/add support for kernels and x is huge...
maybe they should take a month or two to debug their development schedule a bit...
(afaik xorg 7.5 will likely feature xserver 1.7 and will be released after jaunty... it's actually support for xserver 1.6 they need to implement)
Yeah, there was a version leaked to the public, but I can't find the thread around here that discusses it - if it's been deleted I'm not re-posting it.Originally Posted by EmbraceUnity
The thread discussing the 9.1 leaked driver is still around though, but as you say, it'll probably be on amd.com shortly
the thread is at http://phoronix.com/forums/showthread.php?t=14784Yeah, there was a version leaked to the public, but I can't find the thread around here that discusses it - if it's been deleted I'm not re-posting it.
The thread discussing the 9.1 leaked driver is still around though, but as you say, it'll probably be on amd.com shortly
it hasn't worked well for me though... both this driver and the 9.1 leaked beta hard-lock my system in some cases
Oh, I didn't see that, I thought there was a 1:1 correlation of Xorgs to Xservers these days. In that case, I can't say whether 9.1/9.2 has any xserver 1.6 support...
FYI, I did get 8.12 working under Intrepid recently. I'm going to apply the same steps to Jaunty. Lets keep our fingers crossed.
The epithany I had with Intrepid was to get the stock fglrx working first. Then the system was apparently primed for a successful install of 8.12.
The difference with Jaunty is that the Ubuntu packaged 8.12 doesn't work from the get go. Maybe I can prime the system with older versions before attempting the install for the official ATI.
I guess the major problem with fglrx (8.12) and xserver 1.6 is
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
dlopen: /usr/lib/xorg/modules/extensions//libglx.so: undefined symbol: miInitVisualsProc
It would be possible to remove the 2 other checks, but X will not start. The ABI _really_ changed not just the nameing like from 1.3 to 1.4. The nvidia drivers do not need that symbol and work with ignoreABI override. I added that to my nvidia script yesterday.
kano did you try the leaked betas on xserver 1.6 by any chance?
Posting Permissions
Reply With Quote