<ktz_[m]>
<tpw_rules> "hold option in the boot picker..." <- (y) good info
<tpw_rules>
iirc it's in the release post
BenFE has joined #asahi
<BenFE>
i forgot to tell y'all bc i was busy ricing but my install was a success! it's pretty insane how straightforward it is
<BenFE>
im not super familiar with linux audio, but i tried using the headphone jack and an external dac that i have, and i couldn't get any sound to come out
<BenFE>
and the dac is recognized by the computer
creechy has quit [Ping timeout: 480 seconds]
<BenFE>
has anyone had any luck with the headphone jack or an external device yet?
<tpw_rules>
which system do you have?
<Adie[m]>
Headphone jack works on Xorg on my MacBook Air
<BenFE>
im running a macbook pro 13" with the default plasma desktop environment
<BenFE>
but i also tried it in gnome with wayland
<Adie[m]>
Worked in Awesome WM
<Adie[m]>
Not in GNOME 41 Wayland
<BenFE>
interesting
<Adie[m]>
Don't remember about GNOME 41 Xorg
<Adie[m]>
Had to uninstall asahi
<Adie[m]>
not enough space, so I'm reinstalling it with more space this time
<BenFE>
ah
<BenFE>
well i'll go try a few other environments and see what i find
BenFE has quit [Quit: Konversation terminated!]
BenFE has joined #asahi
<BenFE>
yup sound works fine on gnome xorg
<BenFE>
lol
creechy has joined #asahi
al3xtjames has quit [Quit: Ping timeout (120 seconds)]
al3xtjames has joined #asahi
<Adie[m]>
unrelated to asahi but my god is macports slow. no idea why, it just is :/
<BenFE>
well macports compiles everything so yeah it's pretty annoying
<pat42smith>
Hello, all! I just installed Asahi on my Mini... thanks for all the hard work.
kameks has joined #asahi
<Adie[m]>
Quite nice, isn't it?
<BenFE>
nice! welcome to the cool kids table!
<Adie[m]>
Even without GPU!
<Adie[m]>
well, GPU accel
<pat42smith>
There were a couple of issues. First, when installing, after doing the boot picker part and the security stuff, when the system rebooted, the display was just blank.
<BenFE>
oof
<pat42smith>
After an hour or so, I shutdown with the power button and then restarted, and it came up into Linux.
chadmed has joined #asahi
<pat42smith>
So something strange happened there, I don't know what. And I don't know if there was more configuration I missed hiding under that blankness.
<robinp>
pat42smith: I had the same issue - I swapped mointors and it worked (I added an issue in the installer), but your saying it just came good after waiting a while ?
<pat42smith>
No, I pressed and held the power button until the system shutdown, and then started the system again. That fixed the blankness.
<pat42smith>
BTW, this was on my second install. My first install, the same thing happened, but I realized it was because I was using DisplayPort. For the second install, I had HDMI all the time.
<robinp>
pat42smith: i had tried restarting a few time (and booting from the boot picker) - but didn't have any luck with the Lenovo monitor i was trying to use.
<BenFE>
interesting
<Adie[m]>
https://pastebin.com/raw/JgLzHvEU Not really relevant to asahi but it is stopping me from running the installer. Mystery error pops up when trying to run some commands.
<pat42smith>
robinp: I'm not needing to use the boot picker - it boots into Asahi by default.
<BenFE>
looks like some of your libs are compiled for x86 somehow, but that's very strange
<Adie[m]>
couldn't actually find that specific library file/binary/whatever
<BenFE>
hmm
<pat42smith>
Second issue: I have a 4K display, but the resolution being used is 1920x2160 - so everything is distorted.
<pat42smith>
In "Display Configuration" under settings, it says the monitor only supports that one resolution. Weird.
<BenFE>
weird
<chadmed>
we do not yet have support for the display controller/proper modesetting
<chadmed>
we are using simpledrm
<BenFE>
so any ideas for getting audio to work on plasma if it works fine on xorg?
<robinp>
does the mac studio have the same DP2HDMI as the mini ?
nathan has joined #asahi
<pat42smith>
chadmed: Is there any documentation on how to use or control simpledrm? I'm not finding any in my first Internet searches...
nathan has left #asahi [WeeChat 3.4.1]
BenFE has quit [Quit: Konversation terminated!]
BenFE has joined #asahi
user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<chadmed>
you cant control it, it just takes control of whatever framebuffer is set up by the platform firmware
<chadmed>
for proper control over monitors and stuff you just have to wait for display controller support to land in linux-asahi
<BenFE>
fya for some reason restarting the pulseaudio daemon got the audio working on plasma kde ¯\_(ツ)_/¯
user982492 has joined #asahi
<chadmed>
what machine, and out of the headphone jack or internal speaker(s)?
<BenFE>
im actually using an external dac, but im assuming the headphone jack would work as well
<chadmed>
oh well yeah of course thats going to work, its just a UAC device and we have USB support
<pat42smith>
chadmed: Thanks. I'll wait, then.
<BenFE>
well for some reason i have to kill pulseaudio for it to work on plasma
<chadmed>
probably something flaky in its udev module. try migrating to pipewire and pipewire-pulse
<BenFE>
k thanks
<chadmed>
pulse used to dislike my USB DAC on my amd64 machine fwiw, i dont think its a problem endemic to these machines
<chadmed>
i switched to pipewire-pulse and it stopped happening
<kode54>
pulse disliked my built in DAC, and the fix to fix that broke external DACs for me
<kode54>
pipewire-pulse has no such problem
<kode54>
pipewire also has working bluetooth codecs, unlike pulseaudio
<kode54>
pulseaudio's current state of bluetooth is, SBC, and AAC/aptX/LDAC that are dependent on unmerged changes to gstreamer
user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<kode54>
and that popular AUR package for a bluetooth module for pulseaudio that imports the libraries directly, is no longer compatible
BenFE-2 has joined #asahi
<BenFE-2>
well pipewire did the trick, thanks so much!
<kode54>
good
<kode54>
and incidentally, if you've got one of the systems with speakers for the future
BenFE has quit [Ping timeout: 480 seconds]
<kode54>
the current speaker DSP scripts only work with pipewire-media-session, not wireplumber
BenFE-2 has quit []
<kode54>
oh darn, they left
BenFE has joined #asahi
<BenFE>
sick
<BenFE>
and to think that when i woke up this morning i had no idea that linux would ever be bootable on my mac lol
<kode54>
welcome back
<BenFE>
thanks lol. i did a sudo reboot before disconnecting from irc :)
<kode54>
I was gonna say
<kode54>
the DSP scripts
<BenFE>
yeah im super excited for that
<kode54>
the one that chadmed is working on
<kode54>
requires pipewire-media-session at this point
<BenFE>
ah cool
<kode54>
I wondered why my own attempt to use virtual surround downmix on pipewire failed to work on Arch (on a not-asashi machine)
<kode54>
probably the same problem with Wireplumber
<BenFE>
yeah linux audio is kinda funky
<kode54>
computers in general are funky in different ways, no matter where you go
<BenFE>
of course
<kode54>
you just pick whichever flavor you prefer
<kode54>
and sometimes you have to mix it up and use different OSes or computers regularly
<BenFE>
im just curious to see how the linux laptop lifestyle will hold up with the daily college grind
<kode54>
it currently holds up less than macOS does, battery wise, from what I've heard
<kode54>
but that will change
<kode54>
still better than Intel
<BenFE>
yeah for sure
<BenFE>
i used to use a few of the older macbooks and they were so terrible with battery life
<kode54>
oh, and if you use Go at all, it compiles like 5x as fast under Linux than macOS on the same machine
<BenFE>
ooh
<kode54>
it does the same under a Linux VM on macOS too
<BenFE>
im normally working in js/ts for full stack stuff, but my job this summer is probably gonna be mostly working with Go
<kode54>
a lot of this has to do with how it interacts with the OS
<kode54>
under Linux, Go uses syscalls directly
<kode54>
under macOS, it must go through libc
<BenFE>
oh interesting
<kode54>
node is available for alarm right now too
<kode54>
but Electron isn't even packaged by upstream alarm
<kode54>
Electron is in the same boat as Chromium
<BenFE>
right
<BenFE>
that's what i was guessing
<kode54>
oh well, I use Firefox from Linux anyway
<kode54>
Skype will be fun to get, since I use that regularly, but that's all on Microsoft
<BenFE>
yeah a couple of my projects are electron apps, but i'm not really rushing to add support for arm64 linux lmao
<chadmed>
yeah wireplumber is a pseud, it tries to be way smarter than it actually is and almost always breaks something
<BenFE>
nice
<chadmed>
it just does not route the filter chain to the output because it thinks you dont "want" to do that
<BenFE>
do you guys know if there are any packages that will decrease the brightness of the video stream (essentially put a black filter with variable opacity over the screen)? I once did that on Windows when it wouldn't talk to a monitor properly and it worked well enough to save my eyes.
<BenFE>
although i know it's not super power efficient lol
<nicolas17>
BenFE: I think you can set the backlight brightness from macOS, and it will persist when you boot back to Linux
<BenFE>
yeah that is true, im just lazy :))))))
creechy has quit [Ping timeout: 480 seconds]
xqz has joined #asahi
<kode54>
oh yes
<kode54>
and I know the cheapass workaround to no bluetooth
<kode54>
use the bluetooth adapter I bought for my hackintosh back in the day
<kode54>
it's a part I bought off digi-key for like $26 including shipping
<kode54>
bt 5.0 adapter that has 100% embedded firmware
<kode54>
it works through the fully generic Linux bluetooth driver
<kode54>
or macOS, or Windows
<kode54>
not the workaround anyone wants, because it's dodging the real issue
<kode54>
like, nobody wants to have to plug in external hardware to replace unsupported internal functionality
<BenFE>
oh i think there's one of those laying around at my parents' house
<kode54>
Laird branded
<kode54>
it's designed to be a sample component for developing for their component module
<kode54>
but it's also a convenient easily integrated adapter
<kode54>
since they sell fairly high quantities of the USB module form factor
<kode54>
well, by "fairly high" I mean, hobbyists should have no trouble getting one most of the time, since Digi-Key stocks several thousand at a time usually
<kode54>
definitely not mass market
creechy has joined #asahi
creechy has quit [Ping timeout: 480 seconds]
PhilippvK has joined #asahi
phiologe has quit [Ping timeout: 480 seconds]
user982492 has joined #asahi
Guest282 is now known as go4godvin
<BenFE>
is there no xmonad package for arm?
<tpw_rules>
there is on nixos
<tpw_rules>
i'm reasonably sure
<BenFE>
what aur manager should i use?
<chadmed>
git :P
<tpw_rules>
nix?
<tpw_rules>
(also :P)
<BenFE>
lol
<nexus7556>
yay is my favorite aur helper
eotdlt^ has joined #asahi
creechy has joined #asahi
artemist has joined #asahi
THX1984 has quit [Quit: Leaving]
creechy has quit [Ping timeout: 480 seconds]
<chadmed>
hmmm
<chadmed>
the studio display has a large speaker array
<chadmed>
might be something for me to look into once we have thunderbolt up and running
BenFE has quit [Quit: Konversation terminated!]
kov has quit [Quit: Coyote finally caught me]
kov has joined #asahi
BenFE has joined #asahi
<BenFE>
crap i ran out of space on my linux partition
<BenFE>
im confused because disk utility shows that the linux partition is only 2.5 GB
<chadmed>
thats not the root partition, do not use the graphical disk utility
<tpw_rules>
yeah i thought there was a script that automatically expanded the partition and resized it on boot
<BenFE>
oh sick
<tpw_rules>
i guess something went a bit wrong with it
<BenFE>
so im all good?
<tpw_rules>
should be
<BenFE>
sick
<BenFE>
thanks so much
<tpw_rules>
try nixos sometime ;)
<BenFE>
mayb
<BenFE>
im now remembering that i did something something similar on AWS, but it was a while ago and i just cluelessly followed a guide
BenFE has quit [Quit: Konversation terminated!]
user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Ry_Darcy has joined #asahi
rominou66 has quit [Remote host closed the connection]
rominou66 has joined #asahi
nicolas17 has joined #asahi
user982492 has joined #asahi
nicolas17 has quit []
juancri has quit [Quit: WeeChat 3.4.1]
<kode54>
god damn
<kode54>
I didn't think Max Tech could get any stupider
<kode54>
oops, offtopic
<kode54>
I'll take it there
ciggi_ has quit [Read error: Connection reset by peer]
creechy has joined #asahi
ciggi has joined #asahi
CarlosDiazPlaza[m] has joined #asahi
<CarlosDiazPlaza[m]>
Hello
CarlosDiazPlaza[m] is now known as Carlitos[m]
<Carlitos[m]>
Hey
creechy has quit [Ping timeout: 480 seconds]
user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<marcan>
tpw_rules: there's an fstab config to autogrow the fs, yes; it checks on every boot
<marcan>
so if they expanded the partition and rebooted that's all it takes
<marcan>
you can turn that off in /etc/fstab, it's a standard systemd thing
<marcan>
but it won't expand the partition for you, just the filesystem
<marcan>
the partition is created at the size you specify by the installer
<marcan>
so I guess they picked a smaller size then wanted to expand it later from linux
leah2 has quit [Ping timeout: 480 seconds]
ciggi has quit [Ping timeout: 480 seconds]
<kode54>
cool
<kode54>
my monitor just blinked off for like two seconds, then came back up
<kode54>
I'm so happy it didn't kill the session
romain_ has joined #asahi
rominou66 has quit [Ping timeout: 480 seconds]
Guest288 is now known as Skirmisher[m]
user982492 has joined #asahi
romain_ has quit [Ping timeout: 480 seconds]
pat42smith has quit [Remote host closed the connection]
leah2 has joined #asahi
LinuxM1 has joined #asahi
<LinuxM1>
hello, the battery icon has disappeared, it is not detected. i think it's a bug. how can i restore the vision of the battery icon? I went to the tray settings and put the check mark on "always visible" but it is not shown
<chadmed>
reboot
<LinuxM1>
I rebooted several times is not showing
hir0pro has joined #asahi
<LinuxM1>
I also tried plugging in the power supply to see if it was showing, and still nothing
<LinuxM1>
I think it is not detected at the hardware level. perhaps resulting from some update or installation of programs. Until yesterday it was shown correctly, then I remember that it had reached critical level and I then clicked on the notification to remove that message. from that moment it is no longer shown
<j`ey>
lsmod | grep macsmc
<LinuxM1>
macsmc_reboot 65536 0
<LinuxM1>
macsmc_hid 65536 0
<LinuxM1>
tano@tano-linux:~ -$
<LinuxM1>
macsmc_power 65536 0
<LinuxM1>
rtc_macsmc 65536 0
leah2 has quit [Ping timeout: 480 seconds]
<j`ey>
cat /sys/class/power_supply/macsmc-battery/capacity (that path is slightly wrong, but im doing it from memory)
<LinuxM1>
I can't always give the command to check the battery status. at the moment it gives me the value "69"
<LinuxM1>
I would like to have the battery icon back like all other icons
hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<marcan>
yeeeah.
<marcan>
the good news is doing a DCP init is very fast, and setting the mode to the current mode does not cause a cycle/flicker, and we don't reinit the FB when the mode did not change
hir0pro has joined #asahi
<marcan>
so that means I can ship something to update-m1n1 to pull the display= config from /etc/m1n1.conf or whatever, and ship a default config file with "display=auto" in it
<marcan>
and that will fix the display in stage 2 for people with issues in stage 1, including bad mode selection, and hopefully not really affect anyone else
user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<j`ey>
marcan: stage2 m1n1 to the rescue again
<marcan>
yup
<marcan>
best decision I ever made
<j`ey>
^_^
<mps>
ah, didn't know /etc/m1n1.conf is thing
<marcan>
it isn't
<marcan>
not yet
<jannau>
marcan: argh, I started working on the same functionality, I have a proptoype for allocating a larger framebuffer. it will be too small for 4k on the mac mini
<marcan>
yeah, I noticed
<marcan>
also oops, sorry :<
<jannau>
and on the mac studio it is just large enough for 1920x1080
<marcan>
hm, if it were 1920x1200 I'd say we can live without reallocation for now
<jannau>
no problem
<marcan>
but 1920x1080 is a bit ew, 16:10 monitors are a thing
<marcan>
do we have (unmapped) reserved VRAM for larger FBs, or do we need to steal some of main RAM?
<jannau>
it's certainly too small for 1920x1200
<marcan>
I guess the sane thing to do is to give up on the "search the DART for the framebuffer" business and just carve our own FB off the top of RAM unconditionally, though it would be nice to somehow figure out how to unmap those leftover IOVAs so they don't pollute the DART unnecessarily
<jannau>
I haven't looked yet, the annotated "/vram" is too small
<marcan>
jannau: looks like the preallocated fb is outside /vram?
<j`ey>
what is /vram if it's all unified memory?
<marcan>
just memory
Glanzmann has joined #asahi
<marcan>
usually just some block set aside for something special
<marcan>
0x9e3a18000..0x9e4f18000 is what I get for /vram
<Glanzmann>
jannau: If you have the patch with the bigger vram, please send it to me. Ry Darcy would like to try it.
<marcan>
while my FB is at 0x9e6213000
<jannau>
marcan: /vram is mapped in dcp/disp0 dart though
<marcan>
Glanzmann: you really need to stop asking people for patches that aren't done yet, especially when we literally just had a merge conflict here...
<marcan>
jannau: yeah, so I wonder what it is
<marcan>
does it contain anything?
<jannau>
I don't think I've ever compared it to the framebuffer base in bootargs
<marcan>
wait hold on
<marcan>
oh I'm dumb, sorry
<marcan>
it *is* /vram
<marcan>
I was looking at the wrong buffer
<jannau>
I haven't checked yet, it seemed so obvious that it should be the frame buffer that I ever investigated
<marcan>
then yeah, I think that's just the framebuffer
<marcan>
it's the same base
<marcan>
/vram is the bootfb area
<jannau>
ok
<marcan>
so that's easy then, make display.c use that if it's available and the new mode fits in it, otherwise allocate, map, and clear a new one before the swap, pulling from the top of RAM (which nothing else does, so that should be safe)
<marcan>
and unmap the old FB *after* the swap completes, regardless of what direction we go in
<marcan>
actually we might want to just outright mutate the ADT at that point, and point /vram at the new location, and just accept the loss of the old vram
<marcan>
because then chainloading xnu will work as intended
<Glanzmann>
marcan: I was not asking for a broken patch, I asked jannau for the patch once he finished, I litterary just send you an email about it 10 minutes ago.
<marcan>
you didn't say "once it's done", you said "if you have"
<Glanzmann>
marcan: I have to work on my english then.
Tano70 has joined #asahi
m6wiq has joined #asahi
eotdlt^ has quit [Remote host closed the connection]
<bluetail[m]>
can I upgrade to macOS 12.3 and will asahi still work?
<roxiun[m]>
Yes
<marcan>
you have to upgrade to 12.3 to install in the first place
<roxiun[m]>
You need to upgrade to 12.3
<roxiun[m]>
* You *need, * need* to
<Tano70>
and when apple upgrade to 12.4/X asahi still work?
<marcan>
yes
<marcan>
at least in principle
<marcan>
the system is designed to be backwards compatible, but I can't guarantee we won't run into a corner case because obviously we can't talk to apple directly about what the expectations are
<marcan>
but if something breaks it should fail gracefully, not stop everything from working
<Cy8aer[m]>
must then the stub be upgraded too?
<marcan>
no
<marcan>
not unless something goes wrong with the stub which would be very unlikely since it doesn't really try to do anything complicated
<marcan>
in fact the stub will remain at 12.3 for the foreseeable future
<marcan>
until either the next machines are released or we decide to upgrade for some important reason
<Tano70>
ok thanks marcan
Tano70 has quit [Quit: Leaving]
m6wiq has quit []
<Sobek[m]>
Also, can you update the stage 2 stub to using more recent firmware etc, or must stage 1 and 2 be based off the same macOS version ?
<j`ey>
stage 1 and 2 are just m1n1
<j`ey>
I mean, there's only 1 stub, and thats for stage 1
<Sobek[m]>
Ah yes !
<Sobek[m]>
Isn't there a firmware bundle that's derived from a specific version of macOS (for ABI reasons)
<chadmed>
yeah and thats based on 12.3 currently
<chadmed>
the installer just gets the fw blobs from where macos keeps them and writes them to the ESP. we arent allowed to redistribute them ourselves
<Sobek[m]>
(It grabs them by streaming the recovery bundle, so as to be independent from the macOS version on the computer too)
Glanzmann has quit [Quit: leaving]
<Sobek[m]>
If at some point you need to update to the firmware bundle from say macOS 12.5 ou 13.0, will you switch only new installation and keep supporting the old installs ? Or will you write a utility that from linux streams the new OS, extracts the rights bits and dumps them at the firmware location ?
kameks has quit [Ping timeout: 480 seconds]
sjbtrn[m] has joined #asahi
<pparker[m]>
Hey all, I just installed the desktop version on my Mac mini m1. But the screen shows now "no signal" on my Xiaomi Mi Curved 34° monitor. It works fine on my tv screen. Any idea why?
<j`ey>
if you feel confident in following the first step listed there
<pparker[m]>
Oh great. I will do that. Thank you!
<bluetail[m]>
<j`ey> "pparker: https://github.com/..."; <- Can we have a monitor compatibility sheet?
<chadmed>
that would be pretty unmaintainable tbh
<chadmed>
considering this is not going to be a problem for much longer i dont think its worth the effort
<bluetail[m]>
You are right but I still assume some monitors are inherently NOT fully compatible with m1 macs
<bluetail[m]>
or in general with macs
<chadmed>
thats not really how that works though
<bluetail[m]>
ok...
<bluetail[m]>
how does it work?
<chadmed>
HDMI and DP are very standard interfaces. once we have full control over the DCP and framebuffer memory from linux this will literally just not ever be a problem
<qiuren[m]>
Maybe at least 1080p works? We can write the workaround in the docs.
<chadmed>
and before loading the kernel, m1n1 will init the DCP at whatever mode we give it from configuration
<chadmed>
like the only reason this is a problem is because we cant yet control the DCP and rely on whatever iBoot is doing to it, which turns out to be wrong sometimes
<chadmed>
once we are able to overwrite that (soon) this problem goes away
<j`ey>
pparker[m]: any luck?
hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
userll has joined #asahi
<pparker[m]>
j`ey: hm no it doesn't work
<pparker[m]>
tried it with echo display=1920x1080@59.94 >> /boot/efi/m1n1/boot.bin and echo display=1920x1080 >> /boot/efi/m1n1/boot.bin
<qiuren[m]>
<bluetail[m]> "doesnt it say write to the bin..." <- Exactly. It seems that the last section of the file is configuration. Such string append to `boot.bin` appears in some places of Asahi docs.
<qiuren[m]>
> <@bluetail:matrix.org> doesnt it say write to the bin file a new line with this content: `display=1920x1080@59.94`
<qiuren[m]>
* Exactly. It seems that the last section of the file is configuration. Such config string append to `*.bin` appears in some places of Asahi docs.
___nick___ has joined #asahi
<qiuren[m]>
So I think Sobek's comment is better. pparker you can use: `tail /boot/efi/m1n1/boot.bin` and see if any other configuration is already added into it.
___nick___ has quit []
___nick___ has joined #asahi
<bluetail[m]>
`The tail command displays, by default, the last 10 lines of a text file in Linux.` I see
BrenoMaia[m] has joined #asahi
kalios[m] has joined #asahi
<kalios[m]>
Hello. I have an error using the installer. Is this a good place to discuss it?
<povik>
yes
mr_zomka has joined #asahi
<kalios[m]>
The error I got was `Failed to run process: diskutil apfs resizeContainer disk0s2 218175111168`
<tpw_rules>
if you scroll up it should explain why
<mr_zomka>
Hi. Would Asahi Linux have support for emulating amd64 apps like Rosetta2 on macOS in the near future?
<kalios[m]>
I got a bunch of warnings about overallocation. And then `error: orphan/invalid physical extent (1677613)`
<j`ey>
mr_zomka: you can do that with qemu / fex
<tpw_rules>
kalios[m]: ok, you have APFS corruption. reboot into recovery mode, then run disk utility's first aid
<kalios[m]>
tpw_rules: hmmm will do. Did the installer cause the corruption?
<tpw_rules>
no
<kalios[m]>
What might have caused it?
<tpw_rules>
macOS did at some point. but the installer checks for corruption before it resizes the disk
<kalios[m]>
I see. Thanks I will try that out and report back
<tpw_rules>
a bug in apple's APFS driver. there have been a worrying amount of people coming here to report this
<tpw_rules>
i feel like everyone should put a first aid check on their calendar every month or so...
<mr_zomka>
j'ey: wouldn't that cause extra load on the macbook, especially when playing games?
<j`ey>
mr_zomka: but thats what you asked for?
<opticron>
mr_zomka, rosetta2 isn't a magic solution that makes everything run like native code, there is still overhead there
<bluetail[m]>
something runs in rosetta2 faster though :D
<bluetail[m]>
I think for Adobe it did
<kalios[m]>
tpw_rules: ran the disk utility. didn't pick anything up. am going to try run the installer again
<tpw_rules>
kalios[m]: did you run it on the right volume? it said "everything appears to be OK"?
<opticron>
bluetail[m], that sounds like a poorly optimized native build (or they were using a bunch of things available in x86 that they don't have or haven't ported over to the AArch64 build yet)
<kalios[m]>
I only had one volume to check. well, two ... I think one was a system volume? anyway I checked both. it ended with `everything appears to be ok`
<tpw_rules>
that's a little puzzling
<kalios[m]>
hmm same issue tpw_rules
<tpw_rules>
can you boot back into recovery and we can try to do some troubleshooting?
<kalios[m]>
For sure. What do you need me to do?
creechy has joined #asahi
<tpw_rules>
what does "diskutil list" say? you should be able to open safari and paste it somewhere
<tpw_rules>
also just to be sure, you have backups, right?
<kalios[m]>
Not sure I understand. I can open safari but where do I paste that? Is it a terminal command?
<tpw_rules>
yes. i mean you can go to pastebin.com and put the output there so i can see it
<kalios[m]>
Hmmm backups… I suppose I should create a backup. Not sure how to…
<kalios[m]>
How do I open a terminal?
<tpw_rules>
there should be a Utilities menu at the top
<tpw_rules>
iirc
___nick___ has quit []
<kalios[m]>
Hmm I don’t see it
<kalios[m]>
Is it alright if we continue this a bit later? Have a call I need to make
<kalios[m]>
Then I can try backups as well beforehand
<tpw_rules>
sure. time machine should be good enough for a backup
<kalios[m]>
Brilliant will do. Chat soon
___nick___ has joined #asahi
<Radical[m]>
Hey, how do you connect to the internet on the minimal version? I tried iwd but got errors trying it
<Radical[m]>
I’m apparently "connected" but i have no network access
hir0pro has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
___nick___ has joined #asahi
<Radical[m]>
Trying to ping any ip’s on my local network i get "network is unreachable" and pinging anything outside my network just says "Could not resolve host"
m6wiq has quit []
amarioguy has joined #asahi
kita99 has joined #asahi
<mps>
Radical[m]: did you configured iwd to do network setup
LinuxM1 has joined #asahi
<mps>
EnableNetworkConfiguration=True
<Radical[m]>
Ah alright
<Radical[m]>
I see it says disabled
<Radical[m]>
Thanks
leo60228- has joined #asahi
leo60228 has quit [Ping timeout: 480 seconds]
the_lanetly_052___ has quit []
hir0pro has joined #asahi
amarioguy has quit [Ping timeout: 480 seconds]
<meowcat285[m]1>
<EvadingEvasions[m]> "16k page issue." <- Well, whenever chromium gets fixed, it probably wont take too long
<pparker[m]>
VinDuv: Hey, patlux from GitHub here. How do I restore the boot.bin when I can't boot into the system? Can I somehow mount the boot partition when I boot into macOS?
<VinDuv>
pparker[m]: yes
<VinDuv>
From macOS open a Terminal, run diskutil list, and find the identifier (disk0sX) of the EFI - ASAHI partition
<VinDuv>
Then run sudo diskutil mount disk0sX and the partition will show on the desktop (and in /Volumes)
<pparker[m]>
Thanks! Works great :)
user982492 has joined #asahi
doggkruse has joined #asahi
armin has joined #asahi
dwib has joined #asahi
<dwib>
Hi there, i am planning on getting a new laptop soon, and I was thinking of getting a mac but I really want to be able to use Linux. I'm wondering if Asahi would be viable? Like would it be a relatively seamless transition for me from using arch, and are there limitations?
<j`ey>
there's limitations in that not all hardware works
user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Glanzmann has joined #asahi
Tano70 has joined #asahi
<Glanzmann>
jannau: I had to try your display_fb_alloc branch. So I updated my stub to 12.3 because it was still 12.1 on the mini. But I have different results: So hdmi hotplug (turn monitor off/on again never gives me the picture back) And with your branch while 2k works for m1n1 and u-boot, as soon as the kernel boots, i get a black screen on the mini. But I can log in remotely. Framebuffer module is loaded:
<Glanzmann>
simple-framebuffer be3a18000.framebuffer: [drm] fb0: simpledrmdrmfb frame buffer device. I only tied the 2k eizo with and without display=2560x1440.
<Glanzmann>
jannau: And since you mentioned that reinitializing give issue, I tried reboots as well as cold boots. Same result for me.
the_lanetly_052 has quit [Ping timeout: 480 seconds]
<jannau>
Glanzmann: I can confirm the black linux screen. that seems to be unrelated to my changes. I see that with the stage 1 m1n1 from the installer (not recent) and linux.py
<VinDuv>
Skirmisher: I was wondering, does macOS correctly detect the resolutions supported by your monitor?
mr_zomka has quit [Quit: Konversation terminated!]
<Glanzmann>
jannau: I see. I also used m1n1-rust.bin which I build myself but is a little bit older: (22th march). I'll upgrade to latest and retry. Thank you for confirming.
<jannau>
I don't think that updating will help
<jannau>
mine is based on df53f16f763ef83c 19th march
<j`ey>
what pages in particular are you missing from the ones that were removed?
<ktz_[m]>
I'm missing relevant content in the sidebar, most of the times I don't know which page might contain any relevant info to what I'm searching so I'm glancing through the contents and open pages that could contain some info
<j`ey>
at the top you can click 'Pages' to list all of the pages
<ktz_[m]>
Yes I know that but they're always folded by default and you totally get what this commit tried to sort out (which wasn't necessary at this point)
<j`ey>
thats why Im asking which page in particular you think is missing
<ktz_[m]>
This doesn't have to do with usability of course, please don't get me wrong, its just a QOL change for people visiting the wiki
serge133[m] has joined #asahi
colemickens has joined #asahi
<ktz_[m]>
Not a personal thing, just populate the entries with pages you think people will be finding useful, the prime ones
<colemickens>
Is there any reason to hold out hope that M2-powered iPads might be able to run Asahi?
<j`ey>
ktz_[m]: and that's why the sidebar is now
<j`ey>
Im confused, the sidebar has some pages still
<tpw_rules>
colemickens: i mean that's all on apple
<fncraft[m]>
colemickens: i might be wrong but iirc iPad’s are much more locked down than macs so that probably isn’t possible
<tpw_rules>
(also hi)
<colemickens>
tpw_rules: 👋. I did assume as much, it was a very speculative question. Some things about the M1 made it seem like they had maybe intentionally-not made it hard to run linux on the MBP, so I wondered if there was any speculation/hope/code hints that similar flexibility would be present on the iPads. But I also historically know that what @fncraft has been true.
<sven>
very unlikely that apple will ever allow anything like asahi on iPads
<j`ey>
ktz_[m]: im not trying to be contrary, just trying to understand. the sidebar has: Project related:, Platform documentation:, For users:, For developers:, each with multiple links
<sven>
on the MacBooks allowing to run a custom kernel was a feature they designed
<sven>
on the iPads and phones they absolutely don’t want that
<colemickens>
I guess I imagine that a M2 Macbook and M2 iPad are built and boot pretty similarly. I certainly understand they still get to control the initial bootloader, etc.
<colemickens>
* bootloader, etc and might make different business decisions per-sku, etc.
amarioguy has joined #asahi
<colemickens>
Anyway, it's the answer I anticipated, but thought I'd ask :)
<colemickens>
It wouldn't surprise me if they just see or hope to hold onto marketing the Mac lineup as more dev-oriented still compared to super-locked-down/secure vibes of iPad/iPhones.
<fncraft[m]>
btw is the gpu driver still being worked on? The last commit on github repo is way too old
<colemickens>
* of iPad/iPhones. (though, I also understand allowing Asahi doesn't have to mean compromising security)
<j`ey>
ktz_[m]: ok a few of those could be in the sidebar, I will add them later
<ktz_[m]>
Also sorry for being vague in my description j`ey I just didn't want to point to specifics that I'm personally interested rather than leaving it out to you to populate it what you think would be more relevant to everyone
<colemickens>
ktz_: also there are related mesa repos with much more recent commits, but not sure if its appropriate to link those around willy-nilly
kita99 has quit []
<ktz_[m]>
I just wanted to get across that having a sidebar with much content was nice
<colemickens>
s/ktz_/fncraft/
<Glanzmann>
ktz_[m]: I also missed a few entries, however what you can do is clonening the git reposistory and open the md files directly.
<ktz_[m]>
j`ey: by the way I in the logs you mentioning some user named saxung running voidlinux, is he still around? I'll try running void as well once I figure my way around good enough and I was wondering if he got any resources he could share
<ktz_[m]>
Glanzmann: yeah that's definitely the thing to do sir, you're right
<j`ey>
maxung[m] it was
<ktz_[m]>
Thanks, I tried tagging him but I got no results
<mps>
Glanzmann: I would like to add url of your video about setting machine with asahi installer to my guide
<ktz_[m]>
hey mps what is this guide for if I might ask? is it relevant to the draft you wrote about alpine?
<mps>
ktz_[m]: yes
<Glanzmann>
mps: Sure, go ahead.
<mps>
Glanzmann: thanks, what is official url
<ktz_[m]>
mps: glad to hear that man
<mps>
ktz_[m]: I updated it somewhat last night
<ktz_[m]>
By the way I think you forgot to fetch the fwupdate in the script, if the link is any relevant
<fncraft[m]>
<colemickens> "ktz_: also there are related..." <- yeah i noticed that
<ktz_[m]>
I mean the variable containing the link mps
<Glanzmann>
mps: So I have a few videos. This is the latest. But marcan improved the installer a lot since I recorded it: https://tg.st/u/m1debian.mp4
<mps>
ktz_[m]: yes, I had to check script first if it actually works
<ktz_[m]>
@mps great, thanks for updating it already I had a hard time getting to finish the installation properly on my own but I got a bit more into things and I might be able to do it from scratch on my own
<maxung[m]>
<ktz_[m]> "j`ey: by the way I in the logs..." <- ktz_: i mentioned in another reply already, but i dont have many resources to share at this point
<Glanzmann>
ktz_[m]: Btw, but I often do with the wiki if I want to see what's new I run git log -p | less -R -i -p "^commit" # use 'n' to browse
<mps>
Glanzmann: this is about debian, I watched it today, but iirc you had one about generic install
<jannau>
Glanzmann: I can't reproduce anymore. problem was entirely on my side
<jannau>
4k does however not work
<maxung[m]>
ktz_: i installed asahi, booted a debian live stick, installed the void tarball onto the asahi partition (wiping it basically) and then compiled the kernel + m1n1 to boot void directly (because I had problems with the efi setup and grub)
<maxung[m]>
* + m1n1 (with chroot) to boot
<ktz_[m]>
maxung[m]: No problem, I think just compiling the kernel is that part that I'm not familiar with yet but I'll do it as well eventually.. I'll need to put asahi and zfs into the same kernel to get zfsbootmenu working and have root on zfs
<maxung[m]>
ktz_[m]: ktz_: actually I dont believe its necessary though
<Glanzmann>
jannau: I see, strange. I'll make you a video and upload it, just in case that I don't miss something.
<ktz_[m]>
maxung[m]: Maybe you're right I'm not sure, my experience is pretty limited
<maxung[m]>
I just did it to get the latest changes + dtb's, but the asahi one should work fine
<maxung[m]>
And if you don't struggle with the EFI setup like I did, it's pretty straightforward
<ktz_[m]>
you mean the asahi kernel as is?
<maxung[m]>
Although a nice install script or USB image like Debian would be nice
<maxung[m]>
I'm not sure though, if I (want to) find the time
<maxung[m]>
ktz_[m]: yeah I think if you choose glibc variant and not musl it should work
<mps>
Glanzmann: thanks, will look and if I find it useful for end users I will add url to guide
<maxung[m]>
* glibc variant of void and not
<Glanzmann>
mps: If you want I can make you a script which creates an asahi installer image for alpine. Do you have a link for the kernel config and the rootf?
<mps>
Glanzmann: this will be for end users who like to watch video to get idea how it works, not as official guide
<ktz_[m]>
maxung[m]: Okay, I guess I'll be finished with installing alpine as my basic OS today, have myself setup and then try more from there
<maxung[m]>
Maybe I will try to make a script and let the experts here have a look, as for now (other then possibly kernel development) I'm not so much interested yet as a daily driver or something
<mps>
ktz_[m]: I prepared image which could be 'dd'-ed to usb disk, no hassle with script if some users wants simpler solution
<maxung[m]>
And I really like macOS
<mps>
Glanzmann: and if you want to make script which add alpine to installer I'm not against this
<maxung[m]>
mps: mps: I wanted to ask, does alpine use a different kernel format? In your script it has an apk ending?
<ktz_[m]>
mps: Yeap I used the image couple of times already, I couldn't figure out a couple of steps properly after booting from the usb but there are plenty of resources and I think I'll sort it out
<mps>
marcan: apk is alpine packages format
<Glanzmann>
mps: Maybe I find some time to it tomorrow. Does alpine execute a /etc/rc.local if it is there?
<mps>
Glanzmann: no, but /etc/local.d/$scriptname.start
<Glanzmann>
I see. Noted.
<mps>
I worked on draft guide and disk image so didn't had time to merge linux-asahi kernel to alpine repo, have to clean it somewhat
<ktz_[m]>
mps: would including zfs in the kernel require any interventions?
<ktz_[m]>
or I can just run the module of the normal kernel without any problems?
<mps>
ktz_[m]: it must be built as separate package, we (alpine) don't like big patches to kernels
<ktz_[m]>
there are zfs packages available already I just thought they wouldn't be combatible cause its a different kernel or am I wrong?
<mps>
ktz_[m]: you have to install linux-asahi-dev (which I didn't uploaded yet) and then build external modules
<Skirmisher>
maxung[m], ktz_[m]: I'm working on packaging + a live image for void on M1 right now. almost done with the former, only known issue rn is that USB doesn't work in the initrd for some reason. then I'll just glue it all together in void-mklive
<mps>
ktz_[m]: zfs pkg in alpine works only with linux-lts pkg, for other kernels it must be rebuilt by end users
<ktz_[m]>
Skirmisher: nice man that's great news, hope you sort the rest out effortlessly
<jannau>
Glanzmann: 4k is still roughly truncated after 11 / 15 of the height. which is good match for the preallocated fb size of 0x1500000
<ktz_[m]>
mps: Okay, I'll get back to making my installation boot properly and I'll try building it, thanks
<Glanzmann>
jannau: I see.
<maxung[m]>
Skirmisher: Skirmisher: oh thats cool, what do you mean "in" the initrd?
<Glanzmann>
jannau: Maybe, I did something really stupid. Maybe, but only maybe I had the dtbs of your dcp branch ... I'm now rebuilding everything from scratch, just to be safe and try again.
THX1984 has joined #asahi
<maxung[m]>
Skirmisher: I had to specify some kernel modules in the dracut configuration, because not all required kernel modules are built-in
<Glanzmann>
jannau: So turns out, I did something stupid. So with your m1n1 branch and the right dtb. I get 2k resolution without specifying the resolution (normally I get the default 1080p). But hdmi hotplug still does not work for me ( I tested by turning my monitor off and on again while I'm in X).
<Skirmisher>
maxung[m]: I mean in the dracut shell, for boot failures or if you invoke it manually. I already added the modules from the config in asahi-scripts but apparently that's not all the necessary ones, I looked at `lsmod` in the alarm initcpio shell and there are some extras
<Skirmisher>
either that or dracut is blowing up in the middle just because some of the modules are built in and don't exist, and it doesn't add the rest
<maxung[m]>
Skirmisher: i dont know about that, but I added tps6598x dwc3 dwc3-of-simple xhci-pci
<Skirmisher>
wish there was a way to make kmods optional, but oh well
<maxung[m]>
i compared the modules load by the asahi-script and which are builtin and these were the ones
<Skirmisher>
anyway I probably just solved my own problem :)
<maxung[m]>
yeah this is the script ^^
___nick___ has quit [Ping timeout: 480 seconds]
m6wiq has quit []
<maxung[m]>
otherwise i could send you an lsmod dump, if you want to crosscheck
<Skirmisher>
that's what I did already, but thank you
<maxung[m]>
alright, than good luck ^^
<Glanzmann>
marcan[m]: With the latest changes from the m1n1 branch, the right mode for my eizo is selected automatically (2560x1440).
<bluetail[m]>
then*
amarioguy has quit [Ping timeout: 480 seconds]
<Glanzmann>
marcan[m]: I now also installed the newest m1n1 in stage1 and with that, the resolution is again wrong 1080p 'adding display=auto to stage2' did not help, but settings the resolution explicitly works: echo display=2560x1440 >> /boot/efi/m1n1/boot.bin
fly_0ut[m] has joined #asahi
LinuxM1 has quit [Quit: Leaving]
Tano70 has joined #asahi
<marcan>
that's working as intended
<marcan>
it's not supposed to set >1920x1200 modes in auto mode
LukeTheWalker has joined #asahi
Tano70 has quit [Quit: Leaving]
LukeTheWalker has quit [Remote host closed the connection]
nicolas17 has joined #asahi
user982492 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]