ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Chrome OS Trogdor Devices - Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630 - Lenovo ThinkPad X13s - and various other snapdragon laptops) - https://oftc.irclog.whitequark.org/aarch64-laptops
DanielSchfer[m] has joined #aarch64-laptops
smpl has quit [Ping timeout: 480 seconds]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
clee_ has joined #aarch64-laptops
iivanov_ has joined #aarch64-laptops
iivanov has quit [Read error: Connection reset by peer]
clee has quit [Ping timeout: 480 seconds]
jhovold has joined #aarch64-laptops
<MrCatfood[m]>
<sera[m]> "Here's the arch image if you..." <- it looks like the file is broken
<sera[m]>
I will reupload it on a more permanent host once the wifi is tested and I get the blobs
srini_ has joined #aarch64-laptops
indy has quit [Ping timeout: 480 seconds]
<Painkiller995[m]>
.sera: Hey, thanks. I’m still trying to download it, even though I’m at work. Waiting for the new link. 😊
indy has joined #aarch64-laptops
pstef has quit [Read error: Connection reset by peer]
pstef has joined #aarch64-laptops
srini_ has quit [Remote host closed the connection]
pstef has quit [Read error: Connection reset by peer]
pstef has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
iivanov_ has quit [Ping timeout: 480 seconds]
exeat has quit [Remote host closed the connection]
Sayatomoki[m] has joined #aarch64-laptops
<Sayatomoki[m]>
I can't boot after upgrading the kernel
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
<Jasper[m]>
<Sayatomoki[m]> "at 6.9.2? it can" <- I mean 6.10
<Jasper[m]>
You're dropped in a rescue shell I think
<Sayatomoki[m]>
how can i list devices at 6.10, liveusb?
<Jasper[m]>
<Sayatomoki[m]> "ima_d7d5677.jpeg" <- In this state you may be able to do some stuff
<Sayatomoki[m]>
Jasper[m]: i can’t input anything and it well black screen after a few second
<FarchordSteveCossette[m]>
<sera[m]> "I left the lenovo ones since you..." <- What's the instructions to get those files again? The pastebin they were in has expired
<FarchordSteveCossette[m]>
Aiite the initial instructions didn't work, it didn't find the ID, so I'm gonna use the fw tool now
<sera[m]>
What's the log contents?
<Jasper[m]>
<Sayatomoki[m]> "i can’t input anything and it..." <- Oh, that's a shame. Sounds like it doesn't have the modules compiled into the initramfs that you need it to work
<sera[m]>
Hmm yeah it wants the board-2, then the steps I wrote before should work
<FarchordSteveCossette[m]>
Still says same thing even after running the tool
<sera[m]>
You added the the specific string to board-2 using the tool?
<FarchordSteveCossette[m]>
I downloaded the board-2.bin from the git repo in the pastebin, and my board.bin. Then, I ran the tool with the ID it couldn't find (From that dmesg)
<FarchordSteveCossette[m]>
<sera[m]> "oh wait, that's the wrong one..." <- XD Thank you so much for your help. Once that's all done and we got (most) things working I'm gonna put a wiki or something
<FarchordSteveCossette[m]>
Another thing is, seems the clock is working in arch lol on Fedora it keeps resetting to 00:00
<Sayatomoki[m]>
<Jasper[m]> "then regenerate mkinitcpio" <- which should I replace? /boot/initramfs-linux.img or /boot/initramfs-linux-x13s.img
<travmurav[m]>
Farchord (Steve Cossette): dunno how they do it on new ones but rtc was always a mess on those things since qcom's in-pmic rtc is always read-only because firmware locks you out of it, so one needs to store the offset somewhere, afaik nowdays kernel uses the special efivar for it, that uefi leaves with correct offset
<travmurav[m]>
on phones in pmOS we have a script to do swclock-offset since the rtc still ticks but it only ticks from epoch
<f_>
steev, abby: ugh
<robclark>
hmm, is that why the date on my 7x (before I had network working) was ~1mo behind despite being correct in bios?
<travmurav[m]>
robclark: I think the pmic rtc would usually report "start of time" (1970) + how much time the pmic was powered so 1 month would be a weird value...
<robclark>
I guess that was the amount of time btwn device getting manufactured and when I received it?
<FarchordSteveCossette[m]>
robclark: do you have a general list of configs in the kernel that has to be specifically enabled for the snapdragon line?
<robclark>
I'd kinda forgotton about that, since ntp papers over it.. but kinda tripped me up a couple times trying to rebuild kernel when forgetting to manually update the date
<FarchordSteveCossette[m]>
I know you sent the configs, I just wonder if there's a list of specifics, proper to the x1 laptops
<robclark>
I think the closest thing is the x1e defconfig, but that isn't a specific list
<robclark>
and iirc it had a lot more things =y which probably could be =m
<travmurav[m]>
$ sudo hwclock
<travmurav[m]>
1970-01-06 13:57:21.103198+05:00
<travmurav[m]>
I guess mine tracks the time since the last moment I took the battery out when disassembling it...
<travmurav[m]>
but this is 7c
<robclark>
maybe abelvesa or jhovold has some input for distro kernel config?
<travmurav[m]>
absolutely no idea if they changed how rtc works now
<FarchordSteveCossette[m]>
robclark: No worries, I'm trying to get a specific list of _what to enable_ if that makes sense, to have Fedora's kernel team enable it
<robclark>
travmurav[m]: hmm, "Cannot access the Hardware Clock via any known method." on x1e (yoga 7x)
<jhovold>
robclark: the rtc is not yet enabled in dt for x1e80100
<robclark>
ahh
<jhovold>
some unresolved tz permission issue
<robclark>
ok, that would explain
<konradybcio>
i think ive seen some i2c rtc in the t14s dt
<konradybcio>
dsdt*
<kettenis>
I would be really surprised if the rtc on the t14s is different from the other x1e laptops
<kettenis>
vivobook defenitely is "counter in pmic + offset in UEFI variable"
<kettenis>
like the x13s
<nirik[m]>
ha, my 7x was orig scheduled for mid aug, then end of july, now arriving monday.
<JensGlathe[m]>
one reason why I'm mostly on matrix. We use it at work, too. With threading
<FarchordSteveCossette[m]>
Matrix has its issues ofc. But its lightyears ahead of irc
<travmurav[m]>
eh I guess the bridge just choked composing a reply to a rich text message, but also I guess time to make a friendly reminder that while you keep your matrix side messages simple, theyre getting bridged fine, this is a portal'd IRC room, not a matrix-first and excessive use of rich text will make things sad for a big portion of the users here
<travmurav[m]>
and some things like reactions and deletions won't be bridged at all
<steveej[m]>
<steev> "reason=4 "Disassociated due to..." <- it also says "locally_genrated=1"
<steveej[m]>
> reason=4 locally_generated=1
<steveej[m]>
i'm sure my wifi wasn't inactive at the time
<abby>
edits sometimes get bridges as repeating the whole message
<abby>
s/bridges/bridged/
<travmurav[m]>
yeah excessive edits may get spammy on the irc side too
<steev>
steveej[m]: that's definitely odd, that typically means you lost connection ot the AP, and then when you tried to scan for it, it didn't see it
<abby>
matrix-appservice-irc has gotten PRs for implementations of a way to limit bridged matrix rooms to certain features, but they haven't merged any of it
<steev>
open source vendor lock in
<konradybcio>
open source limit cpu usage technology (tm)
<travmurav[m]>
but well, just common sense and looking at how messages got bridged via oftc.irclog.whitequark.org/aarch64-laptops will make everyone less annoyed with the bridge, the bridge tries it's best after all and we still can talk using our favorite tools <3
<pstef>
boomer speaking here, but I never got the appeal of matrix. Seems different just for the sake of being different/new
<lollaritits[m]>
fluffychat doesnt have threads
<lollaritits[m]>
luckily
<steev>
emojis are the future!
<steev>
my boss likes to use threads for everything, which would be fine if he didn't respond to things once a day, so right as i'm about to head to bed, i suddenly have 54 new messages
<JensGlathe[m]>
boss move
<steev>
it really is. but it makes me think something huge is going on that needs my attention
<travmurav[m]>
<abby> "matrix-appservice-irc has gotten..." <- at least reactions and deletions seemingly can be blocked via power levels, I guess those are the only ones that don't get bridged at all
<travmurav[m]>
but well, offtopic
<amstan>
Jens Glathe, Farchord (Steve Cossette) yeah please don't spam with matrix only features, most people here are on irc
<amstan>
travmurav: you too
<amstan>
no more replies pls, it's really stupid how verbose they get
<FarchordSteveCossette[m]>
Mmm ok
<amstan>
i can block things you say?
<FarchordSteveCossette[m]>
I said ok, did I say something wrong? I wont reply anymore, I promise
<amstan>
nope, i can't change room permissions, only the bot can do that
<amstan>
pstef: for irc i like using it because it's a free bouncer and then it's only one app for everything
<amstan>
steev: the only thing i will excuse is "the full message at" for long examples of code. it's handier than a pastebin
<steev>
that is true
<steev>
especially nowadays where it's getting harder and harder to find a pastebin that even accepts long amounts of code (like a dmesg output)
<abby>
0x0.st is my go-to
<amstan>
my goto used to be bpaste.net, but i've stopped caring if it works or not with matrix
<FarchordSteveCossette[m]>
I just use fpaste and the centos pastebin, works fine
<travmurav[m]>
tbh I think replies get bridged fine enough most of the time but I do try to manually format them when I see the context will be lost when it only bridges first 3 words but otherwise not sure what did I contribute to the spam since I try to avoid matrix things in irc portals :(
<amstan>
travmurav: they do not, you just get a whole copy of the previous message, so by the time your reply comes it'll be a "full message at" link
<travmurav[m]>
no, it's only for rich text ones
<travmurav[m]>
so i.e. if the message you reply to had code blocks or other things, the reply will yield garbage. If you reply to plain message, it's fine-ish
<FarchordSteveCossette[m]>
But that's a fedora thing
<FarchordSteveCossette[m]>
.sera: So, I'm working on my fedora install right now, trying to fix the keyboard and mouse. Jens Glathe suggested I add i2c_hid_of and i2c_qcom_geni to the mkinitcpio image, which I did. But now, my USB-C root drive fails to mount XD
<FarchordSteveCossette[m]>
How can I see which modules you put in yours, on the drive you gave me?
smpl has joined #aarch64-laptops
<steev>
lsinitcpio or some such might exist?
<FarchordSteveCossette[m]>
steev: yeah ill have to see what package offers that on arch and install it. I'm taking a break right now I've been doing this non-stop for way too long lol
paddymahoney has quit [Remote host closed the connection]
<steev>
should be part of the same package (mkinitcpio) :)
<bamse>
went spelunking a couple of weeks ago, and now i have to fight the urge not to switch to fedora
<HdkR>
I was searching for that rfc page again :D
<bamse>
abby: right, i've been running archlinuxarm on qualcomm hardware for the last 10 years...but archlinuxarm != archlinux...and there are a lot of packages that are lagging behind
<bamse>
although that things says 10 outdated packages...did something magical happen in the last month or so?!
<HdkR>
Didn't one of the maintainers come back from a hiatus recently or something?
<bamse>
i'll have to withdraw my complaints then, this is wonderful news :)
<HdkR>
I still need to hunt a bug in building mesa for Arch x86/x86-64. Had to disable Asahi and Intel Iris due to some Arch packaging bug as far as I can tell
<HdkR>
Will be a bit frustrating to FEX's Arch users if the 32-bit libraries aren't built :D
<konradybcio>
HdkR: well that was intel's dream at one point :P
<HdkR>
Which one, ia64 or x86S? :P
<konradybcio>
the former
<konradybcio>
x86s seems like a random idea
<HdkR>
I added Telemetry to FEX because of x86s. There are some feature removals that can technically break legacy 32-bit applications
<HdkR>
So I want to capture what games hit the removed featuers
<HdkR>
ia64 was kind of nutty, no backwards compatibility plan kills momentum for consumer adoption