General :: Get The Matching Kernel Headers Automatic On A Regular Kernel Update Via The Ubuntu Packed Manager?
Nov 26, 2010
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`
As a follow-on to something Telemachos said in another post:
Quote:
Originally Posted by Telemachos
You can see what kernels you have installed - to check if you have a virtual kernel and to clean up - by running this command:
Code:
If you've been installing kernel-headers along with the kernels (say to build modules for graphics or wireless), you should remove those when you remove the corresponding kernel. The command to search for those is parallel:
Code:
I would have thought that removing a given kernel package would trigger the removal of the older kernel headers. Can someone confirm that is, or is not, the behavior? I ask this because it seemed to me that the older kernel header packages were indeed removed when I removed some older kernel packages.
For example, the linux kernels I have installed are:
Code:
Also, the linux-headers packages I have installed are:
Code:
So, when I get around to removing the linux-image-2.6.25-2-amd64 package like this:
Code:
I would expect apt-get to automatically also remove linux-headers-2.6.25-2-amd64 and linux-headers-2.6.25-2-common. Is that what will happen, or do I need to explicitly state all three packages on the apt-get remove command?
A 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.
This week my ubuntu 10.10 was updated via update center. I obtained the new kernel headers 2.6.35-23-generic but now I can't boot using this kernel version and I have to select manually 2.6.35-22-generic in grub. I can see the ubuntu plymouth splash screen but it never rise gnome. where are the boot logs and how to activate them, In /var/log/ I have "boot" file but is empty and in "boot.log" I cant see any usefull information (I have BOOTLOGD_ENABLE=yes in /etc/defaul/bootlogd).
Having ubuntu 8.04, when I updated my computer to the latest kernel and headers through Update Manager, an error popped up. The error stated that it wouldn't update at this time. When I tried to download again, the update was gone in Update Manager. I checked and I don't have the most recent kernel installed. I still have 2.6.24-19. Accrding to [URL]the most recent one is: 2.6.27.
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??
Before 2.6.35-23 released this packages is present in the system:
i A linux-headers-2.6.35-22 i A linux-headers-2.6.35-22-generic i A linux-image-2.6.35-22-generic
But after automatic update to 2.6.35-23 updater install just linux-image-2.6.35-23-generic without headers. In result kernel modules of nVidia driver not compiled and next boot X server can not start.
Now I can install 2.6.35-24 image and headers by hands, but how to explain updater not forget to update headers next time and why this problem occurs?
I'm just installed OpenSuse 11.3 (64) on a 30gb SSD, hoping to get virtualbox 4.0 running to virtualize an instance of Windows 7.I went through some pain with my Nvidia video card and actually getting vb to install, but through lots of searching and tinkering got here.I created a vm in the vb control panel, but when I go to start it I get:
Code: Failed to open a session for the virtual machine Win7Main. The virtual machine 'Win7Main' has terminated unexpectedly during startup with exit code 1.
I'm attempting to install the driver for my atheros AR8131 PCI-E Gigabit Ethernet adapter (in my Lenovo laptop) on my newly installed RHEL5 system (it's not currently being recognized).
I tried using: 'make install' but hit an error "Makefile:61: *** Linux kernel source not found."
After this, I tried: 'sudo yum install kernel-devel kernel-headers'
To rectify this, but hit this error "No package kernel-devel available" (and the same for the headers). What should I do?
I've just installed debian sid and see that I've the kernel 2.6.32. I was a bit surprise as on ubuntu I had the 2.6.35 and debian sid is supposed to be more up to date that ubuntu (maybe I'm wrong).So I checked what were the packages available :
mart@mart-laptop:~$ uname -a Linux mart-laptop 2.6.32-5-686-bigmem #1 SMP Sat Oct 30 23:25:58 UTC 2010 i686 GNU/Linux mart@mart-laptop:~$ sudo aptitude search ^linux-image
I updated the Ubuntu version 10.04.1. After updating the program it tells to restart the system. After restarting the system the following message appears:
error: can not read the linux header error: you need to load the kernel first
my friend updated kernel today and it "stopped working" and I was asked to fix it he is new to linux, and I don't have physical access to that notebook from what I know main problems are:
1. no network devices exist (except for loopback) 2. sound card driver is missing (nVidia MCP79) 3. in grub menu after choosing new kernel uname -r sais the old one's version
wifi card is atheros, but I don't know specific model.
I'm trying to install the "kernel26-headers" package in Arch so I can (try to) compile the Intel 865G graphics drivers from off their website (I can't get H/W acceleration working with xf86-video-intel, but I know the thing has a GPU, because if I boot a Knoppix CD that I have, it enables Compiz by default, and it works damn well).
Any time I try "pacman -S kernel26-headers" I just get a bunch of errors spat back at me code...
Now, I have tried enabling all the US mirrors (HTTP and FTP), and I have even tried a couple of FTP servers in Canada and even Great Britain. None of them seem to work at all!
Many here know I distribute alot of live stuff and thus many say I should try to putout as high a kernel version as possible for wireless, netbooks, etc.my questions are about using a much higher kernel version than the installed headers for instance; I use kernel 2.6.34-ZEN in my arch/slackware builds but the slackware version contains headers 2.6.33.4 from slackware and so is that a problem or no?I built the kernel from source using headers 2.6.33.4 in slackware and headers 2.6.34 in arch...now, I may be upgrading those kernels to meerkats 2.6.35-r5 and need to know if having headers 2.6.33.4 is an issue?also, after compiling kernel does it install a new set of headers when you do make modules_install?
I received an update to my kernel through the update manager (updated from ****.32.14 to ****.32.19, or something like that) but grub still shows the old kernel and not the updated one. Was this not a full kernel update and only a patch or do I have to do something to use the new kernel? I'm new bear with me if this doesn't make any sense.
I'm noticing that maybe twice a month the Update Manager is asking me to upgrade my kernel. Currently it's asking me to move to 2.6.32.24.25. Is this the smart thing to do? Are these primarily securtiy updates to the kernel?
I run Ubuntu and yesterday the update manager downloaded a new kernel I think. It asked me to restart. I unlike before where when I select Ubuntu at boot up time and it just goes into it I am getting this black screen called GNU GRUB. What do I do here? Has Linux got corrupted by the updates I downloaded?
It's taken a lot of work, but I have figured out over thecourse of many many fresh installs over the past few days that the kernel updatefrom the update manager in ununtu is breaking my system. This is both for the -22 and -27 updates.Is anyone else having problems with these and/or is there a fix?
I'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.
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.
Yesterday, I think I did something stupid: I removed kernel-headers, gcc, glibc-devel and glibc-headers. My box is a CentOS 5.4 webserver (it has loads of packages installed, but that was done through Virtualmin config, so it's quite coherent all in all). The thing is that now I need to reinstall at least the headers and glibc, but hey! this is what I get :
9.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 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".
I 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:
after 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:
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:
My Ubuntu Lucid update-manager recently suggested that I install a group of updates. The following appears in /var/log/messages
Code: dkms_autoinstaller: tp-smapi (0.40): Installing module on kernel 2.6.32-24-generic-pae. dkms_autoinstaller: Kernel headers for 2.6.32-24-generic-pae are not installed. Cannot install this module. dkms_autoinstaller: Try installing linux-headers-2.6.32-24-generic-pae or equivalent.[code]....
I'd like to upgrade a live ISO file before burning a new CD.
So, following the instructions in "How to Customise the Ubuntu Desktop CD", I chrooted to the squashfs and ran "apt-get update/upgrade/dist-upgrade", expecting apt-get to upgrade the chroot kernel... only to find out that apparently, even when being chrooted, this command upgrades the actual kernel. I guess it makes sense, but I was under the - wrong - impression that chroot would build a filesystem totally isolated from the underneath host.
So I rebooted to use this new kernel:
Next, since the Nouveau video driver requires the kernel header files, I ran the following:
Code:
I don't understand why apt-get upgrades the kernel but won't install its header files.