Prev: Gnucash segfaults
Next: If you have a hardwood floor, times have changed.
From: Andrei Popescu on 15 Mar 2010 18:10
On Mon,15.Mar.10, 17:51:01, Snood wrote:

> I know about rebooting and purging. I've done it lots before. It's
> not working that way in this case. Honestly. There's just no
> evidence that I can find that there's more than one kernel to select
> from. In fact, there's not even any evidence at all that there was
> any kernel upgrade on the three machines that had the initial OS
> installation done with the trunk kernel install option. On the other
> system, I can see that a new linux-image package was installed. But
> there's only one choice of kernels at boot time. And any attempt on
> any of these systems to remove the "obsolete" kernel results in the
> warning that the only kernel is being removed.

Please post your /boot/grub/grub.cfg

Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
From: Wolodja Wentland on 15 Mar 2010 18:20
On Mon, Mar 15, 2010 at 17:51 -0400, Snood wrote:
> Stephen Powell wrote:
> >Sam wrote:

> >First of all, you replied to me personally instead of to the list.
> >I'm putting this back on the list where it belongs.

Same happened here.

> >If you have already done the upgrade, you should have two kernel
> >image packages installed: linux-image-2.6.32-3-<arch> and
> >linux-image-2.6.32-trunk-<arch>. If you wish to purge the old
> >kernel, shutdown and reboot first. This will cause the new kernel
> >to be booted. Then you can purge the old one. aptitude will
> >not let you purge or remove a running kernel.

> I know about rebooting and purging. I've done it lots before. It's
> not working that way in this case. Honestly. There's just no
> evidence that I can find that there's more than one kernel to select
> from. In fact, there's not even any evidence at all that there was
> any kernel upgrade on the three machines that had the initial OS
> installation done with the trunk kernel install option. On the other
> system, I can see that a new linux-image package was installed. But
> there's only one choice of kernels at boot time. And any attempt on
> any of these systems to remove the "obsolete" kernel results in the
> warning that the only kernel is being removed.

It would be great, if you could provide us with the output of the
following commands:

# aptitude search ~i~n^linux-image
# apt-cache policy linux-image-2.6.32-3-686

It is quite likely that you have indeed two packages installed, namely
linux-image-2.6.32-3-686 and linux-image-2.6.32-trunk-686. The latter
is no longer present in the archives and therefore obsolete.

We can see that linux-image-2.6.32-3-686 is in testing:

$ rmadison linux-image-2.6.32-3-686
linux-image-2.6.32-3-686 | 2.6.32-9 | testing | i386
linux-image-2.6.32-3-686 | 2.6.32-9 | unstable | i386

so you should have installed it. That assumes that you have a kernel
meta-package installed, which depends on the current package that
provides the newest kernel. That meta-package is probably
linux-image-2.6-686.

It has already been pointed out in this thread that this kernel
update did, in contrast to previous updates, not select the kernel
provided by linux-image-2.6.32-3-686 as default kernel for grub. I
therefore think that the warning you get is not due to the fact that you
have only one kernel installed, but rather that you are trying to remove
the kernel *you are currently using*, because you booted into the "old"
kernel.

