Heat sinking the rack micro-inverters for long term reliability. They are just Cheap 12VDC models that likely won't last long. I opened them up for inspection, they have proper fuses and AC line filtering but heat sinking was minimal with just the case at full power.


A little thermal compound and a DIY holding bracket for the other end to keep them in good contact.

 

How awesome is it that we Linux users can debate the inanity of how our boxes boot.

Try to have such a discussion with the powers-that-be in Redmond.

 

End of 10.

 

How awesome is it that we Linux users can debate the inanity of how our boxes boot.

Try to have such a discussion with the powers-that-be in Redmond.

It's click-bait for Linux fan boys.

SystemD sucks for embedded or servers. I do care a lot about init system because a lot of what I do happens then. I need something that's totally transparent and doesn't try to fix it self every time it boots, and doesn't need cryptic commands to fix it when it randomly stops booting, something that happens far to much with a SystemD init based system. I write things that crash the kernel, modules and driver. With SysVInit, worse is better. "Works for me".

I want and do have a choice in the Linux world.

 

Now Redmond users can feel right at home on Linux!

 

 

View attachment 351710

Friends don't let even enemies use SD.

 

> RISC-V Patches for the 6.17 Merge Window, Part 1

No. This is garbage and it came in too late. I asked for early pull requests because I'm traveling, and if you can't follow that rule, at least make the pull requests *good*.

https://lore.kernel.org/lkml/CAHk-=wjLCqUUWd8DzG+xsOn-yVL0Q=O35U9D6j6=2DUWX52ghQ@mail.gmail.com/

If you write the code out as "(a << 16) + b", you know what it does
and which is the high word. Maybe you need to add a cast to make sure
that 'b' doesn't have high bits that pollutes the end result, so maybe
it's not going to be exactly _pretty_, but it's not going to be wrong
and incomprehensible either.

In contrast, if you write make_u32_from_two_u16(a,b) you have not a
f%^5ing clue what the word order is. IOW, you just made things
*WORSE*, and you added that "helper" to a generic non-RISC-V file
where people are apparently supposed to use it to make *other* code
worse too.

So no. Things like this need to get bent. It does not go into generic
header files, and it damn well does not happen late in the merge
window.

 

 

Don't take it from me, take it from him!

BTW, I've given up on Ubuntu with their move towards Snap everything (i.e. they own your experience -- not you).

Pure Debian from now on.

 

I upgraded my testing server to Trixe. (with a custom Linux kernel)

[ 0.000000] Linux version 6.17.0+ (root@hpha) (gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #5 SMP PREEMPT_DYNAMIC Thu Oct 9 18:13:28 PDT 2025
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.17.0+ root=UUID=4a52071e-d3c5-422e-a273-8f1a695e7041 ro systemd.unified_cgroup_hierarchy=false systemd.unified_cgroup_hierarchy=1 quiet
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009c7ff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009c800-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bddabfff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bddac000-0x00000000bddddfff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000bddde000-0x00000000cfffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fee0ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ff800000-0x00000000ffffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000103fffefff] usable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] APIC: Static calls initialized
[ 0.000000] SMBIOS 2.8 present.
[ 0.000000] DMI: HP ProLiant DL360p Gen8, BIOS P71 05/24/2019


processor: /devices/system/cpu/cpu21
processor: /devices/system/cpu/cpu11
processor: /devices/system/cpu/cpu9
processor: /devices/system/cpu/cpu7
processor: /devices/system/cpu/cpu18
processor: /devices/system/cpu/cpu5
processor: /devices/system/cpu/cpu16
processor: /devices/system/cpu/cpu3
processor: /devices/system/cpu/cpu14
processor: /devices/system/cpu/cpu1
processor: /devices/system/cpu/cpu22
processor: /devices/system/cpu/cpu12
processor: /devices/system/cpu/cpu20
processor: /devices/system/cpu/cpu10
processor: /devices/system/cpu/cpu8
processor: /devices/system/cpu/cpu19
processor: /devices/system/cpu/cpu6
processor: /devices/system/cpu/cpu17
processor: /devices/system/cpu/cpu4
processor: /devices/system/cpu/cpu15
processor: /devices/system/cpu/cpu2
processor: /devices/system/cpu/cpu23
processor: /devices/system/cpu/cpu13
processor: /devices/system/cpu/cpu0

So far it's great but I can't run Home Assistant on it, yet.

 

 

I upgraded my testing server to Trixe. (with a custom Linux kernel)

