| [15:27] <ndichtel> Hi all | |
| [15:27] <ndichtel> I'm trying to find some docs about supported kernel versions. This page is quite old: https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Kernel.2FSupport.Ubuntu_Kernel_Release_Schedule (nothing after kernel 4.15). Is there something up to date somewhere else? | |
| [15:28] <apw> ndichtel, hmmm, well the supported versions are exposed most accuratly by the archive, but that being out of date isn't right for sure | |
| [15:29] <ndichtel> you mean mailing list archive? | |
| [15:30] <apw> ndichtel, hmm actually as that page only talks about lts release it is nominally mostly up to date, other than a lack of the latest backports | |
| [15:30] <ndichtel> for example, I'm interessing to know when the hwe kernel version will change | |
| [15:30] <apw> ndichtel, no that actual archive itself, the hwe version in 18.04LTS ? it just changed to 5.3 didn't it ? | |
| [15:31] <ndichtel> there is a lot of vTBD for kernel versions ;-) | |
| [15:31] <apw> yes it did | |
| [15:31] <ndichtel> yes | |
| [15:31] <ndichtel> it just changes | |
| [15:32] <apw> well it announced on the kernel mailing lists, and normally it changes about 6-8 weeks after teh release of the next development release | |
| [15:32] <apw> so we have 6-8 weeks of lead time before teh point release which is about to drop for 18.04 | |
| [15:33] <apw> but those diagrams are slightly out of sync with reality as we move hwe a little earlier than we used to so we don't slip the point release itself | |
| [15:33] * apw will find someone to fix them up | |
| [15:33] <ndichtel> ok, thank you for the details | |
| [15:34] <apw> ndichtel, thanks for pointing it out | |
| [15:35] <ndichtel> ;-) | |
| [15:37] <ndichtel> sorry for the naïve question: which mailing list can I subscribe to get the announcement? | |
| [15:40] <apw> kernel-team@ lists.ubuntu.com | |
| [15:40] <ndichtel> oh, I thought it was a private ml | |
| [15:40] <ndichtel> thanks | |
| [16:26] <zx2c4> apw: https://xn--4db.cc/5xyUvbQg/diff maybe this will help | |
| [16:27] <zx2c4> perhaps it just works out of the box O_o | |
| [16:31] <zx2c4> Lotta crazy scripting going on | |
| [17:04] <apw> zx2c4: close to what I have, just it is on top of the new versioned provides bits | |
| [17:08] <zx2c4> apw: version provides bits? | |
| [17:08] <zx2c4> am i on the wrong branch of the repo? | |
| [17:11] <apw> zx2c4, not published anywhere yet, i am fixing 3-4 bugs in the same area; yours includeed | |
| [17:12] <apw> zx2c4, should be finished tommorrow if i haven't pooched anything | |
| [17:12] <zx2c4> apw: oh cool | |
| [17:12] <zx2c4> i looked at those scripts | |
| [17:12] <zx2c4> dkms-build--{packagename} | |
| [17:12] <zx2c4> and | |
| [17:12] <zx2c4> dkms-builds--{packagename}-configure | |
| [17:12] <apw> zx2c4, i assume you will contact us direct if there are any security/urgent updates for the driver | |
| [17:12] <zx2c4> or something similar | |
| [17:13] <zx2c4> and i couldnt see anything in those that wireguard would need | |
| [17:13] <apw> yeah it is all a bit more complex than it needs to be because of nvidia not being really shipped by linux | |
| [17:13] <zx2c4> but if you do find yourself needing some hacky stuff like that, we cna probably put that upstream instead | |
| [17:13] <apw> zfs is a good exmaple to follow | |
| [17:13] <zx2c4> cept zfs has like 20 modules | |
| [17:13] <apw> right, but overall as you guestimated it is about as complex | |
| [17:14] <zx2c4> 18:12:51 <apw> zx2c4, i assume you will contact us direct if there are any security/urgent updates for the driver | |
| [17:14] <zx2c4> i'd probably be inclined to do that _but_ you (or kerneltoast) should join wgml and watch the [ANNOUNCE] emails | |
| [17:14] <apw> zx2c4, oh while a remember; where will the upstram bits land in the tree, ie where will the .ko express | |
| [17:14] <apw> zx2c4, can you pm where that is, and i'll get added | |
| [17:14] <zx2c4> drivers/net/wireguard.ko | |
| [17:14] <zx2c4> https://lists.zx2c4.com/mailman/listinfo/wireguard | |
| [17:14] <apw> ok good, so the dkms one will appear in wireguard/* so that is not going to clash | |
| [17:15] <zx2c4> ./5.5.0-rc6+/kernel/drivers/net/wireguard/wireguard.ko | |
| [17:15] <zx2c4> actually, that^ | |
| [17:15] <zx2c4> alright thats fine | |
| [17:15] <zx2c4> wireguard-dkms builds into net/wireguard in fact | |
| [17:15] <apw> zx2c4, right but i don't let it go where it thinks it wants to :) | |
| [17:16] <apw> zx2c4, the dkms-build magic sorts that out for all of 'em | |
| [17:16] <zx2c4> so wireguard/wireguard.ko (apwlandia), net/wireguard.ko (dkms), and drivers/net/wireguard/wireguard.ko (upstream) all do not clash | |
| [17:16] <apw> i think dkms is updates/<omething>) | |
| [17:16] * apw looks for a keyboard with all of the keys in the normal place | |
| [17:16] <zx2c4> https://git.zx2c4.com/wireguard-linux-compat/tree/src/dkms.conf | |
| [17:16] <zx2c4> DEST_MODULE_LOCATION="/kernel/net" | |
| [17:17] <zx2c4> kernel/net apparently, in fact | |
| [17:17] <zx2c4> O_o | |
| [17:17] <zx2c4> perhaps ubuntu overrides that though | |
| [17:17] <zx2c4> but, anyway, sure -- feel free to put it wherever you think is best | |
| [17:17] <apw> /lib/modules/5.4.0-9-generic/updates/dkms/wireguard.ko | |
| [17:17] <zx2c4> gotcha | |
| === jdstrand_ is now known as jdstrand | |