

Hello from Sifive Hifive Premier P550, Fedora 44, Kernel 7.0, XFCE 4.20
Had a heck of a time trying to get the latest community image to boot. Had to rebuild the DTB, patching it with the one from Sifive. I still haven't got Ethernet working, but I am using wi-fi via a USB dongle.
Chromium + XFCE is a heck of a combo. Really fast.
More information tomorrow (if you want it).
Was I wrong?
EDIT: Website now shows a header to make clear that the reviews are for the C64 Ultimate. Imagine if they had done that from the beginning, or if Chris had asked me what I meant if he didn't understand, without getting sarcy. Anyway, OP below.
-
Sorry that I am breaking the rule about "No AI-generated content". That wasn't me, it's on the Commodore website.
Being serious for a bit now: one of the things I called Chris out on was the fact that the website has these non-clickable reviews right below the phone's image.
To me, it makes it seem like the reviews are for the phone (they are not). There is no way to click on the reviews to read them (it's just an image).
Am I wrong?
Chris replied, none too happy about it, saying I was making serious accusations about their integrity, etc.
But to be honest, while I was definitely sarcy, I don't think I am wrong. It is at the very least "deceiving-by-omission" to not have the reviews linked so that a customer can check what product they were written for.
Nearly all replies to criticism by Chris that I saw had a very negative tone, which I sort of understand, he must have been excited about the launch. But that is not CEO/president behavior.
I don't think you should go after people who have been fans for years because they are at the very least making you aware of a potential issue.
I certainly don't want to pile on the hate, but I do want to know if I am so off-base about these reviews not being optimally placed and referenced.
Challenges when teaching game development in schools?
Hello fellow teachers!
I wanted to find some correlation in our experiences when teaching game development in schools.
Equipment limitations in labs (if they exist), lack of materials, outdated materials, or even stuff like compliance issues or purchase order issues.
My personal pet peeve is having to buy the most amazing GPU just to load up a project (which takes hours). There is just no money for that, and the kids are the ones that suffer.
What has your experience been like? How have you solved the issue?
Thank you for your opinion!
Hey everyone,
If anyone here has tried running Linux on their Surface Laptop 4 AMD Edition, and it's running hot, sluggish, or losing 50% of its battery life on Linux recently, it’s not your distro: it’s a firmware-level "handcuff."
The Technical Issue: Microsoft has recently issued firmware updates (non-revertible) that effectively hide or remove the CPPC (Collaborative Processor Performance Control) ACPI tables. Without these tables, the Linux kernel (specifically the amd-pstate driver) cannot communicate with the hardware to manage frequency scaling or power states.
Essentially, Microsoft has "locked" the hardware’s efficiency so it only works correctly on Windows. On Linux, your CPU is flying blind, leading to massive battery drain and poor thermals. This issue is well documented, and many of us are hitting the same dead end.
What I'm Doing: I've decided to push back. I am currently in the process of filing formal complaints and seeking counsel with:
- The FTC (US): Reporting this as an "Unfair or Deceptive Practice" and a violation of the Magnuson-Moss Warranty Act (intentional performance degradation post-purchase).
- The EFF (Electronic Frontier Foundation): Providing technical logs to highlight how firmware is being used as a "Digital Lock" to stifle OS interoperability.
- A class-action law firm: Inquiring about legal challenges regarding planned obsolescence and software locks that degrade purchased hardware.
Hey everyone,
If anyone here has tried running Linux on their Surface Laptop 4 AMD Edition, and it's running hot, sluggish, or losing 50% of its battery life on Linux recently, it’s not your distro: it’s a firmware-level "handcuff."
The Technical Issue: Microsoft has recently issued firmware updates (non-revertible) that effectively hide or remove the CPPC (Collaborative Processor Performance Control) ACPI tables. Without these tables, the Linux kernel (specifically the amd-pstate driver) cannot communicate with the hardware to manage frequency scaling or power states.
Essentially, Microsoft has "locked" the hardware’s efficiency so it only works correctly on Windows. On Linux, your CPU is flying blind, leading to massive battery drain and poor thermals. This issue is well documented, and many of us are hitting the same dead end.
What I'm Doing: I've decided to push back. I am currently in the process of filing formal complaints and seeking counsel with:
- The FTC (US): Reporting this as an "Unfair or Deceptive Practice" and a violation of the Magnuson-Moss Warranty Act (intentional performance degradation post-purchase).
- The EFF (Electronic Frontier Foundation): Providing technical logs to highlight how firmware is being used as a "Digital Lock" to stifle OS interoperability.
- A class-action law firm: Inquiring about legal challenges regarding planned obsolescence and software locks that degrade purchased hardware.