Fedora X86/64bit :: Kernel Update Fails To Install - 2.6.27.15-170.2.24.fc10
Feb 19, 2009
I just tried to update to kernel 2.6.27.15-170.2.24.fc10 (x86_64) at the suggestion of the gnome update widget, and the process hung. A bunch of other things were updating at the same time, many of which were related to audacity or wine.
I'm not sure just what was being updated, because the option to review which updates are available does not work - when I click on it, nothing happens, but when I take the other choice (install all updates), I take pot luck. It would be nice to be able to choose which programs to update, and to be able to upgrade the kernel independently, but I don't seem to be able to do that at the moment.
Downloaded from here: [URL] then ,it is 32-bit and I need to know what all 32-bit libs are needed as dependency for skype to work. I am on Gnome Fedora and purposefully selected static version of skype to prevent installation of libqt4.
my update today failed, because the packages raydium and maniadrive depend on libphp5-5.2.9.so, which is provided by php-embedded, which is (apparently) not in the fedora 64bit repository There does however seem to be an i586 version...
I am unable to boot my Fedora 14 after last nights kernel update. When I start the boot up and hit F2 the system fails after outputting the line : Starting vservers of type 'default'. At some point the console displays an error message :
serial8250 : Too much work for irq17
How do I restore my previous version? I know some people have suggested in the past - just modify the grub.conf but how? When I boot off the cd I only get access to the liveuser disk. I need to have access to my own /boot/grub/grub.conf file.
My main systems runs Fedora 14 x64 with the latest updates (I can't check anymore, but I believe it has the .13.91 x64 kernel). Since this afternoon it became unsuable. First, Opera Browser crashed and the crash report app of the browser showed up. Clicking one of the options there resulted to X crash, if I understood what really went on. No input, mouse or kb, I couldn't go to tty etc. I had to do a hard reset. Next boot proceeded normally up to the point that GNOME desktop is fully loaded. ABRT began reporting numerous kernel oops. Rebooted again (noticed that init.d fails, so hard reset again) and tried past two kernel versions, same results. Yum crashes and so does everything. I tried to revert all recent updates with yum history, but yum crashed.
Last update was May 22, and it updated kmod-nvidia.
Quote:
uname -a Linux innovator 2.6.35.13-91.fc14.x86_64 #1 SMP Tue May 3 13:23:06 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux initial crash Package: kernel
[code]...
before the reboot Opera 11.11 had crashed and it's own bug report tool came up. Clicking the "do not report this error now" option probably crashed X, because the screen went black and no input was possible (no mouse or keybord, so I couldn't go to tty either. Had to do a hard reset) Bug Reports:Kernel oops report was uploaded
One of the numerous crashes Package: kernel Latest Crash:Τρι 24 Μάι 2011 09:19:56 μμ
After updating my kernel from 2.6.34.7-56.fc13.i686 to 2.6.34.7-61.fc13.i686 I can't boot anymore. The error message says: "No root device found Boot has failed, sleeping forever." I'm booting from 2.6.34.7-56.fc13.i686 now but I would like to sort this thing out. What should I do? File a bug? I never did that, so I don't know where to go.
I assumed this had to be a FAQ, but after hours of searching, how to do this on FC11, but that didn't work with the yum on FC10. I don't need a huge list, but at least the basics (ld-linux.so, and I imagine the C++ compatibility libs).
Keep 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'm I seeing this wrong or is the initrd file in kernel-2.6.27.25-170.2.72.fc10.x86_64 a zero byte file and that's why I can't boot with it( get this "kernel panic not syncing VFS unable to mount root fs on known -block (0,0)" message)
Initial FC12 install worked great, kernel 2.6.31.5-127.fc12.x86_64 allowed radio kill switch functionality Fn-F11 for wlan and Fn-F12 for bluetooth.The last two kernels have broken that functionality.
Finally updates are broken - I've been able to use my upgraded F12 system for some time, faithfully keeping up with f10, then f11. Just yesterday it finally broke:
Test Transaction Errors: installing package kernel-2.6.31.12-174.2.22.fc12.i686 needs 10MB on the /boot filesystem
It would appear that the most recent kernel update has broken the 10MB barrier initially set by the version I first installed (for the boot partition). Needless to say, I have quite an investment in this machine, and of course no time to back it all up and do a fresh F12 install. I am hoping someone out there can give me a bulletproof way to steal some space and expand the boot partition...
Googled this and found the same problem mentioned in the yum site: [root@plouton ~]# yum update kernel Loaded plugins: refresh-packagekit Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package kernel.x86_64 0:2.6.33.6-147.fc13 set to be installed --> Finished Dependency Resolution --> Running transaction check ---> Package kernel.x86_64 0:2.6.33.4-95.fc13 set to be erased --> Finished Dependency Resolution Dependencies Resolved
I have programs that work in FC10 and FC12, but when I run them on FC11, i get behaviour that is very similar to a deadlock. They don't crash or anything. It just seems that all program output stops at one point and never resumes. I am wondering if FC11 has any known threading issues that one may need to know about before trying to use it to run their software from FC10 or FC12. Maybe something in the way that threading is handled differently from FC10 or FC12 that is not necessarily a problem, but just needs to be kept in mind when writing code for FC11.
I have fedora 10 installed and when my monitor is turned off the X session fails to start because it can not probe for settings. Is there a way to hard code the settings for x instead of letting them assign dynamically on boot?
Since 2.6.27.19-170.2.35.fc10.x86_64, dhclient wlan0 doesn't seem to work any more.
However, bizarrely, dhclient eth0 does (to the same D-link wireless router).
The AP shows connected - tail /var/log/messages
No working leases in persistent database - sleeping.
WINXP connects just fine. This (B43) has worked nicely ever since FC10 came out, and I was able to use the WiFi at all kinds of places on a recent trip. Other than a couple of yum updates, I don't think anything else has changed since. Other devices on the wlan are getting their DHCP requests satisfied correctly.
Is anyone else having this problem since about a week ago? Perhaps there's something really obvious I'm missing. I can manually assign an IP address to wlan0, manually edit the routing tables and edit /etc/resolv.conf, and then Wifi seems to work OK, so it doesn't seem to be b43 itself unless it is dropping DHCPOFFERS. If this isn't a regression, does anyone have any tips about how to debug this?
Here's the deal: I had a nice little fileserver running under 2.6.27.21-170.2.56.fc10.x86_64.
3 disks in raid 5 ext4fs, then I thought..."hey I'm a greedy bastard..I want another drive!!
So I get it..do a normal mdadm --grow...after around 1100 minutes .. FINISHED!..whee..happy...
I decide to do a upgrade to 2.6.29.2-52.fc10.x86_64 to get the fix for growing the ext4..
reboot...
Code: md: bind<sda3> md: sdc3 has same UUID but different superblock to sda3 md: sdc3 has different UUID to sda3 md: export_rdev(sdc3) md: sdd3 has same UUID but different superblock to sda3
I was finally able to install Fedora 11 x64 after choosing to only install packages from the repository on the install DVD. Prior to that when I had chosen tio install from the default online repositories, the install itself failed with a Python exception ( see my other post ). Now, however, once I boot after the install I eventually receive a kernel panic message, and failure. The exact same thing happened with CentOS 5.3 x64 after a flawless install. So unless someone knows what might be going on I will assume that Fedore, Red hat, and offshoots for x64 bit systems are just not for me. I have been able to successfully install the latest Mandriva and SUSE x64 Linux distros so whatever Red Hat/Fedora has done just does not work on my system.
I am getting a problem when login into FC10. It boots correctly an shows the login screen; then, when typing my user and passwd goes to the desktop and shows a KERNEL FAILURE. At this moment, most of the times the PC is blocked and doesnt works any more. One time has continued working without problems.
After the las failure, my system log has this info:
Code:
I have checked my hard disks (fsck) y every thing looks fine. However, i dont know how to fsck the VolGroup0. I cant'get it unmounted.
So, my second real attempt at getting the 64 bit F11 up and running. I just started adding stuff before all the updates. Crash. So, I'm in the post install phase. Before anything else I installled akmod-nvidia manually, rebooted, and I'm doing yum update right now. I'm hoping many dependencies are solved in the update. There are about 209 line items to update after the initial install. Been updated all afternoon.
So, after the updates are done, I'm heading over to download the different repos I need for the fun stuff. Did you know Java is installed with this first yum update? Wasn't like that in F10. I think I tried 5 times on F10 before I got it right.
Just installed FC10 and noticed no sound with latest kernel (2.6.27.15-170.2.24), however I do have sound with kernel 2.6.27.5-117. No other differences. Anybody else have this problem?
I recently got the Message, that i should do a partial System Upgrade. It included an update to Kernel 2.6.34. Since this update, i cannot boot with this kernel:
Code: Mounting none on /dev/ failed...
i can still boot with older kernels, but many drivers including wifi and graphics drivers dont work there anymore.
when I launch Yast2 - Online Update, I get an error during the repository refresh that it could refresh the repository.Since it's easier to copy-paste - here is the output from 'zypper ref' with the same error:
Code: Retrieving repository 'Updates for openSUSE 11.3 11.3-1.82' metadata [|] Failed to download ./repodata/cefcc9d56264aa169f70a53c560ffc39cb6af575-deltainfo.xml.gz
from http://download.opensuse.org/update/11.3/ A[code]...
I've just installed Fedora 11, and in the process of testing it, decided on trying out virtualization tools.
Services: libvirtd, xenner and xend are started and i'm still unable to connect to hypervisor with the message:
Unable to open a connection to the Xen hypervisor/daemon.
Verify that:
- A Xen host kernel was booted - The Xen service has been started
Unable to open connection to hypervisor URI 'xen:///': <class 'libvirt.libvirtError'> unable to connect to 'localhost:8000': Connection refused None
xend.log is empty
Now, I've also tried installing Fedora 11 x86_64 as a guest OS with KVM/QEMU as a solution, and the installation process starts, but after some time, the console screen goes black and there is no DVD driver activity or HDD led activity. The CPU is at 2-5 % utilization. And there is nothing I can think of to 'resume' the installation or whatever.
[Code].....
Now, I've tried the same thing 3 times and the process always hangs during the installation with the same symptoms.
