kernel with which most version number may be compiled in Debian 5 stable without updating to testing? 2.6.32.8 can't compile, if not turn off virtualization, since Documentation/least/least.c
contains #include <sys/eventfd.h>
which is present in libc6-dev from testing, but is absent in stable.To drivers compiling kernel used own linux/eventfd.h.
can't use catalyst driver, virtualbox refuse to run, selinux problems,I want to know if its possible to install only this new kernel 2.6.38 without "contaminating" the rest of my installation with unstable packages?
I have met a Bug in the debian squeeze with the kernel 2.6.32-5-xen-amd64 and Xen 4.0.1 I have try with two differents environment, but i have the same result. I haven't this bug when i use just the kernel 2.6.32-5-xen-amd64 without the hypervisor Xen 4.0.1 and on the debian lenny with the kernel 2.6.26-2-xen-amd64 + Xen 3.2.1. When i run a script who create a snapshot of a LV, i have this Bug error: Just after the "lvcreate -s -n Snap -L 1G /dev/data/svsqueeze" in the script
I'm looking for some guidance on how to install a mainline kernel. I opened a ticket for a problem I'm having here: [URL]. It was suggested to me that I go here for instructions on how to install the mainline kernels: [URL]. However, when I go there, it explains what to download if you have 32 bit intel (i386) or AMD 64 bit (amd64), but does anyone know what I should download if I need an x86_64 (64bit 10.04 lucid) kernel? Is it i386? Wouldn't that just be 32 bits? I have a Dell e6510 laptop running 64 bit lucid (10.04 - kernel 2.6.32-23) on an Intel Core i5. My laptop stopped working when the 2.6.32-24 kernel was downloaded and installed through the update manager.
I've just install debian squeeze version, or the testing one, but I am not really happy with it. Is not listening me all the time. If I install the debian stable I don't have internet connection. Is it possible to update the kernel somehow using the testing version?
I am trying to keep a stable system (after a date with the unstable version which broke everything ) but a package (namely deluge) is horribly out-of-date. It is better in the unstable packages.I read the official documentation with the preferences file, pinning and the rest of the apt zoo but after a few tests I am still there with my old deluge in my stable environment.(in reality I managed to upgrade deluge by swapping the sources.list file with one with only the unstable repositories -- but this is not a particularly clever approach)I would be very grateful if someone could give me the right content for the preferences file which would allow to keep the system at stable level, except for the deluge package which should be updated to the newest, bleeding edge version.
I believe this has something to do with an mdadm update which was included in the release. When I configured the array, I didn't partition the disk devices, so maybe that has something to do with it. I am thinking of rebuilding the array and partitioning prior to build, but a quick fix would be referable.
And also something appears to have happened to the raid device since the update.
Prior to update, the array was /dev/md0 - now it is /dev/md/0 which is a symbolic link back to /dev/md0.
mdadm --detail --scan now reports /dev/md/0 where previously it reported /dev/md0
I created a new RAID1 array on a fresh system and immediately after the create, these messages appear at 5 minute intervals.
I'm wondering what the stable kernel is for opensuse 11.4 kde because I ran an update and I'm at 2.6.37~ and I remember Ubuntu is at 2.6.39.10~ ; is the 2.6.39.10 kernel considered unstable is that why opensuse is not using it yet? I just started using opensuse KDE and I haven't used other distros/linux so thats why I'm asking.
At this time use opensuse11.3 (all as deafult).In this place The Linux Kernel Archives read about new kernel:stable: 2.6.37 2011-01-05 How compile and boot opensuse11.3 with this new kernel ?
I can cause the kernel to panic immediately with the following command. lvcreate --snapshot --name Snap --extents 100%FREE VolGroup00/LogVol00 The last line of the panic message is "<0>Kernel panic - not syncing: Fatal exception" If I create a snapshot of any other volume it works just fine. It only panics on LogVol00 which is my root fs.
I'm running 5.4 after update from 5.3. It didn't work with 5.3 either. This is a 32-bit guest running in VMWare Server 2.0.1 which is running on FC10 x86_64. I've tried the guest in both UP and SMP (2 cores) modes and observed no difference.
However, I noticed that there are some difference in the headers files that get generated with the above command as compared to the header files that are available from Debian repo. For example, the header files for 2.6.24 kernel have files like:
Code:
debian:/usr/src/linux-headers-2.6.24-etchnhalf.1-686/arch/x86# ls Kconfig Kconfig.cpu Kconfig.debug kernel Makefile Makefile_32 Makefile_32.cpu Makefile_64 However, if I custom compile the above kernel from Debian sources (2.6.24), the headers files does not have the above files:
Code:
debain:/usr/src/linux-headers-2.6.24-generic-ide/arch/x86# ls boot ia32 Kconfig.cpu kernel lib mach-es7000 mach-visws Makefile mm pci vdso xen crypto Kconfig Kconfig.debug lguest mach-default mach-generic mach-voyager math-emu oprofile power video
As you can see from above output, files like Makefile_32, Makefile_32.cpu are not present, if I generate kernel headers files using the make-kpkg command as mentioned in the beginning of the post. I happened to notice the above issue, while I was trying to compile a out-of-tree kernel module and the "make" command for those sources (some graphics card drm module) worked with the default header files (linux-headers-2.6.24-etchnhalf.1-686) but did not work with (linux-headers-2.6.24-generic-ide) because it did not find the Makefile_32. Although I was able to fix the problem by copying the Makefile_32 from linux-headers-2.6.24-etchnhalf.1-686 but I would like to know why there is a difference. This is bit of a concern because it unnecessarily breaks the out-of-tree module compilation process because of trivial reasons.
I installed a fresh copy of Slackware 13.1 (stable) on one of my media servers and I am experiencing something strange.... When I power up the machine, I see the kernel booting, no errors, until it gets to the point where it says:
And then randomly freeze there.... Well the machine is not totally frozen because the cursor still blinks. But it will never continue... Like I said, this happens on a random basis... After a reset, it might go through or simply stall at the same spot.
I remember after installing Slack 13.1, I rebooted the machine but forgot to remove the DVD from the player, so the install routine started up, and froze at the same point when it was loading the kernel for the setup programs...
My mobo is a MSI k9N platinum.
I never had this problem before.... (well I never used 13.1 before). Since I got this machine, I used slack 12.2 and slack 13-current with success.
This problem makes the machine extremely unreliable because I intent to use it as a backup and media server, so chances I will WOL the machine and use it remotely... if that happens.
I recently installed debian squeeze 32bit on a second partition of my amd athlon 64 X2 dual core machine.Currently it is using linux-image-2.6.32-trunk-686 kernel.But linux-image-2.6.32-trunk-amd64 is available.on the repository.Is it a 64bit kernel or 32bit kernel optimized for amd64 architecture?
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 a problem with my custom kernel when I want to create the Nvidia kernel module.After this finished I installed the image and headers and created the Nvidia kernel module. Everything worked fine.However, if I remove the linux-source from my home directory then I can't create the kernel module.Even though I have the headers for the kernel installed.
I have a set of vm's with stable, testing, and sid to keep track of how things are going. When I did an apt-get dist-upgrade with squeeze last week, things seemed to OK (350 package updates) until the end. It didn't seem to like and / or was confused by a kernel dependency.
I am not too concerned yet. Because these are in vm's, I do a snapshot before any significant change. I can futz around with impunity because I have that backup.
I re-booted, and tried the apt-get dist-upgrade again with same results. I think I also tried apt-get -f install.
So I reverted to the snapshot, and will simply try again in the future. I recall that with lenny as testing, the font-desktop was really screwed up for about a period of 6 weeks.
However, just in case someone else runs into this:
1) a re-boot worked, but the failure of apt-get made me nervous enough to revert.
2) waiting for corrections has seemed to work in the past (with a single exception with a 4-disk SCSI software RAID10 update that failed to re-boot lenny successfully after what seemed to be a minor update -- that was on a real system, not a vm. I haven't gotten back to look at that.)
I started to use Debian Live about three months ago. I can't get snapshot to work correctly. Each time the system boots or shutdown, the system over-writes the persistent file. I'm currently have to use the live-snapshot command to make a snapshot. Make a copy of the file for a backup. Then I have to boot my system and make a copy of the backup and rename the file the correctly. Turn off my laptop (not shutdown). then restart it for the persistent to work. Must be a easier way.I have three partitions: debian-live (/dev/sdb1), live-sn(/dev/sdb2), and home-rw (/dev/sdb3) on a 8 gig usb flash drive.
It sounds like he's making a difference between the kernel "source code" and the kernel itself(as in the downloaded file/ files) but the way he talks about both is the same.So then, if one had already "installed" the "kernel sources code," why would he need the "tarball with the newest Linux kernel?" He's already "installed" a kernel, right?
I used to install the latest kernel for opensuse 11.3 from this repo:
Index of /repositories/Kernel:/stable
but for 11.4 it is empty. I can see that for 11.3 the 2.6.38 kernel is already built.For 11.4 there is only the Kernel:/HEAD repo. Are we going to have a kernel:/stable repo for 11.4?
Sometimes 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
Which is the current stable version of kernel in fedora 10 and how can I installed because right now I have unstable kernel: uname -a Linux blind 2.6.29.3-60.fc10.x86_64 #1 SMP Sat May 9 04:18:14 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
I just want to get back to latest stable kernel of fedora 10. I'm not able from the grub to choose an older because there are only kernels for fedora 9. The problem was that previously I used fedora 9 however I upgrade it but it was still with kernel of fedora 9 so I pick it the unstable of fedora 10 and I installed it. Right now I just want to get back to current version of kernel in fedora 10 so I can upgrade it to fedora 11.
On Lenny, due to some compatibility issues: kernels before 2.6.26 don't recognize part of my vaio laptop's hardware, while the last drivers of my videocard (version: 260, card: nvidia gt 230m) suffer some incompatibility problem (this is one of the most problematic computers I ever had), so I have to use version 256, which doesn't work with kernels after (perhaps) 2.6.32. So, I suppose I have to check each kernel between that two versions and hope that one of them will be ok. I searched quite deeply over the net but didn't find anything related to debian, except for generic kernels [URL], but as someone told me that it's better if I only install stuff from the stable repository or backports. What can I do? Is there any backports archive or something like that? Otherwise, what should I do?
I have installed CentOS 5.4 & am trying to install VirtualBox on it. To install VirtualBox I run the command:
yum localinstall path/Virtualbox.rpm
It runs through the dependency check & says everything is fine. It installs the rpm & then says that compiling of the kernel module failed & that VirtualBox will not start until this is fixed, & that the most like cause is that the kernel sources are not installed.
I have installed the kernel-devel package & have the kernel source tree located at /usr/src/kernel/2.6....
Since all what I can find on google is about benchmarks I'd like to ask you if a 64 bit kernel would be more stable , secure and reliable than a 32 bit one.
I ask this question because apparently the 64 bit instruction set offers more advanced security features (i'm saying apparently because I'm not able to give details since it been a really fast read) which would be used by a 64 bit Operating System (Apple also stated that 64 bit applications are less likely to be "attacked").
I have to assume that a 32 bit one does not use them right? Should I stick to 64 bit? (to be honest that "not for everyday" thing on ubuntu download pages made me wonder lol, because since intrepid i ALWAYS used the 64 bit version)
My "lowest" computer has a pentium processor (1,6 ghz dual core) according to lshw I have NX enabled and my ram is 2GB (might seem useless using a 64bit kernel on 2 GB but i'm more concerned about security now)