2022-04-04

<r0ni> i'll try it my next reboot

2022-04-03

<Guest1043> tried rebooting a few times to work around that flakeyness too
<tpw_rules> ok yeah. reboot into recovery mode and run disk utility's first aid function

2022-03-30

<zv> (logging in as root has been reliable, reboots are fine)
<zv> tpw_rules: it's actually quite stable. stock "debian installer from glanz". no extra hardware for reboot capabilities, not a tethered boot.
<bluetail[m]> I will do a reboot as it still fails after First Aid
<joske> well, no harm in trying asahi, if you don't like it, you can just reboot in macOS (just with less diskspace ;-))

2022-03-29

<asahi-test[m]> Hello all, i just want to report that i booted to ASAHI with 10% batt only but charging and could not see anything on the screen, rebooted, same. Then pressed the key to make the screen bighter and image came back.
<cmalvi[m]> install success, now im' trying to reboot
<chadmed> you dont need to do anything, grub will be updated with your new kernel. just reboot and you will be in the patched kernel
<clayscode[m]> I don't believe I have it at 100% on MacOS, but I could be wrong. Will give it a try next time I reboot though, thanks!
<kode54> mainly because there's no Mac firmware to switch it back on when you reboot

2022-03-28

<bluetail[m]> CTRL+ALT+DEL for instance lets me logout, reboot or poweroff
<nicolas17> bdju: you need to boot into macOS, set a password for the initial user, reboot into the recovery environment (which is also macOS), and install Linux from there; that's unlikely to change in the future

2022-03-27

<Glanzmann> jannau: And since you mentioned that reinitializing give issue, I tried reboots as well as cold boots. Same result for me.
<tpw_rules> kalios[m]: ok, you have APFS corruption. reboot into recovery mode, then run disk utility's first aid
<pparker[m]> reboot
<LinuxM1> macsmc_reboot 65536 0
<LinuxM1> I rebooted several times is not showing
<chadmed> reboot
<marcan> so if they expanded the partition and rebooted that's all it takes
<tpw_rules> might need to reboot first
<BenFE> thanks lol. i did a sudo reboot before disconnecting from irc :)
<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.

2022-03-26

<M1bn3mar[m]> j`ey: k, the main thing stopping me from daily driving asahi is the speaker's i literally reboot 4 that reason so is it a priority right now or is it secondary?
<j`ey> oh, I really should have put my stuff in BOOTCOMMAND way earlier, speeds up the reboot cycle so much
<enchiladasconpinguino[m]> will test, have to reboot now

2022-03-25

