Ubuntu Installation :: Possible To Get 2.6.35 Kernel Onto 10.04 System?
Mar 7, 2011
I've got two systems, one with 10.10 and one with 10.04.2 LTS. The 10.10 system has the 2.6.35 series of kernels, the 10.04 system has 2.6.29 (i think) series of kernels. Is there any way to get a 2.6.35 kernel onto the 10.04 system? If so, what package(s) are needed for it to operate, assuming its possible to get said kernel onto the system?
If I would like to update my kernel to linux 2.6.34 on my asus eee 1001px laptop. How can I do that in the easiest way? I already downloaded the kernel from kernel.org.
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 got a rather big problem since an attempt to upgrade.My debian version is 8.0.I upgraded when apt proposed the change. I did that in two steps, with apt-get upgrade and then apt-get dist-upgrade, with the installation of a new kernel. I moved from 3.2.0-4-686-pae to 3.16.0-4-686-pae.Since the upgrade, I can't boot my system any longer.During the boot sequence, this message appears with a countdown (it's copied by hand) :
Code: Select all(1 of 4) a start job is running for dev-disk-byX2du
At the end of the countdown, the boot sequence starts again, and ends up on an invite to log in as root in rescue mode. I can't connect (maybe due to some azerty/qwerty issue, I got a French keyboard. I tried to type in "qwerty mode", with no success (the password is not prompted)).I can connect with the 3.2 kernel however, selecting it form the grub interface. I can't log in in rescue mode either, but with this kernel the boot sequence goes on and I can log as a regular user or as root, at the end of the boot sequence. There is no X, but the system seems to work.What could I do to make the system boot properly with the new kernel, or to go back to the 3.2 version ?
I've been having a problem on my AMD based machine, 4cpu, gigabyte ga-ma78gm-s2h Mobo, 8GB mem, two 2 terabyte Sata HDs.One thing I've found is that any kernel after 2.6.32-17 has a randomness at boot time whether the system will completely boot or not.
For instance just today I downloaded and installed 2.6.32-24
It fails to boot (I've tried cold boot, warm boot).Running its repair also fails to completely boot.My experience is that if I keep trying it "may" eventually boot but I believe there was some change after 2.6.32-17-generic that's causing the problem.Because as with 2.6.32.23... which also fails to complete bootup many times... eventually my guess is that 2.6.32.24 will also boot "sometimes".But why does 2.6.32.17 always boot for me? Something changed and its not my setup.
I had a working ubuntu 10.10 system two days ago with kernel 2.6.35-24. I have a gtx 460 card so I have the driver from Jockey/Additional Drivers installed.
Two days ago update manager prompted me to install 2.6.35-25. I've never had problems updating kernels so I did. I Rebooted my machine and gdm/gnome no longer starts. I always get stuck on the tty1 screen. I did some troubleshooting and figured out that my current NVidia drivers seems to be messing it up. So I booted into my older kernel (2.6.35-24) and removed my NVidia driver.
I used these steps to switch from nvidia to nouveau: NvidiaDriverSwitching
I can now boot into my latest kernel (2.6.35-25) but now I'm having problems trying to reinstall the nvidia drivers.
jockey sometimes doesn't list any available drivers. and when it does, it gives me an "System InstallArchive() error" when trying to install.
I tried installing nvidia-current via apt-get and I get these errors:
Code: Setting up nvidia-current (260.19.06-0ubuntu1) ... Removing old nvidia-current-260.19.06 DKMS files... dkms.conf: Error! No 'DEST_MODULE_LOCATION' directive specified. dkms.conf: Error! No 'PACKAGE_NAME' directive specified. dkms.conf: Error! No 'PACKAGE_VERSION' directive specified.
I'm trying to install Sun VirtualBox Additions into Fedora 12 which is installed in VirtualBox running on top of Windows 7. As the Fedora install was originally a live distro which was then installed to the HD, it may be missing some essential files for compiling.
My attempt to install the VBoxLinux additions is incomplete and I can't get the full range of video displays. The largest is This is the error message: "Your system does not seem to be set up to build kernel modules".
Should I update Fedora to install all the updates available? I did find one webpage which gave an accurate list of files to install for this purpose but can't find it now.
i want to add a new system call.im following this guide [URL] in this step 6 he said add __NR_mycall to some number, in unistd.h. in include/asm/unistd.h there are are around 1079 calls for different hardwares. and the __NR_SYSCALLS is also defined many places. I don't know where to add my new system call. and another qn is. whether the number for syscall in unistd.h and arch/x86/syscall_32.s both should be same?or they can be different.
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??
Over the past few days I have been trying to install an older kernel (kernel 2.6.28.1) on ubuntu 9.10 64-bit WUBI installation. I compiled, installed, and updated my grub for the kernel. When I reboot, the grub menu correctly gives me the option of booting into the older kernel but when I do so I receive the following error message:
error: you need to load the linux kernel first.
I am at a complete loss on how to fix this. I even downgraded grub but I still get the same error.
With the recent upgrade kernel, my ATI driver can no longer work. After upgrading to the new kernel, upon reboot I would get stuck at the "checking battery status" and can't boot into kubuntu.
I'm running Kubuntu 10.10 64 on intel i5 with radeon hd 4870.
So I thought I messed something up since I was fooling around with conky script the day before. I did a clean install of kubuntu 10.10 64 and reset all my settings and my files. At this point, everything works smoothly and I can reboot multiple times without a problem.
I proceeded to install the Radeon catalyst driver following the documentation, which worked perfectly for me on the previous kernel. After rebooting, I can no longer get pass the "checking battery state" black screen. I had to boot into safe book, uninstall all fglrx and also delete xorg.conf to be able to boot back in normally.
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 just updated my mainboard, because of a failure in the grafic chip. Now I have a icore 7-2600K CPU with 16GB memory.The system will not boot with the latest kernel version Kernel 2.6.38.11 - Kernel 2.6.38.10 . It crashed and resets the system.
But when I am using Kernel 2.6.35.30, then it works, as you can see. As well the kubuntu 64bit CDROM does not work. Crashed as well.
Trying 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....
there is an issue with the way the Linux Kernel addresses memory by default and the graphic drivers for my Asus G1Sn. I have a patch that I had compiled against a custom kernel for 2.6.27.xx how ever it does not work with the latest kernel in Fedora 11. It is beyond me to rewrite the patch to work with a different kernel.
I use a pretty fresh installed RHEL 5.4, which should be very similar to Fedora. After the basic installation I installed xen and xen-kernel via yum with no errors. I can select the xen-kernel at boot time. But after booting the normal kernel shows up.
I installed the latest kernel liquorix (2.6.35) but when i want to install the Nvidia driver downloaded on the Nvidia website (256.53), i have an error message because Nvidia doesn't found the kernel source tree.
I install linux-image-2.6.35-6.dmz.2-liquorix-686_2.6.35-16_i386.deb, linux-headers-2.6.35-6.dmz.2-liquorix-686_2.6.35-16_i386.deb and build-essential. I don't understand why the installation doesn't works.
I have upgraded my Ub-10.10 to 11.04 yesterday. Everything works well except new kernel.When i try to boot with 2.6.38 kernel, i can't get to the desktop. Only black screen.But when i try to boot with old kernel (2.6.35) from "Previous Linux" on GRUB, it works well without any problem.PC Specs >> AMD Athlon X2 5200+, ASUS M2A-VM, OCZ 2 GB DDR2 800 Mhz RAM and Palit Sonic GTS 450.
i upgraded my kernel to the latest version that being linux-image-2.6.31-19 and now when i start my linux box i get the grub shell. this problem happend once before but i only had to run the command: sudo update-grub2 and everything turned back normal. now even though i run the command everytime i restart my linux i get the grub shell.
Firstly my gdesklets have gone, and if I try to run gdesklets then I get a blank window in the top left corner, followed by another blank window in the centre which disappears, then the first one fades to gray.
Secondly, clicking the 'running man' to exit just closes both gnome panels.
Ubuntu 8.04 (2.6.24-25)I know 8.04 is pretty old now, and I should probably start over, but it was all fine until this latest update.
I'm running Ubuntu 9.04 side-by-side with Windows XP.
Today, all of a sudden my system kept freezing up, forcing me to manually power-down my computer. Well, I tried picking an earlier kernel to boot from and, sure enough, there was no longer a problem.
I upgraded a PC from 10.04.1 to 10.10 and it will not boot into the new kernel. Because the system started as Ubuntu 7.10, it is using Grub 1.
It gets to the point where it displays "Starting up..." then displays a flashing cursor at the upper left of the screen, it does nothing further.
Yet it will boot into the previous kernel from the 10.04.1 installation, but X will crash if I login using the XFCE desktop, yet it will log into LXDE without a problem.
Is this a known issue (not booting up with new kernel)?
The CPU is an AMD Athlon 32-bit which does have CMOV (per cat /proc/cpuinfo). I have also manually run various apt-get commands to upgrade/update everything, no change resulted.
System continues to boot OK and everything seems to work fine as I expect. I am not sure what the above causes. It looks related to USB, but I am not sure. lsusb gives:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
I;m installing RTAI and I get this message. I can't seem to find the solution, because I really don't know exactly what the main problem is. There are a list of error,s and warnings that I 'm not sure from where should I tackle the problem: Here is what I get when I boot my 2.6.31.8 kernel with GRUB. (I used the RTAI x86 compatible patch):
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?