[ 0.000000] Linux version 6.17.0+ (root@hpha) (gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #5 SMP PREEMPT_DYNAMIC Thu Oct 9 18:13:28 PDT 2025
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.17.0+ root=UUID=4a52071e-d3c5-422e-a273-8f1a695e7041 ro systemd.unified_cgroup_hierarchy=false systemd.unified_cgroup_hierarchy=1 quiet
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009c7ff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009c800-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bddabfff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bddac000-0x00000000bddddfff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000bddde000-0x00000000cfffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fee0ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ff800000-0x00000000ffffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000103fffefff] usable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] APIC: Static calls initialized
[ 0.000000] SMBIOS 2.8 present.
[ 0.000000] DMI: HP ProLiant DL360p Gen8, BIOS P71 05/24/2019


processor: /devices/system/cpu/cpu21
processor: /devices/system/cpu/cpu11
processor: /devices/system/cpu/cpu9
processor: /devices/system/cpu/cpu7
processor: /devices/system/cpu/cpu18
processor: /devices/system/cpu/cpu5
processor: /devices/system/cpu/cpu16
processor: /devices/system/cpu/cpu3
processor: /devices/system/cpu/cpu14
processor: /devices/system/cpu/cpu1
processor: /devices/system/cpu/cpu22
processor: /devices/system/cpu/cpu12
processor: /devices/system/cpu/cpu20
processor: /devices/system/cpu/cpu10
processor: /devices/system/cpu/cpu8
processor: /devices/system/cpu/cpu19
processor: /devices/system/cpu/cpu6
processor: /devices/system/cpu/cpu17
processor: /devices/system/cpu/cpu4
processor: /devices/system/cpu/cpu15
processor: /devices/system/cpu/cpu2
processor: /devices/system/cpu/cpu23
processor: /devices/system/cpu/cpu13
processor: /devices/system/cpu/cpu0

So far it's great but I can't run Home Assistant on it, yet.

I've got two office desktops running so far: one Gnome and another KDE.

Both are pretty seamless, but they are far less "configured" than an out-of-the-box Ubuntu. So, some configuration and package installations are required on each new install to make it comfortable and productive to use.

 

I've got two office desktops running so far: one Gnome and another KDE.

Both are pretty seamless, but they are far less "configured" than an out-of-the-box Ubuntu. So, some configuration and package installations are required on each new install to make it comfortable and productive to use.

I usually run a very lightweight desktop like icewm.

 

Oh, the irony!

 

https://www.abc.net.au/news/2025-10...egedly-misleading-365-subscriptions/105937436

The head of the consumer watchdog has slammed Microsoft, claiming it "deliberately hid" a subscription option from Australian customers.
...
The ACCC said Microsoft misled customers by not disclosing that subscribers could retain their current plans, without Copilot, at their existing lower prices.

"Following a detailed investigation, the ACCC alleges that Microsoft deliberately hid this third option, to retain the old plan at the old price, in order to increase the uptake of Copilot and the increased revenue from the Copilot integrated plans," ACCC chair Gina Cass-Gottlieb said.
...
The regulator said Microsoft's communication with subscribers did not refer to the existence of the cheaper "classic" plans, and the only way subscribers could access them was to begin the process of cancelling their subscription.

This involved navigating to the subscriptions section of their Microsoft account and selecting "cancel subscription".

It was only on the following page that subscribers were given the option to instead move to the classic plan.

MS and AI slop.

...

 

Here is a new, interesting, VM for Linux, distributed under a MIT license.

I've no opinion on it -- just passing along as apropos to this thread for those who are interested.

 

Pure Debian from now on.

Update: I am finding that Debian is far more of a hands-on experience than Ubuntu. Ubuntu runs out of the box the way I want it to, while everything needs to be micromanaged in Debian.

I like not having to deal with the egregious waste of resources that is Snaps, but I am starting to wonder if Debian is worth the effort.

As an aside, does anyone know if there is a way to manage displays so that I can name different configurations and quickly switch between them?

 

Debian is IMO worth the effort is you want reliable compute resources. I've been running Debian for 20+ years in my home and workplace for engineering projects that ran for decades of Debian updates.


It's designed to be stable, not newbie easy or wonderful.
https://wiki.debian.org/DisplayManager

 

Lately i was doing some development for RPI which seem to be based on Debian. hooooollyyyy cow, how many commands i had to enter just to get to a point where it is more or less usable to develop some code that access network port. apparently it does not like anything that is too close to hardware. but it does run nicely. no hiccups or surprises.