marcan changed the topic of #asahi to: Asahi Linux: porting Linux to Apple Silicon macs | https://asahilinux.org/2022/03/asahi-linux-alpha-release/ | General project discussion | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Topics: #asahi-dev #asahi-re #asahi-gpu #asahi-alt #asahi-stream #asahi-offtopic | Keep things on topic | Logs: https://alx.sh/l/asahi
<ComradeMisato[m]> <Dementor[m]> "I use a matrix client 😉..." <- what matrix client works on asahi 🤔 should i try element
<ComradeMisato[m]> btw marcan: i used diskutil to uninstall asahi before per this video and nothing has happened so far. is the video wrong? https://www.youtube.com/watch?v=nMnWTq2H-N0
<ComradeMisato[m]> * btw marcan: i used disk utility to uninstall asahi before per this video and nothing has happened so far. is the video wrong? https://www.youtube.com/watch?v=nMnWTq2H-N0
<ComradeMisato[m]> * btw marcan: i used disk utility to uninstall asahi before per this video and nothing bad has happened so far. is the video wrong? https://www.youtube.com/watch?v=nMnWTq2H-N0
<tpw_rules> just replace "NixOS' there with "Asahi" in your mind as you read it
<tpw_rules> don't use the graphical disk utility app. it's buggy and bad
<ComradeMisato[m]> i dont need instructions bc i already did it per the video
<ComradeMisato[m]> as i said
<tpw_rules> then the video might be wrong. there are instructions i know work properly
<tpw_rules> if you want help you'll have to be more clear about what the video said, what you did, and what went wrong
<ComradeMisato[m]> nothing bad has happened so far, as i previously said
<ComradeMisato[m]> nothing went wrong lol
<ComradeMisato[m]> i just wanted the guy's input
<tpw_rules> oh, i see, you edited it. those don't show up properly on irc
<tpw_rules> sorry
<ComradeMisato[m]> no worries
<tpw_rules> anyway what did the video say might happen that's bad? like i said IME disk utility.app is buggy and sucky and diskutil is not a whole lot better. i crashed disk utility.app once trying to make a FAT partition with lowercase letters in the name
<ComradeMisato[m]> tpw_rules: Nothing really. I mean what I'm trying to say is that using Disk Utility app is not recommended officially, however the video (and following the instructions on said video) shows no errors so far yet. I am just wondering if theres something in the video that the creator did not take into account
<tpw_rules> oh, not really probably. just that it's unclear and hard to use
<tpw_rules> if the video creator came up with good instructions then they are most likely just fine
<tpw_rules> i screwed up my m1 mini and had to DFU restore it trying to remove asahi with disk utility...
<tpw_rules> but that was really my fault
<ComradeMisato[m]> i see
riker77_ has joined #asahi
riker77 has quit [Ping timeout: 480 seconds]
riker77_ is now known as riker77
PhilippvK has quit [Ping timeout: 480 seconds]
marvin24 has joined #asahi
marvin24_ has quit [Ping timeout: 480 seconds]
kov has quit [Quit: Coyote finally caught me]
pyropeter1 has joined #asahi
PyroPeter_ has quit [Ping timeout: 480 seconds]
boardwalk has quit [Quit: Ping timeout (120 seconds)]
boardwalk has joined #asahi
amarioguy has quit [Remote host closed the connection]
amarioguy has joined #asahi
the_lanetly_052__ has joined #asahi
rootbeerdan has joined #asahi
jluthra has quit [Remote host closed the connection]
jluthra has joined #asahi
Chainfire has joined #asahi
<jannau> kettenis: it looks like they moved the input controller to the SoC. It looks like it's now a standard ASC coprocessor so it might use rtkit, otoh it has an interrupt and regs so it might be accessible directly
<jannau> events appear to be still HID
eroux has joined #asahi
rootbeerdan has quit [Ping timeout: 480 seconds]
the_lanetly_052__ has quit [Ping timeout: 480 seconds]
rootbeerdan has joined #asahi
MajorBiscuit has joined #asahi
os9 has joined #asahi
os has quit [Read error: Connection reset by peer]
eroux_ has joined #asahi
eroux has quit [Read error: Connection reset by peer]
bps2 has joined #asahi
voliteon has joined #asahi
MajorBiscuit has quit [Ping timeout: 480 seconds]
MajorBiscuit has joined #asahi
<voliteon> I only just learnt of Asahi Linux. Love the idea!
MajorBiscuit has quit [Ping timeout: 480 seconds]
MajorBiscuit has joined #asahi
MajorBiscuit has quit [Ping timeout: 480 seconds]
<marcan> dockchannel is trivial
<marcan> hopefully it's similarly trivial :)
<marcan> I guess they shoved the keyboard controller into the main SoC now, sounds like something they'd do
<j`ey> we still need SPI for mesa and something else, so we cant not upstream that :P
MajorBiscuit has joined #asahi
MajorBiscuit has quit [Ping timeout: 480 seconds]
MajorBiscuit has joined #asahi
ChaosPrincess has quit [Quit: WeeChat 3.5]
ChaosPrincess has joined #asahi
MajorBiscuit has quit [Ping timeout: 480 seconds]
Ry_Darcy has quit [Remote host closed the connection]
eroux_ has quit []
eroux has joined #asahi
<nsklaus_> i've heard some feedback saying asahi makes the laptop to run hotter than macos, i was wondering what part of the planned future work is supposed to correct that ? CPU deep idle maybe ? or is it something else ?
<nsklaus_> ( to note, i haven't installed asahi myself yet, i'm waiting for sound speaker support to land, as having sound is important for me )
<j`ey> the CPU doing software rendering doesnt help either, i guess
<nsklaus_> .. so i cannot confirm first hand that it does indeed run hotter ..
<ChaosPrincess> it does
<voliteon> interesting
<nsklaus_> ChaosPrincess: thanks for confirmation
<Dcow[m]> It is, but yeah - CPU is constantly consumed by software rendering, so much less idle mode so it is hotter
<Dcow[m]> Can't say drastically, but yeah
<Dcow[m]> prays for lina here ;)
<nsklaus_> it may be interesting to locate where the heat zone are on the laptop, physically speaking. it might be an indication of what part exactly is not properly handling hardware ?
<ChaosPrincess> its the soc
<nsklaus_> ah i see, so gpy driver, cpu deep idle, and such will probably improve on that situation then ?
<nsklaus_> *gpu
<ChaosPrincess> it is likely to do so, yes
<Dcow[m]> also, afaik, some pcie sleep issues here, so count this too
<Dcow[m]> don't really remember which exactly, but something pcie or wifi related
<nsklaus_> i have seen the lina's challenge video ;) the 3months caesar vs cleopatra challenge, it was kind of funny ;) maybe when the 3 months date is reached there could be substantial progress on that front too then ?
<nsklaus_> the "three meow" ;)
<nsklaus_> there's pcie sleep isssues too i read ?
<nsklaus_> dologne[m]
<nsklaus_> err tab error
<nsklaus_> Dcow[m]
<j`ey> yes the wifi driver crashes when trying to sleep
<nsklaus_> interesting.. i haven't said so before, so i take the opportunity to say congrats on the first release, i read good feedback about it so far, wish you all courage for the remaining work ahead
rootbeerdan has quit [Ping timeout: 480 seconds]
kov has joined #asahi
eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
eroux has joined #asahi
rootbeerdan has joined #asahi
MajorBiscuit has joined #asahi
rootbeerdan has quit [Ping timeout: 480 seconds]
rootbeerdan has joined #asahi
rootbeerdan has quit [Read error: Connection reset by peer]
rootbeerdan has joined #asahi
citizen1[m] has left #asahi [#asahi]
rootbeerdan has quit [Read error: Connection reset by peer]
rootbeerdan has joined #asahi
Ry_Darcy has joined #asahi
Ry_Darcy has quit [Remote host closed the connection]
opticron has quit [Ping timeout: 480 seconds]
rootbeerdan has quit [Remote host closed the connection]
rootbeerdan has joined #asahi
bps2 has quit [Remote host closed the connection]
rootbeerdan has quit [Ping timeout: 480 seconds]
eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
LinuxM1 has joined #asahi
<nsklaus_> i wonder if macbook air m2 will heat mor than m1, i mean even using macos ?
rootbeerdan has joined #asahi
eroc1990 has quit [Quit: The Lounge - https://thelounge.chat]
rootbeerdan has quit [Ping timeout: 480 seconds]
<psydroid[m]> hopefully it will, so we'll have a higher chance of surviving next winter
<nsklaus_> ;)
<nsklaus_> and do plancha cooking, like on intels ? ;)
<psydroid[m]> yes :D
eroc1990 has joined #asahi
millenialhacker has joined #asahi
MajorBiscuit has quit [Ping timeout: 480 seconds]
<povik> mps: why are you not running a sound server? :-p
<povik> (not a serious questin, but a question about your use-case did arose on the list: https://lore.kernel.org/asahi/YqIhYPBpVcvz9iLQ@sirena.org.uk/#t )
LinuxM1 has quit [Quit: Leaving]
<mps> povik: I don't like them, they are more problem than useful
<mps> setting alsa directly is more convenient, simple and stable, ime
<Dcow[m]> povik: did admac get merged?
<j`ey> dont think so
<kettenis> even OpenBSD has a (rather minimal) sound server
<j`ey> oh nice, i found v3, not v4
<mps> povik: reading ML messages I think you are correct, i.e. your reasoning but I'm far from expert in the field
<j`ey> Dcow[m]: cant find it on vinods git :/
<j`ey> (oh applied today, so probably just not pushed)
derzahl has joined #asahi
<povik> mps: well in the end it's not an issue of correctness but of being worth the added complexity...
<povik> yeah, couldn't find merged admac too
<povik> i have a fix for it already
<Dcow[m]> I guess fixes are easier to get merged
<povik> sure they are
<povik> want to insert the right Fixes: tag though
<sven> depending on the maintainer they might even just squash the fix in
<sven> but anyway, nice job on ADMAC :-)
<Dcow[m]> within current window?
<Dcow[m]> yeah, right! congrats!
<sven> I’ve seen fixes squashed in as long as they’re only on -next since some maintainers don’t mind rebasing there
<sven> cant squash anything after the PR is sent to Linus ofc
<povik> my experience is that fixes weren't squashed
<povik> thanks, good it finally got merged
<povik> :)
<j`ey> povik: and macaudio looks like it got some good feedback
<povik> :p
<sven> I think it’s rather rare, I’ve only seen it once or twice
<sven> iirc for something small in pcie, but it’s been a while
<kettenis> povik: yes some changes are going to be needed
<povik> ah, the interrupts= thing i bet
<kettenis> that needs to be rolled into the asahi linux branch sooner than later as well
<povik> how is your driver so short?!
<povik> less than half the no. of lines of the linux one
<povik> > sooner than later
<povik> ah, i see you've got to know me :-p
<mps> povik: so, using plain alsa is more complex than using sound server? I don't undertand quite well
<povik> yes, in case you want some of the features the sound server would otherwise take care of implemented in kernel
<povik> here, the speakers/headphones switching based on jack detection
<mps> I use acpid to detect jack plugs in and switch output in script with amixer
<derzahl> whoa, you guys are talking about audio? i just came here to ask what I would need to do to make noises come out of my macbook air speakers, even at the risk of blowing them out
<mps> derzahl: you have to edit DTS file for air and remove 'disabled' line there, and rebuild DTS and add them to m1n1+u-boot
<derzahl> there _seems_ to be a working driver. the audio hw is detected, controls are all there in pavuctl and alsamixer. but..silence
<derzahl> mps: gotcha! thanks
<derzahl> so u-boot is what loads the .dtb?
<mps> derzahl: no, m1n1 loads it
<kettenis> no, m1n1
<j`ey> its just that you m1n1 is combined with u-boot and the dts in stage 2
<derzahl> what if i just added a "devicetree" line in grub? wouldnt that override?
<kettenis> povik: the driver is short because it just does what I need for playing back audio
<mps> derzahl: this doesn't work
<kettenis> would almost certainly fail
<povik> derzahl: the reason that can't work is that there are things that need to be filled into the devicetree by m1n1, and grub won't put those in
<derzahl> j`ey: so remove line 122 completely? or set status = "enabled";
<derzahl> ?
<povik> you can just remove it
<povik> i think status="okay" would work too?
<derzahl> ok, will remove then
<mps> usually will do
<j`ey> povik: I think jannau found a bug in our device trees because we had status="ok", which is the same as disabled :P
<derzahl> can I add the dtb to m1n1 from the OS or do I need to do it at boot? I havent played around with it much yet
<mps> povik: input events have these two signals for jack, SW_HEADPHONE_INSERT and SW_MICROPHONE_INSERT but I think you know this
<povik> j`ey: yeah, i can see how that would happen
<povik> but i thought status="ok" is... ok?
<povik> if we can take eli's word for it: http://billauer.co.il/blog/2017/02/linux-dts-dtsi-status-ok/
<j`ey> povik: probably just misremembered what the bug was then
<povik> mps: i don't! didn't need to know it so far, maybe i will
<mps> ah, ok. I use input events for a lot of things
<kettenis> it needs to be "okay", "ok" isn't recognized by some devicetree consumers
<derzahl> j`ey: ok, and I think m1n1-update has a pacman hook that runs automatically, right? I recall it running when I installed a new kernel. so maybe I can just comment out line 112 in the dts, rebuild the dtb. then reinstalling the kernel should kick off m1m1-update
<jannau> the keyboard was broken in u-boot on m1 pro/max because linux accepts the non standard 'status = "ok";' but u-boot doesn't
<kettenis> (and "ok" isn't mentioned in the devicetree specificatin)
<derzahl> or change to status="okay"...maybe commenting out wont work it seems
<mps> derzahl: I just commented it
<j`ey> derzahl: that might work? or just run the update-m1n1 script manually.. just make sure you back up your m1n1.bin on the EFI/ESP partition
<mps> derzahl: https://tpaste.us/oOyR
<j`ey> povik: see, I was right! uboot doesnt accept "ok"!
<povik> yeah, and i hate it :-p
<povik> does anyone here know C?
<povik> why do i need this patch: https://tpaste.us/Kenq
<povik> for context
<povik> #define FLAG_DESC_NOTIFYBIT(16)
<povik> uh it ate the tabs
<povik> #define FLAG_DESC_NOTIFY BIT(16)
<povik> what rule does apply here that the numeric constant is an unsigned long argument to the variadic function?
<j`ey> #define BIT(nr) (UL(1) << (nr))
<povik> thanks
<povik> ok, now that i understand it i can send it
<derzahl> ok, all ready to go with the new $ESP/m1n1/boot.bin
<j`ey> derzahl: save the old one
<derzahl> speaks wont blow before I get booted into gnome and try to test audio will they?:)
<povik> shouldn't blow until that point :p
<derzahl> and re: update-m1n1, am I correct in my reading, that only the dtb file from the last installed kernel will be loaded?
<j`ey> arch only has one kernel at a time (apparently..)
<derzahl> would be nice to be able to load on a per kernel basis. not sure how often the dtb changes...
derzahl has quit [Remote host closed the connection]
<sven> would also be annoying to implement
<sven> the dtb ideally is backward and forward compatible *for things that are upstream*
<sven> for everything else, well, it’s called alpha for a reason
derzahl has joined #asahi
<kettenis> one approach for making modifications to a device tree is using overlays
<kettenis> u-boot can do that I believe (but I've never used that myself)
<derzahl> ok assholes im back. my speakers are blown my ears are ringing and my dick fell off. I need addresses to send to me lawyer RIGHT NOW
<derzahl> jk. sound works beautifully so far:)
ciggi has quit [Ping timeout: 480 seconds]
<j`ey> just keep the volume low
<kettenis> vlad the bad, kremlin, moscow, russia ;)
<povik> yeah, when you write in caps i read it as shouting
<derzahl> j`ey: so is the only problem that there is no proper limiter? shouldnt that be fairly easy to code for?
<povik> yeah j`ey
<povik> why isn't that done already?
<j`ey> derzahl: povik is lazy
<povik> ah, busted
<mps> kettenis: iirc there were some efforts to load dtb overlays on running systems but I don't if it ever materialized to something to even test
ciggi has joined #asahi
<eramon[m]> Hi, I was wondering if the binaries used by the asahi installer (kernel + dtb) are available somewhere to download?
<j`ey> eramon[m]: theyre in the asahi pacman repo i suppose
<eramon[m]> Do you know the url of the repo?
<eramon[m]> Thank you :)
<derzahl> well thanks for the tips. maybe ill give it a try loading from grub instead of m1n1? I made a grub script that will extract the dtb from each kernel and create a "devicetree" line in the grub.cfg when it is generated
<derzahl> for another aarch64 laptop i have
<j`ey> derzahl: you probably wont even get video output if you do that :P
<derzahl> j`ey: ill play around with it when i have the chance a report back
<derzahl> btw, anyone know who is working on the fedora port? Anyone from redhat or just the community?
Moprius has joined #asahi
the_lanetly_052__ has joined #asahi
derzahl has quit [Remote host closed the connection]
<sven> loading the DT from grub is a bad idea in general
<sven> see https://github.com/AsahiLinux/m1n1/blob/main/src/kboot.c for all the things that have to be patched
<sven> grub won’t do any of that which will break many things
Moprius has quit [Remote host closed the connection]
Moprius has joined #asahi
the_lanetly_052__ has quit [Ping timeout: 480 seconds]
Gaspare has joined #asahi
vdanielmo has joined #asahi
<MichaelMesser[m]> https://twitter.com/never_released/status/1534889394242572288?cxt=HHwWgMC-lbPxgs0qAAAA Apparently, no 32 bit. Has some tried something like i386_set_ldt that Wine uses to run 32 bit Windows apps on M1?
vdanielmo has quit [Quit: vdanielmo]
Moprius has quit [Quit: Konversation terminated!]
opticron has joined #asahi
Gaspare has quit [Quit: Gaspare]
derzahl has joined #asahi
<derzahl> noticed tons of commits on m1n1:master
<derzahl> most i dont understand....dont suppose theres a menu?:)
<j`ey> menu?
<povik> you mean like a boot menu?
<derzahl> im back to trying to get zfsbootmenu working
<derzahl> so yes
<j`ey> m1n1 just boots a payload, no menu
<tpw_rules> no, there's no input
<tpw_rules> zfsbootmenu working is between you and u-boot
opticron has quit [Read error: No route to host]
<derzahl> gotcha, keep mixing up m1n1 and u-boot
opticron has joined #asahi
<derzahl> i can boot it from grub. and i booted the efi once from u-boot
<j`ey> hmm zfsbootmenu uses kexec, so hopefully it wont start the other cores
<derzahl> the interface is pretty f'd up. keyboard input often slows to a crawl or doesnt echo
<tpw_rules> there was a problem with that in u-boot due to a ludicrous timer interal
<derzahl> j`ey: other cores? why would we not want them to start?
<tpw_rules> but that was fixed
<tpw_rules> does your keyboard work well in u-boot and grub?
<povik> derzahl: kexec won't work then
<derzahl> tpw_rules: yes
<j`ey> derzahl: until we have psci, we cant stop/start cores. which kexec needs. but if zfsbootmenu doesnt start the cores it should be ok
<derzahl> i have not been ableto get it working so...maybe kexec is why.hm
<tpw_rules> there was that m1n1/asahi/whatever alternative that was just a chain of kexecs so someone has gotten something working
<j`ey> kexec is after youve selected a kernel
<j`ey> derzahl: so if you havent gotten to zfsmenu at all, thats not the issue
<derzahl> Ive gotten to the menu
<j`ey> oh
<derzahl> but it gets all garbly, so im hoping to get better output...make sure its not a mistake i made in config
<derzahl> im new to zfsbootmenu. just got it set up on an old x86 macbook air
<derzahl> seemed like th best way to get my encrypted zfs root booted on asahi...i dunno
<derzahl> im open to other suggestions. but i would like boot env's to work
jackbijou[m] has joined #asahi
derzahl has quit [Remote host closed the connection]
opticron has quit [Ping timeout: 480 seconds]
derzahl has joined #asahi
opticron has joined #asahi
<derzahl> yeh, got zfsbootmgr running cleanly now. just straight says that it 'cannot load' the kernel
<derzahl> any alternative suggestions?
<j`ey> derzahl: debug it a bit?
<j`ey> or maybe theres a way to get verbose errors