marcan changed the topic of #asahi to: Asahi Linux: porting Linux to Apple Silicon macs | 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
<Glanzmann>
j`ey: That option does not exist in a current kernel config.
yuyichao has quit [Ping timeout: 480 seconds]
<j`ey>
drivers/video/fbdev/Kconfig line 2195ish
<Glanzmann>
You're right. Strange. Because it was not included in my .config.
<Glanzmann>
And plays youtube, although with tiering.
aidenfoxivey has joined #asahi
<Glanzmann>
No, it was _not_ the kernel config it was this one: curl https://ab34.de/u/device.conf > /etc/X11/xorg.conf.d/device.conf
<Glanzmann>
Of course than X is slow again.
<Glanzmann>
So in order to get firefox to work, you need to use the fbdev driver and not the modesetting driver.
darkapex2 has joined #asahi
darkapex1 has quit [Ping timeout: 480 seconds]
StupidYui has quit [Read error: Connection reset by peer]
yuyichao has joined #asahi
rwhitby has quit [Quit: rwhitby]
Leidenfrost has joined #asahi
<Leidenfrost>
Hello guys. Is Asahi usable enough for dual bot mac/linux and basic desktop usage? The most demanding usecase will be Youtube and some compiling
<i509vcb[m]>
I recall discussion here in the past that if you are using a mac mini it is usable enough (can't recall audio situation).
<i509vcb[m]>
Although don't expect a flawless experience
<i509vcb[m]>
I think the mini is still on software rendering?
phiologe has joined #asahi
PhilippvK has quit [Ping timeout: 480 seconds]
Leidenfrost has quit [Ping timeout: 480 seconds]
darkapex3 has joined #asahi
darkapex2 has quit [Ping timeout: 480 seconds]
darkapex4 has joined #asahi
darkapex3 has quit [Ping timeout: 480 seconds]
marvin24_ has joined #asahi
marvin24 has quit [Ping timeout: 480 seconds]
asmopve has joined #asahi
kijdshfgg has joined #asahi
kijdshfgg has quit []
kijdshfgg has joined #asahi
<kijdshfgg>
.. c e r t a i n l y , - z a m e r i c a n s -n e e d e d s o m e t h i n g - l i k e -9 / 11 - t o J u s t i f y i n v a d i n g - i r - a q w h i c h h a s b e e n a l r e a d y p la n n e d a s a p a r t o f c r e a t i v e c -h a o s p l a n f o r m i d d l e -e a s t D i d u s a t r a i n &
<kijdshfgg>
s u p p l y i s i s - w i t h w e a p o n s l i k e i t d i d w i t h a l - q a- e d a t o j u s t i f y c r e a t i n g w a r .s C R -E - A T - I V E C H A - O S d i d - c i a - d i d 9 / 11 o r i t j u s t l e t i t h a p p e n i f a l q a e d a d i d i t
<kijdshfgg>
W H Y t o k - i - l - l - 9 m i l l i o n - i r -a q i - s a b o u t 9 - m i l l i o n - i r a q i - d i -e d E i t h e r -b e c a u s e - o f d i r e c t a m e r ic a n v i o l e n c e -a n d b e c a u s e o f s i e g e u s a m a d e a g a i n s t i r - a q t h a t p r e v e n t e d- i -r a -q i -f r o m e s s e n t i a l
<kijdshfgg>
l i v i n g m a t e r i a l s , f o o d , m e d i c i n e a n d e v e n -p e n c i l s f o r z c h i l d e r n - - i s i s a n d a l q- a e d a - o n l y a p p e a r e d i n i r - a q a f t e r u s a i n v a s i o n , D i d u s a p a v e t h e w a y for i s- i s t o i r a -q ? s a d -d -a m h
<kijdshfgg>
u s- s i n who l o s t m o s t of his p o -w e r in 1 st , 2 nd g u l f w a r s a n d d u r i n g 1 0 y e a r s of s i e g e - , -d i d -n o t -a l l o w - i s ` i s or a l , q a , e d e a t o e n t e r -i r -a q , e v e n -t o ` -h e l p -h i m --a g a i n s t -u s a
<kijdshfgg>
asmopve has quit [Quit: Leaving]
kijdshfgg has quit [Quit: Leaving]
<jannau>
marcan: please kick
<marcan>
jannau: they're already gone, these are bots that come and go
<marcan>
looks like they're connecting via tor
<jannau>
they stayed yesterday for some time. this time they spammed #oftc too
<marcan>
I think we have nobody else on tor, so let's do the practical thing
<amw>
I also found out that I need to compile the kernel with CONFIG_TYPEC as builtin now to get my USB keyboard working... dts has changed quite a bit!
<amw>
Mine is macBook Air 2020 - t8103-j313
<mps>
Glanzmann: about month ago I tried with fbdev driver but it segfaults when starting xorg so I switched to simpledrm
<Glanzmann>
mps: It works for me on Debian testing on the mini.
<Glanzmann>
mps: I think I got now why modesetting (aka simpledrm) does not work.
<mps>
some people reported that FF works on systems with glibc so I think it is related to (yet unknown to me) xorg problem with musl
<Glanzmann>
mps: I have Debian testing. I think that it does not have musl, does it?
<mps>
when I finish my $day_job today I will try with older alpine release and old xorg to see if there are any changes
<mps>
Glanzmann: debian is glibc based, not musl libc
<Glanzmann>
mps: I also tried to compile the kernel with 4KB page size, that broke USB-a however USB-C was still working with a USB-C to USB-A HUB.
<Glanzmann>
Firefox did not start. But with the fbdev it does. But you notice that everything is slower for example fullterm xterm scrolling and even moving the mouse.
<mps>
Glanzmann: also I compiled kernel with 4K page size and it works same as 16K
<Glanzmann>
mps: Do you found a way to set the resolution to anything different than 1920x1080?
<Glanzmann>
mps: I see, strange, maybe I screwed something else up. Are you on macbook air or mini
<Glanzmann>
?
<mps>
Glanzmann: didn't tried to change resolution
<mps>
on my mbp resolution is 2560x1600
<mps>
macbook pro 2020 is my machine
<Glanzmann>
mps: I see, perfect. I also have a macbook air, but run macos at the moment. However now that the keyboard is working and firefox, maybe I'll switch to linux. I see. I do all the testing on the mini.
<mps>
Glanzmann: heh, also. what keeps me switch to use it for work is FF
Techcable has joined #asahi
<Glanzmann>
mps: I see. So FF should work now. I noticed that if you disable smooth scrolling, scrolling is actually more smooth. However if you watch a video in youtube or mpv fullscreen you have a lot of tiering.
<mps>
Glanzmann: in current state it is expected that not everything is smooth, so not big problem for me
<sven>
the usb a port won't work with 4k kernels for now
<Glanzmann>
sven: I noticed that. But since mps has a macbook pro, he has no usb-a. :-)
<sven>
sure
<mps>
sven: hmm, my external usb wifi works
<sven>
on the macbook pro internal wifi won't work
<mps>
ah, internal wifi is on usb?
<sven>
no
<sven>
pcie won't work
<Glanzmann>
sven: But the mini works fine. I mean once we have GPU driver that would be really great. And also nvme random write performance needs to be improved. At the moment I use 'eatmydata apt-get install -y <packages>'. That speeds up things because apt runs a 'sync' after each packet, so if you install many, it slows you down.
<sven>
and usb a ports, internal wifi and ethernet are on pcie
<mps>
sven: you mean with asahi kernel?
<j`ey>
with 4k pages
<Glanzmann>
sven: That explains why it lost my network card as well with 4k pages.
<sven>
you guys figure it out, i'm busy, sorry :D
<Glanzmann>
sven: Got it, thanks.
<mps>
I don't see any difference with 4K or 16K pages on mainline kernel with jannau patch
<Glanzmann>
mps: I see. On mini I noticed what sven said (USB-A and network stopped working). Wifi I don't use.
<mps>
also I'm busy with $day_job now, will have more time on the evening to 'play' again with macbook
<zimsneexh>
Is there any way to list CPU freq in linux? cat /proc/cpuinfo doesn't give Frequency and I assume they run at quite a low clockspeed?
<Glanzmann>
zimsneexh: IIRC, the cpufreq driver is set to maximum performance.
<j`ey>
just a little under maximum
<j`ey>
when m1n1 boots
<zimsneexh>
Hm, that would be surprising. I tried to compile the kernel on baremetal asahi and it was quite a lot slower than even in parallels. Or is it scheduler related?
<Glanzmann>
zimsneexh: Maybe the ssd, try to put 'eatmydata' before.
<Glanzmann>
zimsneexh: I'm running the Linus Torvalds benchmark right now for you: make allmodconfig; time eatmydata make -j 16 V=0 &> /dev/null
<zimsneexh>
Hm, I'm running it of an external SSD. That could be it..
<j`ey>
zimsneexh: how long was the build?
<zimsneexh>
j`ey: In parallels the build took around 4 minutes (parallels only uses the 4 performance cores) and baremetal i killed it 10 or 11 minutes in, I think.
<j`ey>
zimsneexh: and all the same options?
<_jannau_>
Glanzmann: should be faster after running proxyclient/experiments/cpu_pstates.py, m1n1 initializes the performance cores just at 2GHz
<zimsneexh>
j`ey: default config for the asahi branch, yes
<_jannau_>
zimsneexh: external SSD might be partly limited by USB 2 speeds if connected to a USB-C port
<zimsneexh>
_jannau_: Could be it. The MBA i'm trying this on only has type-C ports
<zimsneexh>
I could try in a ramdisk, that should be plenty fast
<Glanzmann>
jannau: I see. I thought the cpufreq driver takes care of that, but I think it is not enabled on my mini. Btw. this is with your kernel config + usb sound: https://pbot.rmdir.de/JiI5c5Gh611h9xjytaPwLw
aleasto has joined #asahi
aidenfoxivey has quit [Quit: aidenfoxivey]
aidenfoxivey has joined #asahi
gladiac is now known as Guest8136
gladiac has joined #asahi
bps has quit [Ping timeout: 480 seconds]
Guest8136 has quit [Ping timeout: 480 seconds]
darkapex has joined #asahi
darkapex4 has quit [Ping timeout: 480 seconds]
bps2 has joined #asahi
the_lanetly_052__ has joined #asahi
aleasto has quit [Remote host closed the connection]
Gaspare has joined #asahi
yuyichao has quit [Ping timeout: 480 seconds]
aleasto has joined #asahi
yuyichao has joined #asahi
kgarrington has joined #asahi
kgarrington has quit [Remote host closed the connection]
yuyichao has quit [Ping timeout: 480 seconds]
mini_ has joined #asahi
the_lanetly_052___ has joined #asahi
mini_ has quit [Quit: ZNC closing...]
the_lanetly_052__ has quit [Ping timeout: 480 seconds]
<j`ey>
mps: check jannau's branch ^ his is based on asahi
<mps>
j`ey: ok
<j`ey>
mine is just mismatched hacked stuff. Im looking forward to 5.17, hope it has a lot more stuff!
malvo has quit [Ping timeout: 480 seconds]
Glanzmann has joined #asahi
<Glanzmann>
NightRaven[m]: https://ab34.de/u/asahi.txt - Which Distribution on which device do you want to install?
<Glanzmann>
jannau: Are you going to include the keyboard/spi patches in your AsahiLinux-PKGBUILD repository?
<j`ey>
Glanzmann: probably when theyre working a bit better
<zimsneexh>
jannau: Is there a kernel config to use with the spi-keyboard tree?
<j`ey>
zimsneexh: just use your config and turn on CONFIG_KEYBOARD_APPLESPI
<j`ey>
and CONFIG_SPI_APPLE
<NightRaven[m]>
Glanzmann: The problem is I can't use another device
<NightRaven[m]>
* The problem is I can't use another device I only have my MacBook
<j`ey>
NightRaven[m]: you said you had an rpi too?
<NightRaven[m]>
j`ey: I do but like I cannot use it for my mac since I cannot it to my mac
<NightRaven[m]>
* I do but like I cannot use it for my mac since I cannot connect it to my mac
<zimsneexh>
NightRaven[m]: You could build m1n1, kernel image and a device tree and just install that macho as a boot object, I'm guessing
<Glanzmann>
NightRaven[m]: do you have a usb stick?
<NightRaven[m]>
I do
<Glanzmann>
Than use that.
<NightRaven[m]>
But how it only shows how to do it using a second device
<jannau>
tree refreshed, I can't break it anymore with caps lock, waiting 'Inter Transaction Us' between the key event and toggling the led seems to fix that
<j`ey>
NightRaven[m]: you can conenct it to the mac, as I said last time, thats how Im doing it
<NightRaven[m]>
But when I I boot into the macho it says waiting for proxy
<Glanzmann>
NightRaven[m]: Than you need to put the m1n1, kernel, initrd (if you use one) and kernel command line in one file.
<Glanzmann>
Look in yesterdays IRC backlog. There is an example IIRC.
<j`ey>
jannau: yay!
<Glanzmann>
jannau: You use MacBook Air with wayland, correct?
<jannau>
Glanzmann: macbook pro 14"
<Glanzmann>
I see.
<Glanzmann>
NightRaven[m]: 10:36 <mps> as400: I have this script "cat m1n1.macho <(echo 'boot-args=root=PARTUUID=3d20affd-c082-421b-a111-f5d6b1587fe4 rootwait') nk.gz nk-t8103-j293.dtb > ../nk.macho"
<Glanzmann>
NightRaven[m]: nk.gz is the kernel, mps doesn't have a initrd.
<mps>
yes, you could add initramfs there if you have it
<NightRaven[m]>
One question what do I put into the partuuid I will compile the linux kernel and then run that but do I have to change the partuuid
<Glanzmann>
NightRaven[m]: root=/dev/sda1 and later root=/dev/nvme0n1 or the uuid which you get with blkdev-id or so.
<NightRaven[m]>
* Glanzmann : One question
<Glanzmann>
root=/dev/nvme0n1pX*
<jannau>
Glanzmann: I'm not sure if I want to update the package to a linux-next based tree. I'll see if I can rebase it onto v5.16-rc4. I think the simpledrm fixes are the only incompatible changes with 5.16-rc
<NightRaven[m]>
Oh ok I will run blkdev-id let me see if I can find it
<Glanzmann>
jannau: I see. What are these simpledrm fixes about?
<Glanzmann>
First thing you have to do is, make space, than use the asahi installer. Than you need a linux root filesystem on a usb stick. YOu can do that with your raspberry pie.
<jannau>
Glanzmann: supporting the 10-bit color format apple uses for the frame buffer. There are conflicting already in drm for linux 5.17
<NightRaven[m]>
Glanzmann: i mean i have manjaro installed on my rpi but as i have said i cannot use the rpi since i cannot connect it to my mac
<mps>
built asahi kernel with input patches, booted but keyboard/touchpad are 'dead'
<Glanzmann>
Than you need to cat the boot macho with the m1n1 kernel, command line, kernel
<mps>
and firefox shows same problem, i.e. it is stuck on start
<NightRaven[m]>
i will try to get the linux rootfs system on a usb
<Glanzmann>
jannau: I see. I was wondering yesterday who made that work becasue marcan mentioned it is non standard. I see.
<Glanzmann>
NightRaven[m]: What kind of m1 device do you have? mini, macbook air, macbook pro?
<jannau>
rebasing was painless, just the drm color conversion patch
<NightRaven[m]>
Glanzmann: I have a MacBook pro 13 inch 2020
<Glanzmann>
jannau: What is the name of the branch?
<Glanzmann>
jannau: Which dtb is for the macbook pro?
<Glanzmann>
j`ey: You have todays keyboard patches running on the macbook air without xorg, right?
malvo has joined #asahi
<j`ey>
Glanzmann: yes
<Glanzmann>
I see. Than I'll try with jannaus rebase. But mps seems to have no luck, and IIRC he also has a macbook air.
<Glanzmann>
mps: Did you saw the fix for firefox?
<mps>
Glanzmann: I have mb pro
<mps>
as I wrote above firefox is still stuck on asahi kernel
<Glanzmann>
mps: I see, but jannau has to and for him it seems to work and IIRC he has it working with wayland.
<mps>
practically same as mainline with jannau patch but keyboard doesn't work and it is shown in evtest
<mps>
so, I will wait for 5.17-rc
<jannau>
mps: try changing spi-max-frequency back to 2000000 in t8103-j293.dts / t8103-j313.dts
<jannau>
any spi messages in dmesg?
<NightRaven[m]>
<NightRaven[m]> "I have a MacBook pro 13 inch 202..." <- Does it affect it
<mps>
jannau: I reverted it to mainline with your patch, and have to visit someone now, will try tomorrow again
<NightRaven[m]>
<Glanzmann> "NightRaven: 10:36 <mps> as400: I..." <- Is there a way I can find my device ssd uuid like this so I can boot without a second device
Gues__________________________ has joined #asahi
<mps>
NightRaven[m]: blkid should show it
<NightRaven[m]>
But like I need to find it on my mac terminal
<NightRaven[m]>
blkid is a Linux command it does not work on Mac
<mps>
NightRaven[m]: right
<NightRaven[m]>
But I need to find it on my mac os
<NightRaven[m]>
Any way ?
Gues__________________________ has quit []
<mps>
I first made rootFS on usb ssd disk, then booted it and installed on internal nvme and looked for partuuid, then recreated macho and reinstalled in 1TR
<mps>
complicated yes, but that was 'safe' path for me
<NightRaven[m]>
Any tutorial how to make a rootFS on USB and boot from it
<NightRaven[m]>
mps: How did you do it
<mps>
well, actually I copied it from my arm64 chromebook
<mps>
but for test I made simple script to install basic alpine linux and tested it
<mps>
you probably will not use alpine (for now at least ;) )
<mps>
also for test I 'fired' qemu aarch64 and installed alpine from iso img on usb stick
<Glanzmann>
NightRaven[m]: On you raspberry pie: mkfs.ext4 /dev/sdX (replace X with the usb stick device)
<Glanzmann>
Than you mount it: mount /dev/sdX /mnt
<Glanzmann>
Than you get the root filesystem and extract it.
<Glanzmann>
NightRaven[m]: Which Distribution do you want to install?
<NightRaven[m]>
For now I want arch Linux but on my raspberry pi I have Manjaro on it
<mps>
I have somewhere script to completelly install alpine on olimex a64 SBC, maybe I could adapt it for M1 and post somewhere
<NightRaven[m]>
<Glanzmann> "NightRaven: Which Distribution..." <- But can I just boot into the rootFS on my mac using my USB and do blkid to find the. Uuid
<zimsneexh>
Yes, this one. Keyboard seemed fine, touchpad did nothing. Rebooted and it seems fine for now, although the touchpad seems somewhat "laggy" compared to rc3_1-keyboard
<zimsneexh>
Ah, never mind that. After checking again, seems about the same
<jannau>
please check dmesg for messages containing 'spi' if the touchpad is not working again
kumoko has joined #asahi
kumoko has quit []
<NightRaven[m]>
ok so i am quite confused for PARTUUID is this my ssd uuid and i just input it there but i am confused how i can find it do i boot into a linux system on my mac if i have to then how can i do it using a usb i have tried the ubuntu one by corellium and it did not work so any ideas ?
<zimsneexh>
Build a m1n1 macho, build a .macho image with m1n1, your kernel and your device tree. Set that m1n1-payload as the boot object then bootstrap some rootfs to a USB drive. Should work.