[02:48] good morning to all [03:37] does anyone know the program whcih expands the ISO on install? (it'll be same if calamares/lubuntu or ubiquity/rest so I'm betting not the the installer package) [03:39] "expands"? [03:40] writes the squashfs to the actual disk... bug 1898302 [03:42] sorry, wasn't well explained; bug complains ubuntu are putting details in wrong locations on disk, non-Linux standards.. https://bugs.launchpad.net/ubuntu/+bug/1898302 [03:44] guiverc: that's called usrmerge, it's all the ragethese days, https://wiki.debian.org/UsrMerge [03:45] thank you most kindly sarnold :) I'll read it.. and hopefully get clues ! thanks [03:46] That's most apt !! (not the package name, no pun). thanks! [03:46] hah, and coming back to re-read what I wrote, 'rage' is quite the perfect choice :) [03:46] a great many people seem to think usrmerge is the best thing ever [03:47] and a great many people are driven to apoplexy over something so inane [03:47] anywaym, have fun :) [03:47] :) always try! [09:29] guiverc: in #ubuntu , nickanme lapion brought up something which sounded similar: [09:29] Why do the ubuntu install dvd's rely on a symbolic and or a hard-link ? [09:29] has everybody forgotton that the only truly useful file system for smaller usb-sticks is vfat ? [09:31] starting at 02:12 am CEST (should be 00:12 UTC), if you ant to look at the logs. [09:32] i'm not sure it's the same thing, though. [09:37] thanks tomreyn [09:40] * guiverc was dealing with food so waited till I'd finished & washed hands .. I expected to find a duplicate of it so I could mark it as such, I gave up looking; but settled with EOL'ing numerous bugs that cluttered my searches... [09:41] guiverc: if my eyes see correctly, the bugs about ltsupgrade seems like to be 4.15 kernel bionics to 20.04.1 [09:44] I was commenting about the /bin link /usr/bin.. ; but most bugs I've seen on upgrade seemed to be python, qt4/5 but I'm opening less than half of upgrade bugs I see on -announce [09:45] ah kk === akem_ is now known as JohnnyCage [14:22] oh i missed that 18.04 -> 20.04 is now supported [14:25] since 2020-09-28 [14:56] that was a heck of a delay [14:59] longer than usual for sure, but probably not longer than needed. [17:05] are zfs services running or even installed on a default 20.04.1 desktop, if anyone knows? [17:06] that's if the zfs option hasn't been chosen on the installer [17:07] dmesg | grep zfs on a default install should tell (i don't have one here currently) [17:08] tomreyn: grep returns nothing here [17:09] thanks [17:09] and i installed 20.04.1 in such early stage, i cant recall i saw the option in ubiquity [17:10] so before .1 release? [17:11] tomreyn: yeah i always help testing lts very early stage [17:11] so i dont have .1 clean installed systems here [17:12] okay, so it could have been added late rone [17:12] * later on [17:12] thanks [20:03] welcome Squarism & Seven_Six_Two [20:05] my brain isn't 100% awake yet, my apologies for not inviting you earlier [20:07] thanks [20:08] np. didn't know about this chan. I do sit in -offtopic now and again [20:10] offtopic is just too busy and most of the time only about nonsense imho. In this channel users can chat more relaxed about non support related Ubuntu stuff. [21:42] Anyone familiar with dkms? I am wondering why it seemed to fail on https://github.com/jeremyb31/bluetooth-5.4.git details at https://askubuntu.com/questions/1277459/bluetooth-rtl8723be-does-not-find-devices-on-lenovo-ideapad-100-14iby [21:46] how is it failing? [21:47] source install path should match the package name and version, e.g. /usr/src/$PACKAGE-$VERSION [21:47] Hi TJ- It seemed to fail for the user on the askubuntu site, but it worked when I tested it, his modinfo showed intree module loading after a reboot [21:48] ` I must have missed that part in the ask [21:51] TJ-: bottom of the question, might have been some glich where a new kernel was installed before the dkms was added [21:53] there's a link to "show 14 more comments" but it never does! [21:54] is it a 'depmod -a' issue? or is the module never built or installed ? [21:55] TJ-: worked fine after I told them to go into the directory and do a make clean, make, and had them copy the new module to where the original btusb.ko was and reboot [21:55] jeremy31: so did they do a "sudo dkms install module/version" ? [21:56] if it fails, it will/should report why [21:56] TJ-: dkms add and dkms install [21:57] and they've put the source in the correct /usr/src/$MODULE-$VERSION directory? [21:58] you'd need to capture/grab the dkms log of the build from /var/lib/dkms/ [22:01] TJ-: I think I will try again on this machine after installing a new kernel but before rebooting to see what I find out [22:03] Thanks for your time [22:41] Hello [22:43] TJ-: It must have been a kernel update before a reboot when the dkms was installed. Got similar results on this machine [22:44] jeremy31: that sounds likely, especially if you're not passing the -k option to specify which kernel version to build/install for [22:46] TJ-: A rare case from what I see. Any way to do it automatically in Makefile or dkms.conf? [22:49] jeremy31: in theory the /etc/kernel/postinst.d/dkms script should ensure a new build / install... but if that fails (silently) then the symptoms would match [22:52] TJ-: I think that depends on the newer kernel being installed before the dkms [22:53] after not before