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
calebccff has quit [Remote host closed the connection]
calebccff has joined #aarch64-laptops
davidinux has quit [Quit: WeeChat 4.3.1]
initard[m] has joined #aarch64-laptops
Caterpillar has quit [Remote host closed the connection]
alfredo1 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
srinik has quit [Ping timeout: 480 seconds]
srinik has joined #aarch64-laptops
nothorseface has joined #aarch64-laptops
nothorseface has quit [Read error: Connection reset by peer]
alfredo has quit [Ping timeout: 480 seconds]
<wizzard>
Hi, has anyone noticed, that since 6.12-18 the external monitor (usb c to hdmi) support has goten worse? TTY works fine for me, but sway is the only DE which does not crash. When logging in there is some static, before the image is correct. After suspend I need to toggle the screen of and on to make it output anything. This is accompanied by a low pitch and then high pitch whining in my screen.
<wizzard>
Also I lost the abillity to change the brightness of the t14s screen since I upgraded to the 6.12 kernel
<wizzard>
Is anyone going to 38C3 and interested in talking about our endeavors 🙂
<Jasper[m]>
Yep
<JensGlathe[m]>
Uh...just compiling 6.12.0-18. Did a few tests with 6.12.0-16 and it generally worked fine. Or lets say "behaves well enough". To reliably enable external display you need to boot it with adapter plugged in (yigh), hot-plug is a gamble with diminishing chances.
nothorseface has joined #aarch64-laptops
<JensGlathe[m]>
stacked up on other adapters: type-c to HDMI/VGA/DVI/USB combo, and a type-c to dp 8k cable.
<wizzard>
Shall we organise a banner or a table or something? Is there anything planned? I would like to have a sign or something better. Lets not spam the chat here: We can brainstorm in this pad: https://t1p.de/aarch64at38C3
<wizzard>
jensGlathe[m]: I should try that. Using 6.12-20 my process of booting is the following. Remove all external devices. Insert the one usb stick, which makes grub not crash. Boot. There will be a kernel panic and a rescue shell. Force Reboot. Now Grub shows up. Boot the first entry. Wait for GDM to show up. Unplug the USB Stick. Connect the USB-C to HDMI hub. Login.
<JensGlathe[m]>
Oh this sounds hacky
<JensGlathe[m]>
T14s 64GB I assume
<wizzard>
The kernel crash has only started to occur since 6.20. No I am using the 32GB Version.
<tobhe>
wizzard: I'll be at 38c3
<tobhe>
and I reverted the brightness control because it broke the oled model
<tobhe>
we probably need separate dts for those...
<wizzard>
I would be really grateful if I could help and contribute a bit at 38C3. I am using the T14s as my daily driver 🙂 If you are also interested, I could check if we can have a table at the cluster I am part of. I would hope that some publicity will bring us more hackers. If you have any ideas you can write them into the pad I linked above.
srinik has quit [Ping timeout: 480 seconds]
derzahl has joined #aarch64-laptops
<derzahl>
anyone know of a newish bootable img for getting linux on a c630? Just ran the lenovo windows restore since something got boned way back when
<derzahl>
also is there any reason to bothing updating windows to get latest firmware etc? I have a dump of firmware extracted from the windows install from a couple years ago
<spawacz>
is there some builtin loudness equalization in x13s? the audio through the headphone jack sounds so odd, the volume is going up and down like on stairs. It doesn't happen when headphones are plugged to a dock and dock to the laptop
<steev>
derzahl: i don't... i would *guess* that a new enough debian installer iso should work at this point?
<steev>
as lonng as the dtb is available
<derzahl>
steev: from 2021? yeh thats all i could find
<derzahl>
ok, its a starts
<steev>
i meant the actual debian installer
<steev>
not bookworm though, a trixie/testing/sid one
<steev>
i should try that here soon, i want to redo my system now that i've got a much firmer grasp of things than when i first got my c630
<derzahl>
steev: did you ever figure our what all those other little disks and partitions are for? In windows its actually showing that I have a "disk" with 13GB unallocated space
<steev>
no, i meant from debian.org - trixie and newer should have a 6.11+ kernel which should have all the support (iirc)
<derzahl>
oddly when i right click on the windows partition and select shrink nothing happens at all...no popup dialog
<derzahl>
ohh ok
<steev>
they're... various TZ related stuffs
<derzahl>
so pretty much anything with a 6.11+ kernel and the dtb should work then?
<steev>
the only thing i can think of is that they don't have enough room on the boot/efi partition for the dtb file, so you might have to do some weirdness with the partition to expand it to put the dtb on there. i keep meaning to ask about that in debian-arm
<steev>
the support has been in since ~6.7? but 6.11 got the audio fixes (or maybe it was 6.12 and backported to 6.11 stables)
chrisl has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<Jasper[m]>
@spawacz it gets fucky over some volume amount.
<Jasper[m]>
Calibration for audio hasn't been done yet so these are semi-safe defaults
sally has quit [Remote host closed the connection]
<HdkR>
The headphone jack is trying to be safe? Does it have some sort of impedance measurement circuit so it doesn't just assume crappy low-end headphones or something?
sally has joined #aarch64-laptops
<Jasper[m]>
There's some amp before it aswell
<Jasper[m]>
And iirc it just hasn't been calibrated yet either
<HdkR>
I haven't tried it, but that sounds like if I plug in my 800ohm headphones, then I'll basically get zero sound :D
<spawacz>
Jasper[m]: what component of the system is reponsible for that behavior? Is the the audio player, pulseaudio, the driver, or firmware?
<Jasper[m]>
<HdkR> "I haven't tried it, but that..." <- I have plugged in my hard to drive headphones aswell and it still messes up above 30% vol
<Jasper[m]>
spawacz: I've had behaviour change between pw and pa, but it's janky regardless
<HdkR>
Huh, interesting
<spawacz>
Hm, I don't mean glitches and screeching sound - that happens under pipewire. With pulseaudio the sound is perfectly smooth and continuous, but the volume jumps abruptly
<spawacz>
so when a sound fades and gets quieter, I actually hear it jump in volume up and up 5 times before it ends
alfredo has quit [Quit: alfredo]
<gwolf>
steev: I recall your modified d-i image copied over some firmware from Windows. I guess that will still be required if installing from a regular d-i
<steev>
ah, yeah we still don't have c630 firmware in linux-firmware huh
<gwolf>
And... Well, I have kept hand-copying dtbs per kernel...
<gwolf>
So d-i should do a good portion of the work... But we should ™ document what is needed to actually get a working system...
<derzahl>
i dont think the c630 firmware is required for install right? just wifi
<derzahl>
anyway, i extracted the sdm845-lenovVsfjlnvd.dtd for the aarch64 debian iso kernel package, put it on a usb drive with ventoy and the debian iso and then loaded linux,initrd, and devicetree from grub cmdline. it didnt like that any better
<derzahl>
so im back to using the old shawnguo image
<JensGlathe[m]>
I added the RTC patches, but it didn't want to initialize. On 6.12.0-18 it works
jhovold has quit [Ping timeout: 480 seconds]
derzahl has quit [Ping timeout: 480 seconds]
<TheBITLINK[m]>
aren't some kernel modules and command line arguments required for it to actually boot?
<TheBITLINK[m]>
I installed Debian the other day, but I started from the Ubuntu Concept live USB, installed debootstrap and set everything up manually, couldn't bother trying to get the Debian installer to boot
todi has quit []
<JensGlathe[m]>
Ubuntu concept gets by without the cl arguments. No idea how, didn‘t look into the qcom-settings package. But apparently there’s a way