<Sobek[m]> Well, it definitely is brutal compared to the GUI shutdown. I think there must be a way to invoke the graceful shutdown (macOS installers do it, my AV software package too (well those do reboot, but hoepfully the same API can be used for shutdown))
<kode54> Linux isn't rebooting for you?
<kode54> Sobek[m]: it can't reboot afterward
<Sobek[m]> kode54: Yes it does, but unlike when I use the menu stuff, (and the various window get closed, plus getting all the auto save requests et al), here the screen goes black immediately. (I'd say a option to reboot later would be great, one that allows me to ensure all good and shutdown using the macos menu)
<Sobek[m]> Currently waiting for the installer to finish filling up the root, before the 1TR reboot.
<Sobek[m]> Well rebooting on recovery to try and fix those orphans doesn’t fix the orphan in Time Machine snapshots. (Those orphan will go away when the snapshot is deleted). If this still prevents Asahi from installing it is going to be a bit annoying.
<Glanzmann> bluetail[m]: So updating a kernel normally means instaling a newer kernel and rebooting. On a live system it is more trickier because you have to put the kernel outside of the initrd. And often live systems have stage1 initrd and than use squashfs and an overlay but to be honest these days, I don't really want that anymore.
<Ry_Darcy> @Glanzmann I applied your boot fix (4K) yesterday evening. The machine (M1 Mini 2020) reboots with no problems. In BE, I am using a cheapo 2K Benq monitor. As stated, this works, i.e. no black screen.
<kode54> it extracts this stuff mac side before rebooting

2022-03-24

<geerlingguy> ah... since I updated kernel probably just need a reboot
<WhyNotHugo> Booting an uefi bundle (systemd-stub+kernel+initrd+cmdline) just results in this and then the system reboots: https://pasteboard.co/UAeo9Q4tVuQK.jpg
<Ry_Darcy> @Glanzmann I have applied your 4K boot.bin and rebooted. As you can see, I am still running on this cheap Benz 2K monitor in BE. I will have to wait until tomorrow evening to test this setup on my 4K monitor in ZH.
<enchiladasconpinguino[m]> I guess I can boot it headless without HDMI plugged in at all? reboot for GUI when needed .. or else leave a gentle screensaver going for poor old monitor
<enchiladasconpinguino[m]> if I turn the monitor power off, display signal never comes back on. I have to then reboot the system remotely
<AntoniosPapadakis[m]> if by Arch you mean Asahi Linux on an M1 [Pro|Max] chip, then WiFi should work. Try fiddling around with WiFi on|off switch. It sometimes gets stuck. If that doesn't work, a reboot should sort out the issue

2022-03-23

<AdryzzOLEDEdition[m]> do it in macos then reboot
<clover[m]> maybe every 4th or 5th reboot
<clover[m]> i got some horrible loud metallic sounds through my headphones occasionally when doing soft reboots i.e., `sudo reboot`
<Glanzmann> sven: When I unplugg usb devices, I often get spammed with 'tps6598x 0-0038: cd321x_interrupt: failed to read events' See: https://pbot.rmdir.de/OfE4f99rklj_ncDhreNh8Q until i reboot. Just in case you didn't have that issue seen before which is unlikely.

2022-03-22

<maxung[m]> alden4[m]: I had the exact same error message yesterday. Boot into recovery and in disk utility show all devices, then click on the container (important!) of your main hard drive and run first aid. afterwards reboot and it should work
<Glanzmann> enchiladasconpinguino[m]: I think someone set the brightness from macos and rebooted and the brightness state is unmodifed.
<enchiladasconpinguino[m]> DCP state survives reboot?
<Glanzmann> Ry_Darcy: Run this command as root and reboot. Let me know if your screen works. If it does not work at first. Try to turn the mini off again and on again. This patch works for me on a 2k display. curl -sLo /boot/efi/m1n1/boot.bin https://tg.st/u/rydarcy.bin
<Glanzmann> Ry_Darcy: So, I'll make you a patch ready. You need to install it and reboot and than let me know if it works.
<LuigyLeon[m]> tpw_rules: I must have done something like that, I think I skipped both of those steps x.x. Rebuilding and rebooting after the hardware-configuration
<LuigyLeon[m]> tpw_rules last message for me? rebooting brb

2022-03-21

<j`ey> megalodon42[m]: you should turn the machine off. then when you reboot make sure you hold the power button, dont tap it or anything
<j`ey> anyway sounds like the reboot helped
<nametable[m]> Welp that's sad - ok, rebooting and then trying again
<nametable[m]> Ooh, so maybe I just need to reboot
<clover[m]> does anyone know how to get their headphone jack working? i am on a 2020 macbook pro M1 and rebooting didn't help
<Glanzmann> marcan: Have you seen that? https://1drv.ms/v/s!Ao2g8XS1zhsehf8A9EQBSh1hVLklXw?e=5KAfaX - Mounting the arch rootfs and than rebooting?
<Glanzmann> EvadingEvasions[m]: Everything looks good, but it should not reboot but give you graphical or textual login.
<Glanzmann> opticron: So it should work. Just to make sure, you extracted the kernel, removed the 'status = disabled' lines, build the kernel, build the m1n1/dtb/u-boot object, installed that as /boot/efi/m1n1/boot.bin and rebooted?
<life-the-user[m]> but after creating partitions and mounting and rebooting it didnt work
<enchiladasconpinguino[m]> I did absolutely no changes, just apk add and reboot :)
<enchiladasconpinguino[m]> I just did apk add and reboot, no extlinux config edits
<enchiladasconpinguino[m]> rebooting now
<enchiladasconpinguino[m]> perfect, I will try and reboot .. hopefully back soon heh
<Chainfire> gsora[m]: doh, actually logging out and back in works. The screen said reboot, which I did, and changed nothing. Seems to work now :S
<Chainfire> gsora[m]> yeah reboots and all that
<enchiladasconpinguino[m]> assuming that the VM on USB then reboots successfully with "5.17-asahi", will then boot that USB bare metal

2022-03-20

