Upgrading the kernel on Debian 3.1

COKE CAN · 08-01-2005, 01:42 PM

How do I go about updating the kernel?

I was trying to follow this: http://www.debian-administration.org/articles/90 I got the 'kernel-package' and 'fakeroot'. I also downloaded the compressed kernel. After that I am in the dark.

priller · 08-01-2005, 02:43 PM

cant you just use apt-get to install a new kernel?

COKE CAN · 08-01-2005, 02:53 PM

I don't know, that's why I am asking.

COKE CAN · 08-01-2005, 03:22 PM

Wow, I feel like a bag of deusche. I should have looked up at the top of the forum.

samael26 · 08-01-2005, 04:27 PM

If you wish to go for sid (unstable), there is a 2.6.11 kernel that you can apt-get. It creates an entry

in Grub and is ready to use with no hassle. Now if you want to go to kernel.org, d/load the newest and

compile it, you can.

Freedom of choice, as they say.

cheers

priller · 08-01-2005, 04:29 PM

Quote:

Originally posted by samael26

If you wish to go for sid (unstable), there is a 2.6.11 kernel that you can apt-get. It creates an entry

Or just use the 2.6.8 kernel in sarge.

COKE CAN · 08-01-2005, 04:39 PM

I installed 2.6.8-2-686 through apt-get. When I restarted, it hangs up on thse last 3 lines:

Code:

pivot_root: no such file or directory
/bin/init: 432: can not open dev/console: no such file
Kernel panic: Attempted to kill init!

Why is this?

It ran fine on my laptop, but not on my desktop.

juanjavier_xxx · 09-16-2005, 02:01 AM

Quote:

Originally posted by COKE CAN

Code:

pivot_root: no such file or directory /bin/init: 432: can not open dev/console: no such file Kernel panic: Attempted to kill init!

Why is this?

---I have the same issue, too. I refused to open a new thread since there is one open already that touches the same question.

----How could get this fixed?

I have:

/dev/hda1: Windowze XP
/dev/hda2: Debian Testing w/2.6.8-1-k7
/dev/hda3: Debian Unstable 2.6.11-1-k7
/dev/hda4: Debian Sarge 2.6.8-1-1-k7

I can not post the menu.lst file 'cos I am not at home. I shall try this evening.

I remember I changed stupidly something regarding the drive which had the [boot] label assigned when fooling around with cfdisk.....

I should chop out my hands, I suppose

Any ideas out there??

juanjavier_xxx · 09-16-2005, 12:35 PM

Quote:

Originally posted by juanjavier_xxx
---I have the same issue, too. I refused to open a new thread since there is one open already that touches the same question.

----How could get this fixed?

Easily: learn to love your /boot/grub/menu.lst. Study it as hard as you can. In my case it was simply an (hd0,x) versus /dev/hdaX mismatch (where x -from 0 to 3- or X -from 1 to 4- is the number of any of my four partitions).

Quote:

----I can not post the menu.lst file 'cos I am not at home. I shall try this evening.

----It is not necessary, it is solved by now. Read the last paragraph.

Quote:

I remember I changed stupidly something regarding the drive which had the [boot] label assigned when fooling around with cfdisk..... I should chop out my hands, I suppose

----Cfdisk has got nothing to do with it. You can label any partition as boot....obviously a different grub menu will display depending on the menu.lst that lives on the partition marked as bootable. Different partition marked as boot....different menu displayed at boot time....unless they are all identical...