#1 2016-04-20 06:59:50

dhalgren

Member

Registered: 2015-10-01

Posts: 152

uninstalling unwanted kernel

Hi again.

Somehow, I had installed an unwanted kernel:

bruce@debian:~$ uname -a
Linux debian 4.4.0-0.bpo.1-amd64 #1 SMP Debian 4.4.6-1~bpo8+1 (2016-03-20) x86_64 GNU/Linux

which was resulting in missing microcode messages.

I have been trying to configure and install the latest lyx release candidate, and the suggestion has been made that the 4.4.0 kernel may be the problem with configuration.

My question is: can I uninstall the 4.4.0 kernel, and its meta package, without problems arising? Is there some specific procedure I need to follow in order to do this without breaking my system (further than it already is broken, perhaps)?

Head_on_a_Stick

Member

From: London

Registered: 2015-09-29

Posts: 9,093

Website

Re: uninstalling unwanted kernel

My question is: can I uninstall the 4.4.0 kernel, and its meta package, without problems arising?

Yes, it should be fine.

dpkg(1) will throw a hissy fit if you try to remove a running kernel so as long as you're not actually using it then the removal will proceed without error.

Note that the specific package(s) will have to be removed along with metapackage.

which was resulting in missing microcode messages.

Can you explain this further please?

Just having the kernel installed should not affect running programs if it is not the kernel that booted the system.

---

Para todos todo, para nosotros nada

dhalgren

Member

Registered: 2015-10-01

Posts: 152

Re: uninstalling unwanted kernel

which was resulting in missing microcode messages.

Can you explain this further please?

Just having the kernel installed should not affect running programs if it is not the kernel that booted the system.

On booting, the first message I receive if I boot the 4.4.0 kernel is that intel microcode is missing. Apparently this is a known bug, at the moment.

I now boot using the standard jessie kernel via grub advanced options.

I agree, that the 4.4.0 kernel should not affect anything, but when I run ./configure for the new lyx release candidate, the kernel it recognises is the 4.4.0, not the kernel actually running. That seems to be what is happening, in any case.

xaos52

The Good Doctor

From: Planet of the @pes

Registered: 2015-09-30

Posts: 695

Re: uninstalling unwanted kernel

What makes you think ./configure for lyx is using kernel 4.4.0?

I presume you have downloaded the lyx rc from this site. Is that correct?

Edit:
That version compiled cleanly for me, on an up-to-date bl-rc2, with up-to-date kernel 3.16.0-4-amd64. Starts up OK too.

Hint: Run

sudo apt-get install bc
sudo apt-get build-dep lyx

before starting ./configure

dhalgren

Member

Registered: 2015-10-01

Posts: 152

Re: uninstalling unwanted kernel

What makes you think ./configure for lyx is using kernel 4.4.0?

Thelyx configure log referred only to the 4.4.0 kernel, even though I was compiling under 3.16.0-4.

I presume you have downloaded the lyx rc from this site. Is that correct?

Yes.

That version compiled cleanly for me, on an up-to-date bl-rc2, with up-to-date kernel 3.16.0-4-amd64. Starts up OK too.

I didn't mention the actual problem with lyx, as I was asking about uninstalling the kernel. However:

[1] When testing the release candidate it was not possible to open citation insets by clicking on them to open the citation dialogue box.

[2] It was not possible to insert citation via the Insert menu.

[3] This behaviour appears only under openbox (as far as I know, no other window manager causes this problem), and the release candidate performs on gnome, xfce, kde.

[4] The Lyx 2.1.x series compiles and does not replicate this problem on openbox, and I am now doing a git bisect (under instruction, as I know nothing about this procedure) to attempt to discover the commit which has given rise to this issue on openbox.

This behaviour on openbox has been confirmed by two of the developers.

Hint: Run

sudo apt-get install bc
sudo apt-get build-dep lyx

before starting ./configure

bc already installed, and all other dependencies present.