From F12 to F13. Is there anything I should remove before updating? I have few programs isntalled from source/binary installers in /usr for example. Would it cause problems?
And is there any chance to be able to switch from a 32 bit kernel to 64 bit kernel during the update? The hardware is capable of this.
Initial FC12 install worked great, kernel 2.6.31.5-127.fc12.x86_64 allowed radio kill switch functionality Fn-F11 for wlan and Fn-F12 for bluetooth.The last two kernels have broken that functionality.
Fedora (2.6.31.6-162.fc12.x86_64) broken!
Fedora (2.6.31.6-145.fc12.x86_64) broken!
Fedora (2.6.31.5-127.fc12.x86_64) works!
[code]...
Fresh and Full install: Slackware 13.37 64-bit x86_64. What is the correct procedure to switch from huge kernel to 2.6.38.4 kernel?
View 6 Replies View RelatedI am using DEBIAN 6.0 and I wannna update my kernel from 2.6.32 to 2.6.38. Every time, I do it but after the installation & rebooting into the new kernel it gives me error "UNABLE TO BOOT INTO THE KERNEL".
View 1 Replies View RelatedI have the following strange thing with a RHEL4 installation. Since last week, the system did a reboot and now something is really fucked up. During boot we get the following messages (don't care about 'strange' typo's, my colleague typed it 'blind' from the screen)
Code:
The strange thing is that we never see a 'could not mount blabla' or similar messages. First we thought it was a failing kernel update by plesk, but even after manually updating the kernel with RHN RPM's, still the same message. Booting with rescue mode and then chroot the system works. After that we even can start things like plesk and so on.
We double checked things with another RHEL4 install, and at least two things were odd:
1: the working machine has /dev/dm-0 and /dev/dm-1, the broken one doesn't
2: some files on /dev didn't have group root, but 252
We tried to recreate the /dev/dm-X nodes with [vgmknodes -v], output:
Code:
A fdisk /dev/sda shows: /dev/sda2 XX XXX XXXXX Linux LVM (I removed the numbers because this line is from another machine, but rest was identical)
We have a copy of the boot partition so if one need more info please let me know.
grub.conf:
Code:
last part of init extracted from initrd-2.6.9-78.0.8.ELsmp.img:
Code:
Is there a way to get the matching Linux kernel headers automatic on a regular kernel update via the Ubuntu packed manager? Every time I get a new kernel I must do an aptitude install linux-headers-`uname -r`
View 1 Replies View RelatedA recent kernel update seems to have misplaced the Kernel Headers. VMWare needs these headers and cannot find them. Attempting to run VMWARE gets the message: Kernel headers for version 2.6.31.12-0.2-desktop were not found.
View 4 Replies View RelatedI'm running Virtualbox from the Sun website (need the USB support) and it breaks after each kernel update.The problem is that I installed a lot of Ubuntu systems for transitioning windows users with Windows in virtualbox to ease the migration but I have to rerun vboxdrv setup after each kernel patch.
View 2 Replies View RelatedAt 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 Relatedafter update to kernel-2.6.18-164.el5 one of the 2 NIC's of my machine are only found at 1 of 4 reboots. Using the old one kernel-2.6.18-128.7.1.el5 all is fine. This are the to NIC's:
00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:0b.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 0c)
And the Intel one, makes the problems with the new kernel.
The server runs# uname -r2.6.18-128.4.1.el5However, today I executed yum update kernel*due to security advisory. I was just about to reboot the system when I realized that it runs VMWare Server Instance that will most likely fail to restart after kernel upgrade (I had a hard time fixing it after previous kernel update). Now I want to keep 2.6.18-128.4.1.el5 after reboot.I see that new kernel is scheduled for booting:
# cat /etc/grub.conf
default=0
timeout=20
[code]....
One of our F14 machines was originally set-up with the i386 Kernel. I found out it had a kernel crash and the person tried to fix it by reinstalling the kernel, unfortunately they installed i686. Now some of our software that was setup to work with i386 is not cooperating. Is there a way to switch from the i686 kernel to i386 without reinstalling the system?
View 1 Replies View Related9.04 this morning updated my kernel to I believe it is 2.6.28.18 and upon the reboot I had no desktop. It booted wanting to go into low graphics.
So I drop to shell and stop the gdm and try to run the latest nvidia run file I have and it hangs saying I have a x server running.
Otherwise I am needing assistance with getting my desktop back! I can boot into an older kernel and if need be I would like to roll back that latest update this morning, but once again I am forgetting the command line for that.
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 RelatedI am receiving a transaction error when I try to update to a newer kernel, the error is:
Test Transaction Errors: installing package kernel-debug-2.6.32.16-150.fc12.i686 needs 519KB on the /boot filesystem If I run disk usage I get:
# du -h /boot
217K/boot/efi/EFI/redhat
219K/boot/efi/EFI
[code]....
System monitor shows I have 56% free in /boot. So where can I get the extra free space or force yum to recognize there is enough in that directory?
I'm using F13 and I would like to update my computer using yum update.
I did this a few weeks ago and yum update downloaded and installed
Quote:
kernel i686 2.6.34.7-61.fc13
After a reboot I got
Quote:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
To get around this I did a ctrl + s and booted to an earlier kernel. Once in I deleted the latest kernel using
Quote:
rpm -q kernel
to list the available kernels and
Quote:
rpm -e kernel-version
to delete the latest kernel. Once deleted my computer starts up perfectly.
How do I run yum update without reinstalling the bad kernel?
I do not understand this problem. I am using kernel 2.6.35.10-74.fc14.i686.PAE and while that works fine I know new kernels makes things work better. As such, every time a kernel update comes along just like all other updates, I perform a yum update. But for some unknown reason, I am successfully updating everything except the kernel.
I have attempted updates with 2.6.35.11-83.fc14.i686.PAE, 88, and 12-90 and at the very beginning of the boot I always get the same panic error and boot freeze. The message is ALWAYS as foolow. The only part of the message that changes is the kernel numbers.
[I did my best at hand writing the error message.]
I hope this makes sense to someone.
MESSAGE:
Traceback (most recent call last):
File "/init" , line 157 , in <modules>
if _name_ == ' _main_ ' : main()
[Code]....
Does any of the above make any sense?? I cannot even figure how I am supposed to fix anything since the computer completely freezes at that point! I am, of course, able to hard reboot. The I switch back to the previous kernel and everything is fine but why does everything EXCEPT the kernel update?
My laptop has only 2GB of RAM so I don't think I need the PAE kernel, also there are some drivers that I want to install, they were built for non-PAE kernel.
So far I read that I have to change the :
/etc/sysconfig/kernel
---------
# UPDATEDEFAULT specifies if new-kernel-pkg should make
# new kernels the default
UPDATEDEFAULT=yes
[Code]....
I attempted to install the new kernel 2.6.29.6-217.2.3.fc11 (x86-64) A depsolv message appears:
Quote:
ERROR with rpm_check_debug vs depsolve:
kernel-uname-r = 2.6.27.19-170.2.35.fc10.x86_64 is needed by (installed) kmod-wl-2.6.27.19-170.2.35.fc10.x86_64-5.10.79.10-1.fc10.x86_64
kernel-uname-r = 2.6.27.21-170.2.56.fc10.x86_64 is needed by (installed) kmod-wl-2.6.27.21-170.2.56.fc10.x86_64-5.10.79.10-2.fc10.x86_64
[Code].....
I upgraded from fc10; there was a residue of four fc10 2.27 kernels in /lib/modules from my fc10->fc11 upgrade; I moved them to a new subdirectory /usr/oldmodules, but the yum update command still produces the same failure message.
even from a terminal it wouldn't update? Maybe because I put my bootsector as ro ?
I don't know here is the message:
When yum updates the kernel it keeps the last 3 versions; the older kernels are deleted. Is there a way to keep more than 3 versions?
I presently have one working version and two which are not compatible with my machine. One more bad version and my system will be toast. (I would like to keep the "bad" versions for testing.)
Last Saturday, I ran an update on my laptop using F12 and received a new kernel. As of this morning, the new kernel hasn't shown up on my desktop, using f 11. (Yes, I check every day.) Currently, my uptime is 34 days, so you can see how long it's been since the last kernel update for F11. Does anybody know why there'd be an update for one version and not for another? In case anybody's wondering:
[joe@khorlia ~]$ uname -r
2.6.30.10-105.2.23.fc11.i586
I'm using F13 64bit with the proprietary nvidea driver. From yesterday's software update, a new kernel was installed:
old kernel: vmlinuz-2.6.33.5-112.fc13.x86_64
old initramfs: initramfs-2.6.33.5-112.fc13.x86_64.img
new kernel: vmlinuz-2.6.33.5-124.fc13.x86_64
new initramfs: initramfs-2.6.33.5-124.fc13.x86_64.img
I load grub from another distro partition. After the update, I changed the two lines in menu.lst, as per the above mentioned, to match the new kernel.
The problem now is that after booting F13, my monitor displays a warning saying "video mode not supported".
These two files are now at /etc/x11:
xorg.conf.livna-config-backup:
# Xorg configuration created by livna-config-display
Section "Files"
ModulePath "/usr/lib64/xorg/modules"
EndSection
[Code].....
I'm not sure if it's exactly the same issue as mine. In case it is, it looks like that all I have to do is:
1 - boot from the previous kernel, and
2 - code: "yum install akmod-nvidia"
After installing the latest updates (dont know which ones) yesterday, I get a kernel panic (LED lights flashing at the keyboard and black screen) when starting X (the login manager). I am running on 64 bit with the proprietary ATI catalyst driver. How can I start in text only mode?
View 5 Replies View Relatedwondering if fedora 15 users will get kernel 3.0 by update,, or is that a typicall update for FC16??
View 5 Replies View Relatedmy problem is on installing nvidia driver on fc12 32bit but, first of all, as i understood the pae kernel requires more than 4gb of ram,i have a 2.2 ghz cpu with 2 gb ram,but when i run command:uname -r it answers: 2.6.31.5-127.PAE [i have fc12 32 bit] when we try to download linux we have a 32bit edition or 64bit edition,do we have an edition which is only for pae? or when we install for example the 32bit edition on a computer with more than 4gb of ram then the kernel automatically will change to be a pae kernel??
View 10 Replies View RelatedI'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 RelatedTrying to install virtualbox in F12 but fails when recompiling kernel module. Output of vbox-install log is:
Attempting to install using DKMS
removing old DKMS module vboxdrv version 3.1.6
Deleting module version: 3.1.6
completely from the DKMS tree.
Creating symlink /var/lib/dkms/vboxdrv/3.1.6/source ->
/usr/src/vboxdrv-3.1.6
DKMS: add Completed.
Error! Your kernel source for kernel 2.6.32.11-99.fc12.i686.PAE cannot be found
at
/lib/modules/2.6.32.11-99.fc12.i686.PAE/build or /lib/modules/2.6.32.11-99.fc12.
code....
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 RelatedI have installed the fedora 14, but there is no kernel source tree.I read the doc "building a custom kernel".But I don't want to rebuild a new kernel.I just want to install the source tree of current kernel.Could someone tell me the way?
View 6 Replies View Related
