<p dir="ltr">An F19 build is scheduled for Monday. If that flops, I'll slap 6.5 on and move to the next issue.</p>
<div class="gmail_quote">On Jul 25, 2014 10:08 PM, "Michael B. Trausch" <<a href="mailto:mike@trausch.us">mike@trausch.us</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 07/25/2014 05:28 PM, Jim Kinney wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Don't mix 'em yet.<br>
<br>
for the efficient (i.e. busy) admin, RPMFusion is not yet online with v7.<br>
So no NVIDIA modules to run a k4000 or a Tesla GPU.<br>
<br>
The official Nvidia installer pukes during the build with a failed kernel<br>
test in autoconf and suggests a make oldconfig && make prepare<br>
<br>
which also fails in the 3.10.0-123.4.4 kernel tree with a failed call to<br>
arch/x86/syscall/syscall_32.<u></u>tbl<br>
<br>
There is_no_ 32 bit support at all in RHEL7. So what's with a 32-bit sys<br>
lookup table?<br>
<br>
Running kernel works fine but building new stuff fails instantly. ugh.<br>
</blockquote>
You can install 32-bit headers to make the build happy, and GCC can build the 32-bit module. That said, you'd have to not use nVidia's script to do it, but do it by hand. You can probably patch it to just avoid it as well—most problems I've had building nvidia software on "unsupported" environments often amounted to patching 10 or less lines to get it to correctly and successfully build.<br>
<br>
Having now learned The Way of Red Hat, I also spend much less time building and deploying binaries than I used to. Build once, write spec file, build again with split packages, upload to repo, and just yum install everywhere.<br>
<br>
And, as long as I manage 100% of the mirrors and repositories, yum never, ever breaks! It's all about finding the tricks!<br>
<br>
(Sorry, though, I can't help with nvidia... I don't think I have any more nvidia hardware left. I won't use a graphics display unless it's got KMS-enabled drivers in-tree that perform well... and I don't do anything that requires massive vector processing since most of my work is programming or data manipulation.)<br>
<br>
You might try doing the build on a F19 or F20 system and simply copying the 64-bit modules to the R7/C7 system. That might actually work, since they're similar enough.<br>
<br>
— Mike<br>
______________________________<u></u>_________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/<u></u>listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/<u></u>listinfo</a><br>
</blockquote></div>