Fedora :: Yum Update Produces Kernel Errors?
Jul 14, 2010I did 'yum update' this morning. It stopped with the following errors:
Code:
Install 7 Package(s)
Upgrade 207 Package(s)
[code].....
I did 'yum update' this morning. It stopped with the following errors:
Code:
Install 7 Package(s)
Upgrade 207 Package(s)
[code].....
I've run today command: "sudo yum update"
and I've noticed that the new kermel have been installed (2.6.31.12-174.2.3.fc12.x86_64).
After that installation .. my camputer has several errors while booting and it doesn't want to start. So while booting I can see Code...
I got this upon installation of the new kernel:
Code:
And then, on the Cleanup phase:
Code:
My question is, am I going to have issues on reboot, and if so, is there anything I can do to prevent them?
I'm a bit loose on what, specifically, grubby does other than what yum info tells me:
Code:
When using YUM UPDATE from the prompt more than 230 items are scheduled for update however when the download process has completed I receive errors regarding Perl dependences such as:
file /usr/lib/perl5/5.8.8/List/Util.pm from install of perl-5.8.8-27.el5.x86_64 conflicts with file from package perl-5.8.8-18.el5_3.1.i386
I am unsure how to overcome this. It occurs on two different servers.
when I tried to uninstall qmmp (which I had been trialling as a music player) I came across this error.
roy@suzuki:~$ sudo apt-get remove qmmp
Reading package lists... Done
Building dependency tree
Reading state information... Done
[Code].....
I am dual-booting with Windoze XP and just this week notice 2 new ubuntu kernel lines in grub when my computer boots.
Not too sure what to do now - it seems I can't install or remove anything. Also, update manager does not work.
Fedora 11 update released today creates a dependency issue in my x86-64 system: Processing Dependency: kernel-uname-r = 2.6.29.5-191.fc11.x86_64 for package: kmod-wl-2.6.29.5-191.fc11.x86_64-5.10.91.9-3.fc11.1.x86_64 # yum info kernel-uname-r produces "no matching packages to list" the yum info pack tells me kmod-wl is: Metapackage which tracks in wl kernel module for newest kernel so it seems important to have it up to date. What should I do?
View 5 Replies View RelatedTrying to install virtualbox in F12 but fails when recompiling kernel module. Output of vbox-install log is:
Attempting to install using DKMS
removing old DKMS module vboxdrv version 3.1.6
Deleting module version: 3.1.6
completely from the DKMS tree.
Creating symlink /var/lib/dkms/vboxdrv/3.1.6/source ->
/usr/src/vboxdrv-3.1.6
DKMS: add Completed.
Error! Your kernel source for kernel 2.6.32.11-99.fc12.i686.PAE cannot be found
at
/lib/modules/2.6.32.11-99.fc12.i686.PAE/build or /lib/modules/2.6.32.11-99.fc12.
code....
This was also posted under Newbie Forum as I was unsure which was the best spot. On a fresh install of Fedora 12: I am trying to do a software update and keep getting these errors. I am new to Fedora but have used Ubuntu for some time. An Internal system error has occurred:
Under more details it states:
Error Type: <class 'yum.Errors.RepoError'>
Error Value: Error getting repository data for installed, repository not found
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3125, in <module>
main()
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3122, in main
backend.dispatcher(sys.argv[1:])
[Code]...
Now I don't know if those errors each apply to a distinct update but theres about 430 updates available. It looks like maybe I need to add something to the repository? I don't know
The error message is: "est Transaction Errors:
installing package kernel-debug-2.6.31.6-166.fc12.i686 needs 27MB on the /boot filesystem
installing package kernel-doc-2.6.31.6-166.fc12.noarch needs 27MB on the /boot filesystem
installing package setroubleshoot-2.2.50-1.fc12.i686 needs 27MB on the /boot filesystem
installing package perf-2.6.31.6-166.fc12.noarch needs 27MB on the /boot filesystem
installing package hunspell-1.2.8-13.fc12.i686 needs 27MB on the /boot filesystem
installing package gettext-0.17-16.fc12.i686 needs 27MB on the /boot filesystem"
I have boot as a separate partition, this time around I have set it to ext4 for the first time. That partition is only 250 Mb, but that has always been sufficient in the past, perhaps I am holding too many kernels or kernel versions?
I am running Fedora 12 64-bit on a MacBookPro5,1 system. After two weeks of not running Fedora on the system, I boot into it and check for updates with Yum Extender. It only finds a small handful of updates despite the fact that my other system running Fedora 12 32-bit has installed several update over the past two weeks. When I try to apply the available updates I get the following errors: Dependency Resolution Errors:
Missing Dependency: kernel-uname-r = 2.6.32.9-70.fc12.x86_64 is needed by package kmod-wl-2.6.32.9-70.fc12.x86_64-5.60.48.36-1.fc12.3.x86_64 (rpmfusion-nonfree-updates)Missing Dependency: kernel-uname-r = 2.6.32.9-70.fc12.x86_64 is needed by package 1:kmod-nvidia-2.6.32.9-70.fc12.x86_64-190.53-3.fc12.x86_64 (rpmfusion-nonfree-updates)Dependency Resolution Errors:
Missing Dependency: kernel-uname-r = 2.6.32.9-70.fc12.x86_64 is needed by package 1:kmod-nvidia-2.6.32.9-70.fc12.x86_64-190.53-3.fc12.x86_64 (rpmfusion-nonfree-updates)Dependency Resolution Errors:
Missing Dependency: kernel-uname-r = 2.6.32.9-70.fc12.x86_64 is needed by package kmod-wl-2.6.32.9-70.fc12.x86_64-5.60.48.36-1.fc12.3.x86_64 (rpmfusion-nonfree-updates)Missing Dependency: kernel-uname-r = 2.6.32.9-70.fc12.x86_64 is needed by package 1:kmod-nvidia-2.6.32.9-70.fc12.x86_64-190.53-3.fc12.x86_64 (rpmfusion-nonfree-updates)
What is needed to resolve these update issues? Also, I suspect the system is not picking up all the updates that it should. What can I do to determine which updates the system should be getting?
I try to update my kde to kde 4.4.1 from updates repository but i get dependency resolution errors:
Code:
Dependency Resolution Errors:
I checked my system:
Code:
It means i have the newest versions. So how to update my kde?
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 have been running F11 for some time now. I install updates regularly and to this time have had no issues. Now it comes up with error.
Code:
[root@red 2305 ~]
$ yum update
Loaded plugins: protectbase, refresh-packagekit
0 packages excluded due to repository protections
Setting up Update Process
Resolving Dependencies
--> Running transaction check .....
--> xorg-x11-drv-nvidia conflicts with xorg-x11-drv-catalyst
Error: xorg-x11-drv-nvidia conflicts with xorg-x11-drv-catalyst
Error: xorg-x11-drv-catalyst conflicts with xorg-x11-drv-nvidia
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
[root@red 2306 ~]
I do not believe that I even have the 'xorg-x11-drv-catalyst' mentioned here installed:
Code:
[root@red 2315 ~]
$ yum list all | grep installed | grep catalyst
[root@red 2316 ~]
This returns nothing so why the error?
I just installed the latest compiz as per leigh's instructions - nice, easy install!I notice that the snow application is missing. That was my favorite, but where has it gone??
How about floating windows above desktop cube? Dodge? In which upon selecting a window, the non-selected windows move around it to move it to the front.I also notice that many window updates are very poor. For example, in the compiz settings manager when I switch tabs, the window does not actually update unless I move it. I click on a tab and it looks just like the previous tab. If I move the mouse around, it will update the wind in blocks under the mouse, but not the whole window.And, it would appear that the standard compiz is still available from my desktop settings in KDE. Could I have failed to remove the original compiz?
I installed Fodora 12 on my aspire one EEEpc, I was trying to do a software update but i get an error: Code: An internal system error has occurred a problem that we were not expecting has occurred. Please report this bug in your distribution bugtracker with the error description more details: Error Type: <class 'yum.Errors.RepoError'>
[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:
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.)
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.
Did a fresh install of Fedora 12 on a system w/ FC8. hd0 is an IDE drive, hd1 a SATA drive.I successfully preserved the partitions containing /home and several partitiosn containing video data. (This is a myth box.) I had the installer scrub out the / partition. Installed a relatively minimal set of packages.It's up and running!
I bring up Firefox and the Myth install and configure Wiki page. One of the first things it suggests is create a new environment variable, $KVER, then reboot. I do this. When I check out $KVER it tells me I'm running:
2.6.31.5-127.FC12.i686.PAE
Installed the atrpms repository information. I tried installing the rpmfusion repository, but apparently the FC12 information wasn't up yet. So, I thought I'd go atrpms-only. Per the wiki:
yum install nvidia-graphics
(My motherboard has Geforce 7050 / 630) There were a couple of errors about missing firmware during the install. Oi! I also noticed it downloading a new kernel. "Well!" I thought, "If the new kernel is messed up, I'll boot with the other from the grub menu, and try again."
Reboot. System stops dead after the BIOS hardware display. The message "FROM CD" shows. After that, nothing. Booted to Fedora 12 DVD. Hit Rescue. Confirmed that everything is there file system with. Confirmed that grub.conf was there, and looked OK. I edited it so the timeout wasn't zero and so the menu wasn't hidden.
Rebooted. Several times. Every time, it sticks right after the hardware display.I eventually looked up "master boot record" here and found some directions for resetting grub on the MBR. That did the trick.