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
<janrinze>
a bit 'off topic' but: does anyone here know how to build a recent mainline kernel for the Jetson AGX Xavier? (Since it is an ARM processor there might be people here who know..)
reng_ has joined #aarch64-laptops
reng has quit [Ping timeout: 480 seconds]
<HdkR>
janrinze: Looks like it has a t194 dts in upstream, just build and run it probably?
<HdkR>
Does the DCO/MTS firmware ship with the upstream kernel in some way, or is it just really slow although? :think:
ravikant_ has quit [Ping timeout: 480 seconds]
valpackett has quit [Ping timeout: 480 seconds]
cyrinux94907 has joined #aarch64-laptops
akaWolf has quit [Read error: Network is unreachable]
akaWolf has joined #aarch64-laptops
ravikant_ has joined #aarch64-laptops
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
craftyguy has quit [Remote host closed the connection]
craftyguy has joined #aarch64-laptops
mani_s has joined #aarch64-laptops
<janrinze>
HdkR: just finished a build of 6.12.34 and will test soon. We'll see if this can boot.
mani_s has quit [Remote host closed the connection]
SpieringsAE has quit [Quit: SpieringsAE]
ungeskriptet_ has joined #aarch64-laptops
ungeskriptet has quit [Ping timeout: 480 seconds]
xbjfk has quit [Ping timeout: 480 seconds]
mani_s has joined #aarch64-laptops
xbjfk has joined #aarch64-laptops
ravikant_ has quit [Ping timeout: 480 seconds]
valpackett has joined #aarch64-laptops
valpackett_ has joined #aarch64-laptops
valpackett has quit [Ping timeout: 480 seconds]
mani_s has quit [Ping timeout: 480 seconds]
valpackett_ has quit [Ping timeout: 480 seconds]
mani_s has joined #aarch64-laptops
mani_s has quit [Ping timeout: 480 seconds]
lynxy has joined #aarch64-laptops
<lynxy>
this is likely a dumb question- but i'm currently setting up arch on the xps 13 9345, an x1e device, using a usb c stick flashed with the archlinuxarm generic linux-aarch64 image and then upgraded to the latest linux-aarch64 kernel, self-built
<lynxy>
i've managed to isolate the modules required for input & framebuffer so that the device does not black-screen, but i *cannot* get the device to recognise the usb stick partitions- it can never find root
<lynxy>
there is discussion on the ubuntu-concept thread which hints at the qcom-16v5-pas module causing issues with usb c on boot but even with it blacklisted (confirmed in emergency shell) the device cannot boot fully
<lynxy>
qcom_q6v5_pas, sorry
<lynxy>
any thoughts?
mani_s has joined #aarch64-laptops
<JensGlathe[m]>
yes that's true
<JensGlathe[m]>
do you have type-a ports?
<JensGlathe[m]>
Problem is the load of adsp firmware interrupts VBUS on type-c ports
<JensGlathe[m]>
an issue that gets worse the faster the SoC is
<JensGlathe[m]>
blacklisting q6v5_pas disables firmware load for adsp and cdsp
<JensGlathe[m]>
which you could do later, but not when booted from type-c.
<JensGlathe[m]>
Maybe a self-powered device mitigates it
<anthony25>
Otherwise you can remove the firmware from the ISO, if it's just to access to the installer
mani_s has quit [Ping timeout: 480 seconds]
<lynxy>
unfortunately the xps 13 has no usb a ports :sob:
<lynxy>
i suppose i could remove the internal nvme and flash that instead.
mani_s has joined #aarch64-laptops
jhovold has quit [Ping timeout: 480 seconds]
enyalios has quit [Read error: Connection reset by peer]
enyalios has joined #aarch64-laptops
mani_s has quit [Remote host closed the connection]
<kuruczgy[m]>
sgerhold: Nope, MST does not work for me either, as expected. (But built-in the display is fixed with your patches.)
<kuruczgy[m]>
In fact the MST dock I am using stops working even with a single display.
jglathe_ has joined #aarch64-laptops
jglathe_angrybox has quit [Remote host closed the connection]