I think I might just have to do a cmos reset because this is annoying af
I think I might just have to do a cmos reset because this is annoying af
Bi even tried 2.4ghz and 5ghz already with no difference, last thing to try is wired ethernet
![[REDACTED]](https://cdn.discordapp.com/avatars/1209538476798902422/6b05b51c6e3709c10a018c13c3241999.webp?size=16)
Tyeah idk whats wrong with your bios
Tlike i said you can unhide grub and regenerate it with a
ujust command so you can have your dual boot shown
Tyeah i dont know
![[REDACTED]](https://cdn.discordapp.com/avatars/1209538476798902422/6b05b51c6e3709c10a018c13c3241999.webp?size=40)
[Ctrl Alt Del to the rescue
[Best keys on the planet
[The thing is grub is already not hidden
[I already hate this h110 eco by msi
KThe cases I saw were the p-state driver failing to load. I think we just remove that patch since it's only a benefiting threadripper anyway and let them merge it themselves in 6.9 or whatever
KSorry for recommending that
Toh
K6.8 is gonna need careful testing anyway on all images @antheas
KSince it needs special patches to gamescope because of the official HDR support using different naming
KSo the current pin strategy is good for the short term
KLet's us do what we need in
:testing
Asure, but maybe its not worth trying to fix 6.7 anymore
[Oh I know the problem now
[Since I can see the display output when I boot up
[It most likely means that it isn’t outputting anything to the hdmi during post
[It’s probably going to the displayport ports
[The bad thing is that my monitor doesn’t have any displayport ports
Ais there a tester group? maybe it'd be a good idea to have stable pinned, and have testers check new kernels, etc, before deploying to stable
Amaybe have testers per-device, etc
Aand a checklist of stuff to check
KThere's no tester group that we can certainly set that up, the kernel testing in the testing branch and then merging into stable is the new design
[Yep I found the issue 100%
Ahhd 2.0 ready to ship
[It’s the first Front usb port causing the freezing
Ai have to write the changelog now rip
KI love computers
[So it’s completely the cases fault
[AWESOME
Aso almost hhd overlay time 
KIt's going to take me a bit to package it since I'm going to be out at scale, but it will happen
KFinally feeling human again tho, so at least I'm done being sick
Ahow do you package appimages?
Aelectron has an rpm option
KYou wanted that electron app in copr, yea?
Ai think you can just install the appImage and set an env variable with the path
Adoesn't have to be through copr
KIf there's an easier way I'm all for it
Ayou can have a ujust for it
KHeck that can just be boilerplate and done as part of the setup script
KWhy make users run a command
Atbh it might be better that way on bazzite, since you'd be able to update the hhd-ui appimage independently if installed to ~/.local/bin
Aits an open source project it should be pacckaged
Ai fixed the local updater
Aunless something has changed, I think you basically pull the latest hhd-ui appImage and then set the env var
HDD_OVERLAY=/path/goes/hereAthat variable is for testing
Abut it'd work for a ujust
