Fedora :: No Initrd With Kernels Newer Than 126.96.36.199-147?
Jun 5, 2011
I'm running FC 13. I believe that the base install is kernel 188.8.131.52-147.x86_64. That is the last version of the kernel that I have installed that includes an initramfs file. Neither 184.108.40.206-56 nor 220.127.116.11-68 installed an initramfs file. Since my root volume is in LVM, I can't boot with those kernels. I saw in another post that doing a "yum install kernel" would install the missing files. I tried that and it tells me that kernel-18.104.22.168-68.fc13.x86_64 is already installed and latest version.
I ultimately want to upgrade to FC 15 because I've got a new nVidia video card and need driver 270.41.06 for fc15. My fear is that if I upgrade I might not get the initramfs files in the new versions of FC and end up with an unusable system. Is there a way to add the initramfs files for the newer kernels and/or will I have the files after an upgrade?
I've always booted Slackware with an initrd until recently. With my new installation of Slack Current (13.37), I didn't bother to create an initrd because of the constantly updating/transient nature of the current branch at the moment.My question is this: when 13.37 does go final in a few days, should I go back to my normal practice of booting with an initrd? Also, I think I understand how the initial ramdisk works, but is it really needed with the more modern kernels?
I can boot xubuntu fine in kernel 22.214.171.124, but nothing newer. When I try to boot in a later kernel, I get a bunch of scrolling text, followed by a text based login prompt that doesn't work.I've been running xubuntu on this computer since version 8.04. I've had this problem since I upgraded to version 10.04. I figured an update would fix it, so I just made do. I figured for sure when the next upgrade came out it would be fixed, but I upgraded to 11.04 and still have the same problem. I figured somebody else would have had this problem by now and posted a solution, but I haven't found one, either on this forum or even on a google search.
It's an old compaq with 236 megs of memory.I just noticed that, while ubuntu used to require at least 256 megs of memory, and xubuntu was for older computers with as few as 192, I believe, xubuntu now requires 256. Is that my problem? Should I be looking at a different distro now?
I've just installed a Slackware64-13.0 test machine with alienBOB's multilib packages. I'm running the stock kernel generic-126.96.36.199 with an initrd set up using mkinitrd.confEverything is fine except that I cannot build a right initrd for kernels 2.6.30, both the /testing one or a custom build: if I try, it will panic at boot with the "couldn't find a valid RAM disk image" error.On the same hardware, without multilib support, I was able to correctly build and boot 2.6.30 initrds.
Are there any official, almost-official or maybe even reasonably stable kernel repositories with new kernels for opensuse 11.2? I recently changed my laptop for a new one which has some issues, which then again are solved in 2.6.33 (and even in 2.6.32 with some tweaking). I would by any means try to avoid kernel recompilation.
What seems like forever ago now I tried to install Linux on this Intel 82855GME chipset laptop I was given. I started off with Fedora because it's what I'm most familiar with, unfortunately the live disk would crash at GDM so I could never get anywhere with it. Even doing a console based install would crash, but it at least pointed me in the right direction, it seemed the kernel was crashing for some reason (see image)Fedora livedisk crashlivedisk-error.jpg (95.96 KiB) Viewed 695 times
I'm running kind of a mix between Wheezy and the occasional package from Sid. I've got the 2.6.32 kernel installed, as well as 2.6.38 and 2.6.39.
With the first kernel (2.6.32), my sound is normal, everything works fine. With the latter two, even using the same driver, my sound is quiet even with the volume up all the way, not to mention that somehow the available volume controls change along with this update. I was wondering if anyone else has experienced something similar, and if they managed to fix it or work around it without just booting into the older kernel?
I have a rather old webcam, a Logitech quickcam messenger. This webcam was working fine with older linux kernel version, I think < 2.6.27. The gspca driver that makes this peripheral working has been merged into kernel sources, and I think that my webcam stopped working with this merge. I am a Slackware user, and until version 12.2 my webcam was working (I manually compiled and installed drivers). If I well remember, with version 13.0 (kernel 2.6.29) the video was full of strange artifacts, and with Slackware 13.1 (kernel 2.6.33) the webcam does not work at all. I am performing these tests with skype, that had videocalls fully working before gspca was merged into the kernel tree, while now I can only make phone calls.
This are the informations given by dmesg:
Code: usb 3-3: new full speed USB device using ohci_hcd and address 6 usb 3-3: New USB device found, idVendor=046d, idProduct=08da usb 3-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 gspca: probing 046d:08da
Is removing previous older kernels "vmlinuz", when updates do get a newer version an easy task, or do the more recent Linux like Ubuntu 9.10 do that automatically, and only keep a few older previous kernels ?
When I compile a custom kernel with this command: make-kpkg --initrd kernel_image kernel_headers and then install the .deb, there's no initrd in /boot and I have to create it manually. I've thought that the --initrd option should take care about this, but somehow it doesn't.
It behaves like this for about two years at least (since I've compiled my first kernel). Of course, it's no big deal to create it manually, I was just wondering whether do I do anything wrong or whether should I fill a bug report..
I do not find any initramfs-188.8.131.52-112.fc13.i686.PAE.img in my /boot folder after I updated Fedora 13 after a fresh installation. The vmlinuz file is present in the /boot folder.he grub.conf file does not show any initrd entry too.
I had to uninstall f10 from my system because it would lock up my system anywhere from 1 to 5 minutes into using it and noone could tell me why.
NOW, I put 9 back on my system and after it updates everything, it locks up again. it does give me the option of the new kernel and the original install's kernel and if I choose the original to boot with, I don't have any problems.
SO, is there any way to fix it, OR to exclude the kernel and initrd from being updated?
I've downloaded 2.6.36-rc8 vanilla kernel, then I copied .config file from my current working kernel 184.108.40.206-168.fc12.x86_64, then I've configured, compiled and installed kernel like this:
Code: make gconfig make -j4 all (or make all) make modules_all make install The last command edits my grub.conf file and writes this: [Code]....
I checked my .config and ACPI, and File Systems are built into kernel and not loaded as modules... And, I have LVM but my /boot partition isn't in it, so I don't HAVE to use initrd, right? How can I boot from a vanilla kernel without initrd ?
For example, if I choose to install Fedora 11, then never upgrade to Fedora 12,13, etc. Will newer packages work on the old Fedora 11, or will I have to constantly upgrade to be able to use newer RPM packages?
I use a BLAG (F12) with a free-kernel 220.127.116.11-libre.168.fc12.x86. I'd like to install a newer kernel (.35). But don't know what is the better way to do this. Is it to download the .35 src.rpm and rebuild the RPM under F12 ? Or should I compile it since the source ?
Oftentimes, I want to restore a directory from a tar.gz backup file.When I extract the backup tar.gz, is there a way to make it only replace newer files in t directory?Currently, I have only been able to achieve this bydeleting the entire target directory and extracting the entire backup file. This is timeonsuming because the backups are sometimes hundreds of gigabytes.
So, I had fun with this one the past week. I had an FC11 system running just fine. Then one day it would not boot - it was hung somewhere inside the init script of the initrd image. CTRL-ALT-DEL would reboot the system. Using grub editor, I could temporarily delete the initrd line and boot into the system OK. But what was going on?
mkinitrd was of no help to me. I even did a yum update, which got a new kernel, which also generated a new initrd - no joy. I extracted the initrd file system and edited the init script. I eventually hit on this tidbit: If I commented out this line:
daemonize --ignore-missing /bin/plymouthd and rebuild the initrd image - the system would finally at least tell me what the problem was: mount failed for selinuxfs on /selinux. No such file or directory.
So, I examine the root (the real root, not the initrd temporary root) - and sure enough, no /selinux. I make one and reboot. The system goes into a "targeted policy relabel" operation, reboots, and I am back in business - even with my original, unmodified, initrd.
I have no idea what happened to my /selinux directory, but I think the initrd "init" script needs to check for this directory's existance, and make it if necessary. Or at least report that it isn't there. In FC11 right now the system just HANGS without this directory being present, without any clue as to what the problem is!
i have a new vServer with Fedora 6.So now i want to update my box. how can i get a full updated server??
i do this stepps: yum install yum-fastestmirror yum update << all installed yum upgrade << no packages to update
is it a good idea to change the respository to a newer version? can I get a secure and good server with Fedora v6? if no, how can I upgrade to a newer version? is my box now updated or is this only a lightupdate of an old fedora version? ps: sorry for the very bad english
Is there a way to use the diff command between an older and a newer version of a file and only display the lines that have been added to the newer file and not the ones that have been removed without any of the explanation formatting, just the new lines. I'm trying to bypass the process of putting both files into a database and running an SQL "left join where old data is null" as I will need to do this on a regular basis.
I have a fairly aged Pentium 4, RAID, desktop computer with Fed 11. I started off with the 686 PAE kernel and update it whenever the update software tells me to. Some time ago I downloaded an NVidia driver which said it needed the 586 kernel so I installed that as well.I then uninstalled the NVidia driver as it caused some minorish problems without any improvement to the graphics. The bottom line is I now have the last three 686 kernels and the last three 586 kernels, which I'm pretty sure I don't need. The machine seems to run fine whichever I use with no discerable differences.My questions are, what is the difference between the two types, which should I actually use and how do I get rid of the other. It would at the very least reduce bandwidth use when updating.
My MythTV system is running under F12. It is in "appliance mode;" all configured and happily doing the PVR thing without a pressing need for upgrades.However, there is a feature in the upcoming 2.6.32 kernel that I'd like to take advantage of; internal support for a certain capture card.
I see 2.6.32 mentioned as part of the F13 release. My question is, will it also be available for F12 . . . maybe sooner than the F13 release?Another way to put this is: How wedded are Fx releases and kernel releases? Is a major kernel goalpost like 2.6.32 the reason why Fx releases are made?
operating system : fedora 15 kernel 18.104.22.168-32.fc15.x86_64 bugs : when updated with the latest update it always log into the fallback, i read somewhere that the nvidia driver version 275.09.07 does not work correctly with gnome shell so i did reinstall it and it fix the log in issue but now it gives me a screen with lots of bad mixed color after returning back from suspend. kernel 22.214.171.124-35.fc15.x86_64
bugs : it gives me this error at boot time "alg: skcipher: Failed to load transform for ecb-aes-aesni: -2" and this message does not save at boot.log anyone have any idea how to fix those issue
I am attempting to run ssmtp from an initrd image to send an e-mail, via Gmail MTA, upon reboot of the machine. I have already successfully installed and configured ssmtp on the running box (in other words, ssmtp successfully runs after completion of the boot cycle). When attempting to mail something via `echo "Test" | ssmtp firstname.lastname@example.org`, I receive the following error message:
I have 3 kernels installed. When I look at my installed kernels with yumex or package kit all I see is the latest kernel. rpm -qa lists them and I was able to remove the oldest using rpm -e.Is this some new feature of YUMEX and package kit to only show the latest version installed?
I'm sure there is a thread on this somewhere, but after looking though the first 100+ search results, I can't seem to find it.
After a kernel update today, I noticed that new kernels are not being added to my grub menu.lst (so consequently, I was running an older kernel).
Any obvious reason why this would happen (kernels being installed normally, with yum update)? I thought the whole process was supposed to be automagic.
Would it have anything to do with the fact that I just kept my F11 menu.lst, and added a F12 kernel to it when I installed F12 (to a separate partition), then eventually (today, finally) removed the f11 kernels from it?
The latest kernel screwed up my laptop and I would like to reload the previous kernel to get back to where I was but I dont see it as available anymore... Is there an archive to pull previous versions from ?