NetBSD Planet


March 17, 2024

DragonFly BSD Digest Lazy Reading for 2024/03/17

Command line / history is I guess the mini-theme.

Ruben Schade Finally got my ultimate retro KVM setup working!

It took almost a year of tinkering, buying parts, testing, configuring, fixing, cursing, and shouting with excitement, but I now have a KVM setup that finally works, across two decades of computer history from a Commodore VC-20 to a Dell Dimension Pentium III!

We start with this assortment of parts to take signals and convert them to VGA for my KVM, inspected for quality by one of Clara’s Prince Cats. Some of these ended up being replaced or not used.

Photo showing the parts listed below.

Clokwise from left to right we have:

  1. The RetroTINK-2X-Pro, with a Belkin HDMI to VGA adaptor. This box of wonders converts and upscales the S-Video from my 8-bit Commodore machines with zero configuration and fuss. The Belkin converts this to a crisp VGA signal for the KVM.

  2. A DB13W3 connector. This converts the Sun TurboXGX frame buffer card on my Sun SPARCStation 5 to VGA.

  3. The GGLabs CGAtoRGBv2. This converts the EGA signal from my Am386 tower to 15 KHz VGA, which surprisingly my VGA LCD accepts. It might also work with my Commodore 128’s 80-column mode eventually, if I get its VDC working.

  4. A cheap S-Video and Composite to VGA converter (retired). I used this with the Apple //e before I got the ∀2 Analog VGA card. It was fine.

  5. Luis Antoniosi’s MCEtoVGA converter (retired). Worked fine for EGA, but the GGLabs card has no artefacting or fuzziness.

  6. The ∀2 Analog (not pictured). This card generates a VGA signal from any slot on an Apple ][, including my //e Platinum. 80 column colour is not only feasible on this machine now, but it looks stunning!

The next piece was my handsome beige KVM, which I got on eBay for a steal because it had no cables; something I later came to regret! But I finally have cables now.

Photo showing the Master View KVM switch above the NEC APEX 486.

With these connectors, we now have the KVM ports set up like this:

  1. Am386 EGA → CGAtoRGBv2 → VGA
  2. NEC APEX 486 DX2 → VGA
  3. DIY childhood P1 → VGA
  4. Dell Dimension 4100 P3 → VGA
  5. Sun SPARCStation 5 → DV13W3 adaptor → VGA
  6. 8-bit Commodores → RetroTINK → HDMI → VGA
  7. Apple //e Platinum → ∀2 Analog → VGA
  8. Reserved for another upstream KVM? Gulp

And it works! I can press the button on the KVM, or invoke a key command, and jump between DOS 3.3 on my Apple //e, to NetBSD on the SPARCStation, then across to GEM on the 386, then check where my BNSF GP38-2 is up to in Train Simulator on my Dell.

It’s a hornet nest of cables, and I can’t tell you how happy I am now! Well, I guess I just did! Now it’s time to update Sasara.moe with all this stuff.

The Apple //e later in the evening booting into DOS 3.3 via the V2 Analog card and the KVM.

FAQs

More of Clara's Prince Cats inspecting the VC-20.

By Ruben Schade in Sydney, 2024-03-17.

Ruben Schade Finally got my ultimate retro KVM setup working!

It took almost a year of tinkering, buying parts, testing, configuring, fixing, cursing, and shouting with excitement, but I now have a KVM setup that finally works, across two decades of computer history from a Commodore VC-20 to a Dell Dimension Pentium III!

We start with this assortment of parts to take signals and convert them to VGA for my KVM, inspected for quality by one of Clara’s Prince Cats. Some of these ended up being replaced or not used.

Photo showing the parts listed below.

Clokwise from left to right we have:

  1. The RetroTINK-2X-Pro, with a Belkin HDMI to VGA adaptor. This box of wonders converts and upscales the S-Video from my 8-bit Commodore machines with zero configuration and fuss. The Belkin converts this to a crisp VGA signal for the KVM.

  2. A DB13W3 connector. This converts the Sun TurboXGX frame buffer card on my Sun SPARCStation 5 to VGA.

  3. The GGLabs CGAtoRGBv2. This converts the EGA signal from my Am386 tower to 15 KHz VGA, which surprisingly my VGA LCD accepts. It might also work with my Commodore 128’s 80-column mode eventually, if I get its VDC working.

  4. A cheap S-Video and Composite to VGA converter (retired). I used this with the Apple //e before I got the ∀2 Analog VGA card. It was fine.

  5. Luis Antoniosi’s MCEtoVGA converter (retired). Worked fine for EGA, but the GGLabs card has no artefacting or fuzziness.

  6. The ∀2 Analog (not pictured). This card generates a VGA signal from any slot on an Apple ][, including my //e Platinum. 80 column colour is not only feasible on this machine now, but it looks stunning!

The next piece was my handsome beige KVM, which I got on eBay for a steal because it had no cables; something I later came to regret! But I finally have cables now.

Photo showing the Master View KVM switch above the NEC APEX 486.

With these connectors, we now have the KVM ports set up like this:

  1. Am386 EGA → CGAtoRGBv2 → VGA
  2. NEC APEX 486 DX2 → VGA
  3. DIY childhood P1 → VGA
  4. Dell Dimension 4100 P3 → VGA
  5. Sun SPARCStation 5 → DV13W3 adaptor → VGA
  6. 8-bit Commodores → RetroTINK → HDMI → VGA
  7. Apple //e Platinum → ∀2 Analog → VGA
  8. Reserved for another upstream KVM? Gulp

And it works! I can press the button on the KVM, or invoke a key command, and jump between DOS 3.3 on my Apple //e, to NetBSD on the SPARCStation, then across to GEM on the 386, then check where my BNSF GP38-2 is up to in Train Simulator on my Dell.

It’s a hornet nest of cables, and I can’t tell you how happy I am now! Well, I guess I just did! Now it’s time to update Sasara.moe with all this stuff.

The Apple //e later in the evening booting into DOS 3.3 via the V2 Analog card and the KVM.

FAQs

More of Clara's Prince Cats inspecting the VC-20.

By Ruben Schade in Sydney, 2024-03-17.

Pullup 10 [pullup-10 #638] strptime(3): Avoid arithmetic overflow (PR 58041).

March 16, 2024

UnitedBSD Gah! Your tabs all crash! All the time!

Maybe everyone but me already knew this, but I finally solved the every-tab-crashes-every-time problem in Firefox. I normally don't use a time zone in NetBSD; I normally use UTC. That was what was causing the problem. Setting the system time zone to my local time zone causes no tab to ever crash.

It also has the side benefit that poorly written corporate retail websites actually know when their local stores are open or closed. >sigh<

UnitedBSD Battery Data such as Vendor, model

Hello,

I am writing some software in Rust regarding batteries, in hope to maybe make a pull request on upstream starship-battery (rust-battery) for NetBSD support in a few weeks. (it is a side project as I have another job and I am new to rust)
Actually I am even new on NetBSD, but well well Its fun to contribute on nice projects.

My goal on the long term is to have both starship and bottom building natively on NetBSD and why not as a secondary project, change the envstat command execution from macchina and just use the rust-battery integration.

I am trying to avoid at most the use of C libraries with bindings outside of the libc crate, and as such I did not use proplib (on envsys) and used the IOCTL through the *nix crate.

I am now able to read battery data in Rust as I want.

Now I still need to incorporate it into my fork of rust-battery because right now it is just a dirty sole main.rs file.

However, there are some Information I can't find that way such as Battery Vendor and Model, and generally static information.

I now the acpi tables to get these informations are BST and BIF (or something like that) and thats what Freebsd is actually exposing.

I don't know anything about acpi tables and dealing with these seems a colossal work.

I managed to get some kind of battery Id with acpidump but not much more.

I am sure acpi brings some more info but have no idea how to access these data experimentaly even before trying to write a program for that.

Do you think I can parse /dev/acpi with some sort of rust crate ? I did not find an Ioctl for /dev/acpi so I suppose regular file reading and binary parsing is possible.

If any of you is knowledgeable on this; I am very interested.

Cheers

/r/NetBSD Link with -ldl on NetBSD

I am trying to build the latest version of wine (to play Minecraft), and I got everything to work, but at the last stage - linking - it fails, as it can't find the -ldl library.

I checked it, and seems like there is no dl library on NetBSD.

Is there an equivalent or smth that I can make libdl.so symlink to?

Thanks in advance.

submitted by /u/glowiak2
[link] [comments]

March 15, 2024

/r/NetBSD Has anyone gotten LWJGL3 to work?

Hello.

For a long time I wanted to run Minecraft on this fantastic OS. Back in the day I have managed to compile LWJGL2 using modified OpenBSD patches, but this only allows to run <=1.12.2.

Newer versions need LWJGL3, and NetBSD is the only major (one of the big 3) BSD OS, that does not have it; both FreeBSD and OpenBSD have it - FreeBSD got upstream support, while OpenBSD has a port.

Latest wine (9.0 at the moment of writing) can run the windows version of Java and LWJGL, and Minecraft runs pretty smooth on here. But the version of wine in pkgsrc (5.0) is several years old, and Java simply crashes there.

Someone suggested using the Linux compat. I tried, but no Linux version of java works - Adoptium builds get stuck waiting for something, while the port adoptopenjdk11-bin straight up segfaults.

I tried building LWJGL3 myself, but I ran into problems. First I tried to use the official sources, and modified the FreeBSD build.xml to use NetBSD's paths, but for some reason some .o files were actually compiled as LLVM bytecode (!) and the linker failed. Then I tried to use the OpenBSD patched version, with of course paths patched. The result was that it was trying to use some OpenBSD-specific commands, and it failed because they were't found on NetBSD.

Has anyone gotten LWJGL3 to work?

submitted by /u/glowiak2
[link] [comments]
Pullup 9 [pullup-9 #1819] [PATCH] openssl: Avoid buffer overrun in SHA512/256 and SHA512/224 output (PR lib/58039).
Pullup 10 [pullup-10 #637] openssl: Avoid buffer overrun in SHA512/256 and SHA512/224 output (PR lib/58039).
/r/NetBSD Xorg: anyone still using xf86-input-keyboard ?

Hello folks,

since I'm currently doing lots of cleanups in Xorg codebase, I'm wondering where / how much legacy drivers like xf86-input-keyboard are still needed (Linux has entirely moved to either evdev or libinput, the legacy driver doesnt even compile there anymore)

I dont know much about BSD, but I've heared libinput works there, too - so the legacy driver shouldn't be needed anymore and we could drop BSD support here.

Am I correct ?

submitted by /u/metux-its
[link] [comments]

March 14, 2024

UnitedBSD sysctl: operation not permitted

Hi! I'm new to NetBSD but a longtime user of Unix. I have a Dell Latitude 7490 that on Linux requires two kernel options to be set: i915.enable_psr=0 and i915.enable_dc=0. Without these the display driver will crash constantly.

I'm trying to set the same options on NetBSD. I've found there are two sysctl settings that match with these: hw.drm2.i915_modparams.enable_psr and hw.drm2.i915_modparams.enable_dc.

I am able to change the psr one with the sysctl command (and sysctl.conf), but get the following when I try to change the dc one (manually or in sysctl.conf):

# sysctl -w hw.drm2.i915_modparams.enable_dc=0
sysctl: hw.drm2.i915_modparams.enable_dc: Operation not permitted

How can I change this setting at boot?

Thanks!


March 13, 2024

NetBSD Blog NetBSD 10.0 RC6 available!

The NetBSD project is pleased to announce the sixth release candidate of the upcoming 10.0 release, please help testing!
See the release announcement for details.

The netbsd-10 release branch is more than a year old now, so it is high time the 10.0 release makes it to the front stage. This matches the long time it took for the development branch to get ready for branching, a lot of development went into this new release.

This also caused the release announcement to be one of the longest we ever did.

Since RC1 there have been numerous changes, including major updates to external software included in the release: Postfix, OpenSSH, and the firmware used for Raspberry PI devices. Various issues with RC1 have been fixed, including installer (sysinst) crashes. Lots of architecture specific fixes happend, e.g. various toolchain changes for VAX (so it is now finaly self-hosting again), and kernel changes for macppc, netwinder, and alpha.

For RC3 only few (relatively) minor changes were made, including https certificate verification in libfetch (which is used by pkg_ad(1)), and also improvements to the EFI bootloader to better deal with booting from CD (or in virtual machines ISO images), plus lots of various bug fixes.

RC4 became necessary as a few very important DRM/KMS issues especially for Intel GPUs have been resolved. And as an (unexpected) bonus support for the Nintendo Wii has been added to the evbppc port.

RC5 has a few important security related updates of third party components (named, nsd, unbound, wpa_supplicant).

RC6 fixes a few issues with the new named/bind imported for RC5 plus several minor issues.

Especially on amd64 machines please notes that we got a new DRM/KMS subsystem version, and this may lead to fallout on some hardware. Unfortunately not all known bugs from the release engineering pre-release task list could be fixed in time for this release - we will continue to improve the current state and hope to have more of them solved for the next (10.1) release.

If you want to test 10.0 RC6 please check the installation notes for your architecture and download the preferred install image from the CDN or if you are using an ARM based device from the netbsd-10 builds from the bootable ARM images page.

If you have any issues with installation or run into issues with the system during use, please contact us on one of the mailing lists or file a problem report.

/r/NetBSD bozohttpd bzremap

I am having trouble with .bzremap file. I want to use it to hide the perl cgi file suffix .pl. Lets say I have "/test:/test.pl" in it. It never loads test.pl file. Anyone had success with this?

submitted by /u/bubba2_13
[link] [comments]
UnitedBSD sshfs and shotwell

To enable sshfs for regular user on the netbsd,
/dev/puffs and /dev/putter must be enabled to her.
Is there any security risk regarding this?

On the linux I like shotwell. More precisly, I like
how it implements crop, straighten and rotate funcitons.
Shotwell has issues in pkgsrc. I was looking for alternatives,
but could't find something I liked. I tried to use gimp,
imagemagick, fotoxx,... What do you use for image
manipulation?

Thank you

Pullup 10 [pullup-10 #636] Non critial fix for mac68k/sbc(4)

March 12, 2024

/r/NetBSD Welcome to NetBSD 10.0_RC6

Welcome to NetBSD 10.0_RC6! Official announcement should follow.

https://mail-index.netbsd.org/source-changes/2024/03/12/msg150403.html

submitted by /u/ptkrisada
[link] [comments]
Pullup 10 [pullup-10 #635] omnibus /usr/bin/kdump updates
Pullup 8 [pullup-8 #1948] please pullup src/usr.bin/audio via sync-to-current
Pullup 9 [pullup-9 #1818] please pullup src/usr.bin/audio via sync-to-current
Pullup 10 [pullup-10 #634] please pullup src/usr.bin/audio via sync-to-current
Ruben Schade Questions about modding my Blueberry iMac DV

Below is my beloved Blueberry iMac DV, albeit taken at a weird angle and on the floor because I forgot how difficult it is to photograph! It’s basically a giant reflective sphere that messes with focus and colour balance unless you have a really good quality diffused light source, which I don’t! It’s a hard life.

Bad photo of a wonderful machine.

My parents bought this for me for Christmas in 2000 after I couldn’t stop raving about the Macs I was using at school. Its bright colours and friendly OS embodied so much of the optimism and happiness I had during that period of my life, to the point where it still makes me smile looking at it today.

This was a machine of firsts for me. It was the first computer I cut video on, thanks to iMovie and its FireWire ports. It ran the very first Mac OS X betas. My iBook G3 was the first computer I booted a BSD on (NetBSD), but this iMac was the first to specifically boot PowerPC FreeBSD. I started my iTunes library on it that I still maintain today. It was also where I played the most SimCity 3000 and Sims, thanks to Aspyr.

Zzzzzap

Unfortunately, the poor thing hasn’t worked for more than a decade. The CRT was the first component to go, with the picture becoming blurry from the centre before eventually fizzling out. I was able to use an external display for a few more years, until a house move from KL to Singapore in the late 2000s jostled it enough to damage the logic board (2000s Apple parlance for motherboard). There are no signs of life when turning it on now.

I want to do something about it, but I’m a bit unsure how to proceed.

First, I definitely want to get as much of the original hardware working again. This will almost certainly involve pulling it apart and testing as many parts as I can individually. The good news is replacement logic boards don’t seem to be too difficult to find, and I’ve got plenty of RAM sticks to try.

I’m not confident enough with electronics to touch the power supply, so that might be something I source a replacement for if I detect any anomalous voltages. It’s nearing twenty-five years old anyway, so it might be due (and no, I haven’t plugged it into mains in at least four years, so I’m not about to electrocute myself on a cap).

Another option is to gut the machine entirely, and put a more modern PowerPC Mac Mini board inside, then route the cables out the side. This would be a bit of a kludge, but it would let it run classic Mac software in that familiar shell again.

Replacing the display

The CRT is another issue. As much as I love retrocomputers, CRTs give me bad headaches after a few minutes of use now, from expensive Trinitrons to old phosphor units. I can keep the CRT disconnected and use an external monitor with it like I did before, but that seems a bit sad.

Alternatively, a sillier side of me wants to replace it with an LCD panel. This would make the machine significantly lighter and easier to move with, and would mean I could actually use it. The challenge is that the bezel is curved to fit the CRT, which means I’d need to fill the gap between it and the flat LCD somehow. I’ve seen some people print 3D gap fillers with varying degrees of success, but they seem to be highly dependent on the panel you source. As much as it pains me to say, some of these conversions look pretty terrible.

I think I’ve already overthought this, so step zero is just to check if I can get any part of it working again to start. If and when this is done, I can evaluate how to proceed. If you have any ideas or suggestions, I’m all ears.

By Ruben Schade in Sydney, 2024-03-12.

The NetBSD Foundation NetBSD 10.0 RC6 is available!

March 11, 2024

Pullup 9 [pullup-9 #1817] nvme(4): Fix nvmectl(8) after suspend/resume cycle (PR 58025).
UnitedBSD NetBSD ram usage

Hi there,

I'm wondering why NetBSD uses so much ram? I have a NetBSD box and it ran for a couple weeks without a reboot, and it seemed to have creeped up to nearly 8GB of ram, with only 10 MB free. It only has one daemon running outside of the base system, dnetc , so it's possible that that is causing the memory leaks, but I've ran other boxes without it and I've always noticed a disproportional amount of ram usage on netbsd compared to the other bsd's, and it always seems to creep up over time.

I also get differing ram usage amounts depending on which program I use to check it. Neofetch, htop and free all give differing amounts and is never the same.

Pullup 8 [pullup-8 #1947] Fix memory leak in getent()
Pullup 9 [pullup-9 #1816] Fix memory leak in getent()
Pullup 8 [pullup-8 #1946] tun(4): Allow IPv6 packets with TUNSLMODE configured (PR 58013).
Pullup 9 [pullup-9 #1815] tun(4): Allow IPv6 packets with TUNSLMODE configured (PR 58013).
Pullup 8 [pullup-8 #1945] [PATCH] sysv_shm: Avoid overflow when computing kern.ipc.shmmax (PR 57979)

March 10, 2024

Ruben Schade The tiny NanoPi R2S

I can’t remember where I first read about this, but it looks like a cool little box for a router or VPN endpoint:

The NanoPi R2S uses Rockchip’s quad-core A53 RK3328 SoC with powerful performance. Its default frequency is 1.2GHz. The NanoPi R2S has 1GB (or optional 2GB) RAM, dual Gbps Ethernet ports. It uses RK805 PMU chip and supports dynamic frequency scaling. It has one USB 2.0 port that can interface with 4G modules, USB HD cameras, USB WiFi modules etc.

Below is their store photo. The Ethernet jacks give you a visual indiciation just how small this box is:

Images of the motherboard and case for the tiny NanoPi 2RS

It comes with Ubuntu Core, which makes me think it could run FreeBSD and NetBSD too? The machined metal case is pretty swish.

By Ruben Schade in Sydney, 2024-03-10.

The NetBSD Foundation One New Security Advisory: NetBSD-SA2024-001

March 07, 2024

Ruben Schade Running NetBSD 10 Release Candidate 5!

The word exciting is overused thesedays, thanks to unimaginative marketing executives and chatbots. But NetBSD 10.0 is exciting. I remember talking with some of the devs about it at AsiaBSDCon in 2019.

I spun up some arm64 and amd64 QEMU builds on my work machine while sitting at a coffee shop, like a gentleman. I built my usual cgd(8) encrypted volumes, installed pkgsrc, and ran my essential (cough) packages. Don’t forget to install compat9 if you intend to run software built for NetBSD 9.0.

Impressions thus far are very, very good! The maintainers weren’t kidding about speed improvements either. In a world where major software and OS releases come with as much trepidation on my part as interest, it’s wonderful to simply be pleasantly surprised.

I don’t think I’ve mentioned this before, but in addition to some personal servers and retrocomputers, I’ve always had a NetBSD VM on work and personal laptops, and this latest one is no exception. I use it for testing, but also when I need a more distraction-free environment for writing (he says as he blatantly runs PySol). It absolutely screams on arm; faster than macOS has felt in a long time.

NetBSD with Fluxbox remains my other favourite OS combination, and I don’t blog about anywhere near enough. I plan to change this.

My thanks to everyone in the NetBSD Project. I share my sadness at the loss of Ryo Shimizu, and also pay my respects to his memory and family. He made a lasting impression on all our lives. 🧡

By Ruben Schade in Sydney, 2024-03-07.


March 04, 2024

DragonFly BSD Digest March 6 NYCBUG meeting

The March 6 NYCBUG meeting is coming up, and it sounds like something I’d want to see: NetBSD for the Advanced Minimalist, working remote using only a $100 Pinebook.  Be sure to RSVP if you can go cause this is in-person and they need to know who is coming into the NYU facility.


March 02, 2024

Pullup pkgsrc [pullup-pkgsrc #6839] [[email protected]: CVS commit: pkgsrc/editors/nano]

March 01, 2024

Pullup 8 [pullup-8 #1944] netinet6: Avoid NPD on certain inet6 addr configs (PR 53922)
Pullup pkgsrc [pullup-pkgsrc #6838] security/libfido2: Fix NetBSD support (PR 57919)

February 29, 2024

Pullup pkgsrc [pullup-pkgsrc #6837] 2 forwarded messages...

February 28, 2024

NetBSD Blog NetBSD 10.0 RC5 available!

The NetBSD project is pleased to announce the fifth (and probably last) release candidate of the upcoming 10.0 release, please help testing!
See the release announcement for details.

The netbsd-10 release branch is more than a year old now, so it is high time the 10.0 release makes it to the front stage. This matches the long time it took for the development branch to get ready for branching, a lot of development went into this new release.

This also caused the release announcement to be one of the longest we ever did.

Since RC1 there have been numerous changes, including major updates to external software included in the release: Postfix, OpenSSH, and the firmware used for Raspberry PI devices. Various issues with RC1 have been fixed, including installer (sysinst) crashes. Lots of architecture specific fixes happend, e.g. various toolchain changes for VAX (so it is now finaly self-hosting again), and kernel changes for macppc, netwinder, and alpha.

For RC3 only few (relatively) minor changes were made, including https certificate verification in libfetch (which is used by pkg_ad(1)), and also improvements to the EFI bootloader to better deal with booting from CD (or in virtual machines ISO images), plus lots of various bug fixes.

RC4 became necessary as a few very important DRM/KMS issues especially for Intel GPUs have been resolved. And as an (unexpected) bonus support for the Nintendo Wii has been added to the evbppc port.

RC5 has a few important security related updates of third party components (named, nsd, unbound, wpa_supplicant).

Especially on amd64 machines please notes that we got a new DRM/KMS subsystem version, and this may lead to fallout on some hardware. Unfortunately not all known bugs from the release engineering pre-release task list could be fixed in time for this release - we will continue to improve the current state and hope to have more of them solved for the next (10.1) release.

If you want to test 10.0 RC5 please check the installation notes for your architecture and download the preferred install image from the CDN or if you are using an ARM based device from the netbsd-10 builds from the bootable ARM images page.

If you have any issues with installation or run into issues with the system during use, please contact us on one of the mailing lists or file a problem report.


February 27, 2024

The NetBSD Foundation NetBSD 10.0 RC5 is available!

February 25, 2024

NetBSD Installation and Upgrading on DaemonForums NetBSD 10 RC_4 experiences
A few days ago I installed the 4th release candidate of NetBSD on a 32 GB USB 3.0 memory stick.

Install went well and fast. After booting up I installed the Firefox compiled package with pkgin This also went smooth.

I did not have to do anything for the X configuration. But when I started firefox the system became unresponsive (crashed) and seemed to be busy writing a dump file.
Sometimes OpenBSD also shows the same behaviour on this system. Powering off is the only way to regain control.

The system I used is my grumpy HP Proliant server. Linux, FreeBSD and DragonFlyBSD complain that about mixed 32bit and 64bit ACPI data.
The cheap 64bit Xeon CPU has a built-in Matrox VGA processor (mga driver in X Window) and probably uses part of the normal ECC RAM.

NetBSD also mentions problems with the ACPI stuff. It seems to truncate some entries:
The dmesg:
Code:

$ sed -e "s/^\[    /[/" U/dmesg_netbsd10_rc4.txt

[ 1.000000] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003,
[ 1.000000]    2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013,
[ 1.000000]    2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023,
[ 1.000000]    2024
[ 1.000000]    The NetBSD Foundation, Inc.  All rights reserved.
[ 1.000000] Copyright (c) 1982, 1986, 1989, 1991, 1993
[ 1.000000]    The Regents of the University of California.  All rights reserved.

[ 1.000000] NetBSD 10.0_RC4 (GENERIC) #0: Tue Feb  6 12:38:53 UTC 2024
[ 1.000000]    [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC
[ 1.000000] total memory = 4061 MB
[ 1.000000] avail memory = 3902 MB
[ 1.000000] timecounter: Timecounters tick every 10.000 msec
[ 1.000000] Kernelized RAIDframe activated
[ 1.000000] timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
[ 1.000004] mainbus0 (root)
[ 1.000004] ACPI: RSDP 0x00000000000F4F00 000024 (v02 HP    )
[ 1.000004] ACPI: XSDT 0x00000000F1DE6400 0000B4 (v01 HP    ProLiant 00000002 ??  0000162E)
[ 1.000004] ACPI: FACP 0x00000000F1DE6540 0000F4 (v03 HP    ProLiant 00000002 ??  0000162E)
[ 1.000004] Firmware Warning (ACPI): 32/64X length mismatch in FADT/Pm1aControlBlock: 16/32 (20221020/tbfadt-640)
[ 1.000004] Firmware Warning (ACPI): 32/64X length mismatch in FADT/Pm2ControlBlock: 8/32 (20221020/tbfadt-640)
[ 1.000004] Firmware Warning (ACPI): Invalid length for FADT/Pm1aControlBlock: 32, using default 16 (20221020/tbfa
dt-742)
[ 1.000004] Firmware Warning (ACPI): Invalid length for FADT/Pm2ControlBlock: 32, using default 8 (20221020/tbfadt
-742)

[ 1.000004] ACPI: DSDT 0x00000000F1DE6640 002A13 (v01 HP    DSDT    00000001 INTL 20030228)
[ 1.000004] ACPI: FACS 0x00000000F1DE4140 000040
[ 1.000004] ACPI: SPCR 0x00000000F1DE4180 000050 (v01 HP    SPCRRBSU 00000001 ??  0000162E)
[ 1.000004] ACPI: MCFG 0x00000000F1DE4200 00003C (v01 HP    ProLiant 00000001      00000000)
[ 1.000004] ACPI: HPET 0x00000000F1DE4240 000038 (v01 HP    ProLiant 00000002 ??  0000162E)
[ 1.000004] ACPI: FFFF 0x00000000F1DE4280 000064 (v02 HP    ProLiant 00000002 ??  0000162E)
[ 1.000004] ACPI: SPMI 0x00000000F1DE4300 000040 (v05 HP    ProLiant 00000001 ??  0000162E)
[ 1.000004] ACPI: ERST 0x00000000F1DE4340 000230 (v01 HP    ProLiant 00000001 ??  0000162E)
[ 1.000004] ACPI: APIC 0x00000000F1DE4580 000252 (v01 HP    ProLiant 00000002      00000000)
[ 1.000004] ACPI: FFFF 0x00000000F1DE4800 000176 (v01 HP    ProLiant 00000001 ??  0000162E)
[ 1.000004] ACPI: BERT 0x00000000F1DE4980 000030 (v01 HP    ProLiant 00000001 ??  0000162E)
[ 1.000004] ACPI: HEST 0x00000000F1DE49C0 0000BC (v01 HP    ProLiant 00000001 ??  0000162E)
[ 1.000004] ACPI: DMAR 0x00000000F1DE4A80 00030E (v01 HP    ProLiant 00000001 ??  0000162E)
[ 1.000004] ACPI: FFFF 0x00000000F1DE63C0 00002D (v01 HP    ProLiant 00000001      00000000)
[ 1.000004] ACPI: SSDT 0x00000000F1DE9080 000137 (v03 HP    CRSPCI0  00000002 HP  00000001)
[ 1.000004] ACPI: SSDT 0x00000000F1DE91C0 000573 (v03 HP    riser0  00000002 INTL 20030228)
[ 1.000004] ACPI: SSDT 0x00000000F1DE9740 0001E1 (v01 HP    pcc      00000001 INTL 20090625)
[ 1.000004] ACPI: SSDT 0x00000000F1DE9940 000377 (v01 HP    pmab    00000001 INTL 20090625)
[ 1.000004] ACPI: SSDT 0x00000000F1DE9CC0 0009E4 (v01 INTEL  PPM RCM  80000001 INTL 20061109)
[ 1.000004] ACPI: 6 ACPI AML tables successfully acquired and loaded
[ 1.000004] ioapic0 at mainbus0 apid 8: pa 0xfec00000, version 0x20, 24 pins
[ 1.000004] x2APIC available but disabled by DMAR table
[ 1.000004] cpu0 at mainbus0 apid 0
[ 1.000004] cpu0: Use lfence to serialize rdtsc
[ 1.000004] cpu0: Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz, id 0x306c3
[ 1.000004] cpu0: node 0, package 0, core 0, smt 0
[ 1.000004] cpu1 at mainbus0 apid 2
[ 1.000004] cpu1: Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz, id 0x306c3
[ 1.000004] cpu1: node 0, package 0, core 1, smt 0
[ 1.000004] cpu2 at mainbus0 apid 4
[ 1.000004] cpu2: Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz, id 0x306c3
[ 1.000004] cpu2: node 0, package 0, core 2, smt 0
[ 1.000004] cpu3 at mainbus0 apid 6
[ 1.000004] cpu3: Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz, id 0x306c3
[ 1.000004] cpu3: node 0, package 0, core 3, smt 0
[ 1.000004] acpi0 at mainbus0: Intel ACPICA 20221020
[ 1.000004] acpi0: X/RSDT: OemId <HP    ,ProLiant,00000002>, AslId <  <2147483602>^D,0000162e>
[ 1.000004] acpi0: MCFG: segment 0, bus 0-63, address 0x00000000f4000000
[ 1.000004] acpi0: SCI interrupting at int 9
[ 1.000004] acpi0: fixed power button present
[ 1.000004] timecounter: Timecounter "ACPI-Fast" frequency 3579545 Hz quality 1000
[ 1.021219] hpet0 at acpi0: high precision event timer (mem 0xfed00000-0xfed00400)
[ 1.021219] timecounter: Timecounter "hpet0" frequency 14318180 Hz quality 2000
[ 1.021431] ipmi_acpi0 at acpi0 (MI0, IPI0001-0): io 0xca2-0xca3
[ 1.021431] ipmi0 at ipmi_acpi0
[ 1.021431] attimer1 at acpi0 (TIME, PNP0100): io 0x40-0x43 irq 0
[ 1.021431] pcppi1 at acpi0 (BEEP, PNP0800): io 0x61
[ 1.021431] spkr0 at pcppi1: PC Speaker
[ 1.021431] wsbell at spkr0 not configured
[ 1.021431] midi0 at pcppi1: PC speaker
[ 1.021431] sysbeep0 at pcppi1
[ 1.021431] com0 at acpi0 (COMA, PNP0501-0): io 0x3f8-0x3ff irq 4
[ 1.021431] com0: ns16550a, 16-byte FIFO
[ 1.021431] pckbc1 at acpi0 (KBD, PNP0303) (kbd port): io 0x60,0x64 irq 1
[ 1.021431] pckbc2 at acpi0 (PS2M, PNP0F13) (aux port): irq 12
[ 1.021431] PMI0 (ACPI000D) at acpi0 not configured
[ 1.021431] acpitz0 at acpi0 (THM0): cpu0
[ 1.021431] acpitz0: levels: critical 31.3 C, passive 9.8 C, passive cooling
[ 1.021431] attimer1: attached to pcppi1
[ 1.021431] pckbd0 at pckbc1 (kbd slot)
[ 1.021431] pckbc1: using irq 1 for kbd slot
[ 1.021431] wskbd0 at pckbd0: console keyboard
[ 1.021431] pms0 at pckbc1 (aux slot)
[ 1.021431] pckbc1: using irq 12 for aux slot
[ 1.021431] wsmouse0 at pms0 mux 0
[ 1.021431] pci0 at mainbus0 bus 0: configuration mode 1
[ 1.021431] pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
[ 1.021431] pchb0 at pci0 dev 0 function 0: Intel Xeon E3-1200 v3 Host Bridge, DRAM (rev. 0x06)
[ 1.021431] ppb0 at pci0 dev 1 function 0: Intel Haswell PCI-E x16 Controller (rev. 0x06)
[ 1.021431] ppb0: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x8 @ 8.0GT/s
[ 1.021431] pci1 at ppb0 bus 4
[ 1.021431] pci1: i/o space, memory space enabled, rd/line, wr/inv ok
[ 1.021431] ppb1 at pci0 dev 1 function 1: Intel Haswell PCI-E x8 Controller (rev. 0x06)
[ 1.021431] ppb1: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x8 @ 8.0GT/s
[ 1.021431] pci2 at ppb1 bus 7
[ 1.021431] pci2: i/o space, memory space enabled, rd/line, wr/inv ok
[ 1.021431] xhci0 at pci0 dev 20 function 0: Intel 8 Series USB xHCI (rev. 0x04)
[ 1.021431] xhci0: 64-bit DMA
[ 1.021431] xhci0: interrupting at msi0 vec 0
[ 1.021431] xhci0: xHCI version 1.0
[ 1.021431] usb0 at xhci0: USB revision 3.0
[ 1.021431] usb1 at xhci0: USB revision 2.0
[ 1.021431] ehci0 at pci0 dev 26 function 0: Intel 8 Series USB EHCI (rev. 0x04)
[ 1.021431] ehci0: 64-bit DMA
[ 1.021431] ehci0: interrupting at ioapic0 pin 21
[ 1.021431] ehci0: BIOS has given up ownership
[ 1.021431] ehci0: EHCI version 1.0
[ 1.021431] ehci0: Using DMA subregion for control data structures
[ 1.021431] usb2 at ehci0: USB revision 2.0
[ 1.021431] ppb2 at pci0 dev 28 function 0: Intel 8 Series PCIe (rev. 0xd4)
[ 1.021431] ppb2: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x1 @ 5.0GT/s
[ 1.021431] pci3 at ppb2 bus 10
[ 1.021431] pci3: i/o space, memory space enabled, rd/line, wr/inv ok
[ 1.021431] ppb3 at pci0 dev 28 function 4: Intel 8 Series PCIe (rev. 0xd4)
[ 1.021431] ppb3: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x1 @ 5.0GT/s
[ 1.021431] pci4 at ppb3 bus 2
[ 1.021431] pci4: i/o space, memory space enabled, rd/line, wr/inv ok
[ 1.021431] ppb4 at pci0 dev 28 function 5: Intel 8 Series PCIe (rev. 0xd4)
[ 1.021431] ppb4: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x1 @ 5.0GT/s
[ 1.021431] pci5 at ppb4 bus 3
[ 1.021431] pci5: i/o space, memory space enabled, rd/line, wr/inv ok
[ 1.021431] bge0 at pci5 dev 0 function 0: Broadcom BCM5720 Gigabit Ethernet
[ 1.021431] bge0: APE firmware NCSI 1.1.15.0
[ 1.021431] bge0: interrupting at msix1 vec 0
[ 1.021431] bge0: HW config 002b10d4, 00006014, 0000aa38, 00000000 00000000
[ 1.021431] bge0: ASIC BCM5720 A0 (0x5720000), Ethernet address a0:1d:48:97:5b:74
[ 1.021431] bge0: setting short Tx thresholds
[ 1.021431] brgphy0 at bge0 phy 1: BCM5720C 1000BASE-T media interface, rev. 0
[ 1.021431] brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
[ 1.021431] bge1 at pci5 dev 0 function 1: Broadcom BCM5720 Gigabit Ethernet
[ 1.021431] bge1: APE firmware NCSI 1.1.15.0
[ 1.021431] bge1: interrupting at msix2 vec 0
[ 1.021431] bge1: HW config 002b10d4, 00006014, 0000aa38, 00000000 00000000
[ 1.021431] bge1: ASIC BCM5720 A0 (0x5720000), Ethernet address a0:1d:48:97:5b:75
[ 1.021431] bge1: setting short Tx thresholds
[ 1.021431] brgphy1 at bge1 phy 2: BCM5720C 1000BASE-T media interface, rev. 0
[ 1.021431] brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
[ 1.021431] ppb5 at pci0 dev 28 function 6: Intel 8 Series PCIe (rev. 0xd4)
[ 1.021431] ppb5: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x1 @ 5.0GT/s
[ 1.021431] pci6 at ppb5 bus 13
[ 1.021431] pci6: i/o space, memory space enabled, rd/line, wr/inv ok
[ 1.021431] ppb6 at pci0 dev 28 function 7: Intel 8 Series PCIe (rev. 0xd4)
[ 1.021431] ppb6: PCI Express capability version 2 <Root Port of PCI-E Root Complex> x1 @ 5.0GT/s
[ 1.021431] ppb6: link is x1 @ 2.5GT/s
[ 1.021431] pci7 at ppb6 bus 1
[ 1.021431] pci7: i/o space, memory space enabled, rd/line, wr/inv ok
[ 1.021431] Hewlett-Packard iLO3 Slave (miscellaneous system, revision 0x05) at pci7 dev 0 function 0 not configured
[ 1.021431] vga0 at pci7 dev 0 function 1: Matrox MGA G200eH (rev. 0x00)
[ 1.021431] wsdisplay0 at vga0 kbdmux 1: console (80x25, vt100 emulation), using wskbd0
[ 1.021431] wsmux1: connecting to wsdisplay0
[ 1.021431] drm at vga0 not configured
[ 1.021431] Hewlett-Packard iLO3 Management (miscellaneous system, revision 0x05) at pci7 dev 0 function 2 not configured
[ 1.021431] uhci0 at pci7 dev 0 function 4: Hewlett-Packard iLO3 Virtual USB (rev. 0x02)
[ 1.021431] uhci0: interrupting at msi3 vec 0
[ 1.021431] usb3 at uhci0: USB revision 1.0
[ 1.021431] ehci1 at pci0 dev 29 function 0: Intel 8 Series USB EHCI (rev. 0x04)
[ 1.021431] ehci1: 64-bit DMA
[ 1.021431] ehci1: interrupting at ioapic0 pin 20
[ 1.021431] ehci1: BIOS has given up ownership
[ 1.021431] ehci1: EHCI version 1.0
[ 1.021431] ehci1: Using DMA subregion for control data structures
[ 1.021431] usb4 at ehci1: USB revision 2.0
[ 1.021431] ichlpcib0 at pci0 dev 31 function 0: Intel C222 LPC (rev. 0x04)
[ 1.021431] timecounter: Timecounter "ichlpcib0" frequency 3579545 Hz quality 1000
[ 1.021431] ichlpcib0: 24-bit timer
[ 1.021431] tco0 at ichlpcib0: TCO (watchdog) timer configured.
[ 1.021431] tco0: autoconfiguration error: TCO timer reboot disabled by hardware; hope SMBIOS properly handles it.
[ 1.021431] tco0: Min/Max interval 1/367 seconds
[ 1.021431] ahcisata0 at pci0 dev 31 function 2: Intel 8 Series (desktop) SATA Controller (AHCI) (rev. 0x04)
[ 1.021431] ahcisata0: 64-bit DMA
[ 1.021431] ahcisata0: AHCI revision 1.30, 6 ports, 32 slots, CAP 0xdf30ff45<EMS,PSC,SSC,PMD,ISS=0x3=Gen3,SCLO,SAL,SALP,SSS,SMPS,SNCQ,S64A>
[ 1.021431] ahcisata0: interrupting at msi4 vec 0
[ 1.021431] atabus0 at ahcisata0 channel 0
[ 1.021431] atabus1 at ahcisata0 channel 1
[ 1.021431] atabus2 at ahcisata0 channel 2
[ 1.021431] atabus3 at ahcisata0 channel 3
[ 1.021431] atabus4 at ahcisata0 channel 4
[ 1.021431] atabus5 at ahcisata0 channel 5
[ 1.021431] isa0 at ichlpcib0
[ 1.021431] com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, 16-byte FIFO
[ 1.021431] acpicpu0 at cpu0: ACPI CPU
[ 1.021431] acpicpu0: C1: FFH, lat  1 us, pow  1000 mW
[ 1.021431] acpicpu0: C2: FFH, lat  96 us, pow  350 mW
[ 1.021431] coretemp0 at cpu0: thermal sensor, 1 C resolution, Tjmax=100
[ 1.021431] acpicpu1 at cpu1: ACPI CPU
[ 1.021431] coretemp1 at cpu1: thermal sensor, 1 C resolution, Tjmax=100
[ 1.021431] acpicpu2 at cpu2: ACPI CPU
[ 1.021431] coretemp2 at cpu2: thermal sensor, 1 C resolution, Tjmax=100
[ 1.021431] acpicpu3 at cpu3: ACPI CPU
[ 1.021431] coretemp3 at cpu3: thermal sensor, 1 C resolution, Tjmax=100
[ 1.021431] timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
[ 1.021431] timecounter: Timecounter "TSC" frequency 3092842000 Hz quality 3000
[ 1.907097] uhub0 at usb0: NetBSD (0x0000) xHCI root hub (0x0000), class 9/0, rev 3.00/1.00, addr 0
[ 1.907097] uhub0: 2 ports with 2 removable, self powered
[ 1.907097] uhub1 at usb1: NetBSD (0x0000) xHCI root hub (0x0000), class 9/0, rev 2.00/1.00, addr 0
[ 1.907097] uhub1: 10 ports with 10 removable, self powered
[ 1.907097] IPsec: Initialized Security Association Processing.
[ 1.923540] uhub2 at usb2: NetBSD (0x0000) EHCI root hub (0x0000), class 9/0, rev 2.00/1.00, addr 1
[ 1.923540] uhub2: 2 ports with 2 removable, self powered
[ 1.923540] uhub3 at usb3: NetBSD (0x0000) UHCI root hub (0x0000), class 9/0, rev 1.00/1.00, addr 1
[ 1.923540] uhub3: 2 ports with 2 removable, self powered
[ 1.923540] uhub4 at usb4: NetBSD (0x0000) EHCI root hub (0x0000), class 9/0, rev 2.00/1.00, addr 1
[ 1.923540] uhub4: 2 ports with 2 removable, self powered
[ 2.003540] ahcisata0 port 0: device present, speed: 6.0Gb/s
[ 2.003540] ahcisata0 port 4: device present, speed: 1.5Gb/s
[ 2.383539] uhub5 at uhub1 port 3: vendor 0424 (0x0424) product 2660 (0x2660), class 9/0, rev 2.00/8.01, addr 1
[ 2.383539] uhub5: single transaction translator
[ 2.383539] uhub5: 2 ports with 1 removable, self powered
[ 2.993539] uhub6 at uhub4 port 1: vendor 8087 (0x8087) product 8000 (0x8000), class 9/0, rev 2.00/0.04, addr 2
[ 2.993539] uhub6: single transaction translator
[ 2.993539] uhub7 at uhub2 port 1: vendor 8087 (0x8087) product 8008 (0x8008), class 9/0, rev 2.00/0.04, addr 2
[ 2.993539] uhub7: single transaction translator
[ 2.993539] uhub6: 6 ports with 6 removable, self powered
[ 2.993539] uhub7: 4 ports with 4 removable, self powered
[ 3.563538] umass0 at uhub0 port 2 configuration 1 interface 0
[ 3.563538] umass0: USB (0x0781) SanDisk 3.2Gen1 (0x5567), rev 3.20/1.00, addr 2
[ 3.563538] umass0: using SCSI over Bulk-Only
[ 3.563538] scsibus0 at umass0: 2 targets, 1 lun per target
[ 3.573537] sd0 at scsibus0 target 0 lun 0: <USB, SanDisk 3.2Gen1, 1.00> disk removable
[ 3.573537] sd0: 29358 MB, 59648 cyl, 16 head, 63 sec, 512 bytes/sect x 60125184 sectors
[ 3.583536] wd0 at atabus0 drive 0
[ 3.583536] wd0: <ST2000DM001-1CH164>
[ 3.583536] wd0: drive supports 16-sector PIO transfers, LBA48 addressing
[ 3.583536] wd0: 1863 GB, 3876021 cyl, 16 head, 63 sec, 512 bytes/sect x 3907029168 sectors (4096 bytes/physsect;
first aligned sector: 8)
[ 3.593538] wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133), WRITE DMA FUA, NCQ (32 tags)
[ 3.593538] wd0(ahcisata0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA), NCQ (31 ta
gs)
[ 3.593538] atapibus0 at atabus4: 1 targets
[ 3.603537] cd0 at atapibus0 drive 0: <hp      DVD-RAM GHA3N, KD5DAF43954, WH01> cdrom removable
[ 3.613539] cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
[ 3.613539] cd0(ahcisata0:4:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100) (using DMA)
[ 3.633538] uhidev0 at uhub1 port 5 configuration 1 interface 0
[ 3.633538] uhidev0: SEM (0x1a2c) USB Keyboard (0x2124), rev 1.10/1.10, addr 3, iclass 3/1
[ 3.643536] ukbd0 at uhidev0
[ 3.643536] wskbd1 at ukbd0 mux 1
[ 3.643536] wskbd1: connecting to wsdisplay0
[ 3.643536] uhidev1 at uhub1 port 5 configuration 1 interface 1
[ 3.643536] uhidev1: SEM (0x1a2c) USB Keyboard (0x2124), rev 1.10/1.10, addr 3, iclass 3/0
[ 3.643536] uhidev1: 2 report ids
[ 3.643536] uhid0 at uhidev1 reportid 1: input=2, output=0, feature=0
[ 3.643536] uhid1 at uhidev1 reportid 2: input=1, output=0, feature=0
[ 4.123538] uhidev2 at uhub1 port 6 configuration 1 interface 0
[ 4.123538] uhidev2: vendor 275d (0x275d) USB OPTICAL MOUSE (0x0ba6), rev 1.10/1.00, addr 4, iclass 3/1
[ 4.123538] ums0 at uhidev2: 3 buttons and Z dir
[ 4.123538] wsmouse1 at ums0 mux 0
[ 4.603537] uaudio0 at uhub1 port 9 configuration 1 interface 0
[ 4.603537] uaudio0: C-Media INC. (0x0d8c) USB Audio (0x0001), rev 1.10/0.10, addr 5
[ 4.603537] uaudio0: audio rev 1.00
[ 4.603537] audio0 at uaudio0: playback
[ 4.603537] audio0: slinear_le:16 2ch 48000Hz, blk 11520 bytes (60ms) for playback
[ 4.603537] spkr1 at audio0: PC Speaker (synthesized)
[ 4.603537] wsbell at spkr1 not configured
[11.453530] ipmi0: version 32.0 interface KCS iobase 0xca2/0x2 spacing 1
[11.453530] ipmi0: ID 19.2 IPMI 2.0 Available
[11.453530] ipmi0: Additional Chassis FRU SEL SDR Sensor
[11.453530] ipmi0: Manufacturer 0000b Product 200b
[11.453530] ipmi0: Firmware 1.32
[11.453530] swwdog0: software watchdog initialized
[11.493529] WARNING: 1 error while detecting hardware; check system log.
[11.493529] boot device: sd0
[11.493529] root on sd0a dumps on sd0b
[11.503529] root file system type: ffs
[11.503529] kern.module.path=/stand/amd64/10.0/modules
[11.503529] WARNING: NVRAM century is 33 but RTC year is 2024
[24.873516] wsdisplay0: screen 1 added (80x25, vt100 emulation)
[24.873516] wsdisplay0: screen 2 added (80x25, vt100 emulation)
[24.873516] wsdisplay0: screen 3 added (80x25, vt100 emulation)
[24.883516] wsdisplay0: screen 4 added (80x25, vt100 emulation


February 18, 2024

Unix Stack Exchange NetBSD: how to mount a disk image?

I have create a disk image on netbsd

newfs -F -s 10G 1.img

How to mount it?

I have tried "nodev" but give error and try to mount /mnt/p2

mount -v -o nodev /home/user/1.img /mnt/p2
DragonFly BSD Digest Lazy Reading for 2024/02/18

Mini-theme: collections of media.

Your unrelated music link of the week: Omni: Souvenir.


February 14, 2024

Unix Stack Exchange Is possible to find a single file of NOT installed package on Netbsd?

Simple question:

On Fedora, i want to search mplayer..

dnf provides *bin/mplayer

on Debian

apt -y install apt-file
apt-file update
apt-file search mplayer|grep bin

on Freebsd

pkg install -y pkg-provides
pkg provides -u 
pkg provides *bin/mplayer$

Anything similar on netbsd? Actually seems no similar tool exist.


February 13, 2024

Pullup pkgsrc [pullup-pkgsrc #6836] pullup-request: pkgsrc/net/bind916
Pullup pkgsrc [pullup-pkgsrc #6835] pullup-request: pkgsrc/net/bind918

February 12, 2024

Unix Stack Exchange Netbsd, what is dk?

Simple question, today making iostat on netbsd machine I see..

    iostat 2 3
          tty              ld0               ld1               dk0               dk1               dk2               dk3               dk4               cd0             CPU
     tin  tout  KB/t  t/s  MB/s   KB/t  t/s  MB/s   KB/t  t/s  MB/s   KB/t  t/s  MB/s   KB/t  t/s  MB/s   KB/t  t/s  MB/s   KB/t  t/s  MB/s   KB/t  t/s  MB/s  us ni sy in id

---explanation---

ld0 is the first virtio hd
ld1 is the second virtio hd
cd0 is the first SATA cdrom

what is dk1-4?


February 11, 2024

DragonFly BSD Digest Lazy Reading for 2024/02/11

No theme this week.


February 07, 2024

NetBSD Blog NetBSD 10.0 RC4 available!

The NetBSD project is pleased to announce the fourth (and probably last) release candidate of the upcoming 10.0 release, please help testing!
See the release announcement for details.

The netbsd-10 release branch is more than a year old now, so it is high time the 10.0 release makes it to the front stage. This matches the long time it took for the development branch to get ready for branching, a lot of development went into this new release.

This also caused the release announcement to be one of the longest we ever did.

Since RC1 there have been numerous changes, including major updates to external software included in the release: Postfix, OpenSSH, and the firmware used for Raspberry PI devices. Various issues with RC1 have been fixed, including installer (sysinst) crashes. Lots of architecture specific fixes happend, e.g. various toolchain changes for VAX (so it is now finaly self-hosting again), and kernel changes for macppc, netwinder, and alpha.

For RC3 only few (relatively) minor changes were made, including https certificate verification in libfetch (which is used by pkg_ad(1)), and also improvements to the EFI bootloader to better deal with booting from CD (or in virtual machines ISO images), plus lots of various bug fixes.

RC4 became necessary as a few very important DRM/KMS issues especially for Intel GPUs have been resolved. And as an (unexpected) bonus support for the Nintendo Wii has been added to the evbppc port.

Especially on amd64 machines please notes that we got a new DRM/KMS subsystem version, and this may lead to fallout on some hardware. Unfortunately not all known bugs from the release engineering pre-release task list could be fixed in time for this release - we will continue to improve the current state and hope to have more of them solved for the next (10.1) release.

If you want to test 10.0 RC4 please check the installation notes for your architecture and download the preferred install image from the CDN or if you are using an ARM based device from the netbsd-10 builds from the bootable ARM images page.

If you have any issues with installation or run into issues with the system during use, please contact us on one of the mailing lists or file a problem report.


February 06, 2024

The NetBSD Foundation NetBSD 10.0 RC4 is available!

February 01, 2024

Benny Siegert NetBSD 10: Thirty Years, Still Going Strong!
In 2023, the NetBSD project celebrated 30 years since its first release, 0.8. Now, four years after NetBSD 9, NetBSD 10 brings a huge number of changes and improvements. This talk will dive into the most important new features of NetBSD 10, such as performance and security improvements, expanded CPU and GPU support, improved virtualization and more! Another strength of NetBSD is its package system, pkgsrc, which is portable to dozens of other OSes and can even be used like virtualenv for development and deployment environments.

January 28, 2024

NetBSD Package System (pkgsrc) on DaemonForums Authentication error when executing pkgin
Hi all,
since last last time I executed pkgin full-upgrade , I get the following error message:

# pkgin update
processing remote summary (https://cdn.netbsd.org/pub/pkgsrc/pa...0.0_2023Q4/All)...
00886327D6700000:error:0A000086:SSL routines:tls_post_process_server_certificate:certi ficate verify failed:/usr/src/crypto/external/bsd/openssl/dist/ssl/statem/statem_clnt.c:1889:
00886327D6700000:error:0A000086:SSL routines:tls_post_process_server_certificate:certi ficate verify failed:/usr/src/crypto/external/bsd/openssl/dist/ssl/statem/statem_clnt.c:1889:
00886327D6700000:error:0A000086:SSL routines:tls_post_process_server_certificate:certi ficate verify failed:/usr/src/crypto/external/bsd/openssl/dist/ssl/statem/statem_clnt.c:1889:
pkgin: Could not fetch https://cdn.netbsd.org/pub/pkgsrc/pa...kg_summary.gz: Authentication error

Any idea how to solve this ?

I am Using NetBSD 10.0_RC3 amd64 on my home-office desktop.

Thanks,

January 21, 2024

DragonFly BSD Digest Lazy Reading for 2024/01/21

I’ve got some real gems this week.

Your unrelated extended music of the week: Bill Laswell featuring DJ Rob Swift – Reanimation.  Which of course reminds me that Rob Gets Busy.  If you like that, here’s a crazy amount of beat juggling, at its best when it creates new music and rhythms.  (via)


January 17, 2024

NetBSD Blog NetBSD 10.0 RC3 available!

The NetBSD project is pleased to announce the third (and probably last) release candidate of the upcoming 10.0 release, please help testing!
See the release announcement for details.

The netbsd-10 release branch is more than a year old now, so it is high time the 10.0 release makes it to the front stage. This matches the long time it took for the development branch to get ready for branching, a lot of development went into this new release.

This also caused the release announcement to be one of the longest we ever did.

Since RC1 there have been numerous changes, including major updates to external software included in the release: Postfix, OpenSSH, and the firmware used for Raspberry PI devices. Various issues with RC1 have been fixed, including installer (sysinst) crashes. Lots of architecture specific fixes happend, e.g. various toolchain changes for VAX (so it is now finaly self-hosting again), and kernel changes for macppc, netwinder, and alpha.

For RC3 only few (relatively) minor changes were made, including https certificate verification in libfetch (which is used by pkg_ad(1)), and also improvements to the EFI bootloader to better deal with booting from CD (or in virtual machines ISO images), plus lots of various bug fixes.

Especially on amd64 machines please notes that we got a new DRM/KMS subsystem version, and this may lead to fallout on some hardware. Unfortunately not all known bugs from the release engineering pre-release task list could be fixed in time for this release - we will continue to improve the current state and hope to have more of them solved for the next (10.1) release.

If you want to test 10.0 RC3 please check the installation notes for your architecture and download the preferred install image from the CDN or if you are using an ARM based device from the netbsd-10 builds from the bootable ARM images page.

If you have any issues with installation or run into issues with the system during use, please contact us on one of the mailing lists or file a problem report.

Stack Overflow Problems with $PATH on the .bashrc file

I am using a Linux Ubuntu machine, and recently, I've been having issues regarding changing the $PATH in the .bashrc file.

I want to change the $PATH in the .bashrc to install a Golang extension called goose. I was having issues with the installation, and after looking at some forums, it seems that to solve the problem, it's necessary to change the $PATH in this .bashrc file.

I replaced the data in it, removed other $PATH entries that were in the file, leaving only the ones I intended to use. However, after running echo $PATH in the terminal, it returns a $PATH that is no longer in the .bashrc.

I tried restarting the machine multiple times, re-editing the file, looked at the .profile, but I don't think that's the issue. However, nothing is working.

What can I do to resolve this problem?

.bashrc:

# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

export PATH="$PATH:$HOME/go/bin"

# If not running interactively, don't do anything
case $- in
    *i*) ;;
      *) return;;
esac

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar

# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
    debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
    xterm-color|*-256color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then
    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
    # We have color support; assume it's compliant with Ecma-48
    # (ISO/IEC-6429). (Lack of such support is extremely rare, and such
    # a case would tend to support setf rather than setaf.)
    color_prompt=yes
    else
    color_prompt=
    fi
fi

if [ "$color_prompt" = yes ]; then
    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
    PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
    PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
    ;;
*)
    ;;
esac

# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
    test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
    alias ls='ls --color=auto'
    #alias dir='dir --color=auto'
    #alias vdir='vdir --color=auto'

    alias grep='grep --color=auto'
    alias fgrep='fgrep --color=auto'
    alias egrep='egrep --color=auto'
fi

# colored GCC warnings and errors
#export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01'

# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'

# Add an "alert" alias for long running commands.  Use like so:
#   sleep 10; alert
alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.

if [ -f ~/.bash_aliases ]; then
    . ~/.bash_aliases
fi

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
  if [ -f /usr/share/bash-completion/bash_completion ]; then
    . /usr/share/bash-completion/bash_completion
  elif [ -f /etc/bash_completion ]; then
    . /etc/bash_completion
  fi
fi



export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"  # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"  # This loads nvm bash_completion

.profile:

# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.

# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022

# if running bash
if [ -n "$BASH_VERSION" ]; then
    # include .bashrc if it exists
    if [ -f "$HOME/.bashrc" ]; then
    . "$HOME/.bashrc"
    fi
fi

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/.local/bin" ] ; then
    PATH="$HOME/.local/bin:$PATH"
fi

What returns in the terminal:

echo $PATH

/home/zeus/.nvm/versions/node/v20.11.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin:/home/zeus/go/bin:/home/zeus/go/bin
Stack Overflow Is it possible to authenticate a user to Azure AD (with MFA) only by using CLI?

Few developers in my organization are using Ubuntu 18.04 Server machines (no GUI). I want them to get authenticated to my organization's Azure AD from CLI alone.(not in any browser)

I tried to do that with a custom python-selenium script but I don't think that is reliable and robust. The script just

  1. Opens the Login URL,
  2. Types the username and password by xpath,
  3. Reads and prints the OTP number to be entered on the Authenticator app
  4. Waits until the user types the OTP in the device
  5. Prints the response

One more thing to add, I don't want to modify the Azure Portal's configurations whatsoever, the user still needs to use the MFA everytime to login. I don't want to use any other alternative type of logins too.

I also searched alternatives like elinks, w3m but those couldn't help the cause.

Is there any tool(better if official) that could solve this? Or is this task technically not feasible? I read online that even az-cli depends on a browser for authentication.

Stack Overflow How to force "pip download" to download all dependencies including the "setup_requires"

Here is the setup.py copied from onnx-caffe2:

setup(
    name="onnx-caffe2",
    version=VersionInfo.version,
    description="Caffe2 frontend and backend of Open Neural Network Exchange",
    install_requires=install_requires,
    setup_requires=['pytest-runner'],
    tests_require=['numpy', 'pytest-cov', 'psutil'],
    cmdclass=cmdclass,
    packages=find_packages(),
    author='bddppq',
    author_email='[email protected]',
    url='https://github.com/onnx/onnx-caffe2',
    entry_points={
        'console_scripts': [
            'convert-caffe2-to-onnx = onnx_caffe2.bin.conversion:caffe2_to_onnx',
            'convert-onnx-to-caffe2 = onnx_caffe2.bin.conversion:onnx_to_caffe2'
        ]
    },
)

Here is the requirements.txt:

...
onnx-caffe2
...

The pip download will not download any packages inside the "setup_requires":

pip download -r requirements.txt

How to force "pip download" to download all dependencies including the "setup_requires"?

If it is not possible for "pip download", then how to parse the "setup.py" to get all packages inside the "setup_requires"? What's the standard way for parsing the "setup_requires"?

Stack Overflow connection between mysql and mysql-workbench for root user

I have installed MySQL on my Linux Ubuntu 22.04 system and subsequently installed MySQL Workbench (8.0). However, upon attempting to launch Workbench for the localhost user, I encountered an error. I have attached a screenshot depicting the error, and I have also shared the websites I consulted in an attempt to resolve this issue. I would appreciate assistance in resolving the MySQL Workbench connection problem.

I checked https://www.youtube.com/watch?v=LdsEkrtlgKc https://www.youtube.com/watch?v=F1_fkOYgu8g https://askubuntu.com/questions/773446/unable-to-connect-via-mysql-workbench-to-localhost-in-ubuntu-16-04-passwordless MySQL Workbench cannot connect to database in Ubuntu 20.04

Stack Overflow Why can very long pipe (%>%) statements cause "Error: C stack usage is too close to the limit"?

Before I start:
I'm aware that there are quite a few threads on this error "out there" but none of them seem to narrow the problem down to very long pipe statements specifically.

By chance I came across the observation that very long pipe (%>%) statements can trigger the
"Error: C stack usage is too close to the limit" error.

Also, some machines I have access to will trigger this earlier while others will trigger it later.

Ubuntu 20.04 with R 4.0.5 (rocker/r-ver:4.0.5) tiggers later
Ubuntu 22.04 with R 4.3.2 (rocker/r-ver:4.3.2) tiggers earlier

Both machines return 8192 for ulimit -s.

Since I don't want to paste hundreds of lines of redundant code here I will give an example that will need to be adapted for personal reproduction on your local machine. Repeating the piping into the mutate() statement about 1000 times should do the trick on most machines.

library(dplyr)

df <- data.frame(col1 = 1:10000)

df <- df %>%
  mutate(col1 = 1)

  # uncomment and copy paste below lines until about 1000 mutate() statements are used
  #mutate(col1 = 1) %>%
  #mutate(col1 = 1) %>%
  #mutate(col1 = 1) %>%

As a solution I now break down long pipes into smaller chunks so that's easy enough really. I'm still interested in some more background on the topic.

Why does this trigger that error and does anyone have general thoughts on the topic?


January 16, 2024

The NetBSD Foundation NetBSD 10.0 RC3 is available!