2024-10-23

<charnam> i'm going to reboot when i'm ready and see how much the update fixed, but honestly, i don't know how much i'm expecting to change, since i tried restarting ksystemstats after the upgrade (no reboot) and it still gave me the same error

2024-10-21

<russell--> just reporting another weirdness: m1 macbook air 2020, plugged a usb-c docking station, lsusb registered nothing. rebooted, lsusb showed my docking station and attached peripherals
<SimplyCorbett> Did a system update through the software center, 10+ reboots (bootloop) later im in recovery.

2024-10-15

<mbeavitt> but I can't get this change to persist after reboot. I tried adding vm.swappiness = 100 to /etc/sysctl.conf, but on reboot 'cat /proc/sys/vm/swappiness' returns 60, the default value

2024-10-11

<chadmed_> the soft-reboot prequel to deus ex

2024-10-01

<chaos_princess> temporarily create a partition in the free space (does not matter what type as long as it exists), then reboot into recovery and run disk first aid on all involved disks and partitions
<gorbypark> final step of the "partitioning cheatsheet" of resizing blank space just freezes macos, forcing a hard reboot, and the partition isn't resized. I tried it twice`diskutil apfs resizeContainer disk0s2 0` is the command, verified this is the correct partition and that there's free space to expand into. Wonder if this is a macos sequoia 15 thing, maybe?

2024-09-13

<Guest2808> I rebooted into macOS and things seem not-broken at a glance, but curious if anyone else has seen it and ended up noticing something corrupted?

2024-09-11

<leio> linux came up clean from macos soft reboot without monitor being annoying, but still same -EIO for edid stuff in dmesg
<leio> and now with reboot to kernel upgrade, it randomly re-detected again and switched on game mode for me and now the red text looks fine with whatever other settings it changed; I guess that's good for 240Hz EDID, that game mode...

2024-09-01

<chadmed> quaff: install widevine-installer, run it, then reboot

2024-08-31

<allmazz> Why fstab changes not applied? I copied /home data to a new volume, changed /etc/fstab and rebooted, but nothing changed. I still see old mounts in 'df -h'. Why there is such strange behavior, and how to fix it? P.S: I'm doing this for setup LUKS2 encryption.

2024-08-20

<nicolas17> Slendi: I think this was fixed recently, install updates (using a password-less Wi-Fi network, or Ethernet) and reboot

2024-08-19

<JamesB192> Siilwyn: rebooting, pausing GRUB and passing brcmfmac.feature_disable=0x82000 on the kernel commandline was mentioned earlier j`ey the changing the wpa_supplicant version; that is a cargo cultist answer now though.
<Siilwyn> After suspending on my M1 laptop my wifi doesn't connect to any network anymore. I can see available networks but when trying to connect it hangs on the initial connecting state. I have done `dnf downgrade wpa_supplicant` in the past because of the bugged release but also have done an update of all packages since and rebooted a couple times. How can I troubleshoot this, any ideas?

2024-08-11

<chaos_princess> Update to latest kernel and mesa, and reboot.

2024-08-06

<thasti> is there any known wifi regression that I missed? since last reboot, my asahi doesn't want to connect to any wifi network - works fine in macos. asahi kernel is 6.9.12-401.asahi.fc40.aarch64+16k

2024-08-05

<j`ey> arosvall: have you tried rebooting?

2024-08-04

<leio> but that one I need to check with current kernels; meanwhile I'm in a habit of rebooting to macOS and then shutdown from there
<Slendi> I did do a reboot but nothing changed, also tried to manually restart pipewire* services and wireplumber, and restarting the xdg desktop portals
<leio> perhaps after a reboot to recover a bit from any direct alsa usage problems?

2024-08-03

<zirix> That leaves people without the possibility of connecting an ethernet cable in a pretty bad situation. But I must confirm that downgrading to 2.10 solved the issue after a reboot.

2024-08-01

<runxiyu_> can't make it work without force rebooting

2024-07-30

<chaos_princess> reboot to macos run diskutil list, post output

2024-07-28

<chaos_princess> sprokkel: anyway, run the command that janna_u linked, then reboot the system, the command says that it is enough to restart the browser, but it might be wrong

2024-07-21

<Slendi> I'll reboot

2024-07-02

<DarkShadow44_m> Anything else I should do before rebooting?
<PaulFertser> Darkshadow44_m: usually when a new kernel is installed along with it's modules in /lib/modules/ a tool like update-initramfs or dracut or something is called to generate a new initramfs image with the kernel modules for that version. If it failed to do the job you got an error during upgrade, you shouldn't have ignored it but fixed before rebooting.

2024-06-29

* vveapon reboots
<vveapon> alicejustplaying: annoying, I haven't had any flashes since removing the ICC / rebooting. and of course I don;t know which one fixed it :P

2024-06-28

<vveapon> ok disabling colour profile didn't fix my whole screen black flashes :( I'll try a reboot just in case

2024-06-26

