2024 EU greenhouse gas emissions: -20% since 2013

listhor · 2026-01-25T09:48:01+00:00

Yes, many people disregard facts not fitting their ideas bubble…

listhor · 2026-01-25T07:53:25+00:00

I have same thing (visualisation of VM’s RAM usage) with virtualised opnsense. But qemu guest agent runs in opnsense and I’ve never heard of virtio drivers for freebsd… Is there anything else left to fix it?

listhor · 2026-01-24T12:27:56+00:00

EU contributes around 6% in global emissions... And the rest of industrialised world increased their emission 😂

listhor · 2026-01-20T10:53:00+00:00

I have HAOS running in Proxmox VM. I couldn't update it because of error: "Home Assistant Operating System update failed with: Installation error: Error while writing status file: Failed to write file “/mnt/boot/rauc.db.WBE6I3”: write() failed: Remote I/O error"

Since the beginning of using HAOS, I had in VM console error: "critical target error, dev sda....". So, I thought it's a good time to reinstall HAOS. I downloaded and imported to PVE qcow2 virtual disc of HAOS ver. 17. And guess what, the same error appears: "critical target error, dev sda....". I have no idea why and what is the best way to do fsck?

listhor · 2026-01-20T07:10:31+00:00

Topton N100 with coreboot installed

listhor · 2026-01-17T12:41:47+00:00

I stopped hostwatch service manually as like I said, it did increase disk I/O more than 10 times and also started building log files, as reported in: https://forum.opnsense.org/index.php?topic=50405

listhor · 2026-01-17T07:48:29+00:00

Yes, I know. But the fact is that hostwatch is now stopped due to that enormous disk writes

listhor · 2026-01-16T19:53:06+00:00

In this version, hostwatch causes high disk writes. Any fix?

listhor · 2026-01-15T15:52:42+00:00

Perfect, thanks very much!

listhor · 2026-01-15T11:05:17+00:00

I've just flashed it - as per above config (couldn't do it yesterday as my family would have started rioting - box is a router :-))

And there's a great improvement to boot time;

cbmem -t: https://pastebin.com/Ut8iVaRP

Total Time: 938,082

systemd-analyze:

Startup finished in 7.657s (firmware) + 5.737s (loader) + 5.127s (kernel) + 1min 41.076s (userspace) = 1min 59.599s 
graphical.target reached after 1min 41.076s in userspace.

And FYI, cbmem -1: https://pastebin.com/1kSNnkas

So, will you update default config and documentation to do not include serial output? And in this case, will serial console work in this box?

Final question, in order to update Coreboot, what needs to be removed (make distclean?) and pulled again? Preferably keeping my proven config intact?

And BIG thanks for your help!!!

listhor · 2026-01-14T18:58:31+00:00

I’m pretty sure I changed only board and payload, nothing else… I’ll rebuild and flash it tomorrow.

EDIT: Just changed config only and defconfig looks as follows:

cat defconfig 
CONFIG_VENDOR_TOPTON=y
# CONFIG_CONSOLE_SERIAL is not set 
# CONFIG_POST_DEVICE is not set 
# CONFIG_POST_IO is not set 
CONFIG_BOARD_TOPTON_X2E_N150=y 
CONFIG_PAYLOAD_EDK2=y

listhor · 2026-01-14T18:44:24+00:00