<marcan> then you reboot and voila
<marcan> and I meant did the macos part of the installer, before the reboot, finish successfully
<johey> I have followed the installation script until until the installation is complete and "press enter to reboot". I press enter. It reboots. Then everything is black. The screen is put to sleep.
<Ry_Darcy_> One last point. After the message "Wrapping up..." and "Installation complete, press enter to reboot"
<M1bn3mar[m]> chadmed: i have to reboot
<RudraSaraswat|btwiusearchandub> j`ey: Is it safe to reboot into macOS?
<chadmed> M1bn3mar[m]: run update-vendor-firmware and reboot
<Glanzmann> And than you reboot into the booted version.
<thewalt[m]> Hello! I tried to erase the partition Asahi Linux from created from diskutility on macOS and when I rebooted I was met with a screen with an exclamation mark and a link to support.apple.com/restore. Any idea
<liott[m]> the like third or so time it asked me to authenticate my password (after partitioning, pre-reboot) it wouldn't work
<doggkruse> I didn't do the minimal install, but to get my wifi working I just rebooted several times

2022-03-19

<SamHep0803[m]> hi, i'm currently having an issue with the installer where when i go into 1TR, bputil fails with the error: "Failed to create local policy". i tried doing "csrutil clear" and rebooting but that hasn't fixed it
<Glanzmann> marcan: 20:37 < beacon[m]> Hey guys, could someone help me, I keep getting the "preboot folder path [path] doesn't exist couldn't set bless data in reboot volume for device" error
<silverocean[m]> Hi folks! Is there a way to turn off the 2 second delay in U-Boot? I tried `setenv bootdelay 0`, then rebooted, but if I runt `printenv`, it's automatically reset back to 2.
<beacon[m]> Hey guys, could someone help me, I keep getting the "preboot folder path [path] doesn't exist couldn't set bless data in reboot volume for device" error
<nicolas17> oh video playback due to audio issues is a thing yeah... on my Linux desktop I once had video in all apps stop working (Firefox, Discord, etc) and I was about to reboot to fix it, it turned out to be something stuck in bluetooth audio, I turned my headset off and everything got instantly unstuck
<joshtau> Hi, I'm using a M1 Macbook Air, and installed asahilinux and it worked great, did a system update (sudo pacman -Syu), it upgraded these packages: https://gist.github.com/joshuataylor/9c8a6021d3c5ccddf97290fdb9d0aec9 , now when I reboot and login it goes to a black screen after showing the KDE spinner, and showing these errors: https://gist.github.com/joshuataylor/da4f18f6b67d5b8db3754c89ff21e38f . Highly doubt that an upgrade bricked
<mps> enchiladasconpinguino[m]: reboot works fine
<enchiladasconpinguino[m]> reboot just hangs, never comes back
<j`ey> reboot should work
<enchiladasconpinguino[m]> bug: machine cannot reboot properly yet? poweroff/halt works
<kode54> macOS Monterey added the setting, but it either doesn't work, or it just forgets to reset it on reboot
<kode54> and actually make the setting stick across reboots
<Ry_Darcy_> Have been running the M1 Mini with Pipcet´s Pearl Linux since last summer with no problems. Yesterday evening, as per M. Glanzmann´s instructions, I installed the Asahi stuff - https://github.com/AsahiLinux/docs/wiki/Debian#soon-to-be-released-asahi-installer. All steps followed to the letter. Result on last reboot, black screen.i.e.no Asahi Linux.
<JohnWells[m]> Is this a good place to ask for install help? `bputil -nc` gave me the error "Failed to create local policy". I also tried `csrutil disable` + reboot with no luck. Thanks!
<rqou_> setting it back to full with bputil -f *does* work, but it somehow reverted back to permissive after some rounds of rebooting
<silverocean[m]> tried to reboot several times
<tpw_rules> that's worrying. try rebooting the machine. i wonder if it's just some fluke
<doggkruse> time to reboot into my new install :D
<tpw_rules> LuigyLeon[m]: but some people have reported that audio is intermittent even if set up correctly and you may have to reboot a bunch
<Retr0id> yeah I almost did a hard-reboot when it happened, which would almost certainly have broken my fs even more...

2022-03-18

