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
KhazAkar has quit [Quit: Connection closed for inactivity]
uwu has joined #aarch64-laptops
<robclark>
craftyguy: btw, got link to model for nvme insert.. not urgent yet (due to lack of time to re-image my daily driver) but at some point I intend to upgrade to a larger drive..
<craftyguy>
the model I printed for securing the 2230 ssd?
* craftyguy
looks
<robclark>
yeah.. if you can find it
Dylanger has joined #aarch64-laptops
<Dylanger>
Anyone know if Snapdragon 888 has any mainline linux support?
<Dylanger>
I have 2 HDK's that aren't doing anything
djakov_ has joined #aarch64-laptops
djakov has quit [Ping timeout: 480 seconds]
<bamse>
Dylanger: 888 is known as sm8350 in the upstream kernel, so yes there's some support
<Dylanger>
Ooo that's awesome
<Dylanger>
It would have lower wattage usage than my seeedpc
<bamse>
how much ram does it have?
<Dylanger>
One sec lemme see
<bamse>
product page doesn't say :/
<bamse>
internal page indicates 12gb...so that's pretty good
<Dylanger>
What would be the best OS to run on it? I'm guessing the bootloader wouldn't support Fedora CoreOS
<Dylanger>
bamse: Ah my bad
<bamse>
Dylanger: the problem with the bootloader is that it loads a kernel+dtb+ramdisk packaged up as a android boot.img...so there's that extra step of packaging things up
<Dylanger>
I'll go get it, iirc I had 2
<Dylanger>
bamse: Sounds like ChromeOS's depthcharge
<bamse>
same problem, when it comes to running a standard distro
<Dylanger>
Yeah sounds like a little weekend thing
<bamse>
other than that (i.e. with some manual work) you can run whatever distro...
<bamse>
i'm running arch linux on all devboards (and phones) that gets a distro installed
<Dylanger>
I'd love to run Fedora Server or something, if I can get it running, I'll have it replace my little Media SeeedPC
<Dylanger>
Debugging on it should be easy as there's literally UART etc headers
<bamse>
probably worth getting anything running on the hdk first, to see how stable it is
<bamse>
right, it's a really convenient development board
<bamse>
and if it's not stable, i'd like to know about it...might not be people's highest priority, but we should make sure it's functional and stable in the upstream kernel
<jbowen>
Is an x13s with Rawhide your daily driver?
<dgilmore>
My daily driver is an adlink ampere developer workstation. When I am not at my desk I'm using the x13s running Fedora 39
<dgilmore>
I can't do video conferencing on the x13s
hexdump01 has joined #aarch64-laptops
<dgilmore>
I do power it off when not using because it doesn't suspend. It boots pretty quickly
hexdump0815 has quit [Ping timeout: 480 seconds]
<jbowen>
I've never grown to trust suspend on a system
<jbowen>
(If this isn't the right place for this discussion or I just need to go scrounge around on my own, please do tell me)
<jbowen>
I'm only able to get it to start booting into linux if I pass dtb= on the command line
<Dylanger>
<dgilmore> "I do power it off when not using..." <- > adlink ampere developer workstation what even is this? Sounds awesome
<Jasper[m]>
Many core socketed workstation board
<jbowen>
They're pretty sweet
<HdkR>
I'm looking to an AmpereOne version of that device :)
<HdkR>
looking forward to*
<craftyguy>
robclark: this is what I printed: https://www.thingiverse.com/thing:5254081 IIRC I had to do a little sanding, especially on the top so that it wouldn't interfere with the heat spreader that lays on top of the drive
Lucanis has quit [Ping timeout: 480 seconds]
martiert has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
<jhovold>
steev: haven't noticed anything like that, but then I don't use Gnome or wayland
<jhovold>
the closest thing that come to mind is audio not working on the first boot after removing the alsa state
<jhovold>
either way, it should be a user space bug
rfs613- has joined #aarch64-laptops
rfs613 has quit [Ping timeout: 480 seconds]
KhazAkar has joined #aarch64-laptops
Libre___ has quit [Ping timeout: 480 seconds]
Libre___ has joined #aarch64-laptops
<_[m]1>
<jbowen> "Is there a place I can grab a ...." <- look at debian install instructions,they host it
<jbowen>
_[m]1: Thank you, I did actually stumble across their instructions after I asked that (and found it in the Fedora image I'd downloaded)
<Jasper[m]>
<jbowen> "(â_â): Thank you, I did actually..." <- Which image? One of the live disks?
<Jasper[m]>
I couldn't find it weirdly enough
<exeat>
BTW, suspend has been perfectly reliable on the x13s; no hangs or "lost" devices
<_[m]1>
so -again offtopic - but why would anyone run zfs on rolling update distro? it's scary no?
<Jasper[m]>
Why?
<Jasper[m]>
I mean you can choose to enable experimental releases
<Jasper[m]>
Otherwise it either works (on your kernel version) or it doesn't
<_[m]1>
dunno I sign in first thing I do is pacman -Syu lol
<dgilmore>
Dylanger: I power off the x13s
<Jasper[m]>
_[m]1: Well yeah, but the package won't update if there are no updates
<Jasper[m]>
and the module won't load if the kernel's too new
<Jasper[m]>
So unless you care a loy about uptime/availability it won't really matter since you could feasibly install a stable kernel
<_[m]1>
and exclude it from being updated?
<_[m]1>
* being updated? IgnorePkg = linux mm
<jbowen>
Jasper[m]: The raw image, but I'd guess it's in the ISO as well
<nscnt[m]>
My Windows work laptop reliably wakes up with a blue screen from suspend. I always get the cursed hardware. >.<
<Jasper[m]>
jbowen: Couldn't find it there, that's the issue
<Jasper[m]>
I can copy it over myself, but to get it working ootb it would be good to include those in the live image by default
<jbowen>
It's in a subdirectory of what would be mounted at /boot, not in the ESP
<jbowen>
There is are just RPi dtb's there
jkm has joined #aarch64-laptops
<Jasper[m]>
The live images I've seen have a squashfs that needs to be unpacked first
<Jasper[m]>
But it can't do that without Linux itself functioning first
<Jasper[m]>
Chicken and egg thing
iivanov has quit [Remote host closed the connection]
iivanov has joined #aarch64-laptops
<robclark>
craftyguy: thx
<jbowen>
Jasper[m], yeah, that's why I switched to using the raw image
<jbowen>
I didn't get things to a working state before giving up for the evening
<Jasper[m]>
Aww,
<jbowen>
I'll try again
<steev>
fwiw, i've been using suspend since it has been available and haven't lost any data (yet)
<jbowen>
Giving up old fears is difficult, lol
<steev>
understandable :)
<_[m]1>
maybe we can use rocky linux instead of fedora ðĪŠ
<steev>
lets not get too crazy
<steev>
this is so fucking weird
<steev>
i can't get gdm to run on wayland on 6.7, but sway works fine?
<steev>
switch back to 6.6 and wayland is available
* jbowen
turns rocky linux mug around....
<jbowen>
I understand nothing about graphics, X or Wayland
<_[m]1>
ð
<_[m]1>
steev: 1s and 0s they said grr
<steev>
to be fair... no one really understands X or wayland
<_[m]1>
lol wasn't wayland going to be the solution to all of X s longstanding issues?
<jbowen>
I still maintain that GUIs were a mistake
<steev>
yes... they said that 20 years ago when it was announced
<clover[m]>
steev: is it a mutter issue?
jkm has quit [Ping timeout: 480 seconds]
Caterpillar has joined #aarch64-laptops
<steev>
clover[m]: maybe? seems odd that 6.6 is fine but 6.7 isn't?
<steev>
i haven't rebuilt mutter with the patch, i should do that
jkm has joined #aarch64-laptops
<clover[m]>
i can sent you a binary of mutter 45.0 if you want to test that quickly
<clover[m]>
it includes daniel thompsons patch
iivanov has quit [Quit: Leaving]
<steev>
o
<steev>
i've already got it
<steev>
just hadn't done it
<steev>
so i've installed it, just haven't yet logged out
hexdump01 has quit []
hexdump0815 has joined #aarch64-laptops
<steev>
it's not mutter
<clover[m]>
ok
<craftyguy>
well this is weird. I disabled the trackpad on the x13s in the EFI setup, but sometimes it randomly (?) get re-enabled in the OS
<jenneron[m]>
craftyguy: is it weird tho? kernel uses dtb and kinda ignores what EFI does to ACPI or whatever the way it disables trackpad
<jenneron[m]>
if it disables power or something, kernel still can enable it
<craftyguy>
it's disabled on boot though, so it doesn't completely ignore it?
<craftyguy>
yeah maybe it's not weird. I'm still used to x86 systems :P
<craftyguy>
ya or I can just disable it in my sway config :P
<craftyguy>
but I should finish reviewing your MR :)
<jenneron[m]>
i think you did, the problem is me not testing it..
<craftyguy>
ah ya, now that I actually clicked on the link
<jenneron[m]>
craftyguy: i made this MR actually to make pinephone closer to being able to use extlinux.conf instead of u-boot config
<jenneron[m]>
so maybe we should force pinephone maintainers to work on it instead of me
<jenneron[m]>
*u-boot script
<gwolf>
_[m]1: "not starting up" is not a longstanding issue. "not starting up" is a longlying issue.
<gwolf>
(sorry for the word pun... at least it works better in Spanish ;-) )
<gwolf>
FWIW, better support under my ARM laptop is what prompted me to switch from XOrg (i3) to Wayland (Sway). I have migrated all of my x86 systems, and am not going back.