Auf YouTube findest du die angesagtesten Videos und Tracks. Außerdem kannst du eigene Inhalte hochladen und mit Freunden oder gleich der ganzen Welt teilen.
I recently had an rfid scanner immediately rma-d back that had just been returned to us. The new issue was caused by a setting and not by a defect. I asked our IT/help desk if it WAS a setting that could be changed
“I don’t know. I get the thing, I check these settings, I check those settings, that’s all I know”
😑😑😑
So me and another person are out of our equipment for another couple weeks while the scanner is sent back for “repairs” and the repair people will go “😑 tap tap tap idiots”
(Edit: I know it’s a setting because I talked with the other person who uses it and I explained the issue and he let me know it is something he changes)
And Microsoft is shutting out most third parties in the near future because of Crowdstrike, so Linux likely won’t be supporting Secure Boot in the future, even if someone did want to enable it for some odd reason.
Microsoft’s kicking third parties out of the kernel because of crowdstrike. Secure boot is a completely different thing Microsoft can’t kick people out of.
Do you have any advice for someone that dual boots SteamOS and Windows 10 on a Steam Deck?
I’ve heard online that since SteamOS manually signs keys or something, that if any changes happen to the kernel that later need to be updated by SteamOS, I’d need to re-sign the keys or whatever. Idk I’m not well versed in any of this
I’ve heard it’s as easy as downloading the M$ keys to enable Secure Boot, but I also don’t want to brick my Deck.
Windows 10 support is ending soon so there’s no reason to have it on your steam deck. Steam will stop supporting it sooner after Microsoft does, just like steam does with Apples operating system.
Im fairly certain any legacy hardware that doesn’t have secure boot as an option is going to struggle loading BF6 regardless.
The first two points are not related to secure boot at all.
you think loading my own kernel modules is not related to secure boot? i guess you don’t work in IT then.
Most people who work IT don’t even know what a kernel is, tbf
I recently had an rfid scanner immediately rma-d back that had just been returned to us. The new issue was caused by a setting and not by a defect. I asked our IT/help desk if it WAS a setting that could be changed
“I don’t know. I get the thing, I check these settings, I check those settings, that’s all I know”
😑😑😑
So me and another person are out of our equipment for another couple weeks while the scanner is sent back for “repairs” and the repair people will go “😑 tap tap tap idiots”
(Edit: I know it’s a setting because I talked with the other person who uses it and I explained the issue and he let me know it is something he changes)
It doesn’t matter which kernel modules are used, as long as you have signed those changes before rebooting.
You can’t install most linux distributions with secure boot enabled.
This is outdated information. Linux has supported secure boot for quite a while now.
And Microsoft is shutting out most third parties in the near future because of Crowdstrike, so Linux likely won’t be supporting Secure Boot in the future, even if someone did want to enable it for some odd reason.
Microsoft can’t stop you from signing images with your own keys.
That’s what I do, and it’s almost entirely automated on Linux these days.
Microsoft’s kicking third parties out of the kernel because of crowdstrike. Secure boot is a completely different thing Microsoft can’t kick people out of.
Do you have any advice for someone that dual boots SteamOS and Windows 10 on a Steam Deck?
I’ve heard online that since SteamOS manually signs keys or something, that if any changes happen to the kernel that later need to be updated by SteamOS, I’d need to re-sign the keys or whatever. Idk I’m not well versed in any of this
I’ve heard it’s as easy as downloading the M$ keys to enable Secure Boot, but I also don’t want to brick my Deck.
Windows 10 support is ending soon so there’s no reason to have it on your steam deck. Steam will stop supporting it sooner after Microsoft does, just like steam does with Apples operating system.
Windows 10 commercial is ending, not the LTSC versions. Those are good for another 2-7 years iirc
No, they are killing it unless you pay and extra $30 a month and use a Microsoft account and kill local accounts.
Source?
https://www.tomshardware.com/software/windows/microsoft-no-longer-permits-local-windows-10-accounts-if-you-want-consumer-extended-security-updates-support-beyond-eol-requires-a-microsoft-account-link-up-even-if-you-pay-usd30
Really? Which would those be? So far I haven’t come upon one.
Yeah that simply isn’t true. I use Secure Boot on all my Linux installs - both in the deb and rpm ecosystem system.
Sorry, I read it backwards – we agree, most Linux distributions do support Secure Boot