<threerik[m]> ill reboot and double check
<george147> I'll have to quickly reboot to linux as I haven't installed an IRC client there yet
<j`ey> it might be a good idea to reboot my host too..
<giskard> I didn't disable filevault. When I rebooted into recovery mode first thing was asking for my password to unlock filevault. I guess that when I exited the "Recovery.app" into Terminal it got locked / unmounted
<tpw_rules> giskard: are you logged in with an administrator account? try rebooting and running it soon after
<marcan> we literally do `shutdown -h now`... if it reboots at that point that has to be a macOS bug :/
<marcan> < zamadatix> Hmm when I do the new installer desktop option after the "press enter to shutdown" it seems to actually do a reboot
<rkjnsn> I've had builds of Chromium completely lock up my system not infrequently if I have other memory-hungry processes running at the same time. I imagine the watchdog on the M1 would turn that into a reboot.
<tpw_rules> possibly, but i wouldn't think that would crash it. i didn't see it reboot, i just heard it
<zamadatix> Hmm when I do the new installer desktop option after the "press enter to shutdown" it seems to actually do a reboot, then fail a bunch, instead of shutdown and allow me to long press the power button.

2022-03-17

<marcan> another reboot and stereo works
<marcan> povik: weird, I rebooted and got only left channel
<Glanzmann> j`ey: I tried 'reboot' and 'halt -p' about 10 times and I can't reproduce the issue.
<Glanzmann> usb broke. I rebooted a few times, still broken usb. Than I did a halt -p and booted again now I can no longer reproduce the issue.
<Glanzmann> I'll reboot a few more times.
<Glanzmann> sven: You'll probably kill me, but ... I once booted the air with the right kernel with the wrong dtb and the right kernel and than rebooted (without turning it completly off). Now I did a 'halt -p' and tuned it on again, and guess what, usb is back: https://pbot.rmdir.de/NaxC4a28g2wRK5XcR99VEg
<Glanzmann> sven: Here is my kern.log same kernel multiple reboots (you can see the jabra headset and than its gone): https://pbot.rmdir.de/43zzHbfzdvxHmRqn_zcPgA
<Glanzmann> And reboot (don't know if the reboot was necessary).
<povik> ah so you are sure you haven't run load-module since last reboot
<Glanzmann> Since i tried the speakers, I rebooted about 20 times.
<povik> try rebooting
<mps_> after blindly typing 'dmesg > dms.2' I've found this in file after reboot with working kernel `simple-framebuffer be206c000.framebuffer: [drm] *ERROR* could not acquire memory range [mem 0xbe206c000-0xbe300bfff flags 0x200]: error -16`
<zv> reboots always fix it.

2022-03-14

<j`ey> hm ok, maybe it's cos sometimes I'm rebooting through m1n1's shell then
<marcan> er, macsmc-reboot

2022-03-12

<zv> weird. rebooted and it came up again. hopefully it doesn't turn into a recurring issue.
<tohatsu[m]> j`ey: just a sec, need to reboot
<Glanzmann> zv: Execute this as root: https://pbot.rmdir.de/yjN2_z1Bir9I1t52fySgUg and reboot for 16k kernel with the curren asahi tree and device tree. I tested this on my mini: https://pbot.rmdir.de/u/fao2DLLMIwrXNOkqIblVTg
<chadmed> it should come back if you reboot

2022-03-11

<milek7> it also once hanged on boot, until watchdog rebooted it
<marcan> I'm not booted but just grep /sys for macsmc-reboot, it has an obvious name
<VinDuv> IIRC macvdmtool reboot is able to start up a MBP from normal$ shutdown
<marcan> also, if you have a PDU/switch and you want to be ultra safe, you could blacklist the macsmc-reboot module (which you might not even have in that kernel); reboot will still work using the watchdog driver as a fallback, but clean shutdown will be impossible at least from linux, which I guess is a good thing for you :)

2022-03-10

<j`ey> which means rebooting into a special mode and running commands etc
<Glanzmann> zv: For me I also never had issues rebooting the mini remotely.
<zv> I can confirm that the installer (after ensuring only free-space was available with nothing else beyond stock layout) worked perfectly. I've put that mac mini in a data center and am confident in its ability to reboot reliably. nicely done all around.
<j`ey> wait, when running the installer from 1tr it doesnt need a reboot to set the startup disk?

2022-03-09

<mofux[m]> also sometimes the login hangs after reboot. and sometimes wlan0 is not there after reboot

2022-03-08

<kov> chadmed, you can probably just rmmod brcmfmac; modprobe brcmfmac instead of rebooting
<chadmed> but its definitely a race because sometimes it actually does work if i reboot enough times
<Glanzmann> chadmed: I see, but I did a lot of reboots on my mini on my air (at least 2-5 per day) and I not once had the issue.

2022-03-06

<Glanzmann> And don't miss the tldr for the soon be released progress report: u-boot max/pro, nvme and spi support, wifi, wifi firmware extractor, smc (battery, reboot, poweroff, rtc), asahi installer (retry downloads, warn user about recovery OS, m1n1 nvme support, robustness), dcp, debian installer, OpenBSD, Asahi Installer for Arch, backlight for 2020 laptops, wip: Audio speakers on 2020 models, stable audio jack

2022-03-05

