Update: I reset the bios and that fixed the issue.
Update: I reset the bios and that fixed the issue.
This may work in 99% of the cases, but not in my situation since I’ve tried 5 distros and none of them boot. I’m pretty sure there are deeper issues, but they are clearly beyond my level of knowledge.
Good recommendation, but didn’t work. I’m quite puzzled by this problem and it’s much more difficult than I at first thought. I’m pretty sure it has to do with the bios since the computer doesn’t turn off properly and there are many more weird bugs.
I have tried to boot from 3 distros and none of them worked, but a windows USB worked perfectly. I’m thinking that it has to do with the bios. No they are not on the same drive.
Yes, I’m thinking that the bios got corrupted somehow and from what I can tell, it doesn’t matter what linux kernel version I try to run. There is no SGX setting in the bios. I will try to update the bios tomorrow (I already tried once and that hung as well) and will update the thread then. Luckily windows still works.
When I restart the computer, the screen remains dark so I have to shut it down. After I select distro it hangs. When I boot from any live USB I get the error
0.083296] x86/cpu: SGX disabled by BIOS.
0.263311] ACPI Error: Aborting method \_SB.PCI0.SPI1.FPNT._CRS
due to previous error (AE_AML_INVALID_RESOURCE_TYPE)
(20220331/psparse-529)
0.263591] ACPI Error: Method execution failed
\_SB.PCI0.SPI1.FPNT._CRS (AE_AML_INVALID_RESOURCE_TYPE)
(20220331/uteval-68)
0.264837] ACPI Error: Aborting method \_SB.PCI0.SPI2.FPNT._CRS
due to previous error (AE_AML_INVALID_RESOURCE_TYPE)
(20220331/psparse-529)
0.265092] ACPI Error: Method execution failed
\_SB.PCI0.SPI2.FPNT._CRS (AE_AML_INVALID_RESOURCE_TYPE)
(20220331/uteval-68)
It wasn’t the windows update. It happened after a Linux update.
When I restart the computer, the screen remains dark so I have to shut it down. When I select my distro, the screen hangs on that. When I boot from any live USB I get the error
0.083296] x86/cpu: SGX disabled by BIOS.
0.263311] ACPI Error: Aborting method \_SB.PCI0.SPI1.FPNT._CRS
due to previous error (AE_AML_INVALID_RESOURCE_TYPE)
(20220331/psparse-529)
0.263591] ACPI Error: Method execution failed
\_SB.PCI0.SPI1.FPNT._CRS (AE_AML_INVALID_RESOURCE_TYPE)
(20220331/uteval-68)
0.264837] ACPI Error: Aborting method \_SB.PCI0.SPI2.FPNT._CRS
due to previous error (AE_AML_INVALID_RESOURCE_TYPE)
(20220331/psparse-529)
0.265092] ACPI Error: Method execution failed
\_SB.PCI0.SPI2.FPNT._CRS (AE_AML_INVALID_RESOURCE_TYPE)
(20220331/uteval-68)
I have tried different distros, but none work. Interestingly windows still works.
The same has been also said about every tech revolution.
“There is no reason anyone would want a computer in their home." —Ken Olsen, Founder of Digital Equipment
Give it some time, the progress is pretty fast
No and that’s not my point. Fox news is slanted just as much as CNN. I mainly only get my news from Reuters and APnews (not including tech news). I recommend you to look at resources like Media Bias Factcheck or an app called Ground News.
CNN bleh
I just looked at your profile and holy shit, you spam like this everywhere. Just one post is fine, no need to repost it a million times.
In what way is it different from TPB AFK?
Peertube in it’s current form is not a replacement for anyone other than tech nerds and it’s not gonna change unless some real changes are made to how the platform fundamentally operates.
This is just my opinion so correct me if you think I’m wrong. Many of these problems have plagued the site for a while.
I much prefer OsmAnd. Organic maps is too simplistic for my taste.
What
That’s what I’m also doing – using a junk old laptop as NAS and it’s been pretty great so far. What would you recommend for expanding the storage of it? It has a SATA 2.5" port and I believe an nvme SSD slot. From past experience, the bigger 2.5" HDDs are slow and have a high failure rate. Maybe it’s just time to ditch the old laptop.
I mean isn’t it already that is included in the datasets? It’s pretty much a mix of everything.
I fixed it! A bios reset did the trick.