<alicejustplaying> I've installed Asahi (fresh) with KDE; did a dnf upgrade; applied an ICC profile; rebooted; now all panels are black and unusable the screen blinks at times; removing the ICC profile setting or rebooting doesn't fix it. Am I missing something here

2024-06-24

<mort_> oh, sorry, it wasn't after the kernel update. I just happened to accidentally change a setting in the web application (by accidentally hitting a hotkey) right before or after rebooting for the upgrade. Still, a website should never be able to cause the cursor to lag, but at least it's not the update's fault

2024-06-09

<runxiyu> PaulFertser: Before reboot, dmesg | head was at 80000 seconds or something
<runxiyu> (I rebooted anyways)
<PaulFertser> No need to reboot for just that.
<runxiyu> Alright, lemme reboot because the system has been running for ages and the dmesg at boot was overwritten

2024-06-01

<runxiyu_> Hi, my system is stuck at "Downloading Packages" after "sudo dnf system-upgrade reboot"

2024-05-29

<vveapon> nothing particularly exciting in journal logs from the crash but on the reboot I see "May 29 19:17:49 samsa kernel: macsmc-reboot macsmc-reboot: PMU logged 1 boot error(s) and 0 panic(s)
<vveapon> odd, I just had a hard lock and reboot while trying to use the KDE screenshot tool

2024-05-27

<flokli> an excellent question. it does work on a thinkpad, but I can reboot this machine to macos in a bit and check
<testirus> rebooted and this happened

2024-05-23

<cy8aer> 6.8.9-10 - the messages like "pipehandler lock not acked, this type-c port is probably dead until the next reboot." do come from the usb stuff to be come or is this a real problem?

2024-05-22

<sprokkel> Oke, rebooting the new kernel on M1 Mac Mini seems safe. No weirdness here.
<sprokkel> Hi, i'm currently updating to the new kernel on my M1 Mac Mini. Is it safe to reboot ? I'm ready about an issue on asahilinux.org about failure to boot.
<iyes> while i still have access to the kernel log, before i reboot
<iyes> there are scary messages in dmesg about usb-c ports being dead until next reboot
<dontdieych> reboot

2024-05-16

<vveapon> anyway I rebooted and removed the .icc config and all is well, but it might be nice to have it working one day

2024-05-15

<pedantic_picto> the trigger was changing enforcing to permissive in /etc/selinux/config and then rebooting. i noticed "dependency failed for selinux-autorelabel-mark.service" but i haven't been able to dig much deeper than just throwing the kill switch

2024-05-14

<jannau> pedantic_picto: which device? did you update before the reboot? edit the kernel command line in grub and remove "rhgb" and add "nomodeset" that should allow you to see more
<pedantic_picto> i'm not sure if this is the right place to ask this question, but after a reboot today i will either see the fedora loading screen (after u-boot) freeze and become unresponsive, or go for a while and then the display goes blank. pulling up the grub menu to boot into the previous image didn't seem to help. has anyone else run into this?

2024-05-10

<nickchan> I have an issue where audio stops working after a systemctl soft-reboot, any ideas?
<billak> just tried to do fresh install and something didn't went well at the recovery after i entered the password and it started updating the policies and after few seconds it rebooted. tried again again the same thing happened. so doing second attempt just to make sure i did everything right.
<alicejustplaying> rebooted to mac
<PaulFertser> LarstiQ: ah, so with NixOS I'm sure the kernel upgrade would have recompiled evdi properly prior to rebooting.

2024-05-09

<sven> I’ve seen the SoC reboot on such cases as well
<iyes> i tried to reboot into macos, and when i tried to connect to the headset from macos, it just didnt work
<fooxi> Rebooting doesnt help. Reinstall?
<fooxi> ... and it persists on reboot.
<maz> sven: I just realised I'm also getting messages that say "[ 4.068348] phy-apple-atc 703000000.phy: pipehandler lock not acked, this type-c port is probably dead until the next reboot."
<fooxi> Do I need to reboot because that b0rked my screen :D

2024-04-28

<cy8aer> So: - boot into the kernel - plug in HDMI - unplug when a picture is on the second screen - reboot -> that works
<cy8aer> (after hot plugging HDMI and unpluging and working, the plugging does not occur a reboot of course)
<cy8aer> jannau: Crazy: It reboots if you hot plug HDMI.
<jannau> yes. so this means failure to reboot could be caused by the display driver
<cy8aer> And now I tested it with HDMI (on a tv) plugged in. There it does not reboot either (no boot options)
<cy8aer> Back again: it reboots with "nomodeset" but not with "apple_drm.noaudio" (the last without "nomodeset", right?)
<jannau> does the laptop reboots with "nomodeset" in the kernel command line? if yes does it still reboot "apple_drm.noaudio"? is with or without using the hdmi output?
<cy8aer> But it compiles without problems. And the "shut down" is ok, until the point where it should reboot. Then it hangs.
<cy8aer> But - I now found out: 6.8.6-4 does not reboot (6.8.6-3 does). Machine shuts down - and black screen, keyboard still alight.

2024-04-27

