DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Both can be installed via apt-get if you have unstable repositories in /etc/apt/sources.list A nice guide to Debian kernel can be found here: http://kernel-handbook.alioth.debian.org/ It provides some generic descriptions of the changes Debian makes to the "pristine" kernel sources.
I am currently using Kubuntu breezy and I compiled the 2.6.15.1 "pristine" kernel just yesterday without applying any patches and it works. I'm not sure if Ubuntu uses a different filesystem for the initrd, but I did not apply any cramfs patch and my initrd works. It is also possible to change the filesystem used for initrd, but I haven't investigated it.
Everything that I've read says that Debian needs extra patches because of cramfs used in the initrd filesystem. Perhaps this has been incorperated into the kernel by now.
The grub menu.lst should be updated automatically when you install the deb file created by make-kpkg. However, if you do not need to apply special patches to the kernel, the easiest way to upgrade is by using apt. Just make sure you have unstable repositories in /etc/apt/sources.list, then do:
still get errors
/usr/src/kernel-source-2.6.8/scripts/gcc-version.sh: line 11: i486-linux-gnu-gcc: command not found
/usr/src/kernel-source-2.6.8/scripts/gcc-version.sh: line 12: i486-linux-gnu-gcc: command not found
/usr/src/kernel-source-2.6.8/scripts/gcc-version.sh: line 11: i486-linux-gnu-gcc: command not found
/usr/src/kernel-source-2.6.8/scripts/gcc-version.sh: line 12: i486-linux-gnu-gcc: command not found
/usr/src/kernel-source-2.6.8/scripts/gcc-version.sh: line 11: i486-linux-gnu-gcc: command not found
/usr/src/kernel-source-2.6.8/scripts/gcc-version.sh: line 12: i486-linux-gnu-gcc: command not found
/usr/src/kernel-source-2.6.8/scripts/gcc-version.sh: line 11: i486-linux-gnu-gcc: command not found
/usr/src/kernel-source-2.6.8/scripts/gcc-version.sh: line 12: i486-linux-gnu-gcc: command not found
/usr/src/kernel-source-2.6.8/scripts/gcc-version.sh: line 11: i486-linux-gnu-gcc: command not found
/usr/src/kernel-source-2.6.8/scripts/gcc-version.sh: line 12: i486-linux-gnu-gcc: command not found
/usr/share/kernel-package/rules:1637: *** Error. I do not know where the kernel image goes to [kimagedest undefined] The usual case for this is that I could not determine which arch or subarch tihs machine belongs to. Please specify a subarch, and try again.. Stop.
I had a similar problem while compiling linux-2.6.15.6 from the original sources.
It worked after upgrading kernel-package from version 8.135 (stable) to version 10.035 (testing).
hm on howtoforge said that it isnt possible ;/
What to do? beause 2.4 is working fine but i want upgrade on 2.6 can i do that on safe way i dont wanna mess up config.
Yes it does work.
Anyway you won't mess anything. Make oldconfig is done in your new 2.6, and your 2.4 won't be touched. What could go bad is your new 2.6, but not the 2.4! If you want, make backup of /boot/vmlinuz24 (or whatever its name) , your /boot/config-2.4 and /lib/modules/kernel-2.4/ directory and /boot/grub/menu.lst
Going from 2.4 to 2.6 will add a /boot/vmlinuz-2.6, add a /boot/config26 and add a directory /lib/modules/kernel26/
So you will still keep your old files.
As it may be recommended, burn a livecd before like knoppix.
Hello. I discovered this thread recently, and my message relates to post #1: the patching of the kernel to change the resolution used during boot and have the Debian logo. I use a custom 2.6.15 kernel on Debian unstable, and all seems to have worked well. I can even switch to a console from X and be in the 0x307 resolution. I use a Go5700FX Nvidia card. This is what I observe during boot:
- *two* Debian logos appear at the top of the screen, side by side
- the resolution is what I asked for using the vga=0x307 argument
- the two logos 'fade out' after a little while, leaving the whole display to the messages.
My question is: is this the expected behavior? Why do I have 2 logos? Is it possible to update the logo without recompiling the kernel again?
OK, I haven't watched this thread for some time but now it seems I may need your help people.
After I moved to Arch I can't seem to be able to compile a clean kernel anymore.
Compiling in Gentoo was very easy :-D but anyway that's what Gentoo is all about - compile it yourself.
I get a kernel panic that it can't mount the root partition.
More details this night, I hope.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.