When yum updates the kernel it keeps the last 3 versions; the older kernels are deleted. Is there a way to keep more than 3 versions?
I presently have one working version and two which are not compatible with my machine. One more bad version and my system will be toast. (I would like to keep the "bad" versions for testing.)
I checked my kernel version (uname -r) and see I'm on "2.6.34.8-0.2-default", and I noticed that they just released 2.6.39. I'm assuming (perhaps incorrectly) that there's been at least versions 2.6.35/6/7/8 released in there. Why isn't my openSUSE 11.3 using anything more recent than .34? How does this updating work? Is 11.4 on a more recent one?
View 8 Replies View RelatedI need to prevent that the latest kernel update removes the only kernel that still works in my computer. how can i do this? Currently I have 3 linux kernels versions:
Code:
Ubuntu 10.04 LTS, kernel 2.6.32-23-generic
Ubuntu 10.04 LTS, kernel 2.6.32-23-generic (recovery mode)
Ubuntu 10.04 LTS, kernel 2.6.32-22-generic
[code]...
But only the oldest works. With the new update there is a new kernel version (2.6.32-24) that possibly will not boot (like previous 2.6.32-* kernels) and also I expect that, as in previous updates, the oldest kernel will become inaccessible, thus rendering my ubuntu unbootable.
PS: unsolved threads on the underlaying problem: Can't boot default kernel after upgrading from 9.xx to 10.04 lucid Upgrade to 10.04 freezes on the Ubuntu screen
How do I know the exact kernel version (or rpm package name) of fedora 14 without having to install one? I couldn't find the information on the the website. And one more question. Does one fedora distribution has only one kernel available all the time? Where can I find all the kernels for a particular distribution (for example Fedora 12) distributed by Fedora Project? I can find all the available kernels for a RedHat Enterprise distribution on [URL], but not for Fedora.
View 1 Replies View RelatedAfter some updates Jessie 8 my boot grub shows now 2 kernel versions to boot from.
3.16.0-4-amd64
3.16-3-amd64
- How do I know which one is the newest and if happy with it, how to remove the older one?
In the processing of reinstalling VirtualBox, I found this：2.6.35.6-48.fc14.i686.PAE/source -> /usr/src/kernels/2.6.35.6-48.fc14.i686.PAE/ ，but this folder don't exist.。 I try to relink the ln as source -> /usr/src/kernels/2.6.35.9-64.fc14.i686.PAE , but VirtualBox still get problem with the kernel. Since VirB works fine with other 2 kernels, the solution for this is not quite needed, but I just wonder why this happens. See below. I don't know why these two folder contain different version of kernels. Anybody get an idea?
2.6.35.6-48.fc14.i686.PAE]$ ll /usr/src/kernels/; ll /lib/modules/; ll /lib/modules/2.6.35.6-48.fc14.i686.PAE/ |grep build
total 16
drwxr-xr-x. 22 root root 4096 Nov 19 14:58 2.6.35.6-45.fc14.i686
drwxr-xr-x. 22 root root 4096 Nov 15 00:04 2.6.35.6-48.fc14.i686
drwxr-xr-x. 22 root root 4096 Dec 8 17:08 2.6.35.9-64.fc14.i686
drwxr-xr-x. 22 root root 4096 Dec 8 15:19 2.6.35.9-64.fc14.i686.PAE
[Code]...
From F12 to F13. Is there anything I should remove before updating? I have few programs isntalled from source/binary installers in /usr for example. Would it cause problems?
And is there any chance to be able to switch from a 32 bit kernel to 64 bit kernel during the update? The hardware is capable of this.
I've been having some odd kernel issues recently. A while back I installed 2.6.32rc6 when I first upgraded to 9.04, because it solved issues I was having with surround sound. A few months back I installed mythtv and the mythbuntu binaries as well, although I have since uninstalled them. All of a sudden, I seemed to have issues booting into ubuntu with certain versions of the kernel, where it would just freeze at the white ubuntu logo, while other versions of the kernel would load fine (I think 2.6.31?) but it would display the mythbuntu logo instead (not sure if this is related).
I just upgraded to 10.04, and I still seem to have issues booting with certain kernel versions. Right now I'm running 2.6.32-020632rc6-generic which seems to work, but it's outdated, and I have surround sound issues again. Which one should I be using? Is there a way to clean this mess up? How do I fix the problem of freezing at the boot screen?
it turns out that I don't have my Ubuntu option in GRUB any more. I need the kernel version in order to add it to my list file. Any help? I can't boot it to find out because GRUB doesn't recognize it as an option.
View 4 Replies View RelatedTrying to install VMWare I get the following message:
Really after it VMWare anyway doesn't agree to install. Zypper says that no newer version of gcc is available. So I can't see how I can install VMWare.
I'm sorry if this is recurring subject, but I have searched the forum for such a subject and can't find one.I'm using Xubuntu 8.10, I'd like to update my programs to the latest releases, but the available updates in 8.10 versions are not the newest ones. I can't upgrade to a newer version of Ubuntu due to some known issues with older Intel drivers.
Is it possible to have the latest updates of packages while I still using 8.10 version?
My Grub2 boot menu includes:
Ubuntu, Linux 2.6.31-19-generic
Ubuntu, Linux 2.6.31-19-generic (recovery mode)
Ubuntu, Linux 2.6.31-14-generic
Ubuntu, Linux 2.6.31-14-generic (recovery mode)
Q1) I only really need the latest kernel, 2.6.31-19, don't I?
Q2) So how can I get rid of the two 2.6.31-14 entries?
Here's how to always have only the latest kernel version in your grub:
Code:
sudo gedit /etc/grub.d/10_linux
Find these lines:
Code:
list=`for i in /boot/vmlinu[xz]-* /vmlinu[xz]-* ; do
if grub_file_is_not_garbage "$i" ; then echo -n "$i " ; fi
done`
And change it with this:
Code:
for ver in /boot/vmlinu[xz]-* ; do
list="$ver"
done
Notice two differences.
1. There's no ` before "for" and after "done" keywords.
2. There's no list= before "for"
If you want to change the name of entry, scroll down to the end of the file and find last two occurrences of:
Code:
linux_entry
${OS} stands for Ubuntu and ${version} stands for your kernel version. I changed this into:
Code:
linux_entry "${OS} 9.10 Karmic Koala"
You can use your own imagination. If you want to have specific name for your Windows entry, in /boot/grub/grub.cfg copy everything between:
Code:
### BEGIN /etc/grub.d/30_os-prober ###
and
Code:
### END /etc/grub.d/30_os-prober ###
paste it in
/etc/grub.d/40_custom
Change the text between double quotes right after menu entry. (For example, my 40_custom looks like this now:
Code:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the menu entries you want to add after this comment. Be careful not to change the 'exec tail' line above.
menuentry "Windows 7" {
insmod ntfs
set root=(hd0,1)
search --no-floppy --fs-uuid --set bcdc24dddc249424
chainloader +1
}
)
and make 30_os-prober not executable:
Code:
sudo chmod -x 30_os-prober
If you want to remove recovery mode entry, just uncomment this line in /etc/default/grub:
Code:
#GRUB_DISABLE_LINUX_RECOVERY="true"
PS Don't forget to run
Code:
sudo update-grub
After you finish editing everything! And check in /boot/grub/grub.cfg if everything is ok!
I have looked for existing threads on this issue, but found no matches, so I am starting a new one.I first installed Ubuntu 9.04 on my laptop from a bought CD last year. When I later installed the kernel updtates with the Update Manager, I noticed the the list of versions growing when I booted up. Then something horrible happened. After installing maybe the third or fourth kernel update, I couldn't boot into Ubuntu, it failed every time. After that I left Ubuntu broken on my laptop for a while.I have now reinstalled from the CD again However, I am now very wary when it comes to installing even the important security updates, never mind the recommended ones! I prefer to keep it simple, because I don't want to do any more reinstalls for a while. So far I have just one kernel headers update on the boot list, and I am trying to figure out how to remove the previous one. I do not see the point in having a growing list of them again.
View 9 Replies View RelatedToday, I used the Update Manager to do my first post-installation update of Ubuntu 9.10. I have a multi-boot setup (Ubuntu / WinXP), using GRUB2. Before the update, I had 5 options:
Ubuntu, Linux 2.6.31-14-generic
Ubuntu, Linux 2.6.31-14-generic (recovery mode)
Memory test (memtest86+)
Memory test (memtest86+, serial console 115200)
[Code]...
Is it valid that the -14- has remained in the list? Surely I can only boot -20- now? How should I get rid of this version since it is added by update-grub because of the existence of this file: /boot/vmlinuz-2.6.31-14-generic,Should I delete the file or just rename it? Or is there a better way?
ubuntu lucid, firefox 3.6... but it seems the firefox 3.6 is not a complete 3.6 as its gecko is 3.0...; so whenever i want to install a update that is for ff >= 3.5, i always get, that this addon is not available for ff 3.0... my question:
1. is it normal that the ff 3.6 is running on gecko 3.0 on ubuntu? cuz in windows the ff 3.6 also has the 3.6 gecko
2. if so.. how can i update that gecko?
I have tried a lot of distributions, and have been using Ubuntu for the last year or so. However I would really like to use a good KDE4 distribution. I do have some stringent requirements though.
1- Easy and quick to get it up and going.
2- It needs to use pulse (or at least very easy to add it and get it working). I know a lot of people don't like pulse, but I can't do what I need to do without it.
3- it needs to have a large repository (like ubuntu, debian, or any major distribution). It also has to have a good package management system, again like ubuntu, debian, but not like slackware.
4- I would like it to be easy to update to new versions. I don't care if it is a rolling release or not, but I don't want to have to install it all over again each year.
5- I want it to be a stable system, not too cutting edge, but also not too old.
6- It would be nice if it had multimedia codecs, etc included like mint. But it is ok as long as it is not too difficult to get them installed later.
[Code]....
I am receiving a transaction error when I try to update to a newer kernel, the error is:
Test Transaction Errors: installing package kernel-debug-2.6.32.16-150.fc12.i686 needs 519KB on the /boot filesystem If I run disk usage I get:
# du -h /boot
217K/boot/efi/EFI/redhat
219K/boot/efi/EFI
[code]....
System monitor shows I have 56% free in /boot. So where can I get the extra free space or force yum to recognize there is enough in that directory?
I'm using F13 and I would like to update my computer using yum update.
I did this a few weeks ago and yum update downloaded and installed
Quote:
kernel i686 2.6.34.7-61.fc13
After a reboot I got
Quote:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
To get around this I did a ctrl + s and booted to an earlier kernel. Once in I deleted the latest kernel using
Quote:
rpm -q kernel
to list the available kernels and
Quote:
rpm -e kernel-version
to delete the latest kernel. Once deleted my computer starts up perfectly.
How do I run yum update without reinstalling the bad kernel?
I do not understand this problem. I am using kernel 2.6.35.10-74.fc14.i686.PAE and while that works fine I know new kernels makes things work better. As such, every time a kernel update comes along just like all other updates, I perform a yum update. But for some unknown reason, I am successfully updating everything except the kernel.
I have attempted updates with 2.6.35.11-83.fc14.i686.PAE, 88, and 12-90 and at the very beginning of the boot I always get the same panic error and boot freeze. The message is ALWAYS as foolow. The only part of the message that changes is the kernel numbers.
[I did my best at hand writing the error message.]
I hope this makes sense to someone.
MESSAGE:
Traceback (most recent call last):
File "/init" , line 157 , in <modules>
if _name_ == ' _main_ ' : main()
[Code]....
Does any of the above make any sense?? I cannot even figure how I am supposed to fix anything since the computer completely freezes at that point! I am, of course, able to hard reboot. The I switch back to the previous kernel and everything is fine but why does everything EXCEPT the kernel update?
I attempted to install the new kernel 2.6.29.6-217.2.3.fc11 (x86-64) A depsolv message appears:
Quote:
ERROR with rpm_check_debug vs depsolve:
kernel-uname-r = 2.6.27.19-170.2.35.fc10.x86_64 is needed by (installed) kmod-wl-2.6.27.19-170.2.35.fc10.x86_64-5.10.79.10-1.fc10.x86_64
kernel-uname-r = 2.6.27.21-170.2.56.fc10.x86_64 is needed by (installed) kmod-wl-2.6.27.21-170.2.56.fc10.x86_64-5.10.79.10-2.fc10.x86_64
[Code].....
I upgraded from fc10; there was a residue of four fc10 2.27 kernels in /lib/modules from my fc10->fc11 upgrade; I moved them to a new subdirectory /usr/oldmodules, but the yum update command still produces the same failure message.
even from a terminal it wouldn't update? Maybe because I put my bootsector as ro ?
I don't know here is the message:
Last Saturday, I ran an update on my laptop using F12 and received a new kernel. As of this morning, the new kernel hasn't shown up on my desktop, using f 11. (Yes, I check every day.) Currently, my uptime is 34 days, so you can see how long it's been since the last kernel update for F11. Does anybody know why there'd be an update for one version and not for another? In case anybody's wondering:
[joe@khorlia ~]$ uname -r
2.6.30.10-105.2.23.fc11.i586
I'm using F13 64bit with the proprietary nvidea driver. From yesterday's software update, a new kernel was installed:
old kernel: vmlinuz-2.6.33.5-112.fc13.x86_64
old initramfs: initramfs-2.6.33.5-112.fc13.x86_64.img
new kernel: vmlinuz-2.6.33.5-124.fc13.x86_64
new initramfs: initramfs-2.6.33.5-124.fc13.x86_64.img
I load grub from another distro partition. After the update, I changed the two lines in menu.lst, as per the above mentioned, to match the new kernel.
The problem now is that after booting F13, my monitor displays a warning saying "video mode not supported".
These two files are now at /etc/x11:
xorg.conf.livna-config-backup:
# Xorg configuration created by livna-config-display
Section "Files"
ModulePath "/usr/lib64/xorg/modules"
EndSection
[Code].....
I'm not sure if it's exactly the same issue as mine. In case it is, it looks like that all I have to do is:
1 - boot from the previous kernel, and
2 - code: "yum install akmod-nvidia"
After installing the latest updates (dont know which ones) yesterday, I get a kernel panic (LED lights flashing at the keyboard and black screen) when starting X (the login manager). I am running on 64 bit with the proprietary ATI catalyst driver. How can I start in text only mode?
View 5 Replies View Relatedwondering if fedora 15 users will get kernel 3.0 by update,, or is that a typicall update for FC16??
View 5 Replies View RelatedKeep trying update the packages (36 in total) and every time I keep getting this error
ERROR with rpm_check_debug vs depsolve:
kernel-x86_64 is needed by kmod-nvidia-2.6.26.6-49.fc8-173.14.12-5.fc8.2.x86_64
kernel-x86_64 is needed by kmod-nvidia-2.6.26.8-57.fc8-173.14.12-5.fc8.3.x86_64
Please report this error at [URL]
I just updated my kernel to kernel-2.6.29.5-191.fc11.x86_64 on my x64 system, after I reboot my machine, the Fedora loading bar comes up and finishes but then no gui comes up. I attempt to issue commands at the hanging prompt that comes up but nothing happens. I can boot into my older kernel just fine but not the updated one.
What can I do?
The girlfriend did an update a few nights ago. Besides removing her NVidia drivers, it also installed kernel version 2.6.27.29-170.2.78.fc10.i686.
That kernel was causing problems. Now it won't boot at all. How do we remove that kernel altogether?
If we remove it, would simply doing another update from the previous (still working) kernel just try to reinstall that bad kernel?
I am trying to update my fedora 8 kernel, is there a way to do that? I build the one of kernel.org but when i want to boot it a get a lot of messages like:
mount: cant find /dev/root
I tried to follow the guide at building a custom kernel for fedora, but thats just for the last supported version of the kernel of fedora 8.