patch added in sgfxi for 313.18, that should work in 3.7 and 3.8 I believe.

That patch only partially works in 310.32 so needs some fixing.

bugs.gentoo.org/show_bug.cgi?id=447566
Back to top

patches added also for 173.14.36, 304.64
Back to top

I'm still not able to install 313.18 on the aptosid 3.8 kernel (OK up until 3.7) but 310.32 installs OK.


Back to top

I can't say then, does this work on debian vanilla or siduction/liquorix kernels?

The patch I added is from gentoo, and their users reported it worked.
Back to top

The patch for 313.18 on 3.7.6+ does not work for me anymore.
Did you change something?
Back to top

@ techAdmin

I checked the sgfxi version on my other computer so I can say that

will install 313.18 on a 3.7 kernel with a version higher than 3.7.5 but the latest version

does not for me.
It fails the same way it did without the patch now.
Back to top

the patches are not in sgfxi, they are pulled from the server and run so the sgfxi version isn't really related to the patch unless I change the patch file name.

I didn't need any patches at all for 3.7 so I didn't actually test the 313.18 patch.

I'm unclear on this situation, I'm only seeing some people report that the patches do not work, and my testing shows that 313.18 doesn't need any patches at all to run as long as the version.h link is done, which happens the first time you install the new driver, or with -f.


Back to top

check this:



if you are missing one of those directories, show me which one is missing.

As you can see, in liquorix for example, the link is not needed since the paths are already present.

You can find that by removing one directory from the end until you get a ls that does not show error.

Also, in this thread: forums.gentoo.org/viewtopic-p-7239256.html#7239256

the gentoo people said that all that is required is the link fix:


which sgfxi already runs with -f if you need it but you only need that once per kernel version.

Something is not right here, I've almost never seen the gentoo guys be wrong about things like this.

Show your system data, and show the results of those ls things I posted. The reason these patches keep breaking is not because of the patches imo, it's something else, you don't even need to patch 3.7 at all except for the link on liquorix.

I'm not going to change the patches again until we find out why one kernel works and another doesn't.
Back to top

I have the "version.h" link, I am using Liquorix so I already have it, adding "-f" changes nothing.
It installs without the patch up to 3.7.5 and fails with 3.7.6 or higher.

You mentioned adding the patches before after I and others brought up the problem.


There is a commit to the SVN about it here.

This is my other computer running 3.7.8 which I installed 313.18 on with sgfxi 4.20.26.

I had 313.18 installed on this computer with 3.7.8 with the same sgfxi version but when I updated to 3.7.9 sgfxi no longer worked for any 3.7 kernel above 3.7.5.

I can see that there have been more commits to the SVN about 3.7 patches since then so I can only conclude that some change to the patch has caused it to stop working.
Back to top

Again, from now on post ALL relevant data until we pin down which kernels are failing and why.

313.18 works without any patches on my kernel, and my kernel does not require any path fix.

I added in the 3.8 / 313.18 patch which is the simplest patch, but let me repeat, the quality of the web's patches is absolutely terrible for this issue, there is absolutely no consistency between the patches out there, and they are all totally random in terms of what they fix and patch.

If you post further in this thread, post the results, each time, for your installed kernel with the ls of /usr/src kernel I posted above, and post: inxi -SCx so I can see your system at a glance, at this point no benefit occurs from doing random changes without knowing why we are changing and what systems require the change, otherwise we just spin around in circles and don't get anywhere.
Back to top