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
chrisl has joined #aarch64-laptops
denisix has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
pabs has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
hightower2 has quit [Remote host closed the connection]
hightower2 has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
hightower3 has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
hightower2 has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
hightower3 has quit [Remote host closed the connection]
hightower2 has joined #aarch64-laptops
hightower2 has quit [Remote host closed the connection]
hightower2 has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
hightower2 has quit [Remote host closed the connection]
hightower2 has joined #aarch64-laptops
hightower2 has quit [Remote host closed the connection]
hightower2 has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
tobhe has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
agl_ has joined #aarch64-laptops
agl has quit [Read error: Connection reset by peer]
tobhe_ has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
hightower2 has quit [Remote host closed the connection]
sally_ has joined #aarch64-laptops
hightower2 has joined #aarch64-laptops
hightower2 has quit [Remote host closed the connection]
chrisl has quit [Ping timeout: 480 seconds]
sally has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
agl_ has quit [Ping timeout: 480 seconds]
agl has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
harrisonvanderbyl has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
agl has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
hexdump01 has quit [Ping timeout: 480 seconds]
xbjfk has quit [Remote host closed the connection]
xbjfk has joined #aarch64-laptops
xbjfk has quit [Remote host closed the connection]
xbjfk has joined #aarch64-laptops
xbjfk has quit [Remote host closed the connection]
xbjfk has joined #aarch64-laptops
xbjfk has quit [Remote host closed the connection]
xbjfk has joined #aarch64-laptops
agl has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
agl has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
agl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
agl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
harrisonvanderbyl has quit [Quit: Connection closed for inactivity]
SpieringsAE has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
KREYREN_oftc has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
agl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ravikant_ has joined #aarch64-laptops
xeliteCJF has joined #aarch64-laptops
denisix has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
harrisonvanderbyl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
denisix has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
denisix has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<Treibholz[m]>
You need to subscribe to "HyprLand Premium", to get the best experience.
chrisl has joined #aarch64-laptops
martiert has quit [Quit: WeeChat 4.6.3]
chrisl has quit [Ping timeout: 480 seconds]
martiert has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
pbrobinson has quit [Remote host closed the connection]
chrisl has quit [Ping timeout: 480 seconds]
pbrobinson has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
harrisonvanderbyl has quit [Quit: Connection closed for inactivity]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
jglathe_angrybox has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<SpieringsAE>
Treibholz: 🙃
<SpieringsAE>
Hyprland is somehow borked on my asus, in general some weird stuff happening. Sometimes during a pacman -Syu kde just craps out during the update and sends me back to sddm
<SpieringsAE>
I think I may have had a partial update and some inconspicious part of my system is now unhappy, KDE works fine otherwise though
<SpieringsAE>
ik ik, its only some dotfiles though right?
<Treibholz[m]>
probably - and prioritized answers in a forum.
<Treibholz[m]>
Heard and read other weird stuff about the Hyprland people... Never got it running anyway - seems only to work on distributions for the cool kids like (Arch, NixOS) and not for old farts like me. So I'll stay with sway.
<SpieringsAE>
arch linux arm repos are probably going to be dead for a month again, new glibc version came out
<SpieringsAE>
hmm, just did another update from a tty this time and it sent me to sddm from my tty during the post transaction hooks or the upgrading part again
chrisl has joined #aarch64-laptops
<SpieringsAE>
at least the process kept running in the tty now, some weird thing going on there
<Treibholz[m]>
"Move fast and break things" is just my personal preference for a WM/Compositor - I even think about switching back from neovim zu vim again...
<Treibholz[m]>
* is just not my personal
<Treibholz[m]>
* "Move fast and break things" is just not my personal preference for a WM/Compositor - I even think about switching back from neovim to vim again...
<SpieringsAE>
for some reason it seems hyprland cant properly initialize the monitor, atomic drm request: failed to commit: permission denied, flags: ATOMIC_ALLOW_MODESET ATOMIC_TEST_ONLY
<SpieringsAE>
pretty sure my user is in the required groups
chrisl has quit [Ping timeout: 480 seconds]
xeliteCJF has quit [Remote host closed the connection]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<\[m]>
briefly giving up ong etting bcachefs to work, looking at power consumption idle - 5-6W
<\[m]>
that's pretty good really
<\[m]>
compared to other laptops ánd compared to woa usage
<\[m]>
on ubuntu
chrisl has quit [Ping timeout: 480 seconds]
<\[m]>
close to 60watts compiling, most have been wrong on the 12W compiling on windows ?
<\[m]>
holy fck super fast - must be mega throttled then on windows
<robclark>
I suppose they were referring to "we have all the right dts bits to make display/etc over usb-c work"
<travmurav[m]>
speaking of having display/etc over usb-c work.... Was there anything for 4 lane dp alt mode? I somehow recall it discussed but it was a while ago
<JensGlathe[m]>
working on sc8280xp and x1
<travmurav[m]>
Is there some series stuck on the lists or something?
<JensGlathe[m]>
alexVinarskis may have a sharper eye on that, but: one series from Neill Anderson / konradybcio , and one from Alex. One handling the qmpphy (for X13s), the other necessary definitions in x1e80100.dtsi and individual x1 dts. You're right, its probably not all on the list.
<travmurav[m]>
ah I think I've found what you're talking about, thanks
lynxy has quit [Ping timeout: 480 seconds]
<maz>
how do we get this thing to EL2 if we don't have a windows build for it?
<travmurav[m]>
the tuxedo? the file from another windows install should just work
<travmurav[m]>
the only requirements are that microsoft has signed it and that it still has the error handler xD
<maz>
I thought these were per-device?
<travmurav[m]>
no
chrisl has joined #aarch64-laptops
<travmurav[m]>
per device part (signed by oem) is included in the uefi
<travmurav[m]>
the mssecapp
<travmurav[m]>
and mssecapp contains a list of microsoft signatures that it checks tcblaunch.exe against
<travmurav[m]>
and tcblaunch is a generic part of windows install/bootloader
<maz>
ah, gotcha. in a way, that makes sense -- MS probably doesn't want to deal with per-device crap.
<travmurav[m]>
yeah it would be insane to have a critical boot component be per device xD
<maz>
insane? we're talking about the same people, right? :D
<travmurav[m]>
the main problem is that apparently cannary windows has removed the funny code we care about
<maz>
yeah, I saw that. doesn't bode well for the future.
<travmurav[m]>
so if you have a tcblaunch file that works, keep it precious xD
<tobhe[m]>
but does the tuxedo firmware ship with the microsoft signing key if they don't intend to ship windows
<travmurav[m]>
oh that would be hilarious if they strip mssecapp xD
<travmurav[m]>
because then you definitely not getting el2
<travmurav[m]>
well unless they also forget (or "forget") to enable hardware secureboot I guess
<travmurav[m]>
but I'd assume the firmware is provided by the odm and it'd just have all the things
<travmurav[m]>
including the microsoft's trustlet and tpm stuff
<tobhe[m]>
and can they even legally ship mssecapp if they don't have a contract to ship Windows
<tobhe[m]>
we will see I guess 🙂
KREYREN_oftc has quit [resistance.oftc.net graviton.oftc.net]
KREYREN_oftc has joined #aarch64-laptops
lynxy has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
KREYREN_oftc has quit [Remote host closed the connection]
<konradybcio>
Jens Glathe: awaiting some boring dependencies on 4lndp..
xeliteCJF has joined #aarch64-laptops
<albsen[m]>
travmurav: which windows update removed the error handling updates from tcblaunch? I've not upgrade my windows 11 install (on a ssd that is removed) for a while. is there a way to check?
enyalios has quit [Remote host closed the connection]
chrisl has quit [Ping timeout: 480 seconds]
<travmurav[m]>
I don't know sadly, but we discussed it in this chat before that cannary/insider preview are broken already, it's possible that main branch isn't yet though
chrisl has joined #aarch64-laptops
<travmurav[m]>
so I'd hope that as of today most (especially old) installations still have good version of the file
<albsen[m]>
its not hardware specific is it?
<travmurav[m]>
no
<albsen[m]>
ok, should be easy to strip from an old install and try - good
enyalios has joined #aarch64-laptops
<albsen[m]>
travmurav: I've went through the documentation on slbounce and don't really see how I would go from the last step documented: fdtoverlay ... to a bootable (grub or sd-boot) linux env. can you point me to some follow up documentation or maybe give me some hints how that would work.
<albsen[m]>
on for example debian trixie
<albsen[m]>
or ubuntu
<travmurav[m]>
albsen: with the latest slbounce and linux 6.16 you need to load the driver and boot with -el2.dtb from upstream linux basically
<albsen[m]>
so, referencing the el2.dtb in grub as devicetree ... ok
<albsen[m]>
and then I can have 2 entries, one with the devicetree without (-el2) and one with el2.dtb in grub?
<albsen[m]>
it "just" works? (tm)
chrisl has quit [Ping timeout: 480 seconds]
<travmurav[m]>
yes, as long as you've automated loading the driver - if you pick el2 - it will switch, if you pick normal dtb - it won't do anything
<albsen[m]>
how do I "automate" loading the driver? if you're referring to the devicetree, I usually hardcode it in my grub to point to the exact one that I placed manually in reach of grub on the efi partition
<travmurav[m]>
in sd-boot there is a drop-in dir for efi drivers, in grub I tried to propose it and was ignored, but you could add it to the efi driver boot order
chrisl has joined #aarch64-laptops
<albsen[m]>
in that grub proposal did you send a patch?
<travmurav[m]>
otherwise you can put it on esp, then `efibootmgr -rcl "slbounce.efi" -L "slbounce" -d /dev/nvme0n1 -p <esp partition number>` I think
<travmurav[m]>
and it would put it into efi's own driver loading list
<albsen[m]>
perfect
SpieringsAE has quit [Quit: SpieringsAE]
<albsen[m]>
in which case it's already loaded by efi and grub will have it available irrespective, correct?
<travmurav[m]>
but maybe make sure it works by loading it manually via efi shell just in case
<travmurav[m]>
yes
<travmurav[m]>
well, grub doesn't really interact with the efi driver itself per se, the driver modifies parts of efi services to add el2 switching on ebs though
<albsen[m]>
thx, thats really helpful. I'll try this and come back with questions. (don't have the device with me right this minute)