<Glanzmann> With that, you can turn your tv off and on without the need to reboot.
<David[m]123> Failed to start Hostbame service and GDM on reboot
<pugguu[m]1> And reboot
<pugguu[m]1> Guess I’m gonna have to reboot
<mps> marcan: on my MBP `echo 0000:01:00.0 > /sys/bus/pci/drivers/brcmfmac/unbind' and `echo mem > /sys/power/state` work but don't wake up, have to keep power button 10 seconds and reboot
<David[m]123> You're rigth, weird, I had ping before I rebooted
<Glanzmann> Once you put ssid and psk, reboot
<Glanzmann> reboot time.
<pugguu[m]1> Reboot time
<Glanzmann> zamadatix: Yesterday there was someome who needed several reboots until the adapater shows up. Due to a timeout issue as marcan mentioned. You can also try to the Debian live system, it uses another kernel.
<chadmed> BUT, after hard rebooting, what i had tried to type into the keyboard at sddm appeared in the u-boot console. seems the keyboard got stuck in some state during reset that had it buffering input that got dumped the next time it was probed by something
<chadmed> oh wow cool new beahviour (read: fail mode) for the keyboard: i soft rebooted the machine from linux, and when it came back up the keyboard and trackpad did not respond to input
<chadmed> marcan has changed the installer, you now just need to reboot into 1TR and select the option labelled "Finish Asahi Installation" or something similar
<tpw_rules> you migt have to reboot or remove and reprobe the brcmfmac module

2022-03-04

<pugguu[m]1> It even gave me Debian branded grub on reboot
<pugguu[m]1> Imma reboot it for now
<pugguu[m]1> Hmm Maby a reboot will fix it
<Glanzmann> put your ssid and your psk and reboot
<Glanzmann> And than reboot
<Glanzmann> pugguu[m]1: You can also just reboot and it should boot into Linux and your keyboard should work (at least one of them).
<Glanzmann> I rebooted, (un)plugged the charger a few times and also turned of the backlight, no luck.
<Glanzmann> pugguu[m]1: If everything goes wrong, since you were already in u-boot/grub. You can also just reboot right now. But you won't have the newest device trees and as a result will miss todays features..
<Glanzmann> Than either reboot or wait or poke the interface.
<mps> hmm, when rmmod brcmfmac and press power again it actually reboots
<zimsneexh> j`ey: Okay, I rebooted 4 times with debug and the interface came up 3 times out of 4.
<j`ey> zimsneexh: would be good to do a few reboot cycles with and without debug

2022-03-03

<Glanzmann> zimsneexh: Out of curiosity, on which m1 machine did you isntall it? Have you tried rebooting?

2022-03-02

<j`ey> when you rebooted into 1TR, what did it say under the asahi icon?

2022-02-28

<ChristianvonElm[m]> Hi, im currently trying to do single stepping by setting mdscr.ss, mdscr.mde and spsr_el1.ss in the kernel under the hypervisor, but it crashes with an unrelated exception in the Hypervisor reboot function, is there something simple I'm currently missing?

2022-02-27

