💾 Archived View for gemini.ctrl-c.club › ~phoebos › logs › kisslinux-2022-01-22.txt captured on 2022-07-17 at 03:04:37.
⬅️ Previous capture (2022-03-01)
-=-=-=-=-=-=-
[2022-01-22T05:03:33Z] <testuser[m]> Hi
[2022-01-22T06:24:48Z] <testuser[m]> https://fuchsia.dev/fuchsia-src/contribute/respectful_code
[2022-01-22T06:52:54Z] <tleydxdy[m]> doesn't even have dark mode, my eyes are violated
[2022-01-22T06:55:47Z] <testuser[m]> Hey that's called night mode
[2022-01-22T13:05:28Z] <Guest7849> Hello!
[2022-01-22T13:06:28Z] <testuser[m]> Hi
[2022-01-22T13:08:00Z] <Guest7849> Is it a good idea to install grub from outside the kiss chroot? ive just heard that its not very reliable
[2022-01-22T13:08:31Z] <testuser[m]> just try it bruh
[2022-01-22T13:55:00Z] <Guest7849> OK I got it installed but it says Loading Linux 5.16.2 ... and nothing else, and my caps lock button is flashing
[2022-01-22T13:55:33Z] <Guest7849> I've never seen this issue before
[2022-01-22T14:06:53Z] <Guest7812> Hey sorry I got disconnected
[2022-01-22T14:13:46Z] <Guest7816> Oh my it happened again, just a quick one, if I wanted to load all of the firmware in the firmware tarball, would I do "cp ./* /usr/lib/firmware" from inside the extracted tarball of firmware
[2022-01-22T14:17:25Z] <Guest7816> hello
[2022-01-22T14:22:41Z] <soliwilos> Hello.
[2022-01-22T14:22:51Z] <Guest7816> Hmm maybe my kernel is broken
[2022-01-22T14:23:31Z] <soliwilos> That would be unfortunate.
[2022-01-22T14:25:30Z] <Guest7816> Yeah I'm getting a kernel panic, it sucks.
[2022-01-22T14:30:36Z] <Guest7897> Oh my why does it continue to disconnect me
[2022-01-22T15:59:09Z] <Guest7864> Got another kernel panic. Very confused by this now
[2022-01-22T16:09:05Z] <Guest7864> I have an initramfs and everything but I still get a kernel panic despite everything being built into the kernel (no modules)
[2022-01-22T16:09:43Z] <testuser[m]> Show
[2022-01-22T16:10:46Z] <Guest7864> The only things displayed on the screen is "Loading Linux 5.16.2..." and the caps lock flashes.
[2022-01-22T16:13:56Z] <Guest7864> Wait where are the kernel images stored after they are installed?
[2022-01-22T16:14:25Z] <testuser[m]> They don't install themselves
[2022-01-22T16:14:27Z] <testuser[m]> I think
[2022-01-22T16:14:38Z] <testuser[m]> u need to copy arch/x86/bzImage
[2022-01-22T16:14:49Z] <Guest7864> Oh wait really
[2022-01-22T16:15:02Z] <Guest7864> is that copy it to /boot?
[2022-01-22T16:19:22Z] <Guest7864> tried copying bzImage to /boot. same result
[2022-01-22T16:20:07Z] <Guest7864> My esp is mounted at /boot/efi if that makes any difference
[2022-01-22T16:21:41Z] <Guest7864> Apparently the vmlinuz file is the bzImage? but that was already in /boot
[2022-01-22T16:42:57Z] <Guest7864> I'm just gonna restart and follow a YouTube guide, I probably missed out something stupid
[2022-01-22T17:16:07Z] <Guest7864> Oh my ram was made to use SwapOnZRAM idk if that breaks stuff
[2022-01-22T18:03:04Z] <dilyn> Guest7864: so you are mounting your FAT32 formatted partition to /boot/efi?
[2022-01-22T18:03:15Z] <dilyn> are you using grub or efibootmgr directly to boot?
[2022-01-22T18:03:28Z] <Guest7864> I restarted my install, im using /boot now
[2022-01-22T18:03:37Z] <dilyn> okay
[2022-01-22T18:03:57Z] <dilyn> a minimal, simple way to boot and make sure your kernel works fine is to just use efibootmgr directly
[2022-01-22T18:04:19Z] <Guest7864> Though what I overlooked is that my ram is set to function as swap space and not as regular ram so I've fixed that in my fstab and hopefully it fixes things
[2022-01-22T18:04:21Z] <dilyn> after building the kernel, move the arch/x86/boot/bzImage file /boot
[2022-01-22T18:05:10Z] <Guest7864> I thought it was vmlinuz that was the image and and it was moved by make install in kernel source directory
[2022-01-22T18:05:47Z] <dilyn> make install presumably copies all the relevant things to the relevant locations (specifically, I think the default is /boot and /usr/local/lib)
[2022-01-22T18:06:00Z] <dilyn> so if you're using modules you're right to use make install
[2022-01-22T18:06:16Z] <Guest7864> I'm specifically avoiding modules LOL
[2022-01-22T18:06:26Z] <dilyn> then you can just copy the bzImage file
[2022-01-22T18:06:45Z] <Guest7864> alright, and leave the System.map and vmlinuz where they are?
[2022-01-22T18:06:51Z] <dilyn> mmhmm
[2022-01-22T18:07:12Z] <dilyn> you just need the bzImage file, which would be an EFI executable file (if you care to inspect it with `file bzImage`)
[2022-01-22T18:07:15Z] <Guest7864> Sounds good, was also wondering if the system expects ram to be present
[2022-01-22T18:07:26Z] <dilyn> you would certainly need RAM
[2022-01-22T18:07:39Z] <Guest7864> because my ram is swap space
[2022-01-22T18:07:39Z] <dilyn> but the settings in your fstab aren't relevant until after the kernel is loaded and execs /sbin/init
[2022-01-22T18:08:21Z] <Guest7864> My arch install loads up fine with zram, I just don't know how it interacts with other systems.
[2022-01-22T18:09:11Z] <dilyn> https://github.com/kiss-community/wiki/tree/master/storage this is how I handled zram and zswap on KISS
[2022-01-22T18:10:11Z] <dilyn> you could also change the loglevel of your kernel (it might be set to a value where you can't actually see a panic happening?)
[2022-01-22T18:10:30Z] <Guest7864> Right, I thought RAM was wiped on a restart.
[2022-01-22T18:11:08Z] <Guest7864> I would rather not use Zram as I have more than enough RAM to handle my system. I just don't know how to revert it back
[2022-01-22T18:11:28Z] <dilyn> either way from there I would just use efibootmgr real quick to test, and do `efibootmgr -c -d /dev/sda -p 1 -L KISS -l '/bzImage' -u 'root=/dev/sda2 rw'`, assuming your device is /dev/sda and your ESP is /dev/sda1, you named your kernel in /boot bzImage, and your root filesystem is on /dev/sda2
[2022-01-22T18:11:39Z] <Guest7864> thanks for that link though, its very useful
[2022-01-22T18:11:53Z] <dilyn> your zram should be turned off when you poweroff :V
[2022-01-22T18:12:29Z] <Guest7864> Yeah but is it zram forever because I used genfstab for my fstab and it reports zram
[2022-01-22T18:13:07Z] <Guest7864> I'm sorry if these questions are redundant, I really don't know a whole lot about ZRAM
[2022-01-22T18:14:36Z] <dilyn> zram is just some block device -- optimally, you would have some number of zram devices which total together to equal your total amount of RAM
[2022-01-22T18:15:07Z] <dilyn> for instance I wrote that zram article on an 8GB laptop, and so my example creates 4 zram block devices of 2G in size
[2022-01-22T18:15:16Z] <Guest7864> Yeah I think my RAM is all one device
[2022-01-22T18:15:21Z] <Guest7864> its all /dev/zram0
[2022-01-22T18:15:56Z] <dilyn> it doesn't so much matter how many devices you have nowadays anyways
[2022-01-22T18:16:12Z] <Guest7864> is there not a way I can revert my zram to work as normal ram again
[2022-01-22T18:16:16Z] <dilyn> it was more relevant during earlier releases but it's become far more efficient nowadays
[2022-01-22T18:16:33Z] <dilyn> you would start here https://github.com/kiss-community/wiki/blob/8a55f77fd3d2bb708f1a528e0769780e31b11d36/storage/zram.txt#L98
[2022-01-22T18:16:41Z] <dilyn> or just disable it in the kernel
[2022-01-22T18:17:20Z] <Guest7864> If I disable it in the kernel does it ignore that its made to be zram and just functions as normal RAM?
[2022-01-22T18:17:46Z] <dilyn> well it's not made to be zram until you hit userspace and init mounts all the filesystems specified in /etc/fstab
[2022-01-22T18:18:22Z] <Guest7864> Oh thats super weird, maybe my livecd mounted my ram as ZRAM automatically then?
[2022-01-22T18:18:57Z] <dilyn> presumably your live cd didn't build zram as a module and instead built it in, in which case only a single block device is created unless some other number is specified in the kernel command line
[2022-01-22T18:19:00Z] <Guest7864> It's Fedora I don't know if they are big advocates of zram
[2022-01-22T18:19:36Z] <Guest7864> Oh thats interesting
[2022-01-22T18:24:09Z] <zazpro> Hey guys is there anyone who's using Nvidia gpu?
[2022-01-22T18:24:56Z] <jslick> idk about "big advocates", but I'd say advocates to some degree - https://fedoraproject.org/wiki/Changes/SwapOnZRAM#Benefit_to_Fedora
[2022-01-22T18:30:16Z] <testuser[m]> zazpro: what do u wanna know
[2022-01-22T18:33:21Z] <zazpro> testuser[m]: Just installed system on my main pc. When trying to run sway I get. EGL_NOT_INITIALIZED error
[2022-01-22T18:33:36Z] <zazpro> DRI2 failed to create server
[2022-01-22T18:33:57Z] <zazpro> I guess problem is in missconfigured kernel or in the driver?
[2022-01-22T18:34:26Z] <dilyn> I can't believe there isn't a rewrite of wl-clipboard in go...
[2022-01-22T18:34:29Z] <dilyn> Guess I have a project
[2022-01-22T18:46:49Z] <Guest7864> Hey this is probably stupid but in /usr/lib/firmware am i meant to have the contents of the linux firmware folder i extracted or the linux firmware folder?
[2022-01-22T18:51:15Z] <acheam> contents
[2022-01-22T18:51:28Z] <Guest7864> Thanks
[2022-01-22T18:51:50Z] <acheam> testuser[m]: bruh
[2022-01-22T18:52:27Z] <acheam> > blackout
[2022-01-22T18:52:54Z] <acheam> since when was this word race related?
[2022-01-22T18:56:37Z] <dilyn> Most English words which incorporate 'black' are negative, pejorative, or derogatory, and can be contrasted with their counterpart words; these words are almost assuredly identical with black swapped out for white, and these antonyms are just that
[2022-01-22T18:56:54Z] <dilyn> Essentially, black{foo} is associated with a negative thing
[2022-01-22T18:57:14Z] <dilyn> From there, you can analyze it however you want; psychology, history, etymology...
[2022-01-22T18:58:10Z] <dilyn> it's less about racism than it is about "We can describe this scenario without using a term that clings to historically codified tropes in white countries where black == bad && white == good, so why wouldn't we do that"
[2022-01-22T18:59:33Z] <dilyn> I like their point at the end about idioms: "Prefer descriptive and factual statements instead of idioms." This I think is a more salient argument for those who merely think that these sorts of requirements are purely that "racism bad and {slave,blackout,...} are racist because {history,black,...}"
[2022-01-22T19:15:15Z] <testuser[m]> zazpro: ur using gkiss? Did u enable the modeset parameter
[2022-01-22T19:15:27Z] <testuser[m]> dilyn: why in go?
[2022-01-22T19:15:38Z] <dilyn> because I don't like rust
[2022-01-22T19:15:47Z] <dilyn> neither building rust itself, nor the things written in it
[2022-01-22T19:15:59Z] <testuser[m]> Bruh wl-clipboard is in c
[2022-01-22T19:16:04Z] <dilyn> and the C implementation is GPL:P
[2022-01-22T19:16:12Z] <testuser[m]> Bruh
[2022-01-22T19:16:33Z] <zazpro> No I am not using gkiss as I don't know what's that. And which modeset stuff should I do?
[2022-01-22T19:18:03Z] <testuser[m]> Are u using nouveau?
[2022-01-22T19:18:10Z] <testuser[m]> Wat gpu
[2022-01-22T19:18:43Z] <zazpro> I have enabled nouveau in the kernel I think. Gpu: gtx1080
[2022-01-22T19:19:39Z] <testuser[m]> dilyn: what do you think of stuff like crazy -> unexpected, incoherent
[2022-01-22T19:20:03Z] <testuser[m]> zazpro: Bruh i don't think nouveau will work at all for that card
[2022-01-22T19:20:09Z] <testuser[m]> U need proprietary driverd
[2022-01-22T19:20:32Z] <testuser[m]> zazpro: https://github.com/gkisslinux/grepo
[2022-01-22T19:21:57Z] <zazpro> Understood, thanks :)
[2022-01-22T19:53:14Z] <noocsharp> seems like a good idea to use more precise terms than crazy in technical discussions
[2022-01-22T22:31:31Z] <acheam> dilyn: are there no permissive compilers?
[2022-01-22T23:34:20Z] <phinxy> Any pointers on how to install a python module "properly"? Should it be done with kiss? https://github.com/quodlibet/mutagen
[2022-01-22T23:35:31Z] <phinxy> Perhaps I'll go with PIP.
[2022-01-22T23:41:08Z] <phinxy> Pip put stuff in /usr/bin, not sure what I feel about that
[2022-01-22T23:41:52Z] <jslick> grep for "setup.py" in community, e.g. https://github.com/kiss-community/community/tree/main/community/python-psutil
[2022-01-22T23:43:26Z] <acheam> venvs