Haiku Activity & Contract Report, June 2026 | Haiku Project

This report covers hrev59754 through hrev59820.

The thing that should be the biggest news item this month is that the GSoC 2024 work to port “NVMM”, the NetBSD Virtual Machine Monitor (which runs on more than just NetBSD, despite the name), providing hardware-accelerated virtualization support for QEMU, was finally merged. Unfortunately it still doesn’t fully work, so it’s still disabled by default: hence, it’s only a minor news item, unfortunately.


This is a companion discussion topic for the original entry at https://www.haiku-os.org/blog/waddlesplash/2026-07-13-haiku_activity_contract_report_june_2026/
19 Likes

Those are great news! Sounds like a lot of user-visible improvements, too.

1 Like

Thanks for the fixes, especially for those ones which restored statuses / functions after unexpected regressions.

I wish all who waited some improvement listed in the report to be capable to use them, as there were many. As I think any fixes/additions to filesystems and drivers are improvements at the same time. Enables to use devices, especially storage devices, more reliably than before .. or at all.
Getting closer to several kind of HW accelerations.
Also, soon who remained on Beta5 can step toward Beta6, and can enjoy fixes/improvements and wider software choices – for Haiku 64bit surely - without stepping into Nightly revisions often risky or unexpected “flavored” experiences. Now there is date for the transition process – planned to be done in the following weeks with RC versions and testings and finally appearing a new Haiku version “Beta6” stamped on the Haiku Home page – according to preliminary plans – in 2026 Augustus.

:cowboy_hat_face:

1 Like

He said mid-August, but 2026 is your own interpretation :wink:

Sorry, in Hungary the date-endianness is Year Month (Day) :stuck_out_tongue_winking_eye:
I forgot to adapt to foreign rules, so that not days, but the year itself !

On the Haiku Wiki you can find the the entire planned transition project – me myself intentionally had not precised on days, as it depends on more changing factors that could push the announcement closer to the end of the month – if I understood the estimate correctly.

18th of August would be the perfect timing for beta 6 for the 25 years of Haiku :stuck_out_tongue:

1 Like

May it be the best release ever made…

2 Likes

Oh yeah, this 2 years period will deliver many fixes dated back decade(s) ago, just as I see last hours patches and some tickets in progress.

Among other things, there were again unscheduled tickets which are actually closed now as R1B6 resolved ones ! :smiley: Exciting … Especially as even ticket #3 came up as unresolved and related to brand new ticket as same issue.

(Haha, I became curious what was ticket #1. Turned out :
it was opened in 2005,
it was about an issue related grouped processes, it was closed as fixed in 2006, almost 1 and half years later.)

Also I saw a ticket that can resolve my observation about CPU identification. I did not know it relates to AMD CPUs too, but I recognized, my Intel CPU core generation was detected/identified well, but in listdev and syslog it was identified Xeon equivalent core Intel CPU instead of core i7. However fetch scripts - I assume using dmidecode - identified them well.

So, for me it seems like
… a “Coding sprint” at :heart_exclamation: Closing Haiku R1Beta6 development - worldwide :heart_exclamation: :heart_eyes: :+1:

It is going to be good feeling to read July 2006 report too !

:cowboy_hat_face:

1 Like

Let me know, or log a ticket, if you run into any CPU identification issues after the latest change. I tried my best to follow the guidelines from the Intel and AMD docs, but there could be some edge cases out there.

In regards to Issue #3, I don’t think it is hard to solve, I just don’t have any hardware that has the symptom so I wouldn’t want to make the change without being able to test.

Ahoy @Nighthawk !

I forgot to check is changed anything toward my CPU in listdev output, however meanwile I upgraded to hrev59860 , so the patch in hrev59856 could have effect, if core i7 and Xeon also contained in that patch regarding CPU info.

Let’s see - is this changed listdev’s output →

   user  ~/Desktop    04:14    listdev

device Bridge (Host bridge) [6|0|0]
  vendor 8086: Intel Corporation
  device 0c04: Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller

device Bridge (PCI bridge, Normal decode) [6|4|0]
  vendor 8086: Intel Corporation
  device 0c01: Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller

device Display controller (VGA compatible controller, VGA controller) [3|0|0]
  vendor 1002: Advanced Micro Devices, Inc. [AMD/ATI]
  device 6640: Saturn XT [FirePro M6100]

device Multimedia controller (Audio device) [4|3|0]
  vendor 1002: Advanced Micro Devices, Inc. [AMD/ATI]
  device aac0: Tobago HDMI Audio [Radeon R7 360 / R9 360 OEM]