<marcan> you should use u-boot unless you're just doing tethered testing or you fancy rebooting into 1TR and doing the kmutil dance every time you change your kernel
<j`ey> you can't do the USD PD reboots with it, like you can with the serial / second m1
<marcan> heck, we can probably do a fun hack where we let the boot picker provision the new boot volume, then *break* it so the next reboot is into 1TR in the right partition (pretty sure iBoot doesn't care about the version plists etc), but the (still incomplete) volume doesn't even show up yet

2022-02-25

<VinDuv> weird, I tried after switching the filesystem to read-only, and it still failed but tune2fs added a "(and reboot afterwards!)" at the end of its error message

2022-02-23

<Glanzmann> sarah[m]: Sure. u-boot max/pro, nvme and spi support, wifi, wifi firmware extractor, smc (battery, reboot, poweroff, rtc), asahi installer (retry downloads, warn user about recovery OS, m1n1 nvme support, robustness), dcp, debian installer, OpenBSD, Asahi Installer for Arch, backlight for 2020 laptops, wip: Audio speakers on 2020 models, stable audio jack output 2020 models, stable audio input capture

2022-02-22

<sven> it has USB in its name and the wire signals are beyond cursed (seriously, look up how complex it is for what feels like a glorified uart) but other than that the reboot command has been pretty reliable
<sven> but it’ll emulate the serial console as another usb serial device and you’ll be able to quickly reboot the machine with a Python command
<Glanzmann> zv: Or you have another mac and can use macvdmtool to reboot the mac.
<zv> in a tethered configuration, if some exception occurs then /dev/ttyACM0 might disappear on the host. disconnecting and reconnecting the USB cable seems insufficient to resurrect it, and only rebooting the mac appears to work. is this the only solution?
<Glanzmann> mps: But to be honest, even as experienced user, I prefer the dd approach. because it takes me 10 seconds to install Linux (of course setting up the stub and rebooting in 1tr also takes a little bit of time especially if you don't get it right the first time, like I always do).
<Glanzmann> povik: Before that I had no audio every other reboot. Now I have audio on every reboot.
<Glanzmann> Okay here is that tldr: u-boot max/pro, nvme and spi support, wifi, wifi firmware extractor, smc (battery, reboot, poweroff, rtc), asahi installer (retry downloads, warn user about recovery OS, m1n1 nvme support, robustness), dcp, debian installer, OpenBSD, Asahi Installer for Arch, backlight for 2020 laptops, wip: Audio speakers on 2020 models, stable audio jack output 2020 modes, stable audio input

2022-02-21

<Glanzmann> From the last output you pasted the identifier of the stub partition was disk0s3 but that can change after you reboot.
<Glanzmann> And than after rebooting u-boot was gone?
<Glanzmann> immychan[m]: I had also a few times. I needed a reboot. But could not reproduce.
<Glanzmann> Maybe change the startup disk to the macos, reboot and try again.
<Glanzmann> immychan[m]: I would reboot into macos and try it again.
<Glanzmann> zv: For me it happened a few times. (mac mini going black after reboot from u-boot.bin kmutil thing) - I always power it off and on again and everything works.

2022-02-20

<zv> jannau: this is the reboot right before step2.sh, after the step 2 heading in the developer quickstart guide
<jannau> zv: after executing step2.sh and reboot? do you see the asahilinux logo if power the mac mini on normally?
<zv> hello, anyone experience mac mini going to a black screen immediately after flashing "Options" (after the reboot in step 2) ?
<David[m]123456789> s/followed the debian installer video but when I rebooted, there were a simili 2 flashes of the Apple logo then I entederred recovery which says tha amy custom kernel was not able to boot and then proposed to change my startup disk with only Machintosh HD available (which I did), there is still no more available asahi available as startup disk/followed the debian installer video but when I rebooted, there were 2 flashes of the Apple
<David[m]123456789> followed the debian installer video but when I rebooted, there were a simili 2 flashes of the Apple logo then I entederred recovery which says tha amy custom kernel was not able to boot and then proposed to change my startup disk with only Machintosh HD available (which I did), there is still no more available asahi available as startup disk
<tpw_rules> i think if you try to delete them with diskutil it will let you, but force you to reboot into recovery mode to install the os again

2022-02-19

<Glanzmann> Than run the grub commands from quickstart.txt and reboot that's it.
<Glanzmann> povik: Can I reboot the target, than I'll take a screenshot.
<Glanzmann> As you can see it worked later when I switched to the usb-a. But it messages which are above are all from usb-c tries. I tried several times by rebooting the air.
<Glanzmann> sven: https://pbot.rmdir.de/jVYHqmxczhWTAXWvcR-Ngw https://pbot.rmdir.de/yy_bARGOSDLL3vSKtT4WcQ I rebooted the air with the m1n1 multiple times.
<tpw_rules> grr, something is unstable. i keep having random hangs and reboots. i assume there is a watchdog cause i don't see a kernel panic
<Glanzmann> povik: I don't know if you do, but you could run the kernel in the hypervisor, than you can reboot without my help.
<tpw_rules> Glanzmann: you can type `reboot` into the hypervisor console
<Glanzmann> povik: Should I reboot?
<axboe> brb, time to reboot into new kernel
<mps> lets reboot
<Glanzmann> Also something hangs for me on reboot, have to find out what though. Will report if I find it. It has something to do with the new kernel.

2022-02-18

<David[m]123456789> * Due to a network outage it failed but still installed itself, I then later installed it properly and rebooted on what I though was the correct install
<David[m]123456789> * Due to a network outage it failed later but still installed itself, I then later installed it properly and rebooted on what I though was the correct install
<David[m]123456789> <jmr2> "OK. Any idea why there were 2..." <- Due to a network outage it failed later but still installed itself, I then later installer it properly and reboot on what I though was the correct install

2022-02-17

<Glanzmann> mps / kov / joske: Does audio still work for you? I rebooted twice, everything looks like it should work (alsamixer, pavucontrol) but no sound.

2022-02-16

<Glanzmann> I also compiled a kernel and rebooted ...
<Glanzmann> David[m]123456789: Have you tried to reboot and run the installer again? Or have you tried to run it from 1tr?
<joske> I still reboot into macOS for youtube ;-)
<kov> I tried rmmod -> suspend and it rebooted heh

2022-02-15

<jannau> missing reboot and rtc, strange
<jannau> can you test on the mac mini? how does it not work? it reboots?

2022-02-14

<j`ey> alxsh requires a reboot

2022-02-12

<NightRaven[m]> i will try PARTUUID after the reboot
<NightRaven[m]> i will reboot now thanks

2022-02-11

<mps> ok, will reboot then
<Glanzmann> And extract it in /lib/firmware and reboot

2022-02-10

