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
kmeaw has quit [Remote host closed the connection]
<craftyguy> Battery doesn't seem to drain when I'm using el2, but it may not be charging either
creemj has quit []
creemj has joined #aarch64-laptops
agl has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
agl has joined #aarch64-laptops
shoragan has quit [Quit: quit]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
tobhe has joined #aarch64-laptops
tobhe_ has quit [Ping timeout: 480 seconds]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
sally has quit [Quit: sally]
sally has joined #aarch64-laptops
<JensGlathe[m]> 0,0 HTC Rx errors on all devices so far with msi-map and msi-parent completely off
<JensGlathe[m]> wdk2023 el1 started spewing HTC Rx errors, just on cue
jglathe_volterra has joined #aarch64-laptops
jglathe_volterra has quit [Remote host closed the connection]
alfredo has joined #aarch64-laptops
SpieringsAE has joined #aarch64-laptops
<SpieringsAE> JensGlathe: wouldn't the extra pins on the sd card require bus-width = <8>?
<SpieringsAE> on my riscv framework thingy the sd card has bus-width = <4>, that one does not have the extra pins in the sd card holder
<SpieringsAE> does windows detect it at proper speed?
<SpieringsAE> ah no I read now that in that case the new data lines are differential pairs
<JensGlathe[m]> Yea. I guess it is operational but not yet optimized. I did some config-tests yesterday and managed to get the UHS-II into spewing i/o errors, too. Something like „dbus object not found“. So nothing to publish there, will need more work.
<SpieringsAE> my sd woes have not been solved yet either, just tried a regular usb adapter which worked normally
<JensGlathe[m]> I have one of those, too. Interesting Test for quirkiness of USB chipset.
alfredo has quit [Ping timeout: 480 seconds]
<SpieringsAE> I find the `[ 2458.072281] sd 0:0:0:0: [sda] Media removed, stopped polling` line weird
<SpieringsAE> because an actual usb drive doesn't doe that but instead dumps more info
<JensGlathe[m]> looks like a card detect hack
SpieringsAE has quit [Remote host closed the connection]
SpieringsAE has joined #aarch64-laptops
<JensGlathe[m]> I have the same messages for all slots of the reader
<SpieringsAE> in sd.c in spinup_disk() it calls scsi_execute_cmd() which returns ENOENT for some reason
<SpieringsAE> hmm okay
<SpieringsAE> my seperate usb sd card reader does not do this
SpieringsAE has quit [Remote host closed the connection]
SpieringsAE has joined #aarch64-laptops
<SpieringsAE> I don't understand why this function keeps getting called
<SpieringsAE> even though it says `stopped polling`
alfredo has joined #aarch64-laptops
jglathe_volterra has joined #aarch64-laptops
SpieringsAE has quit [Remote host closed the connection]
alfredo has quit [Ping timeout: 480 seconds]
patrickm has joined #aarch64-laptops
SpieringsAE has joined #aarch64-laptops
<SpieringsAE> I think this sd-card reader is just borked, the fact that it doesn't even work in windows either
<SpieringsAE> And I believe that was also the case for the other asus vivobook owners in here _mike TheBITLINK
<SpieringsAE> wait no it worked for kettenis
<SpieringsAE> there is a new firmware update from asus btw
<SpieringsAE> firmware version 362 and EC firmware 3.09
todi1 has quit [Ping timeout: 480 seconds]
SpieringsAE has quit [Quit: SpieringsAE]
todi has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
<macc24> wait a minute, does linux-next have drivers required for external display on x1e laptops?
<JensGlathe[m]> Huh
<JensGlathe[m]> Put a bootable SD into the DevKit and it boots
<JensGlathe[m]> What odd concept
<TheBITLINK[m]> <SpieringsAE> "there is a new firmware update..." <- oh yeah, got it the other day, it solved some weird driver bugs I was having with the GPU drivers on windows
<TheBITLINK[m]> SD card reader is still broken though
teythoon has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
rmsilva- has joined #aarch64-laptops
rmsilva has quit [Ping timeout: 480 seconds]
srinik has joined #aarch64-laptops
kalebris_ has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
kalebris has quit [Ping timeout: 480 seconds]
alfredo1 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
alfredo has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
srinik has quit [Ping timeout: 480 seconds]
jglathe_volterra has quit [Remote host closed the connection]
jglathe_volterra has joined #aarch64-laptops
jglathe_volterra has quit [Remote host closed the connection]
jglathe_volterra has joined #aarch64-laptops
<kuruczgy> macc24: not sure what's in linux-next, but I had dp altmode working on the yoga for a while now with Johan's branch + a device tree patch (well "working" sort-of, the link training still has some issues and fails for a lot of displays)
hightower3 has quit []