dc7800 has quit [Read error: Connection reset by peer]
martiert_ has joined #aarch64-laptops
martiert has quit [Ping timeout: 480 seconds]
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
<clover[m]>
SpieringsAE_sffis it not enough just to read /proc/device-tree/model, and then keep a map of dtb filenames for each model? or can many DTBs have the same model name 🤔
<JensGlathe[m]>
Usually not, but maybe not distinct enough (lcd/oled, hamoa/purwa maybe)
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Ping timeout: 480 seconds]
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Ping timeout: 480 seconds]
notHorseface has quit [Remote host closed the connection]
blaztinn has quit [Remote host closed the connection]
blaztinn has joined #aarch64-laptops
notHorseface has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Remote host closed the connection]
deathmist has quit [Quit: WeeChat 4.9.0]
deathmist has joined #aarch64-laptops
kalebris has quit [Ping timeout: 480 seconds]
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
kalebris has joined #aarch64-laptops
Mike56-2 has joined #aarch64-laptops
jhovold has quit [Quit: WeeChat 4.7.2]
Mike56-2 has quit [Read error: Connection reset by peer]
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Ping timeout: 480 seconds]
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #aarch64-laptops
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #aarch64-laptops
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
<deathmist>
getting some nice "ath12k_wifi7_pci 0004:01:00.0: dp_tx: failed to find the peer with peer_id 0" non-stop kmsg spam on X1E Vivobook running just abouts mainline 7.1.5 with active network traffix it seems, fun
d0pefish0 has joined #aarch64-laptops
d0pefish has quit [Ping timeout: 480 seconds]
d0pefish0 is now known as d0pefish
sre7 has quit []
sre7 has joined #aarch64-laptops
dc7800 has joined #aarch64-laptops
etehtsea has quit [Remote host closed the connection]
etehtsea has joined #aarch64-laptops
dc7800_ has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
Hmm no such messages here
<deathmist>
suspend/resume also made it stop for me, maybe I can figure out what triggered it later
<\[m]>
aha you too !! I need to restart NetworkManager seems
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Remote host closed the connection]
antoinelassagne7 has joined #aarch64-laptops
antoinelassagne has quit [Read error: Connection reset by peer]
antoinelassagne7 is now known as antoinelassagne
<anthony25>
I don't see the issue, but I use iwd (it connects faster than wpa_supplicant for me)
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Remote host closed the connection]
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
bandini has joined #aarch64-laptops
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
<Polkorny[m]>
anthony25: Thank youu for your ideapad-slim-3 dtb, it has helped me a lot
<anthony25>
you're welcome, but it's probably not me
<Polkorny[m]>
Sorry miss click hahahaha is the asteroid (i'm/a little/teapot)
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
dc7800_ has quit [Remote host closed the connection]
dc7800 has joined #aarch64-laptops
bandini has quit [Ping timeout: 480 seconds]
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
<Jadesheher[m]>
<clover[m]> "we've moved to codeberg! https:/..." <- actually very great work. It works perfectly
dc7800_ has quit [Read error: Connection reset by peer]
<clover[m]>
Woot! I drive two displays with my wdk2023 with arch ports kernel. Seems like only one USB c port has display out though. But it works for my setup
antoinelassagne3 has joined #aarch64-laptops
antoinelassagne has quit [Read error: Connection reset by peer]
antoinelassagne3 is now known as antoinelassagne
<JensGlathe[m]>
You need to look at my latest dtb, there is a gpio change for the second type-c to work with dp altmode
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
<JensGlathe[m]>
With that you can make it three (and encounter a new set of issues 😈
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Ping timeout: 480 seconds]
<Jadesheher[m]>
nope it recognizes only one out of 2 displays for me
<Jadesheher[m]>
the second displays says that it has the wrong resolution (tho there is no resolution specified)
<clover[m]>
Sometimes my usb-c display has wrong resolutions. My method is unplug and plug it back in and pray
d0pefish0 has joined #aarch64-laptops
d0pefish has quit [Ping timeout: 480 seconds]
d0pefish0 is now known as d0pefish
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
<JensGlathe[m]>
There are patches for this, too. EDID related on lore (also from me)
dc7800_ has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
dc7800_ has joined #aarch64-laptops
<clover[m]>
look forward to your patches. you rule
dc7800 has quit [Read error: Connection reset by peer]
<Jadesheher[m]>
no it only recognized one display. I guess it tried to mirror the image of the 1440p display to the 1080p display
<Jadesheher[m]>
but im on x13s and not volterra
<Mis012[m]>
mirroring would be a DE level setting
<Mis012[m]>
I guess idk what fbcon does
<Jadesheher[m]>
thats what the dock used to do
<Jadesheher[m]>
the config is copied from my X13 and should definitly work
<Jadesheher[m]>
(it did apply display zoom for the display that did work)
<Mis012[m]>
hw mirroring would be deranged, surely you just go into DE settings and say you don't want to mirror?
<Mis012[m]>
* surely you can just go
<Jadesheher[m]>
its sway and its already configured
<Mis012[m]>
right, *compositor
<Jadesheher[m]>
swaymsg -t get_outputs also only showed one display
<Mis012[m]>
can the dock do proper two outputs in windows?
<Jadesheher[m]>
idk it does work with my X13
<Jadesheher[m]>
i dont have any windows in this house
<Jadesheher[m]>
Microsoft windows i do have a window dont worry
<Mis012[m]>
"work" meaning you get image or meaning you see two displays and can display different stuff on them
<Jadesheher[m]>
work means i get 2 seperate displays + the laptop screen (on the X13)
<Mis012[m]>
ah, now I see what you mean
<Mis012[m]>
you were just talking about the display not saying "no signal"
<Mis012[m]>
well, still would be weird if the dock is able to do hw mirroring at all
<Jadesheher[m]>
it is definitly able to do that
<Jadesheher[m]>
does it on my google pixel aswell
<Mis012[m]>
is that hw?
<Mis012[m]>
or just AOSP not knowing how to deal with multiple displays
<Jadesheher[m]>
idk the google pixel gives even less info about attached screens
<Mis012[m]>
I mean, if it can do hw mirroring AND only does it off it's own accord as some sort of fallback, that's very deranged
<Mis012[m]>
unless this is some quirk of DP MST
<Mis012[m]>
can't think of any usecase where you'd be like "well, at least it mirrors stuff to the second screen"
<Jadesheher[m]>
Mis012[m]: me neither maybe some kiosk kind of shit? where its better to mirror something instead of showing nothing?
<Jadesheher[m]>
Mis012[m]: i should try and see what it does if i disable one display in software
<Jadesheher[m]>
(on the X13)
<Mis012[m]>
I guess just in case can try whatever DE people have more success with (probably not Gnome, iirc that also did weird stuff)
<Jadesheher[m]>
(on the X13)
<Mis012[m]>
not sure that it's very likely sway could be the issue, but this is Linux so it's not really that much work to try a known working compositor3
<Jadesheher[m]>
aa but i replugged the thunderbolt dock which is a different thing afaik
<Mis012[m]>
well, thunderbolt or usb4 stuff is not happening on qcom in any case
<Jadesheher[m]>
Mis012[m]: but it works on my x86 machine?
<Mis012[m]>
iirc there were issues with Gnome before
<Jadesheher[m]>
Mis012[m]: on any qcom ever or just X13s?
<penguin42[m]>
Jade (she/her)Any of them at the moment
<Mis012[m]>
anything that doesn't use a single exact usb4 router implemented as a pcie function
<Mis012[m]>
luckily the one that is supported is the only one allowed by the spec for pcie
<Mis012[m]>
but qcom was sane and didn't put fake pci(e) stuff in their SoC to deal with the OS being dumb
<Mis012[m]>
so we need to wait until upstream Linux stops making those assumptions
<Jadesheher[m]>
Mis012[m]: im still surprised my AMD laptop has proper pcie support
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Ping timeout: 480 seconds]
anthony25_ has joined #aarch64-laptops
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
anthony25 has quit [Ping timeout: 480 seconds]
anthony25_ is now known as anthony25
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
dc7800 has quit [Remote host closed the connection]