If you really have only one kernel package installed, I would suggest to
install the aforementioned meta-package or linux-image-2.6.32-3-686,
reboot and remove/purge linux-image-2.6.32-trunk-686. Please provide the
complete output of any command that gives errors.
--
.''`. Wolodja Wentland <wentland(a)cl.uni-heidelberg.de>
: :' :
`. `'` 4096R/CAF14EFC
`- 081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC
From: Frank McCormick on 15 Mar 2010 19:10
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 15 Mar 2010 17:39:01 -0400 (EDT)
Stephen Powell <zlinuxman(a)wowway.com> wrote:

> Sam wrote:
> > Maybe I don't understand how aptitude works for this case. From
> > everything I can see, if I remove the kernel that aptitude lists
> > as obsolete, I won't have any kernel at all.
>
> kernel, shutdown and reboot first. This will cause the new kernel
> to be booted. Then you can purge the old one. aptitude will
> not let you purge or remove a running kernel.


Uummm...yes it will. I have done it :( accidentally. What a PAIN!



- --
Frank
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJLnr0gAAoJEMEDyLTvrVhjwLYH/1cN57niwF9oHnMeOESB0zEQ
CCxt8vOno3X3FNWAg1LRjYdbYxbGyqH27w0mDrGxBspID+Ha7azZKB++BS8E3j58
orsCk4vJPUDBY7k2r8sSGHKQqLU53zDyOa8UFoS2b+5bhVckdXo/Q0qOIPk4w1bn
T0lN0RuSvldaX/A2Z2r9lsjv71tBLojON/3F5oRhUhR/pvz1TEqshoeaVGgWBiyT
GtlwSHQNMWyzCi7/tFq06StbRA/i+1ELgZwSGw1chTP7fut4JPKMsr/cQ+N0i0N3
Wr0YYXTy1XfRLgqusbSLOI5e74sRAkncS/Vfxw3IsJvZmgAiuOoiNqbxcSBVwQA=
=qZ8Q
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/20100315190504.ae9769c2.debianlist(a)videotron.ca
From: Snood on 15 Mar 2010 19:20
Andrei Popescu wrote:
> On Mon,15.Mar.10, 17:51:01, Snood wrote:
>
>> I know about rebooting and purging. I've done it lots before. It's
>> not working that way in this case. Honestly. There's just no
>> evidence that I can find that there's more than one kernel to select
>> from. In fact, there's not even any evidence at all that there was
>> any kernel upgrade on the three machines that had the initial OS
>> installation done with the trunk kernel install option. On the other
>> system, I can see that a new linux-image package was installed. But
>> there's only one choice of kernels at boot time. And any attempt on
>> any of these systems to remove the "obsolete" kernel results in the
>> warning that the only kernel is being removed.
>
> Please post your /boot/grub/grub.cfg
>
> Regards,
> Andrei

/boot/grub/grub.cfg contents below:

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set 8ccd4845-705a-4e92-98e2-7129fb7b9cda
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
set locale_dir=/boot/grub/locale
set lang=C.UTF-8
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set 8ccd4845-705a-4e92-98e2-7129fb7b9cda
insmod png
if background_image
/usr/share/images/desktop-base/moreblue-orbit-grub.png ; then
set color_normal=black/black
set color_highlight=magenta/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry "Debian GNU/Linux, with Linux 2.6.32-trunk-686" {
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set 8ccd4845-705a-4e92-98e2-7129fb7b9cda
echo Loading Linux 2.6.32-trunk-686 ...
linux /boot/vmlinuz-2.6.32-trunk-686
root=UUID=8ccd4845-705a-4e92-98e2-7129fb7b9cda ro quiet
echo Loading initial ramdisk ...
initrd /boot/initrd.img-2.6.32-trunk-686
}
menuentry "Debian GNU/Linux, with Linux 2.6.32-trunk-686 (recovery mode)" {
insmod ext2
set root=(hd0,1)
search --no-floppy --fs-uuid --set 8ccd4845-705a-4e92-98e2-7129fb7b9cda
echo Loading Linux 2.6.32-trunk-686 ...
linux /boot/vmlinuz-2.6.32-trunk-686
root=UUID=8ccd4845-705a-4e92-98e2-7129fb7b9cda ro single
echo Loading initial ramdisk ...
initrd /boot/initrd.img-2.6.32-trunk-686
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply
type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4B9EBF41.4090804(a)comcast.net
From: Celejar on 15 Mar 2010 19:20
On Mon, 15 Mar 2010 19:05:04 -0400
Frank McCormick <debianlist(a)videotron.ca> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Mon, 15 Mar 2010 17:39:01 -0400 (EDT)
> Stephen Powell <zlinuxman(a)wowway.com> wrote:

....

> > to be booted. Then you can purge the old one. aptitude will
> > not let you purge or remove a running kernel.
>
>
> Uummm...yes it will. I have done it :( accidentally. What a PAIN!

Not sure how you could have done it by accident - aptitude warns you
thus:

-----

You are running a kernel (version 2.6.34-rc1-lizzie-00005-g522dba7) and
attempting to remove the same version. This is a potentially disastrous
action. Not only will /boot/vmlinuz-2.6.34-rc1-lizzie-00005-g522dba7 be
removed, making it impossible to boot it, (you will have to take action
to change your boot loader to boot a new kernel), it will also remove
all modules under the
directory /lib/modules/2.6.34-rc1-lizzie-00005-g522dba7. Just having a
copy of the kernel image is not enough, you will have to replace the
modules too.

I repeat, this is very dangerous. If at all in doubt, answer Yes. If
you know exactly what you are doing, and are prepared to hose your
system, then answer No. Do you want to abort removal
now?

-----

Celejar
--
foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/20100315191632.33bd4fde.celejar(a)gmail.com
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Gnucash segfaults
Next: If you have a hardwood floor, times have changed.