Making XLibre to compile and run on NetBSD

[fredvs]

Select the version

Git master branch

Describe your issue

Hello.
I try to compile XLibre on NetBSD with already X11 installed and working but it fails because dependencies are obsolete.
How to fix this?
Note that packagexyz-dev do not exist in NetBSD.
PS: A example of option parameters that should be used on NetBSD for meson will be welcome.
meson setup <prefix> build <meson_options>

Steps to reproduce

Try to build XLibre on NetBSD using this (adapted) : https://github.com/X11Libre/xserver/wiki/Building-XLibre

What did you expect?

A out-of-the-box compilation. ;-)

Additional Information

No response

Extra fields

• I have checked the existing issues
• I have read the Contributing Guidelines
• I'd like to work on this issue

[chankongus]

Try changing the meson setup from 1.4 to 1.2 (like with situation here which is almost the same problem...) or compile this dependency yourself so that you'd at least confirm if it compiles. There's no point in fixing this if it doesn't work later down the line.

[fredvs]

@chankongus : Thanks for the tip!

OK, this package must be installed:

pkgin install xorgproto

And now it compiles ok.

I did not change the meson setup.

I am ready now to continue the combat with ninja -C build
But I am not sure the parameters I used are ok for NetBSD:

meson setup --prefix="$(pwd)/image" build -Dxnest=false

[fredvs]

ninja -C build is ok, yep!

[fredvs]

Ok, I continue the combat.

I used this command for meson setup:

meson setup --prefix=/usr/X11R7 build -Dxnest=false

And this to compile/install:

ninja -C build
cd /build
ninja install

But after this, startx fails.
First, I get this error
Unrecognized option: noretro

So I removed in startx script the line with noretro.

But there are still errors and I am lost.
(Pictures added because I was not able to copy/paste the log file outside the NetBSD system)

Any light is welcome.

[cepelinas9000]