<Glanzmann> tpw_rules: So I tried your patch and it works, but after installing the m1n1/dtb/u-boot.bin and I said reboot u-boot said something and rebooted twice. The third time when I had my handy recording it worked out of the box. I tried booting again and had no issue. If I see it again, I'll record it.
<Glanzmann> mps: I tested on the mini using a usb-c port. I'll in a few seconds test on air once I can reboot it.
<j`ey> ah-[m]: backlight is provided by dcp I think, so reboot into macos and turn it down a bit :P

2022-02-09

<axboe> j`ey: heh yes. at least reboot works ;)

2022-02-08

<j`ey> ah-[m]: maybe try reboot the host too
<ah-[m]> yep, push the power button for a few seconds and the chime comes on when it boots, should I reboot it harder?
<sven> just to make sure, did you reboot the m1 between trying each cable?
<Glanzmann> Reboot and everything is working.

2022-02-07

<Glanzmann> either reboot or multiple unloading loading should do the trick
<Glanzmann> axboe: If the wifi does not come up, reboot, or rmmod brcmfmac and brcmutil and load them again. I sometimes had to do that twice in order to get wifi.
<landscape15[m]> “Without modules, we would have to build monolithic kernels and add new functionality directly into the kernel image. Besides having larger kernels, this has the disadvantage of requiring us to rebuild and reboot the kernel every time we want new functionality.”
<landscape15[m]> “Modules are pieces of code that can be loaded and unloaded into the kernel upon demand. They extend the functionality of the kernel without the need to reboot the system. For example, one type of module is the device driver, which allows the kernel to access hardware connected to the system.“

2022-02-06

<mps> right, I was just tired and issued reboot while I thought about poweroff
<Glanzmann> mps: reboot worked for me for a long time.
<mps> nice, reboot works with latest smc/work on MBP
<marcan> you can ^C and `reboot` in the hypervisor
<Glanzmann> jeffmiw: RTC works for me on the macbook air. I tested by disabling wifi and rebooting several times, 'date' shows the real time. I did not see anything in dmesg though. dmesg: https://pbot.rmdir.de/rvz9mbw7L4rnmohnYaQ9FA

2022-02-03

<Glanzmann> povik: On third reboot I have sound. But I pressed the boot options but selected Linux.
<Glanzmann> povik: No sound after reboot. Strange.
<Glanzmann> povik: Sound is not working with the jack: https://pbot.rmdir.de/p74IWGNgp5BWB6f-4SPGKw No idea why, everything looks good. Also what I noticed if when I try to change the levels with alsamixer they jump back to different values. But the range there are in I normally hear sound. I reboot and try again.

2022-02-02

<Glanzmann> wrong (like deleting the old stub and recreating it immedately without rebooting).
<marcan> (if it's streamed we'd need yet another reboot there to switch to system recoveryOS after copying the machine owner list to, say, iSCPreboot)
<marcan> e.g. holding down on reboot will get you into options

2022-02-01

<Glanzmann> I see so with the kernel above reboot works on the mini and macbook air.
<st3g4n0[m]> i will still as now.. because i dont need to reboot it.. so not a big problem
<Glanzmann> make sure it is on top of the grub cfg if you're using u-boot. reboot
<j`ey> shutdown isnt implemented, reboot should work though
<st3g4n0[m]> anyone have problems of kernel panic at reboot or shutdown?

2022-01-30

<nsklaus_> would be nice to figure a way to be able to performs tasks like this directly from asahi instead of having to reboot to macos just to have proper access to ios devices
<Glanzmann> With Macos 12.2 and 12.1 stub the hdmi seems sometimes not initialize after reboot. Am I the only one seeing this?
<tpw_rules> so it seems it's faster the first test after a reboot but otherwise it settles down to that 25% number with every subsequent test

2022-01-29

<ChaosPrincess> you can catch it correctly on reboot, if you entered wrong recovery, you probably mistimed the power button hold

2022-01-28

<Glanzmann> Its not the jack putting in after boot. Now it works. I reboot a few more times.
<Glanzmann> povik: I'll reboot a few more times and let you know if I can see a pattern.
<Glanzmann> povik: I just rebooted to try the new kernel and the sound works.

2022-01-27

