Ok, directory tree list sorting is not something fatal.

I have another question about the Linux Xcom version. I tried to activate famebuffer device (/dev/fb0) to run Xcom, but it still gives me "FATAL ERROR: failed to initialize graphics.".

I did this : Uncommented "GRUB_GFXMODE=640x480" entry in /etc/default/grub file, then:

1sudo update-grub
2sudo apt install v86d
3sudo modprobe uvesafb

Rebooted. Entered into second virtual terminal with <Alt>+<Ctrl>+<F2>, logged in my Linux user profile, started "./xcom64" and got "FATAL ERROR: failed to initialize graphics.".

What am I doing wrong or what am I missing?

analog_programmer wrote on 2026-10-10, 11:57:

I tried to activate famebuffer device (/dev/fb0) to run Xcom

/dev/fb0 is nowadays created and managed by the Linux kernel itself. You dont need to play with boot parameters or obsolete vesa modules (you can uninstall those).
If its not being created, then the creator of your Linux distribution has disabled it when they compiled the kernel.
If you can compile a kernel, go to make menuconfig
and enable Device Drivers / Graphics Support / Frame buffer Devices or something like that, then install the kernel to have the fb0 device show up.
Also ensure you trying to run xcom as root, otherwise the binary might cant access the /dev/fb0 device. (or use sudo if you dont have a root account)

XcomGUI wrote on 2026-10-10, 12:31:

Also ensure you trying to run xcom as root, otherwise the binary might cant access the /dev/fb0 device. (or use sudo if you dont have a root account)

This was it, thank you! I didn't tired "sudo ./xcom64", but actually it now loads. So, I'm suggesting my previous steps for Linux framebuffer activation are OK.

Just one more problem. There is no mouse active in after successful "landing" into Xcom desktop under Linux and I don't remember if there was some keyboard shortcut for the "start button" 😁

analog_programmer wrote on 2026-10-10, 12:47:

Just one more problem. There is no mouse active in after successful "landing" into Xcom desktop under Linux and I don't remember if there was some keyboard shortcut for "start button" 😁

Winkey is the start button.
Mouse uses /dev/input/mice.

sudo modprobe mousedev

Winkey absolutely refuses to work in my Linux Xcom 🙁 I have no idea why.

In "/dev/input/" I have "mice", but also "mouse0" and "mouse1" (probably due to USB attached mouse and deactivated laptop's touchpad). The command "sudo modprobe mousedev" gives me error "modprobe: FATAL: Module mousedev not found in directory lib/module/...bla-bla-bla-...[kernel version numbers]". Typical Linux problems.

analog_programmer wrote on 2026-10-10, 13:01:

Winkey absolutely refuses to work in my Linux Xcom 🙁 I have no idea why.

Unfortunately, the ascii codes for special keys are not standard in ttys and consoles.
I tried to support as many as i could, but there are always different variations and versions which fire the codes differently.

analog_programmer wrote on 2026-10-10, 13:01:

mice

Mice - as the name suggests - should be the one which contains all the mouse data of all the mouses in the system, and thats the primary one xcom tries to communicate with.

If you tell me on what linux distribution you are trying xcom, i could check what is going on with the mouse, and with the keyboard ascii codes. When next time i do a release, i might can fix them.
But if mousedev is not working on that distribution, then i am not sure if i can do anything about that. The alternative to mousedev is tty terminal mouse emulation, which linux doesnt supports, or system mouse iotctls, but those are only supported on freebsd afaik.

I'm currently trying Xcom on old Lubuntu version 22.04.5 LTS x86_64. My USB mouse and laptop's touchpad works perfectly fine in Lububtu's LXQt desktop environment, but I can not make them work in the virtual terminal with Xcom. At least Xcom now loads with root privileges, but without working mouse (or touchpad) and Winkey I can not use it.

Thanks for the tips.

P.S.

analog_programmer wrote on 2026-10-10, 11:57:

I did this : Uncommented "GRUB_GFXMODE=640x480" entry in /etc/default/grub file, then: […]
Show full quote

I did this : Uncommented "GRUB_GFXMODE=640x480" entry in /etc/default/grub file, then:

Copy code to clipboard

1sudo update-grub
2sudo apt install v86d
3sudo modprobe uvesafb

GRUB_GFXMODE=640x480 entry in "/etc/default/grub" file is only for display resolution of grub loader, so I commented it back. Aldo deinstalled "v86d", but Xcom for Linux still loads with "sudo ./xcom64". Seems like I can not remove kernel module "uvesafb" 😁

At least I managed to produce working one-executable-Xcom DOS version. So, enough Xcom tinkering for today.

analog_programmer wrote on 2026-10-10, 13:23:

At least I managed to produce working one-executable-Xcom DOS version. So, enough Xcom tinkering for today.

Thankyou, you helped me a lot by testing it. I will incorporate the things you have mentioned in the next release.
However, for me, its enough xcom thinkering for the year 😁
from now on i have to spend the time on different projects.

And I thank you, XcomGUI, for the latest usable Xcom version! I hope, that next year all Xcom users will sill be alive, healthy and here to play with next DOS, Linux and even BSD version 😀 And mentioning BSD version, I have to try some BSD system soon, since I never used one of these.