<mkurz>
marcan: The charge thresholds patch made it into the edge kernel, so I can set "charge limits" now in KDE's "Advanced Power Settings", however those charge limits are not preserved during reboots. Are you aware of that? Should I open an issue?
2023-03-22
<dax>
new mesa versions take effect when you log out and back in. new kernel versions take effect after a reboot (sounds like you already did the kernel before coming here, so shouldn't need that)
<winter>
I think I found a bug, but I'm unsure where to begin with regards to debugging it. So, when I launch Sway for the first time after a reboot, the DPI looks OK. However, every time I quit and relaunch Sway after this, the DPI is very different. I'm not changing anything, all I'm doing is exiting and relaunching Sway. The logs don't show anything of
2023-03-21
<d4ve>
_jannau_: Rebooting to check, but I'm reasoably sure they did.
<winter>
<Retr0id> I'm confused, are you implying that you've loaded the edge kernel without rebooting? <-- No, I'm running the edge kernel, but en/disabling the same version of Mesa each time causes things to be weird until a reboot. But how Mesa is en/disabled is pretty nonstandard (yanking the binary out of the RPATH of the binary who needs it, and then
<Retr0id>
I'm confused, are you implying that you've loaded the edge kernel without rebooting?
<winter>
Retr0id, psykose: Sorry, to clarify: I'm running into the above quirk with the edge kernel loaded, just en/disabling Mesa using weird symlink RPATH... stuff... unsure how that'd be cached until reboot, though (nscd?).
<psykose>
the uapi comes from the kernel so the new mesa uses the new kernel apis but until you reboot it's only the old kernel
<Retr0id>
since until you reboot, your kernel is the old one
<winter>
Would en/disabling Mesa also cause this? As in, requiring a reboot to get GPU stuff working. How would I see if it's the UAPI change causing this? (Why is it causing issues anyways, wouldn't the new versions of the libraries be loaded? Or are we going off of cached libraries?)
<winter>
> Keep in mind that since the UAPI changed (a lot), apps will probably stop launching or will launch with software rendering until you reboot.
2023-03-20
<Cyrinux9>
ha, sorry for the noise, it was a bad combo for the m1 pro, after update and reboot, opengl 2.1 like my m2 air.
2023-03-15
<ah->
just had asahi lock up on a m1 max, here's what was left in journalctl after rebooting: https://nopaste.net/CnTM4WNrM3
2023-03-14
<Retr0id>
time to reboot and see if it sticks (also I tested xhci-plat-hcd from initrd and it worked, thanks)
2023-03-13
<matteo>
but as I reboot into linux, no keyboard
2023-03-11
<K900_>
OK, rebooting with 015b8cc5e7c reverted now
<K900_>
Rebooting fixed it
2023-03-10
<chadmed>
the watchdog should reboot the system before too long if the kernel dies anyway
2023-03-06
<mort_>
sven: how do you people usually do it? Do you do virtualization or do you compile your new kernel, install it, reboot and pray for the best?
2023-03-04
<Zeroine>
ah, the battery widget started showing the battery after a reboot by the way
<mort_>
Yeah, so I'm in the actual Linux graphical environment after GRUB and everything. But a reboot seems to have fixed it
<altf4_>
hey, I kept having this issue where after I installed asahi on my m1 macbook pro and booted into it, whatever configurations I saved for apps (like terminals etc) kept getting reset after a reboot
<i509vcb>
Interestingly if I restart the wifi works for like 30s and then stops working until I reboot again
2023-03-02
<zv_>
I probably should have asked first, does upgrading from 6.0.0-rc5 to 6.1.0 (via https://thomas.glanzmann.de/asahi/README.txt) require any special steps? the machine is not coming online after a reboot.
2023-03-01
<bluetail>
Also if it matters, I grabbed the frame where it reboots
<jannau>
that has the fix I'm thinking of. what does u-boot report before the reboot? record a video if it's too fast to read before the reboot
<bluetail>
I think I had a succesful reboot with 6 disks, running on USB C. But today when I tested with 4, I had a boot failure via usb c -> c
2023-02-23
<ChaosPrincess>
povik: havent enable speakers, yea, its failed of parsing, sorry, rebooted into macos and was going off memory, i believe those two are built, kconfig forces them on if you say y to macaudio
2023-02-22
<kotleni>
Okay, i rebooted to 6.2 kernel.
<kotleni>
Oh, i founded one bug with my usb c hub. If i connect any devices (like a mouse) to my usb hub - i need reboot system for use it. But if i connect mouse to usb c ports in my macbook - i can disconnect/connect device any time and it's work fine.
2023-02-18
<kesslerd>
Ok ty. Not seeing the bug anymore actually. It was there last night but now it's gone. Maybe it was just that I shut down my system and things rebooted.
2023-02-13
<i509vcb>
I'm trying to diagnose an issue I've had around wifi. I had to switch to wpa_supplicant because iwd is a pain with the PEAP network I use at school. However wifi is quite spotty sometimes (on some days, connection being instant and on others, requiring some luck and many reboots. I've also found sometimes that the network icon in plasma will show as disconnected but the hardware is actually connected. For reference I am using the asahi edge
2023-02-12
<ChaosPrincess>
more like reboot the whole system after changing itl
2023-02-06
<karpouzi>
it eventually shuts down or reboots as requested, but the hanging is odd. haven't seen it on other machines
2023-02-02
<Retr0id>
compassion, it's possible to get away without rebooting by rmmod'ing `spi-hid-apple-of` and then modprobing it again (note that you'll want to do both operations as a oneliner because your keyboard will stop working the moment you rmmod!)
<Retr0id>
actually hang though, merely stop redrawing). Once it starts happening, it seems to happen more frequently until I reboot. Is this a known issue?
2023-02-01
<compassion>
aaand the reboot cured it.
2023-01-27
<jannau>
even apple's boot picker reboots. it will probably possible to replicate that, i.e. select which OS/partition should be booted the next boot or should the standard boot OS
2023-01-20
<nsklaus>
and now that i have rebooted to asahi, the touchbar doesn't flashes constently, as it was earlier
<nsklaus>
i rebooted, i don't have that link anymore
<nsklaus>
rebooting, brb
2023-01-15
<bluetail>
after reboot its fine... but its awkward
2023-01-14
<marcan>
so they boot macOS to do that and tell the bootloader what to boot, then reboot
<chadmed>
the machine just straight up reboots if you try to make a peripheral touch memory its not supposed to
<chadmed>
yknow what let me reboot into macos and hammer out this apple-security-for-dummies thing ive had in the works for about three months now
2023-01-13
<derzahl>
the whole display? I am using the display right now. pixels work, just no backlight since i rebooted yesterday
<derzahl>
what would cause my backlight to stop working after a recent update and reboot? As soon as the edge kernel boots the backlight shuts off. It cannot be adjusted even after booting into DE on either xorg or wayland. /sys/class/backlight directory is empty
2023-01-12
<derzahl>
aww crap. what did i do? after having a beautifully working backlight for a few days with the edge kernel, now after and update and reboot i have no backlight at all...had to boot back into the regular asahi kernel to be able to make out anything on my screen
2023-01-09
<jannau>
yes, I hit that approximately 1 in 25 boots but it is sometimes sticky over reboots
<sven>
but you'd need to reboot after changing the value to see its effect anyway
2023-01-07
<bluetail>
sven I updated my system and after a reboot my usb c enclosure is no longer seen, even after replug. Any changes ?
2023-01-06
<marcan>
blazra: note that the KDE charge limit settings do not persist across reboots (there is a bug open for this)
2023-01-03
<eric_engestrom>
but rebooting in -edge fixed everything, I got a mouse (not that I use it much xD) and networking
<eric_engestrom>
grmbl, `reboot` takes me back to macos... how does one configure which os to boot by default? is that the `bless` thing?
<eric_engestrom>
rebooting to -edge
<eric_engestrom>
`cp boot.bin.old boot.bin` and rebooting
<eric_engestrom>
rebooting to check if that helps, but I'll be away for half an hour after that
2022-12-30
<waldi>
the firmware a new kernel to load -> no way to reboot
<vivithecanine>
Arch will delete those and you won't be able to load them until you reboot unless you run a trigger to keep them aeouns
<merry>
ah the magic of rebooting
<merry>
reboot fixed it
2022-12-27
<tpw_rules>
i'm getting an occasional hang on boot from dcp failing to start ("wait for power timed out"), possibly in a racy way: https://pastebin.com/J5LkdH7F seems like it might be more likely to happen rebooting from macos (asahi is my default boot option) but i can't make it happen on command
2022-12-19
<bcrumb>
at least for me. because i could then just work on this genuine system while rebooting container (i know this sounds wrong but trying to express this somehow :X) such that i can work much faster
2022-12-18
<kallisti>
Or that I should try to install to my usb c flash drive and chroot into the system and reset the password that way? Finally chrooting from docker or a vm on mac os would be nice because I wouldn't have to reboot (until testing if it worked)
<nicolas17>
austen: reboot back into macOS
2022-12-08
<LinuxM2>
now i try reboot and i check if the backlight stays on
<aaron465>
hihi! 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...
2022-12-07
<SuperBalou>
I still can't make a pipe haha, but I may need to reboot because I edited a lot of stuff
<phb>
I'll reboot first, to minimize the noise
<Chainfire>
jannau> pretty sure yes, I'll reboot again in non-edge to make sure
<thasti>
here's two screencaps I got (first one of the kernel oops on the first reboot)
<jannau>
thasti: that looks more like an unclean shutdown. try to reboot to macos and try again
<thasti>
it attempted booting once, however Xorg didn't start and I got a kernel stacktrace instead - after rebooting m1n1 is saying "chainload: NVME init failed" and starts the proxy
2022-12-06
<capta1nt0ad>
did you reboot?
<capta1nt0ad>
then reboot
2022-12-04
<corion>
I have a curious issue sometimes when I boot up asahi-linux (standard, not edge). Trackpad and keyboard doesnt work post grub. To solve it I have to reboot again and then it will work just fine.
<Chainfire>
Anyone know of any livecd that works to boot from uboot to have a GUI to use gparted? I have an old Debian one that I think Glanzman made but nowadays it reboots after a minute or so...
<marcan>
nicolas17: update asahi-dev, reboot, and try `grep -a . /proc/device-tree/chosen/*-version`
2022-12-02
<joske>
rebooting
2022-11-30
<janrinze>
just for the sake of info: after another reboot it seems that the Asahi Linux boot option now starts Debian. And the debian boot option simply hangs.
<janrinze>
the whole installation process finishes, debian boots, as root set passwd etc. reboot, system hangs with waiting Proxy or something like that
2022-11-25
<j`ey>
bcrumb reboot into recoverOS/macOS and change the brightness, then reboot into linux
2022-11-23
<axboe>
I just rebooted to be sure
2022-11-22
<kit_ty_kate>
i got the issue twice when rebooting my machine another time after the m1n1 + kernel upgrades, but then it went away for some reason
<kit_ty_kate>
has anyone got any issues with a total loss of keyboard and mouse when rebooting their machine after the update?
2022-11-21
<cy8aer>
- reboot to linux
2022-11-18
<Glanzmann>
axboe: Let me reboot and try it on my m1 air.
<Glanzmann>
sven: I rebooted a few times but can not reproduce it. :-(
2022-11-17
<Izumoo>
I'm following steps to best of my ability with the hold down -> Entering Startup Options but then it reboots and either goes there (where it fails step2.sh) or goes to a macOS recovery warning screen in my case. 2021 M1Pro MBP
<mps>
yes, reinstalling alsa-ucm-asahi and reboot solved issue. strange
2022-11-16
<tpw_rules>
2. you might have to update and reboot a couple times to get all the bluetooth firmware loaded, and idk if the bluetooth stuff is installed by default
2022-11-15
<kujeger>
j`ey: it's just happened three times so far, so I've just rebooted. But put the rmmod/modprobe in a script now, so I can easily try it next time
<bluetail>
device is found, but not shown in pavucontrol, even after reboot.
<j`ey>
kujeger: oh, you just rebooted to fix it?
<bluetail>
the device is found. I gotta reboot the system -> irc disconnect
2022-11-13
<ChaosPrincess>
update-verndorfw and reboot
<kallisti>
should i reboot, follow next steps then reinstall
<kallisti>
jannau: reading the partioning-cheatsheet it looks like i could wipe the partitions with the "dirty script" and re-run the installer. Would that be a reasonable course or should I reboot, then reinstall?
2022-11-10
<ChaosPrincess>
because when you do it, the system firmware copies the bootloader to internal, and then reboots
2022-11-06
<bgb>
jannau: I just failed, even with NO change to config. clone the PKGBUILDs, cd to PKGBUILDs/linux-asahi/, makepkg and pacman install, reboot
2022-11-04
<mps>
no need to reboot
<cy8aer>
If you just put the params in, nothing happens, reboot and you are at the point before when scary things appear (which might not)
2022-11-01
<Glanzmann>
axboe: I see, I reboot a lot and switch workstations all the time.
<axboe>
Glanzmann: generally don't reboot a lot, only when testing something like this
<ayke>
I have Linux as default which means when I do a reboot inside MacOS I end up in Linux.
<ayke>
Lightsword: not that I'm aware of, but you can set one (Linux or MacOS) as the default. Then, when you do a reboot it will boot the default OS (which may be different from the OS that you were running)
<Lightsword>
is there a way to trigger a reboot from asahi to osx without having to hold the power button similar to the startup disk menu in preferences for going from osx to asahi?
2022-10-28
<UnicornsOnLSD>
Hi, sorry if this is already known but is the Asahi installer known to be broken with Ventura? When rebooting into the new profile (to setup the boot config in RecoveryOS), my Mac bootlooped until it eventually let me select a different startup disk. I did manage to try to select the Asahi option once, it showed that the OS failed to make it the default boot. I have some images, will upload
<millenialhacker>
Yes, but kernel thing I did early in the day before, and tested it rebooting multiple times to ensure I had a bootable system before start the upgrade.
<millenialhacker>
AFAIK yes, I recompiled kernel asahi-wip before but I rebooted first to test it before rebuild whole system. I also kept two fallback kernels just in case and none of them boot now.
<millenialhacker>
Even with rd.break added added to cmdline I just got a blank screen and then reboot
2022-10-27
<joske_>
reboot fixes it
<j`ey>
it's pretty easy to reboot into recoveryOS of course, but a menu is nice too
<joske>
reboot to linux :-)
<joske>
rebooted to macOS to check right speaker wasn't b0rked, it's not
2022-10-26
<gausus>
yet still, after the reboot i get multiple addresses to my interface
2022-10-22
<j`ey>
hm "macsmc-rtc macsmc-rtc: setting system clock to 1976-05-25T00:01:16 UTC (201830476)" I wonder if this is due to a forced reboot/shutdown, I'll reboot into macOS to see if it fixes it
<j`ey>
getting it for reboot too: 'macsmc-reboot: Failed to locate of_node [id: -1]', so maybe a generic issue with the dts, but it still seems to load/probe
2022-10-17
<Ry_Darcy>
@marcan Was watching your live stream today with the CPU and sound etc. Have just compiled 6.1.0-rc1, rebooted and the ring buffer reports "cpu cpu0: apple_soc_cpufreq_init: failed to get cluster info: -2" for all (cpu0-7) CPU's.
2022-10-16
<ayke_>
jannau: I found that when the brightness changes due to automatic brightness changes in MacOS, it doesn't always stay at a reboot. But when I change it manually, the brightness appears to stick.
<derzahl>
eh, ill just reboot. its fast enough
<derzahl>
ok, rebooting into my kernel with CS42L83 enabled and will try turning up brightness in recovery first
<j`ey>
reboot into macos/recovery and turn it up
<derzahl>
ok, lets see. just gonna reboot
2022-10-15
<borisk>
also I tried warm reboot, and that works as well, at least from successful previous boot
<marcan>
hard shut down and reboot
2022-10-14
<mxw39>
thanks for getting back! I have put the files in /usr/share/alsa and rebooted.
2022-10-13
<WhyNotHugo>
jannau: Right, the picker could show "reboot into macOS", for example.
<sven>
isn't there even a boot-uuid or something like that in nvram? I bet all you have to do is change that to the correct value and then reboot
<jannau>
define available. there is no code which does that on linux side. but that's very likely how the boot picker implements that it. note that slecting a statup disk reboots the machine
<WhyNotHugo>
bootctl and some other bootloaders have a "reboot into firmware" mechanism.
<WhyNotHugo>
Is it possible to tell an M1 device to "reboot into fireware recovery mode"?
2022-10-12
<mps>
eric_engestrom: I have to reboot to macos to check (didn't booted macos in last two months or more)
<chadmed[m]>
anything weird in dmesg? also the amps may have triggered that OCP thing that causes the drivers to drop out until you reboot next, its still a bit flaky imo
<r0ni>
and reboot
2022-10-04
<jlinton>
ChaosPrincess: Yes, I've tried just about every variation on the power button, it won't reboot into the menu until it goes through the recovery options to reselect macos.
2022-10-03
<jlinton>
asahi should work on a 2021 macbook pro, right? Any suggestions why it gets stuck in a boot loop (or how to debug) rebooting right after "continue holding for startup options", "loading startup options..." reboot. I DFU cleaned/installed 12.6 on it, and then ran the installer again, and it continues to reboot for mins until I get tired of holding the power button, go through to select the mac hd for boot, shutdown the machine. At
<ashi>
Another observation: If I forcibly shot down 6.0 when in initrd, m1n1 fails to init NVMe on next reboot until I boot to macOS once. In 5.19 nothing like that happens if I do the same (focibly shutting down in initrd)
2022-09-17
<chadmed>
i think more important than the absolute quality is the quality relative to macos, because people are going to reboot into linux and go "wtf this sucks"
2022-09-14
<kazukih[m]>
Then reboots after a while
2022-09-13
<Doliometer>
Generally speaking, if I close the lid and reopen, I get a blank screen with underscore prompt in upper left. The system is unresponsive and I have to reboot. Is that common?
2022-09-11
<GllmR[m]>
It work after a reboot 🤷
2022-09-10
<tpw_rules>
you don't have to do the resize at the end if you want to try to reinstall again. but reboot your system and maybe change your user's password or something to make sure that logic works correctly the next time
<ZachS>
So it seems I have made a stupid mistake. I made a time machine backup of my M1, did a full wipe, almost finished the installer, then it asked me the password for the use "_mbsetupuser". I tried every password I knew, then used the "passwd" command to change it, and it still didn't work. Tried rebooting the computer, and now the installer won't work. I then went to erase the whole Mac, and since ext4 is not readable by MacOS, it thi
2022-09-06
<M4t64[m]>
also after i reboot existing bluetooth connections need to be removed & reset, which is pretty trivial tho
2022-09-02
<mixi>
bestouff[m]: the last time I installed, I set up the unencrypted /, booted it once adding everything required for luks (cryptsetup), creating the new fs (mkfs.*) and network (to get the contents back into the encrypted rootfs) to the initramfs, rebooted into the initramfs rescue shell and set it up from there
2022-08-31
<IcaroDextris[m]>
Just for information: seems after the grub update i can't reapply my previous grub theme using grub customizer, it doesn't show any error but when reboot the theme isn't applied
<zamadatix>
Lowere the brightness in macos, rebooted to asahi, rebooted to macos, raised the brightness, and rebooted to asahi and it seems reasonably bright now. Don't know if it was actually that or just retrying a couple more times but it works now :)
2022-08-24
<kit_ty_kate1>
(it worked fine after a reboot somehow)
<kit_ty_kate1>
hi, I haven't seen anything on the bugtracker so I'm asking here just in case it is a known issue but i just booted my asahilinux partition and past Grub, both the mouse and keyboard were unresponsive and i had to force shutdown and reboot to make it work (pressing the power button did bring up the GDM shutdown prompt though). Is that something anyone else has seen?
<nsklaus>
sven: hmm i see, if it would require a reboot no matter what, then maybe better to wait until dcp driver implements it properly
<sven>
sure, that might work. will still require a reboot for every change then
<nsklaus>
ah really ? if so nice, that ould already be something. even if quite troublesome to reboot to macos and then back in linux just to change brightness level
<mattgirv>
Well it's definitely a fixed value, pretty sure I've rebooted in to asahi with brightness lowered and it maintains that level
2022-08-19
<mps>
jannau: on m1pro I tried to ping it from other computer but didn't got any reply, and machine reboots after about one minute
<Glanzmann>
axboe: and reboot (faster than unload reload the modules).
2022-08-18
<j`ey>
not sure, but I guess you can only reboot remotely then
2022-08-16
<hell__>
in case you want to upgrade, reboot, and delete the old packages once you're satisfied with the new packages (e.g. no regressions)
2022-08-15
<bgb>
marcan: yeah, i need pacman -ySu and reboot, thanks.
<marcan>
did you actually reboot with the updated kernel?
2022-08-13
<Techcable>
yeah a reboot fixed it
<Techcable>
but a reboot fixed it so I'm happy
2022-08-11
<princesszoey>
won't reboot without pink screen crashing, randomly loses all audio, and started hard locking itself
2022-08-08
<princesszoey>
oh cool, my macbook decided it doesn't want to reboot right suddenly. It closes all my apps and it sits at my wallpaper for a minute before pink screening and crashing.
2022-08-05
<j`ey>
dont think so, try a reboot
2022-08-03
<mps>
i.e. u-boot throws error msg and reboot
2022-08-01
<whynothugo>
Just did that; rebooting.
<whynothugo>
Yeah, just forgot to reboot since the last kernel update, my bad.
<whynothugo>
Oh, shit, I didn't reboot!
2022-07-30
<bluetail>
brb reboot
2022-07-28
<ChaosPrincess>
go to system settings -> startup disk, set your macos install as target and reboot into it
2022-07-27
<Glanzmann>
Than reboot, to put the kernel command line ...
<mps>
have to reboot to macos to check
2022-07-26
<marcan>
it should be fixed after a reboot
<boopi>
No, I had it turned off in OSX before rebooting, and the device was not available in linux
<boopi>
j`ey: I think I know what happened - I turned off wifi before rebooting
2022-07-22
<_jannau_>
have you rebooted since you ran pacman -Syu the last time?
<j`ey>
alarm: reboot?
2022-07-21
<Manouchehri>
ElvishJerricco[m]: once you have your machine rebooted, really try to avoid ever rebooting it.
<Manouchehri>
tpw_rules: so for updating to a new kernel, a regular reboot should be fine right?
2022-07-20
<janrinze>
I'm going to test 16 k pages now.. rebooting and brb
<Dcow[m]>
marcan: so the pipeline would be set this key and reboot?
<Dcow[m]>
marcan: do you know if there a key to set one-time reboot target?
<_jannau_>
yes, that has the way the boot picker works as it does a reboot
<clover[m]>
does asahi have a 'reboot into MacOS' feature? where if you are in a shell in asahi you do a command that boots you into the MacOS disk without messing with the boot selector?
2022-07-19
<StellarOrbit44>
kettenis whatever the case, it works now. I just rebooted just fine
<StellarOrbit>
kettenis right. What do you think the issue could be? I am gonna reboot to see what happens if I let it boot normally again
<StellarOrbit>
Glanzmann that's what I did. I wrote the installer to the usb and booted into the installer from asahi u-boot and installed it normally and rebooted into it just fine from u-boot. It was when I upgraded to the snapshot that I had the issue
<chadmed>
so not only will this become increasingly rare as all features are enabled OOB, but outside of that it only affects _some_ users and the solution is to just reboot the system once
2022-07-18
<IcaroDextris[m]>
No after a reboot it stop doing it
<_jannau_>
if the bluetooth firmware is not found try to reboot if you have just rebooted once after the update
<Glanzmann>
jannau: Thank you for the hint about the firmware with the m2. What is your plan, boot into Linux during first boot, grab the firmware, build an initird and reboot or should I just not put the touchpad/keyboard module in the initrd and initialize after the system has booted?
2022-07-12
<clover[m]>
i switched to asahi-dev and rebooted. in bluetoothctl it looks like the agent registered and the controller works, but it doesnt discover any devices when i do `scan on`
2022-07-11
<Ry_Darcy_>
Another note: I have been running the Asahi (debian derivative) 5.18-asahi since April with no problems (performance) etc. Yesterday (Sunday, 10.07.22), I downloaded the latest Asahi kernel (pre-5.19-rc5) and the compile completed as normal. Rebooted and found that xorg was using a lot of CPU. This was not the case before I compiled the kernel yesterday.
2022-07-09
<chadmed>
but if youve just booted the livecd then you can very easily get back to asahi just by rebooting
<chadmed>
ivabus[m] you can literally just reboot and select Arch Linux on grub
2022-07-08
<ChaosPrincess>
no, rebuild the kernel with the new device tree and reboot
2022-07-07
<zzywysm>
have you tried shutting the system down completely? or have you just been rebooting since you discovered the issue?
<janrinze>
quick register list and rebooting again
<janrinze>
sven: I want to update the dtbs. so either need to add it in a working m1n1 or use grub for that.. however both methods seem to fail. lots of reboots
<janrinze>
brb.. rebooting.
<janrinze>
steev: i'll copy the dtbs to the /boot partition.. brb after reboot.
<janrinze>
brb, will reboot now. (wish me luck ;-) )
<nicolas17>
mps: how do I make scaling_governor changes persist on reboot?
<janrinze>
at least rebooting is faaaast
<janrinze>
let me reboot for a second and see if the nwely built kernel can find the root partition now.
2022-06-28
<sami-dev[m]>
Someone told me GPU is in dev, but after adding asahi-dev to pacman.conf and doing a full system upgrade and reboot, I do not see any difference. Do I need to do something else to test out the GPU driver?
2022-06-26
<nicolas17>
so grub sets "boot to macos next time" flag in nvram and reboots?
<tpw_rules>
so a tiny stub kernel which just pokes nvram and reboots would work, if be kind of slow
<tpw_rules>
there's probably a way with nvram. the machine already has to reboot once you select macos from the boot picker
<nicolas17>
"This boot chain is designed to progressively bring the system closer to a "typical" ARM64 machine, so that subsequent layers have to worry less about the particulars of Apple Silicon machines." I think by the time you reach grub you already modified the system state too much to be able to go back to macOS without rebooting
2022-06-24
<jannau>
I guess it will be kind of slow in the beginning anyway. Rebooting a couple of times into macos recovery until chainloading works
2022-06-17
<zx2c4>
alright, rebooting. fingers crossed
<j`ey>
rebooting will run m1n1
<zx2c4>
maybe rebooting doesn't actually rerun m1n1 and i have to totally powerdown?
2022-06-16
<ChaosPrincess>
reboot to recovery and repair your boot disk
2022-06-15
<zx2c4>
_jannau_: okay i "fixed" it by... booting into macos recovery ("Options"), and then rebooting after that
<zx2c4>
not sure what changed. i rebooted a bunch of times
<opticron>
zx2c4, there's a complicated dance you can do to get ext4 read support from macos, but it's not fun and requires disabling security because you have to add a kext and it takes at least a couple reboots to accomplish along with some scary confirmation prompts
2022-06-13
<derzahl>
but he didnt mention what to change, and I rebooted to test the first change right as he mentioned the second file/line to look at
<derzahl>
j`ey: Update on zfsbootmenu: didnt work after the compiling the kernel with the first patch suggested. I see you also posted a link right before I rebooted to test: https://github.com/torvalds/linux/blob/master/arch/arm64/kernel/machine_kexec.c#L70 How would you suggest modifying line 71? Just remove the whole 'if statement'?
2022-06-08
<Guest546>
hello there, after installing, rebooting and complete the install I got a black screen when I try to boot asahi on a macmini m1 via hdmi
<sven>
the update process is probably something like “put ram disk to $special-location and set some magic nvram arguments and then reboot”
2022-06-06
<ComradeMisato[m]>
reboot worked, thanks
<nsklaus>
so try to reboot.. then once rebooted confirm that your changes survived the reboot (they should have) and confirm that behavior of bringing up the start menu do happen but when pressing ctrl key
2022-06-03
<life-the-user[m]>
Lol: setting the brightness in macOS and then rebooting into Linux suffices as a workaround until the patches for the DCP are distributed.
<hectour[m]>
The headphone jack does not work for me on my Macbook Air. Rebooting does not solve the issue is there something else I can try?
2022-06-01
<MTecknology>
The first time I selected asahi at boot time, it prompted me for credentials and to confirm changes and then rebooted. Since then, it just comes to a blank screen and that's it. I'll fiddle with it later, but taking a break now.
2022-05-31
<j`ey>
so rebooting may help
<derzahl>
dang, not sure what is causing all these display artifacts and tearing. Lined up with booting a newly built kernel but I had an uptime of about 6 days before rebooting so there had been multiple changes. anyone else notice anything similar?
2022-05-27
<Glanzmann>
No idea if it is safe or not, but I worked several weeks under Linux. And my macbook air still works fine. I use the system on a daily basis for multiple hours. It is my main machine when I'm traveling. But since I give a lot of online trainings and we don't have camera or microphone under Linux, I use macos to deliver trainings. I often reboot in the evening to Linux to do some work.
<sanpen>
hi, i'm having trouble with my machine after rebooting. i end up in a grub prompt and usb devices don't work so i can't remedy things using my keyboard. how do i get out of this state?
<cmalvi[m]>
i'll reboot and check
2022-05-24
<piroko>
alright updated to latest asahi-dev. reboot time...
<piroko>
povik: I rebooted 5 times. same error every time. it's a MacBook Air (M1, 2020). I'll get you the exact error in a bit
<marcan>
and the SMC reboot driver
2022-05-23
<xfim>
I am rebooting with alpine right now
<xfim>
So I have rebooted with the docking attached to the back usb-c, but it fails anyway.
<xfim>
OK, let me try again. Need to reboot to 1TR
<xfim>
OK, I have rebooted again to 1TR and now I have the "Running proxy...", but there are several more messages that don't look very well.
<_jannau_>
you should be able to break out of the installer with STRC-C without reboot
<xfim>
Or you would recommend, now that I am in MacOS and the installer is not yet rebooting, to mount the FAT32 partition and change the boot.bin?
2022-05-22
<weapon_of_nix[m]>
<j`ey> "weapon_of_nix: you can reboot..." <- how do i enter that into grub? i tried cancelling autoboot and typing it but nothing seems to have happened
<weapon_of_nix[m]>
<rin20xx> "rebooted with them *not* plugged..." <- btw something marcan suggested regarding video playback that has fixed these issues for me is toggling sound off and then back on
<rin20xx>
rebooted with them *not* plugged in, haha! it works now!
<rin20xx>
rebooted twice with the speakers plugged in, didnt work
<rin20xx>
ill brb after trying rebooting again :p
<rin20xx>
tried rebooting twice; ill see if rebooting w.o my speakers plugged into the headphone jack works once i plug 'em back in in a bit
<j`ey>
rin20xx: have you rebooted? its flakey so try rebooting
<j`ey>
weapon_of_nix[m]: you can reboot and try adding 'init=/bin/sh' to your command line in grub
<tpw_rules>
but then i rebooted because the installer didn't pick it up and now it just flashes SOS which i assume is not a positive outcome
<sven>
you do need to configure both usb pd controllers to that serial mode which can only be done from macOS for now and doesn’t stick after a reboot
<jannau>
mps: the guide explicitly has instructions to add symlink from /usr/lib/{modules,firmware} to /lib before rebooting
<holyspirit[m]>
but when i reboot i get keyboard access in grub menu but none in system
2022-05-17
<Sobek[m]>
Just updated my macOS. I should test the asahi reboot at some point (and perhaps run some update in there)
2022-05-13
<spiralw>
ah, I just did a reboot and went back into 1TR and it seems to work correctly now
<spiralw>
hello! I'm trying to install asahi on my macbook air, and I accidentally turned on the laptop after the first reboot without going into 1TR. when I did get into 1TR, I got a message saying "Your system did not boot into the correct recoveryOS", and when pressing enter after that message I get a bless error "could not load apfs.efi data"
2022-05-10
<cmalvi[m]>
Yes I read the warnings about. I reboot now in the 16k kernel to give a try, thanks
2022-05-07
<m1n1m4[m]>
mps: rebooted and without starting x from the same console the error is still the same.
2022-05-04
<kettenis>
ah, the problem happens when you reboot?
<j`ey>
I guess in the asahi tree because we have the actual SMC reboot code, that doesn't happen
<maz>
I have similar problems with rebooting. if I don't disable runtime services from the kernel command line, it goes mad.
<w12101111>
So I recompile m1n1 and uboot, and reboot
2022-04-24
<Ll3macorn[m]1>
for some reason ive just gained 5 gigs according to the storage thing after rebooting
<marcan>
try rebooting
2022-04-23
<asahi-test[m]>
well this install has about 400MB and i no longer need to reboot to macOS to have a browser ihihihihih
2022-04-22
<Sellerie>
Hi there, I recently installed asahi on my Mac Mini M1 using the installer. I'm experiencing a weird issue with media playback though: When I try to watch a video (using a USB soundcard as HDMI audio doesnt seem to be working yet) it sometimes works flawlessly, sometimes it just doesnt start and I have to reboot to make it work again. Same with
<derzahl>
anyone know if I need to mess with m1n1 at all or should I good to reboot after configuring grub?
2022-04-20
<cmalvi[m]>
oh, well, i need to reboot in asahi because i don't remember and now i'm typing from macOS
2022-04-18
<neggles>
at this point it’s “wait as long as you feel is justified, then cross your fingers and reboot it”
2022-04-15
<mofux[m]>
after upgrading from mac os 12.3 to 12.3.1 i can no longer boot my asahi linux (12.3 stub). When selecting it as startup disk it will run into a seemingly endless boot loop (apple logo + progress bar appear for ca 4 seconds, then it reboots)
2022-04-12
<bluetail[m]>
I also have 12.3.1 installed and all I faced so far was that I am kind of in a bootloop - it takes 4 reboots toshow grub and its not instant after asahi was chosen
<blassphemy[m]>
same thing after reboot
<tpw_rules>
try rebooting to double check, especially if you just deleted the asahi partitions
<kode54>
they end up in /tmp which usually lives until your next reboot
2022-04-11
<Cy8aer[m]>
> but instead, the issue manifest as the update deciding to revert when I rebooted back to macOS
<Glanzmann>
kode54: So when I read that there is a new macos update in irc, I usually type 'reboot' and keep the power button pressed which puts me to the boot picker and than I select macos and started the update from there.
<kode54>
it rebooted to Asahi instead
<kode54>
the only issue I recall having was that it didn't reboot into the updater
<kode54>
but instead, the issue manifest as the update deciding to revert when I rebooted back to macOS
2022-04-10
<bluetail[m]>
the thing before the bootloader doesnt work on every reboot
<bluetail[m]>
but its a bit annoying that sometimes it takes 4 reboots to boot asahi
2022-04-07
<Jamie[m]1>
didn't resume successfully (can't remember if kernel panic or serial disconnected), but went away after reboot
<nametable[m]>
When I try to boot to MacOS with m1n1 proxy, the Mac (M1 MacBook Air) seems to reboot and my serial connection drops... I am chainloading to the latest m1n1 so that the tool versions are the same. Any idea what might be going wrong?
2022-04-06
<Glanzmann>
mps: Mar 25 16:44:17 air kernel: [ 3195.590747] tps6598x 0-0038: cd321x_interrupt: failed to read events - this message came 83 times a second until I rebooted.
<bluetail[m]>
i used 1tr to boot macOS and then rebooted
<bluetail[m]>
but like it took 4 reboots and them asahi was booted after I shut it down in the asahi boot loop
<bluetail[m]>
i used apple menu reboot
<j`ey>
bluetail[m]: you forced a reboot in the middle of the update process?
<bluetail[m]>
I installed macOS update and rebooted in the process.
2022-04-04
<r0ni>
j'ey: yes I used that, checked thru it, seemed ok to run. it found my kernel and stuff assumed safe to reboot, I was wrong
<cmalvi[m]>
j`ey: Sure, give me few minutes to reboot the Mac and reproduce it
<r0ni>
ran the update-grub script, it found my kernel and all, rebooted and it goes into a safe mode with no way out
<j`ey>
ok, rebooting into recoveryOS and it thinks it's 1976 :/
<j`ey>
:-) I think I'll reboot into recoveryOS at some point, see if that fixes the rtc