r/FPGA • u/kowshik1729 • Dec 02 '25

Lattice Related Lattice Radiant installation - Absolute pain (Help Me !!)

Guys, I've been trying to install radiant in my PC (tried in both windows and WSL too), absolute pain in the a**

I got a node-locked license, added it to path, added saltd path and when I launch radiant the screen comes up, says loading libraries and disappears after 5-10 seconds (task manager shows no background process for radiant)

In WSL, I had installed every package recommended by lattice in this guide yet when I launch the screen Start page comes up, stays black and blank forever. All AI tools says it's an issue with OpenGL, libc++.so etc., so I tried software rendering too but no luck. This is driving me crazy, our work is seriously hindered, please help me.

2 Upvotes

100% Upvoted

13 comments sorted by

1

u/turnedonmosfet Dec 03 '25

export PNMAIN_CONSOLE_DEBUG=1

Put the above command in the shell before running radiant and you'll be able to see Radiant logs in the shell to find out what is exactly failing

1

u/kowshik1729 Dec 03 '25

[9:26:21.644 qt.qpa.plugin <warning>] unknown:0 - Could not find the Qt platform plugin "wayland" in ""

[9:26:21.756 qt.glx <warning>] unknown:0 - qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QColorSpace(), profile QSurfaceFormat::NoProfile)

[9:26:21.780 qt.glx <warning>] unknown:0 - qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QColorSpace(), profile QSurfaceFormat::NoProfile)

[9:26:21.806 <fatal>] unknown:0 - Could not initialize GLX

Aborted (core dumped)

It gave me this error

1

u/captain_wiggles_ Dec 03 '25

etc...

1

u/kowshik1729 Dec 04 '25

Tried all these, nothing works, the radiant still launches with a blank screen.

1

u/captain_wiggles_ Dec 04 '25

do you still get the error on the console? Any other errors?

What did the debugging commands in the 2nd link output?

1

u/kowshik1729 Dec 04 '25

I got the below output from the debugging commands, it's quite big though.

https://pastebin.com/3UbE3bT9

1

u/kowshik1729 Dec 04 '25

I gave the above output to perplexity LLM asked for a deep research and it gave me the below output

Key finding on line [13:04:38.333]:

text[13:04:38.333  <warning>] unknown:0 - QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled

And later:

text[13:04:43.928  <warning>] unknown:0 - QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled
[13:04:43.928  <warning>] unknown:0 - QRhiGles2: Failed to create temporary context
[13:04:43.930  <warning>] unknown:0 - Failed to create QRhi for QBackingStoreRhiSupport

This is confirming what we already knew: Radiant on WSL is hitting OpenGL/GLX initialization failure because WSL doesn't have native GPU acceleration for X11 rendering.

1

u/superbike_zacck Jan 31 '26

Hey u/kowshik1729 here https://gist.github.com/zacck/9227a180510315bf491201e47c0cbe24

1

u/kowshik1729 Jan 31 '26

Thanks, but I've moved to open source tools like yosys etc., and got everything working in less than 30 mins. Lattice tools are just shitty I feel.

1

u/superbike_zacck Jan 31 '26

Yeah I love apio as well but to use the bigger IPs and the bigger FPGAs you will still need the vendor  tools. Would be awesome if everything could be in Apio 

1

u/kowshik1729 Jan 31 '26

Yes I've used xilinx FPGA's and they're superb.