Fedora Installation :: New FC12 Kernel Will Not Boot
Nov 17, 2009
I just upgraded to Fedora 12 x86_64 via yum upgrade. However I have problems with booting. The new FC12 kernel won't boot. Boot output is something like
ERROR: sil: RAID type 253 not supported
ERROR: adding /dev/sda to RAID set "sil_ajabaccaaidg
ERROR: sil: RAID type 253 not supported
ERROR: adding /dev/sdb to RAID set "sil_ajabaccaaihe
No root device found Boot has failed
I resized boot partition to 400MB, formatted it as ext4 and recopied all files, modified fstab to update boot partition's UUID. Tried to set a boot flag on boot, still, I can only boot with the old kernel from Fedora 11. Is it a Fedora 12 kernel's bug or something wrong with my setup? I don't use any RAID, and the sil error is present with Fedora 11 kernel also.
I have some programs, that will only install on i586 architecture (opposed to x86_64). My CPU is 64-bit architecture. Can I install FC12/11 with i586 kernel on the hardware? How? Any disadvantages except the fact that I'm supposedly not able to use the 64-bit feature of the CPU?
I had FC10 working nicely but decided to move to FC12 to be able to use the latest and greatest... Turning out to be nightmare!
My HDD is partitioned into three:
(hd0, 0) 100MB : used to be original /boot for FC 10 (hd0, 1) 120GB : /home (hd0, 2) 30GB : / > First thing tried: preupgrade
Using this preupgrade setup happend and asked to reboot. However, upton reboot got locked in stage2. So this option was abondoned.
> Second thing tried: installation CDs
Using this method formatted (hd0,2) and installed FC12 on (hd0,2). However, did not change anything on (hd0,0). This still held all the upgrade information from the previous trial. Now, when I rebooted after the install there was a kernel panic with error "kernel panic not syncing vfs". Thinking it might due to the (hd0,0) partition and errors in my install, I abandoned this.
> Third thing tried: installation CDs
Using this method I formatted both (hd0,0) and (hd0,2). The install was similar to above but now (hd0,0) was also formatted and after install was empty. But upton reboot I still got the "kernel panic not syncing vfs" message. I dug through google and saw references to problems in grub.conf and lo behold there were problems with my grub.conf. I don't see the initrd line at all nor do I see the initrd*.img file in my disk. The grub.conf is:
my problem is on installing nvidia driver on fc12 32bit but, first of all, as i understood the pae kernel requires more than 4gb of ram,i have a 2.2 ghz cpu with 2 gb ram,but when i run command:uname -r it answers: 188.8.131.52-127.PAE [i have fc12 32 bit] when we try to download linux we have a 32bit edition or 64bit edition,do we have an edition which is only for pae? or when we install for example the 32bit edition on a computer with more than 4gb of ram then the kernel automatically will change to be a pae kernel??
Have had a clean perfectly working copy of 184.108.40.206-166 for months and after two updates to 220.127.116.11-174.2.3 and 18.104.22.168-174.2.19, neither of the newer kernel versions will allow machine to boot properly. Start-up hangs at the preload daemon with a flickering screen. To use machine, must use grub chooser and choose the original base kernel.
Running on Tyan h2000m board, opteron 2356, Nvidia 9800 GTX+ and 12GB of dram with SELinux security enabled.
Not wanting to speculate why, in the repositories, Fedora doesn't *also* provide a on-KVM enabled kernel counterpart to the default KVM enabled kernel that *is* supplied, I must say I'm frustrated that they haven't done this simple thing.
Considering that everyone who upgrades to KVM enabled FC12 from a previous non-KVM release of Fedora (like FC10) ... considering that these people will be guaranteed to no longer be able to run VirtualBox or VMWare Workstation after upgrading, is a disappointing oversight by / or intent of Fedora (one that manifests in *lost productivity*).
And try though you may to install the kernel source RPM and compile it after running "make xconfig" to disable KVM support, you usually can't! Fedora kernel compile attempts often die very early in the "make" process, indicating something like ...
"Kernel compile error: No rule to make target `missing-syscalls'
or some other silliness. And when you successfully compile a "kernel.org" kernel, and try to boot it, you get all kinds of missing library errors (etc).
Given that it would be simple to provide both a KVM enabled kernel (as they do), and also a non-KVM enabled kernel (which they don't) so the rest of us can seamlessly continue to run VirtualBox and/or VMWare Workstation after an upgrade - and avoid getting entangled with deciding whether use KVM or XEN for guest O/S's... it's a frustrating misstep to not have done this basic thing (i.e. include a non-KVM kernel). It was a rude awakening when we tried to launch VirtualBox only to have it fail after the upgrade.
Anyway, has anyone successfully compiled their own kernel for FC12 and not get errors after boot? If so, which sources did you use; and what kernel version? In the meantime I'll try out other kernels and compile options.
Having just updated various files including the kernel using Package Manager I no longer seem to have the correct version of the Nvidia graphics driver. On previous updates this has been done automatically by the "kmod Nvidia" Metapackage. My last kernel was 22.214.171.124-163 fc12.i686.PAE and the Nvidia driver for that did get downloaded correctly. Looking on Yumex I cannot see a driver for this latest kernel listed.
I have an issue with kernel-126.96.36.199-174.fc12.x86_64. I ran the updates on Christmas Eve and it updated from kernel-188.8.131.52-166.fc12.x86_64 to kernel-184.108.40.206-174.fc12.x86_64. When I rebooted, I no longer received the Fedora Bubble boot screen. It comes up with the Fedora boot bar (across the bottom). Also, I receive failures during boot with the following:
Forgive me if I have posted this in the wrong forum, first time poster with Fedora. I have been using Linux for some time now, mostly Mint, but Fedora 12 @ work. Anyway, I receive the following error in my /var/log/boot.log:
Code: nvidia.ko for kernel 220.127.116.11-70.fc12.i686 was not found and the driver does not load (My xorg.conf file is not loaded), but once I am at a
I am having a problem with lockups on a new FC12 box (dual core 3 ghz, 4 gb memory,nvidia 8400gs). This happens reliably when replaying MythTV videos, but also randomly at other times using other apps (I suspect also boot but I can't be sure; it just occasionally stalls part way through the boot display).
Usually but not always this is accompanied by a kernel panic (caps lock + scroll lock lights flash on keyboard).
I did a core dump with kdump and it reports: Thread 1 (<main task>): Cannot access memory at address 0xffff880028025b70I am in the process of running memtest86+ right now. It's been through several passes without errors. I'm going to let it run some more, but if that is dependable it's looking like the RAM sticks are not the problem.
I had fedora 12 installed on a Macbook pro Intel first generation with ATI Radeon graphics card (see the attachment). Compiz crash when trying to watch *.wmv movie codified with wmvvc1dmo on kernel-PAE-18.104.22.168-67.fc12.i686. I want to convert the film to *.mpg, then I download the mplayer codecs in order to see the film, I can do it without problems with the on kernel-PAE-22.214.171.124-174.2.22.fc12.i686. But I updated my system last Saturday and when I was trying to see the movie again the computer began to respond really slow, then I began to close applications and when I tried to restart I got the message: "compiz is not responding".
I tried again but the same problem. Other thing that I noticed is that when the computer go to sleep, when I wake up it, the display show horizontal black spikes, it is like it doesn't have the appropriate refreshing rate. I think that the problem is related with the acceleration on graphic card. Yesterday, I booted on kernel-PAE-126.96.36.199-174.2.22.fc12.i686, and I watched the film, and the wake up was without problems. That is the reason I call it a regression.
kernel-188.8.131.52-90.fc12 seems to break 802.11n with my intel 4965 chip on my thinkpad t61p. Anyone else seeing the same thing? iwconfig shows extremely low bit rate. dmesg doesn't show anything at all unusual.
I use a pretty fresh installed RHEL 5.4, which should be very similar to Fedora. After the basic installation I installed xen and xen-kernel via yum with no errors. I can select the xen-kernel at boot time. But after booting the normal kernel shows up.
My current task is to add windows 7 to fc12. From other postings it seems the next step is to use the fc12 install disk to create a windows partition from the unused space. Could someone inform me about whether this will delete my current installation of fc12 and my home directory.
When I boot up F12, after I have decrypted the hard drives and after the services have started but before I get to the login screen my display flashes a series of interlaced lines across the screen. As far as i can tell theres no other problems with my computer, everything else seems to work fine. Its been there awhile now and its still there after a yum update. On first boot up of the day it shows white/gray lines (firstboot.jpg) [URL]. On subsequent shut down, boot ups it shows a blue, almost denim like display (shutdown.jpg) [URL]. Theres no problem if i just do a restart. Maybe related as well, last week some time my computer froze (opening large file, watching dvd and had firefox open, guess I ran out of memory?) So I did a reboot using the button on my computer, at the point where I usually get the coloured lines it instead showed a snapshot of my desktop just before it crashed. Though this happened after I first noticed the coloured lines.
Here's the deal: I've done a fresh F12 install on my T61. Told the installer to Encrypt the Hard Disk. The installation went fine. The kernel was 184.108.40.206. I ran a yum update, which added another kernel - 220.127.116.11, but I can't boot from that one. The newer kernel throws a an "Uncompression error -system halted" immediately.
The new kernel upgrade on Fedora 14 will not boot. lib/modules do not exist is the message. Grub was adjusted to match the old kernel, and the new kernel when booting says lib/modules do not exist. The old kernel has twice as many modules as the new kernel in lib/modules. How do I get the new modules to install so I can boot with the new kernel then? Should I reinstall the new kernel?
I have a tricky problem which I could soIve with a c program. I wrote one and found I didnt have gcc so I tried to install it. I was told I needed to install packages. I acknowledged and an error was generated gcc-4.4.2-7.fc12.i686 requires libgomp = 4.4.2-7.fc12 I try to install libgomp and go round again.
Just got the latest kernel update 18.104.22.168-162 for fedora 12 64bit and it won't boot on my PC. I just get a black screen with some text that doesn't mean anything to me. Computer is a s775 E7200 with nvidia 730i/9300 integrated graphics. I am NOT using hardware graphics drivers at the moment, having decided to stick with Nouveau drivers for a time. What system log tools do I need to identify the problem?
I did a clean install of fedora 13 on my sys, however when i run
rpm -qa |grep fc12
lots of and lots of fc12 packages pop up. below is the list. if there is fc13 version of these packages, and if there is (which I suspect for at least some of them there should be) why my sys doesn't update to those packages?
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'd like to reproduce the way I got to f12 from f11, but obviously to f13 basically I started out on the f11 rawhide repos, then as f12 got released a yum update updated my fedora-release and then hey presto I was automatically upgraded to f12 final release if I now turn on my rawhide repos, as f13 is nearing completion, will I be updated to the latest f13 release (RC3 I believe) and then as f13 gets released my fedora-release will be updated and i will then be upgraded to f13 final as happened before?I don't want to download a whole dvd iso and then upgrade when f13 is final, I'd like to do a gradual transition ie..
f12 -> f13 RC3 via rawhide f13 RC3 -> f13 Final via yum update
I got a new laptop, this is the one: [URL] and decided that I wanted to go with Fedora instead of Ubuntu with this computer. The laptop runs win 7 64 bit so I'm trying to go with Fedora 64 but it will not boot. I first installed Fedora 12 64 bit from the DVD install and it would go to grub fine but when I boot the fedora os It just stops in the middle of the boot script. When it stops, the last 4 lines are:
I hadn't messed with it for a few weeks and yesterday I saw that 13 was out, so I downloaded and burnt the Fedora 13 64 bit CD. I popped it in, booted the computer and it did the same crap. It didn't stop at the same line but it was around a line with: ? kernel_init So I guess the kernel isn't loading properly or something. Do ya'll think I would be better off using the 32 bit?