[02:52] good morning [08:09] good morning [08:12] 'morning [13:53] The MT76 fix is in proposed in kernel 5.4.0-61 [13:54] tnx jeremy31 [13:55] That was quick compared to the last fix I submitted [13:56] the customer box suffered it, has still hwe edge 5.8 now, so i guess he will be good for a while [13:58] I am putting 20.04 on a USB to install over 20.10 and see what happens when I install updates after installing without internet. Find out why all these people are getting 5.8 on 20.04 [13:58] yeah its weird man [14:01] linux-generic-hwe-20.04 ? [14:02] TJ-: no, we had volunteers & users reporting fossa dragging kernel 5.8 on regular updates on 20.04 [14:02] after that it started raining bugs of all kinds on 5.8 [14:03] TJ-: jeremy31 had it on a clean install iso updates for example [14:05] suggests something depending on a 5.8 package then [14:07] aren't the latest 20.04 point releases using 5.8 ? [14:07] TJ-: think 20.04.2 planned 5.8 [14:08] dep was what i thought :) no exposure to those reporting though, so no action from me [14:09] in general i'm pretty tired of the frequency of kernel emissions [14:09] daftykins: devops taking over! [14:09] TJ-: from the kernel guys; By default the 20.04 media installs the hwe kernel for desktop images. The hwe meta was still pointing to the 5.4 generic kernel, until this week when we released an update to pull the hwe-5.8 backport [14:10] that response is misleading to me, because it was never the case that 20.04.0 media would install HWE, so are they saying focal changed this behaviour? [14:10] if so... disappointing [14:11] It will cause a lot more headaches [14:14] It is the case, linux-generic not installed but linux-generic-hwe-20.04 is on a fresh install [14:15] yes, the manifects for the ISO contains [14:15] inux-generic-hwe-20.04 5.8.0.32.34~20.04.19 [14:15] linux-headers-5.8.0-32-generic 5.8.0-32.34~20.04.1 [14:15] linux-headers-generic-hwe-20.04 5.8.0.32.34~20.04.19 [14:15] s/manifects/manifest/ [14:15] desktop .1 image? [14:15] desktop image, not a point release ISO [14:15] oh eww [14:16] 20.04.1 manifest still shows: [14:16] linux-generic-hwe-20.04 5.4.0.42.46 [14:16] linux-headers-5.4.0-42 5.4.0-42.46 [14:16] linux-headers-5.4.0-42-generic 5.4.0-42.46 [14:16] linux-headers-generic-hwe-20.04 5.4.0.42.46 [14:16] 20.04: linux-generic-hwe-20.04: [14:16] Installed: 5.4.0.26.32 [14:16] Candidate: 5.8.0.36.40~20.04.21 [14:17] yes, 20.04.0 shows linux-generic-hwe-20.04 5.4.0.42.46 HOWEVER if the user enables updates during install that'll pull in 5.8 [14:17] tricky [14:18] Looks like the only fix to stay on 5.4 would be to install linux-generic before updates [14:20] I'm not sure that'll work since linux-*generic/linux-generic-*hwe* don't Conflicts:/Replaces: each other [14:20] maybe a pin ? [14:20] https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle discusses how it is meant to be [14:20] no, that wouldn't do it if they're side-by-side, you'd need to remove the *hwe* [14:20] so that means all fresh users from now will result on 5.8? [14:21] Looks lika all 20.04 [14:21] lotuspsychje: yes, once they do the first package upgrade, either during install or later [14:22] Now that they switched the kernel linked to linux-generic-hwe [14:22] TJ-: so only offline boxes wont? [14:23] lol who's offline [14:23] lotuspsychje: I *think* that removing "linux-generic-hwe-20.04" before the first update/upgrade would keep on 5.4 [14:23] we get some cool kids with 12.04 offline box questions here sometimes :p [14:24] those are the fakes [14:24] lotuspsychje: the manifest for the 20.04.0 ISO has "linux-generic-hwe-20.04 5.4.0.42.46" so you'd need to 'apt remove linux-generic-hwe-20.04 linux-headers-generic-hwe-20.04 linux-image-generic-hwe-20.04" and then "apt install linux-generic" [14:27] yikes [14:27] no wonder its raining bugs in -announce [14:28] nvidia, broadcom, virtualbox, and a bunch of others [14:28] lotuspsychje: so "apt remove linux-*generic-hwe-20.04 && apt install linux-generic" I think [14:29] all the out-of-tree modules that don't keep up [14:30] anything not backported from groovy [14:31] has bcmwl been patched up ? I didn't notice that in launchpad earlier [14:31] That askubuntu link has a link to bcmwl for groovy [14:33] oh yeah, minor ubuntu patch debian/patches/0028-add-support-for-linux-5.6.patch [16:29] i was bored enough to just install from 20.04.0 media in a VM and spy 5.8.0 indeedy, tsk tsk [16:31] however it ran through it even though i had specified no update during install, which i know is to be expected since i think it handles kernel update tasks regardless of your intention [16:31] daftykins: I installed without internet connected [16:31] yeah i recall [16:32] i was just going through the motions myself for fun, the above being my first choice [16:45] Going to cause quite a few duplicate bugs [16:57] one thing i didn't quite grasp yet then, does it seem to be a new intention or an oversight? [17:06] can confirm i purged linux-image-generic-hwe-20.04 and linux-generic-hwe-20.04 before reconnecting the network, running an apt update, then installing linux-generic [17:19] It would have to be a mistake as nobody using desktop would be left on LTS kernel anymore [17:26] mmm [17:35] All I could find in release notes was: Ubuntu Desktop flavour now always tracks HWE kernel (hardware enablement). It means that from 20.04.2 release Ubuntu Desktop will gain new major kernel versions every 6 months through to summer of 2022. [17:41] hrmm [17:42] About a month away from 20.04.2 [22:53] anyone here trying to use ubuntu on other devices like a chromebook, iPad or other tablet?