<kloenk> j`ey: is panic = "abort" the best idea? do you know that? I have a panic handle with wdt_reboot, so maybe this is not required, as it would reboot?
<chadmed> i dont need to reboot into macos for this thing to charge, right?
<klaus> the connection with memory usage in windowserver, is that like many other os component, their memory usage keep growing and growing as long as the os stays up. a reboot fixes it, but that's not a good solution of course
<Glanzmann> newchima[m]: Btw. deleting the only the stub partition works. I just tried that on my air. It reboots three times but than I get the dialog.

2022-01-26

<Glanzmann> newchima[m]: This happened after I rebooted, I'm not making it up ... https://tg.st/u/stubosdeleted.mp4
<Glanzmann> newchima[m]: This is what I did. https://pbot.rmdir.de/6HphN-hACU5k5gCANCsIwA I'll now reboot and record for you my video
<ciggi> my idevicerestore not worked, after initial reboot USB never shows up :(
<Glanzmann> newchima[m]: Yeah, I had that sometimes again, I rebooted or resized again and at some point it worked again. But when you delete under linux, it is not an issue.

2022-01-25

<Glanzmann> j`ey: I paused at some point when I rebooted, sorry.
<j`ey> (you can also cat m1n1+kernel for a non-tethered boot, but then you have to reboot into recovery (1TR) to update the kernel)

2022-01-21

<j`ey> Glanzmann: thats so that m1n1 will boot to u-boot or whatever payload by default, but you can set a bootarg and when you reboot it will boot to the proxyclient instead

2022-01-20

<Glanzmann> ChaosPrincess: Did you try to reboot, povik said it might be just that.
<joske> rebooting to macOS :-)
<povik> my hunch is that it was the reboot that helped, and communication with cs42l83 is simply still not reliable
<joske> disabled pulseaudio and reboot and now I have sound via audio jack :-)
<joske> let me try a reboot
<joske> after setting the volume, reboot?
<Glanzmann> joske: I did this at first, too. After the reboot sound was working out of the box. But I think the first time you have to move these two.
<Glanzmann> The sound was working without modifying the knob after the reboot and it was a little bit loud. So I had move the volume down. The volume and mute keys work.

2022-01-19

<j`ey> Glanzmann: time to reboot into macOS then :P
<Glanzmann> povik: I rebooted, had the headphones in the ear, I heard two clicks when x started.
<povik> Glanzmann: try simply rebooting :)

2022-01-17

<Glanzmann> kov: I tried to reinstall grub on the macbook air and it rebooted afterwards even with the fbaa64.efi.
<kov> it goes through the probing of the NVME and reboots
<kov> hmm it reboots with the patch
<j`ey> kov: I used the m1n1 hv usually, works well to reboot

2022-01-16

<jannau> 0% success rate in ~15 reboots

2022-01-13

<Glanzmann> mps: But basically what I did. I ran the asahi installer till step 2, but do not execute step2. Than I install m1n1+dtbs+u-boot.macho, create two partition (efi and Linxu root) and dd efi and linux root on the partitions and reboot.
<Glanzmann> After rebooting, I'm able to create the filesystem.
<Glanzmann> jannau: I was able to create the efi parition with your command. However when I try to format it with 'newfs_msdos -v efi /dev/disk0s4' it tells me 'Resource busy'. I'll try to reboot.

2022-01-10

<j`ey> jannau: changing the waiting jiffies to 1000 from 500 seems to have helped, will reboot a few more times

2022-01-07

<marcan> you can tell because installing kexts ends up in a magic double reboot on macOS
<marcan> it doesn't get updated from macOS; stuff gets staged and a reboot through recovery in a special mode happens
<marcan> the remaining question is whether they will *also* require two reboots, doing step2.sh again from upgraded rOS

2022-01-05

<ar> i'm not eager to reboot my router as it's, well, my router

2022-01-04

<dcol542> hmm... seems after a restart the interface is gone, so I assume I'll have to wait after every reboot?

2021-12-29

<tpw_rules> all of mine have been "synchronous abort"s with a register dump. you can also use m1n1 to set up an exception trap to halt and put you in the debugger instead of rebooting but frankly it sounds easier to figure out what step you're missing that's causing a crash
<tpw_rules> rose_: if it reboots then u-boot crashed
<rose_> hey, yesterday someone told me that in order to load u-boot, i should use m1n1's run_guest.py. we've tried this just now and it spat out some register reads and writes before talking about a dangerous write and rebooting the machine - is there anything obvious we could be doing wrong here?

2021-12-28

<joske> from reboot

2021-12-27

<marcan> in 11.x we could do the install without any second reboot, but that's no longer possible (for entirely reasonable security reasons)
<marcan> and this is why you need to set the asahi partition as default, then reboot again into 1TR (which will now be the paired version), then run step2
<jmr2> I guess that the per-os ones are in the same partition as the OS they back-up, and they auto-start if the main OS of that partition fails to start, but that you can't really manually select those in the boot picker, but you can choose them prior to rebooting - which is what the asahi installer is doing?

2021-12-25

<joske> technically, yes, you could, but no sound, no chrome, no resolution change (native is a bit too small), no poweroff, hassle to reboot etc