#
…

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:28tpw_rulesjust use pacman -Syu
02:28tpw_rulesbut gpu drivers are not ready yet afaik
02:29lugpocalypseI kind of expected that, but thanks for confirming it.
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:34marcantpw_rules: missed the blog post?
03:37tpw_rulesso i did. it's not on the twitter yet in fairness
03:40tpw_ruleshearty congratulations though. i will have to try it soon
03:42tpw_rulesthe edge kernel will work independently of the edge mesa right?
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:51axboethat's it?
03:51axboeasahi/mesa.git
03:51chadmedyep just the kernel and the main branch from asahi/mesa
03:52chadmeddont forget to update m1n1 with the DTs from the kernel you build
03:52axboethat I already did
03:52chadmedoh and you need the latest m1n1
03:52axboethat too
03:53tpw_rulesdoes dcp actually need the gpu involed?
03:53tpw_rulesor did they just sort of get released at the same time?
03:53chadmedno dcp has been working for several weeks
03:53axboethat I'm already running
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:54axboeI'm on debian
03:54axboelooks like it ships 22.4
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:55axboechadmed: sure, I'm more worried about 22.4 vs 23.0-devel
03:56chadmedi updated mesa on gentoo without rebuilding the world and it worked fine
03:56axboechadmed: what version was it running prior?
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:57tpw_rulesso uapi connects the kernel and userspace
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
03:58chadmedmesa handles all that internally and apps shouldnt care about it
03:59tpw_rulesi guess there are not a huge number of apps that directly depend on mesa
03:59axboebuilding
04:01jamespmorgan has joined #asahi
04:01axboethese laptops never cease to amaze
04:01chadmedikr its nuts
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:02axboewhich is really nice
04:04axboeaxboe@m1max ~> glxinfo|grep Device 0.000s Device: llvmpipe (LLVM 14.0.6, 128 bits) (0xffffffff)
04:04axboehmm that doesn't seem right, does it?
04:05chadmedwhat options did you feed to meson for configuring?
04:06axboe--prefix=/usr
04:06axboebut looks like I may have some conflicting libs here
04:06jamespmo_ has quit [Ping timeout: 480 seconds]
04:08axboeI'll give it a go on the test laptop tomorrow
04:08unicordion has joined #asahi
04:26marcantpw_rules: lol, I forgot I had the crossposter disabled...
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:28marcanaxboe: ^
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:29marcanalso you need CONFIG_DRM_APPLE and CONFIG_DRM_ASAHI
04:30tpw_rulesand it might even be there just for headers
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:01tpw_rulesmarcan: is that modeset config necessary for dcp and gpu, or just gpu?
05:01marcandcp and gpu because xorg gets confused by the two drm devices
05:02marcanreally just dcp, it's just that it works by accident without it if you don't have the gpu driver
05:02* tpw_rulesok, thank you
05:02* tpw_ruleslearned today that command+enter does /me
05:02marcanthe way it works is apps are supposed to open the DCP DRM device
05:03marcanmesa does the render offload to the GPU behind the scenes (kmsro)
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:45joskechadmed: maybe update your PR for audio PM pretty please? :-)
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:01kettenismarcan: xorg really shouldn't need a config file for this
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:47marcanit's Xorg and ~nobody is working on Xorg
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:48marcane.g. anything related to DPI scaling
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:49marcan(everyone=people on the desktop distro)
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:54marcanas400: that means you have processes waking up the CPU.
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:54marcanyou need to fix the wakeups, not change the governor.
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:55marcanit ends up warm and then I can't wake it up
08:55marcanI'm pretty sure there's something that ends up in an infinite loop or IRQ storm or something
08:56marcanI need to look into that
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:00marcanthat never happens with ondemand (assuming you're sleeping between cats)
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:01as400marcan: you mean deep-idle ?
09:01marcanyeah, sorry, deep idle
09:01as400I was looking for information about it but couldn't find anything useful tbh
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:09mpss/and of/and if/
09:09as400mps: but xorg is just obsolete and nobody is working on it...
09:10mpsas400: that not true. some people works on xorg and make updates from time to time
09:10marcanmps: I don't care :)
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:10marcannon-average users are free to switch the default back to X11
09:11marcanif you don't like it, uninstall asahi-desktop-meta or go with the minimal image
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:12marcanchanging a default is not making it "intentionally hard to use"
09:12waldiand given that there is a translation layer from X to wayland, you can use both anyway
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:13marcanif you uninstall asahi-meta, we will not take bug reports from you
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:15marcantherefore wayland becomes the better option
09:15marcanagain, people are free to pick their poison
09:15marcanbut we *will* be switching to wayland by default
09:15marcanand other distros have done that ages ago already
09:15marcanthat is not vsync
09:15marcanthat is TearFree
09:15marcanthey are different things
09:16marcaneven with the TearFree patches you get no vsync on apple machines
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:17mpsmarcan: I missread and missunderstood you comment above
09:17marcaneven though the blogpost told people to use wayland
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:18marcanthat is a one-time action on package upgrade
09:19marcanif you don't like it, choose xorg again on the login screen
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:19mpsyes, yes, now I don't see any issue
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:28marcankujeger: I think KDE has been doing its own thing for a while now
09:28marcanQt has natively supported fractional scaling for ages
09:28kujegerah, nice
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:29kujegerfollowing the PR has been a rollercoaster for sure
09:30kujegerbut I hope it results in a really good experience across DEs
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:31marcanlina removed the fake IRQ thing because it was broken, right?
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:32marcanthe hardware flips buffers
09:33marcanthat's how it works on every modern display controller
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:33marcansoftware buffer flipping has been broken for ~20 years
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:34marcanbut as we know Xorg is stuck 20-30 years in the past :)
09:35marcanmacOS switched to this model ages ago (Wayland is basically doing what macOS does)
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:36marcanthere is no vblank emulation/IRQs without the actual vblank stuff
09:36marcanxorg gets errors on the relevant ioctls and so never waits
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:39marcanbut are the right speed in Wayland
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:40marcanI don't think we want to go there
09:42marcanincidentally, I looked at the relevant Xorg code and it's also broken :)
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:42marcannot that it matters since neither work for us
09:42marcanbut so much is broken about xorg, really...
09:42marcanit's clear ~nobody cares any more
09:43_jannau_i.e. the workaround will hurt the well behaved clients
09:46_jannau_the modeset driver's atomic modeset implementation was/is apparently that broken that it was forcefully disabled on kernel side
09:47svenlovely :D
09:47svenimho that getting into the kernel is a strong argument for just how broken xorg is
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:49ar(like the menus placement i mentioned)
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:04khlinux-asahi-edge*
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
10:45khI forgot to mention the model, it's j293
10:47chadmedright click it, click enter edit mode and then change the panel height
10:48khThanks that worked
10:49khEverything else still looks huge though (e.g. calendar)
10:53chadmedyour scaling settings are probably wrong then
10:53chadmedchange them in system settings->display
10:54khNah, the scaling is the same yet everything looks so much bigger compared to X
10:54khMaybe it's a KDE thing
11:00khchadmed: Sorry by everything I meant stuff on the taskbar
11:00khApps like Firefox scale fine
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:44as400And the same with s2idle here. It gets hotter and takes more juice than with screen off.
11:45tinstew has joined #asahi
11:46joskechadmed: no worries, take your time
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:56as400ChaosPrincess: change panel settings and scaling in Plasma settings
11:56joske has quit [Quit: Leaving]
11:57as400piroko9: yes, matrix bridge is banned
11:57piroko9alright. good to know at least. thanks :)
11:57as400irc only now
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:59piroko9in one update came brightness control, headphone jack support *and* GPU acceleration
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:00as400ChaosPrincess: right click on panel, enter edit mode, change height
12:05leitao has joined #asahi
12:09leitao has quit []
12:10tinstew has quit [Remote host closed the connection]
12:13marcankh: Check your DPI settings as the post mentioned. DPI forcing should be disabled.
12:13marcanboth that and the scaling settings are stored independently for wayland and X
12:15marcanpiroko9: thanks :)
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:16khmarcan: It's disabled
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:16khI'm assuming ChaosPrincess has the same issue as me as well\
12:16ChaosPrincesssmells very much like userspace bug
12:17marcanChaosPrincess: log out and back in
12:17ChaosPrincesslogging out and back in did not help
12:17marcankh: toggle both that and the DPI scale around and log out and back in
12:17ChaosPrincessin fact, i had to do it for the settings to even apply
12:18khmarcan: I played around with it previously but it didn't really change anything
12:19marcanwhat machine is this?
12:19khWhen I dropped the scale task bar did shrink but so did everything else
12:20marcanthe taskbar being huge at first is normal, just resize it
12:21marcannot sure if it just resets and saves separately or the coordinates are different to x11
12:21marcanI also noticed konsole tends to open tiny windows at first
12:21marcanthe calendar though, looks normal to me, same as on xorg
12:21marcanwait no now it's huge, what lol
12:22marcanoh but it's resizable
12:22marcanjust resize it
12:22marcangoing back to xorg broke it
12:22marcantl;dr coordinates are different on x11 and wayland, so anything saved shows up differently on the other or something like that
12:22khOh I did not notice 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:27jannauI think there was a fix konsole opening tiny last week or the week before that
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:28marcanjmshrv: that almost looks like 12.3 doesn't like something about your laptop
13:29marcanmaybe it has something to do with that Apple bug and repaired machines?
13:29jmshrvThat Apple bug? 👀
13:30marcanwe use 12.3 for asahi
13:30jmshrvYeah that sounds exactly like what's happening
13:30jmshrvWhat a fun edge case
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:31marcanI wonder if 12.3.1 fixed it. that had an iBoot update.
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:32marcanaaron465: unlikely to be specific to Asahi, that sounds like a gnome bug/issue
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:34jmshrvmarcan: That would be great :)
13:34marcanaaron465: no changes to wifi
13:35jmshrvCould the 12.4 firmware used for M2 work here, or would that be way more effort than adding 12.3.1?
13:35marcanthat is more likely to break the GPU
13:36marcan12.3.1 is unlikely to break anything
13:36marcanboth would need changes to m1n1 anyway
13:36marcanjmshrv: curl -L https://alx.sh/dev | sh
13:37marcanuse expert mode, pick 12.3.1 when prompted
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:40jmshrvmarcan: It's only listing 12.4 and 12.3 for the OS:
13:40jmshrvChoose the macOS version to use for boot firmware:
13:40jmshrv 1: 12.4
13:40jmshrv(If unsure, just press enter)
13:40jmshrv 2: 12.3
13:40jmshrv» Version (2): 12.3.1
13:40jacksonchen666 has quit [Ping timeout: 480 seconds]
13:41marcanwhat installer version does it show at the top?
13:41jmshrvv0.5.1-1-gd69b61c5cc87
13:42marcanI'm confused... is my version comparison logic broken again?
13:42marcanoh wait no
13:42marcanduh, the data list
13:43marcanjmshrv: try again now (might need a 5 minute delay for the GitHub cache to expire)
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:00jmshrvThis cache is very long lived lol
14:00minecrell has joined #asahi
14:00marcanit shouldn't take that long...
14:02jmshrvOh I was just checking the version of the installer, my bad
14:03marcanoh yeah that didn't change
14:03jmshrvIt's showing 12.3.1 now, will let you know if it works :)
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:09Sonimarcan: can we send you fan art?
14:09marcanfan art... like of my face?
14:09jmshrv has quit [Remote host closed the connection]
14:09Soniuh not really
14:09Soniliteral fan art
14:10marcanI dunno how this works lol
14:10marcanI know lina gets fan art but that seems more common with vtubers
14:11piroko9 has joined #asahi
14:11Soniwe mean it's literally a fan XD
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:12Sonimay we?
14:12marcanpiroko9: depending on model there seem to be sleep issues sometimes
14:12marcanSoni: I mean yes but I'm still confused
14:12marcanpiroko9: what model?
14:13piroko9m1 pro mbp
14:13marcanokay yeah, lots of reports for that one
14:13piroko9cool cool
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:14marcanI need to add a current log thing to the battery driver, so we can debug this stuff
14:15marcanand just generally debug suspend, I barely had a chance to look into it beyond the stuff that completely broke it
14:15marcanI know the keyboard/trackpad is a problem
14:15bcrumbhi marcan
14:16jmshrv has joined #asahi
14:16piroko9aaron465: you have to explicitly enable lid suspend in kde settings if you haven't
14:16piroko9it's set to just turn the display off by default
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:17marcancool, let me push m1n1 then, thanks for finding this :)
14:17jmshrvnp, wasn't expecting it to be such a weird edge case
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:23marcanjannau: m1n1 sets compat as 12.3.0
14:23marcanoh wait, you check the firmware version, not the compat version?
14:24marcanyou're supposed to check the compat version lol
14:24jannauI check both
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:27marcanthe only piece that should care about exact actual firmware versions is m1n1
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:28jannauI spent too much time thinking whether I want reject missing properties
14:28marcanin this case I think we want to reject missing props, since this is critical information
14:29jannauyes, I still want to be able to report the actual fw_version though
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:30marcanyou can just report it numerically as %d.%d.%d :)
14:30DarkShadow44 has quit [Quit: ZNC - https://znc.in]
14:30DarkShadow44 has joined #asahi
14:30marcanalso the version number length can change in principle
14:30marcanso ideally don't hardcode that
14:31marcanfor example, 12.3 beta1 would probably end up as 12, 2, 99, 1
14:32marcan(this is similar to how the installer internally encodes beta version numbers)
14:34bcrumbbtw should the sound system work right now or we still on hold for it?
14:35bcrumbthanks...
14:40bcrumbcould you btw check #dev? thxx
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:02bcrumbwhat process is tasked to move vmlinuz from lib/modules to boot/ ?
15:02bcrumbto vmlinuz-linux-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:12bcrumbso, the asahi edge kernel is seriously a big improvement
15:12bcrumbvery smooth
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:19bcrumbwhat was apple native, 255 dpi or smth like that?
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:50marcandon't set font DPI
15:50marcanit's mentioned in the article
15:50marcanthat setting should be off in wayland
15:50marcanuse output scale instead
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:57marcanfonts look fine for me, did you log out and back in after changing the settings?
15:57marcanit's normal for stuff to look blurry when first applying until you restart
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:03bcrumbworks, i don't know what I like better though :/
16:04bcrumbforce font looks much sharper, will this setting not be supported in the future?
16:05nate8_ has left #asahi [Leaving]
16:05marcanthis is being fixed in wayland, see the above bug
16:05marcanforcing DPI is likely to cause other issues with apps and is not really supported on wayland
16:06LinuxM1 has joined #asahi
16:07bcrumbaight cool
16:07bcrumbbtw, where should i raise an issue about a USB device not being recognized at boot time?
16:08svendoes this happen on the vanilla asahi distro?
16:08bcrumbboth edge and vanilla i think
16:08svenso you can reliably reproduce it there without any changes to the kernel or the initrd?
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:09bcrumbsince the changes to the initrd are exacty those in that systemd PR
16:10bcrumbi'll go into the vanilla kernel once more
16:10bcrumbto confirm
16:10svenright, it sounds like you’re missing some modules
16:10bcrumbbecause, do note
16:10svenpossibly atcphy and/or nvmem
16:10bcrumbthat usb device does work when i just reconnect
16:10bcrumbpost boot
16:10marcanfwiw the modules should be in the initramfs as of recent asahi-scripts
16:10marcanunless I missed something
16:10marcanbcrumb: that's something else (I think, sven?)
16:11svenyeah, that sounds like something else then
16:11bcrumbyep, that is why i mentioned
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:11svencan you get the full dmesg output?
16:12bcrumbthis is why i just want to open an issue somewhere though
16:12bcrumbto dig first myself
16:12rvalue has quit [Ping timeout: 480 seconds]
16:13svenI assume this is in the typec ports?
16:13bcrumbalso lsmod shows that the above modules are there, but we knew that
16:13svenok, and with the latest kernel from a day or two ago? I recently fixed a race
16:15bcrumbyeah, so from rc6 5-1 to rc8 3-1
16:15bcrumbwas the upgrade
16:15bcrumbscripts 1129 1206
16:16svenok, then please paste the dmesg somewhere
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: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:30bcrumbdon't open the system monitor history tab, i like some of you guys
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:29aaron465noticed because it had renegotiated down to 100mbps
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:44axboemps: thanks, that was useful!
17:44LinuxM1 has quit [Quit: Leaving]
17:44axboeseems to work for me, except chromium doesn't like hardware accel being on...
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:54Putojust to confirm, external display support over usb-c still isn’t a thing, right?
17:58cylm has joined #asahi
18:00das_j has quit [Remote host closed the connection]
18:02jannauPuto: yes, it's not yet supported
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:03sventhere’s some boot argument to just print them to the normal log buffer
18:04svenI blame advent of code and rust for no progress on the typec/atcphy/altmode/tbt stuff :D
18:04jannau'tp_printk tps6598x:*' iirc
18:04sventhat sounds very familiar
18:06jannauI'm not sure that works though if tipd/tps6598x is built as module
18:06WindowPain_ has left #asahi [#asahi]
18:07svenhm, good point. I still don’t run a kernel with modules
18:07jannauI think the events won't get enabled by the command line argument
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:12jannaujust rebuilding hte kernel with tipd looks simpler
18:12svenand hope that it still runs into the same boot issue I guess :/
18:13svenmaybe it’s also enough to just go over the tipd probe again
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:16bcrumbsven: will try with the kernel args i guess?
18:16bcrumbbut thanks for looking into it
18:16bcrumbi will try to use what jannau posted
18:16bcrumbnoted: could this be because I'm using m1n1 stage 2 boot instead of GRUB?
18:16bcrumbi mean I have everything concatenated properly
18:17bcrumband traces also showed kinda fine I guess
18:17svenmaybe that’s what triggers the issue
18:17svenbut this sounds like some coordination issue between tipd, dwc3 and atcphy
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:20svenI’m not gonna stop you if you want to investigate yourself ;)
18:20bcrumbyeah just looking for clues
18:21sventhat requires a lot of context how usb works in these machines unfortunately
18:21svenbut those three drivers and their interactions are a good start
18:21bcrumbi will do my best
18:21das_j has joined #asahi
18:21svenbut it sounds like tipd doesn’t see a plug event
18:22bcrumbyeah, and the plug event should fire on boot even if pre connected?
18:22svenmy first guess would be something going wrong inside tipd’s probe
18:22bcrumbdoes it constantly monitor or only scan once on boot? it should monitor right?
18:22svenugh…. This might be tipd probing before dwc3 and atcphy and firing off the plug event into nowhere
18:23bcrumbso order
18:23Glanzmann has joined #asahi
18:23svenwho knows
18:23bcrumbyeah, i'll look into it based on this
18:23svenI’d start with the trace events and take it from there
18:23Glanzmannaxboe: https://thomas.glanzmann.de/asahi/2022-12-07/ but mps already pointed you to it. Thank you mps. ;-)
18:24axboeGlanzmann: lol shoot, didn't have to build them myself then :)
18:25axboeGlanzmann: works well or me, except chromium
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:26Glanzmannprobeing keyboard backlight stuff.
18:27Glanzmannaxboe: What is the issue with chromium?
18:27Glanzmannaxboe: Never mind, I see. I'll put it on my bug list.
18:27LinuxM1 has joined #asahi
18:28zzywysmGlanzmann: is there a particular type of kernel config for apple silicon you want me to make?
18:28mpsGlanzmann: just for info, chromium works for me on alpine linux
18:28axboemps: oh yeah? with hardware accel on?
18:28axboeif I have that on, it just sits and spins and spews some errors
18:28axboeunless loaded with LIBGL_ALWAYS_SOFTWARE=1
18:28mpsaxboe: hm, don't have idea. how to enable it?
18:28LinuxM1same for me, gpu acceleration on chromium won't start it, it's a problem with shared libraries
18:29axboemps: go into settings, search for 'hardware'
18:29axboea slider will show up
18:29Glanzmannzzywysm: Previously I used the debian testing arm64 config and enabled the asahi options. That config nolonger boots with the gpu stuff.
18:29mpsaha, will try
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:30Glanzmannzzywysm: I try to stick as close as possible to the Debian distro kernel.
18:30zzywysmthe Debian distro kernel, like most distro kernels, is wildly bloated
18:31zzywysmany peripherals you use that i should make sure not to break?
18:31Glanzmannzzywysm: I know, I don't mind. Now that j`ey and jannau told me how to crosscompile.
18:32Glanzmannzzywysm: I only user usb devices like usb audio card, hdmi grabbers, cameras, mice, keyboards.
18:32Glanzmannoh and network cards.
18:32zzywysmk, give me a few hours
18:33tinstew has joined #asahi
18:33mpsaxboe: hm, looks like hardware was enabled already
18:33axboemps: funky
18:34Glanzmannzzywysm: Look forward to it.
18:34mpsany specific site to check/test how it works
18:34LinuxM1Is it normal that the keyboard backlight does not work on a MacBook Pro M1 Max? I use asahi-edge kernels
18:35j`eyLinuxM1: how are you trying to use it?
18:35axboemps: nope, mine just hangs and spins if launched with that, don't even get a window
18:35mpsaxboe: but, aarch64 is first class arch on alpine, it is not less important to x86 as on some/most distros
18:35LinuxM1in what way? I did not understand the question
18:35Glanzmannaxboe: I get a white window with nothing in it. Can't do anything with it.
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:36axboeGlanzmann: yep that's what I see
18:36j`eyLinuxM1: how are you trying to use the backlight?
18:36axboeGlanzmann: and a bunch of errors if you launch from a console
18:36axboemps: debian should be the same, might be a difference in how it's built?
18:36axboeGlanzmann: ditto
18:37LinuxM1I simply can't find a menu where to activate it, on macbook air M2 instead the retruillumination works
18:37mpsfor years I use alpine aarch64 mostly, don't had serious issues with anything
18:37ethernet has joined #asahi
18:37LinuxM1in macbook air M2 the backlight keyboard work
18:38axboeLinuxM1: works for me on m1 max
18:38j`eyLinuxM1: so you cant find it on the same menu?
18:40j`eyLinuxM1: can you run 'ls /sys/class/leds/kbd_backlight/brightness'
18:40LinuxM1maybe i don't remember what i did on macbook air M2 to activate it
18:40bcrumb has quit [Quit: WeeChat 3.7.1]
18:41LinuxM1now I'm from mac os, let me get the MBP m1 max and try from there
18:41Glanzmannaxboe: Can you please send me your kernel config for the gpu kernel? I would like to try it.
18:41axboeLinuxM1: do you have /sys/class/leds/kbd_backlight
18:41axboeGlanzmann: sure
18:41axboeLinuxM1: if yes, read/write to 'brightness' in there
18:42LinuxM1wait while I turn on the MBP and do that check
18:42Glanzmannaxboe: Thank you.
18:42axboeonly difference from my previous is a) using LLVM=1 and enabling rust, and b) enabling the gpu driver
18:43Glanzmannaxboe: I see, thank you.
18:43Glanzmannbacklight works for me on m1 air.
18:43Glanzmannsuspend also.
18:44LinuxM1yes i have /sys/class/leds/kbd_baacklight in my system
18:44mpsGlanzmann: with kernel config I posted to you everything works for me on m1 mpb and m1pro macbook
18:45j`eyLinuxM1: then it should work, but I dont know where the menu is on kde
18:45mpss/mpb/mbp/
18:45LinuxM1exactly I can not find the menu where to enable the backlight
18:46Glanzmannmps: For me, too. I'm only missing automounter, but I could of course enable that. https://pbot.rmdir.de/fUkju8JQ8evyWvr2by0LrA
18:46GlanzmannLinuxM1: What distribution do you use and what desktop environment?
18:47LinuxM1asahi linux desktop
18:47LinuxM1asahi-edge-kernel
18:47jannauaxboe: try MESA_LOADER_DRIVER_OVERRIDE=asahi chromium --ignore-gpu-blocklist
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:48Glanzmannjannau: WOrks for me.
18:48LinuxM2 has joined #asahi
18:49Glanzmannjannau: Even the man over bord video smooth.
18:49LinuxM1Glanzmann, yes work!!!
18:50LinuxM1Glanzmann, so everytime i turn on i have to run that command? Isn't there a way to leave the backlight on?
18:51j`eyit should stay on that level
18:52GlanzmannLinuxM1: and if it doesn't just write a script that runs on boot,
18:52LinuxM1ah ok! a script with this command line
18:54mpsLinuxM1: doesn't it works by default with kde?
18:54LinuxM1mps work on my macbook air M2, but not in MBP m1 Max
18:55mpsah, interesting
18:55LinuxM1to make it go to the MBP I had to give the command suggested before
18:57LinuxM2now i try reboot and i check if the backlight stays on
18:58LinuxM2in this username i use macbookpro m1 max
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:21axboejannau: oops missed this, works!
19:25axboejannau: it's the apple_dri that messes it up
19:30GlanzmannLinuxM1: Where did you put the command that I gave you?
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(at boot before sddm)
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:28qablahey guys
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:28qablalosing about a % every 5-10 mins
20:30qablaim using i3 on xorg btw
20:31qablais anyone experiencing similar issues?
20:33mamba has joined #asahi
20:33tinstew has quit [Ping timeout: 480 seconds]
20:33arplease be patient. people involved in the project are in a lot of different timezones
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:37opticronbut edge also activates GPU
20:38opticronand depending on whether your DE (I know nothing about i3) is offloading to it, it could be saving power or not
20:39aropticron: i3 is a simple non-compositing tiling wm
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:13LinuxM2chromium with gpu enabled in wayland not work:
21:13LinuxM2chromium
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:38psykosethat's not related to anything except not having the latest version of libre2 installed
21:40LinuxM2psykose, So can it be resolved?
21:46psykosetry pacman -Syu :)
21:47LinuxM2My system is updated, that command launch it every day
21:52Moprius has joined #asahi
21:53abbe_ is now known as abbe
21:56amw has quit [Ping timeout: 480 seconds]
21:56axboeLinuxM2: reinstall libre2?
21:58LinuxM2pacman -S libre2 ? There is no specific library with this name
21:59pirokoit's re2
21:59pirokobut it won't fix it
21:59pirokosomething is out of sync
21:59piroko(I have the same issue)
22:00axboerolling distro fun?
22:00LinuxM2ah ok! I'm not the only one to have this problem with Chromium
22:01LinuxM2In my systems I have always used chromium, I don't love firefox
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:02axboebut sounds like chromium just needs to get re-linked, if re2 was updated to .10
22:03axboeof FF had better/smoother scrolling, I'd probably still use it
22:04LinuxM2We hope it will be placed soon
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:51povik23:03 < axboe> of FF had better/smoother scrolling, I'd probably still use it
22:52povikyeah, why does firefox either have chopped scrolling, or annoyingly interpolated?
22:53tinstew has quit [Ping timeout: 480 seconds]
22:54j`eypsanford: jemalloc supports 16K.. but you have to build it to support it
22:56psanforddo you have details on building jemalloc properly for 16k pages?
22:56j`eyyeah trying to find it
22:57j`ey--with-lg-page=16
22:58j`eyor 14 (thats 16K, =16 is 64K but should work)
22:58psanfordgreat i'll try that. I'm curious how distros will handle that in their packaging systems
23:02mpspsanford: alpine doesn't use jemalloc for anything important
23:05j`eythis is not macos!
23:06axboepovik: that I would love to know too
23:09SSJ_GZ has quit [Ping timeout: 480 seconds]
23:09jmshrv has joined #asahi
23:10jmshrvJust thought I'd say that the 12.3.1 firmware is working with KDE :)
23:10jmshrvGPU drivers aren't but that's to be expected
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
…