Hello all,
Got two problems with my new install of F7.
I am using kernel-xen-2.6.20-2925.13.fc7. Problem: I *don't* want to use Xen, I want to use the other kernel on my machine:
kernel-2.6.22.1-27.fc7
How do I fix that? Why did it do that on install?
Second, a program called "prelink" pegs my CPU. Is it necessary, and if not, how do I turn it off besides doing a kill -9 on it?
Thanks for any help!
******************************************************************************* Gilbert Sebenste ******** (My opinions only!) ****** *******************************************************************************
On Tue, 24 Jul 2007, Gilbert Sebenste wrote:
Hello all,
Got two problems with my new install of F7.
I am using kernel-xen-2.6.20-2925.13.fc7. Problem: I *don't* want to use Xen, I want to use the other kernel on my machine:
kernel-2.6.22.1-27.fc7
How do I fix that? Why did it do that on install?
Well, I just fixed that. I don't know why it did it, but I edited grub.conf to put the non-Xen kernels first. Then I blew away the Xen kernels, and all is well with that.
Second, a program called "prelink" pegs my CPU. Is it necessary, and if not, how do I turn it off besides doing a kill -9 on it?
Still need help with this one, though.
******************************************************************************* Gilbert Sebenste ******** (My opinions only!) ****** *******************************************************************************
Gilbert Sebenste wrote:
On Tue, 24 Jul 2007, Gilbert Sebenste wrote:
Hello all,
Got two problems with my new install of F7.
I am using kernel-xen-2.6.20-2925.13.fc7. Problem: I *don't* want to use Xen, I want to use the other kernel on my machine:
kernel-2.6.22.1-27.fc7
How do I fix that? Why did it do that on install?
Well, I just fixed that. I don't know why it did it, but I edited grub.conf to put the non-Xen kernels first. Then I blew away the Xen kernels, and all is well with that.
The xen kernel is picked as default if you choose virtualization at install time. Removing the xen kernel should not hurt anything but the ability to use xen for virtual xen installs.
Second, a program called "prelink" pegs my CPU. Is it necessary, and if not, how do I turn it off besides doing a kill -9 on it?
Still need help with this one, though.
prelink will run heavy on newly installed systems but will then run with less to do on later runs. It optimizes how fast your programs start by optimizing libraries. You should just let it run.
Jim
Gilbert Sebenste
(My opinions only!) ******
Gilbert Sebenste wrote:
On Tue, 24 Jul 2007, Gilbert Sebenste wrote:
Hello all,
Got two problems with my new install of F7.
I am using kernel-xen-2.6.20-2925.13.fc7. Problem: I *don't* want to use Xen, I want to use the other kernel on my machine:
kernel-2.6.22.1-27.fc7
How do I fix that? Why did it do that on install?
Well, I just fixed that. I don't know why it did it, but I edited grub.conf to put the non-Xen kernels first. Then I blew away the Xen kernels, and all is well with that.
No, all is not well, you could have just changed the value of the "default=" line to boot what you want and preserve the ability to run a xen kernel if you find later you need to. You jumped to the brute force solution just 13 minutes after asking the question.
Second, a program called "prelink" pegs my CPU. Is it necessary, and if not, how do I turn it off besides doing a kill -9 on it?
Let it run to completion. If you don't, some fixes may not work as expected. Stopping part way through could leave system files in an inconsistent (partially updates) state, that why a regular kill doesn't stop the program. I assume by now you did something more drastic like deleting the executable...
Still need help with this one, though.
Bill Davidsen <davidsen <at> tmr.com> writes:
No, all is not well, you could have just changed the value of the "default=" line to boot what you want and preserve the ability to run a xen kernel if you find later you need to. You jumped to the brute force solution just 13 minutes after asking the question.
Why should he keep the Xen kernels installed if he doesn't need them? He can always reinstall them later when/if he actually needs them.
Kevin Kofler
On Tue, 24 Jul 2007, Bill Davidsen wrote:
Gilbert Sebenste wrote:
Hello all,
Got two problems with my new install of F7.
I am using kernel-xen-2.6.20-2925.13.fc7. Problem: I *don't* want to use Xen, I want to use the other kernel on my machine:
kernel-2.6.22.1-27.fc7
How do I fix that? Why did it do that on install?
Well, I just fixed that. I don't know why it did it, but I edited grub.conf to put the non-Xen kernels first. Then I blew away the Xen kernels, and all is well with that.
No, all is not well, you could have just changed the value of the "default=" line to boot what you want and preserve the ability to run a xen kernel if you find later you need to. You jumped to the brute force solution just 13 minutes after asking the question.
I can always re-install by doing a yum install xen-kernel.
Second, a program called "prelink" pegs my CPU. Is it necessary, and if not, how do I turn it off besides doing a kill -9 on it?
Let it run to completion. If you don't, some fixes may not work as expected. Stopping part way through could leave system files in an inconsistent (partially updates) state, that why a regular kill doesn't stop the program. I assume by now you did something more drastic like deleting the executable...
What "fixes"? Still, I will reboot and let it run. What does this program do? I've never seen it before.
******************************************************************************* Gilbert Sebenste ******** (My opinions only!) ****** *******************************************************************************
Gilbert Sebenste sebenste@weather3.admin.niu.edu writes:
What does this program do? I've never seen it before.
It computes preferred link addresses for libraries i think, so that programs load (slightly) faster.
Regards Ingemar
Gilbert Sebenste writes:
Hello all,
Got two problems with my new install of F7.
I am using kernel-xen-2.6.20-2925.13.fc7. Problem: I *don't* want to use Xen, I want to use the other kernel on my machine:
kernel-2.6.22.1-27.fc7
How do I fix that? Why did it do that on install?
You can press Enter at GRUB's boot prompt, and select the other kernel.
To make the default change permanent, edit /boot/grub/grub.conf, and change the default= setting. The first menu entry in Grub's boot menu is default=0, the second menu entry is default=1, and so on. Set default accordingly. Take care editing the grub.conf file, an accidental typo may have rather unfortunate results.
Second, a program called "prelink" pegs my CPU. Is it necessary, and if not, how do I turn it off besides doing a kill -9 on it?
That shouldn't happen. Run 'rpm -e prelink', but this should really be investigated further. prelink shouldn't be hogging the CPU, like that. Before nuking prelink, wait for eat to start eating the CPU, find its pid, then do "ls /proc/$PID/fd". Wait a few seconds, and do it again. See if there are any changes. You might have a corrupted binary somewhere that prelink is choking on. Prelinking is good, you want to try to keep it around.
Hi Sam,
To make the default change permanent, edit /boot/grub/grub.conf, and change the default= setting. The first menu entry in Grub's boot menu is default=0, the second menu entry is default=1, and so on. Set default accordingly. Take care editing the grub.conf file, an accidental typo may have rather unfortunate results.
Right on. I remembered that after I sent out my email.
Second, a program called "prelink" pegs my CPU. Is it necessary, and if not, how do I turn it off besides doing a kill -9 on it?
That shouldn't happen. Run 'rpm -e prelink', but this should really be investigated further. prelink shouldn't be hogging the CPU, like that. Before nuking prelink, wait for eat to start eating the CPU, find its pid, then do "ls /proc/$PID/fd". Wait a few seconds, and do it again. See if there are any changes. You might have a corrupted binary somewhere that prelink is choking on. Prelinking is good, you want to try to keep it around.
Maybe a buggy kernel? They just released a new one. I'll see how it goes. Thanks for the help to all who have replied so far!
******************************************************************************* Gilbert Sebenste ******** (My opinions only!) ****** *******************************************************************************
That shouldn't happen. Run 'rpm -e prelink', but this should really be investigated further. prelink shouldn't be hogging the CPU, like that. Before nuking prelink, wait for eat to start eating the CPU, find its pid, then do "ls /proc/$PID/fd". Wait a few seconds, and do it again. See if there are any changes. You might have a corrupted binary somewhere that prelink is choking on. Prelinking is good, you want to try to keep it around.
Maybe a buggy kernel? They just released a new one. I'll see how it goes. Thanks for the help to all who have replied so far!
Its unlikely the kernel has much to do with this.
prelink is an optimsiation thing, to try and speed up application start up time. try googling for prelink for more info.
As has already been said, on a newly installed system prelink has a lot to do, so will take all the cpu and run for a while. Just let it do its thing. Afterwards, you should not notice it much. Occasionally it pops up have a big system update, when a lot of new libs are around and it has to prelink them all again.
Also note that prelink should be running at a nice value of 19, so it will only take all the cpu if there is really nothing else running. If anything else needs the cpu, it will drop down to a few % (The point of nice 19)
cheers Chris
-
Bill Davidsen -
Chris Jones -
Gilbert Sebenste -
Ingemar Nilsson -
Jim Cornette -
Kevin Kofler -
Sam Varshavchik