ChanServ changed the topic of #linux-cros-arm to:
krei-se- has joined #linux-cros-arm
krei-se has quit [Ping timeout: 480 seconds]
hexdump01 has joined #linux-cros-arm
hexdump0815 has quit [Ping timeout: 480 seconds]
<alpernebbi> (I think they mean installing the bootloader replacement)
<janrinze> dcz[m]: I think HP discontinued the model I referred to. Not sure though.
<dcz[m]> the project is mostly about mainline Linux, but as far as I remember that might be hard without another boot loader
<dcz[m]> if I can make it possible to use universal OS images rather than special Chromebook ones I'd take that too
<janrinze> dcz[m]: I don't use a different bootloader. The chromebook is setup to show the bootchoice at power-on
<janrinze> dcz[m]: I prefer it that way, it allows to boot from either inrenal disk or a USB attached disk. That way I can quickly test other kernels.
<dcz[m]> hmmm I guess the Mediatek unique selling point is that you can have radical openness even in the boot loader
<janrinze> dcz[m]: The kernel I built is almost main-line 6.9.0 and hopefully a more recent one soon.
<janrinze> dcz[m]: I think having grub on the machine would facilitate more boot options. I don't know if that is easily implemented.
<janrinze> On a side note: the Mediatek Kompanio 1200 is faster than a RPi 5.
<janrinze> jenneron[m]: The changes for google-dojo are mainlined already, right?
<janrinze> the name dojo is a bit unfortunate since there is another dojo project from google that is kernel related i.i.r.c.
<janrinze> dcz[m]: just for a quick test I am building kernel 6.12.1 now and see if i can get it to boot.
<janrinze> has anyone here yet managed to run grub with an ARM64 chromebook?
<dcz[m]> the worst thing about chromebooks is that several carry the same model number and good luck finding out what you're looking at
<janrinze> dcz[m]: Kernel 6.12.1 runs. Have not yet done testing but it boots and I have a Debian 12 desktop running.
<dcz[m]> ..if the screen was 3:2 I would have no doubts about that being my next main machine
<janrinze> 3:2?
<janrinze> dcz[m]: If you are keen on ARM linux why not use Asahi Linux?
<dcz[m]> I don't care about the arch, I care about the amount of closed firmware
<dcz[m]> 3:2 proportions. The nicest hardware apart from the lack of nvme so far is https://wiki.postmarketos.org/wiki/Acer_Chromebook_Spin_513_(CP513-2H)_(google-tomato)
<dcz[m]> although here the resolution is also wrong
<janrinze> Cortex-A78 is a good base system, plenty power and not too much heat. 1920x1080 is okay. Would love to see 2560x1440 or bigger though..
<dcz[m]> I'm just not sure 128GiB is enough to work :S
<janrinze> What I am more worried about is the state of chromium.. it seems that the last update breaks just about everything.. version 130 already fails to run webgl here and 131 won't even start anymore.
<dcz[m]> if not, the HP would be the only viable option
<dcz[m]> what about Firefox?
<janrinze> I upgraded to 1TB on the HP one. Thanks to NVMe SSD.
<janrinze> Firefox is fine. runs nicely and even does webgl without any problems.
<dcz[m]> is it state of chromium or state of the drivers not supporting what chromium wants?
<janrinze> chromium seems to dislike mesa.
<janrinze> Even with 24.2.4 it won't budge..
<dcz[m]> mesa or drivers other than intel/amd?
<dcz[m]> I wonder what the situation is on snapdragons
<janrinze> Would you need mesa with intel/amd?
<dcz[m]> I mean, that's where Linux matters today, so I expect Chromium cares about that
<dcz[m]> maybe it's just a matter of so few people running mali or adreno that they don't even know this is happening
<janrinze> I seriously doubt that.. Chromebooks are a Google product. They surely know what/how/etc..
<janrinze> Unfortunately they don't seem to contribute the chromeos advancements in the graphics department to trickle through to other linux distributions.
<janrinze> 1920x1080 youtube in FireFox drops about 8% of frames whereas Chromium is closer to 1% dropped frames..
<dcz[m]> what are Chromebooks using for graphics?
<janrinze> Chromium 139 frames dropped out of 10000.
<janrinze> They have their own drivers. usually closed source binary drivers. In the past I have used the mali drivers from chromebooks with linux and they did work.
<dcz[m]> so they just don't care about mesa outside of x86 probably
<janrinze> No idea if ARM cares about Linux support. They don't release any drivers anymore for X11.
<janrinze> dcz[m]: 800 MB/s is still somewhat slow for a NVMe SSD. I think there might be some setting not yet properly done for the PCIe.
<dcz[m]> I'm still on SATA speeds, and it's been entirely rnough
<janrinze> I have had a different older kernel that managed >1400MB/s but i can't find how that worked. It's over PCIe3
<janrinze> Do we still use 4k page size or has 16k page size become the standard?
<dcz[m]> you mean sector size? or the RAM page?
<janrinze> RAM page
<janrinze> I'll test..
<janrinze> I've read somewhere that 16k page size increases performance.
<dcz[m]> I haven't seen anyone use it on Linux
<dcz[m]> I tried to build the kernel for that on the L5 but it didn't boot
<dcz[m]> there still should be an open issue on the bug tracker for that
<dcz[m]> is mediatek doing any mainline Linux/Coreboot contributions, or is it all Google?
alpernebbi_ has joined #linux-cros-arm
alpernebbi has quit [Ping timeout: 480 seconds]
alpernebbi_ has quit []