<fooxi> jannau: After 3-4 reboots it started working again. Not entirely sure why it happened.

2024-04-25

<iyes> I want to try to set up hibernation on my daily driver fedora Asahi system, so that i don't have to close everything when I need to reboot into Mac OS.

2024-04-24

<felixphew> dracut-asahi -3 has hit the repo now and while I haven't rebooted yet, the new initrd looks to not be broken the way the old one was
<jannau> reboots shouldn't be random but time based. that's the watchdog
<felixphew> "Other potential issues are": I was seeing random reboots in initramfs (in addition to the nonfunctional keyboard and occasional loss of display output already documented)
<mort_> During the dnf system-upgrade reboot step, my screen just turns off (though the keyboard backlight is still glowing)

2024-04-17

<PaulFertser> If pink flash is seen does it mean the switch for the permissive mode was actually performed and the script tried to reboot but failed with a SEP exception? I do not know at what point the pink flash happens, is it before the manipulations or after.
<j`ey> rebooting into the wrong recovery shouldnt lead to a kernel panic though
<PaulFertser> Probably somehow you're rebooting in a wrong recovery or something.
<u154ss> I have just done as you said. Please see my previous post - "his is getting complicated... The first phase of the install directly from the macos command line completes, prompts for a reboot, logo appears (macos, Fedora, options). So far so good. Click on Fedora which enters 1TR to continue then the pink flash and abort again."
<u154ss> @all If the installer automatically reboots into 1TR in the second phase of the install, how do I (we) get around that?
<u154ss> @all This is getting complicated... The first phase of the install directly from the macos command line completes, prompts for a reboot, logo appears (macos, Fedora, options). So far so good. Click on Fedora which enters 1TR to continue then the pink flash and abort again.

2024-03-30

<leio> it works just fine after a reboot, solaar sees it again too
<leio> I didn't have solaar see the mouse for a while before already (days) but otherwise it was working until now (rebooted now to get it back)

2024-03-24

<bluetail> so I've setup my unattended access in krfb, and now I reboot. In theory I should be able to connect now, so that I see sddm

2024-03-20

<pitust> hmm, i'll see if it works when rebooting into m1n1

2024-03-17

<kidplayer666> Another reboot with it unplugged solved it

2024-03-14

<mort_> aw asahi-btsync made the keyboard/mouse work in linux but then upon rebooting back into macOS they don't work there, seems I have to re-pai

2024-03-05

<pitust> okay rebooting gets me m1n1 proxyclient over normal usb

2024-03-04

<LarstiQ> I'd tried rebooting with and without the cable attached previously, that didn't seem to matter

2024-02-26

<nicolas17> PaulFertser: I vaguely remember reading that Asahi reboots by setting the watchdog to 0 seconds?
<eldondev> Runtime watchdog is one of the first things I do on systems that can be resilient to reboots.
<PaulFertser> For this argument to be less meaningful and at least somewhat educational, can someone please tell if Asahi has a hardware watchdog that reboots on kernel panic and whether it's activated by default in Fedora? Another question is whether Fedora automatically kexecs a kernel to collect crash dump and save it for later analysis prior to automatic reboot like RHEL does?
<leio> if a watchdog reboots it relatively quickly, it'd be a sudden reboot instead
<PaulFertser> Most PMU ICs will not reboot when someone hold power button no matter for how long. Holding power button usually turns the host fully off eventually but doesn't power it back unless you release and press again.
<eldondev> Right! Even my nontechnical family members will hold down the power button until they get a reboot in that scenario. They definitely call it a crash.
<PaulFertser> Crash is called "panic" in Linux terminology and in that case a distro can often use some machinery to save a crash dump and then reboot (enabled by default in RHEL). Another kind of crash I can imagine is when hardware watchdog forces reboot. Freezing for minutes (and sometimes hours) due to low RAM and then coninuing to run normally is by no sane definition a crash, I'm pretty sure.

2024-02-25

<mort_> with the caveat that I may have missed some discussion because my irc client got sad and I had to hard reboot the VPS (!!):

2024-02-23

<arahael> I haven't rebooted since installing asahi, I should do that at some point, too.

2024-02-22

<j`ey> vmk: that's was the obvious thing I saw missing. but I have to go now, hopefully someone else can help. I would also try a reboot if you havent yet (maybe without eth connected?)

2024-02-13

<linella> hi all, thanks for the great work so far. In the latest blogpost it was mentioned that HDMI is now supported and working, but there are still some issues after s2idle as HDMI output won't power on. As of now, I need to reboot my machine in order to get it working, but I was wondering, is there any way to force the hdmi output to turn on when not connecting? a command to run f.e.?

2024-02-11

<chris> Because if I reboot during the Gentoo well I've obviously wiped the Asahi volume group for Gentoo so can't reboot from that image through GRUB

2024-02-04

