Fedora Installation :: New Kernel Will Not Boot (Modules)
Mar 26, 2011
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 am trying to setup Slacware 13.1 x86_64 to a encrypted partition. I used the README_CRYPT.TXT howto : [URL] At the step when I create an initrd.gz I get this error: Quote: ERROR: No /lib/modules/22.214.171.124-smp kernel modules tree found for kernel "126.96.36.199-smp"
I tried to look into the directory and there was only modules under 188.8.131.52. So I tried to change the command into: Quote: mkinitrd -c -k 184.108.40.206 -m ext3 -f ext3 -r cryptroot -C /dev/sda2
This command was successful, but I don't know if this is alright. I made the changes in lilo.conf, add initrd = initrd.gz. This is all on unencrypted /boot partition. The boot=/dev/sda1 I also set for the unencrypted boot partition. When I boot the system I get a kernel panic:
How do I get modules in the Kernel to load automatically at boottime? I''m specifically trying to get i810fb to load during the boot process. In Ubuntu, I just had to edit a file and update my initramfs. How do I do this in Fedora?
I was trying to install VirtualBox through the YaST > Software Management but it is not working, someone in the forum told me that I have to download the OSE version and do it manual way. Finally I am able to start up VB but not able to use the network connection. Thus I am trying to do this:
/etc/init.d/vboxdrv setup. I get this error:
When I type dmesg, it shows me a bunch of info which I don't know what should look for. When I type modprobe vboxnetflt, I get the error: FATAL: Error inserting vboxnetflt (/lib/modules/220.127.116.11-1.2-default/updates/vboxnetflt.ko): Invalid module format. what should I do in order to get my VB to be able to connect to the internet?
Tonight I installed ubuntu 10.10 (32 bit) on an external usb harddrive with a dvd I burned and I used my older desktop. I disconnected all internal and external drives first so everything had to be put on the usb drive I selected (only option available). I used the option to load extra software, use the entire hard drive, and let the software do it's thing. I basically had no options where to put things and it didn't have much choice.
When I boot the usb drive on my laptop (win 7 64 bit) by telling the bios to boot to it first... I get an error: modprobe: FATAL Could not load /lib/modules 2.6.35-22 generic modules No such file or directory. This message appears twice and then it does boot into ubuntu and seems to work fine. I'm new to this OS so that is an uneducated guess but the things I have done seem to be working. So exactly what is this error referring too? Is there a way to fix the problem or do I just ignore it.
I was wondering how can I determine among the modules loaded at boot which of them are really necessary and which are not, in order to reduce the boot process time and have a more "elegant" system start.
I know this theme is a little bit of complicated because it depends of the user's point of view and demand a high knowledge of which things are happening in your system but I need somewhere to start improving the performance of my debian system.
I'm trying to install Sun VirtualBox Additions into Fedora 12 which is installed in VirtualBox running on top of Windows 7. As the Fedora install was originally a live distro which was then installed to the HD, it may be missing some essential files for compiling.
My attempt to install the VBoxLinux additions is incomplete and I can't get the full range of video displays. The largest is This is the error message: "Your system does not seem to be set up to build kernel modules".
Should I update Fedora to install all the updates available? I did find one webpage which gave an accurate list of files to install for this purpose but can't find it now.
I am attempting to compile the linux-18.104.22.168 kernel from kernel.org to use with an installation of Fedora 14 (22.214.171.124-83.fc14.x86_64). I've done this before with different kernel versions for older versions of Fedora, but I've encountered a new problem this time. Whenever I get to the "make install" step, I get the following:Quote:
sh /home/user/testing/source/linux-126.96.36.199/arch/x86/boot/install.sh 188.8.131.52 arch/x86/boot/bzImage System.map "/boot"
I want to remotely install OpenSUSE on one of my servers. I followed the instructions given at SDB:Remote installation - openSUSE, but it didn't work. (My server reverted back to the already installed system.) I think this has to do with a special kernel module (megaraid_sas) that is necessary for the raid controller. Without this module, the kernel cannot find any disk. Of course, the module is not included in the initrd provided by OpenSUSE. I know how to add files to the initrd, but I have no idea where I have to put the required kernel module and which config file inside the initrd must be modified to make the kernel load the module.
The other day I installed VMware Player on the system when the Kernel was 184.108.40.206-32.fc15.x86_64. On running VMware player after installing the kernel-headers and gcc files the program ran fine (I did not try to install the VMware Tools). I also have not loaded the guess OS as yet.
toady I did and update in which the kernel was updated. I checked to ensure the Kernel-headers were also updated for the latest kernel.
After rebooting the machine the running kernel was then 2.6.40-4.fc15.x86_64. I then tried to start VMware Player. It indicated because the kernel was changed it needed to install new kernel modules, OK, It open the module screen and then crashed.
The log says it can not compile Vmmon which is the first module. it does not go any further.
Tried to installed a new copy of VMware Player over the old one but this only resulted in the same error messages.
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.
I have noticed in the recent updates there is a Kernel update 2.6.32-22 but there is no restricted modules included. On my Desktop I have a Nvidia card which I installed the driver using the Hardware Drivers Application. As far as I know these Drivers are ether reinstalled or updated whenever there is a kernel update.
I also have a Laptop with a ATI Radeon card which I did run the updates and ended up (after the reboot) in low graphics mode, after a bit of work I was able to reinstall the drivers and get my desktop back so that's ok now.
I had this problem a few years ago with an old version of Ubuntu, kernel updates but no restricted drivers. The drivers turned up the next day and all was fine. I was just wandering if this is a known issue with Lucid or if anyone else has had this problem, It's been a couple of days since I noticed the Kernel update but still Restricted Modules. Oh I'm using Ubuntu Lucid 10.04
I opted to install my Linux Fedora distribution, in a SUN VM (Virtualbox). [URL] I have 2 questions:
My current max res available to select is 1024x768. Can I run at 1920x1200? My display indicated that it is 'Unknown'. I don't know if that is in on the deal, or not...
Second question: When installing VBOXADDITIONS_3.1.2_56127, I am getting the error: Building the VirtualBox Guest Additions kernel modules [FAILED]
If I am displaying the log correctly, it indicates: Makefile:23: *** Error: unable to find the sources of your current Linux kernel. Specify KERN_DIR=<directory> and run Make again.. Stop Pictures are located here, in the EVGA Linux forum: [URL] I am new to both Linux, and Fedora.
My mission statement: To run Linux using the Fedora distribution, in a VM window under Windows 7 64bit Ultimate, with the ability for scripting using Bash, with the Perl programming language installed, and use Apache Tomcat to monitor both apps, and various VM installs, on numerous Servers via the internet.
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 220.127.116.11. I ran a yum update, which added another kernel - 18.104.22.168, but I can't boot from that one. The newer kernel throws a an "Uncompression error -system halted" immediately.
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
Code: 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'm trying to install the 32bit 10.04 server to an atom machine from a CD burned with ubuntu-10.04-server-i386.iso. The installer is presenting me with the:"No kernel modules were found" ..error message. Is the atom cpu and chipsets supported by the 32bit server installer?
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 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?
For a diskfull node (the OS installed in a disk), I can use the 'insmod' command to insert a kernel module into the kernel. And after the reboot, the module is still in the kernel. I have a question here: how, when and which kernel module will be loaded in the boot up process for a diskfull node?And for the diskless node, can I use the chroot or some other ways to install the kernel modules into ramdisk, so that kernel module can work when the diskless node boot up? I think it needs certain mechanism to load the kernel like the boot up of diskfull node.
I am trying to install Fedora on my computer but I am getting a kernel panic at liveCD boot after boot menu. It occurs to me for F13 and F14 (all x64, F14 x86 seems to boot fine but I'm trying to host a x64 guest OS on it so I need to get the x64 version to work)
My system specs: Dual Opteron 265 4GB RAM Asus K8N-DL (nVidia nForce Pro 2000, BIOS 1010)
I also tried to install F14 in some other computer (which worked flawlessly) and put the HDD into the computer in question, which gave me the same kernel panic.
I installed F11 x86 from the DVD onto one of my machines using a total of 4 partitions:
1. /boot 2. / 3. /home 4. swap
I then created an image of the first 3 partitions with fsarchiver and restored it onto a second machine (with different hardware). Grub was loaded onto the second machine as well without a problem. The new cloned install will get past grub fine but the kernel hangs. After removing 'rhgb quiet' from the boot options, I can see that the last message outputted to the console is something about the PS/2 mouse - this doesn't make sense as the mouse is working perfectly fine.
Additionally, I can still reboot using ctrl-alt-delete so the kernel/CPU must still be responsive. I have tried troubleshooting the various pieces of hardware, so I'm guessing it's something with the clone. All the cloned filesystems appear to be fully intact; the partition UUID's are all the same. I've even tried changing the UUID's both in grub and /etc/fstab to hardcoded /dev/sdaX , but this does not fix anything.
basically put a new hard drive in my old computer and wanted to install fedora on it, downloaded fedora 12 dvd iso (3ish gb in size) have burnt it to a dvd disc, turned my laptop on and set it to boot from cd drive, restarted it, it reads the disc and displays the following message:
ISOLINUX 3.75 209-04-16 ETCD Copyright (C) 1994-2009 H.Peter Anvin et al Could not find kernel image: Linux boot:_
The uderscore is flashing and i can type stuff in but have no idea what to type in to find the kernel image, or why it cant find the kernel image.
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-22.214.171.124-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 have just compiled a new kernel. When I boot into this new kernel and do an lsmod it is only running two modules. The only thing I changed in the configuration file was to compile ext4 file system into the kernel. My computer is an HP Pavilion dv4. The two modules are lirc_ene0100 and lirc_dev. I am running Ubuntu 10.04. The new kernel is 126.96.36.199+drm33.5. The kernel seems to work fine but I need to know why and how it can only be running two modules.