ChanServ changed the topic of #kisslinux to: Unnofficial KISS Linux community channel | https://kisscommunity.org | post logs or else | "An idiot admires complexity, a genius admires simplicity." -- Terry A. Davis
<riteo>
I'll go for now, bye!
riteo has quit [Quit: epic haiku moment]
micro_O has joined #kisslinux
micro_O has quit [Ping timeout: 260 seconds]
micro_O has joined #kisslinux
jikl has joined #kisslinux
<jikl>
Guys I need some help with this error
<jikl>
I have this after doing kiss update
<jikl>
"/usr/bin/kiss: line 1953: LOGNAME: POSIX requires LOGNAME be set"
<rio6>
try export LOGNAME=your_user_name before running kiss
<jikl>
Thank you, I'll try!
<dilyn>
what're you up to that LOGNAME isn't set
<jikl>
I guess i required a chroot restart
<jikl>
escaped the chroot and re-entered it and now it works
<jikl>
BTW any reason why this happens? I'm currently install KISS btw.
<dilyn>
it's only happened to me when my env has become broken in some way
<dilyn>
usually in a chroot
<jikl>
oh i see
<jikl>
seems like that case if for me too or i've just misconfigured something
<jikl>
thanks for helping :)
jikl has quit [Remote host closed the connection]
illiliti has quit [Quit: leaving]
mahmutov has quit [Ping timeout: 265 seconds]
<dilyn>
hmhmhm I think it's time to do some breaking experiments
<dilyn>
zlib-ng here we come
GalaxyNova has quit [Ping timeout: 265 seconds]
<noocsharp>
well, it appears dilyn is losing it
jikl has joined #kisslinux
<jikl>
Hi there!
<jikl>
I have another problem with mounting EFI variables
<jikl>
When doing "mount -t efivarfs none /sys/firmware/efi/efivars" I get "mount: mounting none on /sys/firmware/efi/efivars failed: Resource busy"
<jikl>
I've tried unmounting the EFI variables from outside the chroot (the actual ISO) but it stills gives me this message.
soliwilos has quit [Remote host closed the connection]
jikl has quit [Remote host closed the connection]
<dilyn>
is something already mounted to /sys/firmware/efi/efivars?
<dilyn>
i lost it long, long ago noocsharp :V
mahmutov has joined #kisslinux
GalaxyNova has joined #kisslinux
<testuser[m]>
Hi
micro_O has quit [Ping timeout: 260 seconds]
<testuser[m]>
dilyn: that's weird, RAMFS_MAGIC does overflow max value of int, but the error should be surpressed by the static cast
<testuser[m]>
of unsigned int *
micro_O has joined #kisslinux
<testuser[m]>
nvm, of int only
micro_O has quit [Ping timeout: 265 seconds]
<testuser[m]>
hmm the new chromium keeps segfaulting randomly on tab closes
<GalaxyNova>
testuser[m]: maybe try gdb
<testuser[m]>
I did
<testuser[m]>
but it didnt, and wouldnt yield anything cuz its not a debug build
<testuser[m]>
just that the problem is in the destructor views::InkDropHost::~InkDropHost()
<testuser[m]>
time to find the bug in 100000 lines of cod
<testuser[m]>
Then just put `export TERM=xterm-256color` in ~/.profile
<joplnk>
Alright
<joplnk>
That worked!
<joplnk>
Thanks.
<joplnk>
BTW, should I open an issue for this problem?
joplnk has quit [Remote host closed the connection]
joplnk has joined #kisslinux
<testuser[m]>
no
<joplnk>
ok
<testuser[m]>
netbsd curses doesn't support terminfo or something
<joplnk>
oh
<joplnk>
so..
<testuser[m]>
so wat
<testuser[m]>
just set term to xterm
<joplnk>
ok.
joplnk has quit [Remote host closed the connection]
micro_O has quit [Quit: micro_O]
<omanom>
@micro_O did you get that digital ocean droplet working with KISS?
michalsieron has joined #kisslinux
micro_O has joined #kisslinux
<micro_O>
omanom eyup
<micro_O>
was a bit painful as a failed kernel compile meant I had to destroy and start from scratch again
<omanom>
last i remember it was a grub install issue? did you end up switching to something else or was it just a quirk of their boot
<micro_O>
thankfully the virt modules were only a few
<micro_O>
I think grub wasn't the issue
<micro_O>
I documented it somewhere, maybe will turn into a wiki article
<micro_O>
key thing is, when you are in the 'rescue image', check lsmod/modprobe, and use that to determine what you need in the kernel
<micro_O>
it was basically virtio stuff
<omanom>
ah yeah good call. when i made a VM in virtualbox i did something similar... fortunately the virtualbox kernel options are pretty much all explicitly labeled
<micro_O>
i started a new server-focused repo for now, under @jedahan, and once that is doing what I want it to will maybe move it to kiss-community or whatever
<micro_O>
that will be worked on this weekend
<micro_O>
I am also fine with giving folks here shell access
<omanom>
livin' the risky life :)
<micro_O>
just link / message me public keys and username and i'll give access
<micro_O>
omanom low-risk: i dont have nothin on there right now xD
<micro_O>
and it aint my hardware
<omanom>
i'm still trying to get time put aside to finish trying to install kiss onto my rpi3
micro_O has quit [Ping timeout: 260 seconds]
<noocsharp>
"rule #1: never break userspace"
<noocsharp>
and yet my touchpad doesn't work on 5.14.1
<noocsharp>
or 5.14.2
illiliti has joined #kisslinux
jompo has joined #kisslinux
<jompo>
Hello there!
<jompo>
I'm having a question while configuring "mold"
<jompo>
It says in the documentation "To verify that mold is being used, disable binary stripping (KISS_STRIP=0) and run the following command on a newly built executable."
<jompo>
So do I need to make the KISS_STRIP variable permanent by putting it in ~/.profile or /etc/profile.d or I just have to do it once for verification?
<jompo>
P.S. can I also know how to un-mute an audio device using .asoundrc?
x4n has joined #kisslinux
<x4n>
wait? is someone online?
<x4n>
<hello!>
<x4n>
testing kirc..
jompo has quit [Remote host closed the connection]
<x4n>
This is alt of jompo talking
<x4n>
clear
<x4n>
exit
<x4n>
exit()
mulc has quit [Ping timeout: 276 seconds]
x4n has quit [Ping timeout: 265 seconds]
<soliwilos>
noocsharp: I'm on 5.14.1 and my touchpad is still working.
x3n has joined #kisslinux
<x3n>
test
<x3n>
noice
<x3n>
its finally working
x3n has quit [Remote host closed the connection]
<noocsharp>
soliwilos: we almost certainly have different touchpads
<noocsharp>
it doesn't work on 5.13.15 either
<soliwilos>
Yeah, considered adding the possibility of different drivers.
mahmutov has joined #kisslinux
<noocsharp>
time to bisect!
illiliti has quit [Quit: Quit]
michalsieron has quit [Ping timeout: 260 seconds]
<noocsharp>
nvm, they just changed the name of the i2c hid option, it works fine
<Guest73>
Find out the latest version of the NVIDIA Linux driver.
mulc has joined #kisslinux
Guest73 has quit [Quit: Client closed]
illiliti has joined #kisslinux
davidgarland has joined #kisslinux
<davidgarland>
to clarify the install instructions for EFI stubs regarding the "loader" argument, should I write like: "efibootmgr ... --loader /vmlinuz-5.14.2 ..." if my vmlinuz is directly in boot? should the argument just be "/vmlinuz" as it is per the instructions on the wiki? should I somehow have generated an EFI directory in boot that has a ".efi" file for
<davidgarland>
me to put here instead, as I see on some other sources?
gtms has quit [Remote host closed the connection]
<davidgarland>
..figured out some issues (PARTUUID and UUID are not the same thing, that "/" needs to be a "\") but still not able to get it to boot :S
<davidgarland>
is there any definitive way to know if the mistake I'm making is in the stub itself as opposed to the kernel or vice versa
jess has joined #kisslinux
<illiliti>
test, try again, test
<illiliti>
this is the only way
<davidgarland>
sad
<illiliti>
you can boot EFI shell and then boot linux
<illiliti>
> Outdated UEFI implementations may have compatibility issues with the Linux kernel. If there is a newer version of your UEFI with bug fixes, consider flashing it with the manufacturer's recommended tool.
<illiliti>
this is one of the possible reasons why efibootmgr doesn't work
<davidgarland>
ouch
<davidgarland>
I hope that's not the reason
<davidgarland>
not because updating would be a pain, but because I bought one of the Z SKU skylake boards with the intent of using a BCLK overclock, and newer firmware locks that out
dilyn has joined #kisslinux
<dilyn>
davidgarland: the loader is relative to the boot partition; think of your efi partition as being a rootfs for your UEFI
<dilyn>
so if you install vmlinuz to /boot/vmlinuz-5.13.1.efi, --loader should be /vmlinuz-5.13.1.efi