matti | fling: 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 | ||
h3rbz | Hi! 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 |
h3rbz | Am 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 |
tjaalton | h3rbz: 4.18 was from cosmic, which is now EOL | 12:38 |
tjaalton | if you want to stay on the hwe kernel, install linux-image-generic-hwe-18.04 which would pull 5.0 now | 12:39 |
lotuspsychje | tjaalton: good news, tomreyn found booting intel_idle.max_cstate=4 fixxed my issue on 5.0.0.25 keeps working after suspend aswell | 12:40 |
tjaalton | just a workaround then | 12:40 |
tomreyn | yes, a workaround | 12:40 |
lotuspsychje | yes | 12:40 |
tomreyn | we read this at https://bugs.freedesktop.org/show_bug.cgi?id=109215 | 12:42 |
ubot5 | Freedesktop 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 |
tjaalton | but doesn't say if it's fixed in 5.3 for him | 12:44 |
lotuspsychje | i tested a 5.3 and confirmed no flickering | 12:44 |
tjaalton | but he didn't | 12:44 |
lotuspsychje | no | 12:45 |
h3rbz | tjaalton: thx! I think I was not inderstanding exactly what this 'hwe' version is. | 12:54 |
h3rbz | I did not consider it, jsu as with lowlatency et. al. | 12:54 |
h3rbz | *just | 12:54 |
h3rbz | nice to have 5.x though :) | 12:59 |
h3rbz | meh.. is it true, that the cephfs kernel client does not support quota in 5.0.0? | 13:15 |
h3rbz | it did not in 4.15, it did in 4.18, that's why I installed it | 13:15 |
h3rbz | n/m my mistake. it works, I was just doing something stupid while testing :) thx anyway | 14:28 |
niluje | hi, which paramater should I give in the cmdline to get a shell in the initrd? break=init-top doesn't seem to work | 16:04 |
tjaalton | recovery? | 16:06 |
tjaalton | or just boot the recovery entry | 16:06 |
niluje | tjaalton: the answer is for me? | 16:07 |
tjaalton | yes | 16:07 |
niluje | tjaalton: you mean I should add the param "recovery" without option? | 16:08 |
tjaalton | look at what grub menu already has in /boot/grub/grub.cfg | 16:09 |
tjaalton | I think that should drop in initrd, but could be wrong | 16:09 |
tjaalton | anyway, there are boot entries for recovery mode, so just try with that first | 16:10 |
niluje | ok, thanks | 16:10 |
niluje | will try | 16:10 |
niluje | hm 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 before | 16:14 |
tjaalton | https://wiki.ubuntu.com/DebuggingKernelBoot | 16:16 |
tjaalton | try break=premount | 16:16 |
tjaalton | or just break | 16:16 |
tjaalton | premount should be the default | 16:16 |
niluje | I already tried break, break=premount and break=top without success | 16:18 |
tjaalton | dunno then | 16:18 |
niluje | thanks a lot for your help :) | 16:18 |
tomreyn | just "break" works for me on bionic | 16:40 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!