@fredvs you installed bare xserver with modesetting driver. Rest drivers are scattered at other repositories (see https://github.com/X11Libre). At a glance you need (not sure 100%):

• https://github.com/X11Libre/xf86-video-wsfb
• https://github.com/X11Libre/xf86-video-vesa
• https://github.com/X11Libre/xf86-input-mouse
• https://github.com/X11Libre/xf86-input-keyboard
• https://github.com/X11Libre/xf86-input-libinput (no idea it works on netbsd)

[metux]

If anybody could add NetBSD to our CI, that would be really great.

[callmetango]

I have created Add NetBSD to the Xserver CI build pipeline · Issue #936 · X11Libre/xserver to implement this idea.

[fredvs]

@fredvs you installed bare xserver with modesetting driver. Rest drivers are scattered at other repositories (see https://github.com/X11Libre). At a glance you need (not sure 100%):

* https://github.com/X11Libre/xf86-video-wsfb

* https://github.com/X11Libre/xf86-video-vesa

* https://github.com/X11Libre/xf86-input-mouse

* https://github.com/X11Libre/xf86-input-keyboard

* https://github.com/X11Libre/xf86-input-libinput (no idea it works on netbsd)

Thanks for the infos but I am still lost. Must I compile those drivers too and how to install when it is done.
Are there how-to that explain how to do this?

If anybody could add NetBSD to our CI, that would be really great.

I can do the packages once all is working ok on my NetBSD system.

[cepelinas9000]

Thanks for the infos but I am still lost. Must I compile those drivers too and how to install when it is done.
Are there how-to that explain how to do this?

install as usual no magic here (configure and then ninja install or make install), but for compilation you need to take care dependencies (see: X11Libre/xserver#714 (comment) )

In summary, If xserver installation is not in default search path, you need to provide prefixes using PKG_CONFIG_PATH and with autotools (sorry I don't have on hand now, just xserver install m4 file $prefix/share/aclocal/xorg-server.m4 )

[fredvs]

@cepelinas9000 , Ok thanks for your light, I will try.

[callmetango]

@fredvs You may also want to have a look at https://felipec.wordpress.com/2025/07/12/compilation .

[fredvs]

@callmetango: Thanks, I'll look into that.

Regarding driver compilation, can I use meson for configuration, like I did for a barebones X server?
And will the settings be correct with this:

meson setup --prefix=/usr/X11R7

(Sorry if the questions are stupid, I'm an explorer in a new jungle.)

[callmetango]

You can use meson for X11Libre/xf86-input-libinput, but most of the other/older drivers are still based on GNU Autotools - Wikipedia. So you need to run something like:

NOCONFIGURE=1 ./autogen.sh
./configure

You can pass command line arguments to configure as needed. Please run ./configure --help to see the available options.

Be advised that autogen.sh depends on GNU Autoconf, which itself depends at least on Libtool - GNU Project - Free Software Foundation. git may also be needed.

I will add these instructions to Building XLibre · X11Libre/xserver Wiki soon.

[fredvs]

@callmetango : Many thanks for your light, lot of meat there.

In summary, If xserver installation is not in default search path,

I installed the X server in /usr/X11R7, as this is the default directory used under NetBSD. But I may have made a mistake and should have installed it in a different directory, as installing in /usr/X11R7 overwrote the "official" X11 installation (but it may be useful to install it in the default directory as well).

[fredvs]

If you'd like to install NetBSD (a cool OS by the way) on VirtualBox, here's a clear explanation:
https://www.youtube.com/watch?v=VMC3fIj5IVQ

The video explains the installation of NetBSD 9.2 but also works with the latest version 10.1.
https://www.netbsd.org/releases/

[fredvs]

First try to compile https://github.com/X11Libre/xf86-video-vesa with
NOCONFIGURE=1 ./autogen.sh

But get error: must install xorg-macros 1.8 before using autogen.sh.

OK, fixed installing xorg-util-macros (package xorg-macros does not exist in NetBSD)
pkgin install xorg-util-macros

[fredvs]

Some news of the front.

This fixed the error: xf860openconsole Server must be suid root :

chmod u+s /usr/X11R7/bin/X

But still errors with startx or xinit: Fatal error: Cannot open log file "/usr/X11R7/var/log/Xorg.0.log" : No such file or directory.

It was solved with this:

mkdir -p /usr/X11R7/var/log
chmod 755 /usr/X11R7/var/log
chown root:wheel /usr/X11R7/var/log

Now, doing startx, no more error but only a black screen.
I think that, step by step, we will win.

[stefan11111]

Now, doing startx, no more error but only a black screen. I think that, step by step, we will win.

Anything in the log?
What is your .xinitrc?
Is the screen black because it's an X server with no clients, or because something went wrong?
Test this by manually starting an X client: DISPLAY=<display name, likely :0> <an X client, xterm or something>

[fredvs]

Anything in the log?

Yes, lot of things, (but no (EE) = error) sadly I cannot export the log file so I can only give screen shots, what do you need?
Here the first 4 pages:

What is your .xinitrc?

xfce4-session

Is the screen black because it's an X server with no clients, or because something went wrong?

I dont know, I am a few lost.

Test this by manually starting

How to do this?

[smj-cc]

I encountered only a black screen (and a mouse cursor. when I moved it enough to get it on the screen), when I switched from xf86-display-intel to modesetting.

All it was for me, was that I have two screens but only one in use, and xfce had discarded my settings, and chosen the closed screen as the default.

Likely not what what's happening for you.

[fredvs]

I tried "Driver "modesetting"", but the error "no display found" occurred. The only compatible drivers are vesa and vboxvideo, but the screen is completely black and the keyboard and mouse are unresponsive.
Note that there doesn't seem to be a crash, because the VirtualBox command "Send shutdown command to client" works. A few seconds later, the client shuts down.

[fredvs]

Maybe the issue is due because of the workaround I did for be able to compile vesa and vbox xlibre drivers.

I've edited the xf86-video-vbox and xf86-video-vesa configure files and commented out the problematic lines (syntax errors). I'm not sure this is entirely legal.

Those lines are commented:

 XORG_DRIVER_CHECK_EXT(RANDR, randrproto)
 XORG_DRIVER_CHECK_EXT(RENDER, renderproto)
 XORG_DRIVER_CHECK_EXT(DPMSExtension, xextprotoproto)

I am in the dark like the screen.
I will do a break.

[callmetango]

Thank you for reporting this issue and your work! It will be moved to X11Libre Xlibre On Other Distributions · Discussions · GitHub since it really is more of a discussion and has already enough attention to be dealt with there.

Once the remaining problems are solved we can add it to our CI pipeline.

[b-aaz]

@fredvs
I suggest you take a look at:
https://github.com/NetBSD/xsrc/tree/trunk/external/mit/xorg-server
and:
https://blog.netbsd.org/tnf/entry/x_org_on_netbsd_the
and:
https://github.com/NetBSD/pkgsrc/tree/trunk/x11/modular-xorg-server/patches

NetBSD maintains a "half fork" of X.Org, with many custom changes and a different build system so, it will not be easy to get XLibre running there OOTB.

[stefan11111]

https://blog.netbsd.org/tnf/entry/x_org_on_netbsd_the

Did you know that Nvidia [used to have](https://lwn.net/Articles/380704/) an open source graphics driver? It supported 2D acceleration for a range of cards. In NetBSD, it's retained for platforms that included embedded Nvidia chips and aren't capable of (or predate, or don't want) the modern novueau driver. Six years ago, it was updated in NetBSD to support EXA acceleration.

So netbsd has patches that port xf86-video-nv to exa.

@metux @ONykyf Maybe we should port them to our nv driver?

[fredvs]

@b-aaz : Many thanks for your attention (I've spent a few more sleepless nights without success, and your feedback is reassuring.)
Indeed, X11 on NetBSD isn't very easily accessible for developers (I had some trouble adapting MSEgui for NetBSD, unlike OpenBSD and FreeBSD).

But this is interesting: https://blog.netbsd.org/tnf/entry/x_org_on_netbsd_the
NetBSD shares some code with OpenBSD that could be interesting for XLibre.

Same goes for this: https://github.com/NetBSD/pkgsrc/tree/trunk/x11/modular-xorg-server/patches
Perhaps XLibre could find inspiration in these fixes.

So I think that for NetBSD and OpenBSD, it's better to let them develop their own fork of Xorg and, if possible, maintain good relationships with their developers and share fixes, ideas and new features together.

[callmetango]

@fredvs OpenBSD is already "xliberated": comment-14244557 - Liberated Screens · X11Libre · Discussion #211

[fredvs]

@fredvs OpenBSD is already "xliberated": comment-14244557 - Liberated Screens · X11Libre · Discussion #211

Hum, are you sure that OpenBSD is "xliberated"?
I don't see an image with it, I see FreeBSD "xliberated" but not OpenBSD (which has its own Xenocara fork of X11).

[fredvs]

Note that both (OpenBSD and NetBSD) have WIPs to maybe switch to Wayland but both have very little drive and enthusiasm to adopt it.

[fredvs]

Oooops, yes indeed there is a new OpenBSD "xliberated" by @cepelinas9000.
Wow so he replaced Xenocara by XLibre!

[callmetango]

I searched for "netbsd build system" on the internet and found these articles:

• Revisiting the NetBSD build system - by Julio Merino
• Part VI. Building the system
• Chapter 13. The build process

They may be helpful. Er, or not... This all seems very familiar to those who are Gentoonians. 😉

[fredvs]

Thanks, I'll look into it. I'm not really a NetBSD user. I installed it on a virtual machine to test/adapt a set of widgets using X11, but I never delved into the system.

[fredvs]

My humble diagnosis.
Since the log file doesn't contain any errors ("EE") and the system responds to a shutdown request (so no crash), but the screen is still black and the cursor isn't visible, the problem probably stems from the video driver.
On a VirtualBox machine, the xlibre vesa and vbox drivers work with startx or xinit (no screen not found).
So there's something to adapt for the NetBSD video drivers, but I don't have the expertise to know what.

[fredvs]

And I suggest enable port forwarding to ssh service into machine.

@cepelinas9000 : I did not yet reinstall everything from scratch using your steps but indeed, much more info using ssh, the screen in the VB machine is still black but now I can see those infos when running startx from the remote machine ( and I think you did have the same problem Undefined PLT symbol "xf86SlowBcopy" with OpenBSD ).

frednetbsd$ startx
xauth: (argv):1:  bad display name "frednetbsd.fredvs:0" in "list" command
xauth: (stdin):1:  bad display name "frednetbsd.fredvs:0" in "add" command
XLibre X Server 1.25.0
X Protocol Version 11, Revision 0
Current Operating System: NetBSD frednetbsd.fredvs 10.1 NetBSD 10.1 (GENERIC) #0: Mon Dec 16 13:08:11 UTC 2024  [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC amd64
Current version of pixman: 0.46.2
        Before reporting problems, check https://github.com/X11Libre/xserver
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/usr/X11R7/var/log/Xorg.0.log", Time: Fri Aug 29 22:49:25 2025
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/X11R7/share/X11/xorg.conf.d"
mtrr set failed: Operation not supported by device
/usr/X11R7/lib/xorg/modules/xlibre-25/drivers/vesa_drv.so: Undefined PLT symbol "xf86SlowBcopy" (symnum = 43)
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
xauth: (argv):1:  bad display name "frednetbsd.fredvs:0" in "remove" command

[cepelinas9000]

Apply that patch-for-vesa.patch on vesa driver or copy xf86SlowBcopy in vesa.c and compile & install

[fredvs]

Ok, done, added your patch and it compiles (with some warnings):

// took from hw/xfree86/os-support/misc/SlowBcopy.c
/* The outb() isn't needed on my machine, but who knows ... -- ost */
void
xf86SlowBcopy(unsigned char *src, unsigned char *dst, int len)
{
    while (len--)
        *dst++ = *src++;
}

And the excellent news is that there are no more errors loading the VESA driver.

But the fight isn't over yet; there's still resistance:

frednetbsd$ startx

XLibre X Server 1.25.0
X Protocol Version 11, Revision 0
Current Operating System: NetBSD frednetbsd.fredvs 10.1 NetBSD 10.1 (GENERIC) #0: Mon Dec 16 13:08:11 UTC 2024  [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC amd64
 
Current version of pixman: 0.46.2
        Before reporting problems, check https://github.com/X11Libre/xserver
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/usr/X11R7/var/log/Xorg.0.log", Time: Fri Aug 29 23:31:57 2025
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/X11R7/share/X11/xorg.conf.d"
mtrr set failed: Operation not supported by device
XKB: Failed to compile keymap
Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.

Fatal server error:
Failed to activate virtual core keyboard: 2

Please consult the XLibre support 
         at https://github.com/X11Libre/xserver
 for help. 
Please also check the log file at "/usr/X11R7/var/log/Xorg.0.log" for additional information.

(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
xauth: (argv):1:  bad display name "frednetbsd.fredvs:0" in "remove" command

And here errors in the log file:

[2025-08-29 23:31:57] (EE) AIGLX error: dlopen of /usr/pkg/lib/dri/swrast_dri.s>
[2025-08-29 23:31:57] (EE) AIGLX error: unable to load driver swrast
[2025-08-29 23:31:57] (EE) GLX: could not load software renderer
[2025-08-29 23:31:57] (II) GLX: no usable GL providers found for screen 0
[2025-08-29 23:31:57] (II) Initializing extension XFree86-VidModeExtension
[2025-08-29 23:31:57] (II) Initializing extension XFree86-DGA
[2025-08-29 23:31:57] (II) Extensions initialized
[2025-08-29 23:31:57] (II) Screen(s) initialized
[2025-08-29 23:31:57] (EE) XKB: Couldn't open rules file /usr/X11R7/share/X11/x>
[2025-08-29 23:31:57] (EE) XKB: Failed to load keymap. Loading default keymap i>
[2025-08-29 23:31:57] (EE) XKB: Couldn't open rules file /usr/X11R7/share/X11/x>
[2025-08-29 23:31:57] XKB: Failed to compile keymap
[2025-08-29 23:31:57] Keyboard initialization failed. This could be a missing o>
[2025-08-29 23:31:57]
Fatal server error:

[fredvs]

It seems that the vesa driver is working, but only for a flash, no black screen only a kind of chessboard show, but comes back to terminal because of the keyboard errors.

[fredvs]

This is the xorg.conf I used, with the XLibre xf86-input-keyboard and xf86-input-mouse drivers.

I dont get why error to load the keyboard, the vesa driver seems ok (flash with grey little boxes).

Section "ServerLayout"
    Identifier     "XLibre Layout"
    Screen         "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
    FontPath     "/usr/X11R7/lib/X11/fonts/misc/,/usr/X11R7/lib/X11/fonts/TTF/,/usr/X11R7/lib/X11/fonts/Type1/"
EndSection

Section "InputDevice"
    Identifier     "Keyboard0"
    Driver         "keyboard"
EndSection

Section "InputDevice"
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/input/mouse0"
EndSection

Section "Device"
    Identifier  "Video Card"
    Driver      "vesa"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device     "Video Card"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    EndSubSection
EndSection

I will stop for tonight and I am happy that the vesa driver works.
Of course any advice is welcome.

[fredvs]

Could you try start with "-retro" argument : it will draw classical pattern.

Still a black screen without cursor.

Another try use same patches as I used in OpenBSD case (https://github.com/orgs/X11Libre/discussions/346)

OK I will try.

And I suggest enable port forwarding to ssh service into machine.

OK, I will try. (I never used it for a VB machine, for forwarding data I use curl and it works ok).

[fredvs]

Another try use same patches as I used in OpenBSD case (https://github.com/orgs/X11Libre/discussions/346)

@cepelinas9000: Or maybe (surely) I have to start all over again, reinstall a fresh NetBSD + Xfce (i.e., with their X11 fork) and then follow the steps you did for OpenBSD adapted to NetBSD.

OK, asap.

[fredvs]

@cepelinas9000 : In case you also want to play explorer, you are of course very welcome! ;-)

[fredvs]

Yeeep!!

The trick was to do this:
ln -s /usr/pkg/share/X11/xkb /usr/X11R7/share/X11/xkb

Well, not yet perfect, the mouse does not respond so the fight is not totally terminated but this will be for a other day.

[b-aaz]

Congratulations!

[fredvs]

This is the end.

XLibre works perfectly on NetBSD.
Once again, the patches of @cepelinas9000 was a great help.
Adding this to xorg.conf made the mouse work:

Section "InputClass"
  Identifier "ForMouse"
  MatchIsPointer "on"
  Driver "mouse"
EndSection

It was a huge battle, and I apologize for monopolizing the discussion.
But the result is excellent.

Long live XLibre!

[callmetango]

Congratulations and very good you made it!

The timing is more than perfect because with this newest achievement we can Run a Social Media Mini-Series "Week of the Beasties" · X11Libre · Discussion #349.

[callmetango]

A feedback from 𝚟𝚒𝚗𝚜 (@[email protected]) - Mastodon in 𝚟𝚒𝚗𝚜: "@joel @XLibreDev the same ques…" - Mastodon:

the same question applies to NetBSD/xsrc: what about wscons input integration and the other downstream patches that the project keeps maintaining? https://blog.netbsd.org/tnf/entry/x_org_on_netbsd_the

[callmetango]

Replied in 𝚟𝚒𝚗𝚜: "@joel @XLibreDev the same ques…" - Mastodon:

Thank you for your questions! We forwarded them to https://github.com/orgs/X11Libre/discussions/339 .

The principle is the same here: We like to merge distribution specific patches if they are of general interest. The wscons driver for example seems to be available for several BSDs so it could benefit them all. The accelerated drivers sound interesting as well. We will take a look at this matter and evaluate the extent to which we can integrate these changes.

[fredvs]

Thank you for your questions! We forwarded them to https://github.com/orgs/X11Libre/discussions/339 .

Would it be possible for people (like me) who don't have a Mastodon account to copy and paste here what was said?
Thanks.

[callmetango]

Er, yes, it already has been done: The comment https://github.com/orgs/X11Libre/discussions/339#discussioncomment-14342801 is the question and the reply below https://github.com/orgs/X11Libre/discussions/339#discussioncomment-14344775 is the answer.