Fedora Installation :: Exclude The Kernel And Initrd From Being Updated?
Jan 21, 2009
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 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?
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 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 ?
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 recently updated the kernel of lucid from 2.6.32-22 to the ""-23 release through update manager. Now whenever i try to boot the new kernel from GRUB the screen goes black and the computer stops responding with the caps lock and scroll lock lights flashing on the keyboard.
I can still boot into ""-22 fine and keep using ubuntu.
My first thought that the problem was the newer kernel itself so I tried to update to 2.6.33-5 from [url]but the same boot problem exists within this one also.
Because it goes straight into the black screen after GRUB I have no way of telling what has happened without error messages. Would this appear in any log files and if so which ones?
I recently upgraded Linux kernel headers for version 2.6.35 on x86/x86_64 from 2.6.35-22 to 2.6.35-23. and my system will not reboot to the upgraded kernel. To reboot I have to force shutdown my Toshiba L-450 laptop and the restart. This brings me to the GRUB screen were I can choose to use the previous 2.6.35-22. Normally do not see the GRUB screen as I am only running Ubuntu 10.10 64 bit on this computer. I have tried reinstalling linux-headers-2.6.35-23 and linux-headers-2.6.35-23-generic and got the same result.
So I have been using Ubuntu for the past couple of months using Wubi, mainly because my parent's are afraid that I'll screw something up on the computer if I partition the hard drive and stuff like that. And Today I installed the latest updates for 9.10, asked me to restart the computer, and now whenever I try to boot using the latest kernel GRUB keeps telling me to "Load kernel first". The funny thing is that I can boot with the older kernel fine, But I would really like to get the lates updates, which I can't using the older kernel.
I've been having trouble getting the latest kernel to update, due to an error resolving dependencies. I've used yumex to remove old versions of kmod-nvidia that were fc10 specific, and gotten past that. However, when I updated the kernel, yumex reported that mkinetrd failed. Checking, the newest kernel listed in grub.conf is the one I'm using, not the one I just installed. What do I need to do to get the updated kernel properly listed and ready to use?
In an attempt to ameliorate some other problems (lm_sensors, and loopback), and based on several forum entries, I decided to update the default f15 kernel (2.6.38.35) using kernel-2.6.39-1.fc16.x86_64.rpm from rawhide. It seemed to install without problems and when I rebooted it seemed to hang just before completing the boot process. The on screen boot messages ended with:
Started Display Manager Started LSB: daemon for libvirt ........ Starting LSB: suspend/resume libvirt guests on shutdown/boot [ 12 ...... about a dozen similar lines ending with [25.030991 hci_cmd_timer: hci0 command tx timeout then it apparently hangs
However, at that point I can log into to a console using Cntl-Alt-f2, so most, if not all, the crucial boot processes seem to have completed. There is an issue with the nVidia driver that I will deal with by modifying /boot/grub/grub.conf to re-enable nouveau, but I am stumped by what is causing the hang up. There is a certain amount of traffic regarding a similar problem with Ubuntu 11.04, but no solution other than it seems to be related to a BIOS bug (NFI)
what sub-system uses the "hci_cmd_timer" and why it might interfere with the boot process? Has anyone else run into a similar problem with f15?
Is there a better way to get an updated kernel in f15? I do want to keep all the Red Hat patches and back ports, so reluctant to build a kernel from scratch from upstream sources at kernel.org (and maybe just a bit apprehensive ;-})
I think I know quite well what my problem is. However, I'm still too much of a newbie to know how to solve it.My problem: I no longer get a login screen on my server after I ran a yum update which updated my kernel (thank god, vnc server still works).Cause: During startup Fedora complains that it can't load the module nvidia.ko. Reason: The module doesn't match the current kernel.
I upgraded to Fedora 12 right after release, everything was working fine until update on previous weekend. Looks like it updated Wacom drivers and kernel. Now what I have. I hotplug my tablet in USB, and everything seems fine, I can position a cursor and press buttons, but after I press some button it hangs (LEDs on tablet are responding) I must remove Stylus from proximity in order to make it respond again (while stylus is away LED on tablet switches off for a fraction of second).
If I move mouse during tablet hanging, applications barely respond and if they are it is like mouse button is pressed (selecting text). I tried wacdump, and it's reporting everything's fine (X,Y, Tilt, Pressure everything shows up). I couldn't find evidence that wacom driver is controlling it, but I assume if wacdump is reporting then it is. I have: Kernel 2.6.31.6-145.fc12.x86_64 linuxwacom.x86_64 0.8.2.2-15.fc12
I didn't touch xorg.conf in sense of tablet, but it worked for me in F11 and until now. I'm trying to make least manual configurations possible. Through exploring /proc/bus/usb/devices and kernel messages I confirmed that wacom drives is handling the tablet. And I noticed that in X's log
(II) config/hal: Adding input device Wacom Intuos3 9x12 (**) Wacom Intuos3 9x12: always reports core events (**) Wacom Intuos3 9x12 device is /dev/input/event8 (**) Wacom Intuos3 9x12 (Wacom Intuos3 9x12) is not a pad (**) Wacom Intuos3 9x12 is in absolute mode (**) WACOM: suppress value is 2 (**) Wacom Intuos3 9x12: reading USB link (**) Wacom Intuos3 9x12: threshold = 61 (**) Wacom Intuos3 9x12: max x = 60960 (**) Wacom Intuos3 9x12: max y = 45720 (**) Wacom Intuos3 9x12: max z = 1023 (**) Option "BaudRate" "9600" (**) Wacom Intuos3 9x12: serial speed 9600 (II) XINPUT: Adding extended input device "Wacom Intuos3 9x12" (type: Wacom Stylus) (EE) Wacom Intuos3 9x12: Top/Bottom area overlaps with another devices. (EE) Couldn't init device "Wacom Intuos3 9x12" (II) UnloadModule: "wacom" (EE) config/hal: NewInputDeviceRequest failed (1)
I've encountered quite similar error in openSUSE when was configuring tablet manually in xorg.conf. As I can see problem is with "pad" device, which I disabled in openSUSE in order to make X running. So why is it not working?
Do you have to reinstall Nvidea and Broadcom drivers every time the kernel is updated? The new kernel would not even load to where I could get to my desktop. Help?? I could not even sign in with older kernels. Had to use a Puppy CD to edit my Grub menu.lst so I could sign in on the older kernel.
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.
Yesterday fedora automatically updated the linux kernel, and now it wont start entirely up. After the fedora logo has finished loading up the white, and it has turned into the real logo, nothing happens.However, i can boot into fedora with the old kernel via grub, so i guess it is related to the kernel update.
Sorry if this is the wrong place to inquire. I was wondering if it is possible to install fedora without any remote administration tools in particular SSH?
i upgraded from 11.1 to 11.2. Unfortunately the new kernel does not work with my sata/southbridge (i googled and figured its a known issue). So i tried to boot a 11.1 64bit rescue system to install the older kernel and the corresponding initrd. The problem is, that i cant find the kernel and initrd on the rescue system.
I've changed for huge kernel to a generic+initrd setup per the instructions in the README.initrd file however my machine fails to boot using that method. I get the following errors: /boot/initrd.gz: Loading kernel modules from initrd image: mount: mouting /dev/sda2 on /mnt failed: No such device ERROR: No /sbin/init found on rootdev (or not mounted)
1. I've created the initrd using the results from /usr/share/mkinitrd/mkinitrd_command_generator.sh mkinitrd -c -k 2.6.33.1 -f ext4 -r /dev/sda2 -m usbhid:ehci-hcd:ext4 -o /boot/initrd.gz 2. my root fs is ext4 on /dev/sda2 3. I've changed all necessary links in /boot 4. I've changed my /etc/lilo to: image = /boot/vmlinuz initrd = /boot/initrd.gz root = /dev/sda2 label = Linux-Generic read-only
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..
So I'm building a custom kernel cuz I want the fbcondecor patch in my kernel. I use the same .config that 2.6.32 debian kernel package comes with. This kernel runs perfectly. I pass --initrd to make-kpkg when building the package but no initrd is built when I install it so I have to make it using "mkinitramfs -o /boot/initrd.img-2.6.33 2.6.33" to get it to boot. Now when I try to build the nvidia drivers it complains it can't find the source. I did build kernel_headers and installed them also the source is in /usr/src/linux. I also tried to specify the path by passing --kernel-source-path= to the nvidia script but no change. What is going on? I've done this fifty times before and never had any problems. Has there been some changes to how debian kernel packages are built? EDIT: Just thought I'd add some info about the steps I took.
Code: tar xjvf linux-2.6.33.tar.bz2 ln -s linux-2.6.33 linux cd linux patch -p1 < ../fbcondecor-0.9.6-2.6.33-rc7.patch cp /boot/config-2.6.32-trunk-686 ./.config
make menuconfig Loaded .config then I removed support for maxtorfb, tile blitting and some sirrusfb thing, nothing thats relevant to my system. Changed cpu from Pentium 4 to Core 2 and added framebuffer decor support from my patch, exited and saved. Then:
[Code]....
EDIT2: I have now tried to build 2.6.32.8 in the same way with the same strange results, anyone have any thoughts as to what I'm doing wrong just throw it at me, I'm getting desperate and running out of ideas. I've checked all the kernel source symlinks and everything looks good.
i have created on folder in my server to upload some regular states. I want that user can modify or upload already stored files. but, should not upload any unwanted files orfolders.for that i want to use "rm" command as auto scheduler (putting this in cron tab.so that all files will be removed except some required files / folders for which this upload facility is activated. users are using secure-shell for uploading data.
I set up my home server like 3 year ago on a Fedora core 4, I am running a NAT, firewall and FTP very smoothly on it. In the past 3 years, it has been doing perfectly without any modification/ upgrade. But recently, I just realized I might need a VPN server on it, but the recent release of OpenVPN doesn't support Fedora core 4 anymore, therefore I suddenly want to make an upgrade. I've read the articles/ manual for Fedora 13, yet I do not find any suggestion on how to upgrade to 13 from core 4.
how can I do an upgrade in the easiest manner as I don't want the server cease working too long (I need its NAT for my network).
I installed VirtualBox (and the virtualbox repo) a few months ago and it works brilliantly. The other day it informed me there was an update available. I downloaded: VirtualBox-3.1-3.1.2_56127_fedora11-1.x86_64.rpm from [URL]
Why doesn't yum update find these new versions of VirtualBox? Is the original repo file out of date? Here it is:
