ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
Lucanis has joined #aarch64-laptops
janrinze has quit [Quit: Leaving.]
janrinze has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
rmsilva_ has joined #aarch64-laptops
rmsilva has quit [Ping timeout: 480 seconds]
<clover[m]>
:) this was the missing grub env variable that fixes grub-mkconfig not finding my initrd:
janrinze has quit [Remote host closed the connection]
hightower2 has joined #aarch64-laptops
systwi_ has joined #aarch64-laptops
<steev>
probably
<steev>
and, good to know about the initial rebase
systwi has quit [Ping timeout: 480 seconds]
jhovold has quit [Quit: WeeChat 3.8]
agl7 has joined #aarch64-laptops
Erisa has quit [Remote host closed the connection]
Erisa has joined #aarch64-laptops
<agl7>
Good Evening! (It's 11:05 pm in Europe/Germany)
<agl7>
steev: Have you updated your Linux kernel? I ask, so I want to get it, compile it and test it.
<agl7>
It's two week ago where I get the last Linux kernel from you.
systwi has joined #aarch64-laptops
systwi_ has quit [Ping timeout: 480 seconds]
<steev>
i'm about to push 6.3.7
<clover[m]>
I updated my EndeavourOS tutorial. It's a lot shorter now and includes a grub tutorial
<cenunix[m]>
Does anyone know how the qrtr package works ? when starting qrtr-ns, I get the output: nameserver already running, going dormant: Address already in use
<cenunix[m]>
No idea how I can check what is using the address/debug this
<bamse>
cenunix[m]: qrtr-ns keeps track of what services/protocols are registered in the system...it started out in userspace in the form of qrtr-ns...but was later implemented in the kernel as well
<bamse>
cenunix[m]: so "Address already in use" means that your kernel already does the ns'ing
<bamse>
cenunix[m]: you can use qrtr-lookup to query the ns...so that should give you something or at least not fail...
<bamse>
cenunix[m]: and the "going dormant" thing is to keep systemd happy and continue to run the dependent services
<bamse>
perhaps there's a saner way to say "depends on the qrtr-ns service, if that is enabled, otherwise not"?