<PaulFertser> Rebooting also resets the states of all the firmwares running on the numerous additional CPUs.
<martin2020> I wish I knew a command that could make it try to detect the monitor again without rebooting
<martin2020> hmm yes, rebooting is the only fix I've seen work
<leio> that is unfortunate. Here I have ended up just keeping it on and rebooting in evening or morning to get back - easier than the plugging tries which sometimes took 5 minutes to yield results

2024-02-03

<atomic-bomb123> chadmed: yeah I restarted my compositor and tried rebooting as well after the hwdb reload

2024-02-01

<matthiasvonarx> i was not able to boot the new kernel from grub. Tried to make it default with grub2.mkconfig and with grubby -> 413 should be default but there is still 411 showing after rebooting. Idk looking into it further tomorrow going to sleep now :). Thanks very much for your help anyway.
<j`ey> reboot, once u-boot has finished the countdown, hit esc
<j`ey> matthiasvonarx: have you tried a reboot?
<the_mariner> Installed. Does this require a reboot?

2024-01-31

<gauss_> However, after I've rebooted the system I can't get pass the login screen. Seems like I can't click on anything and I don't get an input box to enter my username/password. Clicking on clock/battery/... in the status bar doesn't result in any action and the only thing I can do is to force shutdown the system. Thus, I would appreciate only help in debugging this :)
<gauss_> Also, I would like to ask for help since I'm having some issues with Asahi Fedora 39 on my MacBookPro M1Max. I've installed the system and rebooted into it. Been working with it for a few hours and everything seemed perfect.

2024-01-28

<kidplayer666> then another reboot and everything works as usual
<kidplayer666> when i rebooted, another apparent hardfreeze right before grub, on the "hit to stop autoboot" screen
<kidplayer666> and had to reboot
<kidplayer666> also, i am supposing that rebooting is a reasonable way to restart the deamon

2024-01-26

<joshheyse> is it possible to change configure the default boot os? Mine laptop defaults to MacOS. Also is it possible to select the os that it will boot into on reboot? Bootcamp had a "reboot into Macos/Windows" option in the taskbar

2024-01-19

<odlg> Is there a known issue with gnome (gdm perhaps) and rebooting after setting keyboard backlight to something above 0 - I have seen gdm getting very slow (taking minutes to show and login) and trackpad only partly working

2024-01-18

<leio> ref: you'll need to re-plug it a bunch then (or reboot)
<ref> nicolas17, yes, exactly.. so far I've only managed to get it going again by a reboot

2024-01-17

<helene> (and the reboot is made clear by the Apple chime)
<helene> well, plymouth is still on screen by the time it self-reboots
<j`ey> btw you said it rebooted aftew a few minutes.. it shouldnt still be in plymouth at that point..?

2024-01-12

<Madokaiii> https://pastebin.com/RfDjyhBP I must say though tas2764 and speakersafetyd never woke up on their own on a fresh install after downloading all package and rebooting

2024-01-06

<psanford> i have occasionally been able to get back to sddm but most of the time i have to hard reboot. sometimes after pushing the power button i see the shutdown terminal messages. (also an m2 air, with nixos and hyprland)
<Tramtrist> didnt reboot
<Tramtrist> no way to reboot without holding down power button
<janneg> Tramtrist: do you have a way to recover the display without reboot?
<j`ey> can you type reboot? wonder if the screen is just bust
<austriancoder> janneg: I have a CS and I can reboot my macbook. now I want to use proxyclient/tools/picocom-sec.sh and/or proxyclient/tools/linux.py

2024-01-04

<knedlik> And of course all works after a reboot... sorry for not troubleshooting further before messaging
<knedlik> Hi, so I have reinstalled Asahi with a larger portion of the disk allocated... and now KrunVM won't stop throwing undefined symbol with passt despite multiple reinstalls and reboots... selinux is disabled... any ideas what I can do to troubleshoot?

2024-01-03

<felixphew> is there an intended mechanism to persist it across reboots?
<chadmed> it is using the sysfs interface. it does not persist across reboots
<felixphew> or is it trying to do something else? I mainly ask because whatever I set there doesn't appear to be persisting over a reboot...

2024-01-01

<odlg> I am running Fedora Remix an M2 Pro. Is it a known issue that HDMI works when just rebooted, but after suspend or similar it does not?

2023-12-31

