💾 Archived View for gemini.ctrl-c.club › ~phoebos › logs › freenode-kisslinux-2020-11-18.txt captured on 2022-07-17 at 03:17:08.

View Raw

More Information

⬅️ Previous capture (2021-12-17)

-=-=-=-=-=-=-

2020-11-18T08:03:11 #kisslinux <tink_> is it normal to have penguins at the top of the screen all the time? the resolution appears to be 1280x720 although my display is 1920x1080
2020-11-18T08:03:30 #kisslinux <tink_> i am not using any display server, i'm talking about the shell
2020-11-18T08:32:33 #kisslinux <tink__> test
2020-11-18T08:46:49 #kisslinux <testuser[m]> <tink_ "is it normal to have penguins at"> Not sure but i think that's controlled by the the Bootup Logo (`CONFIG_LOGO`) option in Device Drivers > Graphics support (menuconfig)
2020-11-18T10:59:26 #kisslinux <tink> I think the penguins stay at the top and they act as the screen's borders, so I feel like it's 1280x720 instead of 1920x1080. Is there any setting that controls this?
2020-11-18T11:32:01 #kisslinux <konimex> <claudia02 "UUID are the long ones. PARTUUID"> isn't it the other way around? (and in case of UUID (or PARTUUID when using MBR instead of GPT), depends on the filesystem)
2020-11-18T11:42:57 #kisslinux <tink> the penguins can be seen here for reference https://www.reddit.com/user/sabrtorte/comments/jw26sy/
2020-11-18T12:14:09 #kisslinux <konimex> the penguins are there if you enable CONFIG_LOGO
2020-11-18T12:14:25 #kisslinux <konimex> if you disable it, the penguins won't appear
2020-11-18T13:58:42 #kisslinux <claudia02> konimex : acording to my system configuration, uuid is the long one and partuuid the short one. http://ix.io/2EA5 . Even we have dealt so often with this stuff its still confusing.
2020-11-18T14:01:37 #kisslinux <konimex> https://termbin.com/no0n this is mine
2020-11-18T14:08:22 #kisslinux <claudia02> What file is that?
2020-11-18T14:08:55 #kisslinux <claudia02> I dont have /dev/disk
2020-11-18T14:12:59 #kisslinux <claudia02> Ah I see. Its the other way around
2020-11-18T14:13:02 #kisslinux <claudia02> hm..
2020-11-18T14:23:17 #kisslinux <claudia02> konimex: this is my output of blkid from util-linux. UUID the long one.
2020-11-18T14:37:36 #kisslinux <tink> Well, now that I have a partially working system, I guess I can work on the modules then.
2020-11-18T14:38:38 #kisslinux <tink> According to dmesg, the blobs I put in /lib/firmware aren't loaded, which leads to a cpu vulnerability and the network interface not showing up
2020-11-18T14:40:23 #kisslinux <soliwilos> Unless you build firmware files into the kernel, the relevant drivers must be loaded as modules and not builtin, for the firmware to be picked up from lib/firmware.
2020-11-18T14:41:01 #kisslinux <tink> Do you mean "CONFIG_EXTRA_FIRMWARE"?
2020-11-18T14:41:55 #kisslinux <tink> CONFIG_EXTRA_FIRMWARE="intel-ucode/06-8e-09 i915/kbl_dmc_ver1_04.bin i915/kbl_guc_33.0.0.bin i915/kbl_huc_4.0.0.bin ath10k/QCA6174/hw3.0/board-2.bin ath10k/QCA6174/hw3.0/firmware-6.bin"
2020-11-18T14:42:00 #kisslinux <tink> I have this line in .config
2020-11-18T14:42:21 #kisslinux <soliwilos> I mean if you're wanting a firmware file for your network card, then the network cards driver must be a module.
2020-11-18T14:45:34 #kisslinux <soliwilos> tink: Do you have CONFIG_EXTRA_FIRMWARE_DIR set to "/usr/lib/firmware" or "/lib/firmware" as well?
2020-11-18T14:45:41 #kisslinux <tink> CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"
2020-11-18T14:50:17 #kisslinux <claudia02> tink: When you build as module, you have to manually load them
2020-11-18T14:59:04 #kisslinux <soliwilos> tink: Firmware files with CONFIG_EXTRA_FIRMWARE are builtin to the kernel, and then the hardware drivers should be builtin too. If you're using the hardware drivers for ath10k as a module, then it's firmware must be removed from CONFIG_EXTRA_FIRMWARE.
2020-11-18T15:00:56 #kisslinux <tink_> If you require firmware blobs, the drivers you enable must be enabled as
2020-11-18T15:00:56 #kisslinux <tink_>     [m] (modules). You can also optionally include the firmware in the kernel
2020-11-18T15:00:56 #kisslinux <tink_>     itself.
2020-11-18T15:01:12 #kisslinux <tink_> it says they need to be enabled as modules in the kiss installation guide
2020-11-18T15:02:07 #kisslinux <soliwilos> Essentially.. If a driver is loaded from the filesystem as a module, then the firmware too must be loaded from the filesystem. At least that's how I have understood things.
2020-11-18T15:02:51 #kisslinux <tink_> Then I'll just build everything in
2020-11-18T15:06:18 #kisslinux <tink_> What I don't get is there is nothing related to the microcode among the modules
2020-11-18T15:06:32 #kisslinux <tink_> Yet it still isn't loaded
2020-11-18T15:10:36 #kisslinux <soliwilos> As far as I know, microcode updates aren't entirely builtin. You enable the relevant microcode options in the kernel as builtin, but load the actual microcode as an initrd file in your bootloader.
2020-11-18T15:11:25 #kisslinux <soliwilos> "Early microcode loading"
2020-11-18T15:15:40 #kisslinux <tink_> https://wiki.gentoo.org/wiki/Intel_microcode#New_method_without_initram-fs.2Fdisk_.28efistub_compatible.29
2020-11-18T15:16:00 #kisslinux <tink_> This page is talking about efi stub compatible intel microcode loading
2020-11-18T15:17:12 #kisslinux <tink_> I have done as described (copied the relevant microcode files to /lib/firmware, added an entry for it in CONFIG_EXTRA_FIRMWARE and specified the directory in CONFIG_EXTRA_FIRMWARE_DIR)
2020-11-18T15:17:51 #kisslinux <tink_> But when I ran dmesg | grep microcode, SRBDS: Vulnerable: No microcode
2020-11-18T15:20:49 #kisslinux <soliwilos> I see. You also used the iucode_tool to identify the correct microcode?
2020-11-18T15:23:35 #kisslinux <tink_> I didn't use the tool but I confirmed that the microcode is the right one for my cpu from official intel sources
2020-11-18T15:25:08 #kisslinux <tink_> I'll check it again just to make sure.
2020-11-18T15:28:59 #kisslinux <soliwilos> You also have CONFIG_MICROCODE, CONFIG_MICROCODE_INTEL and CONFIG_FIRMWARE_IN_KERNEL set to builtin?
2020-11-18T15:45:04 #kisslinux <claudia02> konimex : I have not send the link earlier. Output of blkid http://ix.io/2EAc
2020-11-18T15:57:38 #kisslinux <tink_> @soliwilos: I have those two enabled but there is no FIRMWARE_IN_KERNEL option to be set in the first place
2020-11-18T15:58:38 #kisslinux <micr0> yay, new firefox version
2020-11-18T16:02:27 #kisslinux <soliwilos> tink_: Hmm, page you linked mentioned it among the kernel options that had to be enabled.
2020-11-18T16:03:17 #kisslinux <tink_> Yes, I noticed it as well but for some reason it's not found in .config
2020-11-18T16:03:23 #kisslinux <soliwilos> It's possible it depends on something that is currently unset.
2020-11-18T16:03:25 #kisslinux <tink_> Maybe it was removed in a new kernel version?
2020-11-18T16:03:43 #kisslinux <soliwilos> Then it won't show in the .config file.
2020-11-18T16:03:51 #kisslinux <tink_> It doesn't show in the .config file
2020-11-18T16:06:02 #kisslinux <soliwilos> Do you have PREVENT_FIRMWARE_BUILD enabled? If yes, try disabling it.
2020-11-18T16:06:52 #kisslinux <tink_> I have it enabled
2020-11-18T16:08:44 #kisslinux <tink_>  I believe this is why I disabled it:
2020-11-18T16:08:50 #kisslinux <tink_> (enabled it, I mean)
2020-11-18T16:08:51 #kisslinux <tink_> Firmware should not be being built as part of kernel, these days                                                                │
2020-11-18T16:08:51 #kisslinux <tink_>   │ you should always prevent this and say Y here. There are only two                                                               │
2020-11-18T16:08:51 #kisslinux <tink_>   │ old drivers which enable building of its firmware at kernel build                                                               │
2020-11-18T16:08:51 #kisslinux <tink_>   │ time:
2020-11-18T16:09:20 #kisslinux <tink_>  o CONFIG_WANXL through CONFIG_WANXL_BUILD_FIRMWARE                                                                            │
2020-11-18T16:09:21 #kisslinux <tink_>   │   o CONFIG_SCSI_AIC79XX through CONFIG_AIC79XX_BUILD_FIRMWARE
2020-11-18T16:11:04 #kisslinux <soliwilos> It does seem unrelated.
2020-11-18T16:19:53 #kisslinux <soliwilos> Looking at the kernel.org documentation, it seems you should only need CONFIG_EXTRA_FIRMWARE and CONFIG_EXTRA_FIRMWARE_DIR.
2020-11-18T16:20:47 #kisslinux <soliwilos> tink: https://www.kernel.org/doc/html/latest/x86/microcode.html#builtin-microcode
2020-11-18T16:28:05 #kisslinux <sh4rm4^bnc> fwiw on kernel 4.14 lts all modules except one intel wifi driver can be built statically yet can load their firmware from /lib/firmware
2020-11-18T16:30:32 #kisslinux <tink_> Just used iucode_tool. I suppose I need to load 5 files
2020-11-18T16:30:48 #kisslinux <tink_>   064/001: sig 0x000906e9, pf_mask 0x2a, 2019-10-03, rev 0x00ca, size 100352
2020-11-18T16:30:48 #kisslinux <tink_>   065/001: sig 0x000906ea, pf_mask 0x22, 2019-10-03, rev 0x00ca, size 99328
2020-11-18T16:30:48 #kisslinux <tink_>   066/001: sig 0x000906eb, pf_mask 0x02, 2019-10-03, rev 0x00ca, size 100352
2020-11-18T16:30:48 #kisslinux <tink_>   067/001: sig 0x000906ec, pf_mask 0x22, 2019-10-03, rev 0x00ca, size 99328
2020-11-18T16:30:48 #kisslinux <tink_>   068/001: sig 0x000906ed, pf_mask 0x22, 2019-10-03, rev 0x00ca, size 100352
2020-11-18T16:32:25 #kisslinux <tink_> I'll rebuild the kernel then.
2020-11-18T16:40:17 #kisslinux <exoost-fume> good evening or whatever time of the day you're having
2020-11-18T16:48:28 #kisslinux <micr0> hiya exoost-fume
2020-11-18T16:48:31 #kisslinux <exoost-fume> I am trying to build my own kiss-chroot by Dylan's comment on reddit (https://www.reddit.com/r/kisslinux/comments/dn3iui/question_is_there_any_plan_to_support_other/f6wd6pn/) on a RPi4. I've installed gcc, musl. Set KISS_ROOT to the desired chroot location. Git cloned kiss pkg manager, set up the KISS_PATH with the /repo and /community repos.
2020-11-18T16:48:32 #kisslinux <exoost-fume> Successfully built baselayout. When trying to build baseutils -> "Building: m4 flex zlib binutils" -> Got an error "Please port gnulib freadahead.c to your platform..." -> "m4 Build failed". I have no idea what to do. Could someone please help?
2020-11-18T16:51:34 #kisslinux <micr0> exoost-fume lemme see if I can reproduce
2020-11-18T16:52:00 #kisslinux <micr0> if its possible to share your chroot history somewhere (with sensitive info removed if there is any) so I can make sure I am doing the same steps that would be nice
2020-11-18T16:52:11 #kisslinux <sh4rm4^bnc> haha, gnulib bites again
2020-11-18T16:52:15 #kisslinux <micr0> you can use http://ix.io or https://0x0.st for pasting from the cli nicely
2020-11-18T16:52:23 #kisslinux <micr0> Or i can just follow that link
2020-11-18T16:53:37 #kisslinux <exoost-fume> Dunno if that would help: imgur.com/a/mbVTVpQ
2020-11-18T16:53:40 #kisslinux <sh4rm4^bnc> https://wiki.musl-libc.org/faq.html
2020-11-18T16:54:08 #kisslinux <sh4rm4^bnc> that exact freadahead thing was added to the FAQ 9 years ago
2020-11-18T16:54:13 #kisslinux <exoost-fume> a
2020-11-18T16:55:33 #kisslinux <sh4rm4^bnc> what's the m4 version its trying to build ?
2020-11-18T16:57:21 #kisslinux <exoost-fume> how do i check which one?
2020-11-18T16:57:50 #kisslinux <micr0> Also I wonder what the env is too
2020-11-18T16:57:58 #kisslinux <sh4rm4^bnc> what's the name of the tarball you're using
2020-11-18T17:00:32 #kisslinux <exoost-fume> oh boy uhh
2020-11-18T17:01:08 #kisslinux <micr0> ls /var/cache/kiss/bin perhaps?
2020-11-18T17:05:06 #kisslinux <exoost-fume> i installed rasbian and just made a folder KISS_TESTING. KISS_TESTING/kiss/ - cloned from github repo. KISS_TESTING/chroot/ - made an empty dir. .../repos/repo/ & .../repos/community/ - repos. .../.profile - a file with export KISS_PATH(repos before mentioned) and KISS_ROOT (.../chroot/)
2020-11-18T17:05:30 #kisslinux <exoost-fume> KISS_TESTING/kiss/ is the pkg manager
2020-11-18T17:05:52 #kisslinux <sh4rm4^bnc> when you run m4's configure, it should show: checking for __freadahead... yes
2020-11-18T17:06:34 #kisslinux <exoost-fume> it shows no for me.
2020-11-18T17:06:42 #kisslinux <sh4rm4^bnc> that's the problem
2020-11-18T17:07:01 #kisslinux <sh4rm4^bnc> how did you get the source tarballs for your installation attempt ?
2020-11-18T17:07:42 #kisslinux <exoost-fume> i.. needed tarballs for that?
2020-11-18T17:07:48 #kisslinux <sh4rm4^bnc> do you understand what a tarball means ?
2020-11-18T17:07:55 #kisslinux <exoost-fume> a .tar file
2020-11-18T17:08:03 #kisslinux <sh4rm4^bnc> or tar.bz2 or whatever
2020-11-18T17:08:07 #kisslinux <exoost-fume> yeah
2020-11-18T17:08:26 #kisslinux <sh4rm4^bnc> yes, so for example m4 is installed from a source tarball, e.g. m4-1.4.18.tar.gz
2020-11-18T17:08:55 #kisslinux <sh4rm4^bnc> it is downloaded, then extracted, then built
2020-11-18T17:10:54 #kisslinux <exoost-fume> where do i get the tarball from?
2020-11-18T17:11:45 #kisslinux <sh4rm4^bnc> http://ftp.gnu.org/gnu/m4/m4-1.4.18.tar.xz
2020-11-18T17:11:50 #kisslinux <exoost-fume> damn
2020-11-18T17:12:10 #kisslinux <sh4rm4^bnc> but since you are clueless about it, propabably kiss whatever already downloaded it for you and put it somewhere
2020-11-18T17:12:54 #kisslinux <sh4rm4^bnc> how did you build your musl-targetting gcc ?
2020-11-18T17:13:40 #kisslinux <exoost-fume> i have no idea what i am doing whatsoever. i just installed the packages gcc and musl with apt.
2020-11-18T17:14:00 #kisslinux <sh4rm4^bnc> that's insufficient
2020-11-18T17:14:11 #kisslinux <sh4rm4^bnc> the gcc you downloaded targets your host libc
2020-11-18T17:15:10 #kisslinux <sh4rm4^bnc> build a gcc targeting your architecture with https://github.com/richfelker/musl-cross-make
2020-11-18T17:15:33 #kisslinux <sh4rm4^bnc> or get one pre-built from musl.cc
2020-11-18T17:16:50 #kisslinux <sh4rm4^bnc> this one should work i guess http://musl.cc/aarch64-linux-musl-native.tgz
2020-11-18T17:18:24 #kisslinux <exoost-fume> i wonder since it's aarch64, shouldnt i be using that one repo where the guy already ported the chroot to aarch64
2020-11-18T17:18:40 #kisslinux <exoost-fume> and just give up doing this
2020-11-18T17:19:00 #kisslinux <sh4rm4^bnc> up to you
2020-11-18T17:25:32 #kisslinux <exoost-fume> it may be a problem that rpi doesnt have its own storage and boots from the microsd card and i cant use a livecd
2020-11-18T17:27:42 #kisslinux <exoost-fume> copied files to /mnt, sudo /mnt/bin/kiss-chroot /mnt, and "chroot: failed to run command /usr/bin/env: Exec format error"
2020-11-18T17:29:21 #kisslinux <exoost-fume> so aarch64 wont work on this
2020-11-18T17:29:27 #kisslinux <exoost-fume> crap
2020-11-18T17:29:30 #kisslinux <sh4rm4^bnc> rpi4 is aarch64, but probably your distro ain't
2020-11-18T17:30:36 #kisslinux <sh4rm4^bnc> so the kernel they built doesn't even support 64bit bins
2020-11-18T17:33:20 #kisslinux <tink__> Building every module into the kernel apparently fails
2020-11-18T17:35:07 #kisslinux <tink__> Oh, it looks like an issue with the microcode
2020-11-18T17:35:07 #kisslinux <tink__> make[4]: *** No rule to make target '/lib/firmware/intel-ucode/06-9e-0da', needed by 'drivers/base/firmware_loader/builtin/intel-ucode/06-9e-0da.gen.o'.  Stop.
2020-11-18T17:35:08 #kisslinux <tink__> make[4]: *** Waiting for unfinished jobs....
2020-11-18T17:35:08 #kisslinux <tink__>   UPD     drivers/base/firmware_loader/builtin/intel-ucode/06-9e-0da.gen.S
2020-11-18T17:35:08 #kisslinux <tink__> make[3]: *** [scripts/Makefile.build:500: drivers/base/firmware_loader/builtin] Error 2
2020-11-18T17:35:09 #kisslinux <tink__> make[2]: *** [scripts/Makefile.build:500: drivers/base/firmware_loader] Error 2
2020-11-18T17:35:11 #kisslinux <tink__> make[2]: *** Waiting for unfinished jobs....
2020-11-18T17:35:13 #kisslinux <sh4rm4^bnc> i guess i could make my distro sabotage linux super-popular if i'd provide a rpi4 rootfs...
2020-11-18T17:36:30 #kisslinux <tink__> Yep, a typo.
2020-11-18T17:40:05 #kisslinux <exoost-fume> welp, downloading alpine and flashing it then
2020-11-18T17:40:19 #kisslinux <exoost-fume> gonna try it on aarch64
2020-11-18T17:49:05 #kisslinux <sh4rm4^bnc> yeah, compile-from-source distros are for people that are familiar with compiling
2020-11-18T17:50:24 #kisslinux <exoost-fume> how do i get familiar with compiling if whatever i use is already precompiled
2020-11-18T17:50:59 #kisslinux <sh4rm4^bnc> you'd probably start with compiling single projects from source
2020-11-18T17:51:39 #kisslinux <exoost-fume> right
2020-11-18T17:51:39 #kisslinux <sh4rm4^bnc> or writing some C code of your own
2020-11-18T18:11:54 #kisslinux <exoost-fume> thanks for everything
2020-11-18T20:02:31 #kisslinux <tink> Is it safe to ignore these? Saw them in dmesg
2020-11-18T20:02:39 #kisslinux <tink> ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
2020-11-18T20:02:46 #kisslinux <tink> ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
2020-11-18T20:03:01 #kisslinux <tink> acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration
2020-11-18T20:04:18 #kisslinux <tink> atkbd serio0: Spurious ACK on isa0060/serio0. Some program might be trying to access hardware directly.
2020-11-18T20:04:42 #kisslinux <tink> Panel advertises DPCD backlight support, but VBT disagrees. If your backlight controls don't work try booting with i915.enable_dpcd_backlight=1. If your machine needs this, please file a _new_ bug report on drm/i915, see https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs for details.
2020-11-18T20:05:12 #kisslinux <tink> bluetooth hci0: Direct firmware load for qca/rampatch_usb_00000302.bin failed with error -2
2020-11-18T20:05:13 #kisslinux <tink>  Bluetooth: hci0: failed to request rampatch file: qca/rampatch_usb_00000302.bin (-2)
2020-11-18T21:11:38 #kisslinux <micr0> anyone have their microphone working in firefox on wayland on kiss?
2020-11-18T21:32:44 #kisslinux <kqz> i do, but im also probably one of the only ones who uses pulseaudio here ;p
2020-11-18T21:44:04 #kisslinux <micr0> kqz full pulseaudio or apulse?
2020-11-18T21:44:38 #kisslinux <micr0> i mean its just 2 libraries (libflac libsndfile) and one package (pulseaudio), so I'm willing to try it
2020-11-18T21:51:16 #kisslinux <micr0> ok so pulseaudio build and installed fine, and parecord worked fine, so thats promising
2020-11-18T21:51:26 #kisslinux <micr0> i guess i have to fork firefox and remove the --disable-pulseaudio line and try that
2020-11-18T21:53:50 #kisslinux <sh4rm4^bnc> why would one need a microphone in firefox ?
2020-11-18T21:54:37 #kisslinux <sh4rm4^bnc> to have big brother listening to all your conversations ?
2020-11-18T21:56:18 #kisslinux <micr0> yes exactly
2020-11-18T21:58:33 #kisslinux <kqz> just full pulseaudio
2020-11-18T22:15:26 #kisslinux <micr0> got i love modern infra /s
2020-11-18T22:15:52 #kisslinux <micr0> easier to run a cli from a container image than yknow, just curl shit with the correct tokens :(
2020-11-18T22:16:20 #kisslinux <micr0> because big cloud can't just package their tools correctly and have to write their own installed with precompiled binaries
2020-11-18T22:18:23 #kisslinux <micr0> related to the pulse question - anyone have screensharing working under wayland? I think the two paths are xdpw+pipewire or obs-studio+virtualcam, but i dont see any packaged pipewire/xdpw for kiss
2020-11-18T22:26:45 #kisslinux <dan[m]> have the firefox binary packages gone?
2020-11-18T22:28:07 #kisslinux <mcpcpc[m]> dan: for a while now.