I do not find any initramfs-2.6.33.5-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.
View 3 RepliesI 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?
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 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?
If you can access Suse Studio here is thlink to the buildLFS Host - SUSE GalleryGoogle hasn't been friendly and neither has a search on these forums, I don't know which man to read so a finger in the right dirrection (preferably not the middle) would be nice as far as that goesRight now the yast live installer trips up at %84 while saving the boot loader configuration and displays a popup that says �An error occurred during initrd creation. /sbin/mkinitrd: illegal optionI then press enter to acknowledge the message and the installation continues without a hitch.
When I go to boot up (no other os installed) grub says it cant find the file initrd-2.6.34.7-0.5-defaultIf you boot the live cd again you can mount the boot partition and you�ll find a broken symlink called initrd that islooking for the missing file above.Like I said above, if it an obvious fix, all I need is some direction, I don't mind reading. (been doing that all day)If you need more specifics Id be happy to supply, I'm just not sure whats relevant and don't want to bloat the post.
Just spent three whole days barking up the wrong tree, solving Fedora 11 and Fedora 12 boot failures because the correct hypothesis was illogical: installation did not update/modify the initrd.
The first couple of times I installed Fedora 11 on the HighPoint Technologies RocketRaid 2640x4, the installation inserted my "custom" driver module (rr26xx) into the initrd, permanently, so that the system booted off the controller card for which the custom driver was inserted. (I yelled about this success in this thread: [url]
My most recent installs of BOTH F11 and F12 on the RocketRaid failed to properly set up the boot. It turns out that the "rr2640" module I "slipstreamed" into the installation process was *NOT* permanently added to the initrd by anaconda. (F12 gave me "no root device found boot has failed, sleeping forever", on boot; F11 hung also, without such error, I presume, during the init script execution). Because of limited resources and time, I only know for sure the module was missing from the F11 initrd, and am ASSUMING the same was the case with F12.
The only difference between the successful installs and the ones with failed boot is that the successful installs were made on a single-drive (JBOD) mode on the controller; whereas, the failed ones were placed on RAID 5. But, AFAIK, the created logical device for the card is "/dev/sda", in both cases, and the kernel can not distinguish between the two cases (or can it?). Thus, the inconsistency cost me a lot of time, and is still inexplicable to me.
Question: What is the best way to deal with custom drivers, today? There are custom spins, and many tools, like isomaster. Stupid question: Is there a way to modify the initrd inside an installer ISO -- be it for CD/DVD/USBboot drive -- beefing the init RAM disk with whatever modules you'd like, for the boot process (using, say, isomaster)?
And what makes anaconda understand that a module must be added to the initrd ? How can one force anaconda to do so?
How does moving to dracut as the initrd tool affect any/all of the above?
I tried compiling linux kernel 2.6.37-rc2 (mainline), Compilation and installation of kernel and modules went fine. After that while trying to make initrd image, I used the following command :-
mohitdhingras@mohitdhingras-laptop:~$ sudo mkinitramfs -o initrd.img-2.6.37-rc2 2.6.37-rc2
It is showing warnings like :-
W: Possible missing firmware /lib/firmware/2.6.37-rc2/radeon/RV610_me.bin for module radeon
W: Possible missing firmware /lib/firmware/2.6.37-rc2/radeon/RV610_pfp.bin for module radeon
W: Possible missing firmware /lib/firmware/2.6.37-rc2/radeon/R600_me.bin for module radeon
W: Possible missing firmware /lib/firmware/2.6.37-rc2/radeon/R600_pfp.bin for module radeon
Actually, "2.6.37-rc2" folder is missing in "firmware".
I'm running FC 13. I believe that the base install is kernel 2.6.33.6-147.x86_64. That is the last version of the kernel that I have installed that includes an initramfs file. Neither 2.6.34.7-56 nor 2.6.34.8-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-2.6.34.8-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 just did a new install of Ubuntu 10.04 (64 bit) on a system with multiple older versions of Ubuntu already installed. There was a dpkg error during the install with no useful information provided, otherwise the install completed normally. When I rebooted, the old grub2 ran and presented my old boot menu. When I mounted the 10.04 partition to see what was there, I found that /boot/grub/ was empty and /boot/initrd.img was missing. The other boot files were present.
View 2 Replies View RelatedI am using grub4dos 0.44 but can't boot directly into Kubuntu. The bootup freezes at the step of reading the initrd. Can't copy 'n paste the exact bootup-message but it looks similar to this one, I found on another forum-thread:
Code:
Filesystem type is fat, partition type 0x06 [Linux-bzImage, setup=0x1400, size=0xcff87] Unlike the guy who posted the two lines above, I installed Kubuntu on an ext3-partition (hd0,5), (which is /dev/sda6 in Ubuntu) and without an own bootloader, since I wanna use grub4dos instead of grub2. The installation is fresh - the initrd-file shouldn't be broken. My menu.lst looks like this:
[Code]..
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.
initrd.lz is a Lzip file in the casper directory of the Ubuntu install iso.
I'm having trouble finding a program that will extract it.
Lzip - fails
file-roller fails
How to extract it?
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 ?
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:
Code:
faust@faust:/# sudo apt-get -u dist-upgrade --install-recommends
Reading package lists... Done
[code].....
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 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.
View 9 Replies View RelatedI 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:
[Code]...
I have installed vmlinuz and initrd.gz (squeeze) in /boot/newinstallation and added to Grub the lines:titleNova Instalaçãoroot(hd0,0)kernel/boot/newinstall/vmlinuzinitrd/newinstall/initrd.gzNevertheless, when I choose this option at the grub, it begins to start the kernel vmlinuz and thus restart the system. The installed Debian Lenny boots in a normal way.
View 10 Replies View Relateduring its installation I faced the same problem as now: because my default sound card is gone and I am using an external one, during the installation, everythnig goes fine untill the first try for boot of the system, when the blue lines loads, loads, and stop on about 80%.I was told by specialist that the reason fot this is that the hardware check is failing and that this is why the system can not load. He disabled my sound card so to Fedora not to check for it (I don't know how) and installed Fedora 13. Now I am using it. And I am using an external sound card as well and I have sound working.
But now I want to instakll Fedora 14. And i tried and the same happened again!!! After installation, the blue bars loads, alods, untill abou t 80% and then stop!Please, tell me what to do! I have no connecion to the specialist now but I want to get Fedora 14 nstalled, and working with sound. This is the problem - that I have only external sound card
I have an asus pc, and its network hardware is not recognized by debian, the drivers are not even in the list provided during the installation process. I managed to download them from another pc, but if i try to make them and install them, i'm stucked because Make is not installed on debian (nor is sudo).So i need a connection to install the drivers that provide me a co0nnections..
View 4 Replies View RelatedI thought I'd have a play with F13 so downloaded the 64bit live cd and away I went. It loaded ok but I ended up with no desktop icons or menus in fact nothing but the background. I right-clicked, created a folder and browsed to the install icon and installed anyway.
As before that went fine but again once logged in I had no desktop other than the background. I opened a terminal and did an update but still no different. I can run apps from the terminal but no desktop at all.
I have just installed Fedora 14 on a machine which already has Windows XP on one hard drive and Ubuntu 10.10 on another. Fedora was supposed to be installed alongside Ubuntu
The installation appeared to be successful in that the process came to a natural end and I was told to reboot. However on rebooting I found that the boot menu did not contain an option to choose Fedora and was the same as it had been before I installed Fedora.
I opted to boot Ubuntu and then opened a terminal and typed 'sudo update-grub' and got a message to the effect that grub.conf was being created. When I rebooted again, there was still no sign of Fedora.
Is there any way of getting Fedora to boot? I am not sufficiently experienced in Linux to try anything else as the computer that I am using is not mine and I don't want to wreck the data of the owner. I did do 'sudo fdisk -l' whilst booted in Ubuntu and I saw that there are Linux partitions on both hard drives but I don't know how to tell which is Ubuntu and which is Fedora
When I am installing it always happen
7:kdegraphics-4.0.3-3.fc9.i386 from fedora has depsolving problems
--> Missing Dependency: kdegraphics-libs = 7:4.0.3-3.fc9 is needed by package 7:kdegraphics-4.0.3-3.fc9.i386 (fedora)
7:kdenetwork-4.0.3-6.fc9.i386 from fedora has depsolving problems
--> Missing Dependency: libkopete_oscar.so.4.0.0 is needed by package 7:kdenetwork-4.0.3-6.fc9.i386 (fedora)
digikam-0.9.3-2.fc9.i386 from fedora has depsolving problems
--> Missing Dependency: libkdcraw.so.2 is needed by package digikam-0.9.3-2.fc9.i386 (fedora)
7:kdegraphics-4.0.3-3.fc9.i386 from fedora has depsolving problems
--> Missing Dependency: libkolourpaint4_lgpl.so.4 is needed by package 7:kdegraphics-4.0.3-3.fc9.i386 (fedora)
kdeedu-4.0.3-3.fc9.i386 from fedora has depsolving problems
--> Missing Dependency: libopenbabel.so.2 is needed by package kdeedu-4.0.3-3.fc9.i386 (fedora) .....
why the Fedora 7 Repository is missing? We run a number of Fedora 7 machines in the office and when I went to configure a local repository sync of Fedora 7, i noticed that [URL] no longer has any Fedora 7 packages? After looking at a few other mirror repositories, it seems this has synced down to the mirrors as well. Would like to know if anyone knows why this is the case and if the packages will be restored?
View 6 Replies View RelatedI have followed the instructions at installsoftware to configure my system for installs from rpmfusion, and I can now use Add/Remove Software to search for and install kmod-nvidia modules. When I attempt to install kmod-nvidia for my current kernel, I get: "Transaction error GPG key retrieval failed... No such file or directory '/etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-fedora-10-i386' (although I do have keys for fedora and livna)
View 3 Replies View RelatedI have just upgraded from F9 to F11. There are a lot of problems I appear to be having with dependencies.
yum update produces the following (the bits before appear ok):
Code:
Processing Dependency: libslapd_db-4.4.so()(64bit) for package: openldap-debuginfo
--> Finished Dependency Resolution
vlc-core-0.9.9-2.fc9.1.x86_64 from installed has depsolving problems
--> Missing Dependency: libass.so.3()(64bit) is needed by package vlc-core-0.9.9-2.fc9.1.x86_64 (installed)
openldap-debuginfo-2.4.10-2.fc9.x86_64 from installed has depsolving problems
--> Missing Dependency: libslapd_db-4.4.so()(64bit) is needed by package openldap-debuginfo-2.4.10-2.fc9.x86_64 (installed)
vlc-0.9.9-2.fc9.1.x86_64 from installed has depsolving problems
--> Missing Dependency: dejavu-fonts is needed by package vlc-0.9.9-2.fc9.1.x86_64 (installed)
devede-3.12c-3.fc9.noarch from installed has depsolving problems
--> Missing Dependency: dejavu-fonts is needed by package devede-3.12c-3.fc9.noarch (installed)
Error: Missing Dependency: libass.so.3()(64bit) is needed by package vlc-core-0.9.9-2.fc9.1.x86_64 (installed)
Error: Missing Dependency: dejavu-fonts is needed by package devede-3.12c-3.fc9.noarch (installed)
Error: Missing Dependency: libslapd_db-4.4.so()(64bit) is needed by package openldap-debuginfo-2.4.10-2.fc9.x86_64 (installed)
Error: Missing Dependency: dejavu-fonts is needed by package vlc-0.9.9-2.fc9.1.x86_64 (installed)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
Windows 7 wont start from the GRUB menu. After selecting the windows 7 entry I added to my '/boot/grub/menu.lst' i get an error saying BOOTMGR is missing. Both windows 7 and fedora 13 were freshly installed just yesterday. Win 7 first on one HD, fedora on another.
Heres some info:
Code:
Ger�t boot. Anfang Ende Bl�cke Id System
/dev/sda1 * 2 26762 15360000 83 Linux
/dev/sda2 26762 35682 5120000 82 Linux Swap / Solaris
/dev/sda3 35682 126504 52131840 83 Linux
[code]....
Windows is installed on my 200 GByte HD, sdc1 - and since Fedora is booting from sda1 and the menu.lst says root (hd0, 0) the windows entry should look like root(hd2,0), no? I tried a couple of different variations of my menu.lst, but i always got this BOOTMGR error. I read that mapping is not needed since vista, is this true? i can only enter the GRUB menu after hitting escape on start up, is there any way how i can have it starting the menu automatically?
I installed an MP3 plugin, and tried to play a podcast on Rhythmbox, and was presented with an error message, which said: Your GStreamer installation is missing a plugin. How can I remedy this?
View 1 Replies View RelatedI installed Fedora 13. While booting I press any key to get the os to boot option. It displays fedora and other. I select other (windows). It says BOOTMGR missing. Press ctrl+alt+del.
View 8 Replies View RelatedI just did a clean install of F15 (32-bit) on a brand new 500 GB hard drive (partitioned and formatted in Win 7 (long 1.5 hr. format, no drive issues). Install was minimal, just Gnome desktop, and I have 894 software updates to do. I've twice started the updates and got two transaction-error dialogs, the first of which I noticed mentioned the Rawhide repository, so I added it to software sources and restarted the update. The second transaction-error dialog lists these files in details
gnome-shell-3.1.4-1.fc16.i686 requires libecal-1.2.so.9
xulrunner-6.0-2.fc15.i686 requires libhunspell-1.2.so.0
gnome-shell-3.1.4-1.fc16.i686 requires libedataserver-1.2.so.14
gnome-shell-3.1.4-1.fc16.i686 requires libebook-1.2.so.11 : gnome-shell-
[Code].....
but in which repository they can be found?