libera/#devuan/ Wednesday, 2023-11-01

yauzOk, Devuan install completed successfully and my initial hope bears out. I originally setup the machine (Alix: 500 MHz Geode (Pentium class) with 256M RAM and CF card for OS) with Debian Bookworm. But the minimal installation (only ssh service, no graphics) was already 78M into swap after boot & login via serial console, mostly due to the systemd stack. Reinstall the same machine with Devuan Daedalus and00:31
yauzafter boot and ssh login: no swap used, 160M RAM free. I call that a solid win for a very small machine.00:31
KZSAZOTrying to share my screen to OBS Studio but I'm getting this "Failed to connect PipeWire context" error (https://i.imgur.com/yg52jl1.png), PipeWire is installed by default but I guess I need to configure something to make it work, any ideas? I'm running on Devuan 5, Plasma on Wayland and latest OBS Studio flatpak01:06
gnarfaceKZSAZO: group membership maybe? dunno01:25
gnarfacetry to find a log entry that's more verbose01:25
gnarfaceyauz: you can also try changing "MODULES=most" to "MODULES=dep" in /etc/initramfs-tools/initramfs.conf then running update-initramfs -u (and rebooting)01:27
gnarfacethat should lower the memory usage, hopefully it's accurate and doesn't cripple your booting...01:27
dan9erI can't connect to devuan.onion since a few hours ago. Aptitude is giving "SOCKS proxy socks5h://127.0.0.1:9050 could not connect to 2s4yqjx5ul6okpp3f2gaunr2syex5jgbfpfvhxxbbjwnrsvbk5v3qbid.onion (0.0.0.0:0) due to: Host unreachable (4) [IP: 127.0.0.1 9050]"02:18
dan9erIt appears that 2s4yqjx5*.onion is down, and the load balancer is refusing to switch off of it02:21
dan9erRestarting tor or aptitude doesn't fix it02:21
dan9erCancelling actions in aptitude & trying to redownload didn't fix it02:25
dan9erWell I cancelled actions, restarted tor, then tryed to redownload, still stuck on 2s4yqjx5*.onion02:33
dan9ers/tryed/tried/02:33
dan9erHow often does devuan.onion rotate?02:37
rrqrotate?03:45
dan9errrq: Swap out a mirror used for a package for another15:14
dan9erIt's now the next morning and it looks like it rotated away from the bad onion mirror15:14
AnOldHackerI got things working.  A couple of issues.  Of course, the EFI load path mess.  But also, if a boot partition is created by fdisk or gdisk, its size is not read--even after a reboot.  I had to clear the EFI bit & let the installer set it up.  Of course, the first one I created WAS read somehow.  And I created it with 1M, which had its own problems...  (Dell Latitude where I blew away the partition table without understand what was happ17:04
AnOldHackering...)17:04
AnOldHackerAlso, when I turned the flag off but something something, I got "Unknown filesystem" from grub-install.  I'm wondering now, however, if mount was reading data from the NVRAM that was not being updated.18:09

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!