Regarding the relationship between the lack of OpenGL support in Slitaz 5.1 and the Radeon driver.

en hardware

Solved. The reply by shinji solved it.

shinji · 2026-10-21 13:42 UTC

This message was translated with machine translation.

Hello, my name is Shinji.

I only speak Japanese, so I am using machine translation. Please excuse any unnatural English.

I have been using SliTaz since June 2026. I have tried to solve this problem by reading websites and using AI, but I still could not understand it, so I would like to ask here.

When I boot slitaz-core-retro 5.1 from the Live CD, it starts in text mode instead of GUI mode.

Here is the error part from Xorg.0.log:

[    20.132] (II) LoadModule: "radeon"
[    20.133] (II) Loading /usr/lib/X11/modules/drivers/radeon_drv.so
[    20.177] (EE) Failed to load /usr/lib/X11/modules/drivers/radeon_drv.so: /usr/lib/X11/modules/drivers/radeon_drv.so: undefined symbol: exaWaitSync
[    20.177] (II) UnloadModule: "radeon"
[    20.177] (II) Unloading radeon
[    20.177] (EE) Failed to load module "radeon" (loader failed, 7)

Is this error related to the reason why GUI does not start?

Is it also related to missing OpenGL support?

I am a beginner and have been using Linux for only about one year.

Hardware information:

Laptop: Fujitsu NB18B
CPU: Mobile Pentium 4 1.8 GHz
Memory: 768 MB

lspci:
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD/ATI] RS200 Host Bridge (rev 02)
00:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] RS200/RS250 AGP Bridge
00:03.0 Modem: ULi Electronics Inc. M5457 AC'97 Modem Controller
00:04.0 Multimedia audio controller: ULi Electronics Inc. M5451 PCI AC-Link Controller Audio Device (rev 02)
00:06.0 Bridge: ULi Electronics Inc. M7101 Power Management Controller [PMU]
00:07.0 ISA bridge: ULi Electronics Inc. M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+]
00:0c.0 CardBus bridge: O2 Micro, Inc. OZ711M3/MC3 4-in-1 MemoryCardBus Controller
00:0c.1 CardBus bridge: O2 Micro, Inc. OZ711M3/MC3 4-in-1 MemoryCardBus Controller
00:0c.2 System peripheral: O2 Micro, Inc. OZ711Mx 4-in-1 MemoryCardBus Accelerator
00:0c.3 CardBus bridge: O2 Micro, Inc. OZ711M3/MC3 4-in-1 MemoryCardBus Controller
00:0c.4 CardBus bridge: O2 Micro, Inc. OZ711M3/MC3 4-in-1 MemoryCardBus Controller
00:0e.0 FireWire (IEEE 1394): NEC Corporation uPD72873 [Firewarden] IEEE1394a OHCI 1.1 Link/2-port PHY Controller (rev 01)
00:0f.0 IDE interface: ULi Electronics Inc. M5229 IDE (rev c4)
00:11.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10)
00:12.0 Multimedia controller: Philips Semiconductors SAA7130 Video Broadcast Decoder (rev 01)
00:13.0 USB controller: NEC Corporation OHCI USB Controller (rev 41)
00:13.1 USB controller: NEC Corporation OHCI USB Controller (rev 41)
00:13.2 USB controller: NEC Corporation uPD72010x USB 2.0 Controller (rev 02)
01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS200M [Radeon IGP 330M/340M/345M/350M]

pankso moderator · 2026-10-22 19:41 UTC

Hello Shinji,

Thank you for this very clear report. Your English is fine.

Yes, you found the real problem. The error "undefined symbol: exaWaitSync" is a bug in our build of the radeon driver, not a mistake on your side. The driver is built in a way that makes Xorg 1.12 unable to load it. We will fix the package and rebuild it.

And yes, it is related to OpenGL. Your Radeon IGP 340M is supported by Mesa (the "radeon" DRI driver), but OpenGL acceleration only works when the radeon X driver loads correctly.

Until the fix is published, you can start the desktop with the generic VESA driver. In text mode, log in as root and create this file:

/etc/X11/xorg.conf.d/20-vesa.conf

    Section "Device"
        Identifier "Card0"
        Driver "vesa"
    EndSection

Then run: startx

It will be slower and without 3D, but the desktop should work.

Could you also send us two things?
1. The full /var/log/Xorg.0.log (not only the error part).
2. The date in the name of your ISO file.

Normally Xorg should fall back to another driver by itself, so we want to understand why it stayed in text mode.

Thank you for using SliTaz on this old Pentium 4. This is exactly the kind of machine SliTaz is made for.

Christophe (pankso)

shinji · 2026-10-24 08:02 UTC

This message was translated with machine translation.

Hello, pankso.

I apologize. After having the AI ​​proofread the translation, some of the sentences changed.

"When I boot slitaz-core-retro 5.1 from the Live CD, it starts in text mode instead of GUI mode."

The correct sentence is:

"When I upgraded from slitaz 5.0 to slitaz-core-retro 5.1 using the Live CD, it started in CUI mode instead of GUI mode."

I apologize and correct this.

Currently, after performing a clean install of slitaz-core-retro 5.1 (not an upgrade installation), the original desktop appeared.

As you mentioned, it seems to be working with the VESA driver.

I've also attached the Xorg.0.log from the time of the upgrade installation and the current Xorg.0.log.

https://paste.slitaz.org/?17327885b01f4542#CSFyB6GF7NeUw6M798UTfqupk1xEf5VsyLg9s5Ve1Nh5

2026-10-18 12:10:41 +0900 slitaz-core-retro-i486-cooking.iso

I'm impressed by how little memory slitaz uses.

From shinji.

pankso moderator · 2026-10-24 18:29 UTC

Yeah!!! Very happy you got to the desktop with a fresh install.

I know we still have work to do about performing an upgrade from the installer.

Right now, the safest solutions for everyone is to perform a new install.

Regards,
- Pankso

shinji · 2026-10-24 23:45 UTC

Thank you very much.

Please feel free to contact me again if you need anything else.

Goodbye.

shinji · 2026-11-07 13:41 UTC · edited 2026-11-07 13:44 UTC · Solution

P.S.

Thank you for fixing the radeon driver.

The message "[20.177] (EE) Failed to load /usr/lib/X11/modules/drivers/radeon_drv.so: /usr/lib/X11/modules/drivers/radeon_drv.so: undefined symbol: exaWaitSync"

is no longer displayed, the radeon driver loads successfully, and the display is faster.

Also, although it's probably not recommended, the 'tazpkg up' command on my backup environment 'slitaz 5.0', which temporarily displayed the above error, now loads correctly after the update, and the GUI displays correctly.

Thank you very much.
1 thank you

pankso moderator · 2026-11-10 13:18 UTC

@shinji

Happy to read everything is fixed on your side!

Log in to reply Sign up