subject:"Kernel upgrade."

Hi Dan,

Thanks for your reply. We need few more information.

  1.  Debian 10 Buster is not released with Linux Kernel 5.10 ; That means We 
cant upgrade Kernel 5.10 with Debian 10? - Please confirm.
  2.
  3.  In order to upgrade Linux Kernel to 5.10 means we have to install Debian 
11 BullsEye. Please  Confirm.
  4.
  5.  What will be the impact for upgrading Debian 10 with Kernel 4.19 to 
Debian 11 with Kernel 5.10.

Thanks in advance,

Regards,
Bala

From: Dan Ritter 
Sent: Thursday, December 16, 2021 9:05 PM
To: Balasubramanian Ravuthan 
Cc: debian-user@lists.debian.org 
Subject: Re: Need Support on Debian10 Linux Kernel Upgrade

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

Balasubramanian Ravuthan wrote:
>
>  We are looking support from you on the Linux Kernel upgrade on  Debian 10.
>
> We are currently using Debian10 Buster Linux Kernel 4.19 version and trying 
> to upgrade to Debian10 Buster Linux Kernel 5.10 version. Is there any impact 
> on this upgrading.
>
> In other words, what are the things will get affected if we do kernel upgrade.

Buster was not released with a 5.10 kernel. A 5.10 kernel came
with Bullseye, Debian 11. Are you getting this from backports?

In general, Linus is pretty flexible about what kernels are
being used. The difference will be that the 5 series presumably
has fixed some old bugs, introduced some new bugs, and some
things will be faster or slower. Overall, more hardware is
supported, but if everything was working well with 4.19, then
there's no immediate reason to suspect it won't work with 5.10.

For more details, you're going to have to ask a more specific
question.

-dsr-
::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.

Re: Need Support on Debian10 Kernel Upgrade

2021-12-16 Thread Cindy Sue Causey

On 12/16/21, David Wright  wrote:
> On Thu 16 Dec 2021 at 16:12:37 (+0100), to...@tuxteam.de wrote:
>> On Thu, Dec 16, 2021 at 12:28:17PM +, Balasubramanian Ravuthan wrote:
>> > Hi Team,
>> >
>> >   We are looking support from you on the Linux Kernel upgrade on  Debian
>> > 10. Please help on this.
>>
>> This is a user's list, not a support channel.
>>
>> If you have concrete questions, you can pose them here. Chances are good
>> that some experienced users can help you. Note that this is all
>> voluntary work.
>>
>> There are companies out there offering commercial Debian support. I'm
>> sure a web search will turn up a couple of good candidates.
>
> Anyone think it ironic that a multinational IT company with a
> market capitalisation of $50 billion as of September 2021 comes
> here for help on upgrading the kernel on an old Debian system?


Sounds like something I'd say (and actually have in the past). I
didn't go to the length you did regarding research, but I did notice
it had a style similar to something else in the last week or so
something that... just didn't "sit quite right" from start to finish.

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

Re: Need Support on Debian10 Linux Kernel Upgrade

2021-12-16 Thread Dan Ritter

Balasubramanian Ravuthan wrote: 
> 
>  We are looking support from you on the Linux Kernel upgrade on  Debian 10.
> 
> We are currently using Debian10 Buster Linux Kernel 4.19 version and trying 
> to upgrade to Debian10 Buster Linux Kernel 5.10 version. Is there any impact 
> on this upgrading.
> 
> In other words, what are the things will get affected if we do kernel upgrade.

Buster was not released with a 5.10 kernel. A 5.10 kernel came
with Bullseye, Debian 11. Are you getting this from backports?

In general, Linus is pretty flexible about what kernels are
being used. The difference will be that the 5 series presumably
has fixed some old bugs, introduced some new bugs, and some
things will be faster or slower. Overall, more hardware is
supported, but if everything was working well with 4.19, then
there's no immediate reason to suspect it won't work with 5.10.

For more details, you're going to have to ask a more specific
question.

-dsr-

Re: Need Support on Debian10 Kernel Upgrade

2021-12-16 Thread David Wright

On Thu 16 Dec 2021 at 16:12:37 (+0100), to...@tuxteam.de wrote:
> On Thu, Dec 16, 2021 at 12:28:17PM +, Balasubramanian Ravuthan wrote:
> > Hi Team,
> > 
> >   We are looking support from you on the Linux Kernel upgrade on  Debian 
> > 10. Please help on this.
> 
> This is a user's list, not a support channel.
> 
> If you have concrete questions, you can pose them here. Chances are good
> that some experienced users can help you. Note that this is all
> voluntary work.
> 
> There are companies out there offering commercial Debian support. I'm
> sure a web search will turn up a couple of good candidates.

Anyone think it ironic that a multinational IT company with a
market capitalisation of $50 billion as of September 2021 comes
here for help on upgrading the kernel on an old Debian system?

Cheers,
David.

Re: Need Support on Debian10 Linux Kernel Upgrade

2021-12-16 Thread Christian Britz

On 2021-12-16 16:04 UTC+0100, Balasubramanian Ravuthan wrote:
>  We are looking support from you on the Linux Kernel upgrade on  Debian 10. 
> 
> We are currently using Debian10 Buster Linux Kernel 4.19 version and
> trying to upgrade to Debian10 Buster Linux Kernel 5.10 version. Is there
> any impact on this upgrading.
> 
> In other words, what are the things will get affected if we do kernel
> upgrade.

Kernel 5.10 for buster is available as a backport (backports.debian.org).
There should be no negative impact, but I would suggest to upgrade
a test system first. There should be some Linux expert available at HCL,
otherwise I would suggest to pay a Debian consultant.

Please give an indication that you actually read the replies on this
mailing list, otherwise I will stop trying to help you.

Regards,
Christian

Need Support on Debian10 Linux Kernel Upgrade



Hi Debian Team,

 We are looking support from you on the Linux Kernel upgrade on  Debian 10.

We are currently using Debian10 Buster Linux Kernel 4.19 version and trying to 
upgrade to Debian10 Buster Linux Kernel 5.10 version. Is there any impact on 
this upgrading.

In other words, what are the things will get affected if we do kernel upgrade.

Please help on this.

Regards,
Bala
::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.

Re: Need Support on Debian10 Kernel Upgrade

2021-12-16 Thread tomas

On Thu, Dec 16, 2021 at 12:28:17PM +, Balasubramanian Ravuthan wrote:
> Hi Team,
> 
>   We are looking support from you on the Linux Kernel upgrade on  Debian 10. 
> Please help on this.

This is a user's list, not a support channel.

If you have concrete questions, you can pose them here. Chances are good
that some experienced users can help you. Note that this is all
voluntary work.

There are companies out there offering commercial Debian support. I'm
sure a web search will turn up a couple of good candidates.

Cheers
-- 
tomás

signature.asc
Description: PGP signature

Re: Need Support on Debian10 Kernel Upgrade

2021-12-16 Thread Dan Ritter

Balasubramanian Ravuthan wrote: 
> Hi Debian Team,
> 
>   We are looking support from you on the Linux Kernel upgrade on  Debian 10. 
> Please help on this.
> 

sudo apt update && sudo apt upgrade

Consider a dist-upgrade to Debian 11.

-dsr-

Re: Need Support on Debian10 Kernel Upgrade

2021-12-16 Thread Christian Britz

On 2021-12-16 13:28 UTC+0100, Balasubramanian Ravuthan wrote:
> Hi Team,
> 
>   We are looking support from you on the Linux Kernel upgrade on  Debian
> 10. Please help on this.

There is no "Team" who will support you, we are all users who support
each other. Paid support is available elsewhere.

What is you specific issue? What do you want to do?

Regards,
Christian

Need Support on Debian10 Kernel Upgrade

Hi Team,

  We are looking support from you on the Linux Kernel upgrade on  Debian 10. 
Please help on this.

Regards,
Bala
::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.

Need Support on Debian10 Kernel Upgrade

Hi Debian Team,

  We are looking support from you on the Linux Kernel upgrade on  Debian 10. 
Please help on this.

Regards,
Bala
::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.

Re: Pending kernel upgrade

2021-04-03 Thread David BERCOT


Bonjour,

La réponse est oui...
Au bout d'un moment, ne sachant plus où chercher, j'ai ré-installé mon 
portable et tout est maintenant OK.


Merci.

David.

Le 02/04/2021 à 09:11, Sébastien NOBILI a écrit :

Bonjour,

Le 2021-03-29 13:31, David BERCOT a écrit :

Bon, j'ai rebooté et... aucun changement...
Bizarrement, au démarrage, on dirait que la config est "gélée" et ne
tient pas compte des mises à jour précédentes.


