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
icecream95 has joined #aarch64-laptops
<icecream95>
JensGlathe[m]: The SD card reader on my Vivobook works in both Linux and Windows for my basic SDHC/SDXC cards
<icecream95>
Whether the cards themselves work (without any IO errors) is a different matter... apparently leaving them unused for years isn't good for them
tobhe_ has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
If the card works without errors in the USB card reader, this can be ruled out. It's some oddity with the DevKit card reader, we'll find out eventually.
albsen[m] has joined #aarch64-laptops
<albsen[m]>
hi, did anyone here replace the SSD on their t14s? I've read that there might be some compatibility issues
<icecream95>
JensGlathe[m]: Some of my cards work fine and without errors in the Vivobook's reader, and the others show corruption with other readers as well. What's fun is that the corruption isn't static, so maybe I should make multiple disk images and average them to reduce errors...
krzk has quit [Ping timeout: 480 seconds]
<JensGlathe[m]>
I don't use them much, but on SBC these are common - so I have a few. No card age related errors encountered so far. For testing I bought 2 new ones (one SDXC, one micro-sdxc) and was surprised how expensive they have become. I opted for 256GB ones since the base 64GB usually started at ~50€ anyway.
<JensGlathe[m]>
And now its a data point: put an UEFI bootable sd into the dev kit and it boots from there
<JensGlathe[m]>
with priority
krzk has joined #aarch64-laptops
krzk has quit [Ping timeout: 480 seconds]
krzk has joined #aarch64-laptops
krzk is now known as Guest5771
Guest5771 has quit [Read error: Connection reset by peer]
krzk has joined #aarch64-laptops
krzk has quit [Ping timeout: 480 seconds]
<macc24>
icecream95: power supply issues?
krzk has joined #aarch64-laptops
SpieringsAE has joined #aarch64-laptops
<SpieringsAE>
icecream95: With my latest 6.13-rc6 kernel? It has to be coincedence then that both me and TheBITLINK have this issue, I have opened a support ticket with Asus about it yesterday
<icecream95>
SpieringsAE: Yes, for me the card reader works with your kernel (I tested in EL2).
<SpieringsAE>
I doubt this would have a difference between el1/el2
<SpieringsAE>
but yeah, the fact that it works in windows for you aswell is also a better indicator
krzk has quit [Ping timeout: 480 seconds]
<icecream95>
I wonder if your problem is related to the issues with the ROG Ally SD card reader...
creemj has quit [Ping timeout: 480 seconds]
creemj has joined #aarch64-laptops
<icecream95>
I wonder if having the card reader right next to the USB-C ports was a good idea, given how hot that part of the case gets when charging
<SpieringsAE>
it does really get very hot there yeah
<icecream95>
Though the Ally used a PCIe card reader, so it wouldn't be exactly the same issue
<SpieringsAE>
ah that was also an overheating one yeah?
<SpieringsAE>
was that the controller that got damaged or just the sd-card itself though?
<_mike>
hi *
jhovold has joined #aarch64-laptops
krzk has joined #aarch64-laptops
<icecream95>
It seems like it was both. But there isn't really much evidence to say that the issues are related yet
<icecream95>
Chromebooks have an EC command for limiting charging current, it would be nice to be able to control that here, because even if it isn't burning up components, it is still uncomfortable
krzk has quit [Ping timeout: 480 seconds]
krzk has joined #aarch64-laptops
<SpieringsAE>
definetly would like charge capacity limit to work like it does in windows
<SpieringsAE>
my previous vivobook had it too
<SpieringsAE>
ah well, well see what asus has to say
krzk has quit [Ping timeout: 480 seconds]
icecream95 has quit [Ping timeout: 480 seconds]
srinik has joined #aarch64-laptops
<kuruczgy[m]>
Can any x1e laptop do charge capacity limiting? (Last I looked on my yoga I could not even find such a feature on Windows)
pneuhardt has joined #aarch64-laptops
<SpieringsAE>
yeah I was able to set it up in the myasus app or something on windows
<JensGlathe[m]>
The mere fact that this option exists is proof they know of the issue
<SpieringsAE>
this is only capacity so dont charge above 80%
<JensGlathe[m]>
Seems to be an issue nonetheless. No need to add controls when it is fine with default settings.
checkfoc_us9 has quit []
checkfoc_us9 has joined #aarch64-laptops
<HdkR>
Users almost certainly want controls for charge limit. I would basically always set 80% on all my devices unless I know I'm travelling and then I remove that limit
<HdkR>
Also if it is basically always sitting plugged in, setting the limit is also good :D
<HdkR>
Which is my devices nearly 100% of the time
<SpieringsAE>
same
krzk has joined #aarch64-laptops
krzk is now known as Guest5784
Guest5784 has quit [Read error: Connection reset by peer]
krzk has joined #aarch64-laptops
krzk has quit [Ping timeout: 480 seconds]
krzk has joined #aarch64-laptops
smoorgborg[m] has joined #aarch64-laptops
<smoorgborg[m]>
Not sure if anyone noticed, but theres a critical "Qualcomm Retimer" firmware update posted for ThinkPad T14s which should fix standby issues with USB plugged in -> https://download.lenovo.com/pccbbs/mobiles/n42tt02w.html
<smoorgborg[m]>
(Requires BIOS v2.15 or later)
krzk has quit [Ping timeout: 480 seconds]
krzk has joined #aarch64-laptops
nothorseface has joined #aarch64-laptops
krzk has quit [Ping timeout: 480 seconds]
kmeaw has joined #aarch64-laptops
ungeskriptet has quit [Ping timeout: 480 seconds]
krzk has joined #aarch64-laptops
janrinze has quit [Quit: Leaving.]
ungeskriptet has joined #aarch64-laptops
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #aarch64-laptops
<jhovold>
smoorgborg[m]: thanks for the link!
nothorseface has quit [Ping timeout: 480 seconds]
nothorseface has joined #aarch64-laptops
nothorseface has quit [Ping timeout: 480 seconds]
<SpieringsAE>
does anyone know an IRC where Marek Vasut is active? I'm going crazy on this display issue and he seems to be very active in this part
SpieringsAE has quit [Remote host closed the connection]
_mike has quit [Remote host closed the connection]
<macc24>
<icecream95> "Chromebooks have an EC command..." <- you're free to learn 8051 assembly and figure out if that's the case on devices with it8987 :)
zxvxc has joined #aarch64-laptops
zxvxc has quit [Remote host closed the connection]
jglathe_volterra has quit [Remote host closed the connection]
<HdkR>
It's an 8051?
<macc24>
yes
ben__ has quit [Ping timeout: 480 seconds]
<abby>
everything is an 8051
<HdkR>
A market that the Cortex-M0 still hasn't defeated
<steev>
i just cheat and read the cros sources
<kettenis>
are you sure it isn't a Cortex-M0 emulating a 8051? ;)
ben__ has joined #aarch64-laptops
<TheBITLINK[m]>
SpieringsAE: I was testing your SD Card reader patches, I'm seeing USB connect messages on dmesg when inserting a card, and a /dev/sda appears, but I get "No medium found" when trying to do anything with it
<TheBITLINK[m]>
considering icecream95 said it's working for them, and it isn't working on windows for either of us, I think it's safe to assume it's a hardware issue, probably even from the factory
<TheBITLINK[m]>
that or it's very easy to get damaged from the high temperatures near the USB-C ports
ben__ has quit [Ping timeout: 480 seconds]
enyalios_ has joined #aarch64-laptops
enyalios has quit [Ping timeout: 480 seconds]
nothorseface_ has quit [Read error: Connection reset by peer]
nothorseface_ has joined #aarch64-laptops
nothorseface_ has quit [Read error: Connection reset by peer]
<farchord>
Anyone have a script that copies the firmware from the Windows partition? I used a modified version of the ubuntu one, but it didn't work so I think I missed some stuff as my battery meter still dont work
<tobhe_>
farchord: which device?
tobhe_ is now known as tobhe
<robclark>
it could also be kernel module probing before rootfs mounted (if the adsp fw doesn't end up in initrd)... I have something that runs some sysfs writes at startup to kick the adsp
<farchord>
tobhe_: Asus vivobook s15
<farchord>
Dangit i forgot you guys hated matrix features sorry
<farchord>
Didnt mean to reply
<farchord>
Im on fedora and alot of things are working. Im running on you guys’ kernel thanks to nirik’s build on copr
<farchord>
The install is currently on a usb-c drive