#
…

2022-12-23

00:40swaggie has joined #asahi-alt
01:54swaggie has quit [Remote host closed the connection]
02:05swaggie has joined #asahi-alt
02:07jamespmo_ has joined #asahi-alt
02:14jamespmorgan has quit [Ping timeout: 480 seconds]
02:48swaggie has quit [Remote host closed the connection]
02:49swaggie has joined #asahi-alt
02:57swaggie has quit [Ping timeout: 480 seconds]
04:04swaggie has joined #asahi-alt
04:50swaggie has quit [Remote host closed the connection]
05:53jamespmorgan has joined #asahi-alt
05:59jamespmo_ has quit [Ping timeout: 480 seconds]
06:42jamespmo_ has joined #asahi-alt
06:49jamespmorgan has quit [Ping timeout: 480 seconds]
06:52jamespmorgan has joined #asahi-alt
06:58jamespmo_ has quit [Ping timeout: 480 seconds]
08:07swaggie has joined #asahi-alt
09:13cylm_ has quit [Ping timeout: 480 seconds]
09:57jannauGlanzmann: https://github.com/AsahiLinux/m1n1/pull/272 should unbreak dcp with m1n1 setting high resolution display modes at boot on mac mini/studio
10:46swaggie has quit [Remote host closed the connection]
10:47swaggie has joined #asahi-alt
10:56swaggie has quit [Ping timeout: 480 seconds]
11:21swaggie has joined #asahi-alt
11:30swaggie has quit [Ping timeout: 480 seconds]
11:44swaggie has joined #asahi-alt
11:45Dcow has joined #asahi-alt
11:54Dcow has quit [Ping timeout: 480 seconds]
12:01swaggie has quit [Ping timeout: 480 seconds]
12:02Glanzmann has joined #asahi-alt
12:03Glanzmannjannau: Thank you. I'll incorporate it. I have only a 2k screen on the mini. Ry_Darcy has a 4k screen on the mini, but he did not complain. So I assume it works for him. What kind of resolution do I need to reproduce the error? Unfortunately the biggst screen I have is a TV with 4k.
12:09mpshow can I know if I have display with this thing called 'notch'? I'm using m1pro macbook
12:11Glanzmannmps: I think the current m1n1 spares out the notch.
12:12GlanzmannIf you want to use the notch areas you need to patch m1n1. Don't know the details but it was in the irc backlog somewhere.
12:14mpsGlanzmann: thanks. I don't have any incetive to extend screen area just curiosa
12:15Glanzmannmps: I see.
12:20ashi has joined #asahi-alt
12:20swaggie has joined #asahi-alt
12:24ashimps: the notch is hidden by default, I can only speak for the m2 air, resolution is 2560x1600 with notch hidden, but there is an extra space with rounded edges and no pixels where the webcam is, making ist 2560x1664 (64 extra height)
12:26ashimps: I enabled the notch area and patched gnome3 css to make the top panel 64 pixel, and moved the date/time display to the right with a gnome shell extension, this is super cool imo, so 2560x1600 real screen resolution with the area around the notch for panel applet stuff
12:27ashimps: enabling the notch is a kernel/module parameter, you do not patch/compile anything yourself
12:29j`eymps: the 'notch' is the webcam that comes over the screen a bit
12:29swaggie has quit [Ping timeout: 480 seconds]
12:33ashij`ey: thanks for making this a simple sentence :D
12:33ashiGlanzmann: the area around the notch can be enabled without patching m1n1
12:35j`eyashi: even simpler is: 14" pro has notch, yes :)
12:36Dcow has joined #asahi-alt
12:36ashij`ey: I tried to find that info but apple does not say anything about that https://support.apple.com/kb/SP824?locale=en_US ;)
12:36ashi"2560-by-1600 native resolution at 227 pixels per inch"
12:37ashiAnyway using that area with a DE with a top panel makes sense
12:41mpsashi: j`ey: I see, thank you
12:42mpson my m1pro resolution is 3456x2160
12:42ashimps: let me know if I should look up how I enabled it
12:43swaggie has joined #asahi-alt
12:43mpsashi: not needed, I know what is needed in kernel cmdline 'apple_dcp.show_notch=1'
12:43ashimps: looks familiar ;)
12:44mpswill test right now
12:44Dcow has quit [Ping timeout: 480 seconds]
12:45ashiProblem is if you really go fullscreens then the notch might be annoying, but for desktop stuff I like it.
12:47mpsashi: yes, it works out of the box
12:48mpsbut yes, looks like is not good to enable it for my setup
12:49mpsbtw, I noticed again u-boot boot loop with usb-c ssd plugged when booting
12:51ashimps: Which setup do you use, out of curiosity...
12:51mpsashi: awesome wm with status bar on bottom
12:52mpsmaybe I should move status bar to top
12:52ashimps: yes, or get another one for free :)
12:52mpsanother status bar?
12:53swaggie has quit [Ping timeout: 480 seconds]
12:53ashiYes, I mean you now have a "black status bar" on the top :D - you could also fill the area with anything you like left and right to the notch :)
12:54mpsashi: just changed to top, now screen look better
12:54mpsbut I will have to get used to it
12:55ashiscreen estate is valueabe, so could make sense one you get used to it ;)
12:55jannauGlanzmann: configuring the display in m1n1 to a resolution larger than 2560x1600 (real limit is above that but that's the commom display resolution which I remember still works)
12:57jannauGlanzmann: Ry_Darcy complained a few weeks ago and I think you confirmed. no need to patch m1n1 except for testing. it will land in upstream m1n1
12:57mpsashi: mostly irritating thing for me is firefox which also have tabs and menu on top and then I have two bars on top
12:58mpsrest of software I use daily is fine with awesome wm status bar on top
13:18swaggie has joined #asahi-alt
13:26swaggie has quit [Ping timeout: 480 seconds]
13:31Ry_Darcy has joined #asahi-alt
13:33Ry_DarcyI have automatic 4K display resolution now (M1 Mini) without doing any echo display= etc.
13:33Ry_Darcy has quit [Remote host closed the connection]
13:34jamespmorgan has quit [Remote host closed the connection]
13:37jamespmorgan has joined #asahi-alt
14:02swaggie has joined #asahi-alt
14:03ncopashould apple_dcp.show_notch=1 work on mbp 14 too? Does not seem to work on my machine
14:04jannauRy_Darcy: yes, but only after the drm driver has reconfigured the display
14:05jannauncopa: yes, it was only recently merged. you need asahi-6.1-2
14:06ncopamps: I am refactoring the alpine linux-asahi and u-boot-asahi packages. You will have to `apk add u-boot-asahi` as linux-asahi will no longer depend on u-boot-asahi. I have also moved the update script for m1n1 to a trigger to u-boot-asahi, so it gets triggered when either kernel, u-boot or m1n1 is updated
14:06ncopajannau: should be the kernel i am running
14:07ncopaLinux ncopa-mbp14 6.1.0-2-asahi #3-Alpine SMP PREEMPT Fri, 23 Dec 2022 13:53:36 +0000 aarch64 Linux
14:08ncopaBOOT_IMAGE=/vmlinuz-asahi root=UUID=2345d30b-acfb-4dbf-a986-5b35d24a0df1 ro modules=ext4,nvme quiet rootfstype=ext4 apple_dcp.show_notch=1
14:08jannaudmesg | grep notch
14:08ncopanope. only in cmdline
14:08jamespmorgan has quit [Remote host closed the connection]
14:09jannauit needs DRM_APPLE
14:09ncopathat explains
14:09ncopa# CONFIG_DRM_APPLE is not set
14:09ncopawill fix that. thanks!
14:10ncopagrepping for _APPLE_ in the config also reveals: # CONFIG_APPLE_MFI_FASTCHARGE is not set
14:10swaggie has quit [Ping timeout: 480 seconds]
14:11ncopalooks like that is only for iOS devices?
14:11jannauthat is for fast charging apple devices via USB (not USB PD)
14:11wintertpw_rules: why do you exclude setting the xvmc libs path in https://github.com/tpwrules/nixos-m1/blob/f6bd2e82c1b5ed01561d06eb7c494f3af7d7672a/nix/m1-support/mesa/package.nix#L19, over all the other paths; what makes that required?
14:12ncopaok. so if i charge the iphone via usb port
14:13jannauwinter: mostly unrelated: xvmc is dead and will never supported on apple silicon devices
14:15jannaumps: which u-boot version/commit boot loops? Any u-boot messages printed? if not recognizable try recording it with a smartphone camera with slow motion
14:15jamespmorgan has joined #asahi-alt
14:16winterjannau: noted
14:18winterwhy do you exclude setting the xvmc libs path in https://github.com/tpwrules/nixos-m1/blob/f6bd2e82c1b5ed01561d06eb7c494f3af7d7672a/nix/m1-support/mesa/package.nix#L19, over all the other paths; what makes that required? <-- i ask this since, based on the asahi pkgbuild, it doesn't seem that just not setting the directory would be enough to disable
14:18winterxvmc? or maybe the asahi pkgbuild just includes it with other stuff that tpw's package disables
14:22mpsncopa: jannau suggested to not enable APPLE_DRM for distros yet
14:22swaggie has joined #asahi-alt
14:23mpsbecause this I didn't enabled it though I was very tempted
14:23mpsjannau: what you think about this ^
14:24mpsjannau: u-boot boot looping is this tagged release asahi-v2022.10-1
14:25mpsoh, btw I'm also tempted to enable ASAHI_DRM for alpine but didn't
14:26jannauit's too early to enable it in distro's main linux kernel package. same for DRM_ASAHI
14:26mpsjannau: for u-boot message I have to make video or photo
14:27mpsncopa: see what jannau says about distro kernel ^
14:27mpsthough I found both working fine but understand that they still are not 'stable'
14:28ncopaso, this would be for alpine edge (rolling) kernel itself is in testing repo, so i don't think anybody expect anything to be stable at this point
14:29winterDRM is enabled in edge though, iirc, right?
14:29mpsjannau: u-boot loop messages is same as earlier when we had this issue, saying from memory
14:29mpswinter: not on alpine edge
14:29mpswinter: it is on asahi alarm linux-asahi-edge pkg
14:30winteryeah, by "edge" i meant asahi-edge on alarm
14:30wintersorry for the confusion
14:30mpswinter: np
14:31swaggie has quit [Ping timeout: 480 seconds]
14:32mpsncopa: also I think kernel linux-asahi should depend on u-boot-asahi for alpine
14:32mpsand the versioned dependency
14:32mpsmuch safer
14:53jannaumps: what kind of SSD is that? this seems to be a different issue than the device not ready fix for usb-c hubs/card readers
14:54jannauI don't remember what the issue was with your ssd. I thought it was the same issue as the card readers but the fix for that is in asahi-v2022.10-1
14:54mpsjannau: '2174:2000 00 1IF [USB 3.10, 10000 Mbps, 0mA] (Transcend StoreJet Transcend' from lsusb
14:55mpsjannau: I could test later with another usb-c ssd
14:57mpsand with usb-c hub with mmc card reader
15:11jamespmorgan has quit [Remote host closed the connection]
15:15ncopamps: i disagree on the hard dependency of u-boot-asahi for the kernel. At some point i will boot the kernel in qemu, and you don't need u-boot for that
15:19mpsncopa: you will boot linux-asahi kernel in qemu? why?
15:19swaggie has joined #asahi-alt
15:20mpsjannau: I tested u-boot with another usb-c ssd and it works fine, i.e. no boot loop
15:20mpsjannau: also tested with usb-c hub with two mmc card readers, also works fine
15:21mpsjannau: so boot loop happens only with above mentioned transcend usb-c ssd
15:22ncopamps: because i want test boot the kernel to make sure its not completely broken before pushing it on updates
15:22ncopait lets me test that the trigger scripts works as they should, that installer works as it should, etc
15:23mpsncopa: but testing linux-asahi in qemu doesn't guarantee it is ok
15:23ncopaof course not, but it lets me conveniently test everything around it in a virtual environment
15:24mpsncopa: ok, do what you think is best
15:24ncopajust like i test the linux-lts kernel in qemu, not only the linux-virt kernel
15:24mpsI usually test kernels with external usb ssd or stick before pushing upgrades
15:25mpsyes, this makes sense for linux-lts but not sure about linux-asahi
15:28mpsncopa: to be clear, I trust you that you will do proper things and I don't argue with your opinions, just expressing my my thinking
15:28swaggie has quit [Ping timeout: 480 seconds]
15:32mpsbtw, Greg Kroah-Hartman just told me that we don't need to enable CMA for arm64 kernels in general, and only for specific SoCs cases
15:33mpsso I will disable it for alpine kernel
15:36jannauCMA is not needed for asahi. we have IOMMUpple sisahi. I think it's still enabled in out configODODODODODODODthe asahi disto config
15:37jannauCMA is not needed for asahi. we have IOMMUs. I think it's still enabled in the asahi distro config
15:37jannauthat was a mosh fail
15:39cylm_ has joined #asahi-alt
15:41mpsand I copied it from one of your first configs
15:52swaggie has joined #asahi-alt
16:00swaggie has quit [Ping timeout: 480 seconds]
16:03Dcow has joined #asahi-alt
16:08swaggie has joined #asahi-alt
16:11Dcow has quit [Ping timeout: 480 seconds]
16:16swaggie has quit [Ping timeout: 480 seconds]
16:55swaggie has joined #asahi-alt
17:03swaggie has quit [Ping timeout: 480 seconds]
17:14jamespmorgan has joined #asahi-alt
17:35Dcow has joined #asahi-alt
17:44Dcow has quit [Ping timeout: 480 seconds]
18:10opticron has quit [Ping timeout: 480 seconds]
18:18opticron has joined #asahi-alt
18:21jamespmorgan has quit [Remote host closed the connection]
19:19Dcow has joined #asahi-alt
19:24ashi has quit [Quit: Leaving]
19:42Dcow has quit [Remote host closed the connection]
19:42Dcow has joined #asahi-alt
19:51Dcow has quit [Remote host closed the connection]
19:56Dcow has joined #asahi-alt
20:26jamespmorgan has joined #asahi-alt
20:43Dcow has quit [Ping timeout: 480 seconds]
20:50Dcow has joined #asahi-alt
21:01Dcow has quit [Ping timeout: 480 seconds]
21:11zzywysm_ has joined #asahi-alt
21:13zzywysm_ has quit []
21:16Dcow has joined #asahi-alt
21:16zzywysm has quit [Ping timeout: 480 seconds]
21:20zzywysm has joined #asahi-alt
21:25swaggie has joined #asahi-alt
21:27Dcow has quit [Ping timeout: 480 seconds]
22:08Dcow has joined #asahi-alt
22:11winterhow would I confirm that my GPU drivers are working? my terminal emulator (wezterm on Wayland) feels really sluggish, and i'm not sure why
22:22mpswinter: dmesg and grep for gpu
22:22mpsalso you will need gallium asahi driver
22:23winteri have that
22:23Dcow has quit [Ping timeout: 480 seconds]
22:24winteryup, i see GPU log entries
22:24winterno clue why it's so sluggish then
22:24mpsmy test is 'mpv -vo=gpu $videofilename'
22:28jacksonchen666 has quit [Ping timeout: 480 seconds]
22:29jannaueglinfo | grep 'driver name'<
22:29winter> Failed initializing any suitable GPU context!
22:29winterhmm, wonder what's up here
22:29jacksonchen666 has joined #asahi-alt
22:29jannau`eglinfo | grep 'driver name'` should report apple and asahi
22:29swaggie has quit [Ping timeout: 480 seconds]
22:32winteryup, i see both
22:36winternot sure what would be wrong then, hm.
22:40winterlooks like chromium also fails to init the gpu
22:41winterbut eglinfo output looks sane...
22:44jannauI wouldn't start looking at chromium but with the mesa test programs and if those work continue with glmark2
22:44winter(from mesa-demos?)
22:47winterglxgears for example works fine
22:49wintertrying glmark2(-wayland) now
22:53wintergot a score of 287 on an M1 MBA
22:54winterif that's expected for cpu (or gpu) rendering, not sure
23:12jamespmorgan has quit [Remote host closed the connection]
23:19swaggie has joined #asahi-alt
23:22jannauthat sounds like CPU rendering, expected score is 1-2k. does the score gets worse if you increase the resolution?
23:31jamespmorgan has joined #asahi-alt
23:58chadmed has joined #asahi-alt
…