<stelleg> If anyone else comes across this: the disk utility explicitly specifies it could take hours of the machine being frozen, so probably best to wait and let it work. I did not do this and was able to reboot succesfully, but I may just have been lucky.
<ydalton> yes, but i would like it done like how the asahi installer does it, where it sets everything for you, and all you have to do is just reboot
<j`ey> for a normal PC you'd just partition, then reboot into a livecd or something with an installer
<ydalton> what my idea is is just you download an exe, and it sets up a distro of linux, and then when you reboot, you reboot into that fresh installation of linux

2023-12-25

<ydalton> after this my speakers wouldn't make sound and i had to reboot to fix the issue

2023-12-24

<chaos_princess> not possible unless you want to have to reboot to recovery on every kernel update
<holiday> i will reboot now and see if that fixed anything

2023-12-23

<kidplayer666> Nefsen402: I rebooted and it assumed the swap automatically

2023-12-21

<unixpoet> okay, that's installed, going to reboot to see if that fixes things

2023-12-20

<Fridtjof> alright, i quickly rebooted to check
<unixpoet> I'm also curious about speakers; I just updated my packages, rebooted, and I can adjust volume, but there's no actual output, on an M2 Air. it's listed as supported on the support matrix but there's no actual detail on what I need to do to make it happen
<unixpoet> should I be able to upgrade to fedora 39? I see that it's available to install but I'm not seeing it as available to install via the Discover program. I've tried refreshing and rebooting and it's still not available
<kit_ty_kate> ah, mmh, let me reboot and make sure i'm not saying something wrong

2023-12-19

<Retr0id> if I reboot now, am I gonna end up with an unbootable system? full logs here https://gist.github.com/DavidBuchanan314/488cba9f6b495ebc5e4acdc4ed04a520

2023-12-18

<ydalton> okay, did a full reinstall of the kernel related packages, rebooted, and i have speakers!

2023-12-17

<Tramtrist> yeah it did this time.. put before i rebooted it didnt seem to
<Tramtrist> OK it turned off after lid close after reboot...

2023-12-16

<seb4nih70> okay reboot doesn't help
<janneg> it needs at least restarting wireplumber. a reboot should be the safest option
<seb4nih70> okay, installed it, didnt Change anything, reboot now
<kidplayer666> huh. do you happen to have easy effects active? last time i tried to enable them, the speakers suddenly stopped working until i did a reboot

2023-12-15

<millenialhacker> interesting... I got GPU running on Gentoo. But somehow after reboot plasma doesn't start right away

2023-12-10

<kidplayer666> Gotta reboot into Linux I suppose, otherwise macOS just can’t see empty space
<kidplayer666> I just rebooted

2023-12-07

<kidplayer666> rebooted and its normal again

2023-12-03

<ydalton> rebooting into the new kernel, i see the addition of the dcpext DT node, but it's disabled, as expected

2023-12-01

<j`ey> trying to reboot into a non working state again, trying for the 4th time..
<j`ey> going to reboot until it doesnt show up. I think it's somehow related to the battery charge udev rule I added
<PaulFertser> So, again, better to not reboot and to inspect the state of its dependencies.
<PaulFertser> For troubleshooting it's of course better to not reboot.
<j`ey> im going to reboot a few more times, it does sometimes show up. showed up on that boot, trying again

2023-11-30

<ayke> oh, a third (or fourth?) reboot seems to have fixed this.

2023-11-23

<iaguis> I was playing some music on my BT headphones and when one song finished and the next song started the system completely froze and rebooted in 30s (I guess the hardware watchdog got triggered). I don't see anything on journalctl -b -1. Anybody knows how to get some info on what happens in this case? Maybe pstore or something?

2023-11-19

<j`ey> maybe later, dont feel like rebooting into macOS rn
<zrhoffman> Rebooting with no additional buttons pressed puts me back on the recovery screen
<janneg> what happens if you reboot?
<zrhoffman> When I rebooted, trying to choose startup options gives me the "restore" screen as soon as I release the power button, and I can't seem to get it into DFU mode.
<zrhoffman> I followed the instructions, including after rebooting into recovery, and when it was done, it put me in my previous Asahi Linux install.

2023-11-15

<leio> janneg: I've had some fun display stuff on m1n1-1.4.6 the last couple times when rebooting from macOS. I think it might be from macOS having driven HDMI at 6K before the reboot
<marcan> I'm so tired of rebooting...
<marcan> and a reboot brought it back, I guess something fixed the EAN data

2023-11-14

<frusr> thx for your help, i am gonna reboot to macosx now and try some things with the keyboard :)

2023-11-11

<kallisti> Would anyone share what the default tooling that comes with the arch minimal install is that can be used to connect to a WPA or WPA2 wireless network? I have a single computer RN and no phone, so it's not fun having to reboot to look for help.
<holiday> rebooting now :D

2023-11-08

<nicolas17> (nothing like rebooting a server after an outage and finding boot has been broken for months and nobody noticed... or even remembers what was changed months ago)
<mort_> nicolas17: good news, rebooting worked flawlessly :)
<nicolas17> mort_: you should probably reboot

2023-11-07

<marcan> you could implement kexec by setting some environment/file flags and putting the new kernel/initramfs somewhere in the ESP and rebooting with a flag that tells u-boot to load that instead
<marcan> this is why apple reboots after the boot picker, they *can't* do it any other way
<marcan> too lazy to reboot with debug right now :p

2023-11-06

<leio> yeah, but in theory there could be reboot-persistent in-memory "next boot" thing, but not the case the
<ChaosPrincess> the boot process is not "cold and dark -> picker -> macos", but "cold and dark -> picker -> full reboot -> macos"
<leio> can one do a one-off boot into macos with asahi-bless or whatnot for the next reboot without having to go through the boot picker/recoveryOS?

2023-11-04

<jb1277976> Anyone know what permissive mode is? I rebooted and now I'm at the screen in a terminal
<ivabus__> Hi, after an unsuccessful attempt to install Asahi (overflowing /System/Volumes/iSCPreboot), running the script alx.sh/cleanbp, and attempts to upgrade to 14.1 (I didn't notice, it was available before I tried to install Asahi) my MacBook Air J413 started randomly rebooting during the macOS update (while "Downloading macOS Sonoma 14.1", the crash log says about the SEP panic). Can I do something to it fix it?

2023-11-02

<what> MacOS started even after a reboot
<holiday2> reboot the mac fisrt

2023-10-31

<alain68> to remove asahi i did a "diskutil eraseVolume JHFS+ drive /dev/disk0s4" then within the diskutil graphical tool i remove the different partition so that they are merged back and i rebooted the mac... i tried to do what was told in this youtube video https://www.youtube.com/watch?v=nMnWTq2H-N0
<alain68> my wife let the old MBP fall down, i replaced the screen (myself) but it was not as good as the default one and later it had some random reboot... maybe a false contact . Anyhow it battery also seems to die (after 8 years... ) so i went for the easy solution ;)
<alain> Hi All, just a small question, if i found a small bug, is there any place to tell it ? (i set the brightness to 10%, reboot and the brightness is like 30%)

2023-10-25

<axboe> no idea why my boot.bin just causes a reboot then

2023-10-18

<frekko> j`ey: still getting errors with these changes applied via command line or in etc/environment and reboot: http://paste.bingner.com/paste/ncg6m

