Fedora Installation :: MBR Mucked Up After Kernel Update?
Nov 19, 2009
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.
On a new install of Fedora 12, I did the online update (using PackageKit). However, though the new kernel with images are seen in /etc/boot it still boots into the old kernel:
New-2.6.31.9-174.fc12 Old-2.6.31.5-174.fc12
Code: $ uname -a Linux LinuxFedora.HomePC 2.6.31.5-127.fc12.i686.PAE #1 SMP Sat Nov 7 21:25:57 EST 2009 i686
I have recently updated my Fedora 11 installation which replaced my older 167 kernel with the newer 217 kernel. However, the 217 kernel will not boot completely. It will show the splash loading screen, and then will switch to a rapidly blinking cursor. This cursor blinks for about 5 seconds and then disappears. I can access terminals using ALT+F2, etc. I can log in to these terminals, but init commands do not complete (something about a binary handler). I'm not sure if something is conflicting with an update to X or what is wrong. The most recent kernel that I managed to get to work was Kernel 167, however I cannot find this kernel for download.
Sys info: AMD Athlon 64 X2 4800+ 3GB RAM nVidia GeForce 8600GT with proprietary drivers 320GB Hard Disk with windows and linux partitions Fedora 11 32-bit i586
Hello, i recently update the kernel in fedora through the GUI update manager and after restarting the new kernel wouldn't boot and i had to reboot into the old one. it freezes right after Plymouth finishes and the login screen should show up it just completely freezes, i do have proprietary nvidia drivers could it be that?
I am unable to boot with kernel 2.6.35.13-92.fc14.x86_64 which was installed while applying software updates. It hangs with the last message issued "Registering binary handler for Windows Applications". Searching led to it being related to a problem with the nvidia drivers. I followed the directions in several posts - delete /etc/X11/xorg.conf, reboot, run nvidia-xconfig, reboot and all is fine, but not in my case. The first reboot works but the screen is wrong. There is a 1 inch wide black border around the presentation window. If I then do the nvidia-xconfig and reboot, i am back to where I was before - boot hangs after issuing "Registering...". If I boot to the last good kernel, everything works fine. This happened to me once before and I was able to fix it by rebuilding the nvidia kernel (I think that was what I had to do), but I can't find out how to do that. I have akmod and kmod installed which are supposed to take care of this problem. I booted to kernel 13-92 recovery mode, deleted the xorg.conf file and ran nvidia-xconfig from there. Still fails. I don't know what to list here, but I will do my best to supply whatever is necessary.
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...
I was trying to update the new nvidia drivers since they dont seem to work in the newer kernel, or to try to fix it but now when i run yum update I get a screen like this:
Downloading Packages: Running rpm_check_debug ERROR with rpm_check_debug vs depsolve: kernel-uname-r = 2.6.38.3-18.fc15.i686.PAE is needed by (installed) kmod-nvidia-2.6.38.3-18.fc15.i686.PAE-1:270.41.06-1.fc15.i686
I install fedora on my usb-hdd. Sometimes i boot it from real machine, sometimes i boot from virtual machine (kvm). When I boot from real machine, hdd driver is usb-storage, when i boot from virtual machine hdd drivers are ata_generic and pata_acpi.
Everytime i update kernel, mkinitrd only create initrd image contains only hdd driver current running, and I must recreate initrd manual with all preload hdd driver. How to config fedora to everytime update kernel, mkinitrd can make initrd image with all hdd driver I need?
9.04 this morning updated my kernel to I believe it is 2.6.28.18 and upon the reboot I had no desktop. It booted wanting to go into low graphics.
So I drop to shell and stop the gdm and try to run the latest nvidia run file I have and it hangs saying I have a x server running.
Otherwise I am needing assistance with getting my desktop back! I can boot into an older kernel and if need be I would like to roll back that latest update this morning, but once again I am forgetting the command line for that.
(after i update packages, it says error, and here's whats in the details tab) Preconfiguring packages ... (Reading database ... 197969 files and directories currently installed.) Preparing to replace flashplugin-installer 10.3.181.34ubuntu0.11.04.1 (using .../flashplugin-installer_10.3.181.34ubuntu0.11.04.1_i386.deb) ... code....
How to fix This? i haven't messed with Ubuntu much...Why am i getting an error about a kernel update?
I have a fedora 11 with kernel package: kernel-PAE-2.6.29.6-217.2.3.fc11.i686
I would like to install the devel package for this kernel version, but I can't find it, because in the fedora repo there is only the original kernel (2.6.29.4....) and in the updates repo there is only the newest kernel package (2.6.30....)
Where can I find the packages which are between the fedora and update repos' versions?
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 installed the fedora 14, but there is no kernel source tree.I read the doc "building a custom kernel".But I don't want to rebuild a new kernel.I just want to install the source tree of current kernel.Could someone tell me the way?
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 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?
It seems that updating the Kernel breaks my installation. I've tried it twice, and both times it disabled my gui desktop. I'm posting this with links2 in my terminal. The terminal works perfectly.
This is really annoying, as I can't even use my computer. What do you think is the problem?
Running Karmic on my laptop, I get very occasional kernel panics (suspect it has something to do with the Broadcom WiFi because it only seems to happen with heavy network traffic or HDD access), but just my lucky, this time it Panic'd on me during my recent update -> linux-kernel 2.6.31-20. My system still 'works', but I get the following when doing any other updates, now:
Code: sudo dpkg --configure -a [sudo] password for tango: Setting up linux-image-2.6.31-20-generic (2.6.31-20.57) ... dpkg (subprocess): unable to execute installed post-installation script: Exec format error dpkg: error processing linux-image-2.6.31-20-generic (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-2.6.31-20-generic; however: Package linux-image-2.6.31-20-generic is not configured yet. dpkg: error processing linux-image-generic (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (= 2.6.31.20.33); however: Package linux-image-generic is not configured yet. dpkg: error processing linux-generic (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-2.6.31-20-generic linux-image-generic linux-generic
Now I cannot seem to get rid of that, and of course, I am stuck in the prior version. Granted everything 'works' - but it bothers me. What's the best way to go about tracking down and hashing out a problem like this?
When trying to clean up old kernels I accidentally deleted the current kernel (2.6.35-24). I then had problems when I reinstalled and found that I could only boot into command line mode. I was able to fix this problem but have since installed the latest kernel release (2.6.35-25) and now have the same problem as before. Of course, I could do what I did before but I guess this is going to occur whenever I upgrade in future.
Linux paneasbox 2.6.35-27-generic #48-Ubuntu SMP Tue Feb 22 20:25:46 UTC 2011 x86_64 GNU/Linux I want to update my kernel to the latest version from kernel.org, which is the mainline 2.6.38-rc8 .
EDIT: I found this guide [URL].. and I will give it a try
After upgrading Maverick (perfect!) to Natty, I was unable to boot into anything. (kernel 2.6.38). However, through much PITA, I was able to boot into an older kernel. (2.6.35). I completely removed 2.6.38, rebooted, reinstalled it and ran update-grub. However, 2.6.38 is no longer available no matter how many times I run update-grub, and the only option left is 2.6.35. In my humble opinion, the Natty upgrade experience is rubbish. (blank screen, total PC hangs, boots into a blank screen with only a blinking cursor, NVIDIA official driver not working, bootable only into older kernels etc.)
I tried to update Linux kernel (2.6.39) but after installation procedure PC won't boot into NEW kernel, I get only BLANK screen, but hopefully older kernel works just fine (2.6.38-9), how to fix it, that I can fluently boot into 2.6.39?
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.
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:
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:
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?