Quand tu arrives sur l'écran de Grub (menu de sélection du système à 
démarrer),
si tu édites la ligne sélectionnée (je ne me rappelle plus exactement de 
la touche,
je dirais bien "e", elle est indiquée en bas de l'écran), est-ce que ce 
que tu vois

correspond bien au noyau que tu aimerais voir démarrer (5.10.0-5-amd64) ?

Sébastien

Re: Pending kernel upgrade

2021-04-02 Thread Sébastien NOBILI


Bonjour,

Le 2021-03-29 13:31, David BERCOT a écrit :

Bon, j'ai rebooté et... aucun changement...
Bizarrement, au démarrage, on dirait que la config est "gélée" et ne
tient pas compte des mises à jour précédentes.


Quand tu arrives sur l'écran de Grub (menu de sélection du système à 
démarrer),
si tu édites la ligne sélectionnée (je ne me rappelle plus exactement de 
la touche,
je dirais bien "e", elle est indiquée en bas de l'écran), est-ce que ce 
que tu vois
correspond bien au noyau que tu aimerais voir démarrer (5.10.0-5-amd64) 
?


Sébastien

Re: Pending kernel upgrade

2021-03-30 Thread didier gaumet


Le 29/03/2021 à 13:31, David BERCOT a écrit :

Bon, j'ai rebooté et... aucun changement...
Bizarrement, au démarrage, on dirait que la config est "gélée" et ne 
tient pas compte des mises à jour précédentes.


Suis-je le seul dans ce cas ?


Une autre hypothèse: si tu as joué avec plusieurs installations de grub 
(multiboot Linux en laissant chaque distro installer son propre grub, ou 
usage un peu expérimental en spécifiant l'endroit où Grub doit 
s'installer, etc...), peut-être le fichier /boot/grub/grub.cfg n'est-il 
pas celui utilisé par grub et dans ce cas un simple grub-install avec en 
paramètre ton disque (pas une partition) pourrait suffire à faire rentre 
les choses dans l'ordre...

Re: Pending kernel upgrade

2021-03-29 Thread Luc Novales


Bonjour,


Le 29/03/2021 à 11:53, David BERCOT a écrit :
Hypothèse: si tu l'as encore ce pourrait être que lors de la mise à 
jour du noyau il y a eu un problème et que l'image initrd ne 
correspond pas au noyau utilisé.


C'est possible, sauf qu'il y a eu plusieurs mises à jour depuis qui 
n'ont rien changé. Mais sait-on jamais...


Peut-être la mise à jour de la liste de paquets ne s'est pas bien 
passée, car le noyau de backport en buster est maintenant plus récent :



Linux  5.10.0-0.bpo.3-amd64 #1 SMP Debian 5.10.13-1~bpo10+1 (2021-02-11) 
x86_64 GNU/Linux



Bonne journée,

--
*Luc Novalès*
Enseignant réseaux.
SINA/RCA
Tel : (33) (0)5 62 17 42 63
Mail : luc.nova...@enac.fr


Logo ENAC 7, ave. Édouard Belin
cedex 4
31055 Toulouse

Re: Pending kernel upgrade


Bon, j'ai rebooté et... aucun changement...
Bizarrement, au démarrage, on dirait que la config est "gélée" et ne 
tient pas compte des mises à jour précédentes.


Suis-je le seul dans ce cas ?

Merci.

David.

Le 29/03/2021 à 11:53, David BERCOT a écrit :


Le 29/03/2021 à 11:44, didier gaumet a écrit :


Que te dit la commande:
$ uname -a
?


$ uname -a
Linux TPO-DBE 5.10.0-3-amd64 #1 SMP Debian 5.10.13-1 (2021-02-06) x86_64 
GNU/Linux


Et as-tu encore le message "The currently running kernel version is 
5.10.0-3-amd64 which is not the expected kernel version 5.10.0-5-amd64" ?


Absolument, à chaque mise à jour (ce qui me paraît logique)...

Hypothèse: si tu l'as encore ce pourrait être que lors de la mise à 
jour du noyau il y a eu un problème et que l'image initrd ne 
correspond pas au noyau utilisé.


C'est possible, sauf qu'il y a eu plusieurs mises à jour depuis qui 
n'ont rien changé. Mais sait-on jamais...



Auquel cas tu peux tenter carrément une réinstallation du noyau:
# apt reinstall linux-image-5.10.0-5-amd64
ou alors mettre à jour son initrd
# update-initramfs -u -k 5.10.0-5-amd64


Je vais tenter ça...

En tout cas Grub m'a l'air à jour et selon moi tu démarres bien ce 
qu'il considère être le noyau 5.10.0-5-amd64, simplement il l'appelle 
"Debian GNU/Linux" dans le menu


Je n'ai pas l'impression...
A voir donc après mon prochain reboot.

Merci.

David.

Re: Pending kernel upgrade




Le 29/03/2021 à 11:44, didier gaumet a écrit :


Que te dit la commande:
$ uname -a
?


$ uname -a
Linux TPO-DBE 5.10.0-3-amd64 #1 SMP Debian 5.10.13-1 (2021-02-06) x86_64 
GNU/Linux


Et as-tu encore le message "The currently running kernel version is 
5.10.0-3-amd64 which is not the expected kernel version 5.10.0-5-amd64" ?


Absolument, à chaque mise à jour (ce qui me paraît logique)...

Hypothèse: si tu l'as encore ce pourrait être que lors de la mise à jour 
du noyau il y a eu un problème et que l'image initrd ne correspond pas 
au noyau utilisé.


C'est possible, sauf qu'il y a eu plusieurs mises à jour depuis qui 
n'ont rien changé. Mais sait-on jamais...


Auquel cas tu peux tenter carrément une réinstallation 
du noyau:

# apt reinstall linux-image-5.10.0-5-amd64
ou alors mettre à jour son initrd
# update-initramfs -u -k 5.10.0-5-amd64


Je vais tenter ça...

En tout cas Grub m'a l'air à jour et selon moi tu démarres bien ce qu'il 
considère être le noyau 5.10.0-5-amd64, simplement il l'appelle "Debian 
GNU/Linux" dans le menu


Je n'ai pas l'impression...
A voir donc après mon prochain reboot.

Merci.

David.

Re: Pending kernel upgrade

2021-03-29 Thread didier gaumet




Que te dit la commande:
$ uname -a
?

Et as-tu encore le message "The currently running kernel version is 
5.10.0-3-amd64 which is not the expected kernel version 5.10.0-5-amd64" ?


Hypothèse: si tu l'as encore ce pourrait être que lors de la mise à jour 
du noyau il y a eu un problème et que l'image initrd ne correspond pas 
au noyau utilisé. Auquel cas tu peux tenter carrément une réinstallation 
du noyau:

# apt reinstall linux-image-5.10.0-5-amd64
ou alors mettre à jour son initrd
# update-initramfs -u -k 5.10.0-5-amd64

En tout cas Grub m'a l'air à jour et selon moi tu démarres bien ce qu'il 
considère être le noyau 5.10.0-5-amd64, simplement il l'appelle "Debian 
GNU/Linux" dans le menu

Re: Pending kernel upgrade




Bonjour Didier,

Le 29/03/2021 à 10:01, didier gaumet a écrit :

Le 29/03/2021 à 08:06, David BERCOT a écrit :


En effet, à la racine, j'ai bien :
initrd.img -> boot/initrd.img-5.10.0-5-amd64
vmlinuz -> boot/vmlinuz-5.10.0-5-amd64

J'avoue que je ne sais pas bien où chercher...

David.


A tout hasard, tu pourrais peut-être poster ici /etc/default/grub et 
/boot/grub/grub.cfg?


Pas de souci...

/etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to 
Linux

#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

/boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by 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
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

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
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod lvm
insmod ext2
set 
root='lvmid/Uur1gw-ckhI-8fYh-2Y3J-2UtP-BDVK-3yuxWh/clNBC3-Hkyn-OXgB-ceT2-Dck0-AqVb-FMReXM'

if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root 
--hint='lvmid/Uur1gw-ckhI-8fYh-2Y3J-2UtP-BDVK-3yuxWh/clNBC3-Hkyn-OXgB-ceT2-Dck0-AqVb-FMReXM' 
 4ab6e0b2-ccca-4342-80d4-5b296f73b35f

else
  search --no-floppy --fs-uuid --set=root 
4ab6e0b2-ccca-4342-80d4-5b296f73b35f

fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=fr_FR
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class 
gnu --class os $menuentry_id_option 
'gnulinux-simple-4ab6e0b2-ccca-4342-80d4-5b296f73b35f' {

load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod lvm
insmod ext2
	set 
root='lvmid/Uur1gw-ckhI-8fYh-2Y3J-2UtP-BDVK-3yuxWh/clNBC3-Hkyn-OXgB-ceT2-Dck0-AqVb-FMReXM'

if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root 
--hint='lvmid/Uur1gw-ckhI-8fYh-2Y3J-2UtP-BDVK-3yuxWh/clNBC3-Hkyn-OXgB-ceT2-Dck0-AqVb-FMReXM' 
 4ab6e0b2-ccca-4342-80d4-5b296f73b35f

else
	  search --no-floppy --fs-uuid --set=root 
4ab6e0b2-ccca-4342-80d4-5b296f73b35f

fi
echo'Loading Linux 5.10.0-5-amd64 ...'
	linux	/boot/vmlinuz-5.10.0-5-amd64 root=/dev/mapper/TPO--DBE--vg-root 
ro  quiet

echo'Loading initial ramdisk ...'
initrd  /boot/initrd.img-5.10.0-5-amd64
}
submenu 'Advanced

Re: Pending kernel upgrade

2021-03-29 Thread didier gaumet


Le 29/03/2021 à 08:06, David BERCOT a écrit :


En effet, à la racine, j'ai bien :
initrd.img -> boot/initrd.img-5.10.0-5-amd64
vmlinuz -> boot/vmlinuz-5.10.0-5-amd64

J'avoue que je ne sais pas bien où chercher...

David.


A tout hasard, tu pourrais peut-être poster ici /etc/default/grub et 
/boot/grub/grub.cfg?

Re: Pending kernel upgrade




Bonjour,

Le 28/03/2021 à 11:22, Michel a écrit :

Le 28/03/2021 à 11:00, David BERCOT a écrit :


Hello,

Le 27/03/2021 à 15:41, yamo' a écrit :

Salut,

David BERCOT a tapoté le 27/03/2021 15:00:

Bonjour,

J'ai visiblement répondu trop vite...

En effet, au lancement des commandes grub-mkconfig et update-grub, je
vois bien la ligne "5.10.0-5".
Malheureusement, au reboot, je ne l'ai pas dans mon menu grub qui
n'affiche encore que les options 5.10.0-3 et 5.10.0-2.

Visiblement, le menu n'est pas à jour...

Y aurait-il une autre commande à passer ?



Tu n'aurais pas une partition /boot pleine?


Non, pas de souci de ce côté-là...


Sinon il y a update-grub2 mais ça devrait faire la même chose.


Oui, je me dis la même chose mais j'avais de toutes façons exécuté les 2...

David.



À tout hasard, les liens symboliques dans / ont bien été mis à jour?


En effet, à la racine, j'ai bien :
initrd.img -> boot/initrd.img-5.10.0-5-amd64
vmlinuz -> boot/vmlinuz-5.10.0-5-amd64

J'avoue que je ne sais pas bien où chercher...

David.

Re: Pending kernel upgrade

2021-03-28 Thread Michel

Le 28/03/2021 à 11:00, David BERCOT a écrit :
> 
> Hello,
> 
> Le 27/03/2021 à 15:41, yamo' a écrit :
>> Salut,
>>
>> David BERCOT a tapoté le 27/03/2021 15:00:
>>> Bonjour,
>>>
>>> J'ai visiblement répondu trop vite...
>>>
>>> En effet, au lancement des commandes grub-mkconfig et update-grub, je
>>> vois bien la ligne "5.10.0-5".
>>> Malheureusement, au reboot, je ne l'ai pas dans mon menu grub qui
>>> n'affiche encore que les options 5.10.0-3 et 5.10.0-2.
>>>
>>> Visiblement, le menu n'est pas à jour...
>>>
>>> Y aurait-il une autre commande à passer ?
>>
>>
>> Tu n'aurais pas une partition /boot pleine?
> 
> Non, pas de souci de ce côté-là...
> 
>> Sinon il y a update-grub2 mais ça devrait faire la même chose.
> 
> Oui, je me dis la même chose mais j'avais de toutes façons exécuté les 2...
> 
> David.
> 

À tout hasard, les liens symboliques dans / ont bien été mis à jour?

Re: Pending kernel upgrade

2021-03-28 Thread David BERCOT




Hello,

Le 27/03/2021 à 15:41, yamo' a écrit :

Salut,

David BERCOT a tapoté le 27/03/2021 15:00:

Bonjour,

J'ai visiblement répondu trop vite...

En effet, au lancement des commandes grub-mkconfig et update-grub, je
vois bien la ligne "5.10.0-5".
Malheureusement, au reboot, je ne l'ai pas dans mon menu grub qui
n'affiche encore que les options 5.10.0-3 et 5.10.0-2.

Visiblement, le menu n'est pas à jour...

Y aurait-il une autre commande à passer ?



Tu n'aurais pas une partition /boot pleine?


Non, pas de souci de ce côté-là...


Sinon il y a update-grub2 mais ça devrait faire la même chose.


Oui, je me dis la même chose mais j'avais de toutes façons exécuté les 2...

David.

Re: Pending kernel upgrade

2021-03-27 Thread yamo'

Salut,

David BERCOT a tapoté le 27/03/2021 15:00:
> Bonjour,
> 
> J'ai visiblement répondu trop vite...
> 
> En effet, au lancement des commandes grub-mkconfig et update-grub, je 
> vois bien la ligne "5.10.0-5".
> Malheureusement, au reboot, je ne l'ai pas dans mon menu grub qui 
> n'affiche encore que les options 5.10.0-3 et 5.10.0-2.
> 
> Visiblement, le menu n'est pas à jour...
> 
> Y aurait-il une autre commande à passer ?


Tu n'aurais pas une partition /boot pleine?

Sinon il y a update-grub2 mais ça devrait faire la même chose.


-- 
Stéphane

Re: Pending kernel upgrade

2021-03-27 Thread David BERCOT


Bonjour,

J'ai visiblement répondu trop vite...

En effet, au lancement des commandes grub-mkconfig et update-grub, je 
vois bien la ligne "5.10.0-5".
Malheureusement, au reboot, je ne l'ai pas dans mon menu grub qui 
n'affiche encore que les options 5.10.0-3 et 5.10.0-2.


Visiblement, le menu n'est pas à jour...

Y aurait-il une autre commande à passer ?

Merci.

David.

Le 26/03/2021 à 15:15, David BERCOT a écrit :

OK, c'était très simple.
Un update-grub a tout résolu...

Merci.

David.

P.S. : je ne comprends pas pourquoi ce n'était pas fait automatiquement 
mais bon...


Le 26/03/2021 à 15:10, Daniel Caillibaud a écrit :

Le 26/03/21 à 14:34, David BERCOT  a écrit :

C'est un message que j'ai déjà eu précédemment (logiquement) au moment
des mises à jour de noyau mais, après reboot, tout rentrait dans 
l'ordre.

Là, il semblerait que j'ai installé des noyaux plus récents (5.10.0-4
puis 5.10.0-5) mais qu'ils ne sont pas pris en compte, y compris après
reboot.

Vous auriez une piste ?


Une directive mise dans un /etc/grub.d/* qui imposerait une version ?

Faudrait aller voir le dernier /boot/grub/grub.cfg généré.

Éventuellement relancer `update-grub` pour le regénérer et voir si les 
nouveaux noyaux sont

bien ajoutés et pris en compte par défaut.

Au boot tu as quoi dans le menu grub ?

Re: Pending kernel upgrade

2021-03-26 Thread David BERCOT


OK, c'était très simple.
Un update-grub a tout résolu...

Merci.

David.

P.S. : je ne comprends pas pourquoi ce n'était pas fait automatiquement 
mais bon...


Le 26/03/2021 à 15:10, Daniel Caillibaud a écrit :

Le 26/03/21 à 14:34, David BERCOT  a écrit :

C'est un message que j'ai déjà eu précédemment (logiquement) au moment
des mises à jour de noyau mais, après reboot, tout rentrait dans l'ordre.
Là, il semblerait que j'ai installé des noyaux plus récents (5.10.0-4
puis 5.10.0-5) mais qu'ils ne sont pas pris en compte, y compris après
reboot.

Vous auriez une piste ?


Une directive mise dans un /etc/grub.d/* qui imposerait une version ?

Faudrait aller voir le dernier /boot/grub/grub.cfg généré.

Éventuellement relancer `update-grub` pour le regénérer et voir si les nouveaux 
noyaux sont
bien ajoutés et pris en compte par défaut.

Au boot tu as quoi dans le menu grub ?

Re: Pending kernel upgrade

2021-03-26 Thread Daniel Caillibaud

Le 26/03/21 à 14:34, David BERCOT  a écrit :
> C'est un message que j'ai déjà eu précédemment (logiquement) au moment 
> des mises à jour de noyau mais, après reboot, tout rentrait dans l'ordre.
> Là, il semblerait que j'ai installé des noyaux plus récents (5.10.0-4 
> puis 5.10.0-5) mais qu'ils ne sont pas pris en compte, y compris après 
> reboot.
> 
> Vous auriez une piste ?

Une directive mise dans un /etc/grub.d/* qui imposerait une version ?

Faudrait aller voir le dernier /boot/grub/grub.cfg généré.

Éventuellement relancer `update-grub` pour le regénérer et voir si les nouveaux 
noyaux sont
bien ajoutés et pris en compte par défaut.

Au boot tu as quoi dans le menu grub ?

-- 
Daniel

Quand l'homme aura pollué et empoisonné tous les cours d'eau, mers et
océans, Qu'il aura détruit toutes les forêts et tué tous les animaux,
Il se rendra compte qu'il ne peut manger l'argent.
I Guayazu

Pending kernel upgrade

2021-03-26 Thread David BERCOT




Bonjour,

Depuis quelque temps, j'ai un message bizarre au moment de mes mises à 
jour :
Pending kernel upgrade 
  │ Newer kernel available 
│
│ The currently running kernel version is 5.10.0-3-amd64 which is not 
the expected kernel version 5.10.0-5-amd64. 
   │
│ Restarting the system to load the new kernel will not be handled 
automatically, so you should consider rebooting.


C'est un message que j'ai déjà eu précédemment (logiquement) au moment 
des mises à jour de noyau mais, après reboot, tout rentrait dans l'ordre.
Là, il semblerait que j'ai installé des noyaux plus récents (5.10.0-4 
puis 5.10.0-5) mais qu'ils ne sont pas pris en compte, y compris après 
reboot.


Vous auriez une piste ?

Merci.

David.

Solved kernel upgrade

2019-08-21 Thread John

Total story not understood but it seems as if apt had got the new kernel
package before the notification if the security issues.  It just needed
a reboot.  I suppose I must have assumed it was a new issue

Thank you for the support which eventually led me to the solution.

==John ffitch

Re: Kernel upgrade ?

2019-08-12 Thread Andrei POPESCU

On Lu, 12 aug 19, 08:49:34, Jude DaShiell wrote:
> The other tip about kernel install selection is to install something
> like kernel-i386 or kernel-x86 without all of the long version numbers
> as suffixes in their names.

This is a good idea in general. For the amd64 architecture the package 
name would be linux-image-amd64.

> You get those kernels by default unless you
> run install with expert operational in which case you then get presented
> with all of the choices.  I expect one way or the other you have this
> covered correctly, so it could be something between you and debian pool
> is misconfigured.

More likely in this case, because it's the same package name.

@John: please post the output of:

$ apt policy linux-image-4.19.0-5-*

Kind regard,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Kernel upgrade ?

2019-08-12 Thread Jude DaShiell

The other tip about kernel install selection is to install something
like kernel-i386 or kernel-x86 without all of the long version numbers
as suffixes in their names.  You get those kernels by default unless you
run install with expert operational in which case you then get presented
with all of the choices.  I expect one way or the other you have this
covered correctly, so it could be something between you and debian pool
is misconfigured.

On Mon, 12 Aug 2019, john wrote:

> Date: Mon, 12 Aug 2019 08:23:59
> From: john 
> To: debian-user@lists.debian.org
> Subject: Re: Kernel upgrade ?
> Resent-Date: Mon, 12 Aug 2019 12:24:22 + (UTC)
> Resent-From: debian-user@lists.debian.org
>
> yes
>
> On Mon, 12 Aug 2019, Jude DaShiell wrote:
>
> > You have updated /etc/apt-get/sources.list and replaced testing with
> > buster in all locations too and this failure continues?
> >
> > On Mon, 12 Aug 2019, john wrote:
> >
> >> Date: Mon, 12 Aug 2019 07:12:39
> >> From: john 
> >> To: Holger Skidzun 
> >> Cc: debian-user@lists.debian.org
> >> Subject: Re: Kernel upgrade ?
> >> Resent-Date: Mon, 12 Aug 2019 11:13:13 + (UTC)
> >> Resent-From: debian-user@lists.debian.org
> >>
> >> No I did not; I checked that again kjust niw but sill no upgrade.
> >>
> >> On Mon, 12 Aug 2019, Holger Skidzun wrote:
> >>
> >> > Did you by chance forgot apt-get update?
> >> >
> >> > Cheers, Holger
> >> >
> >> > Mit freundlichem Gru?!
> >> >
> >> >> Le 12 ao?t 2019 ? 12:35, John  a ?crit :
> >> >>
> >> >> I received a notification from the Debian security list saying that
> >> >> there were a number of fixes to the kernel and saying I should update
> >> >> my buster system; "For the stable distribution (buster), these
> >> >> problems have been fixed in version 4.19.37-5+deb10u2."
> >> >>
> >> >> However apt does not seem to know about this and I remain running
> >> >> 4.19.37-5+deb10u1 according to uname.  What am I missing?   I did
> >> >> check /etc/apt/sources and it does include
> >> >> deb http://security.debian.org/debian-security buster/updates main
> >> contrib
> >> >> non-free
> >> >>
> >> >> Thank you for any information.
> >> >> ==John ffitch
> >> >>
> >> >
> >> >
> >>
> >
> > --
> >
> >
>
>
>

--

Re: Kernel upgrade ?

2019-08-12 Thread john

yes

On Mon, 12 Aug 2019, Jude DaShiell wrote:

You have updated /etc/apt-get/sources.list and replaced testing with
buster in all locations too and this failure continues?

On Mon, 12 Aug 2019, john wrote:

Date: Mon, 12 Aug 2019 07:12:39
From: john 
To: Holger Skidzun 
Cc: debian-user@lists.debian.org
Subject: Re: Kernel upgrade ?
Resent-Date: Mon, 12 Aug 2019 11:13:13 + (UTC)
Resent-From: debian-user@lists.debian.org

No I did not; I checked that again kjust niw but sill no upgrade.

On Mon, 12 Aug 2019, Holger Skidzun wrote:

> Did you by chance forgot apt-get update?
>
> Cheers, Holger
>
> Mit freundlichem Gru?!
>
>> Le 12 ao?t 2019 ? 12:35, John  a ?crit :
>>
>> I received a notification from the Debian security list saying that
>> there were a number of fixes to the kernel and saying I should update
>> my buster system; "For the stable distribution (buster), these
>> problems have been fixed in version 4.19.37-5+deb10u2."
>>
>> However apt does not seem to know about this and I remain running
>> 4.19.37-5+deb10u1 according to uname.  What am I missing?   I did
>> check /etc/apt/sources and it does include
>> deb http://security.debian.org/debian-security buster/updates main 
contrib

>> non-free
>>
>> Thank you for any information.
>> ==John ffitch
>>
>
>

--

Re: Kernel upgrade ?

2019-08-12 Thread Jude DaShiell

You have updated /etc/apt-get/sources.list and replaced testing with
buster in all locations too and this failure continues?

On Mon, 12 Aug 2019, john wrote:

Date: Mon, 12 Aug 2019 07:12:39
From: john 
To: Holger Skidzun 
Cc: debian-user@lists.debian.org
Subject: Re: Kernel upgrade ?
Resent-Date: Mon, 12 Aug 2019 11:13:13 + (UTC)
Resent-From: debian-user@lists.debian.org

No I did not; I checked that again kjust niw but sill no upgrade.

On Mon, 12 Aug 2019, Holger Skidzun wrote:

> Did you by chance forgot apt-get update?
>
> Cheers, Holger
>
> Mit freundlichem Gru?!
>
>> Le 12 ao?t 2019 ? 12:35, John  a ?crit :
>>
>> I received a notification from the Debian security list saying that
>> there were a number of fixes to the kernel and saying I should update
>> my buster system; "For the stable distribution (buster), these
>> problems have been fixed in version 4.19.37-5+deb10u2."
>>
>> However apt does not seem to know about this and I remain running
>> 4.19.37-5+deb10u1 according to uname.  What am I missing?   I did
>> check /etc/apt/sources and it does include
>> deb http://security.debian.org/debian-security buster/updates main contrib
>> non-free
>>
>> Thank you for any information.
>> ==John ffitch
>>
>
>

--

Re: Kernel upgrade ?

2019-08-12 Thread john


No I did not; I checked that again kjust niw but sill no upgrade.

On Mon, 12 Aug 2019, Holger Skidzun wrote:


Did you by chance forgot apt-get update?

Cheers, Holger

Mit freundlichem Gruß!


Le 12 août 2019 à 12:35, John  a écrit :

I received a notification from the Debian security list saying that
there were a number of fixes to the kernel and saying I should update
my buster system; "For the stable distribution (buster), these
problems have been fixed in version 4.19.37-5+deb10u2."

However apt does not seem to know about this and I remain running
4.19.37-5+deb10u1 according to uname.  What am I missing?   I did
check /etc/apt/sources and it does include
deb http://security.debian.org/debian-security buster/updates main contrib 
non-free

Thank you for any information.
==John ffitch

Re: Kernel upgrade ?

2019-08-12 Thread Holger Skidzun

Did you by chance forgot apt-get update?

Cheers, Holger

Mit freundlichem Gruß!

> Le 12 août 2019 à 12:35, John  a écrit :
> 
> I received a notification from the Debian security list saying that
> there were a number of fixes to the kernel and saying I should update
> my buster system; "For the stable distribution (buster), these
> problems have been fixed in version 4.19.37-5+deb10u2."
> 
> However apt does not seem to know about this and I remain running
> 4.19.37-5+deb10u1 according to uname.  What am I missing?   I did
> check /etc/apt/sources and it does include
> deb http://security.debian.org/debian-security buster/updates main contrib 
> non-free
> 
> Thank you for any information.
> ==John ffitch
>

Re: Kernel upgrade ?

2019-08-12 Thread Roberto C . Sánchez

On Mon, Aug 12, 2019 at 11:35:34AM +0100, John wrote:
> I received a notification from the Debian security list saying that
> there were a number of fixes to the kernel and saying I should update
> my buster system; "For the stable distribution (buster), these
> problems have been fixed in version 4.19.37-5+deb10u2."
> 
> However apt does not seem to know about this and I remain running
> 4.19.37-5+deb10u1 according to uname.  What am I missing?   I did
> check /etc/apt/sources and it does include
> deb http://security.debian.org/debian-security buster/updates main contrib 
> non-free
> 
That seems quite odd. Accoring to the PTS page for linux [0], that the
current version in the stable-security suite is 4.19.37-5+deb10u2.  The
buildd status page [1] shows that version as being built and installed
on all architectures.  The actual pool directory in the archive [2] also
contains the built binaries.

It seems possible that there is a misconfigured caching proxy between
you and the Debian Security CDN.  Can you try from another network or
another machine?

Regards,

-Roberto

[0] https://tracker.debian.org/pkg/linux
[1] https://buildd.debian.org/status/package.php?p=linux=buster
[2] http://security-cdn.debian.org/debian-security/pool/main/l/linux/

-- 
Roberto C. Sánchez

Kernel upgrade ?

2019-08-12 Thread John

I received a notification from the Debian security list saying that
there were a number of fixes to the kernel and saying I should update
my buster system; "For the stable distribution (buster), these
problems have been fixed in version 4.19.37-5+deb10u2."

However apt does not seem to know about this and I remain running
4.19.37-5+deb10u1 according to uname.  What am I missing?   I did
check /etc/apt/sources and it does include
deb http://security.debian.org/debian-security buster/updates main contrib 
non-free

Thank you for any information.
==John ffitch

Re: Kernel upgrade = freeze on boot (linux-image-4.16.0-2-amd64)

2018-07-05 Thread Brad Rogers

On Thu, 05 Jul 2018 20:02:15 +0200
Guillaume Clercin  wrote:

Hello Guillaume,

>I upgrade nvidia-driver to version 390.67-2 and I can boot without
>option "slab_common.usercopy_fallback".

Thanks for all your input on this, Guillaume.  If you hadn't pointed out
the workaround, I'd have been well and truly stuck.  Thanks also for
confirming the fix in the driver.

Now looking forward to 390-67-2 coming to testing.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
You don't entertain ideas you simply bore them
I Don't Like You - Stiff Little Fingers

pgpydtQBU4CbM.pgp
Description: OpenPGP digital signature

Re: Kernel upgrade = freeze on boot (linux-image-4.16.0-2-amd64)

2018-07-05 Thread Guillaume Clercin

Le jeudi 5 juillet 2018, 08:25:15 CEST Ric Moore a écrit :
> On 07/04/2018 09:12 PM, Carl Fink wrote:
> > On 07/02/2018 04:49 AM, Guillaume Clercin wrote:
> >> You need to update "/etc/default/grub" and add parameter to boot with.
> >> In this
> >> file, you need to edit the line starting with GRUB_CMDLINE_LINUX and
> >> append
> >> option: "slab_common.usercopy_fallback=y". This workaround was
> >> suggested by
> >> nvidia maintainer. Don't forget to run "update-grub" after.
> >> 
> >> nvidia-graphics-drivers (390.67-1) unstable; urgency=medium
> >> 
> >>For using the NVIDIA driver on Linux 4.16.16-1 or newer, the following
> >>kernel boot option may be needed as a workaround for #901919:
> >>  slab_common.usercopy_fallback=y
> >>See https://bugs.debian.org/901919 for details.
> >> 
> >>   -- Andreas Beckmann   Thu, 28 Jun 2018 12:32:19 +0200
> >> 
> >> This workaround works fine for me. Currently, I'm using nvidia-driver
> >> (390.67-1) and Linux (4.16.0-2-amd64).
> > 
> > I am late in saying it, but thank you, Guillaume.
> > 
> > This also worked for me.
> 
> Worked for me too!! THANKS!!! Ric

I upgrade nvidia-driver to version 390.67-2 and I can boot without option  
"slab_common.usercopy_fallback".


nvidia-graphics-drivers (390.67-2) unstable; urgency=high

  * Add kmem_cache_create_usercopy.patch from Red Hat, fixing "Bad or missing
usercopy whitelist? Kernel memory exposure attempt detected from SLUB
object 'nvidia_stack_cache'" on Linux kernels that have disabled
CONFIG_HARDENED_USERCOPY_FALLBACK (i.e. linux-image-4.16.0-2-* or newer).
(Closes: #901919)

 -- Andreas Beckmann   Thu, 05 Jul 2018 02:01:31 +0200


-- 
Guillaume Clercin

signature.asc
Description: This is a digitally signed message part.

Re: Kernel upgrade = freeze on boot (linux-image-4.16.0-2-amd64)

2018-07-05 Thread Ric Moore


On 07/04/2018 09:12 PM, Carl Fink wrote:

On 07/02/2018 04:49 AM, Guillaume Clercin wrote:
You need to update "/etc/default/grub" and add parameter to boot with. 
In this
file, you need to edit the line starting with GRUB_CMDLINE_LINUX and 
append
option: "slab_common.usercopy_fallback=y". This workaround was 
suggested by

nvidia maintainer. Don't forget to run "update-grub" after.

nvidia-graphics-drivers (390.67-1) unstable; urgency=medium

   For using the NVIDIA driver on Linux 4.16.16-1 or newer, the following
   kernel boot option may be needed as a workaround for #901919:
 slab_common.usercopy_fallback=y
   See https://bugs.debian.org/901919 for details.

  -- Andreas Beckmann   Thu, 28 Jun 2018 12:32:19 +0200

This workaround works fine for me. Currently, I'm using nvidia-driver
(390.67-1) and Linux (4.16.0-2-amd64).

I am late in saying it, but thank you, Guillaume.

This also worked for me.


Worked for me too!! THANKS!!! Ric


--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html

Re: Kernel upgrade = freeze on boot (linux-image-4.16.0-2-amd64)

2018-07-04 Thread Carl Fink


On 07/02/2018 04:49 AM, Guillaume Clercin wrote:

You need to update "/etc/default/grub" and add parameter to boot with. In this
file, you need to edit the line starting with GRUB_CMDLINE_LINUX and append
option: "slab_common.usercopy_fallback=y". This workaround was suggested by
nvidia maintainer. Don't forget to run "update-grub" after.

nvidia-graphics-drivers (390.67-1) unstable; urgency=medium

   For using the NVIDIA driver on Linux 4.16.16-1 or newer, the following
   kernel boot option may be needed as a workaround for #901919:
 slab_common.usercopy_fallback=y
   See https://bugs.debian.org/901919 for details.

  -- Andreas Beckmann   Thu, 28 Jun 2018 12:32:19 +0200

This workaround works fine for me. Currently, I'm using nvidia-driver
(390.67-1) and Linux (4.16.0-2-amd64).

I am late in saying it, but thank you, Guillaume.

This also worked for me.

--
Carl Fink  c...@finknetwork.com
Thinking and logic and stuff at Reasonably Literate
http://reasonablyliterate.com

Re: Kernel upgrade = freeze on boot (linux-image-4.16.0-2-amd64)

2018-07-02 Thread Brad Rogers

On Sun, 1 Jul 2018 19:06:10 -0400
Carl Fink  wrote:

Hello Carl,

>Thoughts?

Apply the fix reported by Guillaume.  I can confirm it works.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
No, he's just a w*
You Married A Tortured Genius - Wonk Unit


pgpt8grRa__ri.pgp
Description: OpenPGP digital signature

Re: Kernel upgrade = freeze on boot (linux-image-4.16.0-2-amd64)

2018-07-02 Thread Guillaume Clercin

Le lundi 2 juillet 2018, 01:06:10 CEST Carl Fink a écrit :
> So, on a Testing system, linux-image-4.16.0-2-amd64 came up in the apt
> 
> queue. I installed it and rebooted.
> My system froze on reboot. Scrolled through the boot messages on the
> console, up to X starting, then this (warning, long excerpt from syslog):
> ...
> Jul 1 18:50:09 debian-nitpicking kernel: [ 7.399065] usercopy: Kernel
> memory exposure attempt detected from SLUB object 'nvidia_stack_cache'
> (offset 11440, size 3)!
> ...
You need to update "/etc/default/grub" and add parameter to boot with. In this 
file, you need to edit the line starting with GRUB_CMDLINE_LINUX and append 
option: "slab_common.usercopy_fallback=y". This workaround was suggested by 
nvidia maintainer. Don't forget to run "update-grub" after.

nvidia-graphics-drivers (390.67-1) unstable; urgency=medium

  For using the NVIDIA driver on Linux 4.16.16-1 or newer, the following
  kernel boot option may be needed as a workaround for #901919:
slab_common.usercopy_fallback=y
  See https://bugs.debian.org/901919 for details.

 -- Andreas Beckmann   Thu, 28 Jun 2018 12:32:19 +0200

This workaround works fine for me. Currently, I'm using nvidia-driver 
(390.67-1) and Linux (4.16.0-2-amd64).

Guillaume Clercin

signature.asc
Description: This is a digitally signed message part.

Re: Kernel upgrade = freeze on boot (linux-image-4.16.0-2-amd64)

2018-07-02 Thread Brad Rogers

On Sun, 1 Jul 2018 19:06:10 -0400
Carl Fink  wrote:

Hello Carl,

>Multiple reboots give the same behavior, never
>giving me either a console or X prompt.

Same here.  Discovered by my wife when she turned the computer on this
morning.  I haven't removed .0.2, simply manually selected the .0.1
kernel.

TBH, I expect an update fairly soon given the fatal nature of this bug.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Save me from everybody else
Prisoners - Judgement Centre

pgpR6976by4rC.pgp
Description: OpenPGP digital signature

Kernel upgrade = freeze on boot (linux-image-4.16.0-2-amd64)

2018-07-01 Thread Carl Fink


So, on a Testing system, linux-image-4.16.0-2-amd64 came up in the apt

queue. I installed it and rebooted.
My system froze on reboot. Scrolled through the boot messages on the
console, up to X starting, then this (warning, long excerpt from syslog):
Jul 1 18:50:08 debian-nitpicking kernel: [ 6.862360] caller 
_nv001169rm+0xe3/0x1d0 [nvidia] mapping multiple BARs
Jul 1 18:50:09 debian-nitpicking colord[846]: failed to get session [pid 
728]: No data available
Jul 1 18:50:09 debian-nitpicking kernel: [ 7.237707] nvidia-modeset: 
Allocated GPU:0 (GPU-5f445880-4fd7-5bb8-5709-1ba476256ce5) @ 
PCI::01:00.0
Jul 1 18:50:09 debian-nitpicking colord[846]: failed to get session [pid 
728]: No data available
Jul 1 18:50:09 debian-nitpicking colord[846]: failed to get session [pid 
728]: No data available
Jul 1 18:50:09 debian-nitpicking colord[846]: failed to get session [pid 
728]: No data available
Jul 1 18:50:09 debian-nitpicking kernel: [ 7.399065] usercopy: Kernel 
memory exposure attempt detected from SLUB object 'nvidia_stack_cache' 
(offset 11440, size 3)!
Jul 1 18:50:09 debian-nitpicking kernel: [ 7.399077] [ cut 
here ]
Jul 1 18:50:09 debian-nitpicking kernel: [ 7.399077] kernel BUG at 
/build/linux-uwVqDp/linux-4.16.16/mm/usercopy.c:100!
Jul 1 18:50:09 debian-nitpicking kernel: [ 7.399084] invalid opcode: 
 [#1] SMP NOPTI
Jul 1 18:50:09 debian-nitpicking kernel: [ 7.399085] Modules linked in: 
appletalk ax25 ipx(C) p8023 p8022 psnap llc pci_stub vboxpci(O) 
vboxnetadp(O) vboxnetflt(O) vboxdrv(O) cpufreq_powersave 
cpufreq_conservative cpufreq_userspace binfmt_misc arc4 rt2800usb 
rt2x00usb rt2800lib rt2x00lib mac80211 edac_mce_amd joydev wmi_bmof 
cfg80211 snd_hda_codec_hdmi crc_ccitt rfkill kvm_amd ccp rng_core evdev 
kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
serio_raw fam15h_power pcspkr k10temp sg sp5100_tco shpchp acpi_cpufreq 
wmi button nvidia_drm(PO) drm_kms_helper drm nvidia_modeset(PO) 
nvidia(PO) snd_hda_codec_realtek snd_hda_codec_generic ipmi_devintf 
ipmi_msghandler snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore parport_pc 
ppdev lp parport ip_tables x_tables autofs4 ext4
Jul 1 18:50:09 debian-nitpicking kernel: [ 7.399122] crc16 mbcachJul 1 
18:50:08 debian-nitpicking kernel: [ 6.862360] caller 
_nv001169rm+0xe3/0x1d0 [nvidia] mapping multiple BARs
Jul 1 18:50:09 debian-nitpicking colord[846]: failed to get session [pid 
728]: No data available
Jul 1 18:50:09 debian-nitpicking kernel: [ 7.237707] nvidia-modeset: 
Allocated GPU:0 (GPU-5f445880-4fd7-5bb8-5709-1ba476256ce5) @ 
PCI::01:00.0
Jul 1 18:50:09 debian-nitpicking colord[846]: failed to get session [pid 
728]: No data available
Jul 1 18:50:09 debian-nitpicking colord[846]: failed to get session [pid 
728]: No data available
Jul 1 18:50:09 debian-nitpicking colord[846]: failed to get session [pid 
728]: No data available
Jul 1 18:50:09 debian-nitpicking kernel: [ 7.399065] usercopy: Kernel 
memory exposure attempt detected from SLUB object 'nvidia_stack_cache' 
(offset 11440, size 3)!
Jul 1 18:50:09 debian-nitpicking kernel: [ 7.399077] [ cut 
here ]
Jul 1 18:50:09 debian-nitpicking kernel: [ 7.399077] kernel BUG at 
/build/linux-uwVqDp/linux-4.16.16/mm/usercopy.c:100!
Jul 1 18:50:09 debian-nitpicking kernel: [ 7.399084] invalid opcode: 
 [#1] SMP NOPTI
Jul 1 18:50:09 debian-nitpicking kernel: [ 7.399085] Modules linked in: 
appletalk ax25 ipx(C) p8023 p8022 psnap llc pci_stub vboxpci(O) 
vboxnetadp(O) vboxnetflt(O) vboxdrv(O) cpufreq_powersave 
cpufreq_conservative cpufreq_userspace binfmt_misc arc4 rt2800usb 
rt2x00usb rt2800lib rt2x00lib mac80211 edac_mce_amd joydev wmi_bmof 
cfg80211 snd_hda_codec_hdmi crc_ccitt rfkill kvm_amd ccp rng_core evdev 
kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
serio_raw fam15h_power pcspkr k10temp sg sp5100_tco shpchp acpi_cpufreq 
wmi button nvidia_drm(PO) drm_kms_helper drm nvidia_modeset(PO) 
nvidia(PO) snd_hda_codec_realtek snd_hda_codec_generic ipmi_devintf 
ipmi_msghandler snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep 
snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore parport_pc 
ppdev lp parport ip_tables x_tables autofs4 ext4
Jul 1 18:50:09 debian-nitpicking kernel: [ 7.399122] crc16 mbcache jbd2 
crc32c_generic fscrypto ecb hid_generic usbhid hid sd_mod ohci_pci 
ata_generic crc32c_intel ahci libahci pata_atiixp aesni_intel aes_x86_64 
crypto_simd firewire_ohci xhci_pci cryptd glue_helper libata ohci_hcd 
ehci_pci firewire_core xhci_hcd ehci_hcd crc_itu_t r8169 i2c_piix4 
scsi_mod usbcore mii usb_common
Jul 1 18:50:09 debian-nitpicking kernel: [ 7.399141] CPU: 7 PID: 977 
Comm: Xorg Tainted: P C O 4.16.0-2-amd64 #1 Debian 4.16.16-2
Jul 1 18:50:09 debian-nitpicking kernel: [ 7.399143] Hardware name: 
Gigabyte Technology Co., Ltd. GA-970A-UD3/GA-970A-UD3, BIOS F7 10/22/2012
Jul 1 18:50:09 debian-nitpicking kernel: [

Re: grub error after kernel upgrade: invalid arch independent elf-magic

2016-07-11 Thread Pascal Hambourg


Le 11/07/2016 à 08:21, Miroslav Zaťko a écrit :

Same error here. First boot after fresh installation of Debian 8.5.0
from netinst CD finished with:

-BEGIN
error: invalid arch-independent ELF magic.
Entering rescue mode...
grub rescue>
---END


It could be that the BIOS/UEFI firmware cannot access the location on 
the disk which contains the file normal.mod.


What was on the disk before ?
What is the disk capacity ?
How did you partition it ?

Some BIOSes appear to be unable to access sectors beyond 2 TiB.

Re: grub error after kernel upgrade: invalid arch independent elf-magic

2016-07-11 Thread Miroslav Zaťko

Same error here. First boot after fresh installation of Debian 8.5.0 
from netinst CD finished with:


-BEGIN
error: invalid arch-independent ELF magic.
Entering rescue mode...
grub rescue>
---END

Any chance to fix it?

best regards,
mirec




smime.p7s
Description: S/MIME Cryptographic Signature

grub error after kernel upgrade: invalid arch independent elf-magic

2016-02-15 Thread evilphish


Greetings everyone,

today I ran into a weird problem I can't get my head around.
I run a debian 8 jessie server which was last updated around 4 weeks
ago. I did an apt-get update/upgrade today which only involved
around 20 packages, one of which was an update to the
linux-image-3.16.0-4-amd64 package.

The server has a 2009 asus mainboard which is not uefi capable. It is
booted via a 120MB bios_grub type gpt partition and the system resides
on the following 2TB ext4 partition.

Rebooting after the upgrade led to grub immediately reporting:
error: invalid arch independent ELF magic.
grub rescue>

I then tried to use the rescue prompt to get the system to boot
manually. I set the root to (hd0,gpt2) and was able to use ls to
navigate to the grub folder. Upon issuing an
insmod linux
grub immediately responded with:
error: invalid arch independent ELF magic.
I get the same error if I for example try to insmod configfile or a
couple other modules. the modules gzio, part_gpt and ext2 work fine!

I then proceeded to boot a grml rescue image from a usb stick and after
mounting the root filesystem and taking care of the sys,dev,proc
folders I chrooted into the mounted root filesystem and did a:
grub-install /dev/sda

The grub installation went fine, no errors and after a reboot I did get
back the grub boot menu.
However trying to boot the first entry which contains the 3.16 kernel
image grub responds with:
error: invalid magic number.
Loading initial ramdisk...
error: you need to lead the kernel first

If I try to boot the old 3.2 kernel which I still had on that root
filesystem instead I can boot the system just fine. 

I can repeat this behaviour as many times as I want. Doing a
grub-install from my booted system leads to the invalid arch message
and no way to boot anything. Booting a rescue disk and doing another
grub-install gets my system back to the grub menu and I can at least
boot the old 3.2 kernel. rinse repeat.

After spending more than 10 hours so far on the issue I still don't
know what exactly is causing this behaviour. It can't really be an
uefi issue as this mainboard is not uefi capable. It has been
running fine in legacy gpt mode since 2009.

Also I am usure as to what the arch independent elf-magic error message
means. And is that the same "magic" as the "invalid magic number"
message I can achieve the other way?

So, help me please, since I am running out of things to try.

Best regards
Alexander M. Heuer


signature.asc
Description: PGP signature

Re: kernel upgrade in squeeze; was Re: TP-link TL-WN722N with Squeeze

2014-08-14 Thread Andrei POPESCU

On Mi, 13 aug 14, 17:13:24, pe...@easthope.ca wrote:
 * From: Andrei POPESCU andreimpope...@gmail.com
 * Date: Wed, 13 Aug 2014 08:32:32 +0300
  ... complete output from running apt-get ...
 
 root@armada:/home/peter# apt-get install linux-image-2.6-686-pae
... 
 root@armada:/home/peter# apt-get install linux-image-3.2.0-0.bpo.4-686-pae

I think you're missing '-t squeeze-backports' as per
http://backports.debian.org/Instructions/#index3h2

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

kernel upgrade in squeeze; was Re: TP-link TL-WN722N with Squeeze

2014-08-13 Thread peter

*   From: Andrei POPESCU andreimpope...@gmail.com
*   Date: Wed, 13 Aug 2014 08:32:32 +0300
 ... complete output from running apt-get ...

root@armada:/home/peter# apt-get install linux-image-2.6-686-pae
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 linux-image-2.6-686-pae : Depends: linux-image-686-pae but it is not going to 
be installed
E: Broken packages
root@armada:/home/peter# 

2.6.32 is already running and was reinstalled since the original installation.  
The preceding makes no sense.

root@armada:/home/peter# apt-get install linux-image-3.2.0-0.bpo.4-686-pae
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 linux-image-3.2.0-0.bpo.4-686-pae : Depends: linux-base (= 3~) but 
2.6.32-48squeeze6 is to be installed
 Recommends: firmware-linux-free (= 3~) 
but 2.6.32-48squeeze6 is to be installed
 Breaks: initramfs-tools ( 0.99~) but 
0.98.8 is to be installed
E: Broken packages
root@armada:/home/peter# 

 What does this have to do with the TP-Link in the subject?

The driver for the Atheros AR9170 chipset in the TP-Link isn't working 
with the 2.6.32 kernel; upgrade seemed a reasonable approach.  For the 
subject, my train of thought went off the rails.

Thanks,... Peter



-- 
123456789 123456789 123456789 123456789 123456789 123456789 123456789 12
Tel +1 360 639 0202  http://carnot.yi.org/  Bcc: peter at easthope. ca


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/E1XHifU-W6-KN@armada.invalid

Re: Sound stopped working after kernel upgrade from 3.2 to 3.14

2014-07-07 Thread Cindy-Sue Causey

On 7/6/14, Weydson Lima weys...@gmail.com wrote:
On 7/5/14, B lazyvi...@gmx.com wrote:
Try to add a file in /etc/modprobe.d (eg: NAUGHTY_INTEL_SND.conf)
with a line in: options snd-hda-intel index=-2 (or whatever name
is your module's name, YMMV) and reboot.

What should the file name be? These are the files I have under modprobe.d:

alsa-base-blacklist.conf
alsa-base.conf
dkms.conf
fbdev-blacklist.conf
fglrx-blacklists-radeon.conf
radeon-kms.conf

Putting my foot in my mouth here until B can answer you.. *I
THINK* B is saying create your own file then add that line that
was suggested. Name the file whatever you want so it stands out to you
as being created by you, but just make sure the file ends in .conf so
the system notices it.

*I THINK* :)

I've done something like that along the way in playing with different
setups is why it clicked that might be what they mean..

Cindy

PS Please bottom post when you reply to people. I just had to do
some fancy footwork to get this to kinda sorta mesh for the
convenience of others reading it later one.. In case you've never
heard the term, bottom posting means to simply type your responses
UNDER the writing you're answering.. It helps people follow the
sequential train of thought in a conversation.. :)

--
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/cao1p-kcnzz7rmfr-_u67vo0et2z+uarvwvbfooyi6deqswm...@mail.gmail.com

Re: Sound stopped working after kernel upgrade from 3.2 to 3.14

2014-07-06 Thread Weydson Lima

What should the file name be? These are the files I have under modprobe.d:

alsa-base-blacklist.conf
alsa-base.conf
dkms.conf
fbdev-blacklist.conf
fglrx-blacklists-radeon.conf
radeon-kms.conf

I checked the alsa-base.conf and it had those lines:

options bt87x index=-2
options cx88_alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2




Weydson Lima
http://www.raisenllc.com
Web Development/Design Consulting in Los Angeles, CA



On Sat, Jul 5, 2014 at 9:19 PM, Weydson Lima weys...@gmail.com wrote:

 I have just upgraded the kernel on my Debian box from 3.2 to 3.14 for the
 first time and I have no sound on X anymore. How can I troubleshoot this
 issue?

 I do see the snd_hda_intel module being loaded, but I don't know what else
 I can do to solve this.

 Thank you

Sound stopped working after kernel upgrade from 3.2 to 3.14

2014-07-05 Thread Weydson Lima

I have just upgraded the kernel on my Debian box from 3.2 to 3.14 for the
first time and I have no sound on X anymore. How can I troubleshoot this
issue?

I do see the snd_hda_intel module being loaded, but I don't know what else
I can do to solve this.

Thank you

Re: Sound stopped working after kernel upgrade from 3.2 to 3.14

2014-07-05 Thread Bzzzz

On Sat, 5 Jul 2014 21:19:39 -0600
Weydson Lima weys...@gmail.com wrote:

 I have just upgraded the kernel on my Debian box from 3.2 to 3.14
 for the first time and I have no sound on X anymore. How can I
 troubleshoot this issue?
 
 I do see the snd_hda_intel module being loaded, but I don't know
 what else I can do to solve this.

This is usually because you have 2 drivers, the intel and
the real one (most of the time a realtek); so, your real
audio (rtl) might have become the 2nd audio card.

Try to add a file in /etc/modprobe.d (eg: NAUGHTY_INTEL_SND.conf)
with a line in: options snd-hda-intel index=-2 (or whatever name
is your module's name, YMMV) and reboot.

-- 
Lawrence Radiation Laboratory keeps all its data in an old gray
trunk.


signature.asc
Description: PGP signature

Re: kernel upgrade

2014-04-01 Thread Brad Rogers

On Mon, 31 Mar 2014 18:51:59 -0400
Stephen Allen marathon.duran...@gmail.com wrote:

Hello Stephen,

better although slower. At one time it was the go to, but since I've
gathered that apt-get has been improved.

Also, IIRC, mixing aptitude, apt-get  Synaptic for upgrades and
package installation, was considered a bad idea.  Whether that's still
the case, IDK.  However, (very) occasionally I can't use Synaptic, so
use apt-get at those times.

I've tried aptitude in the past, but just couldn't get on with it.   I
may re-visit it when I buy a new computer.  That's some time off though,
as the one I currently use is absolutely fine for my needs.

-- 
 Regards  _
 / )   The blindingly obvious is
/ _)radnever immediately apparent
Success defined by acquisition stinks
Money is Not Our God -  Killing Joke


signature.asc
Description: PGP signature

Re: kernel upgrade

2014-04-01 Thread Stephen Allen

On Tue, Apr 01, 2014 at 11:38:54AM +0100, Brad Rogers wrote:
 On Mon, 31 Mar 2014 18:51:59 -0400
 Stephen Allen marathon.duran...@gmail.com wrote:
 
 Hello Stephen,
 
 better although slower. At one time it was the go to, but since I've
 gathered that apt-get has been improved.
 
 Also, IIRC, mixing aptitude, apt-get  Synaptic for upgrades and
 package installation, was considered a bad idea.  Whether that's still
 the case, IDK.  However, (very) occasionally I can't use Synaptic, so
 use apt-get at those times.

No they all use apt - there is no issue with using all 3.
 
 I've tried aptitude in the past, but just couldn't get on with it.   I
 may re-visit it when I buy a new computer.  That's some time off though,
 as the one I currently use is absolutely fine for my needs.

Fair enough.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140402012021.GC11778@Jessie

Re: kernel upgrade

2014-03-31 Thread Andrei POPESCU

On Du, 30 mar 14, 10:57:37, Brad Rogers wrote:
 On Sun, 30 Mar 2014 10:42:52 +0200
 Nemeth Gyorgy fri...@freemail.hu wrote:
 
 Hello Nemeth,
 
 Are you sure?
 When the kernel version number changes, the
 linux-image-versionnumber-amd64.deb will be a new package.
 
 Yes.  Stephen said ..assuming of course the meta package is
 installed.  He didn't write that without reason.

The meta package is upgrade, but the actual linux-image-version 
package is not. Without dist-upgrade apt will just hold the meta package 
back, because it can't be upgraded without installing a new package.

You might be thinking of 'aptitude safe-upgrade' which does indeed 
install new dependencies.

Hope this explains,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt


signature.asc
Description: Digital signature

Re: kernel upgrade

2014-03-31 Thread Nemeth Gyorgy

2014-03-30 14:59 keltezéssel, Stephen Allen írta:

 Are you sure?
 When the kernel version number changes, the
 linux-image-versionnumber-amd64.deb will be a new package.

 Plain apt-get upgrade upgrades the installed packages only and does not
 install new package. But in this case the linux-image- is a new
 package so upgrade will not install it.
 
 What Brad said  :)
 
 
... was not correct... :)

-- 
--- Friczy ---
'Death is not a bug, it's a feature'


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5339a9e7.6050...@freemail.hu

Re: kernel upgrade

2014-03-31 Thread Brad Rogers

On Mon, 31 Mar 2014 19:46:15 +0200
Nemeth Gyorgy fri...@freemail.hu wrote:

Hello Nemeth,

... was not correct... :)

For my set of circumstances, it is.  However, I neglected to take proper
note of yours.  You're using apt-get (etc.) and I tend to use Synaptic.
Clearly, behaviour is different in each case.

Mea Culpa.

With the meta-package installed on my system, Synaptic will pull in and
install the latest kernel, and run grub-config to update the boot
loader.  This result in making the new kernel the default, and demoting
an other kernel(s) installed.  Once I'm happy that the upgraded kernel
works as required, I can delete the old kernel(s), if I wish.  I usually
keep one older kernel available, 'just in case'.

-- 
 Regards  _
 / )   The blindingly obvious is
/ _)radnever immediately apparent
It's becoming an obsession
Teenage Depression - Eddie  The Hot Rods


signature.asc
Description: PGP signature

Re: kernel upgrade

2014-03-31 Thread Nemeth Gyorgy

2014-03-31 20:07 keltezéssel, Brad Rogers írta:
 For my set of circumstances, it is.  However, I neglected to take proper
 note of yours.  You're using apt-get (etc.) and I tend to use Synaptic.
 Clearly, behaviour is different in each case.
 
 Mea Culpa.
 
 With the meta-package installed on my system, Synaptic will pull in and
 install the latest kernel, and run grub-config to update the boot
 loader.  This result in making the new kernel the default, and demoting
 an other kernel(s) installed.  Once I'm happy that the upgraded kernel
 works as required, I can delete the old kernel(s), if I wish.  I usually
 keep one older kernel available, 'just in case'.

I have some machines which I administer remotely and some of them don't
have GUI at all. Synaptic is not an option for me. Moreover, apt-get is
faster :)

-- 
--- Friczy ---
'Death is not a bug, it's a feature'


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5339c3f8.3080...@freemail.hu

Re: kernel upgrade

2014-03-31 Thread Stephen Allen

On Mon, Mar 31, 2014 at 07:46:15PM +0200, Nemeth Gyorgy wrote:
 2014-03-30 14:59 keltezéssel, Stephen Allen írta:
 
  Are you sure?
  When the kernel version number changes, the
  linux-image-versionnumber-amd64.deb will be a new package.
 
  Plain apt-get upgrade upgrades the installed packages only and does not
  install new package. But in this case the linux-image- is a new
  package so upgrade will not install it.
  
  What Brad said  :)
  
  
 ... was not correct... :)

Well, I use aptitude so yes it was. Like Brad didn't notice you were
using apt-get, but I wasn't following the entire thread.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140331224855.GB27590@Jessie

Re: kernel upgrade

2014-03-31 Thread Stephen Allen

On Mon, Mar 31, 2014 at 09:37:28PM +0200, Nemeth Gyorgy wrote:
 2014-03-31 20:07 keltezéssel, Brad Rogers írta:
  For my set of circumstances, it is.  However, I neglected to take proper
  note of yours.  You're using apt-get (etc.) and I tend to use Synaptic.
  Clearly, behaviour is different in each case.
  
  Mea Culpa.
  
  With the meta-package installed on my system, Synaptic will pull in and
  install the latest kernel, and run grub-config to update the boot
  loader.  This result in making the new kernel the default, and demoting
  an other kernel(s) installed.  Once I'm happy that the upgraded kernel
  works as required, I can delete the old kernel(s), if I wish.  I usually
  keep one older kernel available, 'just in case'.
 
 I have some machines which I administer remotely and some of them don't
 have GUI at all. Synaptic is not an option for me. Moreover, apt-get is
 faster :)

And I use aptitude from a terminal. Apt-get is useful when a lot of
packages need to be installed, otherwise aptitude has some features that
I'm more used to like 'safe-upgrade' and seems to work dependencies
better although slower. At one time it was the go to, but since I've
gathered that apt-get has been improved.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140331225159.GC27590@Jessie

Re: kernel upgrade

2014-03-30 Thread Nemeth Gyorgy

2014-03-29 22:29 keltezéssel, Stephen Allen írta:
 Do you have linux-image-amd64 installed? If not, install it. It always
 depends on the latest kernel so if there is a newer kernel, it will be
 installed automatically (if you do dist-upgrade).

 
 Actually a 'dist-upgrade' isn't necessary, plain old 'upgrade' will
 install the latest kernel for the applicable distro assuming of course
 that the meta package is installed.

Are you sure?
When the kernel version number changes, the
linux-image-versionnumber-amd64.deb will be a new package.

Plain apt-get upgrade upgrades the installed packages only and does not
install new package. But in this case the linux-image- is a new
package so upgrade will not install it.

-- 
--- Friczy ---
'Death is not a bug, it's a feature'


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5337d90c.2050...@freemail.hu

Re: kernel upgrade

2014-03-30 Thread Brad Rogers

On Sun, 30 Mar 2014 10:42:52 +0200
Nemeth Gyorgy fri...@freemail.hu wrote:

Hello Nemeth,

Are you sure?
When the kernel version number changes, the
linux-image-versionnumber-amd64.deb will be a new package.

Yes.  Stephen said ..assuming of course the meta package is
installed.  He didn't write that without reason.

-- 
 Regards  _
 / )   The blindingly obvious is
/ _)radnever immediately apparent
I don't believe you have to be an idiot to get somewhere these days
Bombsite Boy - The Adverts


signature.asc
Description: PGP signature

Re: kernel upgrade

2014-03-30 Thread Stephen Allen

On Sun, Mar 30, 2014 at 10:42:52AM +0200, Nemeth Gyorgy wrote:
 2014-03-29 22:29 keltezéssel, Stephen Allen írta:
  Do you have linux-image-amd64 installed? If not, install it. It always
  depends on the latest kernel so if there is a newer kernel, it will be
  installed automatically (if you do dist-upgrade).
 
  
  Actually a 'dist-upgrade' isn't necessary, plain old 'upgrade' will
  install the latest kernel for the applicable distro assuming of course
  that the meta package is installed.
 
 Are you sure?
 When the kernel version number changes, the
 linux-image-versionnumber-amd64.deb will be a new package.
 
 Plain apt-get upgrade upgrades the installed packages only and does not
 install new package. But in this case the linux-image- is a new
 package so upgrade will not install it.

What Brad said  :)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140330125937.GA12861@Jessie

kernel upgrade

2014-03-29 Thread François Patte

Bonjour,


Since I installed debian sid (august 2013), I regularly made upgrade,
but the kernel doesn't appear to be upgraded. Why? I am running
3.2.0-4-amd64 kernel.

Do I have to upgrade to 3.13-1-amd64? If yes how to proceed?


Thanks.
-- 
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 8394 5849
http://www.math-info.univ-paris5.fr/~patte



signature.asc
Description: OpenPGP digital signature

Re: kernel upgrade

2014-03-29 Thread Ralf Mardorf

On Sat, 2014-03-29 at 14:31 +0100, François Patte wrote:
 Bonjour,
 
 
 Since I installed debian sid (august 2013), I regularly made upgrade,
 but the kernel doesn't appear to be upgraded. Why? I am running
 3.2.0-4-amd64 kernel.
 
 Do I have to upgrade to 3.13-1-amd64? If yes how to proceed?

I'm not aware about the Debian policy regarding to what kernel version,
does replace what other kernel version.

[rocketmouse@archlinux ~]$ ls -hAl /mnt/debi386/boot/vm*
-rw-r--r-- 1 root root 2.7M Feb  8 06:20 
/mnt/debi386/boot/vmlinuz-3.12-0.bpo.1-rt-686-pae
-rw-r--r-- 1 root root 2.6M Feb  2 02:06 
/mnt/debi386/boot/vmlinuz-3.2.0-4-rt-686-pae
-rw-r--r-- 1 root root 2.8M Mar 21 10:57 
/mnt/debi386/boot/vmlinuz-3.8.13.14-rt30-pae-rocketmouse-1
-rw-r--r-- 1 root root 2.8M Jan 27 16:44 
/mnt/debi386/boot/vmlinuz-3.8.13-rt14-pae-rocketmouse-2

The kernels without the extension rocketmouse are from the Debian
repositories and for me it's good, that 3.12...rt doesn't replace
3.2...rt, since all kernels  3.8...rt lock my machine. I build the
3.8...rts by myself.

Use Synaptic, (force) install 3.13-1-amd64, test it and assumed it's ok,
purge/completely remove 3.2.0-4-amd64. Take a look at /lib/modules/,
perhaps a hook build modules by dkms that aren't removed, if so remove
them by CLI, IOW rm -r the unneeded dir.




-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1396101623.612.23.camel@archlinux

Re: kernel upgrade

2014-03-29 Thread Brad Rogers

On Sat, 29 Mar 2014 14:31:03 +0100
François Patte francois.pa...@mi.parisdescartes.fr wrote:

Hello François,

Since I installed debian sid (august 2013), I regularly made upgrade,
but the kernel doesn't appear to be upgraded. Why? I am running

Unless an additional package is installed, kernels are exempt from
upgrade.

Do I have to upgrade to 3.13-1-amd64? If yes how to proceed?

Either install the latest kernel manually or, if you prefer to have
kernels handled by your usual update routine, install linux-image-amd64,
which depends on the latest kernel version.

NOTE:  Old kernels are *not* removed during the upgrade process.  This
is intentional.  Once you're happy with the new kernel upgrade, you can
manually remove the old one.

-- 
 Regards  _
 / )   The blindingly obvious is
/ _)radnever immediately apparent
Bet you think you're king but you're really a pawn
When You're Young - The Jam


signature.asc
Description: PGP signature

Re: kernel upgrade

2014-03-29 Thread Ralf Mardorf

On Sat, 2014-03-29 at 14:05 +, Brad Rogers wrote:
 Either install the latest kernel manually or, if you prefer to have
 kernels handled by your usual update routine, install
 linux-image-amd64, which depends on the latest kernel version.

IOW a meta package does handle upgrades. But as Brad and I already
mentioned, it can't harm to test a new kernel, before you remove the old
kernel. I always keep at least one kernel I used for a long time without
(serious) issues, IOW I at least have 2 kernels for all of my Linux
installs, a good old faithful and a new one.



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1396102864.612.28.camel@archlinux

Re: kernel upgrade

2014-03-29 Thread Nemeth Gyorgy

2014-03-29 14:31 keltezéssel, François Patte írta:

 Since I installed debian sid (august 2013), I regularly made upgrade,
 but the kernel doesn't appear to be upgraded. Why? I am running
 3.2.0-4-amd64 kernel.
 
 Do I have to upgrade to 3.13-1-amd64? If yes how to proceed?
 

Do you have linux-image-amd64 installed? If not, install it. It always
depends on the latest kernel so if there is a newer kernel, it will be
installed automatically (if you do dist-upgrade).


-- 
--- Friczy ---
'Death is not a bug, it's a feature'


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5336ebda.3010...@freemail.hu

Re: kernel upgrade

2014-03-29 Thread Stephen Allen

On Sat, Mar 29, 2014 at 04:50:50PM +0100, Nemeth Gyorgy wrote:
 2014-03-29 14:31 keltezéssel, François Patte írta:
 
  Since I installed debian sid (august 2013), I regularly made upgrade,
  but the kernel doesn't appear to be upgraded. Why? I am running
  3.2.0-4-amd64 kernel.
  
  Do I have to upgrade to 3.13-1-amd64? If yes how to proceed?
  
 
 Do you have linux-image-amd64 installed? If not, install it. It always
 depends on the latest kernel so if there is a newer kernel, it will be
 installed automatically (if you do dist-upgrade).
 

Actually a 'dist-upgrade' isn't necessary, plain old 'upgrade' will
install the latest kernel for the applicable distro assuming of course
that the meta package is installed.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140329212906.GA27273@Jessie

Re: kernel upgrade

2014-03-29 Thread Chris Bannister

On Sat, Mar 29, 2014 at 02:05:57PM +, Brad Rogers wrote:
 On Sat, 29 Mar 2014 14:31:03 +0100
 François Patte francois.pa...@mi.parisdescartes.fr wrote:
 
 Hello François,
 
 Since I installed debian sid (august 2013), I regularly made upgrade,
 but the kernel doesn't appear to be upgraded. Why? I am running
 
 Unless an additional package is installed, kernels are exempt from
 upgrade.
 
 Do I have to upgrade to 3.13-1-amd64? 

Absolutely not! If your machine is working perfectly, why risk it?

If yes how to proceed?

apt-get install package name just like any other package.

 Either install the latest kernel manually or, if you prefer to have
 kernels handled by your usual update routine, install linux-image-amd64,
 which depends on the latest kernel version.

Just to point out that there is nothing magical here. A new kernel is
treated just like any other package, dpkg/apt etc doesn't know a kernel
package from, e.g. beneath-a-steel-sky_0.0372-5_all.deb

Have a nosy at
http://www.debian.org/doc/manuals/debian-faq/ch-pkg_basics.en.html


-- 
If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing. --- Malcolm X


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140330033522.GA20599@tal

Re: kernel upgrade

2014-03-29 Thread Ralf Mardorf

On Sun, 2014-03-30 at 16:35 +1300, Chris Bannister wrote:
  Do I have to upgrade to 3.13-1-amd64? 
 
 Absolutely not! If your machine is working perfectly, why risk it?

Good point :D!

OT: We sometimes take a look to our crystal balls and we are unhappy,
when e.g. the RT patched kernels  3.8.x-rty will lock our machines ;).
IOW testing new kernels can't harm, to provide bug reports, if needed.

Anyway, never change a winning team, never change a winning team, never
change a winning team.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/1396151234.1580.25.camel@archlinux

Re: Re: RAID broken after kernel upgrade.

2013-08-02 Thread Dan Ritter

On Tue, Jul 30, 2013 at 11:46:54PM -0400, Doug wrote:
 I have already done this multiple times and nothing seems to have changed. 
 Here is a copy of mdadm.conf for your inspection.
 
 
 Does this look right? Any other ideas? Thanks for the help!

I can't tell whether the copy of mdadm.conf you presented
actually matches what's on disk. Try this:

sudo mdadm --misc --scan --detail

and compare that to your mdadm.conf.

-dsr-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130731132256.gh31...@randomstring.org

Re: RAID broken after kernel upgrade.

2013-07-30 Thread Dan Ritter

On Tue, Jul 30, 2013 at 12:01:40AM -0400, d...@ubutton.com wrote:
 After upgrading to kernel 3.9-1 from 3.2, my system will no longer
 boot. My OS is located on a RAID array, but when the system boots it
 says something along the lines of mdadm: no arrays in the
 configuration file were found and root not found. Then it enters
 busy box. Once in busy box I find that the raid array isn't
 assembled, but can easily be assembled by using mdadm --assemble
 --scan. After exiting busy box it boots normally. I'm sorry about
 the lack of actual log files here, but I will post some when I have
 some time. Any ideas? Maybe it has something to do with initramfs?
 Thanks in advance.

This suggests that you need to make sure your mdadm.conf is
valid and then rebuild your initramfs -- update-initramfs is
your friend.

-dsr-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130730153010.gb31...@randomstring.org

Re: Re: RAID broken after kernel upgrade.

2013-07-30 Thread Doug

I have already done this multiple times and nothing seems to have changed. Here 
is a copy of mdadm.conf for your inspection.

# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST Paratrix.net

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays
ARRAY /dev/md/0 metadata=1.2 name=Paratrix.net:0 
UUID=18833bc1:19156612:646c4e56:43311524
# This file was auto-generated on Mon, 27 May 2013 16:41:43 -0400
# by mkconf 3.2.5-5

# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST Paratrix.net

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays
ARRAY /dev/md/0 metadata=1.2 name=Paratrix.net:0 
UUID=18833bc1:19156612:646c4e56:43311524

# This file was auto-generated on Mon, 27 May 2013 16:41:43 -0400
# by mkconf 3.2.5-5


Does this look right? Any other ideas? Thanks for the help!

--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/a8cacf9b-1de1-403c-b3d3-b36e582a3...@ubutton.com

RAID broken after kernel upgrade.

2013-07-29 Thread doug

After upgrading to kernel 3.9-1 from 3.2, my system will no longer 
boot. My OS is located on a RAID array, but when the system boots it 
says something along the lines of mdadm: no arrays in the configuration 
file were found and root not found. Then it enters busy box. Once in 
busy box I find that the raid array isn't assembled, but can easily be 
assembled by using mdadm --assemble --scan. After exiting busy box it 
boots normally. I'm sorry about the lack of actual log files here, but I 
will post some when I have some time. Any ideas? Maybe it has something 
to do with initramfs? Thanks in advance.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/b734b68c8c23037113d9abb0fd624...@ubutton.com

Re: squeeze kernel upgrade fixes r8169 network driver?

2012-01-17 Thread Jon Dowland

On 16/01/12 21:14, Curt wrote:
 Yes, I verified in the kernel logs (/var/log/kern.log--thanks for that
 tip) : I was using 2.6.32-39 before; after the upgrade I'm using
 2.6.32-39squeeze1.

According to the changelog, there has indeed been no other changes 
between those versions.

I'm *sure* I read something about an 8139 fix on -devel relating to
stable, there was an argument about whether it was appropriate or not.
This struck me as too much of a coincidence.  However, I can't find
the thread I was thinking of, so perhaps it was this earlier change:

linux-2.6 (2.6.32-36) stable; urgency=low

r8169: Backport changes up to Linux 3.0.2 (Closes: #627704)
 - Fix support for RTL8102E and RTL8168DP
 - Add support for RTL8105E, RTL8168E and another variant of RTL8168DP
 - Add support for D-Link DGE-530T rev C1


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f154ab2.20...@debian.org



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/debian-user

squeeze kernel upgrade fixes r8169 network driver?

Got a kernel upgrade today from the security repository.  I had
previously installed the Realtek proprietary driver (r8168) for my
network card, because the kernel module in squeeze was very problematic
(frequent disconnections, diminished throughput, etc...)

(curty@einstein:~$ uname -a
Linux einstein 2.6.32-5-amd64 #1 SMP Mon Jan 9 20:49:59 UTC 2012 x86_64
GNU/Linux
curty@einstein:~$ lspci -v | grep -i ether
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06))

After the recommended reboot the network card is now using the kernel
module (r8169, though the r8168 was also loaded) and it seems to be
working fine.

Did they fix the r8169, or was it all a bad dream?

(I looked at the debian security advisory for the kernel upgrade, dated
15 January, but it says nothing about the matter).


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/slrnjh8hq2.2pd.cu...@einstein.electron.org

Re: squeeze kernel upgrade fixes r8169 network driver?

2012-01-16 Thread Jon Dowland

On Mon, Jan 16, 2012 at 03:50:39PM +, Curt wrote:
 Did they fix the r8169, or was it all a bad dream?

 (I looked at the debian security advisory for the kernel upgrade, dated
 15 January, but it says nothing about the matter).

I think a (prior) point release upgrade fixed it, not this security upgrade,
but the security upgrade is built on top of the point release.

-- 
Jon Dowland


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120116161444.GA23539@pris

Re: squeeze kernel upgrade fixes r8169 network driver?

On 2012-01-16 17:14 +0100, Jon Dowland wrote:

 On Mon, Jan 16, 2012 at 03:50:39PM +, Curt wrote:
 Did they fix the r8169, or was it all a bad dream?

 (I looked at the debian security advisory for the kernel upgrade, dated
 15 January, but it says nothing about the matter).

 I think a (prior) point release upgrade fixed it, not this security upgrade,
 but the security upgrade is built on top of the point release.

According to debian/changelog, 2.6.32-36 was the last version in which
major changes were made to r8169, and the latest Squeeze point release
already has 2.6.32-38.  But only Curt can know which version he had been
using before.

Sven


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87ty3v7f1i@turtle.gmx.de

Re: squeeze kernel upgrade fixes r8169 network driver?

On 2012-01-16, Sven Joachim svenj...@gmx.de wrote:

 I think a (prior) point release upgrade fixed it, not this security upgrade,
 but the security upgrade is built on top of the point release.

 According to debian/changelog, 2.6.32-36 was the last version in which
 major changes were made to r8169, and the latest Squeeze point release
 already has 2.6.32-38.  But only Curt can know which version he had been
 using before.

I don't know where to look to find out what kernel version I was using before.

In /var/lib/dpkg/status-old it says:

Package: linux-image-2.6-amd64
Status: install ok installed
Priority: optional
Section: kernel
Installed-Size: 48
Maintainer: Debian Kernel Team debian-ker...@lists.debian.org
Architecture: amd64
Source: linux-latest-2.6 (29)
Version: 2.6.32+29

So it makes sense, I guess.



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/slrnjh8ok1.2qa.cu...@einstein.electron.org

Re: squeeze kernel upgrade fixes r8169 network driver?

On 2012-01-16 18:46 +0100, Curt wrote:

 On 2012-01-16, Sven Joachim svenj...@gmx.de wrote:

 I think a (prior) point release upgrade fixed it, not this security upgrade,
 but the security upgrade is built on top of the point release.

 According to debian/changelog, 2.6.32-36 was the last version in which
 major changes were made to r8169, and the latest Squeeze point release
 already has 2.6.32-38.  But only Curt can know which version he had been
 using before.

 I don't know where to look to find out what kernel version I was using before.

/var/log/dpkg.log would be the best place.

 In /var/lib/dpkg/status-old it says:

 Package: linux-image-2.6-amd64

This is just a metapackage, you need to look for
linux-image-2.6.32-5-amd64 (more generally, linux-image-$(uname -r))
instead.

Sven


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87zkdn5y7q@turtle.gmx.de

Re: squeeze kernel upgrade fixes r8169 network driver?

On 2012-01-16, Sven Joachim svenj...@gmx.de wrote:

 I don't know where to look to find out what kernel version I was using 
 before.

 /var/log/dpkg.log would be the best place.

I don't have that file on my system.

 In /var/lib/dpkg/status-old it says:

 Package: linux-image-2.6-amd64

 This is just a metapackage, you need to look for
 linux-image-2.6.32-5-amd64 (more generally, linux-image-$(uname -r))
 instead.

in /var/lib/dpkg/status-old

Package: linux-image-2.6.32-5-amd64
Status: install ok unpacked
Priority: optional
Section: kernel
Installed-Size: 99268
Maintainer: Debian Kernel Team debian-ker...@lists.debian.org
Architecture: amd64
Source: linux-2.6
Version: 2.6.32-39squeeze1

Same version I'm running now, so it's imcomprehensible to me how the
upgrade fixed anything.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/slrnjh8qjr.31j.cu...@einstein.electron.org

Re: squeeze kernel upgrade fixes r8169 network driver?

On 2012-01-16 19:20 +0100, Curt wrote:

 On 2012-01-16, Sven Joachim svenj...@gmx.de wrote:

 I don't know where to look to find out what kernel version I was using 
 before.

 /var/log/dpkg.log would be the best place.

 I don't have that file on my system.

That's a bit unfortunate.  Did you deliberately turn off logging in
/etc/dpkg/dpkg.cfg ?

 In /var/lib/dpkg/status-old it says:

 Package: linux-image-2.6-amd64

 This is just a metapackage, you need to look for
 linux-image-2.6.32-5-amd64 (more generally, linux-image-$(uname -r))
 instead.

 in /var/lib/dpkg/status-old

 Package: linux-image-2.6.32-5-amd64
 Status: install ok unpacked
 Priority: optional
 Section: kernel
 Installed-Size: 99268
 Maintainer: Debian Kernel Team debian-ker...@lists.debian.org
 Architecture: amd64
 Source: linux-2.6
 Version: 2.6.32-39squeeze1

 Same version I'm running now, so it's imcomprehensible to me how the
 upgrade fixed anything.

It's expected that they are the same since every dpkg invocation
overwrites status-old, and apt usually invokes dpkg at least twice when
installing/upgrading non-essential packages.

Older versions of the dpkg status file might still be in /var/backups.

Sven


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87r4yz5w9y@turtle.gmx.de

Re: squeeze kernel upgrade fixes r8169 network driver?

On 2012-01-16, Sven Joachim svenj...@gmx.de wrote:

 /var/log/dpkg.log would be the best place.

 I don't have that file on my system.

 That's a bit unfortunate.  Did you deliberately turn off logging in
 /etc/dpkg/dpkg.cfg ?

Nope. I do have /var/dpkg.log, sorry.  Brain fart.

 It's expected that they are the same since every dpkg invocation

Then why the hell am I looking in there?

Here's the question:  I am running a vanilla squeeze system and the
kernel has just been upgraded for security reasons.  How can I find what
kernel version I was using before the upgrade?

dpkg.log says :

upgrade linux-image-2.6.32-5-amd64 2.6.32-39 2.6.32-39squeeze1

So there has been no version upgrade, apparently, and therefore the mystery
remains as to why the r8169 kernel driver works correctly now when it wasn't
working correctly before.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/slrnjh8ugs.35h.cu...@einstein.electron.org

Re: squeeze kernel upgrade fixes r8169 network driver?