Kernel conflict

5 respostas [Última entrada]
Piriponzolo
Desconectado
Joined: 02/19/2016

Hi to everyone.
I'm using Trisquel mini on the HP 510, and old 32 bit notebook. After a general updating and a reboot with the latest linux kernel 4.4.0-178 I had on the screen the following response by GRUB: " Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device ore file completions.
grub> _ "
I have solved with the SUPER GRUB 2 disk, but, in order to avoid this annoyance in the future, after the upgrading via terminal may I contextually remove, always via terminal, the old kernel before rebooting, or will I encounter other problems? Thank you for the attention.

Magic Banana

I am a member!

Desconectado
Joined: 07/24/2010

may I contextually remove, always via terminal, the old kernel before rebooting

That would be a bad idea: if, for some reason, the newer kernel does not boot, you could not boot the older one.

will I encounter other problems?

The problem should not have happened in the first place. It apparently deals with the generation of GRUB's configuration file. Maybe the disk is failing. Have you checked its SMART data, for instance using GNOME Disks ("gnome-disk-utility" in Trisquel's repository)?

Piriponzolo
Desconectado
Joined: 02/19/2016

I have been recently updating my old notebook HP510 and via terminal I have been removing contextually the old kernel before rebooting with the latest, without encountering problems.

jxself
Desconectado
Joined: 09/13/2010

You can, of course, remove whatever you want - it's your system. It is still a good idea to leave the old kernel there in case there's something wrong with the new one. While that may not happen very often (as you say "without encountering problems") there's always a possibility. There's no real benefit to removing the old kernel beyond saving some disk space. Whatever happened with the situation here where you ended up in the rescue mode was almost certainly not because of a "kernel conflict" as a result of 2 kernels existing on disk but something else. There wasn't enough information provided to fully diagnose it though. We know only that you ended up in the rescue shell.

Piriponzolo
Desconectado
Joined: 02/19/2016

Thank you for the reply. Gnome-disk-utility says the disk (a PATA SSD) is ok. How managing the next time the rescue shell?

Piriponzolo
Desconectado
Joined: 02/19/2016

Thank you for the reply. Gnome-disk-utility says the disk (a PATA SSD) is ok.