It's been many years since I implemented G.Hn hardware, but if memory serves the chipsets are typically able to split the available bandwidth into 1 or 2 MHz wide bins and choose different symbol densities and FEC levels for each bin. If you have a bin that has horrible reflections, you don't use it at all.
I also recall that the chipsets don't do toning automatically, and so it's up the the management device to decide when to re-probe the channel and reconfigure the bins.
Email me at contact@eyesoffeugene.org. Things are a bit busy the next few days, but we can discuss what's worked for us. Getting a win in one meeting is a long shot, but you never know -- Bend, Oregon also got theirs canceled just the other day!
I'm also spinning up a new team that will be able to more actively help people get efforts started (or keep them going). Their first meeting is coming up this week too.
I'm really hoping that the Linux gaming folks keep making progress on Windows-on-Linux compatibility so that I can transparently and with zero-fussing run any arbitrary Windows application. Unfortunately there's still plenty of professional software that has not been and will never be released for Linux.
The incentives for improving Linux are driven only in part by commercial interests, and those interests are not completely centralized. Windows' fate is entirely in the hands of the current Microsoft leadership, and they seem hellbent on extracting maximum value from their users while ignoring the suffering their "Continuous Innovation" creates.
It's almost as if they want everyone to start looking for the exits, and thankfully Linux is finally at the point in its maturity on desktop to start attracting power users who have no prior experience.
I don't think 2026 is the year of the Linux desktop, but it does feel like we're at the start of a big shake-up in the industry. Once we start seeing the hockey stick pattern in the adoption rates I would expect that more money and developer time will follow to help smooth out the areas where the transition is still difficult, like professional software.
If the heavy WINE support continues, there will never be a Year of the Linux Desktop because all software will continue to be perpetually Win32 -- OS/2 already proved out this path of [full] compatibility.
>OS/2 already proved out this path of [full] compatibility.
it is not the 1980s anymore. majority of apps are for better or worse in the browser or cross platform with electron.
Wine is merely a stepping stone for adoption because some software compatibility is a hard requirement for user to even considered another platform as an alternative, without these user there won't be any native development to begin with proven by the failure of the original steam machine.
Not all software is for consumers and a good amount runs a hardware as a whole product. 2026 will be the year moving from Windows IoT / embedded to Linux as the host OS for the solutions I work on.
Personally, I find software more stable when coding on Linux and making Windows changes after it is operational. Windows takes more work with edge cases than Linux, BDS, and macOS.
Windows treats STDIN and STOUT different between console and GUI. All other OSes that I have worked on threat them the same.
Note my comment was "Linux on the Desktop", not "Linux on Embedded".
It's quite obvious that not all software is for one platform or another. It's just the vast majority of Desktop software happens to be Windows. And if that's what you're writing, targeting Win32 gets you Linux on the Desktop as well as Windows. There's no reason to write a Linux-native version and have to deal with all of the incompatibilities across distros, let alone compatibility issues over time.
That is a subjective statement. We are moving our software off Windows to Linux hosting for our products. Microsoft has made Windows hostile to the embedded market. They are are pushing a Microsoft account over local with their IoT while plugging the hacks too.
It's difficult to compare embedded to desktop. It's not a market Windows does well today with the available alternatives. And yeah, if you're embedded, by definition you're resource constrained so running Wine makes less sense.
Not so with run-of-the-mill desktop software, games or otherwise.
I dislike them not so much in my home area but everywhere else where I have no idea what I'm doing and worry that I'm going to come home to a ton of envelopes full of enormous fines. This is made worse as cash payment disappears.
I got a couple of type-A cards for my AMD FW13 and generally keep one loaded in the laptop for connecting to random junk like flash drives, charging cables for all sorts of widgets (like my bike light or head lamp), etc. I get dramatically more use out of the type-C cards. And in the quite-rare cases where I really need all of the type-C ports, I'll just eject the type-A card and plug directly into the chassis without the interposer at all rather than carry an extra type-C with me.
That said, there have been a few things that have been a bit less than deluxe on my FW13:
- The touchpad mechanical click is just not that good. It is too sensitive to exact pressure and touch location and I find holding it down and dragging to be excessively difficult compared to all other touchpads I've ever used.
- The delete key seems to oxidize and needs a bunch of hard mashing to get it to become responsive. No, it's not sticky or dirty.
- The air intake on the bottom is highly prone to getting blocked, mostly by my legs.
- There's no BIOS option to turn down the brightness or disable altogether the charging status LEDs, and I find that when I travel and can't keep the laptop in a separate room that it's bright enough to interrupt sleep. I've taped over them, but the light leakage from other crevices is still sufficient to be at least mildly annoying. The translucent Ethernet adapter card also acts like a lightbulb.
- The laptop ramps its current consumption from type-C very quickly and seems like it overshoots its target a little bit, and so it is the only device I have that trips out the OCP on some of my bricks.
- There's no BIOS option to artificially limit the charging power, and so I often trip the OCP on aircraft if my battery is not fully charged before plugging in. I don't want to carry a secondary small brick just to use on planes.
- The LCD backlight uniformity and color quality are mediocre, but for my use case I just don't really care that much. For me, this is a portable technical productivity machine and not an art studio, so it doesn't matter.
- The LCD backlight intensity curve is pretty bad. I very-frequently want to have a brightness in-between the lowest and second-lowest settings. I would love to get more control at the bottom and less at the top. It feels like it's linear when it should be logarithmic.
- The speakers suck. So does the volume control. I very rarely go above 10% volume and frequently don't have sufficient control resolution at the bottom. Anything above about 14-16% volume causes something to distort and other stuff to rattle. Luckily I mostly don't consume media, so this is rarely a real problem. But it is truly atrocious.
All that said, I'm generally a pretty happy camper. I look forward to continued improvements from the company over the years.
Could you reach out to support about the delete key? There was a small window of time where a burr on a batch of Input Cover lattices resulted in wearing down the keyboard membrane in that spot: https://support.frame.work
Thanks for the feedback on LED brightness and airplane OCP. That should be something we can improve in firmware.
Thanks, I'll do that! I figured I've had the machine for a while and it was unlikely to be covered by warranty, so I didn't consider reaching out to support. Instead I assumed I'd buy a new keyboard if it ever annoyed me too much.
At some point I actually considered poking around the firmware and seeing about fixing up the PD behavior. But it never quite rose in priority above my many other projects.
I absolutely love that the embedded controller firmware and much of the motherboard schematics are available. It makes it possible to do these little projects should I gather the gumption. That, plus easy and reasonably priced replacement parts availability and easy OS compatibility, are why I got the Framework.
A note to other folks. Don't bother asking customer service about this. They want you to record videos, as if that's a productive use of your time or required to support a product.
As soon as a CSR asks me to record a video, I write off the brand. Maybe Gen Z will tolerate that, but I'm too old for that nonsense.
The actual touch part of the FW touchpad, including tap to click, works just fine. I might be a weirdo for liking mechanical click for dragging (and I dislike the Macbook tactile fakery; it does not fool my finger).
I find it amazing that even with the redistribution subsidy, the resulting electricity is still more expensive than the national average unsubsidized rate. We are just so incredibly good at vaporizing money.
When I had a solar-charged EV, taking transit to SF only made sense if I was going by myself and didn't need to do any transfers. Any additional people or modes and it was always better to drive.
Ultimately the California Legislature and the CPUC (and therefore the governor who appoints them) are at-fault for rates. PG&E is a regulated monopoly, and in-theory the regulators are supposed to drive value for ratepayers. But our regulators simply do not care and do not perform. The legislature has larded a bunch of redistribution onto rates, and burdened the regulator with a bunch of conflicting goals.
The regulator has no accountability to anyone and just rubber-stamps everything the utilities put in front of them, allowing them to skimp on opex (maintenance) in order to turn everything into capex with cost-plus guaranteed profit. This incentivizes making everything as expensive and as brittle as possible.
Either we need to restructure the market to be more competitive, or we need to restructure the regulations and the regulator to be more performant and responsive to ratepayers. We're suffering a ruinous misalignment of incentives and the best the legislature can think of to fix it is to make it cheaper for the IOUs to borrow money.
The regulators also fail to force proper long term maintenance.
IMO the issue is the board is appointed, and it’s just full of political allies.
We should fill boards like this with experts. For example, make a majority of the board be tenured professors of engineering and finance from the university of California with no financial connections to the industry.
I also recall that the chipsets don't do toning automatically, and so it's up the the management device to decide when to re-probe the channel and reconfigure the bins.