<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hmmm...<br>
What do you see in a terminal if you do:<br>
rpm -q kernel-rt<br>
<br>
If planetccrma-core installed then you should have at least one realtime<br>
kernel listed there. Then I would check the contents<br>
of /boot/grub/grub.conf, you should have an entry there for the rt<br>
kernel and it should probably be the default - "index" points to the 0<br>
based index of the default kernel.<br>
<br>
-- Fernando<br>
</blockquote></div><br></div>[root@ceres sean]# rpm -q kernel-rt<br>kernel-rt-2.6.26.8-1.rt16.1.fc10.ccrma.x86_64<br><br>[root@ceres sean]# cat /boot/grub/grub.conf<br># grub.conf generated by anaconda<br>#<br># Note that you do not have to rerun grub after making changes to this file<br>
# NOTICE: You have a /boot partition. This means that<br># all kernel and initrd paths are relative to /boot/, eg.<br># root (hd0,0)<br># kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00<br>
# initrd /initrd-version.img<br>#boot=/dev/sda<br>default=0<br>timeout=3<br>splashimage=(hd0,0)/grub/splash.xpm.gz<br>hiddenmenu<br>title Fedora (2.6.27.19-170.2.35.fc10.x86_64)<br> root (hd0,0)<br> kernel /vmlinuz-2.6.27.19-170.2.35.fc10.x86_64 ro root=UUID=c14b36c6-4eab-4def-b2ec-a33a006c5164 rhgb quiet<br>
initrd /initrd-2.6.27.19-170.2.35.fc10.x86_64.img<br><br>[root@ceres sean]# <br><br>-------------------------<br><br>Is it just a matter of adding my own entry for the kernel in grub? What information should I use there, if so?<br>
<br>Thanks,<br><font color="#888888"><br>-Sean<br>
</font></blockquote></div><br>Well, after reading up on adding kernels to grub, I know that I just
need to make an entry just like what is there which points to the new
kernel. However, the only initrd img file on my system is the one you
see in my grub.conf file: /boot/initrd-2.6.27.19-170.2.35.fc10.x86_64.img which is clearly is for the vmlinuz-2.6.27.19-170.2.35.fc10.x86_64
kernel. After reading further about initrd images, which are for
storing drivers in a ramdisk so that the kernel can mount / and kick
off init and can be avoided if you build your drivers right into the
kernel instead of into modules, a difference to how the
planetccrma-core rpm builds its' kernel to how the default fc10 kernel
gets build is reveled and some questions come to mind. Obviously, the
planetccrma-core kernel has drivers build into it and I should be fine
having another entry for the rt-kernel without the initrd entry. I
guess putting an entry in grub and rebooting is going to tell me real
fast if my assumptions are correct. The questions I have are:<br><div>
<br><div style="margin-left: 40px;"><ol><li>Are the modules that were
in the original fc10 initrd file get put in the new rt-kernel? I am
thinking somehow my system needed them, if the default fc10 install put
them there.<br>
</li><li>If the rt-kernel has all the modules now, how does adding modules in the future work for other hardware and such?</li><li>Is that strange root=UUID=c14b36c6-4eab-4def-b2ec-a33a006c5164 still needed and, if not, what do I use?</li>
<li>How do I go about changing any module or updating it in the future?</li><li>In addition to the current topic, but something I have always
wonderd--as yum updates get applied after using the rt-kernel, are
these updates being applied to the rt-kernel and do they retain the low
latancy of it?</li></ol></div>Thanks and currious,<br><br>-Sean</div><br>