Hi,
I know it's a bad mix(TM) but I do run rawhide here (updated daily), but do need to use the nVidia 3D acceleration. Daft as it sounds, I've always had my machines running on rawhide, but due to doing some dev work, I need OpenGL.
What is the best way for me to do this? I know I will need to recompile whenever I change kernel, but is there a way that I can use the livna python script to ensure I use the correct xorg.conf file and recompile against the new kernel modules using the either the livna src rpms or the nVidia builder while still using a different kernel?
TTFN
Paul
What is the best way for me to do this? I know I will need to recompile whenever I change kernel, but is there a way that I can use the livna python script to ensure I use the correct xorg.conf file and recompile against the new kernel modules using the either the livna src rpms or the nVidia builder while still using a different kernel?
rpmbuild --rebuild the livna src rpm for every new kernel. That's the best (and probably only correct) way to get this to work.
Stay away from the Nvidia installer - it's evil...
On 5/19/05, Paul paul@all-the-johnsons.co.uk wrote:
What is the best way for me to do this? I know I will need to recompile whenever I change kernel, but is there a way that I can use the livna python script to ensure I use the correct xorg.conf file and recompile against the new kernel modules using the either the livna src rpms or the nVidia builder while still using a different kernel?
0) do not mix the livna rpms with nvidia's installer 1) its very easy to use livna's srpm to rebuild a new kernel module 2) do not mix the livna rpms with nvidia's installer 3) example using nvidia-glx-1.0.7174-0.lvn.1.3.src.rpm from livna assuming kernel-smp-2.6.11-1.1319_FC4 and kernel-smp-devel-2.6.11-1.1319_FC4 are installed on an smp athlon: rpmbuild --rebuild --target i686 --define "kernel 2.6.11-1.1315_FC4smp" nvidia-glx-1.0.7174-0.lvn.1.3.src.rpm (that should be one line but of course email is going to line wrap that) 4) do not mix the livna rpms with nvidia's installer 5) that rebuild command will create nvidia-glx-1.0.7174-0.lvn.1.3.i686.rpm kernel-module-nvidia-2.6.11-1.1315_FC4smp-1.0.7174-0.lvn.1.3.i686.rpm nvidia-glx-devel-1.0.7174-0.lvn.1.3.i686.rpm 6) do not mix the livna rpms with nvidia's installer 7) all you need to do is install the new kernel-module-nvidia package that was built rpm -ivh kernel-module-nvidia-2.6.11-1.1315_FC4smp-1.0.7174-0.lvn.1.3.i686.rpm 8) repeat as needed when a new kernel and kernel-devel package is installed before you reboot into the new kernel.
Appendix A) Always avoid rebuilding packages as root. I STRONGLY suggest you create a rpmbuild directory structure in a normal user's home directory, and use that normal user as the build user for any rpm building that you do. For example on my system my rpmbuild directory tree looks like: tree -d /home/builduser/rpmbuild/ |-- BUILD |-- RPMS | |-- athlon | |-- i386 | |-- i686 --> In the above example this is where the built rpms end up on my system | `-- noarch |-- SOURCES |-- SPECS `-- SRPMS -> good place to keep the srpms you want to rebuild like the nvidia-glx srpm
And to make use of that rpmbuild dirtree you need an .rpmmacros file in the build user's homedirectory that looks like this: cat /home/builduser/.rpmmacros: %_topdir %(echo $HOME)/rpmbuild
additionally you might want this macros in your .rpmmacros file as well %_smp_mflags -j3 %debug_package %{nil}
-jef"did i mention you shouldn't mix livna's rpms with nvidia's installer?"spaleta
Always avoid rebuilding packages as root.
Why is that? And why is it that the nvidia livna srpm will not rebuild in single mode, but will rebuild from X? SElinux is not involved here...
On Thu, 2005-05-19 at 17:43 -0400, Jeff Spaleta wrote:
- example using nvidia-glx-1.0.7174-0.lvn.1.3.src.rpm from livna assuming kernel-smp-2.6.11-1.1319_FC4 and kernel-smp-devel-2.6.11-1.1319_FC4 are installed on an smp athlon: rpmbuild --rebuild --target i686 --define "kernel
2.6.11-1.1315_FC4smp" nvidia-glx-1.0.7174-0.lvn.1.3.src.rpm (that should be one line but of course email is going to line wrap that)
It seems that you definitely need to set some stuff up in advance, since, for instance, this looks for kernel sources. I'm still not able to get it all working.
I exploded the kernel SRPM with rpmbuild -bp, and then made a symlink from /usr/src/redhat/BUILD/kernel-2.6.11/linux-2.6.11 to /usr/src/kernels/2.6.11-1.1315_FC4-i686.
This makes the livna RPM rebuild get further, but it still fails with a message asking me to make sure I'm running the right kernel version (matching the sources, which I think I am), and something about KBUILD_OUTPUT, KBUILD, and SYSOUT.
Doesn't anybody else get this?
Thanks,
AG
On 5/19/05, Anthony Green green@redhat.com wrote:
It seems that you definitely need to set some stuff up in advance, since, for instance, this looks for kernel sources. I'm still not able to get it all working.
kernel-smp-devel or kernel-devel has the header files needed. You dont need the whole kernel source for the nvidia drivers... no way. Read through the livna spec.. there is magic to determine a default kernel version to look for and it knows where to look for the headers both fc3 vintage as well as fc4/rawhide vintage. And both the 'kernel' variable and the 'ksrc' variable can be defined as arguments. I never have to define ksrc as long as i have the right kernel-devel package installed matching the kernel version i want to compile for.
-jef"rpm -ql kernel-devel and be amazed!"spaleta
On Thu, 2005-05-19 at 17:00 -0700, Anthony Green wrote:
On Thu, 2005-05-19 at 17:43 -0400, Jeff Spaleta wrote:
- example using nvidia-glx-1.0.7174-0.lvn.1.3.src.rpm from livna assuming kernel-smp-2.6.11-1.1319_FC4 and kernel-smp-devel-2.6.11-1.1319_FC4 are installed on an smp athlon: rpmbuild --rebuild --target i686 --define "kernel
2.6.11-1.1315_FC4smp" nvidia-glx-1.0.7174-0.lvn.1.3.src.rpm (that should be one line but of course email is going to line wrap that)
It seems that you definitely need to set some stuff up in advance, since, for instance, this looks for kernel sources. I'm still not able to get it all working.
I exploded the kernel SRPM with rpmbuild -bp, and then made a symlink from /usr/src/redhat/BUILD/kernel-2.6.11/linux-2.6.11 to /usr/src/kernels/2.6.11-1.1315_FC4-i686.
This makes the livna RPM rebuild get further, but it still fails with a message asking me to make sure I'm running the right kernel version (matching the sources, which I think I am), and something about KBUILD_OUTPUT, KBUILD, and SYSOUT.
Doesn't anybody else get this?
In addition to what Jeff mentioned, I needed the following installed (available from the yum repositories):
kernel-devel fedora-rpmdevtools
I found that I was also able to build the source rpm in runlevel 3. So, for me, I first update the kernel, then I reboot to run level 3. Then I use the following command to rebuild the source rpm:
rpmbuild --rebuild --target i686 nvidia-glx-1.0.7174-0.lvn.1.3.src.rpm
Note that this particular command builds an i686 architecture rpm set based on the kernel you are running at the time.
Then, the *very first time* installed, I needed to install both kernel-module-nvidia and nvidia-glx. After that, only kernel-module-nvidia needs to be updated when you update the kernel.
Mine is working like a champ.
Hope that helps!
Cheers,
Chris
-- ==================================== "If you get to thinkin' you're a person of some influence, try orderin' someone else's dog around." --Cowboy Wisdom
Is anyone having any luck with x86_64 smp and nvidia (dell 670 with dual xeon 64s)? I get a lovely kernel panic and I have to "push the button..." It works fine on my home single Athlon64.
May 20 14:33:48 wintermute kernel: ----------- [cut here ] --------- [please bite here ] --------- May 20 14:33:48 wintermute kernel: Kernel BUG at "arch/x86_64/mm/pageattr.c":154 May 20 14:33:48 wintermute kernel: invalid operand: 0000 [1] SMP May 20 14:33:48 wintermute kernel: CPU 2 May 20 14:33:48 wintermute kernel: Modules linked in: vmnet(U) vmmon(U) nvidia(U) nfsd exportfs lockd parport_pc lp parport autofs4 i2c_dev i2c_core rfcomm l2cap bluetooth sunrpc md5 ipv6 video button battery ac joydev ohci1394 ieee1394 uhci_hcd ehci_hcd tpm_nsc tpm snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_emu10k1 snd_rawmidi snd_ac97_codec snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc snd_util_mem snd_hwdep snd soundcore e100 mii e1000 floppy dm_snapshot dm_zero dm_mirror ext3 jbd raid5 xor dm_mod ata_piix libata aic79xx aic7xxx scsi_transport_spi sd_mod scsi_mod May 20 14:33:48 wintermute kernel: Pid: 19258, comm: X Tainted: P 2.6.11-1.1323_FC4smp May 20 14:33:48 wintermute kernel: RIP: 0010:[<ffffffff80124b82>] <ffffffff80124b82>{__change_page_attr+706} May 20 14:33:48 wintermute kernel: RSP: 0018:ffff810106341ce8 EFLAGS: 00010282 May 20 14:33:48 wintermute kernel: RAX: 00000000000002a0 RBX: ffff8100010002a0 RCX: ffff81000000e000 May 20 14:33:48 wintermute kernel: RDX: 0000000000000060 RSI: 00000000000c7fec RDI: ffff810001000000 May 20 14:33:48 wintermute kernel: RBP: ffff8100c7fec000 R08: 03fffffffffff000 R09: 80000000c7e001e3 May 20 14:33:48 wintermute kernel: R10: 8000000000000163 R11: 0000000000000020 R12: 0000000000000018 May 20 14:33:48 wintermute kernel: R13: 00000000000001f8 R14: ffff81000000c1f8 R15: 8000000000000163 May 20 14:33:48 wintermute kernel: FS: 00002aaaaabe96e0(0000) GS:ffffffff80512480(0000) knlGS:0000000000000000 May 20 14:33:48 wintermute kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 20 14:33:48 wintermute kernel: CR2: 0000000000967070 CR3: 000000008a45d000 CR4: 00000000000006e0 May 20 14:33:48 wintermute kernel: Process X (pid: 19258, threadinfo ffff810106340000, task ffff810067f2c7c0) May 20 14:33:48 wintermute kernel: Stack: 0000000000000001 ffffffff80101810 0000000000000000 ffffffff8011d6d4 May 20 14:33:48 wintermute kernel: ffffffff80426038 ffffffff8035e973 ffffffff8011aa10 ffff8100c7fec000 May 20 14:33:48 wintermute kernel: 00000000000c7fec 0000000000000000 May 20 14:33:48 wintermute kernel: Call Trace:<ffffffff80101810>{init_level4_pgt+2064} <ffffffff8011d6d4>{flat_send_IPI_allbutself+20} May 20 14:33:48 wintermute kernel: <ffffffff8035e973>{__down_write+51} <ffffffff8011aa10>{do_flush_tlb_all+0} May 20 14:33:48 wintermute kernel: <ffffffff80124e0c>{change_page_attr_addr+172} <ffffffff80124741>{iounmap+257} May 20 14:33:48 wintermute kernel: <ffffffff8866c473>{:nvidia:os_unmap_kernel_space+9} May 20 14:33:48 wintermute kernel: <ffffffff8846046e>{:nvidia:_nv001626rm+102} <ffffffff8858df63>{:nvidia:_nv003856rm+107} May 20 14:33:48 wintermute kernel: <ffffffff8857c777>{:nvidia:_nv004391rm+145} <ffffffff8857c1f1>{:nvidia:_nv004194rm+99} May 20 14:33:48 wintermute kernel: <ffffffff88463395>{:nvidia:_nv001175rm+231} <ffffffff8846662c>{:nvidia:rm_shutdown_adapter+102} May 20 14:33:48 wintermute kernel: <ffffffff886694e2>{:nvidia:nv_kern_close+425} <ffffffff8018ac32>{__fput+114} May 20 14:33:49 wintermute kernel: <ffffffff80187e6a>{filp_close+122} <ffffffff801884f7>{sys_close+151}
tjb
Trying ot get this to work for the x86_64 arch. The get the following error message when trying to rebuild.
error: Installed (but unpackaged) file(s) found: /usr/lib/nvidia/libGLcore.so
"/usr/lib/nvidia/libGLcore.so" is a symbolic link: libGLcore.so -> libGLcore.so.1.0.7174 Anyone know what's going wrong here. Is my system settings or the spec file?
Ivan Gyurdiev wrote:
Always avoid rebuilding packages as root.
Why is that?
Because it is very insecure for one thing, and can silently destroy parts of your installed OS very easily. When building as root, a misplaced "rm -rf" or other fairly fatal snippet of code can really fry your entire installed OS. There are lots of rpm specs out there with rather serious (and likely unintentional) flaws in them which if executed as root have a lot of power to cause silent problems to your system.
Another problem is spec files that do not specify a buildroot, will get installed into your real OS at %install time! This overwrites system installed binaries and is very very bad!
The problems that can and do occur when building rpms as root are far more common that you might think, and while Red Hat supplied src.rpms and some of the better public repositories out there both have much higher quality packaging, the risks are still there for accidental mishaps, and a lot of mishaps go unnoticed for quite some time unless they are really destructive.
Here is a copy of my personal rpm config files, completely documented to assist people in setting up rpm to build from their personal user account rather than risk system corruption from doing it as root:
ftp://people.redhat.com/mharris/hacks/rpmbuild-nonroot-1.0.tar.gz
Be sure to read all documentation before using, and feel free to customize to taste and share with anyone else.
Hope this helps.
Demond James wrote:
Trying ot get this to work for the x86_64 arch. The get the following error message when trying to rebuild.
error: Installed (but unpackaged) file(s) found: /usr/lib/nvidia/libGLcore.so
"/usr/lib/nvidia/libGLcore.so" is a symbolic link: libGLcore.so -> libGLcore.so.1.0.7174 Anyone know what's going wrong here. Is my system settings or the spec file?
This sounds like an rpm packaging bug. I'm guessing, but it seems like the rpm package might create that symlink in rpm install scriptlets, rather than at %install time.
The best way, is to do it in %install, simplify install scriptlets, and update the file list to own the symlink.
tor, 19 05 2005 kl. 17:43 -0400, skrev Jeff Spaleta:
- do not mix the livna rpms with nvidia's installer
- its very easy to use livna's srpm to rebuild a new kernel module
- do not mix the livna rpms with nvidia's installer
- example using nvidia-glx-1.0.7174-0.lvn.1.3.src.rpm from livna assuming kernel-smp-2.6.11-1.1319_FC4 and kernel-smp-devel-2.6.11-1.1319_FC4 are installed on an smp athlon: rpmbuild --rebuild --target i686 --define "kernel
2.6.11-1.1315_FC4smp" nvidia-glx-1.0.7174-0.lvn.1.3.src.rpm (that should be one line but of course email is going to line wrap that) 4) do not mix the livna rpms with nvidia's installer 5) that rebuild command will create nvidia-glx-1.0.7174-0.lvn.1.3.i686.rpm kernel-module-nvidia-2.6.11-1.1315_FC4smp-1.0.7174-0.lvn.1.3.i686.rpm nvidia-glx-devel-1.0.7174-0.lvn.1.3.i686.rpm 6) do not mix the livna rpms with nvidia's installer 7) all you need to do is install the new kernel-module-nvidia package that was built rpm -ivh kernel-module-nvidia-2.6.11-1.1315_FC4smp-1.0.7174-0.lvn.1.3.i686.rpm 8) repeat as needed when a new kernel and kernel-devel package is installed before you reboot into the new kernel.
Can this guide be used on all my RHEL4 workstations too?
Regards Bjorn Andersen
On 6/15/05, Bjorn Andersen ba@linuxin.dk wrote:
Can this guide be used on all my RHEL4 workstations too?
as soon as you buy me a rhel4 ws subscription... I think i could.
-jef
On 6/15/05, Jeff Spaleta jspaleta@gmail.com wrote:
On 6/15/05, Bjorn Andersen ba@linuxin.dk wrote:
Can this guide be used on all my RHEL4 workstations too?
as soon as you buy me a rhel4 ws subscription... I think i could.
-jef
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-test-list
It should work fine on RHEL4. RHEL4 is basically FC3 (in some respects) and whenever you bulid a src.rpm you are rebuilding it for your current platform.