device Display controller (VGA compatible controller, VGA controller) [3|0|0]
  vendor 8086: Intel Corporation
  device 0416: 4th Gen Core Processor Integrated Graphics Controller

device Multimedia controller (Audio device) [4|3|0]
  vendor 8086: Intel Corporation
  device 0c0c: Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller

device Serial bus controller (USB controller, XHCI) [c|3|30]
  vendor 8086: Intel Corporation
  device 8c31: 8 Series/C220 Series Chipset Family USB xHCI

   device Hub (Unused, Full speed (or root) hub) [9|0|0]
     vendor 0000: Unknown
     device 0000: Unknown

      device Hub (Unused, Full speed (or root) hub) [9|0|0]
        vendor 05e3: Genesys Logic, Inc.
        device 0608: Hub

         device Human Interface Device (No Subclass, None) [3|0|0]
           vendor 046d: Logitech, Inc.
           device c52b: Unifying Receiver

         device Human Interface Device (No Subclass, None) [3|0|0]
           vendor 046d: Logitech, Inc.
           device c52b: Unifying Receiver

      device Mass Storage (SCSI, Bulk-Only) [8|6|50]
        vendor 0781: SanDisk Corp.
        device 5595: Unknown

      device Mass Storage (SCSI, Bulk-Only) [8|6|50]
        vendor 04e8: Samsung Electronics Co., Ltd
        device 6300: Unknown

device Communication controller [7|80|0]
  vendor 8086: Intel Corporation
  device 8c3a: 8 Series/C220 Series Chipset Family MEI Controller #1

device Network controller (Ethernet controller) [2|0|0]
  vendor 8086: Intel Corporation
  device 153a: Ethernet Connection I217-LM

device Serial bus controller (USB controller, EHCI) [c|3|20]
  vendor 8086: Intel Corporation
  device 8c2d: 8 Series/C220 Series Chipset Family USB EHCI #2

   device Hub (Unused, Full speed (or root) hub) [9|0|0]
     vendor 0000: Unknown
     device 0000: Unknown

      device Hub (Unused, Full speed (or root) hub) [9|0|0]
        vendor 8087: Intel Corp.
        device 8008: Integrated Rate Matching Hub

         device Video (Video Streaming) [e|2|0]
           vendor 1bcf: Sunplus Innovation Technology Inc.
           device 2984: Unknown

device Multimedia controller (Audio device) [4|3|0]
  vendor 8086: Intel Corporation
  device 8c20: 8 Series/C220 Series Chipset High Definition Audio Controller

device Bridge (PCI bridge, Normal decode) [6|4|0]
  vendor 8086: Intel Corporation
  device 8c10: 8 Series/C220 Series Chipset Family PCI Express Root Port #1

device Bridge (PCI bridge, Normal decode) [6|4|0]
  vendor 8086: Intel Corporation
  device 8c14: 8 Series/C220 Series Chipset Family PCI Express Root Port #3

device Network controller [2|80|0]
  vendor 14e4: Broadcom Inc. and subsidiaries
  device 43b1: BCM4352 802.11ac Dual Band Wireless Network Adapter

device Bridge (PCI bridge, Normal decode) [6|4|0]
  vendor 8086: Intel Corporation
  device 8c16: 8 Series/C220 Series Chipset Family PCI Express Root Port #4

device Bridge (PCI bridge, Normal decode) [6|4|0]
  vendor 8086: Intel Corporation
  device 8c18: 8 Series/C220 Series Chipset Family PCI Express Root Port #5

device Bridge (PCI bridge, Normal decode) [6|4|0]
  vendor 8086: Intel Corporation
  device 8c1c: 8 Series/C220 Series Chipset Family PCI Express Root Port #7

device Bridge (PCI bridge, Normal decode) [6|4|0]
  vendor 8086: Intel Corporation
  device 8c1e: 8 Series/C220 Series Chipset Family PCI Express Root Port #8

device Generic system peripheral (SD Host controller) [8|5|1]
  vendor 1217: O2 Micro, Inc.
  device 8520: SD/MMC Card Reader Controller

device Serial bus controller (USB controller, EHCI) [c|3|20]
  vendor 8086: Intel Corporation
  device 8c26: 8 Series/C220 Series Chipset Family USB EHCI #1

   device Hub (Unused, Full speed (or root) hub) [9|0|0]
     vendor 0000: Unknown
     device 0000: Unknown

      device Hub (Unused, Full speed (or root) hub) [9|0|0]
        vendor 8087: Intel Corp.
        device 8000: Integrated Rate Matching Hub

         device Application Specific Interface (Device Firmware Update) [fe|1|1]
           vendor 413c: Dell Computer Corp.
           device 8143: Broadcom BCM20702A0 Bluetooth

         device Chip/SmartCard () [b|0|0]
           vendor 0a5c: Broadcom Corp.
           device 5800: BCM5880 Secure Applications Processor

