[10:37] <TJ-> Is it possible to modify kernel config to support Bug #1838844
[10:37] <ubot5> bug 1838844 in linux (Ubuntu) ""dm-verity: Invalid number of feature arg" with FEC due to "# CONFIG_DM_VERITY_FEC is not set"" [Undecided,Incomplete] https://launchpad.net/bugs/1838844
[10:56] <apw> TJ-, all things are possible with sufficient motivation
[10:57] <apw> sforshee, ^
[10:58] <TJ-> apw: pretty please :D
[10:58]  * TJ- hands out sweets
[11:03] <tjaalton> lotuspsychje: have you tried 5.0.0-24 from bionic-proposed?
[11:04] <lotuspsychje> tjaalton: no
[11:04] <tjaalton> and did you check new bios?
[11:04] <tjaalton> if there is one
[11:05] <tjaalton> because there have been many dell machines with issues that were fixed by new bios
[11:05] <tjaalton> which comes with a new video bios
[11:05] <lotuspsychje> tjaalton: didnt test yet no, but i can confirm we have 3 different clevo's now with the flickering, diff bios versions
[11:06] <tjaalton> any of them with the latest?
[11:06] <lotuspsychje> tjaalton: got one customer comming this afternoon, ill doublecheck
[11:06] <lotuspsychje> tjaalton: and ill try to update mine asap
[11:07] <tjaalton> try -24 first
[11:07] <tjaalton> hmm
[11:07] <lotuspsychje> tjaalton: can you tell me the procedure, enable propose in sources?
[11:09] <tjaalton> yes, and apt update; apt install linux-generic-hwe-18.04
[11:09] <tjaalton> should pull everything
[11:09] <tjaalton> necessary, and not everything from proposed :)
[11:10] <lotuspsychje> installing
[11:13] <lotuspsychje> tjaalton: flickering aswell
[11:14] <tjaalton> ok
[11:15] <lotuspsychje> tjaalton: so, 4.15 works, 4.18 works, 5.3 latest works, 19.10 5.2 works
[11:16] <tjaalton> what, now 5.2 works?
[11:16] <lotuspsychje> i tested a 19.10 live daily
[11:16] <tjaalton> did you install it?
[11:16] <lotuspsychje> not yet
[11:17] <lotuspsychje> but a 19.04 live also flickers so live/real should not matter?
[11:17] <tjaalton> did you boot it with fastboot=0
[11:17] <tjaalton> ?
[11:17] <lotuspsychje> no
[11:17] <lotuspsychje> all iso tests were default
[11:18] <tjaalton> then it's not the same
[11:18] <tjaalton> fastboot is papering over it for the initial startup, suspend/resume should show flickering again
[11:18] <lotuspsychje> i see
[11:30] <lotuspsychje> tjaalton: think im gonna roll back to 4.18 for now, got a mail from my reseller suggesting so and remove 5*
[11:30] <lotuspsychje> he also doesnt think bios updates will fix this issue
[11:31] <tjaalton> so it's not worth it to try?
[11:31] <lotuspsychje> bricking bios will also break the warranty
[11:31] <lotuspsychje> tjaalton: yeah i will try it on my machine, but for customers ill go to 4.18 for now
[11:32] <lotuspsychje> we know its working there right
[11:54] <fling> Is it not possible to get a patch easily?
[11:57] <tjaalton> fling: look at the commits that touch fs/shiftfs.c, and then git format-patch them
[11:57] <tjaalton> it's not a single patch, nine commits in disco kernel
[12:41] <fling> tjaalton: do I need git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack ?
[12:41] <fling> tjaalton: how deep should I clone it?
[12:42] <fling> the tree is HUGE!
[12:42] <tjaalton> fling: ubuntu kernel
[12:43] <tjaalton> git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco or such
[12:44] <fling> I want the patch for 4.19.63 or similar
[12:44] <tjaalton> then do some work
[12:45] <fling> So there is no patch for 4.19.63 right?
[12:45] <fling> What is disco kernel?
[12:45] <tjaalton> 5.0
[12:45] <tjaalton> or pull it from cosmic (4.18)
[12:46] <tjaalton> I don't know what the closest one for 4.19, go search
[12:49] <apw> fling, better to bite the bullet and clone linus' tree, and use that as a reference for all of our trees when you clone them
[12:53] <fling> tjaalton: I can use 5.0
[12:54] <fling> apw: I have no idea how to perform this
[12:57] <apw> fling, mostly people would clone linus tree (git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git) and then when cloning our trees
[12:57] <apw> fling, literally say like git clone --reference linux <ubuntu tree>
[12:57] <apw> so you only once go get the objects in linus' tree and share them
[13:01] <TJ-> I add all the ubuntu repos as remotes 
[13:03] <apw> TJ-, also tollerable, i tend to need to work on more than one series at once
[13:03] <TJ-> apw: I thought that would be case, it's wonderful how flexible git is
[13:04] <apw> TJ-, right, that in spades
[13:05] <TJ-> I think I've included most Ubuntu releases, the stable tree, Debian, some nvidia-tegra stuff, raspi, and the entire .git is only 4.1GiB
[13:09] <apw> TJ-, believeabe, and given that is 5 or 6M commits that is pretty amazing
[13:09]  * TJ- nods happily
[13:09] <fling> It takes forever to clone!
[13:09] <fling> Is not there a faster way?
[13:09] <TJ-> fling: depends on the remote server load
[13:09] <apw> fling, the first time, likely yes, one never does it more than once
[13:12] <fling> Is 5.0 in git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco ?
[13:12] <fling> Which branch do I need?
[13:19] <apw> fling, which kernel are you runnig on which series
[13:27] <fling> apw: I'm running 4.19 on gentoo
[13:28] <apw> ok now i am confused, why do you want our kernel
[13:28] <fling> I'm trying to get the shiftfs patch.
[13:29] <fling> I need one to be able to use shiftfs.
[13:31] <fling> How to list commits including fs/shiftfs.c ? :P
[13:31] <apw> fling, then yes there are 9ish patches on the master-next branch of the +git/disco which relate to adding shiftfs
[13:31] <apw> git log fs/shiftfs.c
[13:32] <fling> thanks!
[13:38] <fling> How to figure out which version am I getting the patch for?
[13:47] <richi235> fling: try git://kernel.ubuntu.com/ubuntu/ubuntu-disco.git that should be faster
[13:48] <richi235> for almost every git.launchpad.net repo you can find a kernel.ubuntu.com repo which is a mirror and faster
[13:50] <richi235> browsable at https://kernel.ubuntu.com/git/