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?
View 3 RepliesI'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)
View 2 Replies View RelatedI 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 using this guide videos - howto: debian linux kernel compilation, part 1 and the author says i need kernel 2.6.26 this version of kernel doesnt longer exist in kernel.org website and the only 2.6.26 i found is a patch here. should i use the patch? or download another version of kernel?
View 2 Replies View RelatedWhat is the kernel version required for installing NFS4 (RHEL) ??
View 1 Replies View RelatedI'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 :
EIP c0467136 page_remove_rmap+0x66/0xc0 SS:ESP 0068:c3ca6ddc <0> Kernel panic - not syncing: Fatal Exception
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).
I get the following error message trying to install dazuko on xubuntu 10.04: "headers for target kernel version could not be found" But when I run sudo apt-get install linux-headers-$(uname -r), I get the message that I already installed the headers. My current kernel is 2.6.34-020634-generic
How can I install dazuko withouth having this problem??
At the moment I am using kernel 2.6.31-14-generic. I'm not one of those people who needs to have the latest and greatest kernel to be happy, I just rely on the update manager. I swore that I saw an update for a new kernel, but my kernel version hasn't changed. I'm just curious if there was a new kernel that was released or if that was just an update to the kernel listed above.
View 2 Replies View RelatedI am trying to set up autofs in RHEL 5 and every time I run the "automount" command, I receive this message: "automount: test mount forbidden or incorrect kernel protocol version, kernel protocol version 5.00 or above required."
View 1 Replies View Relatedi 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.
View 2 Replies View RelatedI'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
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 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 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.
Suddenly, after installing, boot was failed.
[Code]...
i was surprise, because in initrd-2.6.34.7-0.2-default all was ok.
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.
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..
We all know linux kernel base layer is made up of structures, in which every object of kernel is well defined. Structure members correspond to object properties required to define object behavior.
For example if we take case of File system.It composed of four objects , superblock objects, inode objects, file objects and dentry object.Each having well defined structure which is being operated by system call handler and by system call service routine in the kernel mode.
Now my question is even in kernel mode we do not have some mechanism by which we can get access to pointer of these structures.We have some macro.
If I want to manipulate structure on my on way, or performing some more operation defined by me.For example after the crash of Hard Disk Drive, having ext2/3 file system, If i want to know all the inode pointers, and block details.
Can I have some way out to do desired operation ??
mechanism to operate on these base label structures, even in kernel mode ..
What happens if you get an update for an older version kernel when you are using a new version?
View 3 Replies View RelatedSometimes a kernel image seems to have the same version as the backported kernel image, for example:
linux-image-2.6.32-bpo.5-amd64
linux-image-2.6.32-5-amd64
What are the differences between the two?
I have a server running Reh Hat Linux 7.3 with kernel 2.4.18. Can i upgrade kernel to version 2.6 and glibc to version 2.5?
View 6 Replies View RelatedI am trying to figure out how to load the generic kernel in Grub2.
I have run the /usr/hare/mkinitrd/mkinitrd_command_generator.sh and ran the output:
Code:
Why this will not load.
Was upgrading to the newest kernel in RHEL5 from 2.6.18-164 to 2.6.18-164.10.1 but when I rebooted the machine it gave me these errors.
Unable to access resume device(/dev/VolGroup00/LogVol01)
mount: could not find filesystem /dev/root
setuproot: moving /dev failed: no such file or directory
setuproot: error mounting /proc no such file or directory
setuproot: error mounting /sys no such file or directory
switchroot: mount failed: no such file or directory
kenel panic - not syncing Attempted to kill init!
So I rebooted the machine and picked the old kernel to boot up (2.6.18-164) and everything came back up fine. I don't understand why it keeps failing when trying to boot to the new kernel. I am using the yum upgrade command, is there a different command I should be using?
My RHEL 6 computer at work cannot have access to the internet. Is there any way I can upgrade my kernel without internet access? I do ofcourse of another PC with internet access and a USB flash drive.
View 2 Replies View RelatedWe bought a board with vortex 86x processor. we tried to install RHEL6 beta version. when we select the installation choice we were getting below error: "This kernel requires an i586 cpu, but only detected an i486 cpu. Unable to boot please use a kernel appropritate for your cpu."
We have contacted the board personal. he said(in his words)"If you need to use redhat, you have to use the config & patch file provided in the development note to develop a kernel which is suitable for redhat."
Where can I find the documentation for RHEL 5.4 kernel 2.6.18?
View 1 Replies View RelatedI am in verse to compile a new kernel 2.6.34-rc5 on RHEL 6 Beta.I have been following [URL] for the same. how can i select all the options during :
Code:
make menuconfig/make gconf/make xconfig
I just saved it under .config and when I ran : make modules it threw errro saying "modules not included". So i want to select complete options during make xconfig.
how to upgrade or install a updated kernel version (3.0).I am using RHEL 5 with kernel 2.6.18-8.I am trying to upgrade through source downloaded at [URL.Also will it be a good practice to upgrade the existing kernel?
View 3 Replies View Relatedwe are facing the problem related to Kernel panic in linux . Could u send me details of kernel panic . Why the kernel panic occur and how to resolve this problen
View 2 Replies View RelatedMy application team is asking me to generate the kernel-dump.
Here are details about my server.
OS: RHEL 4.7/32 Bit
Kernel Version: 2.6.9-89.0.23.ELsmp
Processor: Intel(R) Xeon(R) CPU E5520@ 2.27GHz
Hardware: HP Proliant 380G6 series server.
I am using Electric Cloud applications. Sometimes it creates some kernel panic and immediately got rebooted. Kernel-debuginfo rpm is not installed. In some thread, I read the kernel-debuginfo rpm's version should match with the kernel version. In my case I couldn't even find the exact version of kernel-debuginfo version.