2023-10-16

<kidplayer666> only after a reboot

2023-10-15

<leio> janneg: this IOP spam on screen and smaller resolution happened also with 1.4.3 without changes - when I rebooted instead of shutdown and cold boot

2023-10-14

<eldondev> Ok, I will just reboot to macos and try the fedora version of the curlsh
<j`ey> reboot :)

2023-10-13

<eldondev> Some systems have the concept of "boot this other system only the next time", I was wondering if it would be possible to do that with asahi and macOS, where I can ssh into asahi and reboot into macOS, or vice versa.

2023-10-11

<kidplayer666> Bout to reboot
<janneg> if the files are missing, run `sudo asahi-fwupdate` and reboot
<cozydeer> nice it rebooted into lightdm by default!
<cozydeer_> i'll reboot and see what happens
<ah-> finally no more rebooting for zoom calls

2023-10-10

<i509vcb> hmm I grabbed a fedora workstation iso, pointed at it with usbboot and it seems that it said resetting cpu and then just rebooted
<i509vcb> I thought that update-grub and reboot would have been the best solution but clearly not

2023-10-08

<janneg> you need to add /usr/bin/appleh13camerad from recovery/macos to /asahi/all_firmware.tar.gz on the ESP, run asahi-fwupdate and reboot

2023-10-06

<DannyB> and it should require nothing but some dtb changes and a reboot

2023-10-05

<maz> eh, even my SO says "the wifi is down" when I reboot the fibre gateway (and the APs are up...). I pretend I don't understand...

2023-09-28

<pitust> ill reboot, try the new kernel
<pitust> and i had one flicker in macOS, right after rebooting from asahi

2023-09-19

<ydalton> then a week ago i did `systemctl soft-reboot` one too many times and now it's capped at the louder volume
<i509vcb> Too loud? I do notice if I reboot I have to replug since it's silent
<ydalton> if i rebooted with the headphones plugged in it would be too loud
<u154s> @jannau this is my DetectSpeaker.conf now - https://paste.debian.net/1292444/ I still have no sound - have I overlooked something or done something wrong? Obviously, a reboot since the weekend. TIA.

2023-09-18

<pitust> returns -ENOSYS until i reboot into the new kernel ig

2023-09-17

<jannau> on the m1 mac mini yes, on other devices not. no need to reboot, restarting wireplumber should be enough

2023-09-15

<yuey> frustrating, i spent one hour to install a 12.6, and use softwareupdate balalabal 12.6.8. After reboot, it's 12.6.9, and Apple doesnt provide a KDK of 12.6.9:'(

2023-09-14

<i509vcb> Even with the instabilities of agxv, I don't find myself needing to reboot much anyways

2023-09-07

<marcan> j`ey: that's for serial only, normal m1n1 proxy stuff doesn't need anything and macvdmtool just for remote reboots also shouldn't
<completenoob> So i have two Apple devices connected with a type C cable on the debug ports: a macbook pro M1 Pro, and a mac mini M2 on which I want to play around with Asahi Linux. My question is do I have to reboot both devices and do the reduced security step, or just the target device (the M2 mac mini) ?

2023-09-06

<ydalton> hi, there is a problem/bug with the headphone audio and i think it's to do with the sound codec cs42l84. when i plug in my headphones after booting the macbook, it sounds normal, but when i reboot it with the headphones plugged in, the sound is wayyy too loud. but when i plug it out and plug it back in it's back to normal. is this a known issue or should i file a bug report?

2023-08-29

