/srv/irclogs.ubuntu.com/2019/08/14/#ubuntu-kernel.txt

mattifling: It looks like you need to enable support for it in the Kconfig, and then build again :)02:28
=== fling is now known as bedflinger
=== bedflinger is now known as fling
h3rbzHi! I'm running Bionic, with a manual kernel selectionn (4.18, not 4.15, currently). This kernel does not get updates installed when running `apt upgrade'. Is there a way to have apt manage a non-standard linux-image version? Or, should I work around it myself? thx!12:22
h3rbzAm I right to assume that updates do work for 4.15, because it is selected by the meta-package (e.g. linux-image-generic)?12:23
tjaaltonh3rbz: 4.18 was from cosmic, which is now EOL12:38
tjaaltonif you want to stay on the hwe kernel, install linux-image-generic-hwe-18.04 which would pull 5.0 now12:39
lotuspsychjetjaalton: good news, tomreyn found booting intel_idle.max_cstate=4 fixxed my issue on 5.0.0.25 keeps working after suspend aswell12:40
tjaaltonjust a workaround then12:40
tomreynyes, a workaround12:40
lotuspsychjeyes12:40
tomreynwe read this at https://bugs.freedesktop.org/show_bug.cgi?id=10921512:42
ubot5Freedesktop bug 109215 in DRM/Intel "intermittent display on kaby lake/i915 from kernel 4.19 onwards" [Major,New]12:42
tomreyn(where OP also runs a clevo)12:42
tjaaltonbut doesn't say if it's fixed in 5.3 for him12:44
lotuspsychjei tested a 5.3 and confirmed no flickering12:44
tjaaltonbut he didn't12:44
lotuspsychjeno12:45
h3rbztjaalton: thx! I think I was not inderstanding exactly what this 'hwe' version is.12:54
h3rbzI did not consider it, jsu as with lowlatency et. al.12:54
h3rbz*just12:54
h3rbznice to have 5.x though :)12:59
h3rbzmeh.. is it true, that the cephfs kernel client does not support quota in 5.0.0?13:15
h3rbzit did not in 4.15, it did in 4.18, that's why I installed it13:15
h3rbzn/m my mistake. it works, I was just doing something stupid while testing :) thx anyway14:28
nilujehi, which paramater should I give in the cmdline to get a shell in the initrd? break=init-top doesn't seem to work16:04
tjaaltonrecovery?16:06
tjaaltonor just boot the recovery entry16:06
nilujetjaalton: the answer is for me?16:07
tjaaltonyes16:07
nilujetjaalton: you mean I should add the param "recovery" without option?16:08
tjaaltonlook at what grub menu already has in /boot/grub/grub.cfg16:09
tjaaltonI think that should drop in initrd, but could be wrong16:09
tjaaltonanyway, there are boot entries for recovery mode, so just try with that first16:10
nilujeok, thanks16:10
nilujewill try16:10
nilujehm it doesn't work — I'm not sure why. I have a broken RAID, and I think adding "recovery" to the kernel cmdline attempts to mount the failing partitions which fails, and so it doesn't drop a shell. So I guess I need to drop a shell before16:14
tjaaltonhttps://wiki.ubuntu.com/DebuggingKernelBoot16:16
tjaaltontry break=premount16:16
tjaaltonor just break16:16
tjaaltonpremount should be the default16:16
nilujeI already tried break, break=premount and break=top without success16:18
tjaaltondunno then16:18
nilujethanks a lot for your help :)16:18
tomreynjust "break" works for me on bionic16:40

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!