#
#asahi · 2024-01-17 17:14
j`eyhelene: do let us know, maybe leave plymouth disabled for now, so if it does happen maybe you can see some output
#asahi · 2024-01-17 17:10
helenethank you for your time nevertheless; i'm sure the softlock will happen again, but it seems like it'd be a pain to get more than one bit of information out of those; and since i'm the only one suffering from those, might be something wrong with my hardware. hopefully no one else has that issue, as that one looks annoying. thank you!
#asahi · 2024-01-17 16:59
helenesorry about all that :(
#asahi · 2024-01-17 16:59
helenewelp, can't reproduce again even with all flags restored
#asahi · 2024-01-17 16:42
j`eyassuming that s2idle does this.. being able to offline CPUs would help (but we cant do that yet either)
#asahi · 2024-01-17 16:41
j`eyhttps://www.kernel.org/doc/Documentation/power/states.txt is quite verbose, but explains the different options
#asahi · 2024-01-17 16:39
j`eyif you know youre going to leave it unattended for a long time, best to turn it off
#asahi · 2024-01-17 16:39
j`eyFacepunch01: then yeah, not supported yet
#asahi · 2024-01-17 16:39
helenej`ey: just before disabling plymouth it did it around 4-5 times in a row
#asahi · 2024-01-17 16:38
Facepunch01Yeah I mean deep CPU idle like in /sys/power/mem_sleep I don't know the real term for it
#asahi · 2024-01-17 16:35
j`eyonly sleep is s2idle (aka kernel still runs, but not userspace)
#asahi · 2024-01-17 16:35
j`eyif by deep sleep you mean to disk, no
#asahi · 2024-01-17 16:35
Facepunch01I truly couldn't find this, but is there anyway to enable deep sleep on Fedora yet
#asahi · 2024-01-17 16:32
j`eyhelene: how often was it happening before? can you repro again with plymouth enabled?
#asahi · 2024-01-17 16:31
helenemost likely, yeah; i'd like to figure out what, but i fear i might not be {,ca}pable of that
#asahi · 2024-01-17 16:31
j`eyhelene: I mean if it actually is minutes, that means something probably crashed and plymouth was just sat there
#asahi · 2024-01-17 16:31
heleneso far, haven't been able to reproduce it yet with plymouth disabled
#asahi · 2024-01-17 16:22
helene(and the reboot is made clear by the Apple chime)
#asahi · 2024-01-17 16:22
helenewell, plymouth is still on screen by the time it self-reboots
#asahi · 2024-01-17 16:11
j`eybtw you said it rebooted aftew a few minutes.. it shouldnt still be in plymouth at that point..?
#asahi · 2024-01-17 16:10
helenewell, i'm gonna hope the bug doesn't occur only when plymouth is there or when kernel is quiet
#asahi · 2024-01-17 16:10
helenei just have that kind of luck
#asahi · 2024-01-17 16:09
j`eyhelene: esc should show stuff, or plymouth=0 / remove rhgb from command line
#asahi · 2024-01-17 16:09
j`eyhelene: fyi I haven't heard anyone have similar issues
#asahi · 2024-01-17 16:09
heleneand i can't seem to hide plymouth by pressing some keys
#asahi · 2024-01-17 16:09
heleneso i checked journalctl: no logs; removed quiet from kargs, tried reproducing it: i couldn't manage to reproduce it, but i hit another bug causing the boot to halt and eventually restart the laptop by itself after a few minutes, and it occurs during plymouth
#asahi · 2024-01-17 15:16
heleneFedora, GNOME, freshly installed (and with updates installed), no changes from the Asahi installer. I'd presume that's stable
#asahi · 2024-01-17 15:15
PaulFertserhelene: are you running Fedora or ALARM? Also, was it stable with "KDE version"?
#asahi · 2024-01-17 15:15
helenei do wonder if that would be in journalctl, let me check; otherwise i'll try to reproduce it
#asahi · 2024-01-17 15:15
PaulFertserhelene: do you have log or at least a photo of those CPU lockups?
#asahi · 2024-01-17 15:09
helenealso, wrt/ non-tech people using hypervisors: i've seen non-tech (by my definition of "what is a linux" non-tech) use hypervisors unknowingly, by using Windows' WSA or BlueStacks (or alike) to run Android apps and games on their desktops
#asahi · 2024-01-17 15:04
helenehi! i've installed asahi recently (the GNOME version, I tried the KDE one but KDE doesn't work out for me sadly, even though the support is better...); I randomly get watchdog errors on boot (meaning, it doesn't boot) for some hard cpu lockups (the CPU is seemingly random); I'm on a M1 MBAir, is this a known issue?
#asahi · 2024-01-17 11:19
leioI'm getting offtopic though
#asahi · 2024-01-17 11:18
leioor how to make it have access to graphics properly
#asahi · 2024-01-17 11:18
leiorunning in an nspawn with graphics working would feel ideal to me, but I'm not sure it would test properly
#asahi · 2024-01-17 11:17
j`eyleio: best way is to just.. create a disk image and run qemu!
#asahi · 2024-01-17 11:16
j`ey(although that's not upstream yet)
#asahi · 2024-01-17 11:16
j`eyas400: You can use VMs.. with their gunyha hypervisor
#asahi · 2024-01-17 11:06
kidplayer666my bet regarding the qualcom elite is that the whole linux support ordeal is for chromebooks
#asahi · 2024-01-17 10:59
as400They will not even mention that in their materials.
#asahi · 2024-01-17 10:59
as400Might be. But going back to qcom "elite" products. I bet computer vendors will not advertise "no virtual machines" as a feature :P
#asahi · 2024-01-17 10:55
arthat's… a very narrow definition
#asahi · 2024-01-17 10:51
as400I understand tech people being tech by working in it industry.
#asahi · 2024-01-17 10:50
arand what makes them non-tech?
#asahi · 2024-01-17 10:49
as400That's just first thing that comes to my mind.
#asahi · 2024-01-17 10:49
as400ar: for instance, one of my friends wanted to try Linux. So he created a VM for this.
#asahi · 2024-01-17 10:48
aras400: any examples on how they use it?
#asahi · 2024-01-17 10:47
as400ar: I think so, yes. I've seen such people with my own eyes.
#asahi · 2024-01-17 10:47
arwin11 has the vm-based sandbox feature, but even that isn't something people tend to use on their own
#asahi · 2024-01-17 10:46
aras400: non-tech people use VMs? i've yet to see that myself

plus ›