2022-12-08
00:00Chai-T-Rex has quit [Remote host closed the connection]
00:00Chai-T-Rex has joined #asahi
00:05rayanamukami3 has quit [Read error: Connection reset by peer]
00:06rayanamukami3 has joined #asahi
00:09dorkbutt has joined #asahi
00:36Vibrose has quit [Remote host closed the connection]
00:46nate8_ has joined #asahi
00:53nate8 has quit [Ping timeout: 480 seconds]
00:53Kaz has joined #asahi
00:56Kaz has quit []
00:59thesoftmaochine has joined #asahi
01:00thesoftmaochine has quit []
01:02abby has quit [Ping timeout: 480 seconds]
01:13abby has joined #asahi
01:15abby has quit [Read error: Connection reset by peer]
01:15abby has joined #asahi
01:24jacksonchen666 has quit [Remote host closed the connection]
01:29jacksonchen666 has joined #asahi
01:39psykose has quit [Remote host closed the connection]
01:39psykose has joined #asahi
01:48dorkbutt has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
01:49dorkbutt has joined #asahi
02:01user982492 has quit [Quit: Textual IRC Client: www.textualapp.com]
02:11mental has joined #asahi
02:14zalyx has quit [Quit: later alligator]
02:15zalyx has joined #asahi
02:16mental is now known as lugpocalypse
02:16dorkbutt has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
02:17dorkbutt has joined #asahi
02:18lugpocalypse has quit [Quit: Konversation terminated!]
02:27lugpocalypse has joined #asahi
02:28lugpocalypseHey there, just installed asahi. How do I ensure I'm tracking the latest available stuff like gpu drivers/kernels/etc?
02:29lugpocalypseI kind of expected that, but thanks for confirming it.
02:29lugpocalypseThanks
02:32lugpocalypse has quit [Quit: Konversation terminated!]
02:34beeblebrox has quit [Remote host closed the connection]
02:45pjakobsson has joined #asahi
02:49pjakobsson_ has quit [Ping timeout: 480 seconds]
03:23dorkbutt has quit [Read error: Connection reset by peer]
03:49axboemarcan: dumb question, since that post is specifically for that distro - what else do I need outside of the kernel bits? if I missed another post, feel free to point me at it...
03:54axboehmm might be tough to retrofit mesa without recompiling the world here, I think I'll give it a spin on the m1 pro with an asahi install
03:54chadmedwhat distro are you using? its possible meson has set up mesa with an incorrect libdir and dri-drivers-path
03:54chadmedi had to manually set them to /usr/lib64 and /usr/lib64/dri respectively with gentoo (though the ebuild now takes care of that automatically for users)
03:55tpw_rulesdumb mesa question: does the version linked into apps need to be the same as the version driving the GPU?
03:55chadmedthe default libdir for a straight meson setup with no options is /usr/local/lib64 so if thats wrong for debian you need to make a new build dir with the correct meson options and reinstall the mesa branch
03:56tpw_rulesthe blog post mentions there might be "UAPI" breakage but i'm not sure where exactly that split is
03:57chadmedthe UAPI split was before public release so unless you were testing some old picked branch of lina's you shouldnt have uapi issues with the release kernel and asahi/mesa
03:58chadmedyeah, they will be kept in sync for public releases now so even if there are changes required to make it upstreamable you shouldnt notice them
04:01jamespmorgan has joined #asahi
04:02chadmedi had half a mind to set up distcc back to my build server to "save battery" but the 10 core m1 pro compiles almost everything faster than my overclocked server while using less energy so whats the point
04:02axboeI've got faster build boxes, but you need a big build to warrant moving off the laptop now
04:04axboeaxboe@m1max ~> glxinfo|grep Device 0.000s Device: llvmpipe (LLVM 14.0.6, 128 bits) (0xffffffff)
04:06jamespmo_ has quit [Ping timeout: 480 seconds]
04:08unicordion has joined #asahi
04:27marcan< tpw_rules> dumb mesa question: does the version linked into apps need to be the same as the version driving the GPU? <- mesa isn't linked into apps
04:27marcanit's an OpenGL implementation and OpenGL has a very well defined ABI, that's why you can replace it with nvidia's blob
04:29tpw_ruleshttps://packages.debian.org/sid/libgbm-dev this is why it's claimed to be a dependency of several packages in nix. but yeah i looked and mostly it's used through opengl's abi
04:30marcanand if you're running Xorg, this config: https://github.com/AsahiLinux/PKGBUILDs/blob/main/asahi-configs/30-modeset.conf
04:40marvin24 has joined #asahi
04:44marvin24_ has quit [Ping timeout: 480 seconds]
04:46unicordion has quit [Remote host closed the connection]
04:58unicordion has joined #asahi
05:02marcanreally just dcp, it's just that it works by accident without it if you don't have the gpu driver
05:09unicordion has quit [Quit: unicordion]
05:18osaka1990 has quit [Read error: Connection reset by peer]
06:32WindowPain_ has joined #asahi
06:34WindowPain has quit [Ping timeout: 480 seconds]
07:25tinstew has joined #asahi
07:44joske has joined #asahi
07:52SSJ_GZ has joined #asahi
07:53mpsaxboe: yesterday Glanzman wrote all needed things and steps for getting gpu on debian, on #asahi-alt channel, maybe reading backlog there could help to sort out problem
08:02kettenisbut I guess the code that is supposed to select a driver still is a mess for non-PCI graphics
08:02kh has joined #asahi
08:05kh has quit [Remote host closed the connection]
08:09tinstew has quit [Ping timeout: 480 seconds]
08:13LinuxM2 has joined #asahi
08:31SSJ_GZ has quit [Ping timeout: 480 seconds]
08:31SSJ_GZ has joined #asahi
08:47marcankettenis: yeah, don't look at me... as far as I can tell this is the "intended" way to do it.
08:47marcanit really should just autodetect it by looking for devices with actual outputs first (it actually already does that for secondaries), but I dunno
08:48marcanI'm slowly resolving to stop taking bug reports related to Xorg environments because a lot of it is upstream issues and nobody is working on it
08:49marcanI'll probably pull off some hack to force switch everyone on Xorg by default to Wayland (as far as SDDM settings) when we actually push the GPU driver to production or something. they can change it back if they want, but it's just never going to work properly in all aspects.
08:50SSJ_GZ has quit [Ping timeout: 480 seconds]
08:52as400chadmed: when using "ondemand" governor I was able to go to 5.31W on my mbp 14. Yes, I know it's not optimal. Still looks like using this governor it's using less power.
08:54marcanondemand is just slower and therefore less likely to put the CPU into higher power states
08:54pip[m]1 has joined #asahi
08:54pip[m]1 has left #asahi [#asahi]
08:55marcanchadmed: I've seen my MBP14 get into a weird state when I boot it up with the lid closed, which I think causes SDDM to suspend
08:55marcanI'm pretty sure there's something that ends up in an infinite loop or IRQ storm or something
08:57as400marcan: you might be right. I'm doing it out curiosity. And one thing I noticed is that ondemand puts CPUs in lower states much more often than schedutil.
08:57joske has quit [Quit: Leaving]
08:58marcanyes, because schedutil actually takes into account short latencies and is intended for modern SoCs
08:59marcanwhile ondemand dates back to the beginnings of cpufreq on Pentium III systems and is designed for CPUs which have horrible switching latencies
09:00marcanon schedutil, just doing "cat" on the relevant sysfs files is likely to put the CPU running "cat" into the max perf state or close
09:00marcanschedutil is likely to actually save power on modern systems (moreso when we implement deep sleep), google "race-to-idle"
09:01marcanand it's also a requirement to have good desktop responsiveness, otherwise you end up stuttering every time something starts happening until ondemand catches up
09:03guillaume_g has joined #asahi
09:08mpsmarcan: I'm strongly against idea to force users to wayland. distro users doesn't like to be forced to anything and of you make these changes users will start to fill bug reports on distros
09:10marcanour packages and package update scripts cater to the average user. the average user wants to be on wayland after the GPU driver lands.
09:11mpsmarcan: I don't ask to fix bugs or add features, just ask to not make intentionally hard to use it
09:11marcanasahi-desktop-meta means "we will make this as painless as possible assuming you're happy with our intended desktop experience"
09:13marcanI should probably remind everyone: "asahi-meta" means "I want my machine to work". "asahi-desktop-meta" means "I trust marcan & co to make my desktop experience be good by default"
09:13marcanyou are free to uninstall asahi-desktop-meta, but then don't complain if updates mean you have to go tweak settings to make things work the way you want again, or to improve things, because that will happen sometimes
09:14mpswaldi: yes, and I switch between xorg and sway from time to time, so for me personally it is not big issue, but I'm having distro users in my 'advocate' mind
09:14arwayland is still not ready, as libinput maintainers refuse to implement basic functionality that was available for touchpads and trackpoints (ok, that's not a concern on macs…), and wayland compositors still have annoying bugs with, for example, menu "subwindow" placement
09:14marcanar: wayland is at the point where its bugs and annoyances are about on par with the xorg bug and annoyances
09:15marcanand once the GPU driver lands there are significant problems with xorg which will not go away any time soon (e.g. no vsync)
09:16mpsmarcan: ah, ok, now I understand, you will not intentionally criple xorg usage. sorry for noise
09:16marcanand that is unlikely to ever be supported because it doesn't look like the hardware does at all
09:16marcanmps: dude I'm literally just talking of changing the default to wayland, I already said that, I'm not sure what you understood
09:17marcanI even shipped an xorg conf with the alpha GPU driver stuff to make xorg actually work (it doesn't work by default because its device selection algorithm is broken by default, see what kettenis said)
09:18marcanby "force switch" I mean I will edit their SDDM config to switch to wayland, because all existing users on xorg should be switched to wayland, because there is no way to determine intent ("xorg by default" vs "xorg on purpose") and the majority will be of the former category
09:19marcanthe only way it will get reset again is if you start playing really weird games with pacman package versions, it won't happen by accident
09:25marcanFWIW, when Asahi first shipped the alpha I chose Xorg because I think it was faster than Wayland without a GPU driver, and because KWin/Xwayland fractional scaling still wasn't working which made Firefox end up blurry, and I didn't have time to chase down these things since the actual "desktop experience" part of everything was quite rushed
09:25marcanthose concerns no longer apply; the Xwayland on KWin stuff got fixed and Wayland is a significantly smoother experience than Xorg with drivers
09:25SSJ_GZ has joined #asahi
09:26marcan*personally* I still have a partial Xorg blocker (inputleap/barrierd support) but that's me, and it looks like progress is being made there plus there's at least a Wayland version of the client anyway
09:26kujegerit'll be interesting when the fractional scaling stuff for wayland lands in released versions of the various compositors, right now non-integer scaling is still kind of blurry in e.g. sway
09:27marcankujeger: it works well in kwin except for some glitching in weird cases. I hope the bikeshedding about how to do the rounding "perfectly" I hear happened trickles down into that and fixes it
09:27marcanthough FWIW: as far as I know non-KDE desktops mostly implement fractional scaling via output scaling and... guess what, that's how macOS does it too.
09:27marcantrue native fractional scaling is hard and Wayland will have a leg up on macOS there if it all gets implemented nicely and works
09:27kujegeriirc the wayland protocol got merged a few days ago, and code using it already exists in unreleased form
09:27marcan(because the disadvantage of output scaling is you burn more GPU power by pushing more pixels)
09:29kujegerah, here's the PR for the protocol for anyone interested: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/143
09:29marcanbut fractional scaling creates piles of corner cases for interactions, and as far as I know that's why that protocol took so long to work out
09:30marcanyeah, I'm looking forward to the state of things mid-2023 or so, looks like ~everything is coming together nicely on the desktop side
09:31_jannau_I would expect Xorg with tearfree to be less broken with dcp. It should receive fake vblank irq on framebuffer swaps
09:31marcan_jannau_: there is no vblank IRQ support so there is no vblank ioctl support so clients just freewheel even when they think they are vsynced
09:31MajorBiscuit has joined #asahi
09:32marcanTearFree doesn't change the way xorg implements client vsync (which is apparently based on explicit vblank queries which don't work)
09:32kujegermarcan: with pipewire, the current/soon-ish state of wayland etc it sure looks like 2023 will be a good time for a modern linux desktop, year of the linux desktop jokes aside
09:32marcanthey'd have to implement the vblank emulation in xorg proper for this to work somewhat better
09:32kujegerI've been using wayland/xwayland exclusively for years and it's been just steadily getting better and better
09:32ChaosPrincesshow does stuff to know when to flip buffers when there is no vblank interrupt?
09:33ChaosPrincesswhat about stuff like VRR and such?
09:33mpsI built xorg with tearfree patch and enabling it 'Option "TearFree" "on"' then xorg even doesn't start
09:33marcanpresumably you just queue a flip and the hardware issues it at the earliest possible time, quantized to whatever it can do or whatever
09:34marcan(because you cannot guarantee latencies any more so you cannot guarantee the actual flip happens during vblank)
09:34marcanso every display controller implementation switched to hardware double-buffering of the registers with automatic flips
09:35marcanand DCP is strictly built with this model in mind, hence it works well for macOS and Wayland, not so much Xorg
09:36_jannau_she removed the drm_vblank initilisation, dcp still emits vblank events after page swap. I'm not sure if those are still registered as vblank irqs
09:36marcan_jannau_: that function is misnamed, it's not a vblank event, what it really is is a swap complete event
09:37marcanso without TearFree you get tearing in glxgears at a bajillion FPS. with TearFree you get a smooth glxgears, still at a bajillion FPS behind the scenes
09:38marcanbecause Xorg apparently doesn't tie compositor page flips to the actual app swap interval, it instead relies on vblank IRQs to throttle clients and those don't work
09:39marcansame reason some KDE animations are way too fast on xorg (as they've always been on Asahi, since simpledrmfb also doesn't have vblank IRQs of course)
09:40marcanI think in principle you could emulate the vblank stuff by queuing dummy page flips and waiting on those, but it sounds like a recipe for corner cases and pain and higher power usage
09:42marcanit tries to use a newer API and fall back to an older one, but the logic for that is busted so it always uses the newer one
09:42_jannau_yes, I thought about that but I fear that it leads to a ton of bugs for clients doing swaps
09:44_jannau_not sure if you have seen https://lore.kernel.org/dri-devel/CAPM=9twc_TBtG_654Hm4SV_G1Ar+PiCuZGg1fV-Zooga+4S0GQ@mail.gmail.com/
09:46_jannau_the modeset driver's atomic modeset implementation was/is apparently that broken that it was forcefully disabled on kernel side
09:49arso, what one should say about bugs in wayland compositors that have been reported 4+ years ago, that are prevalent across gnome, plasma, and sway? ;)
09:59leitao has joined #asahi
10:02leitao has quit []
10:03kh has joined #asahi
10:03khMy task bar becomes huge on asahi-linux-edge on wayland KDE, does anyone know how to fix this? https://ibb.co/C7Zmy2J
10:14LinuxM1 has joined #asahi
10:19leitao has joined #asahi
10:21kh has quit [Ping timeout: 480 seconds]
10:21LinuxM1 has quit [Quit: Leaving]
10:25LinuxM2 has quit [Quit: Leaving]
10:25tinstew has joined #asahi
10:34chadmedas400: thats a decent temp fix i guess but wont be suitable once we have EAS worked out properly since it ignores that, and will end up using more power
10:35chadmedmarcan: im actually not using sddm at the moment but the behaviour is similar. the machine ends up hotter and pulling more juice in suspend than just locking the session and turning the screen off. i can resume successfully at will though
10:36abby has quit [Remote host closed the connection]
10:38abby has joined #asahi
10:39chadmedjoske: im preparing a new branch with p ovik's suggestions so just ignore that PR for now
10:45kh has joined #asahi
11:01abby has quit [Remote host closed the connection]
11:02abby has joined #asahi
11:15tinstew has quit [Read error: Connection reset by peer]
11:19kh has quit [Remote host closed the connection]
11:26veloek has quit [Ping timeout: 480 seconds]
11:35gladiac has joined #asahi
11:35leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
11:41joske has joined #asahi
11:42joskechadmed: yes, I tried to manually apply the changes to latest asahi branch, but it didn't work. I'll wait until you have a new version
11:43chadmedill sort it all out tomorrow (GMT+10). the PR is redundant, you can just pick the commits from the branch once i push it
11:44as400chadmed: don't know about schedutil but with ondemand when screen is off it takes 3.19W. Have to try with schedutil. For the future schedutil is probably the only way.
11:45tinstew has joined #asahi
11:47as400About the battery - is it possible that charge controller in m1 macs has two "modes" ? Like "high current" and "high voltage" ? That was the case with my Lenovo Ideapad. And when I was using the default, which was "high voltage" the battery health was deteriorating very fast.
11:52piroko9 has joined #asahi
11:55ChaosPrincesstrying out the new gpu driver: why is the cursor and the task bar so huge?
11:56piroko9good morning. does this room have the matrix.org bridge banned? I tried to join this room yesterday from my matrix account (nick piroko) but was met with a ban error
11:56joske has quit [Quit: Leaving]
11:58piroko9anyway I came here to say yesterday, I've been dabbling with asahi linux on my various macs since the day it was announced, and I was blown away by the latest state of the project
11:59ChaosPrincessok, i found how to shrink the cursor, but the task bar is still big
11:59ChaosPrincessand yes, i have scaling set to 150
11:59piroko9this team is incredible and I just wanted to say thank you for your insanely awesome work
12:05leitao has joined #asahi
12:09leitao has quit []
12:10tinstew has quit [Remote host closed the connection]
12:15marcanChaosPrincess: I saw the cursor thing on some machines. not sure what causes it, but it smells like a KDE bug.
12:16ChaosPrincessits even weirder
12:16leitao has joined #asahi
12:16kh has joined #asahi
12:16ChaosPrincessi set cursor to 24 px, it applied and was that way for a bit, but now its back to being huge except when i hover over the top bar of the window, and there it goes back to small
12:16ChaosPrincesssmells very much like userspace bug
12:17ChaosPrincesslogging out and back in did not help
12:17ChaosPrincessin fact, i had to do it for the settings to even apply
12:22marcantl;dr coordinates are different on x11 and wayland, so anything saved shows up differently on the other or something like that
12:23marcanit seems the default calendar size is the minimum, so xorg never shows up tiny, but then saves its coordinates and the next time you're on wayland it's huge
12:27khBtw regarding schedutil vs ondemand power usage schedutil boosts the cpu frequency to max whenever there's an RT task running, so maybe that's why power usage is so high https://github.com/torvalds/linux/blob/master/kernel/sched/core.c#L7228
12:29gladiac has quit [Quit: k thx bye]
12:36kh has quit [Ping timeout: 480 seconds]
12:39leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
12:58beeblebrox has joined #asahi
12:59beeblebrox has quit [Remote host closed the connection]
13:01piroko9 has quit [Remote host closed the connection]
13:06marcankh: That is expected behavior, yes (because RT code runtime is unpredictable if you're switching frequencies)
13:06marcanthat only happens when an RT task is runnable, which hopefully isn't very often unless you're running real time audio apps
13:11UnicornsOnLSD has joined #asahi
13:13UnicornsOnLSD is now known as jmshrv
13:13jmshrvHi, I've been unable to install Asahi on my laptop - the installer fails to boot into the new recovery and bootloops even though I'm 99% sure I'm following the instructions at the end. Here's a video showing the process: https://youtu.be/q9NPPEX3Z8Q
13:14jmshrvThis MacBook is a bit weird since it had to be repaired and jumped straight from 12.0 to 12.6 as the logic board was replaced, but I doubt that's the issue. I was able to install Asahi before the repair, but that was basically a different laptop based on how much was replaced lol
13:15jmshrv_ has joined #asahi
13:22jmshrv has quit [Ping timeout: 480 seconds]
13:22jmshrv_ is now known as jmshrv
13:24veloek has joined #asahi
13:25aaron465 has joined #asahi
13:26gladiac has joined #asahi
13:31jmshrvMy gut instinct was that it wasn't happy with 12.3 because it never ran it or something, but that would be pretty stupid
13:31aaron465hihi! I've been out of the channel for a while but excited about Asahi again thanks to the GPU driver (big love for that). I am running Gnome (Wayland) and trying to set fractional scaling. In general it is working but the gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']" is not persisting reboot. I am trying to figure out what is different between this and my Arch desktop where I do the same thing with no problems...
13:31aaron465Could that be related to Asahi or should I continue doing general Gnome related searching?
13:32marcanjmshrv: I can try adding 12.3.1 to the installer, though that will need m1n1 changes before you can use it with the GPU/DCP
13:34aaron465marcan: thanks. Second question is I keep getting WiFi disconnects; are there any differences there (asahi-edge kernel) vs the regular asahi kernel (it seems like a new problem)?
13:35jmshrvCould the 12.4 firmware used for M2 work here, or would that be way more effort than adding 12.3.1?
13:37marcanyou can also try 12.4 and 13.0 in expert mode; the former should work but is unsupported (expect no GPU, might be able to test whether it works, also it's supposed to be an M2 only build) and 13.0 is completely untested but you can try it if nothing else works just to see
13:38marcanif 12.3.1 works and gets you to a desktop let me know and I'll make the m1n1 changes to make the DCP/GPU bleeding edge drivers enabled
13:40jacksonchen666 has quit [Ping timeout: 480 seconds]
13:44jacksonchen666 has joined #asahi
13:44ptudor_ has joined #asahi
13:45cylm has joined #asahi
13:47ptudor has quit [Ping timeout: 480 seconds]
13:47dordoka has joined #asahi
13:47dordoka has quit []
13:50Chai-T-Rex has quit [Remote host closed the connection]
13:53Chai-T-Rex has joined #asahi
14:00minecrell8 has quit []
14:00minecrell has joined #asahi
14:01marcanjmshrv: https://github.com/AsahiLinux/asahi-installer/raw/main/data/installer_data.json should be showing 12.3.1 by now
14:08marcanI checked and the DCP/AGX firmwares are identical save for build IDs, so if it works for you I'll push the m1n1 update to map the new firmware version and you should be good to go
14:09jmshrv has quit [Remote host closed the connection]
14:11piroko9 has joined #asahi
14:12piroko9is it expected that the currently implemented sleep mode on the edge kernel would make my laptop warm if kept in my bag? or is it more likely that my computer woke itself up
14:13aaron465same for me actually on sleep. I didn't look into that yet though so didn't mention it. Pressing suspend button seems to work, lid suspend seems like a no (and/or it wakes back up after some time)
14:14bcrumb has joined #asahi
14:15marcanand just generally debug suspend, I barely had a chance to look into it beyond the stuff that completely broke it
14:16jmshrv has joined #asahi
14:17jmshrvmarcan: That worked, was able to boot into a TTY. I'm using the minimal install, should be able to set up KDE later today
14:17jmshrv has quit []
14:20marcanI'm going to leave this as expert-only for now since it's such a weird edge case, so we don't proliferate 12.3.1 just in case
14:20marcanbut I'll properly tag a build and push it to the production installer so we can tell people who run into it what to do
14:22ChaosPrincessmacbook pro opus? :P
14:23jannaufortunately I decided to ignore the patch level version in the dcp fw version check. otherwise it would reject 12.3.1 as firmware version even though it's reported as compatible to 12.3.0
14:24marcanthe idea is we check compat only unless a new version adds optional but backwards compatible features, in which case we use version to check for that
14:26marcanand for the latter, the check ideally needs to be done with an actual vercmp style greater-than check, not a hard match
14:27marcancompat can be checked for exactly since we define the "blessed" versions and those are all that should go in compat
14:28marcanfor DCP right now, I think it should just drop the unknown version check for the version field
14:30jannauyes, I came to the same conclusion. missing information should have been only valid for a transitional period to allow everyone to update m1n1
14:30DarkShadow44 has quit [Quit: ZNC - https://znc.in]
14:30DarkShadow44 has joined #asahi
14:40bcrumb has quit [Quit: WeeChat 3.7.1]
14:47Guest1279 has quit [Quit: G-line: User has been permanently banned from this network.]
14:47vx has joined #asahi
14:48vx is now known as Guest1361
14:55gladiac has quit [Quit: k thx bye]
14:57delsol has joined #asahi
15:02bcrumb has joined #asahi
15:02piroko has joined #asahi
15:03bcrumb has quit []
15:05piroko has quit []
15:08piroko has joined #asahi
15:09leitao has joined #asahi
15:11bcrumb has joined #asahi
15:12bcrumb has quit []
15:17bcrumb has joined #asahi
15:19bcrumbthough for some reason my kde stuff looks kinda blurry, not sure what part of my configuration could be affecting my UI, I set up wayland before it was cool and had it work with 150 DPI, i turned that off though before updating
15:21delsol has quit [Quit: Leaving...]
15:21bcrumb has quit []
15:25mkurz has joined #asahi
15:25leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
15:26mkurz has quit []
15:26mkurz has joined #asahi
15:26leitao has joined #asahi
15:28mkurz has quit [Remote host closed the connection]
15:28mkurz has joined #asahi
15:31piroko9 has quit [Quit: nyaa~]
15:32jamespmo_ has joined #asahi
15:39jamespmorgan has quit [Ping timeout: 480 seconds]
15:50bcrumb has joined #asahi
15:51bcrumbmarcan: I've tried that, but then the fonts start blurring at anything beyond 100%, which is tiny, are the fonts high dpi for you?
15:52bcrumbif i know this is not expected behaviour i can go fix it, but otherwise everything works wonderfully even with forced dpi
15:59marcanunless you're talking about stuff looking *slightly* softer with non-integer scaling: https://bugs.kde.org/show_bug.cgi?id=446674
15:59marcanbut it's barely noticeable, and macOS does the same thing. KDE at 150% looks pretty similar to macOS tbh, as far as font rendering.
16:00bcrumbok, let me see if i haven't reset post playing around with scaling by accident, since i saw that update at runtime
16:00bcrumb has quit [Quit: WeeChat 3.7.1]
16:02yuyichao_ has joined #asahi
16:03bcrumb has joined #asahi
16:03yuyichao has quit [Read error: Connection reset by peer]
16:05nate8_ has left #asahi [Leaving]
16:05marcanforcing DPI is likely to cause other issues with apps and is not really supported on wayland
16:06LinuxM1 has joined #asahi
16:09bcrumbchanges to the initrd, no, although the same stuff used in the initrd has formerly also allowed the usb device ( mouse with usb antenna ) to work
16:11svenrighth, I just double check with everyone who messes with the boot process because there have multiple people who messed up so far
16:12rvalue has quit [Ping timeout: 480 seconds]
16:21WindowPain_ is now known as WindowPain
16:21bcrumb has quit [Quit: WeeChat 3.7.1]
16:23leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
16:23bcrumb has joined #asahi
16:24bcrumbsven: https://privatebin.net/?049ce9a9209d76a8#AuUjTe5EAfMtypWGEquGtXJwFoi6WqLsR8RsKNoT2ND1
16:24bcrumb has quit []
16:27leitao has joined #asahi
16:29bcrumb has joined #asahi
16:29jluthra has quit [Remote host closed the connection]
16:30rvalue has joined #asahi
16:30jluthra has joined #asahi
16:31leitao has quit []
16:31bcrumb has quit []
16:34leitao has joined #asahi
16:36LinuxM1 has quit [Quit: Leaving]
16:36Guest1361 has quit [Ping timeout: 480 seconds]
16:38rvalue has quit [Ping timeout: 480 seconds]
16:42LinuxM1 has joined #asahi
16:56guillaume_g has quit []
17:09systwi has quit [Ping timeout: 480 seconds]
17:09systwi has joined #asahi
17:20WindowPain has quit [Quit: ZNC 1.8.2 - https://znc.in]
17:21WindowPain has joined #asahi
17:25MajorBiscuit has quit [Ping timeout: 480 seconds]
17:28WindowPain has quit [Quit: ZNC 1.8.2 - https://znc.in]
17:28WindowPain has joined #asahi
17:29aaron465marcan: turns out, my WiFi issues are down to a dodgy cable connecting to one of my APs :D
17:29leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
17:31leitao has joined #asahi
17:31mkurz has quit [Read error: Connection reset by peer]
17:39leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
17:44LinuxM1 has quit [Quit: Leaving]
17:46bcrumb has joined #asahi
17:46bcrumb has quit []
17:48cylm has quit [Quit: WeeChat 3.6]
17:48mkurz has joined #asahi
17:51rvalue has joined #asahi
17:54WindowPain has quit [Quit: ZNC 1.8.2 - https://znc.in]
17:54WindowPain has joined #asahi
17:58cylm has joined #asahi
18:00das_j has quit [Remote host closed the connection]
18:02das_j has joined #asahi
18:03svenbcrumb: nothing truly suspicious there, can you enable trace events for tps6598x and boot again?
18:03WindowPain_ has joined #asahi
18:06WindowPain_ has left #asahi [#asahi]
18:07svenbut especially for debugging boot issues it’s helpful to have the trace events ordered with respect to messages in dmesg
18:07WindowPain has quit [Ping timeout: 480 seconds]
18:11das_j has quit [Remote host closed the connection]
18:11WindowPain has joined #asahi
18:12jannauhttps://politreco.com/2022/03/tracepoints-and-kernel-modules/ suggest disabling probing for the module, load the module, enable the tracepoints and then reenabling probing
18:13svenwouldn’t surprise me if there’s another race with how it sets up irqs and registers the initial plug
18:15bcrumb has joined #asahi
18:19bcrumbif i know the device name, is there some way i can trace earliest lookups / interactions?
18:19WindowPain_ has joined #asahi
18:20bcrumbi suppose that tps thing is that since it interacts, but i am willing to also go inspect this by myself deeply
18:20WindowPain has quit [Read error: Connection reset by peer]
18:20WindowPain_ is now known as WindowPain
18:21das_j has joined #asahi
18:22svenugh…. This might be tipd probing before dwc3 and atcphy and firing off the plug event into nowhere
18:23Glanzmann has joined #asahi
18:23Glanzmannaxboe: https://thomas.glanzmann.de/asahi/2022-12-07/ but mps already pointed you to it. Thank you mps. ;-)
18:26Glanzmannaxboe: If you want to build yourself. I put a gpu.sh and mesa.sh script in the m1-debian git repository. Btw. if you figure out more kernel configs that work with the new kernel. let me know. Currently the only config that works for me is mps config (which is also in the m1 debian repository). When I try the reference config the kernel does not boot. When I try my old config, it also hangs with some late
18:27LinuxM1 has joined #asahi
18:28zzywysmGlanzmann: is there a particular type of kernel config for apple silicon you want me to make?
18:28LinuxM1same for me, gpu acceleration on chromium won't start it, it's a problem with shared libraries
18:29Glanzmannzzywysm: Previously I used the debian testing arm64 config and enabled the asahi options. That config nolonger boots with the gpu stuff.
18:30zzywysmGlanzmann: do you have any preferences? do you value a large amount of hardware compatibility, or do you like small more secure kernels? are you cool with kernel modules?
18:32Glanzmannzzywysm: I only user usb devices like usb audio card, hdmi grabbers, cameras, mice, keyboards.
18:33tinstew has joined #asahi
18:34Glanzmannzzywysm: This is the config I try to get running on Debian: https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/blob_plain/HEAD:/config-16k.txt
18:34LinuxM1Is it normal that the keyboard backlight does not work on a MacBook Pro M1 Max? I use asahi-edge kernels
18:35mpsaxboe: but, aarch64 is first class arch on alpine, it is not less important to x86 as on some/most distros
18:36tinstewanyone got me something to mess with i have nothing to do and thought maby u guys could give me something to mess with on my m1 mini
18:37LinuxM1I simply can't find a menu where to activate it, on macbook air M2 instead the retruillumination works
18:37ethernet has joined #asahi
18:40bcrumb has quit [Quit: WeeChat 3.7.1]
18:41Glanzmannaxboe: Can you please send me your kernel config for the gpu kernel? I would like to try it.
18:42axboeonly difference from my previous is a) using LLVM=1 and enabling rust, and b) enabling the gpu driver
18:44mpsGlanzmann: with kernel config I posted to you everything works for me on m1 mpb and m1pro macbook
18:46Glanzmannmps: For me, too. I'm only missing automounter, but I could of course enable that. https://pbot.rmdir.de/fUkju8JQ8evyWvr2by0LrA
18:47GlanzmannLinuxM1: Maybe you just set it manuall. As root, run: echo 100 > /sys/devices/platform/led-controller/leds/kbd_backlight/brightness; # 0 means off 255 is the maximum value.
18:48LinuxM2 has joined #asahi
18:50LinuxM1Glanzmann, so everytime i turn on i have to run that command? Isn't there a way to leave the backlight on?
18:59LinuxM2 has quit [Quit: Leaving]
19:00leitao has joined #asahi
19:03LinuxM1very strange thing, I restarted the MBP m1 max with the backlight change given by the command suggested to me by glanzman, and now it remains stuck in the SSDM in the window where I should login, the touchpad does not work and the keyboard does the same which won't let me type
19:03mkurz has quit [Read error: Connection reset by peer]
19:07ariel has joined #asahi
19:07ariel is now known as Guest1386
19:08Guest1386 is now known as facekapow
19:09facekapow has quit []
19:33bcrumb has joined #asahi
19:34bcrumbLinuxM1: try mashing fn+control+option+fn1 (or 2 or 3...) to get a login prompt in shell and change back the stuff you modified
19:34bcrumb has quit []
19:35bcrumb has joined #asahi
19:35bcrumb has quit []
19:35mkurz has joined #asahi
19:45erik has joined #asahi
19:46bcrumb has joined #asahi
19:46bcrumb has quit []
20:01erik has left #asahi [#asahi]
20:01Glanzmann has quit [Quit: l8er]
20:02aaron465 has quit [Quit: ZNC 1.8.2 - https://znc.in]
20:02aaron465 has joined #asahi
20:07jamespmorgan has joined #asahi
20:13jamespmo_ has quit [Ping timeout: 480 seconds]
20:17tinstew has quit [Ping timeout: 480 seconds]
20:19leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
20:25tinstew has joined #asahi
20:28qabla has joined #asahi
20:28qablajust wondering if its to be expected that battery on linux-asahi-edge would be running just about as much (maybe more?) than std asahi
20:33mamba has joined #asahi
20:33tinstew has quit [Ping timeout: 480 seconds]
20:34qablaok i have mmy element logging so i'll just hop off ric, but if anyone has an answer please feel free im still here
20:35qabla has quit [Quit: leaving]
20:35aralso, 1% every 5-10 minutes would still be ~500-1000 minutes → ~8-16 hours, which sounds… reasonable?
20:36opticronlooks like DCP is edge-only for both M1 and M2, so that should provide some power savings I think...
20:38opticronand depending on whether your DE (I know nothing about i3) is offloading to it, it could be saving power or not
20:39jannaugpu rendering should more efficient as long as i3 doesn't redraw a bazillion times due to the vblank irq issue
20:39mamba_ has joined #asahi
20:43mamba has quit [Quit: Reconnecting]
20:44mamba_ is now known as mamba
20:44cylm has quit [Quit: WeeChat 3.6]
20:59LinuxM1 has quit [Quit: Leaving]
21:00LinuxM2 has joined #asahi
21:13tinstew has joined #asahi
21:14LinuxM2chromium/usr/lib/chromium/chromium: error while loading shared libraries: libre2.so.9: cannot open shared object file: No such file or directory
21:23c10l has quit [Quit: Bye o/]
21:33c10l has joined #asahi
21:35LinuxM2 has quit [Remote host closed the connection]
21:36LinuxM2 has joined #asahi
21:52Moprius has joined #asahi
21:53abbe_ is now known as abbe
21:56amw has quit [Ping timeout: 480 seconds]
22:02axboeuntil chromium worked with 16k pages I did use firefox and quite liked it, but got drawn back to chromium from force of habit (and because I'm using it on other platforms)...
22:14jamespmo_ has joined #asahi
22:20jamespmorgan has quit [Ping timeout: 480 seconds]
22:23LinuxM2 has quit [Quit: Leaving]
22:43Moprius has quit [Quit: bye]
22:48mkurz has quit [Ping timeout: 480 seconds]
22:49psanfordi think i've run into a 16k page issue with an application using jemalloc. DuckDB v0.6.0 segfaults consistently for me on asahi/nixos. It looks like they just switched to jemalloc in a recent version. Downgrading to a version before they switched to jemalloc works fine. Are there upstream jemalloc patches for 16k pages?
22:53tinstew has quit [Ping timeout: 480 seconds]
22:58psanfordgreat i'll try that. I'm curious how distros will handle that in their packaging systems
23:04psanfordah, well this patch doesn't seem like its helping: https://github.com/duckdb/duckdb/pull/4971/commits/3b67618ac98e49aaa33163c48eb18ba5f69880f7
23:09SSJ_GZ has quit [Ping timeout: 480 seconds]
23:09jmshrv has joined #asahi
23:20confusomu has joined #asahi
23:39thevar1able has quit [Remote host closed the connection]
23:40thevar1able has joined #asahi
23:50psanfordreverting the `LG_PAGE` patch fixed the segfaults for me. I opened an issue with DuckDB to hopefully get that fixed. thanks for the help!
23:52thevar1able has quit [Remote host closed the connection]
23:52thevar1able has joined #asahi
23:53thevar1able has quit [Remote host closed the connection]
23:53thevar1able has joined #asahi
23:54thevar1able has quit [Remote host closed the connection]
23:54thevar1able has joined #asahi