<_jannau__> did that finish without errors and told you it will reboot the system after pressing enter?

2023-08-27

<danbee> Ah, that sounds like the part I missed. I just rebooted without doing that

2023-08-21

<pounce> then when it reboots, macEACS says 'cannot erase device'

2023-08-20

<nicolas17> that shouldn't survive reboots :)

2023-08-16

<marcan> (for back to linux just reboot, assuming that's still your default boot OS)

2023-08-11

<jack> jannau: thanks for the response earlier, that is very helpful. The workaround I found was that fedora remix enables ssh by default (yay!) but it has PermitRootLogin set to prohibited. Since there is only one user (root) on fedora remix, I managed to reconfigure this file by booting back into macos and using a qemu VM that mounted /dev/disk0s6 (fedora partition) with a fedora live ISO, and then I could modify sshd_config. From there a reboot was all that was n
<handlerug> i've already rebooted and it went away, yeah...

2023-08-10

<marcan> most people probably don't reboot every hour, so I wouldn't worry about that
<marcan> j`ey: as for NVRAM, it's NOR Flash, rated for 100K P/E cycles, split across two NVRAM banks, so assuming you reboot hourly 24/7 and each boot writes to NVRAM once, that'll run out after 22 years
<marcan> (and also when you do anything with m1n1 proxyclient, otherwise after 5 or so reboots you get dumped into recovery)

2023-08-09

<dmitry> Yet some reboot reduction could just help our devs be more efficient overall
<ChaosPrincess> assuming only reboot does a nvram write, and assuming the flash will fail at exactly 100k - 50+ years
<dmitry> Imagine a user needs 5-6 reboots a day (half being macOS, maybe different versions, and half Asahi)
<j`ey> dmitry: how often are you rebooting?
<ChaosPrincess> Dont worry about reboots wearing out your nvram, if something kills it, it will be macos boot logs that it writes there on every boot.
<dmitry> So NVRAM gets written on each reboot once you select a new OS, not only when you change the default?
<dmitry> Is something saved to SSD or NVRAM during that? If so, can some thousand of reboots selecting new os wear out a flash chip?
<stintel> alright, so no need to reboot into macOS to get the installer log :)

2023-08-08

<_jannau__> stintel: you mount ESP in macos, replace m1n1/boot.bin reboot into your uefi-only install which complains about a missing devicetree for your device? after rebooting to macos you determine m1n1/boot.bin is not yours. how do you determine that? by size? by sha156?
<stintel> so I did a m1n1 + U-Boot + ESP install on my MBA15. I'm now trying to replace m1n1/boot.bin on the ESP with the one I built myself (m1n1 + DTB + u-boot), but every time I reboot, somehow the old boot.bin is back... what am I doing wrong?

2023-08-05

<blazra> so, I just rebooted a few times and it seems that the default is still the same, but it seems that macos configures the feedback strength also for the autonomous clicking and sometimes that setting persists across a reboot to asahi

2023-08-04

<marcan> that's weird, unless journals got lost due to hard reboots or something?
<marcan> then timesyncd had some kind of checkpoint with a later time and decided to roll forward, but still several seconds behind (presumably the time it took you to reboot)

2023-07-31

<leio> it's so occasional I can just reboot to OSX or something for it, just... one day directly would be nice :)

2023-07-30

