Fedora Installation :: Mkinitrd Can Make Initrd Image With All Hdd Driver - Config To Everytime Update Kernel?
Jul 16, 2009
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?
The RHEL 4 update 7 installation CD installs the kernel with version 2.6.9-78.EL and therefore must contain corresponding vmlinuz and initrd.img. However I would like to have an all modules initrd that is used during installation but for a different version (2.6.9-78.0.13.EL). Is there a way in which I could obtain/make such an initrd?
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'm trying to run extract-ikconfig because I've mistakenly deleted an old kernel config that I'd like to recover. However, when running the script from the latest (2.6.32.5) tree I run into this error:
Quote:
ERROR: Unable to extract kernel configuration information.
This kernel image may not have the config info.
Coincidentally, this happens with all of my kernel images. Is it a fixable problem? I should really set CONFIG_IKCONFIG_PROC next time..
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'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)
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/2.6.33.4-smp kernel modules tree found for kernel "2.6.33.4-smp"
I tried to look into the directory and there was only modules under 2.6.44.3. So I tried to change the command into: Quote: mkinitrd -c -k 2.6.33.4 -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:
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 username@gmail.com`, I receive the following error message:
I support an application that runs on RHEL 5.X and uses multipath to access a SAN. A Bare Metal Restore backup is done using Storix which needs to write directly to a /dev/sd* device, or at least what you configure it to use.The problem is if the USB drive is plugged in when the system is booted it can be identified as /dev/sdb and the the SAN LUNs are /dev/sdc and up. If the configuration file is then set up to use /dev/sdb and then later the system is booted with the USB drive not plugged in the SAN LUNs use /dev/sdb and up, which is fine because multipathd handles that. But when the USB drive is plugged in and becomes say /dev/sdx and the Storix configuration file is not changed, the Storix backup will still use /dev/sdb and corrupt what is there on the SAN.
I assume a udev rule could be used to make the USB drive appear as the same name, maybe /dev/storixI am looking for some good pointers to how to do this with udev or what ever. The application will soon be running on RHEL 6.X also, so hopefully what ever solution someone points me to will still work on it as well
i ran yum update which updated kernel to 2.6.31.9.174.fc12.i686.PAE. Now after logging in i get a blank white screen. With previous kernel updates i have had no such problem. Anyway, the boot messages are following:
Quote:
checking for module nvidia.ko [FAILED] nvidia.ko for kernel 2.6.31.9-174.fc12.i686.PAE was not found [WARNING] The nvidia driver will not be enabled until one is found [WARNING] Driver already disabled
I'm running Fedora 13 x64 and updated the kernel to the latest version (2.6.34.7-56 to 2.6.34.7-61). I use the proprietary nvidia drivers (currently 260.19.12) so I had to compile the kernel module against the new kernel sources and reinstall the driver. The process was apparently successful, but when I try to start X nothing happens, it's as if the computer had been suspended, my monitor acts like it isn't receiving any input. I have full runlevel 3 access, and the system seems pretty much fine up to that point. Nvidia's own sanity tests which are built into the installer reported no problems with my driver.
i just updated my Fedora 14 from Kernel version 2.6.35.11-83 to 2.6.35.11-88 Now the driver for the broadcom wireless ethernet adapter is not detected anymore I installed the driver using
[code]...
The package is still installed but when i but when i use modprobe again the output is "module wl not found" Anybody some ideas? By the way, here is the hardware specification
I have done a new install of Fedora 14 but the RTL8191 wirless card is not being recognised. Realtek have provided the driver source but the make operation is failing because (I think) Fedora 14 isn't provided with the kernel source to enable it to complete successfully.
Basically (in easy to understand steps): how do I download correctly the Kernel source to enable the driver make operation to proceed?
I need to install Ubuntu on approximately 50-60 netbooks. None of them have CD drives, and I don't want to have to install them individually, walking around with a USB stick. I figured the fastest way to install on so many machines is to use a combination of apt-cacher (http://www.debuntu.org/how-to-set-up...ith-apt-cacher) and netbooting. I have successfully booted one machine to test, but as soon as the kernel comes up, support for the network interface is gone. Specifically, the "atl1c" module is not included on the netboot initrd image. Also, I would like to try to use preseeding, and I need to get that onto the initrd as well.
So, to summarize my question: How can I create a custom install kernel and initrd? I have a feeling it's related to the "debian-installer" category in the package repository, but I have not found any good documentation about doing this.
I've downloaded 2.6.36-rc8 vanilla kernel, then I copied .config file from my current working kernel 2.6.32.21-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 ?
I've had a Centos 5.3 zimbra mailserver set up for about 3 months now.Every 7-10 days or so, the system will do a kernel panic and I've been putting off its resolution due to other matters.I'm now ready to look into it but I have two issues :
1) No logs.
So far, I've manually rebooted when a kernel panic occured and could look at the panic printout and write down relevant info. But since I wanted more info than I had written down, I went hunting in the logs for the kernel panic event (one happened earlier today) but, to my surprise, I noticed the system doesn't log the kernel panic at all. Kdump is currently disabled as I'd like to keep all available memory available to the system but I was under the impression it would log the kernel panic message regardless but would simply leave out more advanced diagnostic information.How would I make sure the kernel panic is logged so I can have more info about it ?
2) The actual panic.Here's a snippet of what's appearing when the kernel panics :
I've also seen f793bee4 instead of the highlighted part above but everything else is always the same from the times I've seen (as I haven't always had the chance to be around when a panic occured).I'm looking further into it at this point but early research seem to indicate this could be a memory issue. I'll run memtest next weekend to check that out (since I don't want to take the system offline for any length of time during office hours) but people here might have other theories based on what I've put up so far. The system has all of the latest patches and updates and is running only what I need as far as software goes (zimbra server + prerequisites, x + GNOME (not loaded on startup), firefox and vnc for windows RDP access). My system also uses a software RAID1 array (boot = md0 and / = md2 with swap files not being mirrored as there's no need to).
PS : In order to further troublehsoot by myself before posting here, I've tried to enable kdump to see if kdump is the culprit for the missing logs but I'm also having an issue with it. I'm getting a "No kdump initial ramdisk found" and "mkdumprd: failed to make kdump initrd" messages at startup. I'm thinking this might be because of my raid array ? I've found an old bug report regarding one of those error messages on centos 5.2 but it was supposedly fixed in the 30 version by RH and I'm using the latest one (56).
When configuring a custom kernel using fedoraproject.org instructions, the make menuconfig options for LIRC are not in the .config file anywhere. I checked the kernel tree and all the files are there in the .../drivers/input/lirc subdirectory (I need the lirc_dev and lirc_i2c drivers). I reset the .config to its original settings to make sure I didn't mess up. I also grep'ed the .config file for any LIRC related settings, none found. Also I'm not getting any sound from the radio-aztech driver.
I seem unable to get an nvidia driver working properly after upgrading to the latest kernel with Fedora 11.Here is my laptop and its specs: http://h10025.www1.hp.com/ewfrf/wc/d...reg_R1002_USEN[URL]I've tried both the kmod and akmod unsuccessfully. Everytime it gives me a black screen on boot, I can fix the problem by popping in the LiveCD, and changing the xorg.conf file back to the backup.Here are the errors/warnings from my boot.log file:
Code: WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. Checking for module nvidia.ko: [60G[[0;31mFAILED[0;39m]
I recently upgraded from fc8. I am running two nvidia NVS 285 cards with four monitors and using nvidia driver 190.53-pkg1. I have one card up and running and can edit the config file and make to other two work I just can't get all four to work together.
System: Ubuntu 10.10 i386 CDI followed the instructions at But I cannot upgrade the livecd using:# apt-get update# apt-get dist-upgrade --install-recommendsit was not possible with aptitude as wellhere's the output of the commands that I issued at the chrooted filesystem:
I am currently running Fedora 10 XFCE on an Acer Aspire 1 (1.6ghz atom, 1.5gb ram, 8gb ssd). I am trying to install Fedora-11-i686-Live-XFCE via USB stick (Kingston 4gb) and am having no luck. I downloaded the .iso via bittorrent. If I use liveusb-creator: .iso passes checksum, installs boot image, installs syslinux, claims it's complete. When I try to boot, or simulate booting with qemu, I get the message "Could not find kernel image: linux" If I use
it says that the .iso passes checksum, installs live image, updates boot config file, and setup USB stick as a live image. Once again though, when I try to boot, or simulate booting with qemu, I get the same message "Could not find kernel image: linux"
I just removed a proprietary (fglrx ) driver which didnt work out well.Now all my updates hanging on: Setting up initramfs-tools (0.98.1ubuntu6) ...update-initramfs: deferring update (trigger activated)Setting up linux-image-2.6.36-020636-generic (2.6.36-020636.201010210905) ...Running depmod.update-initramfs: Generating /boot/initrd.img-2.6.36-020636-genericAnd I dont know how to solve it...besides a clean install.
I'm new to fedora and when I boot from a cd I get the message: could not find kernel image. I currently have windows xp and my motherboard is and ix38 quad gt if that helps.
I want a new kernel RPM in my custom CentOS 5 kickstart distro. I built the kernel, got a nice kernel RPM out, and replaced it in my ks.cfg. The install goes fine until the very end, where Anaconda prints some spurious stuff about mkinitrd failing.I get why it might fail -the kernel version argument to mkinitrd was no doubt for the old kernel. But I have no idea where this is -it's not in the ks.cfg afaict, and so I don't quite get where Anaconda / mkinitrd gets it from.
I'd eventually like to use this kernel for the installer as well, but I think I understand that process much better.How do I tell kickstart / Anaconda / mkinitrd to use the new kernel version number?
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.
i am using linux for couple of years. suddenly i a question arises in my mind. Before loading kernel during booting linux box initrd image loads necessary real mount point, file system, modules etc. but how initrd loads them ?? is there predefined modules list stored in initrd image or something else....what is the background procedure of it
i am using rhel5 and i just wanted to see the contents of the initrd image. I have copied that from /boot/grub and saved in /tmp directory. Then i did the following
when i gave that, it says "mount: you must specify the filesystem type" Then i included "-t ext2" option in the mount command. Now it says,
mount: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so
Then i created a ext2 filesystem and did the same thing. But there is no difference.
