marcan changed the topic of #asahi to: Asahi Linux: porting Linux to Apple Silicon macs | Not ready for end users / self contained install yet. Soon. | General project discussion | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Topics: #asahi-dev #asahi-re #asahi-gpu #asahi-stream #asahi-offtopic | Keep things on topic | Logs: https://alx.sh/l/asahi
Gu____________________________ has quit [Ping timeout: 480 seconds]
bisko has quit [Read error: Connection reset by peer]
Gu____________________________ has joined #asahi
G_____________________________ has joined #asahi
Gue___________________________ has quit [Ping timeout: 480 seconds]
Gue___________________________ has joined #asahi
Gu____________________________ has quit [Ping timeout: 480 seconds]
G_____________________________ has quit [Ping timeout: 480 seconds]
user982492 has joined #asahi
sheepgoose has joined #asahi
jnn has joined #asahi
jn has quit [Ping timeout: 480 seconds]
sheepgoose has quit [Remote host closed the connection]
<matthewayers[m]>
Has anyone been able to find a Kubuntu iso for aarch64, or does anyone have any recommendations for an aarch64 distro that has kde plasma and apt?
<chadmed>
kde neon?
<chadmed>
i mean all distros are gonna have plasma in their package manager, so you could just use glanzmann's debian instructions and install plasma on top of that
<matthewayers[m]>
I am having trouble finding the aarch64 install for KDE neon. If you have a link to where I could download it that would be amazing
<matthewayers[m]>
* chadmed: I am
<chadmed>
i think you need to use the pinebook remix, which is very outdated now. your best bet if you want synaptic is probably just to use the debian-testing instructions and install plasma yourself after youve got it up and running
<chadmed>
unfortunately we're still not at a point where you can just boot a vanilla distro livecd and expect to install it as you would on an amd64 machine, but we're getting there!
<matthewayers[m]>
I'm running within a VM on a M1 Max MBP right now, but thanks for the info
<chadmed>
oh right that simplifies things
<chadmed>
the easiest way to get kubuntu on arm with a gui install procedure is to install vanilla ubuntu and then install the kubuntu-desktop metapackage from the ubuntu repos
<chadmed>
then uninstall gnome or whatever ubuntu's default DE is these days
<matthewayers[m]>
chadmed: Yeah, that's what my original plan was, but I am having trouble finding kubuntu-desktop right now if you'd be able to send over a link. Thanks for your help!
<chadmed>
im looking, but the latest i can find is for 18.04 lts
<chadmed>
looks like they stopped supporting it or something
<chadmed>
mustnt exist for arm anymore then, thats unfortunate
<chadmed>
what about the plasma-meta package
<chadmed>
oh its actually called kde-standard
<chadmed>
yeah that def exists for arm64 on ubuntu
<matthewayers[m]>
And we're off! Haha thanks for your help! I'll be sure to let you know if that works. I am a huge fan of KDE and I hope more arm ports are released in the future
<chadmed>
no problem :) btw, virtually all FOSS works out of the box on aarch64 these days, provided its in the repos of whatever distro you're using. since youre on vanilla ubuntu, virtually everything should be there so long as you know what the package is called
<tpw_rules>
kettenis: does your keyboard disable hack affect keyboards on the usb-c ports of the mac mini?
sheepgoose has joined #asahi
PhilippvK has joined #asahi
phiologe has quit [Ping timeout: 480 seconds]
sheepgoose has quit [Remote host closed the connection]
<amw>
It says 'AIGLX: Screen 0 is not DRI2 capable' and Backtrace : OsLookupColor+0x188 - if that means anything to anyone?
marvin24 has joined #asahi
hendry has joined #asahi
marvin24_ has quit [Ping timeout: 480 seconds]
<Orionian>
joske: Sorry for ping, but I'm also trying to test out internal speakers on my MBA, and I've built povik's branch, but dmesg still says no sound card found. So I'm trying to apply the DT & m1n1 changes now, but I don't know how to apply povik's paste. Can you please tell me what are the exact steps you did to get it working? Thanks!
<Orionian>
nvm, turned out you need to add the updated device tree to u-boot as well, it's working now
<chadmed>
yeah the DT needs to be provided by m1n1 for things to work properly. feeding a dtb to the kernel with a boot argument is not and likely never will be supported
shenki has quit [Quit: leaving]
gladiac has joined #asahi
user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
user982492 has joined #asahi
Gues__________________________ has joined #asahi
shenki has joined #asahi
<Glanzmann>
amw: It might be the framebuffer collor mapping. I give a training till 15:00 german time, than I'll try to reproduce.
nzzz has quit [Remote host closed the connection]
Gue___________________________ has quit [Ping timeout: 480 seconds]
<j`ey>
ChaosPrincess: thanks, managed to find it via a PR anyway!
tomtastic_ has joined #asahi
jnn is now known as jn
tomtastic has quit [Ping timeout: 480 seconds]
mblancom has joined #asahi
<steffen[m]>
Has anyone had "Failed to personalize the software update" when trying to reinstall macos from recovery?
<clrwf0x80>
Glanzmann, thanks! I'm still processing how it works
<clrwf0x80>
does it matter if there is any activation lock on macbook ?
<clrwf0x80>
do we have access to NAND from Asahi linux? especially to hidden sysconfig patition where they store SN/Wifi mac/BT mac?
<Glanzmann>
clrwf0x80: We have access to the nand, but I would not fiddle around with it for the time being until m a r c a n has wiped one and we will see if we can recover from it.
<Glanzmann>
clrwf0x80: How it works, is pretty basic: You have by default fourt partitions: iboot, macos, 1tr. We make macos smaller and put a stub partition which is 2.5GB in size. This stub partition we use to install m1n1. M1n1 chainloads u-boot which loads grub which loads the kernel.
<Glanzmann>
We require two three aditional partitions: one for the stub, one for the esp, one for the root filesystem.
<Glanzmann>
You can use the macos boot picker to switch between linux/openbsd and macos.
<clrwf0x80>
impressive
<clrwf0x80>
haven't seen, wifi does get a mac address from chip internal eprom, or you have to specify one when putting the interface up?
<chadmed>
m1n1 puts it into the DT at runtime AIUI
<chadmed>
no user intervention is required in any case
<ChristianvonElm[m]>
Can someone tell me the magic assembly for enabling and using the Apple cycle counter? I already got it to work once but I lost that code.
<Glanzmann>
ChristianvonElm[m]: find /sys | grep -i battery and look at every file.
<ChristianvonElm[m]>
I am trying to do measurements on bare metal, so that isnt an option :)
clrwf0x80 has quit [Remote host closed the connection]
<_jannau_>
clrwf0x80: MAC addresses are in the ADT and m1n1 transfers them to device tree, no need to access anything other than memory. iboot put it there for the os
user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
mblancom has left #asahi [#asahi]
<mps>
hmm, rust in m1n1, ofc however it is done is good though I would like to see basic things is made by plain C
<j`ey>
it will be, only the chainloading of m1n1 from nvme will be in rust
<mps>
ah, ok.
<mps>
(two years ago I started to learn rust for system programming but after some time concluded it is not good for this and stopped to learn it futher)
subject38[m] has joined #asahi
<chadmed>
i like rust as a language, but rustaceans are very annoying and rustc's development cycle is far too unstable to make it useful. which is a shame because the community seems recalcitrant to any alternatives being proposed
<j`ey>
Im not really sure what alternatives have been proposed
<chadmed>
a couple of years ago someone wrote a front end for gcc and there were... arguments
<j`ey>
well there's a gccrs project now doing it
<chadmed>
seems to have settled down lately though
<j`ey>
in terms of new features.. well, people want new features to make it easier or better to program in rust, i cant really see a way around that
<j`ey>
if a crate wants to use a new feature but you want to stick to an older compiler.. you just have to use an older version of that crate
<j`ey>
(in fact there is a gcc frontend and a separate gcc backend that uses the rustc frontend)
<ChaosPrincess>
have they implemented borrowck in gcc rust?
<j`ey>
I dont think so yet
<j`ey>
since they still dont have all the other language features
<mps>
iirc goal of rust was to be better C++ and they reached to only slow compile target ;)
<mps>
sorry for OT msg
<j`ey>
it's all OT right now :P
<ChaosPrincess>
nah, rust is the best language out there and we should riir the rest of m1n1
<j`ey>
lol
* Glanzmann
misses perl support in m1n1.
<mps>
:D
clrwf0x80 has joined #asahi
<povik>
some alternative timeline...
<clrwf0x80>
Glanzmann, i'm trying to boot livesystem from here: https://github.com/AsahiLinux/docs/wiki/Debian, have uncompressed asahi-debian-live.tar on usb drive.. but M1 mac shows just Options menu, no other boot
<clrwf0x80>
what can be wrong?
<j`ey>
clrwf0x80: did you run the installer?
<clrwf0x80>
no, I want just to run in Livesystem
<j`ey>
I mean the asahi-installer
<j`ey>
not the debian one
<kov>
clrwf0x80, you need to install m1n1/u-boot before you can boot the live system from USB
<kov>
clrwf0x80, "Follow the U-Boot Wiki Entry to make space, setup a 12.1 stub partition using the asahi installer and install u-boot." <- this is not optional
<clrwf0x80>
i see.. this means I can't boot external without touching internal nand of m1 device
<_jannau_>
yes, macos has the same restriction. apple silicon macs can't boot from external storage
<Glanzmann>
clrwf0x80: You did not create the stub partition. Watch the first Debian video, everything is in there.
<Glanzmann>
I'll redo the video soon with voice to explain things.
<clrwf0x80>
i guess my problem is I can't access terminal on M1 device.. so far there can't be made bootable usb image that will load linux instead of macos
<j`ey>
why cant you access a terminal?
<clrwf0x80>
because of activation lock
<clrwf0x80>
secureboot is disabled anyway
<clrwf0x80>
I can see other bootable usb stick icon
<clrwf0x80>
asahi doesn't show
<sven>
you have to be able to access 1TR and run the asahi installer from there, no way around it
<sven>
and you can contact apple with a proof of purchase and they can unlock that activation lock
<clrwf0x80>
not going to work, bought it from ebay, it was working just fine until I updated OS and bricked it
<clrwf0x80>
this is how nowadays we don't really own devices
<chadmed>
its not the config, its the actual kernel. the pcie driver races against the wifi chip's power on sequence so its never probed. the fix is to get hotplug working and let the device tell us via the smc when its ready to be probed i think
<chadmed>
youll probably need to revert back to an earlier commit of the kernel to get wifi working properly again
ChristianvonElm[m] has left #asahi [#asahi]
<Glanzmann>
chadmed: I'm also using the asahi tree and never experienced this problem.
<chadmed>
have you updated your kernel since it was rebased?
<chadmed>
it seems to be endemic to the j31xx machines
<Glanzmann>
chadmed: Yes.
<Glanzmann>
chadmed: Yes, but only with the arch kernel build.
<chadmed>
ive confirmed with my own kernel build, its not just the config that comes from the PKGBUILD
<Glanzmann>
chadmed: But I think I had the issue shortly after marcan released it and noone could tell me what I was doing wrong, than I changed the config and than it worked. But maybe I try to reproduce it and than change the 'hz' value that j`ey always wants to know and noone changes and see if it fights the symptoms.
<chadmed>
i changed the timeout in the pcie-apple driver to 250us and it did not fix the problem
<Glanzmann>
chadmed: I see, but I did a lot of reboots on my mini on my air (at least 2-5 per day) and I not once had the issue.
<j`ey>
well kit_ty_kate has shown a case where the HZ value doesnt matter, the pcie device comes up but still fails
<Glanzmann>
chadmed: Oh, good to know.
<chadmed>
but its definitely a race because sometimes it actually does work if i reboot enough times
<chadmed>
fwiw ive also experienced similar problems with the wifi on my 2011 mac mini and on two raspberry pis
<chadmed>
broadcom really just are the world leaders here
<jannau>
so 1 M1 Max die is 2k and they gift the rest of the hardware
<pugguu[m]1>
sven: lol me too but I don’t have 4k laying around aspetally at 17 years old lol
<j`ey>
gift?
<j`ey>
oh
<j`ey>
pugguu[m]1: finish school and get a good job!
<marcan>
welp, no M2
<marcan>
boring
<j`ey>
marcan: new build machine tho
<marcan>
yeah
<marcan>
I was thinking 3 Mac Minis as home cluster, but it's sounding like a heterogenous one may be the ticket
<robher>
and a 27" iPad
<marcan>
Mac Studio, M1 Mac Mini, and M2 for the third
<pugguu[m]1>
Then again it would only take me 4 years to save 4 grand
<marcan>
gives me test machines + redundancy
<ChaosPrincess>
how fast is 1 zen2 core vs a m1 core? for compile
<marcan>
and I'd totally get the display and call that + M1 Pro or Max my main desktop in the near future
<marcan>
good test subject for proper thunderbolt/etc, and worth supporting the fancy apple things
<j`ey>
why the display?
<j`ey>
i guess you just answered that :P
<marcan>
ChaosPrincess: the 10-core M1 Pro is about as fast as my 16-core zen1 threadripper
<marcan>
so the Mac Studio already thoroughly obsoletes my existing build machine
<ChaosPrincess>
so, for build machines a 32 core zen 2 should still be faster?
<kov>
I'd bet yes
<marcan>
funny thing is I still need x86 for building my Gentoo stuff, for servers/other boxes... so I get the feeling what's going to end up happening is I set up distcc and a cross compiler on the M1 Studio and have the threadripper farm out part of the build to *that :')
<marcan>
yes, it would be
<marcan>
32 core zen 1 technically will beat it too, by a little bit
<marcan>
but those are also going to chew much more power and don't come with a giant GPU
<ChaosPrincess>
dont need a gpu packed in a rack chassis :P
<landscape15[m]>
marcan: I’m more excited to see how well Linux will run on M1 Ultra, and not on macOS. 800Gb/S of memory bandwidth is unbelievable. It is faster than the top of the line amd epyc
<marcan>
also depends on the workload, I could see some really NUMA-adverse workloads being way faster on the M1 Ultra due to, presumably, quite a bit tighter cross-die latency
<marcan>
plus the already better RAM
<marcan>
but compiling isn't one
<marcan>
landscape15[m]: it'll be bottlenecked off of the CPUs though
<ChaosPrincess>
well, for compile its also linking that takes forever and barely parallelizes
<marcan>
you'll get 400 or so without using the GPUs
<marcan>
but still
<kettenis>
so M1 Ultra is 2 M1 Pro dies we reckon?
<marcan>
hey apple, you said I could order today, where's the damn order button?
<marcan>
at least the .jp page hasn't updated yet :(
<marcan>
kettenis: M1 Max
<marcan>
M1 Pro does not have D2D
<kettenis>
ah
<landscape15[m]>
marcan Also .com ;)
<marcan>
I want to sleep ;_;
<jannau>
marcan: it's there in the german store for me
<marcan>
though I guess I'm not in a terrible rush any more
<kettenis>
so now we get to test how well you can predict the future with respect to AIC2?
<marcan>
oh
<marcan>
showed up now
<marcan>
ok, it's a build machine, going for 48-core GPU on this one, 64-core is going to be a waste I reckon, not worth the extra $1k
<henje[m]>
marcan: do you reckon, that M1 Ultra already works with Linux?
<marcan>
RAM though... do I need 128GB? I think I don't...
<marcan>
henje[m]: probably
<marcan>
m1n1 may or may not need changes
<marcan>
linux probably won't unless I goofed up the multi-die AIC2 support
<ChaosPrincess>
in before a heap of chicken bits to make cross die interconnect work
the_lanetly_052__ has quit [Ping timeout: 480 seconds]
<marcan>
64GB or 128GB... hmm... my TR (64GB) *does* run out of RAM doing certain builds, but that runs 33 threads, this has 20...
<landscape15[m]>
henje: most of the work is needed for GPU support I guess
<marcan>
probably 64GB then
<marcan>
besides, considering apparently I'm expected to keep buying these, not like it has to last me 5 years as a main machine...
<henje[m]>
With work I meant mainly CPU
<kettenis>
hey you're forgetting about rust!
<tpw_rules>
is this what our patreon contributions go towards
<marcan>
tpw_rules: it's one thing!
<marcan>
only reason I can even consider getting testing hardware like this
<marcan>
otherwise, no way
<tpw_rules>
then i, as a patreon supporter and RAM fetishist, say get 128GB
<marcan>
ahahahaha
<marcan>
okay, fine
<marcan>
I probably don't need the maxed out GPU though ;)
<marcan>
and 4TB storage should be enough too
<marcan>
won't get the display just yet, that'll come later and I should probably do initial TB bringup with a dock or something, no need to rush that
<henje[m]>
I wonder if it’s possible to run Linux on the display ;)
<marcan>
a
<marcan>
*also, the 10G ethernet should cover that part of the matrix, which I was lacking so far
<marcan>
presumably it's the same as on the M1 Mac Mini
<marcan>
so that's good
<marcan>
oh god the shipping date is already april 8? boo
<jannau>
128G is two weeks later
<j`ey>
marcan: you got plenty of other stuff to play with :P
<jannau>
64G ram is here still 21. - 23.3
<j`ey>
(in the meantime)
<marcan>
jannau: :<
<marcan>
tpw_rules: damn you
<tpw_rules>
i'm not sure i care that much
<j`ey>
jannau: are you actually buying anything?
<tpw_rules>
for me when i checked both displayed march 18
<marcan>
I probably don't really need 128G, especially because I'm going to have to end up getting the Mac Pro when that comes out...
<tpw_rules>
i relent
<j`ey>
marcan: how much extra is it?
<marcan>
1k lol
<j`ey>
dont bother.. I think maybe
<j`ey>
but Im also adverse to spending money heh
<marcan>
yeah
<marcan>
ohh wait
<marcan>
it's the GPU
<marcan>
bumping up the GPU makes it come faster lol
<marcan>
ah, high GPU and lower RAM
<mini_>
the monitor has already slipped a week as well!