<amarioguy> sven: mainly just the whole way it has to set the next boot partition and then fully reboot to do it, instead of having iboot render the UI for the bootpicker, and set the variables then and there followed by booting lol
<ChaosPrincess> set a special linux as default, then have it set boot-next based on user input and reboot
<BenTheTechGuy> I was simply wondering if it was possible to do it without rebooting
<jannau> you have to reboot to boot a different os, even the boot optioons boot picker does that
<j`ey> yeah, so do this and then reboot
<BenTheTechGuy> Is it possible to reboot into an OS after being booted into a different one? It would be great if I could somehow choose between macOS and Linux at startup instead of having to hold down the power button to get into 1TR every time I want to use macOS.

2023-07-26

<Retr0id> this is a classic case of not having rebooted since my last kernel update

2023-07-20

<asdf> Can i somehow reboot it from this support.apple.com/blabla screen into DFU via software?

2023-07-15

<ChaosPrincess> yes, it does, if you want to mark it as primary, reboot into macos and use the startup disk menu in settings

2023-07-10

<leo60228> equivalent to `systemctl reboot --boot-loader-entry=$ABC` on EFI (i assume that might work if dual-booting multiple distros, but not for macOS)
<leo60228> is it possible to reboot between linux and macos without physical access?

2023-06-30

<nicolas17> so rebooting and running memtester again might work on a different subset of memory
<nicolas17> oh also, on my desktop PC I noticed memtester gave errors at a consistent address, but if I rebooted, that address changed, or sometimes it found no errors at all, I suspect some ASLR was going on and sometimes the bad memory ended up in use by the kernel or something, so it couldn't get tested, and rebooting shuffled it around

2023-06-26

<jannau> dyanchapell: was that after an update of kde/qt packages (without logout or reboot)? if yes, than it's something which might happens after updates
<karpouzi> did you try rebooting dyanchapell? i saw this last week
<karpouzi> gosh, they want like five reboots to enable one userspace filesystem
<karpouzi> i suppose some reboots are acceptable

2023-06-22

<TheDcoder> folks how do I reboot into Linux? I forgot

2023-06-19

<seb91nihel> sorry to interrupt your conversation :) ...but I did the 500+ package update on m1 macbook pro, and after the next reboot grub complains about not finding linux-asahi-edge

2023-06-17

<sequencer> does any one encountered the suddenly reboot without any kernel log during a high load(e.g. compiling llvm or ceb)? I'm using Asahi under NixOS.
<BenTheTechGuy> Has the Asahi project developed a way to select a startup disk from within Linux? I have Linux as my default boot option, but I want to be able to remotely reboot into macOS from Linux, which isn't possible if I have to physically be there to enter 1TR and select the macOS volume.

2023-06-12

<tabby> hi. after i deleted plasma kde wlan0 started to act weird. i sometimes work sometimes doesnt. i have to reboot until it actually starts working. its annoying. what should i do?

2023-06-10

<alxdrl> still, the watchdog kicks in and the system reboots

2023-06-06

<Cyrinux9> Hi, after the last update, this is globally good on the m2 air, thx, but I have to reboot after suspend to get wifi back. Restarting iwd and NM is not enought anymore. Also, I feel like my screen/dpms doesnt turn off on suspend now. It was well the case during a moment.

2023-05-31

<i509vcb> What information do I need to get to report a bug I've noticed with wifi. Essentially if I connect to my network at home, the connection works for maybe 10s and then stops working until I reboot the machine. After reboot the same thing happens. This appears to happen with both iwd and wpa_supplicant

2023-05-28

<Zeroine> I'm asking because the installer reboots after a few minutes

2023-05-26

<archiemeng_> Hey guys, after reinstalled some distros on Mac for several times, the installations will always fail at the local policy update stage of step 2 after reboot into the recovery system. When it fails, the screen will flash to pink and reboot instantly. Any advices on troubleshooting?

2023-05-24

<derzahl> i was gonna try rebooting in legacy bios mode, even though i think i tried that before

2023-05-16

<jcm93> letting go of power button when "loading startup options" appears, after which it just shuts down and enters the loop. tried the installer repair and and held it longer, since the installer instructions technically say to wait for "entering startup options", but after a bit it still rebooted and entered the loop regardless

2023-05-07

<marcan> in fact if you run it from recoveryOS having Asahi as the default boot option, it will even avoid asking you to reboot again

2023-05-03

<mps> even some cable/hubs works for me sometimes even they need few tries, i.e. reboots to detect storage

2023-04-28

<marcan> it's just the asahi os firmware so it just bootloops after the first reboot on install, but you can just let it eventually give up and it'll go into recovery
<marcan> SMC has a watchdog, if you crash it it reboots your machine within 30 seconds
<Tolik2000> Well, I know some ways of rebooting easily. ACIO is my faw
<marcan> worst case the thing just locks up or reboots

2023-04-25

<cschutijser> After that the MacBook seems to reboot a couple of times (the Apple logo comes on briefly before the screen turning black; those two things a couple of times), and after that it presents me with the "The version of macOS on the selected disk needs to be reinstalled." screen. If I boot into macOS and run alx.sh again, it tells me the installation is incomplete. Repairing the installation using alx.sh

2023-04-24

<ChaosPrincess> yea, i am rebooting from sddm now, except when i forget
<ChaosPrincess> also, i wish sddm would actually figure out how to not delay reboots by 90s
<ChaosPrincess> well, it fixed that, at least i got to 3 reboots with screen coming up
<ChaosPrincess> please dont tell me its some reboot flakiness :(

2023-04-07

<seb91nihel> Is there a way to reset wifi without rebooting? Does anyone know something about the issue?
<seb91nihel> Hi there, I'm using asahi on a 14" Macbook Pro M1 for 2 month now, the last few days i'm having trouble with wifi, every once in a while it stops working until I reboot the machine. When issuing the reboot command, the following informations are shown:

2023-04-06

<karpouzi> paru -Syu and udevadm trigger seems to have fixed it, let's see if a reboot brings it back
<karpouzi> i must have updated and rebooted at the wrong time
<karpouzi> reboots do nothing; SDDM just doesn't respond to any keyboard inputs

2023-04-05

<jannau> jacksonchen666: should be fixed after another `pacman -Syu` and sddm restart or reboot
<jacksonchen666> jannau: `pacman -S --asdep libinput` didn't seem to change anything (pacman said it was a reinstall). Did try to reboot, still nope.
<jacksonchen666> Having an issue: I recently upgraded my Asahi install, rebooted, and the keyboard & mouse at the KDE login screen doesn't work anymore at all. Not even external mouse/keyboard, and only on the KDE login screen. Everything else (tty at multi-user.target, grub, u-boot) I tested works.