robclark 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
mcbridematt has quit [Quit: Leaving]
wens has quit [Ping timeout: 480 seconds]
wens has joined #aarch64-laptops
strongtz[m] has quit [Quit: Client limit exceeded: 20000]
wens has quit [Ping timeout: 480 seconds]
wens has joined #aarch64-laptops
KhazAkar has quit [Quit: Connection closed for inactivity]
juergh has quit [Ping timeout: 480 seconds]
juergh has joined #aarch64-laptops
checkfoc_us has quit [Quit: ciao x]
Ablu has quit [Read error: Connection reset by peer]
Ablu has joined #aarch64-laptops
checkfoc_us has joined #aarch64-laptops
akawolf[m] has quit [Quit: Client limit exceeded: 20000]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
KREYREN_oftc has quit [Remote host closed the connection]
<travmurav[m]> hexdump0815: I think devices prior sd850 don't have secure-launch feature at all
<travmurav[m]> at least that's what the code (and what I've heard) suggests
<travmurav[m]> There are a few platforms that ///may/// be affected by CVE-2022-22063 but that would need a careful investigation for each SoC
<bamse> robclark: in line with craftyguy, my x13s was waiting for a fence in the drm driver that never arrived, earlier today...also on v6.8-rc1
<bamse> robclark: not sure if more people have reported this?
<bamse> robclark: only got the callstack this time...any useful debug data i should extract if it happens again?
<steev> ah, that makes sense, i saw it once earlier, in that instead of getting gdm, i got a _ in the upper left corner of the screen
kazek[m] has quit [Quit: Client limit exceeded: 20000]
LoganLeland[m] has quit [Quit: Client limit exceeded: 20000]
jglathe has joined #aarch64-laptops
shjim[m] has quit [Quit: Client limit exceeded: 20000]
claydoh[m] has quit [Quit: Client limit exceeded: 20000]
jglathe has quit [Quit: Leaving]
jglathe has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
jhovold has quit [Ping timeout: 480 seconds]
<jglathe> probably one of the dumber questions: I finally got an EFI shell on the X13s (used the iso from pbatard), now on the right fs, and ... how do I get a backslash there? I have a DE keyboard, but all altgr combinations have no effect
<jglathe> argh
* travmurav[m] has included the shell.efi in the tar.gz shared in this room so no one has to look for it
<travmurav[m]> is there nothing on the first layer?
<jglathe> nope, wants an fa selected first. In my case its FS5
<jglathe> *fs
<travmurav[m]> no, I mean the backslash is not on the first layer of the keyboard?
<travmurav[m]> but also, do you need a backslash?
<travmurav[m]> assuming you just do fs5: and sltest.efi tcblaunch.exe (which I assume all are in the root of fs5)?
<jglathe> no.
<jglathe> its in efi\Boot, but (pedantic I know) tcblaunch for the X13s is in \X13s grr
<jglathe> yes I will find a way
<travmurav[m]> ah I see
<travmurav[m]> note you need to type absolute path (from the fs root) as arguments, not sure if I documented that properly
<travmurav[m]> jglathe: but I guess worst case you can just plug another usb keyboard in :D
<jglathe> I tried that, I guess I need to put both in root
<jglathe> That, I will try, too
* travmurav[m] had to use a dedicated keyboard half the time since his laptop had to lay upside-down-half-open so he could get access to the uart pads
<jglathe> the external keyboard is ENU (although it is german) and has a backslash
quinine has quit [Quit: Client limit exceeded: 20000]
Emma[itits][m] has joined #aarch64-laptops
jglathe__ has joined #aarch64-laptops
<jglathe__> Hmm bricking the USB stick on such an attemot is kinda... normal?
<travmurav[m]> sounds like an unfortunate timing
jglathe__ has quit [Ping timeout: 480 seconds]
cenunix[m] has quit [Quit: Client limit exceeded: 20000]
jglathe__ has joined #aarch64-laptops
<jglathe__> no reaction on plug
<jglathe__> the port still works
jhovold has joined #aarch64-laptops
jhovold has quit []
<travmurav[m]> yeah, I guess same issue... Could you try the same on one of your volterras?
<travmurav[m]> and the firmware is 1.59 I guess?
<Jasper[m]> travmurav[m]: Yep
<jglathe__> Anyway, no USB sticks with USB-C plug left. Next time I'll try with a cheaper one
<jglathe__> UEFI: LENOVO v: N3HET87W (1.59 ) date: 12/05/2023
ArtyomK[m] has quit [Quit: Client limit exceeded: 20000]
<jglathe__> Found an old Kingston 256MB stick from the 90s (I guess), scsi 0:0:0:0: Direct-Access Kingston DataTraveler 2.0 4.10 PQ: 0 ANSI: 2
<jglathe__> I guess it should do
LoganLeland[m] has joined #aarch64-laptops
<LoganLeland[m]> finally setup debian with a windows partition on the x13s, once I port my xmonad/xmobar config over I'll be mainly using this for a laptop!
jglathe__ has quit [Ping timeout: 480 seconds]
<steev> heck yeah
jglathe__ has joined #aarch64-laptops
jglathe__ has quit [Ping timeout: 480 seconds]
jglathe__ has joined #aarch64-laptops
jglathe__ has quit [Read error: Connection reset by peer]
jglathe__ has joined #aarch64-laptops
jglathe__ has quit [Remote host closed the connection]
jglathe__ has joined #aarch64-laptops
jglathe__ has quit [Remote host closed the connection]
jglathe__ has joined #aarch64-laptops
<jglathe__> hmm ok the old stick at least survived the experimet, same result though. Will try Volterra later.
f_ has quit [Ping timeout: 480 seconds]
f_ has joined #aarch64-laptops
jglathe_ has quit [Remote host closed the connection]
jglathe_ has joined #aarch64-laptops
<jglathe_> Volterra doesn't power off with sltest, but reboots. And lands in the EFI shell again.
<jglathe_> UEFI: Microsoft v: 11.1.235 date: 07/28/2023
<jglathe_> tcblaunch.exe is from jan 13
<robclark> bamse: I don't think I've seen that, can you paste the splat? I've just switched over to jhovold/wip/sc8280xp-v6.8-rc1 here
jglathe_ has quit [Remote host closed the connection]
jglathe_ has joined #aarch64-laptops
<jglathe_> slbounce said success, though
jglathe_ has quit [Remote host closed the connection]
<Jasper[m]> <jglathe_> "Volterra doesn't power off..." <- Interesting, it worked for me
<Jasper[m]> I'll check whatever I have when I get home
jglathe_ has joined #aarch64-laptops
<jglathe_> Hmm no success booting with slbounce loaded. without dtbhack it hangs, with dtbhack it reboots
Emma[itits][m] has left #aarch64-laptops [#aarch64-laptops]
jglathe_ has quit [Remote host closed the connection]
jglathe_ has joined #aarch64-laptops
<jglathe_> @travmurav[m] @Jasper[m] I have a boot entry now for EFI shell, further testing should go faster. What can I provide for debug?
<Jasper[m]> Picture of the hang I guess
<Jasper[m]> Possibly a video for the sltest reboot
<jglathe_> okay I'll try my best
jglathe_ has quit [Remote host closed the connection]
jglathe_ has joined #aarch64-laptops
<Jasper[m]> @travmurav ^
<Jasper[m]> Going to guess he's afk atm though
<jglathe> I RMA'd that bricked stick :P
<jglathe> @Jasper[m], would be interesting to know which BIOS ver you have
<jglathe> did you have to use dtbhack?
<Jasper[m]> <jglathe> "did you have to use dtbhack?" <- Haven't tried, did some early testing that just seemed to work okay
<Jasper[m]> I'll check in a sec what bios I have
<Jasper[m]> <jglathe_> "UEFI: Microsoft v: 11.1.235 date..." <- I'm on the same version
<jglathe> hmm you didn't try and boot it to EL2, did you
<Jasper[m]> I tried the pre-release equivalent of sltest
<Jasper[m]> But I'll try it right now
<Jasper[m]> Jasper[m]: (which didn't reboot, but turned off as advertised)
<Jasper[m]> @jglathe okay yeah something broke inbetween testing and release it seems
<Jasper[m]> standby
Evaia63101 has quit [Quit: Hack the Gibson]
jglathe__ has quit [Remote host closed the connection]
Evaia631011 has joined #aarch64-laptops
Evaia631011 has quit []
Evaia631011 has joined #aarch64-laptops
KhazAkar has joined #aarch64-laptops
mcbridematt has joined #aarch64-laptops
Caterpillar has quit [Quit: Konversation terminated!]