You are not logged in.
Hello,
About a year without using X-plane 11 and I find out it won't initialize anymore.
It's getting stuck at "will init net" on the loading window.
I figured out that the issue starts from the 6.9 kernel:
https://www.x-plane.com/kb/fixing-x-pla … -on-linux/
Running "./X-Plane-x86_64 --disable_networking" Loads the flight but I'm guessing here: it is preventing zhsi to connect to zibo.
Using "ipv6.disable=1" as a kernel parameter does XP11 load the main menu but crashes while loading the flight.
Are there actually any workaround (official or not)?
If not, I'm thinking about installing the newest kernel before 6.9 which should be:
linux-lts-6.6.72-1-x86_64.pkg.tar.zst
or
linux-6.8.arch1-1-x86_64.pkg.tar.zst
From:
https://archive.archlinux.org/packages/l/
I don't really know how/if nvidia drivers would work using these older kernels though.
:01:07.811 I/OVR: User is leaving the holodeck.
0:01:07.811 E/SYS: MACIBM_alert: Failed to initialize UDP network connectivity. (RAKNET)
0:01:07.811 E/SYS: MACIBM_alert: This is almost certainly because you are already running another copy of X-Plane on the same computer.
0:01:07.811 E/SYS: MACIBM_alert: Another possibility is that you turned off IPv6 support in your operating system. X-Plane requires at least link-local IPv6 connectivity.
0:01:07.811 E/SYS: MACIBM_alert: Be sure that IPv6 support is on, and restart your computer to be sure that no other instance of X-Plane is running in the background. If it still fails, please check the Log.txt file for entries of type E/NET and W/NET for details.
0:01:07.811 E/SYS: MACIBM_alert: /jenkins/design-triggered/source_code/engine/inet/inet_main.cpp:284
0:01:21.661 E/SYS: +-------------------------------------------------------------------------------
0:01:21.661 E/SYS: | Failed to initialize UDP network connectivity. (RAKNET)
0:01:21.661 E/SYS: | This is almost certainly because you are already running another copy of X-Plane on the same computer.
0:01:21.661 E/SYS: | Another possibility is that you turned off IPv6 support in your operating system. X-Plane requires at least link-local IPv6 connectivity.
0:01:21.661 E/SYS: | Be sure that IPv6 support is on, and restart your computer to be sure that no other instance of X-Plane is running in the background. If it still fails, please check the Log.txt file for entries of type E/NET and W/NET for details.
0:01:21.661 E/SYS: | (inet_main.cpp:284)
0:01:21.661 E/SYS: +-------------------------------------------------------------------------------
0:01:21.661 D/STM: Transitioning from state state_Normal to state_ShuttingDown
zhsi-plugin: XPluginStop
zhsi-plugin: XPluginStop : call backs terminated
zhsi-plugin: XPluginStop : memory freed
zhsi-plugin: XPluginStop : threads terminated
2025-05-18 10:56:07 librain[plugin.c:662]: librain unloaded
Zibomod plugin unloaded.
Thanks!
Last edited by felipescotti (2025-05-18 18:45:03)
Offline
Don't just use old binary kernels, especially EOL ones. 6.6 is an lts kernel, so use https://aur.archlinux.org/packages/linux-lts66. nvidia should work fine, you'll need to use DKMS.
Offline
Don't just use old binary kernels, especially EOL ones. 6.6 is an lts kernel, so use https://aur.archlinux.org/packages/linux-lts66. nvidia should work fine, you'll need to use DKMS.
That worked, thanks for the help!
I'm wondering what's gonna be when no kernel under 6.9 will be available anymore, I hope there will be a proper workaround until there.
Offline
6.6 goes EOL in Dec of next year. 6.1 is on the old schedule and gets another year after that.
Looks like the proper 'workaround' is to update to X-Plane 12.
Offline
6.6 goes EOL in Dec of next year. 6.1 is on the old schedule and gets another year after that.
Looks like the proper 'workaround' is to update to X-Plane 12.
Sounds good! My system also feels snappier with the LTS kernel.
Yeap, expensive workaround though , apparently Laminar research said they won't fix it for X-Plane 11.
Offline
hrmm... If it ever worked in an older kernel and breaks on newer ones, doesn't that generally fall under the "kernel shouldn't break userspace" rule? Or do X-Plane use their own kernel driver/module? Might be worth a bug report to the LKML if that is not the case.
Offline
Don't just use old binary kernels, especially EOL ones. 6.6 is an lts kernel, so use https://aur.archlinux.org/packages/linux-lts66. nvidia should work fine, you'll need to use DKMS.
EDIT: Don't bother, I got this error earlier but I end up fixing it just by re/installing the upstream kernel's headers (it may be replaced when I installed the LTS)
"The Lts kernel is working fine, but when I try to boot the upstream kernel (for test reasons) I'm getting a faltal error when starting the X.
Can you tell me if I'm still supposed to comment the KMS on /etc/mkinitcpio.conf and add nvidia_drm.modeset=1 nvidia-drm.fbdev=1 to the kernel parameters when using the Nvidia DKMS driver?
I'm not sure what I missed from the:
https://wiki.archlinux.org/title/NVIDIA
Fatal server error:
[ 102.755] (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
"
Thanks again!
Last edited by felipescotti (2025-05-21 01:17:57)
Offline
hrmm... If it ever worked in an older kernel and breaks on newer ones, doesn't that generally fall under the "kernel shouldn't break userspace" rule? Or do X-Plane use their own kernel driver/module? Might be worth a bug report to the LKML if that is not the case.
Hi, If I'm correct X-plane developers kinda focus the linux version on Debian stable (older kernel). Still I read that the X-Plane 12 has already been patched, but they will not patch the X-Plane 11 as it's not receiving updates anymore but I'd guess that when Debian stable reaches the 6.9 kernel they should patch it.
Cool! I can search for the "kernel shouldn't break userspace" rule. I'm curious about what was this changing in netlink handling for, security reasons?! efficiency?! Do you know about it breaking other than X-Plane?
Thank you!
Last edited by felipescotti (2025-05-21 01:42:05)
Offline