Can't boot with kernel 4.13

[oshunluvr]

The current KDEneon release doesn't use 4.13 by default so I can't see how you could blame KDEneon for a change you made yourself. Remember the intent of KDEneon is to provide rapid access to KDE/Plasma/Qt upgrades, not the latest kernel. If your needs lie elsewhere, then you're right, you probably shouldn't be using KDEneon to begin with. Myself, I'm am very satisfied with a solid 16.06 LTS base with the latest Plasma 5 on tip of it. Seems to me if one were relying on Kubuntu or KDEneon for daily production work, one shouldn't be jumping on every kernel that comes down the release channel, but that's just me.

I haven't bothered to dig into why all the kernel files aren't automatically making the upgrade list because it's just not that hard to manually install a new kernel every so often, and I want the newer kernel enough to do the work. I noticed this behavior when I first tried to boot to the 4.8 or 4.10 kernel (can't remember which) and my keyboard and mouse wouldn't work. Turned out they had moved the USB kernel modules to the "tools" package and the 4.4 kernel didn't need the extra package. Seems stupid to me, like who doesn't need USB these days? But, whatever, I adjusted.

If you were interested, there will be a KDEneon 18.04 release a month or two after Kubuntu 18.04, but it will also - like the current KDEneon release - be an LTS release.

[mr_raider]

You misunderstand. I did not voluntarily install 4.13. I suggest you install the current neon release yourself.and test it in a VM.

The current neon release is based on 16.04.3 which installs the HWE stack just as Ubuntu. The kernel is provided by the linux-hwe-1604 meta package,.as opposed to Linux-generic.

Until last week HWE pointed to a 4.10 kernel, but since 4.10 is EOL Ubuntu switched it to 4.13. They accelerated the transition due to the meltdown bug. The update was pushed by Canonical.

What I don't know his if I borked the upgrade or if the dependencies changed from 4.10

Sent from my ONEPLUS A5010 using Tapatalk

[jglen490]

But only if you start with 16.04.3. If you start with 16.04.1, like I did or even 16.04.2, you will be in the 4.4.0 stream.

john@John-Desktop:/etc/NetworkManager$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.3 LTS
Release:        16.04
Codename:       xenial

john@John-Desktop:/etc/NetworkManager$ uname -r
4.4.0-109-generic

[mr_raider]

But only if you start with 16.04.3. If you start with 16.04.1, like I did or even 16.04.2, you will be in the 4.4.0 stream.

john@John-Desktop:/etc/NetworkManager$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.3 LTS
Release:        16.04
Codename:       xenial

john@John-Desktop:/etc/NetworkManager$ uname -r
4.4.0-109-generic

That's always been how the LTS point releases work. x.04.1 and below use the Ga kernel. After that it's the HWE kernel. I'm not aware of any way to download a neon iso that uses the original stack.

Sent from my ONEPLUS A5010 using Tapatalk

[joneall]

How do you update to 4.10 or 4.13 in Neon? If I just do a dist-upgrade, it leaves me at 4.4.

Is that compatible with Neon's philosophy of using the latest KDE on top of a solid LTS kernel?

[mr_raider]

How do you update to 4.10 or 4.13 in Neon? If I just do a dist-upgrade, it leaves me at 4.4.

Is that compatible with Neon's philosophy of using the latest KDE on top of a solid LTS kernel?

Neon has no philosophy for kernel management. The kernel is managed according Ubuntu LTS rules. If you installed with 4.4, you will stay on 4.4 unless you manually opt in to the HWE kernel:

https://wiki.ubuntu.com/Kernel/Rolli...nablementStack

[joneall]

How do you update to 4.10 or 4.13 in Neon? If I just do a dist-upgrade, it leaves me at 4.4.

Is that compatible with Neon's philosophy of using the latest KDE on top of a solid LTS kernel?

[oshunluvr]

Try "sudo apt install linux-image-4.13.0-32-generic". You'll probably want linux-headers..., linux-tools..., linux-hwe-tools..., and maybe linux-cloud-tools..., linux-hwe-cloud-tools... also.

4.13 works fine here.

[mr_raider]

I would have done

sudo apt install linux-generic-hwe-16.04

Sent from my ONEPLUS A5010 using Tapatalk

[GreyGeek]

I upgraded to 4.13 but my NVidia GT650M driver, nvidia-378.13 didn't give me what the original kernel did. I tried the 384 and 387 drivers with the 4.13 kernel but no joy. So, I restored my @ and @home backups and rebooted.

[vinnywright]

works OK @hear

VINNY

[joneall]

Actually, I did what mr_raider suggested and it seems to work fine now.

Still, dist-upgrade just finds new versions of 4.4, none of 4.13. Could that be because there are no new version of 4.13 beyond 4.13.0-32-generic? That would surprise me.

[mr_raider]

You are on the most recent 4.13 kernel. HWE will track the most recent 4.13 series kernel until 9 months after the release of 17.10. then it will switch to the 18.04 kernel which is probably 4.15

Sent from my ONEPLUS A5010 using Tapatalk

[joneall]

You are on the most recent 4.13 kernel. HWE will track the most recent 4.13 series kernel until 9 months after the release of 17.10. then it will switch to the 18.04 kernel which is probably 4.15

Good to know. Thanks!

[oshunluvr]

Actually, I did what mr_raider suggested and it seems to work fine now.

Still, dist-upgrade just finds new versions of 4.4, none of 4.13. Could that be because there are no new version of 4.13 beyond 4.13.0-32-generic? That would surprise me.

Yes, I see the same behavior here. What I get is an upgrade for the linux-headers package, but not for the image or additional packages. I have to manually install each new kernel version.

Once 18.04 is released, KDEneon will move to the 18.04 base so the behavior should change, so rather than complain or figuring it out, I'm just waiting.