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
EricCurtin[m] has joined #aarch64-laptops
danielt has joined #aarch64-laptops
<bamse>
HdkR: received my shiny new nvme enclosure, hoping to do some debugging...but it just works on all my three sc8280xp devices
<HdkR>
:|
<bamse>
HdkR: the light does indeed go out 3-4 times dring boot, but it comes back every time
<HdkR>
wha
<bamse>
usb 2-1: new SuperSpeed Plus Gen 2x1 USB device number 4 using xhci-hcd
<HdkR>
That's weird
<HdkR>
Old BIOS or firmware issue maybe?
<bamse>
mine is not new...but might be
<bamse>
HdkR: i tried copy a few gb off the device...started off fine, then "usb 2-1: USB disconnect, device number 5"
<bamse>
HdkR: so there's something there
<HdkR>
Oh, that's spooky
<bamse>
i'm not able to reproduce the same issue on the CRD
<HdkR>
That's incredibly weird. Could it pull too much wattage once the SSD is loaded and it gets kicked off the bus?
<bamse>
HdkR: sounds like a very reasonable hypothesis
<bamse>
that i should be able to measure...worse is if it relates to the signal integrity
<HdkR>
Wonder if my device since its BIOS and firmwares have never been updated from launch is just a bit more picky about this
<bamse>
could be, or you have a hungrier nvme device?
<bamse>
but does your system automount stuff of the device?
<HdkR>
It's probably hungry because of how much capacity on it, but I don't even automount
<HdkR>
According to this Tom's Hardware review it should idle at 800mw
<HdkR>
Loaded peak at 8.68W
<bamse>
peak might be a problem unless we negotiate more juice...but to get the partition table out should be fine
<HdkR>
I could test this actually, I have a lower end device I could throw in it
<HdkR>
Holy crap, it is a power draw thing. I used the same SSD as the internal drive and it just worked
<HdkR>
Let's try a Samsung drive...
<HdkR>
Samsung 970 Evo Plus 1TB also works
<HdkR>
and to make sure it isn't a fluke, pull the drive out of the other dock and try again...
<HdkR>
no light
<HdkR>
So really it's the Sabrent Rocket 4 Plus 8TB that causes issues
<bamse>
i think i have a 970 evo plus 1tb in mine too
<bamse>
and i could read a few gb before it failed...
<HdkR>
I guess the real question would be why does early boot seemingly not care, and does Windows also not care?
matalama_ has joined #aarch64-laptops
Bioxvirizm-x13s[m] has joined #aarch64-laptops
todi1 has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
Las[m] has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
todi has quit [Ping timeout: 480 seconds]
sally has joined #aarch64-laptops
sally has quit [Quit: Konversation terminated!]
sally has joined #aarch64-laptops
sally has quit []
sally has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
sally has quit [Remote host closed the connection]
owc[m] has joined #aarch64-laptops
alfredo has quit [Quit: alfredo]
baspar[m] has joined #aarch64-laptops
Guest1956 has quit [Quit: WeeChat 4.0.5]
matalama_ has quit [Quit: Connection closed for inactivity]
martin has joined #aarch64-laptops
martin is now known as Guest2338
systwi has quit [Ping timeout: 480 seconds]
<jhovold>
dgilmore: thanks!
matthias_bgg has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
systwi has joined #aarch64-laptops
Guest2338 has quit [Quit: WeeChat 4.0.5]
juergh has quit [Quit: ZNC 1.8.2+deb2build5 - https://znc.in]
<Dylanger>
I was missing this patch, should land in 6.7
<Dylanger>
I emailed Collabora and got a nice response 🙂
<Dylanger>
Running 6.6-rc4 now 🎉
hightower3 has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
juergh has joined #aarch64-laptops
<altacus_>
enyalios: regarding steam. I was able to get team running with box64 & box86 at one point. Unfortunately, I had to reinstall and wasn't able to create it. If memory serves, I think the directions on the github outline how to get it working.
iivanov has quit [Remote host closed the connection]
Guest2291 is now known as qzed
<push>
does qemu-user not work due to the lack of virtualization?
<enyalios>
altacus_: thanks, some googling looked like i should look into box64 or fex-emu
<Dylanger>
<push> "does qemu-user not work due to..." <- (This is why I didn't buy a x13s)
<danielt>
push: qemu-user doesn't need virtualization extensions... but AFAIK it doesn't shim native libraries which meaning everything running in userspace has to be emulated
<push>
yeah, youd need to install x86 copies of all the dependancies, which for something like steam is gonna be a lot, but afaik, that would be the closest to making it "just work"
<danielt>
push: Depends how "just work" is defined ;-). My experience with Zoom client (for example) is that while the emulation did appear to be functional correct, the client runs slower than real time which stops it being useful.
<exeat>
robclark: Thanks. Unfortunately I have no reliable way of triggering it either.
<robclark>
same.. although sometimes vt switch seems to help
<enyalios>
lol, sub realtime zoom cracks me up
<enyalios>
sometimes my meetings feel that way
<robclark>
danielt: if you were using qemu-user just to run x86 binary, why not use fex-emu instead?
<robclark>
or I suppose box64.. but I haven't tried box64 myself so not sure how they compare
<danielt>
robclark: Mostly curiousity. I use box64 when I really needed the client to work (although mostly the web client is enough for me).
<robclark>
gotcha
iivanov has quit [Quit: Leaving]
matalama_ has joined #aarch64-laptops
<steev>
Dylanger: thats awesome, congrats on getting your cherry
<steev>
(working) just making the joke that irc only shows "i managed to get my cherry..."
<steev>
qemu-user runs "fine" (slow af though, but that's no different from x86_64)
rz has quit [Remote host closed the connection]
rz has joined #aarch64-laptops
<steev>
robclark: i use qemu-user because... i'm just building stuff
<HdkR>
qemu-user also has the issue that its ioctl support is quite limited
rz_ has joined #aarch64-laptops
rz has quit [Ping timeout: 480 seconds]
<altacus_>
Just compiled steev's 6.6.0rc4 kernel and can confirm that it works. In addition, I was able to set up the finger print sensor which works great!
<steev>
finger print sensor should work with 6.4+
<steev>
that was a patch from johan, not me
<altacus_>
steev: yes, I've been going through the chat logs (slowly) and just realized this was added.
<steev>
:) glad it works though!
<steev>
i haven't tried it here because a) i'm against biometrics, and b) here, if i even install fprintd without enrolling, gdm just doesn't let me log in
<altacus_>
I wanted to say that my x13s running debian gnome has been quite responsive compared with some of my intel based systems. I'm really quite blown away.
<altacus_>
steev: I can imagine all the testing you need to do to get these builds up (and to field questions) so I'm happy to sacrifice my biometrics for the cause.
rz_ has quit [Ping timeout: 480 seconds]
<steev>
i'm just hoping we'll reach a point (and we will) where the patches i carry won't be needed anymore
<altacus_>
I recently got the X1 Tablet Gen 3 and cannot find the finger print sensor driver for linux so when I saw that the x13s had it already I was quite stunned.
<altacus_>
steev: I appreciate your efforts. I played around with getting linux on the c630 and it was really quite a nightmare trying to figure out what kernel to use, etc. Even today, I still have my c630 lying around doing nothing and although I want to install linux on it again, I just can't find good directions/kernels for it.
<exeat>
It'd be fun (and possibly even useful) to assign finger-specific functions to the sensor, but I doubt that fprintd is amenable to that
<altacus_>
exeat: I think fprintd can provide which finger is identified, it's up to the software to use that info (I would imagine).
<steev>
i'm not sure; here, i use my c630-linux-6.3.y branch
<steev>
it's not 100% for sure, we're still missing the ec driver and usb iirc
<steev>
i can't recall why i haven't moved to a newer than 6.3
rz has joined #aarch64-laptops
<exeat>
altacus_: I haven't played around with fprintd at all TBH, it may well be more flexible than I think
cyrinux has quit [Quit: bye]
cyrinux has joined #aarch64-laptops
Amber_Harmonia has joined #aarch64-laptops
<altacus_>
steev: I may give it another shot. the c630 really is a nice laptop, battery life is amazing. Is it fully functional in linux (i.e. webcam, etc).
<steev>
webcam does, but usb may or may not
<altacus_>
steev: fingerprint scanner?
<steev>
see my previous thing about not doing biometrics :)
<steev>
i don't know the status of it
matalama_ has quit [Quit: Connection closed for inactivity]