device Bridge (ISA bridge) [6|1|0]
  vendor 8086: Intel Corporation
  device 8c4f: QM87 Express LPC Controller

device Mass storage controller (SATA controller, AHCI 1.0) [1|6|1]
  vendor 8086: Intel Corporation
  device 8c03: 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode]

device Serial bus controller (SMBus) [c|5|0]
  vendor 8086: Intel Corporation
  device 8c22: 8 Series/C220 Series Chipset Family SMBus Controller
   user  ~/Desktop    04:14    

As you can see hostbrige, PCI bridge, HD Audio controller device still reports as Xeon 3th/th generation core

device Bridge (Host bridge) [6|0|0]
vendor 8086: Intel Corporation
device 0c04: Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller

device Bridge (PCI bridge, Normal decode) [6|4|0]
vendor 8086: Intel Corporation
device 0c01: Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller

device Bridge (Host bridge) [6|0|0]
vendor 8086: Intel Corporation
device 0c04: Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller

device Bridge (PCI bridge, Normal decode) [6|4|0]
vendor 8086: Intel Corporation
device 0c01: Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller

If the patch is referred to Haiku’s About window, that always was correct identifying the CPU in my all machines I booted Insrtaller images (32/64 bit).

fastfetch - I assume use dmidecode - write the processor correctly.

   user  ~/Desktop    04:33    fastfetch
           MMMM              MMMM        user@HiQ_R1Nitely_512GO
           MMMM              MMMM        -----------------------
           MMMM              MMMM        OS: Haiku R1B6- x86_64
           MMMM              MMMM        Host: Precision M6800 (01)
           MMMM       .ciO| /YMMMMM*"    Kernel: Haiku R1~beta5+development
           MMMM   .cOMMMMM|/MMMMM/`      Uptime: 28 mins
 ,         ,iMM|/MMMMMMMMMMMMMMM*        Packages: 1459 (hpkg)
  `*.__,-cMMMMMMMMMMMMMMMMM/`.MMM        Shell: bash GNU bash, 5.3.15(1)-release (x86_64-unknown-haiku) verzió
Copyright (C) 2025 Free Software Foundation, Inc.
A licenc GPLv3+: a GNU GPL 3. vagy újabb változata
<http://gnu.org/licenses/gpl.html>
           """"              """"
Ez egy szabad szoftver, terjesztheti és/vagy módosíthatja.
NINCS GARANCIA, a törvény által engedélyezett mértékig.

                                         Display (AUO): 1920x1080, 60 Hz
                                         DE: Application Kit
                                         WM: Application Server
                                         Font: Noto Sans Display Regular (17pt) [Plain / Menu / Bold], Noto Sans Mono Regular (17pt) [Mono]
                                         Terminal: Haiku Terminal 1.0.0
                                         Terminal Font: JetBrainsMono Nerd Font Propo (22pt)
                                         CPU: Core™ i7-4800MQ (8) @ 2.69 GHz
                                         GPU 1: AMD Radeon HD 8950
                                         GPU 2: Intel 4th Gen Core Processor Integrated Graphics Controller
                                         Memory: 3.55 GiB / 31.91 GiB (11%)
                                         Swap: 0 B / 31.91 GiB (0%)
                                         Disk (/DATA_MEDIA): 160.25 GiB / 256.00 GiB (63%) - bfs
                                         Disk (/SANDSK256GO): 212.70 GiB / 234.84 GiB (91%) - bfs
                                         Disk (/data_shared): 10.62 GiB / 29.89 GiB (36%) - fat [External]
                                         Local IP (/dev/net/ipro1000/0): 192.168.1.217/24
                                         Battery (DELL 4HJXXD1): 123%
                                         Battery: 
                                         Battery: 
                                         Locale: hu.UTF-8

                                                                 
                                                                 
   user  ~/Desktop    04:33   

hw-probeshows the same

   user  ~/Desktop    04:40    hw-probe -all
Probe for hardware ... Ok
Reading logs ... Ok
Local probe path: /boot/home/config/non-packaged/data/HW_PROBE/LATEST/hw.info
   user  ~/Desktop    04:40    ls -l /boot/home/config/non-packaged/data/HW_PROBE/LATEST/hw.info
total 18
-rw-r--r-- 1 user root 5040 júl.   18 04:40 devices
-rw-r--r-- 1 user root  406 júl.   18 04:40 host
drwxr-xr-x 1 user root 2048 júl.   18 04:40 logs
   user  ~/Desktop    04:40    cat /boot/home/config/non-packaged/data/HW_PROBE/LATEST/hw.info/host
arch:x86_64
boot_mode:BIOS
cores:4
dual_boot:0
dual_boot_win:0
hwaddr:ACA66517F781B3D0DC573F9992EC6E44
haiku_version:hrev59860 Jul 17 2026 06:28:39
kernel:R1~beta5+development
microarch:Haswell
model:Precision M6800
probe_ver:1.6
sku_number:Precision M6800
sockets:1
system:haiku-hrev59860 Jul 17 2026 06:28:39
system_version:hrev59860 Jul 17 2026 06:28:39
threads:2
type:laptop
vendor:Dell Inc.
year:2015
   user  ~/Desktop    04:41    cat /boot/home/config/non-packaged/data/HW_PROBE/LATEST/hw.info/devices
pci:1002-6640-1028-05cd;03-00-00;failed;graphics card;;Advanced Micro Devices, Inc. [AMD/ATI];Saturn XT [FirePro M6100];Dell
pci:1002-aac0-1028-05cd;04-03-00;detected;sound;;Advanced Micro Devices, Inc. [AMD/ATI];Tobago HDMI Audio [Radeon R7 360 / R9 360 OEM];Dell
pci:1217-8520-1028-05cd;08-05-01;detected;card reader;;O2 Micro, Inc.;OZ777 SD/MMC Card Reader Controller;Dell
pci:14e4-43b1-1028-0017;02-80-00;detected;network;;Broadcom Inc. and subsidiaries;BCM4352 802.11ac Dual Band Wireless Network Adapter;Dell
pci:8086-0416-1028-05cd;03-00-00;failed;graphics card;;Intel Corporation;4th Gen Core Processor Integrated Graphics Controller;Dell
pci:8086-0c01-1028-05cd;06-04-00;detected;bridge;;Intel Corporation;Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller;Dell
pci:8086-0c04-1028-05cd;06-00-00;detected;bridge;;Intel Corporation;Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller;Dell
pci:8086-0c0c-1028-05cd;04-03-00;detected;sound;;Intel Corporation;Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller;Dell
pci:8086-153a-1028-05cd;02-00-00;detected;network;;Intel Corporation;Ethernet Connection I217-LM;Dell
pci:8086-8c03-1028-05cd;01-06-01;detected;storage;;Intel Corporation;8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode];Dell
pci:8086-8c10-1028-05cd;06-04-00;detected;bridge;;Intel Corporation;8 Series/C220 Series Chipset Family PCI Express Root Port #1;Dell
pci:8086-8c14-1028-05cd;06-04-00;detected;bridge;;Intel Corporation;8 Series/C220 Series Chipset Family PCI Express Root Port #3;Dell
pci:8086-8c16-1028-05cd;06-04-00;detected;bridge;;Intel Corporation;8 Series/C220 Series Chipset Family PCI Express Root Port #4;Dell
pci:8086-8c18-1028-05cd;06-04-00;detected;bridge;;Intel Corporation;8 Series/C220 Series Chipset Family PCI Express Root Port #5;Dell
pci:8086-8c1c-1028-05cd;06-04-00;detected;bridge;;Intel Corporation;8 Series/C220 Series Chipset Family PCI Express Root Port #7;Dell
pci:8086-8c1e-1028-05cd;06-04-00;detected;bridge;;Intel Corporation;8 Series/C220 Series Chipset Family PCI Express Root Port #8;Dell
pci:8086-8c20-1028-05cd;04-03-00;detected;sound;;Intel Corporation;8 Series/C220 Series Chipset High Definition Audio Controller;Dell
pci:8086-8c22-1028-05cd;0c-05-00;detected;smbus;;Intel Corporation;8 Series/C220 Series Chipset Family SMBus Controller;Dell
pci:8086-8c26-1028-05cd;0c-03-20;detected;usb controller;;Intel Corporation;8 Series/C220 Series Chipset Family USB EHCI #1;Dell
pci:8086-8c2d-1028-05cd;0c-03-20;detected;usb controller;;Intel Corporation;8 Series/C220 Series Chipset Family USB EHCI #2;Dell
pci:8086-8c31-1028-05cd;0c-03-30;detected;usb controller;;Intel Corporation;8 Series/C220 Series Chipset Family USB xHCI;Dell
pci:8086-8c3a-1028-05cd;07-80-00;detected;communication controller;;Intel Corporation;8 Series/C220 Series Chipset Family MEI Controller #1;Dell
pci:8086-8c4f-1028-05cd;06-01-00;detected;bridge;;Intel Corporation;QM87 Express LPC Controller;Dell
usb:046d-c52b;03-00-00;detected;human interface;;(Logitech, Inc.);(Unifying Receiver)
usb:04e8-6300;08-06-50;detected;disk;;(Samsung Electronics Co., Ltd);
usb:05e3-0608;09-00-00;detected;hub;;(Genesys Logic, Inc.);(Hub)
usb:0781-5595;08-06-50;detected;disk;;(SanDisk Corp.);
usb:0a5c-5800;00-00-00;failed;;;(Broadcom Corp.);(BCM5880 Secure Applications Processor)
usb:1bcf-2984;00-02-00;failed;;;(Sunplus Innovation Technology Inc.);
usb:413c-8143;00-01-01;failed;bluetooth;;(Dell Computer Corp.);(Broadcom BCM20702A0 Bluetooth)
usb:8087-8000;09-00-00;detected;hub;;(Intel Corp.);(Integrated Rate Matching Hub)
usb:8087-8008;09-00-00;detected;hub;;(Intel Corp.);(Integrated Rate Matching Hub)
bios:dell-a13-01-29-2015;;works;bios;;Dell Inc.;BIOS A13 01/29/2015
board:dell-0xwc1m;;works;motherboard;;Dell Inc.;Motherboard 0XWC1M
cpu:intel-6-60-3-core-i7-4800mq;;works;cpu;;Intel;Core i7-4800MQ CPU @ 2.70GHz
cpu:intel-6-60-3-core-i7-4800mq;;works;cpu;;Intel;Core i7-4800MQ CPU @ 2.70GHz
cpu:intel-6-60-3-core-i7-4800mq;;works;cpu;;Intel;Core i7-4800MQ CPU @ 2.70GHz
cpu:intel-6-60-3-core-i7-4800mq;;works;cpu;;Intel;Core i7-4800MQ CPU @ 2.70GHz
cpu:intel-6-60-3-core-i7-4800mq;;works;cpu;;Intel;Core i7-4800MQ CPU @ 2.70GHz
cpu:intel-6-60-3-core-i7-4800mq;;works;cpu;;Intel;Core i7-4800MQ CPU @ 2.70GHz
cpu:intel-6-60-3-core-i7-4800mq;;works;cpu;;Intel;Core i7-4800MQ CPU @ 2.70GHz
cpu:intel-6-60-3-core-i7-4800mq;;works;cpu;;Intel;Core i7-4800MQ CPU @ 2.70GHz
mem:hynix-hyundai-hmt41gs6bfr8a-pb-sodimm-serial-9fa8c954502834f5155a08118f9c043b;;works;memory;;Hynix/Hyundai;RAM HMT41GS6BFR8A-PB 8GB SODIMM DDR3 1600MT/s
mem:samsung-m471b1g73eb0-yk0-sodimm-serial-5eeaf18c668b01bd4527096e9a5ffb00;;works;memory;;Samsung;RAM M471B1G73EB0-YK0 8GB SODIMM DDR3 1600MT/s
mem:samsung-m471b1g73eb0-yk0-sodimm-serial-778f743295b299ba163582bbbbacd296;;works;memory;;Samsung;RAM M471B1G73EB0-YK0 8GB SODIMM DDR3 1600MT/s
mem:samsung-m471b1g73eb0-yk0-sodimm-serial-bf813be8d0cce5e9f5e696a2ccfa506e;;works;memory;;Samsung;RAM M471B1G73EB0-YK0 8GB SODIMM DDR3 1600MT/s
   user  ~/Desktop    04:42   

I may be wrong and that listdev write Xeon CPU cores at that 3 device items is quite normal, I just remembered, and found as a interesting why not core i7 and core i7 extreme as I had in my previous M6700 that was a cire i7 Extreme CPU. There also this Xeon cores were written on devices.

The names for the devices you have that mention Xeon in listdev and hw-probe are generated from a list of PCI ID’s, which is pulled into Haiku from this website (https://pci-ids.ucw.cz/), not the code that was patched by Nighthawk. I get the same listings on my 4th Gen i7-4790k based PC running Haiku and also under Linux with lspci on the same system as it uses the same PCI ID list.

okidoki, thanks.