=== chris14_ is now known as chris14
[07:43] <alkisg> What's the process that autoinstalls `linux-image-oem-22.04c` AFTER regular installations have been working for months with their generic, hwe or aws kernels?
[07:43] <alkisg> It has a bug that I want to research: I've seen more than 20 systems so far that lack the kernel headers because of this process...
[07:43] <alkisg> apt install linux-oem-22.04c solves the issue, but the systems end up having 3 series of kernels, e.g. generic, hwe AND oem, without the user ever having ran anything other than a simple apt full-upgrade...
[07:45] <alkisg> To be clear, installing 22.04 gets you generic, then with plain apt full-upgrades you end up with generic, hwe AND oem
[10:17] <tjaalton> no, installing 22.04 gives you hwe
[10:19] <tjaalton> (on !server)
[10:57] <alkisg> tjaalton: AFAIK 22.04 and 22.04.1 give you -generic, while 22.04.2+ gives you -hwe. But in any case they shouldn't end up with all 3 series, -generic, -hwe and -oem
[10:58] <alkisg> What's the process for auto-installing oem after the initial installation?Which package/script does that?
[11:13] <luna> New kernels today upstream 1-2 days early
[11:22] <tjaalton> alkisg: the hwe-metapackage is always installed, so that it rolls to the next one. in .0 and .1 it does essentially give the generic kernel
[11:23] <tjaalton> there is no process for auto-installing oem on normal upgrades, so you'd need to look at the apt/dpkg logs to figure out why it would install those. but I suspect some nvidia wonkiness
[11:37] <thefossguy> > <@thefossguy:matrix.org> Hello there, I am experimenting with enabling Rust support in the Linux kernel. So far, I have been able to compile the kernel with Rust support enabled; only in theory. The kernel config options say that Rust support is present but trying to build the out of tree Rust module fails... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/f582bed42f7fd03cce7551c679c81ffb0dec197e>)
[12:14] <alkisg> tjaalton: thanks, I'll ask for remote access to check the logs
[12:23] <alkisg> tjaalton: for iso in *22.04*.iso; do echo -n "$iso: "; mount "$iso" /mnt; mount /mnt/casper/filesystem.squashfs /mnt; chroot /mnt dpkg -l | grep -q hwe && echo -n "YES, " || echo -n "NO, "; umount /mnt; umount /mnt; done 2>/dev/null
[12:23] <alkisg> kubuntu-22.04.2-desktop-amd64.iso: YES, lubuntu-22.04.1-desktop-amd64.iso: NO, ubuntu-22.04.1-desktop-amd64.iso: YES, ubuntu-22.04.1-live-server-amd64.iso: NO, ubuntu-mate-22.04.2-desktop-amd64.iso: YES, xubuntu-22.04.1-desktop-amd64.iso: NO
[12:24] <alkisg> At least in the live CDs, in 22.04 and 22.04.1, there's no -hwe; it starts with 22.04.2
[12:24] <alkisg> But OK that's not important, I'll try to discover why these users are getting the -oem package, thanks
[12:25] <alkisg> Ah, it's there in gnome (which I rarely use) but not in the other flavors; that explains it
[12:28] <alkisg> (although all flavours should really have the same kernel packages...)
=== leftyfb_ is now known as leftyfb
[13:26] <arighi> thefossguy, this is with upstream kernel right? not the ubuntu kernel. Also, do you have CONFIG_RUST=y in your kernel .config?
=== Furna_away is now known as Furna