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)
View 2 Replies
A FC10 server hung and had to be power-cycled. I suspect it hung because of an nfs mount timeout.
Now it does not boot. The error is libc.so.6 not found. Kernel panic. Attempting to kill init.
Booting under rescue:
ls: cannot access libc-2.8.so: Stale NFS file handle
Is there a way to reboot to a clean state? There must be some NFS cache file.
I also tried to cp rescueCD:/lib64/libc-2.8.so to the old lib64 dir, but get the same "Stale NFS file handle" message.
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 Replies View RelatedI 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 am getting a problem when login into FC10. It boots correctly an shows the login screen; then, when typing my user and passwd goes to the desktop and shows a KERNEL FAILURE. At this moment, most of the times the PC is blocked and doesnt works any more. One time has continued working without problems.
After the las failure, my system log has this info:
Code:
I have checked my hard disks (fsck) y every thing looks fine. However, i dont know how to fsck the VolGroup0. I cant'get it unmounted.
Code:
Just installed FC10 and noticed no sound with latest kernel (2.6.27.15-170.2.24), however I do have sound with kernel 2.6.27.5-117. No other differences. Anybody else have this problem?
View 10 Replies View RelatedI just tried to update to kernel 2.6.27.15-170.2.24.fc10 (x86_64) at the suggestion of the gnome update widget, and the process hung. A bunch of other things were updating at the same time, many of which were related to audacity or wine.
I'm not sure just what was being updated, because the option to review which updates are available does not work - when I click on it, nothing happens, but when I take the other choice (install all updates), I take pot luck. It would be nice to be able to choose which programs to update, and to be able to upgrade the kernel independently, but I don't seem to be able to do that at the moment.
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 want to compile the vanilla kernel 2.6.37-rc3, but i want to obtain a .rpm file. I found this guide long time ago (i used it many times) but it use src.rpm package and the contained kernel.spec file have many lines for adding patches. Someone know where can i download a kernel.spec for vanilla kernel or a guide to obtain an rpm file
View 4 Replies View RelatedThe latest update changed the default boot from 0 to 1 and added extra parameters to the new kernel boot line.
default=1
timeout=8
splashimage=(hd0,7)/boot/grub/splash.xpm.gz
# hiddenmenu
title Fedora (2.6.31.6-145.fc12.x86_64)
root (hd0,7)
[Code]...
I have just updated my kernel and immediately struck trouble. The kernel update is marked as security update.
When booting I get a multiple warnings " deprecated config file /etc/modprobe...", then "no root device found" followed by "boot has failed, sleeping forever"!Clearly something is amiss with this update, so figured the best thing might be to remove it and wait on a fix, but attempting to remove the kernel via the package manager would cause a whole lot of other packages to be removed as well.Instead, I edited grub.conf, commenting out all the kernel-2.6.34.7-63 lines, so that the default is now the previous kernel (2.6.34.7-61).
I tried to update my f12 today. In the list it showed an update for kernel-2.6.31.6-145.fc12.x86_64 It all seemed to go OK but when I restated my computer it spit up an error and wouldn't boot"Could not load /lib/modules/2.6.31.6-145.f12.x86_64/modules.dep: No such file or directory"Luckily the old kernel still works.
I do have the disk encryption set, could this be related to that? Updated my laptop today with the xx.6-145.f12.PAE kernel and now it's borked to. Same problems.12/07/2009OK today's kernel update seemedto fix the problems and now all is well, execpt for my inkscape not working problem. But I put ubuntu 9.10 in a VBox and it works. So for now that's my work around.
I have an issue with kernel-2.6.31.9-174.fc12.x86_64. I ran the updates on Christmas Eve and it updated from kernel-2.6.31.6-166.fc12.x86_64 to kernel-2.6.31.9-174.fc12.x86_64. When I rebooted, I no longer received the Fedora Bubble boot screen. It comes up with the Fedora boot bar (across the bottom). Also, I receive failures during boot with the following:
[Code]...
I just responded to a (packagekit?) prompt to update packages, which included new kernel 2.6.35.12-88.fc14.x86_64. I use nVidia on my notebook and usually the new driver is installed automatically. This time, the computer would not boot to the stage that the nVidia logo appears, indicating the driver is not present. I edited grub.conf to take me back a version and I am now running under the previous kernel 2.6.35.11-83.fc14.x86_64. I tried a yum search for kmod-nvidia-2.6.35.12-88.fc14.x86_64 and nothing was found. I have enabled these repos:
[Code]...
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 generally check what updates are being installed. This time sadly I didn't and again this kernel had one missing module. VirtualBox-OSE stopped working. It had been working fine with other upgrades. No it's not a problem with dkms or other stuff. This kernel doesn't have vboxdrv module like other kernels...i verified it...
[Code]...
The 2.6.38.8 version doesn't have vboxdrv module!....hence again I have to roll back to older kernel. So before blindly upgrading....read this message!
I just built some machines with the Intel 82574L gigabit ethernet chip, loaded Fedora 14, and discovered a problem with the e1000e driver dying after a few minutes. A little time spent perusing the web told me that the same driver had problems in Fedora 12 and Fedora 13 as well. Congrats to Fedora for the hat trick.As of kernel 2.6.35.10-74.fc14.x86_64, e1000e driver 1.0.2-k4 still had bugs.[URL]
View 6 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
Keep trying update the packages (36 in total) and every time I keep getting this error
ERROR with rpm_check_debug vs depsolve:
kernel-x86_64 is needed by kmod-nvidia-2.6.26.6-49.fc8-173.14.12-5.fc8.2.x86_64
kernel-x86_64 is needed by kmod-nvidia-2.6.26.8-57.fc8-173.14.12-5.fc8.3.x86_64
Please report this error at [URL]
I recently upgraded from FC7 to FC10 (Also, the Kernel from 2.6.22.9 to 2.6.27.19).I did the upgrade through Yum (First installed the fc10 rpms, then did yum upgrade).Now the new Kernel won't boot.These are the options in GRUB for the new Kernel
Code:
root(hd0,1)
kernel /boot/vmlinuz-2.6.27.19-170.2.35.fc10.x86_64 ro root=LABEL=/ rhgb debug
[code]....
Since 2.6.27.19-170.2.35.fc10.x86_64, dhclient wlan0 doesn't seem to work any more.
However, bizarrely, dhclient eth0 does (to the same D-link wireless router).
The AP shows connected - tail /var/log/messages
No working leases in persistent database - sleeping.
WINXP connects just fine. This (B43) has worked nicely ever since FC10 came out, and I was able to use the WiFi at all kinds of places on a recent trip. Other than a couple of yum updates, I don't think anything else has changed since. Other devices on the wlan are getting their DHCP requests satisfied correctly.
Is anyone else having this problem since about a week ago? Perhaps there's something really obvious I'm missing. I can manually assign an IP address to wlan0, manually edit the routing tables and edit /etc/resolv.conf, and then Wifi seems to work OK, so it doesn't seem to be b43 itself unless it is dropping DHCPOFFERS. If this isn't a regression, does anyone have any tips about how to debug this?
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.
I recently upgraded my x86_64 system from FC8 to FC10 using Pre-Upgrade. (related blog link) It appears that the upgrade process installed a steaming pile of i386 packages that are duplicates of existing x86_64 packages. I now get update errors because of this package clash. I have searched the fora and the most progress I've been able to make so far is: I apparently had 8 unfinished yum transactions so I did yum-complete-transaction 8 times and have no more incomplete transactions.
The output of package-cleanup --dupes is not very helpful:
Code:
[tim@servy ~]$ sudo package-cleanup --dupes
Setting up yum
Loaded plugins: refresh-packagekit
Yet I still get transaction errors when I run updates via synaptic. It checks dependencies and downloads everything and errs when testing changes. This is the error it gives at the moment:
Code:
Test Transaction Errors: file /etc/gconf/schemas/gweather.schemas from install of libgweather-2.24.2-1.fc10.x86_64 conflicts with file from package gnome-applets-1:2.20.1-1.fc8.i386
[code]...
the latest kernel 2.6.40-4.fc15.x86_64 is somewhat buggy !It does not the include module for the USB Atheros chip 9170.As a result the TP-LINK TL-821N wireless N (very good) does not work !The previous kernel 2.6.38.8-35.fc15.x86_64 does include them as modules.grep AR9170 config-2.6.38.8-35.fc15.x86_64CONFIG_AR9170_USB=mCONFIG_AR9170_LEDS=yHopefully a version including those will be posted soon as an update.
View 14 Replies View RelatedSo I completely fail at making a kernel x86_64, used to make them fine for just x86 but I haven't a clue on how to make them specifically for 64-bit systems.
View 3 Replies View RelatedI suffered a kernel crash today - then noticed a newer kernel was available, so I updated to it.However, it's since crashed again! Here's the message - can anyone tell me what's going on, is this a known issue or is it bad hardware?
general protection fault: 0000 [1] SMP
last sysfs file: /devices/pci0000:00/0000:00:00.0/irq
CPU 2
[code]....
