#
…

2023-03-12

00:07chadmed_ has joined #asahi-alt
00:12chadmed has quit [Ping timeout: 480 seconds]
00:52jamespmorgan has joined #asahi-alt
00:57jamespmo_ has quit [Ping timeout: 480 seconds]
01:28hightower2 has quit []
01:37jamespmo_ has joined #asahi-alt
01:43jamespmorgan has quit [Ping timeout: 480 seconds]
02:23chadmed_ has quit [Quit: Konversation terminated!]
02:23chadmed has joined #asahi-alt
02:23chadmed has quit []
02:26chadmed has joined #asahi-alt
02:59opticronGlanzmann, getting 110fps on supertuxkart with default settings on the underwater level, everything looks good. didn't try reboot
03:00opticronthe poweroff did work for me
03:03opticronoooh, and you have the charge limit thresholds in there, too
03:03opticronI'm excited
03:04chadmed has quit [Read error: No route to host]
03:04opticronI've been holding off on using this as a daily driver until I could make sure I wouldn't destroy the battery
03:04opticrondid that finally get merged or into asahi or are you pulling it from wip?
03:08chadmed has joined #asahi-alt
05:28chadmed_ has joined #asahi-alt
05:28chadmed has quit [Read error: Connection reset by peer]
06:12possiblemeatball has quit [Quit: Quit]
06:15jamespmorgan has joined #asahi-alt
06:21jamespmo_ has quit [Ping timeout: 480 seconds]
07:06balrog has quit [Ping timeout: 480 seconds]
07:07balrog has joined #asahi-alt
09:05Glanzmannopticron: It got merged. This is the asahi tree that marcan yesterday released.
09:05marcanI did not release anything
09:05marcanyou are still running pre-release software
09:06marcanuntil it hits the `asahi` repo it is not releasexd
09:06marcanI don't know how many times I have to say this...
09:06Glanzmannmarcan: Can you reproduce the 'reboot' hang?
09:06Glanzmannmarcan: Okay, let me rephrase, its the same version that you pushed to the pkgbuild yesterday.
09:07marcanI did not push anything to the stable PKGBUILD branch
09:07marcanwhich is the release branch
09:09marcanat this rate I'm just going to switch to using private repos for everything because I do *not* need a bunch of altdistro guys pulling commits the minute I push them when things aren't even properly tested by the usual team and we're still fixing bugs
09:09marcany'all are worse than Manjaro
09:09Glanzmannmarcan: You asked us to test, we tested.
09:10GlanzmannI did not push anything out to users, I just released the debs on the latest version in a tar ball in this channel.
09:10marcanI asked #asahi-dev to test the `asahi-dev` packages.
09:13GlanzmannI see, than let them test and we go back to sleep.
09:14Glanzmannaxboe had the wrong rust version btw and the gpu now also work him.
09:14Glanzmann has quit [Quit: n8]
09:20mpsmarcan: do you make tagged release and labeled as verified ok for distros?
09:21marcanthat's what the pkgbuilds in the `stable` branch are
09:21mpsaha, ok. I'm trying to stick with tagged kernels and verified
09:25mpsI noticed one crash of driver during boot but kernel works fine, at least for now. dmesg output is here https://tpaste.us/9MP0
09:41svenand now you know why I rarely push wip branches anymore 🙃
09:42svenfor me it was random people asking me in /msg how to run a kernel with external display support
10:30ashi has joined #asahi-alt
10:32chadmed_ is now known as chadmed
10:35chadmedi swear we have this discussion at least once every couple of months
10:36ashiSo, who is the target audience for what PKGBUILDs main branch produces? Why is -alt not allowed to build that? And why is such an agressive atmosphere neccessary towards people who are just playing around, not demanding anything, not expecting anything. I am just happy to see software evolve. But you guys could be really nicer.
10:37ashiThere is no need to treat us like idiots, that kind of arrogance pisses me of.
10:38chadmedthis was all addressed last time you asked about the same thing but to reiterate the problem is absolutely not people wanting to test new and exciting stuff
10:39chadmedits that time and time and time again someone distributes test builds or instructions on how to build test code to people who cannot support themselves
10:39chadmedwho then come here expecting to be supported, usually for some bug that is already known about and being worked on
10:40chadmeds v e n getting private messages about external displays being a prime example here
10:41chadmedto answer the question more directly, the target audience is people who can build, debug and support themselves through a release cycle
10:41chadmedid est, developers
10:41ashiI stopped doing that (sharing instructions, scripts, whatever) completely. But neither me not Glanzmann got the whole message! What we did last time was to build "random branches" without any tags, this time Glanzmann waited till there were PKGBUILDs who pointed to the exact commits or tags until he build that. I thought it was fine but again m a r c a n rant time.
10:44chadmedplaying both sides, sure it probably _could_ have been more explicitly stated where release/ready-to-package stuff lives but that said in what universe is the main branch of any remotely complex repo considered release-ready
10:45chadmedfurther to that, this exact scenario happened months ago when people were trying to build linux-asahi/main, so the default asahi branch was spun out and made the default for release
10:45chadmedlike this exact scenario has literally happened before and it seems very little was learnt from it
10:47ashiI *am* without any doubt the target audience. And I never intended to take someones time. I will try harder to understand the purpose of this channel then by reading passivly, maybe one day I get what it is for then.
10:47ashiThanks
10:47ashi has quit [Quit: Leaving]
11:19Retr0id has joined #asahi-alt
11:21Retr0idcy8aer, I guess you're talking about the glibc-widevine package? I don't maintain that, but if I had to guess it's the TLS alignment thing that's causing issues
11:22cy8aerRetr0id: yep thought about this too. But thanks for your hack, I am nearby 😉
11:24as400 has joined #asahi-alt
11:38chadmed has quit [Quit: Konversation terminated!]
11:39chadmed has joined #asahi-alt
12:14possiblemeatball has joined #asahi-alt
12:52leif has joined #asahi-alt
13:12kode54 has quit [Quit: Ping timeout (120 seconds)]
13:12KDDLB has quit [Read error: Connection reset by peer]
13:12KDDLB has joined #asahi-alt
13:15kode54 has joined #asahi-alt
13:41leifI'm just going to throw my 2 cents in here. Instead of of asking marcan whether he can reproduce an issue, why you don't you just install the arch asahi kernel on Debian? I can easily install the Arch kernel on Fedora via kernel-install (although this can be done manually as well). And also maybe think of setting up a github page (or something similar) and then moving some of the discussion over there? There's absolutely nothing wrong with
13:41leifbeing on the bleeding edge. I personally love it. But I never ever pester the devs w/ support related questions for anything that hasn't been officially released.
13:42leif has quit [Quit: Leaving]
13:44leif has joined #asahi-alt
13:46leifFWIW, I just updated my project to the latest (ie bleeding edge) kernel, mesa, uboot...etc packages and am not not running into any reboot hang issues.
13:46leif has quit []
13:49as400@leif I have a question. Asked this on your gh. But since you're here
13:49svenyeah, usually the -dev releases are for developers who are comfortable debugging the kernel and figuring out *why* something broke. I don’t think anyone cares if you run them but if you package them for others users that becomes an issue
13:50leif has joined #asahi-alt
13:50as400After installing your Fedora - can I switch to rawhide repos ? Or it's not recommended ?
13:50leifas400 I'll answer your question on GH
13:53as400Thanks ! Appreciate it.
13:58leif has quit [Quit: Leaving]
14:13leif has joined #asahi-alt
14:17leifhmmm...it can be issue, but it can also be extremely productive. I've sent a number of bugfixes and bugreports upstream for various issues that either myself or users of my project encountered.
14:24leif has quit [Quit: Leaving]
14:30leif has joined #asahi-alt
14:32leifLike everything in life, it's a balancing act. It is helpful to attract users -- as long as they're the right kind of users ;)
14:34leif has quit []
15:11marcanright, the problem here is all the timewaster reports, not that people are running things at all
15:12marcan"reboot doesn't work"... okay, debug it? give me repro instructions that don't involve "install my debian spin"?
15:12marcanbecause that kind of stuff is 99% going to be some systemd nonsense or a missing kernel module, not something actually broken in the kernel
15:12marcan(and Glanzmann has quite the history of forgetting to enable kernel modules)
15:14marcanit's a dev release and I *already* have known real issues to figure out like kernel oopses, and known problems like stale DT patches, and a bunch of things we already found and fixed in like the first few hours after I started tagging 6.2 kernels
15:15marcanwhen we are already halfway through chasing bugs between the folks who are knee deep in this stuff and know how to debug the kernel, random third party reports are most likely going to be 1) dupes, or 2) not actionable, or 3) lower priority
15:15marcanand you can't know which and it's just much easier if you wait
15:16marcanonce *we* run out of kernel issues to fix *then* you can start reporting whatever ones you have left
15:20marcanalso PKGBUILDs repo now has stable as main and `dev` for dev, so there you go
15:22tpw_rulesmarcan: not sure if this was deliberate to better reflect support level, but the new main branch is now several months before where the old stable branch was
15:22marcantpw_rules: I just fixed that
15:22tpw_rulesninja'd? thanks
15:37jacksonchen666 has joined #asahi-alt
16:28jacksonchen666 has quit [Quit: WeeChat 3.8]
16:56marcanlike in particular these kinds of pings are just so *blatantly* a waste of my time I have no idea why Glanzmann insists on annoying me like this
16:56marcan02:33:59 < Glanzmann> marcan: Mesa does not build on Debian: https://pbot.rmdir.de/u/5w4beZcHH9vh7esDTfn3gw
16:56marcan03:04:50 < Glanzmann> Disabling freedreno let me compile mesa. Kernel boots, xorg starts.
16:57marcanif you cannot look at a build failure and determine it has *nothing* to do with me before pinging me on IRC, you should not be running a distro remix period.
16:59marcanI really, really shouldn't have to tell him that a lua parse error in a freedreno script (????) has nothing to do with us, and that he shouldn't be building freedreno at all if he's making asahi-specific packages (nor any other driver other than asahi and llvmpipe/swrast, like we do in our PKGBUILD)
16:59marcanI'm not Glanzmann's nor any one else's personal "debug my packages" guy, sorry
17:00marcanso yes, this kind of stuff is why I get annoyed
17:02marcannot just people testing stuff and being quiet about it or reporting actual actionable stuff when the time comes, that's fine
17:12* MichaelLongwill be in reading mode for long before asking anything
17:13marcanjust to be clear, being a newbie and getting things wrong is also fine
17:14marcanGlanzmann doesn't seem to have learned in a year+, unfortunately
17:17marcanbut on more general terms: our job is to get the hardware supported, and to help official distros figure out how to do things properly. alt distro remixes are fine *as long as* they are maintained by people who can actually do that without bugging us about things unrelated to hardware support.
17:18marcanalt distro remixes have very little long-term value, just like the official ALARM remix does. our job is to make that remix stop existing, *and so should be yours* if you are doing the same for another distro
17:18marcanif you are getting stuff upstreamed, that has real value
17:21marcanbut if you aren't, you should consider your altdistro a fun project you do for your own sake, not something we have to support in any way, and *definitely* not something we're going to help you with outside Mac-specific stuff, because just no. there are other avenues for learning how to do this stuff.
17:22marcanand if you can't get stuff upstreamed, maybe pick a different distro (like we are, after ALARM has shown itself too unmaintained to work well nevermind upstream stuff to)
17:24marcanwe're the wrong people to ask for help about packaging stuff anyway, it's not what we do
17:25as400Well, actually entire alarm thing is a really sad story.
17:25marcanbut what are we going to do?
17:25as400I've been hit hard with numerous bugs.
17:26as400It seems like very few distros have a strict QA procedures.
17:28marcanI don't think ALARM has any QA, given what I've seen
17:29marcanas far as I can tell it's mostly a pile of undocumented/nonpublic scripts running things mostly on their own, which work most of the time but sometimes fail horribly
17:30marcanunfortunately the lack of documentation/public repos/infra means we can't even try to help
17:31as400It's really extremely strange there is no public repos/docs. Like they don't want people to help ? Hard to understand for me.
17:32marcanI think ALARM suffers from a particularly bad combination of historical laziness around having an open process (at best, or maybe they actively want to hold their cards close for some reason?) and recent serious decline in free time the maintainers have to maintain
17:32marcanresulting in, well, an unmaintained bitrotting distro that nobody else can help with
17:33marcannor fork in any meaningful way
17:35marcanI did have a promising conversation with the main developer when this whole thing all started, but I think since then he's stopped caring about us because he just doesn't have the time to maintain a distro for raspberry pis, nevermind a desktop distro people use on real desktop-class machines
17:35marcanso there's nothing much for us to do other than move on at this point, unfortunately
17:36marcangood news as I've said is we have a distro with proper upstream developer support coming up :)
17:37as400Understandable. And sad. But you guys shouldn't be fighting all sorts of problems that distro is presenting. Yeah I know :) And it's number is 38, right ? :)
17:38marcanwell, we aren't for the most part
17:38marcanI'm making no attempt to fix their broken packages etc
17:38marcangoing there would be a bad idea
17:38as400It would just suck you in big time.
17:39marcanlike I really wish I had free time but I just *don't*
17:39handlerugI'd really love its number to be 3.17 but glibc monopoly :(
17:40marcanI'm at the point where I'm thinking of giving up on yet another personal hobby project I hold dear (that doesn't even take much of my time) because I just can't find the time for it
17:40marcanI've already cut down on a lot of random personal stuff since Asahi started
17:40as400I can imagine it's hell of a job.
17:40svenjust don’t burn out please!
17:41marcanI *like* what I'm doing here and I really want the project to succeed and get us where I know we can get to
17:41sven(easier said than done unfortunately)
17:41marcanand yes, I take care not to outright burn myself out, I've done okay so far
17:41marcanbut I'm just saying, the answer to the question "do I have time for X" where X is not core to the project goals is just, no I don't, unfortunately
17:45marcantoday I was talking with a friend who is giving me a hand setting up a personal task board thing because I just have way too much stuff to keep in my head right now
17:45marcanI might spend tomorrow setting all that up and writing a stupid python script to scrape asahi@ into a patches dashboard, so I can join the I-have-a-boutique-kernel-patch-tracker club too :p
17:49svenlol, I just have a filter to put then in a separate mailbox :D
17:49marcanI have that but mail just doesn't cut it any more
17:50marcanI just *cannot* keep track of patch emails any more, my inbox rarely goes under 500 and email is just horrible in every way for all the reasons we all know
17:51marcanso the point of said script would be to scrape high-level attributes from those emails (like coalescing patch versions into one item, logging the last activity / last patch send timestamps, who sent them, automatically detect merges for those maintainers that bother replying with that, etc.)
17:51marcanhopefully with that I can get the upstreaming train rolling smoother than it has so far
17:54steffen[m]So something like patchwork?
17:54marcanyes but less stupid and that actually does what I want
17:55handlerugor patchew
17:56handlerugside note: this would work well as a patch-oriented email client
17:56marcanI don't care about having a frontend for things, I end up having to use email anyway. I just want an easy dashboard that tells me what I need to do next and what is getting stale and what needs a rev/resend/etc.
17:58marcanmost of these tools seem oriented towards maintainers, *receiving* patches
17:58marcanthere doesn't seem to be much oriented towards submitters *sending* patches
17:58marcanor people overseeing a bunch of others sending patches on their own
17:59marcanhonestly I think what we're doing here is surprisingly unique as far as kernel dev goes
17:59marcan(and my maintainer role is trivial enough - the soc stuff - that I don't need tooling)
18:01marcananyway, I need to wake up early tomorrow, good night :p
19:03opticronglanzmann: fwiw, the charge limiter didn't seem to work properly. I set it to 85% just like my current daily driver and it charged up past 90%
19:42steffen[m] has quit [Remote host closed the connection]
19:47steffen[m] has joined #asahi-alt
19:49steffen[m] has quit [Remote host closed the connection]
19:52steffen[m] has joined #asahi-alt
19:55steffen[m] has quit [Remote host closed the connection]
19:55steffen[m] has joined #asahi-alt
20:18mpsnice, after upgrade u-boot asahi 2023.01-3 no more driver crash (I reported above) on kernel boot
20:18mkurz has joined #asahi-alt
20:37barrett has joined #asahi-alt
…