apwhallyn, it sounds like you are conflating ubuntu abi numbers and upstream stable numbers08:57
jsalisburytsimonq2, apw I'll build a test kernel for that bug.12:25
tsimonq2jsalisbury: Thanks.12:28
mamarleyIt looks like the v4.15-rc9 mainline kernel (with the 4.15.0-5.6 configuration) (inadvertently?) disables several options related to Broadcom B43 and B44 chips, causing these chips to not work with that kernel.12:48
mamarleyAnd also a bunch of SSB-related configuration options, which are also related to these chips.12:49
apwmamarley, are they new?  new ones are taken at their defaults12:58
mamarleyapw: I don't think so; these have been around forever.  I also checked the commit history and it doesn't look like anything related to ssb or b4x changed since -rc8.13:29
hallynapw: coudl be, are you saying the kaiser patches were backported to 4.4.0-109-generic ?  except it's from jan 9, and the magic sysfile telling me i'm safe isn't there :)15:18
apwthose sysfs files.are total rubbish in the main15:19
apwV1 reports bad always iirc even with the patches which fix it applied15:20
jsalisburytsimonq2, I posted a test kernel to the bug.15:58
tsimonq2jsalisbury: Thank you :)17:16
s10gopalhttps://bugs.freedesktop.org/show_bug.cgi?id=104737 please help me20:09
ubot5Freedesktop bug 104737 in DRM/AMDgpu "amdgpu module does not bind to 1002:6660 R5 M330" [Major,New]20:09
tomreynthis is being discussed in #ubuntu now, where it belongs20:18
TJ-the user is inexperienced but persistent :)20:19
hggdhthe shotgunned a lot of channel with the exact same Q20:24
jackpot51I am seeing linux-signed-generic show up when doing debootstrap and then an apt update/upgrade. I do not see linux-signed-image-generic (=, and this is causing a failure to upgrade. Can someone help me out?21:57
=== ben_r_ is now known as ben_r
mamarleyapw: Even when I remove the parts of "0006-configs-based-on-Ubuntu-4.15.0-5.6.patch" that disable the SSB options, the options still end up getting disabled somehow when the kernel is compiled.  I'm trying to figure out why that is, but not having much luck.23:07
apwjackpot51: against which archive pocket?23:11
apwmamarley: that implies a config constraint is disabling them23:11
apwtypically a select or depends influencing the value23:12
mamarleyI figured it was something like that.  I'm not sure how to figure out which one though.23:13
mamarleyI went through all the CONFIG_SSB* options that are defined and ensured that the config has them enabled.23:22
mamarleyI mean that the config has their DEPENDS enabled.23:22
mamarleyapw: I figured it out, https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=664eadd6f44b3d71dcc62d0a825319000de0d5c9 causes the problem.23:32
mamarleyThe problem is, as far as I can tell, CONFIG_PCI_DRIVERS_LEGACY is defined only on MIPS.23:33
apwand _LEGACY is that new, and off?23:34
mamarleyapw: According to https://cateee.net/lkddb/web-lkddb/PCI_DRIVERS_LEGACY.html, it was introduced in 4.9.  There doesn't seem to be a switch for it anywhere in the x86_64 menuconfig though.23:35
mamarleyAnd searching for that symbol in menuconfig shows "Symbol: PCI_DRIVERS_LEGACY [=PCI_DRIVERS_LEGACY]"/"Type  : unknown"23:36
mamarleyEven if I set CONFIG_PCI_DRIVERS_LEGACY=y in the configuration, the next time I run menuconfig it just removes it.  I think the committer must have forgotten to try compiling b43/b44/ssb on anything but MIPS with that patch.  I will open an upstream kernel bug.23:39
mamarleyWait, it is actually nel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=58eae1416b804d900014d84feadda7195007cc3023:45
mamarleyOops, https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=58eae1416b804d900014d84feadda7195007cc3023:45
ubot5bugzilla.kernel.org bug 198555 in Network "Symbol dependency issue prevents compiling SSB_PCICORE and dependants on x86_64 and possibly others since 4.15-rc9" [High,New]23:49

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!