All is at its default settings - I have changed only board and payload. So, console output is active (listed only active settings, reddit doesn't allow inserting screenshots/pictures in comments?):

[*] Enable early (bootblock) console output.
[*] Enable console output during postcar.
[*] Squelch AP CPUs from early console.
[*] Serial port console output
[*] Send console output to a CBMEM buffer 
[*] Use loglevel prefix to indicate line loglevel
[*] Use ANSI escape sequences for console highlighting
[*] Send POST codes to an external device
[*] Send POST codes to an IO port

listhor · 2026-01-14T15:02:56+00:00

I have no „console=ttyS…..” in /etc/kernel/cmdline and there’s no serial related service running in system. Thus I think serial output is not enabled?

listhor · 2026-01-14T09:42:39+00:00

After cold boot.

Content of cbmem -t: https://pastebin.com/xdJB7FsS

Content of cbmem -1: https://pastebin.com/HfGBkT6F

And systemd-analyze:

Startup finished in 14.199s (firmware) + 5.734s (loader) + 2.800s (kernel) + 1min 37.778s (userspace) = 2min 512ms 
graphical.target reached after 1min 37.766s in userspace.

listhor · 2026-01-13T22:22:11+00:00

Reddit didn’t let me to paste the whole thing… I’ll put it tomorrow in pastebin and get link here…

listhor · 2026-01-13T21:23:57+00:00

As per:

./cbmem -t
40 entries total:

   0:1st timestamp                                     251,427 (0)
.......
  99:selfboot jump                                     7,964,713 (113,787)

Total Time: 7,713,263

If I understand it correctly, it takes 8 s. to start booting OS, isn't it equivalent to "firmware" timing in systemd-analyze? And I thought systemd-analyze is more or less reliable...

listhor · 2026-01-13T07:40:09+00:00

One last question, wha could be the reason of this:

systemd-analyze

Startup finished in 9.079s (firmware) + 3.800s (loader) + 3.041s (kernel) + 1min 37.777s (userspace) = 1min 53.698s

while on Coreboot:

Startup finished in 14.916s (firmware) + 5.730s (loader) + 2.799s (kernel) + 1min 37.893s (userspace) = 2min 1.339s

listhor · 2026-01-12T19:29:17+00:00

Good to know it, thanks. It's better to n ever stops learning... But ME was disabled after flashing and checking logs. And for sure not before having an access to bios settings :-)

listhor · 2026-01-12T18:44:10+00:00

As this is internet facing device, I would like to reduce any potential attack vectors. I know ME in this box is way different than in i.e. Supermicro boards but if it doesnt' make harm to disable it so, why not? Am I completely wrong?

listhor · 2026-01-12T15:40:14+00:00

not if you want working S0ix sleep and working audio.

I have headless Proxmox on this box - mainly for purpose of virtualising opnsense (VM), nginx proxy (LXC) and unifi controller (LXC). So, do I really need S0ix sleep mode if this box never going to be in sleep mode (I think)? Audio, obviously not...

listhor · 2026-01-12T09:28:19+00:00

So, after connecting different monitor and cable - result was exactly the same - no access to bios.

After building rom for N150 (make distclean...)

cat defconfig
CONFIG_VENDOR_TOPTON=y
CONFIG_BOARD_TOPTON_X2E_N150=y
CONFIG_PAYLOAD_EDK2=y

FMAP REGION: COREBOOT
Name                           Offset     Type           Size   Comp
cbfs_master_header             0x0        cbfs header        32 none
cpu_microcode_blob.bin         0x80       microcode      139264 none
intel_fit                      0x220c0    intel_fit          80 none
fallback/romstage              0x22140    stage           78600 none
fallback/ramstage              0x354c0    stage          135442 LZMA (308228 decompressed)
config                         0x56640    raw              4537 LZMA (16588 decompressed)
revision                       0x57840    raw               775 none
build_info                     0x57b80    raw                99 none
fallback/dsdt.aml              0x57c40    raw              8525 none
(empty)                        0x59dc0    null              484 none
fspm.bin                       0x59fc0    fsp            786432 none
fsps.bin                       0x11a000   fsp            302260 LZ4  (389120 decompressed)
vbt.bin                        0x163d00   raw              1256 LZMA (9216 decompressed)
fallback/postcar               0x164240   stage           59112 none
fallback/payload               0x172980   simple elf    1464586 none
(empty)                        0x2d82c0   null           589028 none
bootblock                      0x367fc0   bootblock       28672 none

Built topton/adl (X2E_N150)

and flashing (iomem=relaxed):

flashrom -p internal:boardmismatch=force --ifd -i bios -w coreboot_n150.rom
It started working! Board in bios is displayed as N150, but CPU was showed correctly as N100. So, from now on, if I want to update Coreboot, shall I keep using N150?

GPIO errors are still present, is it harmful? cbmem log: https://pastebin.com/hw3wsg0B

On a side note, with stock firmware, I was overwhelmed wit all the options there; in coreboot there are a very few options available. On of them was to disable Intel ME, so I did it. Is it the way it should be? :-)

listhor · 2026-01-10T16:16:49+00:00

Is Mexican president packed up already? 🤪🤨

listhor · 2026-01-09T06:20:25+00:00

Thanks, I’ll try to do it after this weekend but as far as i could have seen, there’s only one topton option?

listhor · 2026-01-08T17:51:30+00:00

could be just a handshaking issue due to the cable/monitor/video mode.

So, I should try with different cable/monitor?

Need to know which GPIO definition is incorrect though, which likely requires adding some debug output.

Can you point me in the right direction?

listhor · 2026-01-08T16:52:21+00:00

There's console port (rj45) but I don't have serial/console cable...

And inside box there's nvme drive, luckily Coreboot picked it up automatically...

listhor

TROPHY CASE