Debian :: How To Upgrade The Debian 3 Kernel 2.4.18 To Kernel 2.6 Or Bigmem-kernel
Nov 9, 2010
We have a Dell 1850 with Debian 3.0 (woody) with 2.4.18 kernel running some critical applications, now the issue is we need to upgrade the memory to 8 GB but the memory is detected by the bios itself, Operating system is not able to detect it, it is showing 3096MB of memory. i came to know the solution i.e I need to install the Bigmem-kernel to detect the ram more than 4Gb, Any another solution for this to update operating system to detect the more RAM.
We have a Dell 1850 with Debian with 2.4.18 kernel running some critical applications, now the issue is we need to upgrade the memory to 8 GB but the memory is detected by the bios itself, Operating system is not able to detect it, it is showing 3096MB of memory,
After a lot of googling and the artical in linux.com/archive/articles/119287 :: Got more than a gig of RAM and 32-bit Linux? Here's how to use it i came to know the solution i.e
1)I need to install the Bigmem-kernel to detect the ram more than 4Gb,
2) or change some kernel parameters in configuration file and rebuild the kernel
Is there any another solution for this to update operating system to detect the more RAM
I'm running Debian Squeeze/current fine with the default kernel & ATi's Catalyset drivers. I'm struggling to get the display drivers to work with the bigmem kernel as I've got 4GB ram on my machine so might as well try to enable it.
I can have my system work with the normal Squeeze kernel by installing the normal kernel headers & then FGLRX drivers, but after additionally installing the bigmem kernel & headers (linux-image-2.6-686-bigmem & linux-headers-2.6-686-bigmem) I cannot get the system to reach X after removing & then re-installing the video drivers.
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?
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?
As a follow-on to something Telemachos said in another post:
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:
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:
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:
Also, the linux-headers packages I have installed are:
So, when I get around to removing the linux-image-2.6.25-2-amd64 package like this:
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?
The 486 kernel works just fine, and while I have only 1GB of RAM at the moment I hope to have 2GB someday and would like to take advantage of the dual core CPU, so I would like to configure grub to run the 686 kernel by default. For whatever reason, it runs the 486 right now and the 686 fails in a major way: there is no network connectivity at all. It could be plugged into my cable modem router and it shows no wired connections. The fact that one works and the other doesn't puzzles me since I haven't touched either since the install and a few rounds of upgrades.
I should mention I'm newbie but getting better; I managed to install debian on this x60, yet while preserving the factory install rescue & recovery partition and preserving the factory install MBR so that ibm-specific hardware functions (thinkvantage button, etc.) still work. This required me to use dd to copy the first 512 bytes of my debian partition to a file in the windows partition, etc., and modifying the windows bootloader. (I wish I had learned dd long ago--it rocks). I did this because if I ever resell the X60, the fact is most people use MS Windows and having that partition adds a perception of value to some potential buyers; not to mention I paid $ for it (I was young & stupid) so why should I delete it. I also backed up the recovery partition on another drive using dd over NFS in case the hd ever heads south.
Anyway, I've never been comfy with messing with the kernel. I did once recompile a module for ALSA because it had a bug in it for an old Yamaha integrated sound card on an old PIII and the newer version worked [alsa fails on this x60 too but I think I found a post on here that has a solution I will try later]. But I'm clueless as to networking modules, not to mention the correct module is installed already from Intel for this chipset. So what is there to do?
Here's a clue: the ifconfig output is radically different from the 686 and 486 kernels. Looks like hardware is not being detected since eth0 fails to show:
I would show the diff output below if it weren't so long--and not allowed--upon 2 text files, the first holding the output of modprobe -l under the 486 kernel and the second under the 686 kernel.
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 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 would like to update my kernel to version 2.6.32 to see if it solves my tv-tuner card issues (not being recognized by the kernel Lenny uses 2.6.26-2 x64). What steps should I follow to accomplish this upgrade?
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'm running Lenny with the default kernel 2.6.26. I recently got a wireless card supported by the ath9k driver, so I followed the instructions on this site:http://wiki.debian.org/ath9kwhich had me install a 2.6.32 kernel image from lenny-backports. Everything installed fine without errors, but when I rebooted after the install, after the kernel messages scrolled by and the screen would normally switch to the gdm login screen, all I got was a blank screen with some distorted squares. I used Ctrl-Alt-F1 to switched to a shell and everything looked fine, but when I Ctrl-Alt-F7ed back to X, I got another black screen with distorted images. Any idea what could have caused this from the kernel upgrade, and what I can do?Edit:Here is the end of my /var/log/Xorg.0.log after booting:
(EE) fglrx(0): PPLIB: PPLIB is not initialized!. (EE) fglrx(0): PPLIB: swlPPLibNotifyEventToPPLib() failed! (EE) fglrx(0): ulEventType = 0000000c, ulEventData = 00000001
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:
I have a MyBookLive where i installed a Debian 2.6 kernel. The system is running fine so far. Because of an error message when apt-get upgrade (udev) i tried to upgrade to 3.16. Here's what i did:
- apt-get install linux-image-xx - apt-get install linux-source-xx - extract the source - copied the old .config from running 2.6 kernel over to the 3.16 directory - make oldconfig - make uImage - make modules - make modules_install - copied uImage to /boot
No error messages because its a headless device - its just not booting up.
Upgraded Debian Lenny kernel from 2.6.26 to 2.6.32 along with Firmware to make my new wireless Linksys WMP600N card with ralink rt2860 chip on it work. I followed directions exctly from [URL]. I answed "YES" to all button options as there were statements threats there would be problems if i did not answer "yes". Eveything seemed to go OK. Only thing alarming during procedure was a statement " Config files still contain depreciated device names. The following configuration files still use some device names that may change when using new kernel: Etc/fstab:/dev scdo. I figure this file easely editable later so I did not worry.
Pleaseantly greated with new kernel 2.6.32 to boot but it fails to get to the log in screen to select GUI. I have previously been using Gnome and KDE3.5 back and forth.
I get the following mesages that I somewhat abriviated
Failure to start X server, Likely it is not set up corectly. View X server output? "yes" reports x.org.x server 1.4.2..........build OS debianlenny.... Check http:wiki.x.org to make sure you have latest version. Modual present The x server is now disabled.
I then booted old kernel and updated xorg with synaptic, some 52 packages and retried booting the new kernel with same results.
I have navigated to the /var/init.d directory and tried starting both Gnome and KDE by typing "kdm start" and "gdm start"with similar results. What have I messed up?
I'd be interested in your views on this. Background: After many hours of trying to configure a particularly recalcitrant graphics card as posted here, I eventually resorted to trying Mandriva 2009, which, with the 2.6.27-desktop 586-0.rc8.2mnb kernel, solved the terrible problem of slow, hit-and-miss booting with Debian and also random freezes with Ubuntu.However, when updating to Mandriva 2010, the problems with booting, and also a wrong screen resolution were back so, for the time being, I settled for the 2009 release.
My question is: Having found out that the Mandriva kernel worked, does anyone know if would it be possible to finally bring this laptop to heel with Debian + a 2.6.27 kernel and following the time-honoured adage of "if it ain't broke, don't fix it" leave such a kernel in place without updating to a newer one?
I'm just wondering what the options are if one wants to try a 'newer' kernel and/or XServer version.
Either on an installed system or virtual machine (for e.g., Squeeze in VirtualBox).
On an installed system, on Debian Sqeeze (or Testing), if one wants to upgrade to 2.6.36 kernel and/or XServer 1.9, what are the options? I noticed that 1.9 is available in experimental so one has to enable and load the experimental package repository?
As for the kernel, I guess there's a few options? One includes installing the liquorix kernel? Best choice/alternative is compiling?
I have a system that was upgraded from Debian 7 to 8. Unfortunately it is not able to boot from the new kernel 3.16. Only the old 3.2 kernel is able to boot. I could transfer a backup, install it in Virtualbox, redo the upgrade and I can reproduce the error..The last error before "panic" is this line
Code: Select all 59.073579] Freeing unused kernel memory: 216K (ffff8800017ca000 - ffff880001800000) Loading, please wait... [ 59.226154] systemd-udevd: starting version 215 [ 59.326564] random: systemd-udevd urandom read with 4 bits of entropy available Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... /init: .: line 210: can't open '/scripts/init-premount/ORDER' [ 59.552148] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200
Finally ran the upgrade from lenny to squeeze and ran into a few issues. I have to admit this is the first dist-upgrade I've ever had go this badly (kernel issues, xorg issues, mysql transition problems, mythtv... Yikes!).Anyway, the first problem I'm trying to fix is getting dpkg to like the new squeeze kernel. Here's the errors
Code: Errors were encountered while processing: linux-image-2.6.32-5-686
Yesterday, I ran a security update that upgraded my Squeeze kernel from 2.6.32-48squeeze8 to 2.6.32-48squeeze9.
Ever since then, my suspend to ram (STR) function is broken.
The machine will suspend normally, but will not resume. When I try to awaken the machine, I can hear the fan in the tower start up (the subject machine is a desktop computer, please see below for specifics), but the machine seems to be otherwise dead (e.g. the monitor stays blank, pressing the "caps lock" key on my keyboard does not activate said keyboard's "caps lock" led, Ctrl-Alt-F[x] has no effect, etc). My only recourse at that point is a hardware reset (ouch!).
I tried running Code: Select allpm-suspend from a terminal, with no joy. Same result running Code: Select allecho -n "mem" > /sys/power/state from a terminal.
I checked the /var/log/pm-suspend.log file and noticed that each Code: Select all...performing suspend line used to (before said kernel upgrade) be directly followed by a Code: Select all...Awake. line, but, now, all said Code: Select all...performing suspend lines are followed by an Code: Select allInitial commandline parameters... line.
Before this, STR has worked well ever since I first loaded Squeeze on this machine back in 2012.
Code: Select allSqueeze 6.0.10; 2.6.32-5-amd64
Intel i7-980 Gulftown CPU Asus P6X58D Premium Motherboard EVGA GeForce GTS-450 Graphics Card G.SKILL Ripjaw DDR3-1600, PC3-12800, 1.5v RAM (6x4GB sticks, 24GB total) Crucial RealSSD C300 128GB SSD Western Digital Caviar Black 1TB HDD Corsair HX850 PSU
I'm running Debian Squeeze and last night i upgraded to the latest kernel release. Rebooted and noticed that as the system temp rises the fan runs louder(as expected)t unlike before, it no longer gets quieter as the temp drops again. I didn't really think the OS managed that so bit confused why it is happening.I booted into Windows 7 and with the exact same temps the fan drops back down to a quieter state
This is a problem about linux-kernel-3.16-0-4-amd64 and LVM, I guess. I decided to write this here in case other users who installed their debian system with encryption enabled experience this problem with a recent kernel upgrade.
I use debian jessie. Today I gave the command:
Code: Select allapt-get upgrade
There was a linux-kernel upgrade to 3.16-0-4-amd64 among other packages to be upgraded.
After this upgrade my computer cannot boot anymore.
I get following error:
Code: Select allVolume group "ert-debian-vg" not found. Skipping volume group "ert-debian-vg" Unable to find LVM "volume ert-debian-vg/root" Volume group "ert-debian-vg" not found Skipping volume group "ert-debian-vg" Unable to find LVM "volume ert-debian-vg/swap_1" Please unlock disk sd3_crypt:
And it does not accept my password.
I used rescue environment on debian jessie netinst iso and decrypted the partition and took a backup of my /home. Now I have not much to lose if I reinstall my system but I still want to fix this problem if possible.
I have reinstalled the kernel using debian jessie netinst rescue iso but nothing changed.
I have Timeshift snapshots located at /home/Timeshift but timeshift --rescue command cannot find a backup device, it sees the device as crypted. If I could restore a snapshot it would be very easy to go back in time and get rid of this problem. It would not be a real solution, however.
There is not any old kernel option in GRUB menu. So removing the latest one does not seem as an option.
Intel Core i7-5500U with Intel HD Graphics.So I updated to the backports kernel and backports intel xorg drivers and I have the weirdest thing.Everything is stuttery even cinnamon desktop effects are no longer smooth. If I boot back to 3.16, everything is butter (except the screen corruption). Even my favorite wine game dropped 25% in fps.
I remember that on windows, if the cpu is too slow (pstate_min_speed), graphics is also stuttery. However, increasing /sys/devices/system/cpu /intel_ pstate/min_perf_pct even to 100% didn't do the trick. I suspect, that this measure is causing it: URL....
how to increase the performance again? I just found out, after running glxgears (with about 40 fps), that xrandr shows an available framerate of 40fps
xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 eDP1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 293mm x 165mm 1920x1080 60.00*+ 59.93 40.00
I guess that's what makes it feel slow. Do you know how to get that back up to 60 (fixed)? It seems like the screen refresh rate set in xrandr has no effect on the problem. When I boot, glxgears runs with 60 fps and everything is fine. After a while, it drops to 40 and the whole desktop keeps stuttering. if I change the resolution with xrandr and then change it back, it goes to 60 again for a while
I have a problem. I'm using the latest Debian stable, Lenny. I am trying to get my usb wifi card working. The Debian wiki advised me to upgrade my kernel to 2.6.30 using backports, because the drivers for my wifi chip are supposedly in the newer kernel.
So thats what I did. The install went fine. However, after rebooting the computer hangs when it is starting gdm. Only the desktop background appears with some fuzzy stripe over it, the mouse doesn't respond. Pressing ctrl+alt+f1 does nothing. I can only restart with ctrl+alt+del.
I can still use the computer with the old kernel. No problems there. I tryed disabling GDM and rebooting again with the new kernel. It boots up and works fine on command line. However when I type startx it hangs, just like before.
I'm not an expert, but I'm suspecting there might be problems with the graphic drivers in the new kernel. When I installed lenny at first, X started fine. However 3d acceleration was not functioning. I got help from IRC, I had to install some package to enable direct rendering. Don't remember which one anymore.
Here's what lspci gives for VGA: 01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS
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 ?