DietPi-Software | X.Org X Server: Start fails on Odroid C2 with mainline kernel #5234

berni2a · 2022-02-03T14:35:01Z

Creating a bug report/issue

Required Information

DietPi version | CORE 8 - 0 - 2
Distro version | 6
Kernel version | 5.10.81-meson64
SBC model | 12
Power supply used | (EG: 5V 2A
SDcard used | (EG: SanDisk ultra 16 GB

Additional Information (if applicable)

Software title | X Server
Was the software title installed freshly
Can this issue be replicated on a fresh installation of DietPi? --> yes

Bug report ID | echo $G_HW_UUID

Steps to reproduce

...I wanted to start MATE - Desktop - ended with error message
/var/log/Xorg.0.log shows --> (EE) Failed to module "fbturbo"
...

Expected behaviour

...Should start X - Server

Actual behaviour

...Server terminated

Extra details

...

The text was updated successfully, but these errors were encountered:

MichaIng · 2022-02-03T14:39:52Z

Many thanks for your report.

Hmm, on the new Odroid C2 image, the X server shouldn't even try to load fbturbo (or fbdev) but use modesetting instead. Can you show the full content of /var/log/Xorg.0.log, please?

MichaIng · 2022-02-03T14:45:55Z

Ah, I see, we still install the old xorg.conf, which has been fixed for DietPi v8.1 already. Please try:

rm /etc/X11/xorg.conf

Then the X server should start.

MichaIng · 2022-02-03T14:52:48Z

I changed this to be more failsafe: a3e37fa1
So if modesetting is not supported (should be with your image), then we install the fbturbo xorg.conf only when the fbturbo package is actually installed. Otherwise we install fbdev where the X server falls back to automatically without any xorg.conf required.

berni2a · 2022-02-03T14:58:41Z

Hello Micha,

Sorry, still not working...
(EE) Cannot run in framebuffer mode. Please specify bus IDs for all framebuffer devices

BR Bernd

MichaIng · 2022-02-03T15:02:30Z

Can you show the full content of /var/log/Xorg.0.log, please?

And:

ls -l /dev/dri

berni2a · 2022-02-03T15:11:09Z

ls -l /dev/dri
insgesamt 0
drwxr-xr-x 2 root root        100  3. Feb 15:51 by-path
crw-rw---- 1 root video  226,   0  3. Feb 15:51 card0
crw-rw---- 1 root video  226,   1  3. Feb 15:51 card1
crw-rw---- 1 root render 226, 128  3. Feb 15:51 renderD128
----------------------------------------------------------------------

[    18.512]    Entry deleted from font path.
[    18.512] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[    18.512]    Entry deleted from font path.
[    18.512] (==) FontPath set to:
        /usr/share/fonts/X11/misc,
        built-ins
[    18.512] (==) ModulePath set to "/usr/lib/xorg/modules"
[    18.513] (**) Extension "DPMS" is disabled
[    18.513] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[    18.513] (II) Loader magic: 0xaaaab6741e28
[    18.513] (II) Module ABI versions:
[    18.513]    X.Org ANSI C Emulation: 0.4
[    18.513]    X.Org Video Driver: 24.1
[    18.513]    X.Org XInput driver : 24.1
[    18.513]    X.Org Server Extension : 10.0
[    18.515] (++) using VT number 1

[    18.523] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[    18.526] (II) xfree86: Adding drm device (/dev/dri/card1)
[    18.531] (II) systemd-logind: got fd for /dev/dri/card1 226:1 fd 11 paused 0
[    18.532] (II) xfree86: Adding drm device (/dev/dri/card0)
[    18.534] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 12 paused 0
[    18.535] (II) no primary bus or device found
[    18.535]    falling back to /sys/devices/platform/soc/d0000000.apb/d00c0000.gpu/drm/card1
[    18.535] (II) LoadModule: "glx"
[    18.539] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    18.607] (II) Module glx: vendor="X.Org Foundation"
[    18.607]    compiled for 1.20.11, module version = 1.0.0
[    18.607]    ABI class: X.Org Server Extension, version 10.0
[    18.607] (==) Matched modesetting as autoconfigured driver 0
[    18.607] (==) Matched fbdev as autoconfigured driver 1
[    18.607] (==) Assigned the driver to the xf86ConfigLayout
[    18.607] (II) LoadModule: "modesetting"
[    18.607] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    18.613] (II) Module modesetting: vendor="X.Org Foundation"
[    18.613]    compiled for 1.20.11, module version = 1.20.11
[    18.613]    Module class: X.Org Video Driver
[    18.613]    ABI class: X.Org Video Driver, version 24.1
[    18.613] (II) LoadModule: "fbdev"
[    18.615] (WW) Warning, couldn't open module fbdev
[    18.615] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    18.615] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    18.615] (WW) Falling back to old probe method for modesetting
[    18.615] (II) modeset(0): using default device
[    18.615] (II) modeset(G0): using drv /dev/dri/card0
[    18.615] (EE)
Fatal server error:
[    18.615] (EE) Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devices
[    18.615] (EE)
[    18.615] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[    18.615] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    18.616] (EE)
[    18.643] (EE) Server terminated with error (1). Closing log file.

MichaIng · 2022-02-03T15:25:07Z

Hmm, so KMS/DRM is supported, it successfully loads the modesetting module, the fbdev module fails to load expectedly. Not sure why it crashes even trying to run in framebuffer mode.

GLES is installed, right?

G_AGI libegl1 libgles2

Are there any other X11 configs?

for i in /etc/X11/xorg.conf{,.d/*.conf}
do
[[ -f $i ]] || continue
echo "${i}:"
cat "$i"
done

berni2a · 2022-02-03T15:47:40Z

G_AGI libegl1 libgles2, it installed something

second question is to hard for me - sorry

MichaIng · 2022-02-03T15:53:17Z

Ah, the trailing single quote was not intended. I hope both packages did now install.

second question is to hard for me - sorry

If you are on an SSH console, simply copy and paste the above code block into the SSH console and hit return. It loops through all X11 configurations and prints their content.

berni2a · 2022-02-03T16:12:36Z

i am using PUTTY on my WINDOWS Computer and have NO idea where i shoud paste it? Sooory

Joulinar · 2022-02-03T16:16:54Z

Directly into Putty

MichaIng · 2022-02-03T16:39:03Z

Hit the copy button, which appears when you hover this code block:

for i in /etc/X11/xorg.conf{,.d/*.conf}
do
[[ -f $i ]] || continue
echo "${i}:"
cat "$i"
done

Then go to your PuTTY window and click the right mouse button, which pastes the copied code into the PuTTY terminal. Then hit return/enter to execute the command loop.

berni2a · 2022-02-03T16:51:44Z

Oh - thank you so much - this makes LINUX live much easier... :-) --> thats the outcome:

/etc/X11/xorg.conf.d/98-dietpi-disable_dpms.conf:
Section "Extensions"
    Option "DPMS" "Disable"
EndSection

Section "ServerFlags"
    Option "BlankTime" "0"
EndSection
root@DietPi:~#

MichaIng · 2022-02-03T17:21:34Z

Okay, strange that the X server does not succeed with KMS/DRM.

Btw, you did try to start it as root user, right?

Please try with a reboot once, just to rule that out. If it still fails the same way, try to use the fbdev driver:

apt install xserver-xorg-video-fbdev

berni2a · 2022-02-03T18:54:42Z

i have installed it but still not working :-(
see log-file

[    45.361] (--) using VT number 2
[    45.361] (II) systemd-logind: logind integration requires -keeptty and -keeptty was no>
[    45.363] (II) xfree86: Adding drm device (/dev/dri/card1)
[    45.364] (II) xfree86: Adding drm device (/dev/dri/card0)
[    45.376] (II) no primary bus or device found
[    45.376]    falling back to /sys/devices/platform/soc/d0000000.apb/d00c0000.gpu/drm/ca>
[    45.376] (II) LoadModule: "glx"
[    45.381] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    45.437] (II) Module glx: vendor="X.Org Foundation"
[    45.437]    compiled for 1.20.11, module version = 1.0.0
[    45.437]    ABI class: X.Org Server Extension, version 10.0
[    45.437] (==) Matched modesetting as autoconfigured driver 0
[    45.437] (==) Matched fbdev as autoconfigured driver 1
[    45.437] (==) Assigned the driver to the xf86ConfigLayout
[    45.437] (II) LoadModule: "modesetting"
[    45.437] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    45.443] (II) Module modesetting: vendor="X.Org Foundation"
[    45.443]    compiled for 1.20.11, module version = 1.20.11
[    45.443]    Module class: X.Org Video Driver
[    45.443]    ABI class: X.Org Video Driver, version 24.1
[    45.443] (II) LoadModule: "fbdev"
[    45.443] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    45.445] (II) Module fbdev: vendor="X.Org Foundation"
[    45.446]    compiled for 1.20.0, module version = 0.5.0
[    45.446]    Module class: X.Org Video Driver
[    45.446]    ABI class: X.Org Video Driver, version 24.0
[    45.446] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    45.446] (II) FBDEV: driver for framebuffer: fbdev
[    45.500] (WW) Falling back to old probe method for modesetting
[    45.509] (II) modeset(0): using default device
[    45.509] (WW) Falling back to old probe method for fbdev
[    45.509] (II) Loading sub module "fbdevhw"
[    45.509] (II) LoadModule: "fbdevhw"
[    45.511] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    45.514] (II) Module fbdevhw: vendor="X.Org Foundation"
[    45.514]    compiled for 1.20.11, module version = 0.0.2
[    45.514]    ABI class: X.Org Video Driver, version 24.1
[    45.515] (II) FBDEV(1): using default device
[    45.526] (II) modeset(G0): using drv /dev/dri/card0
[    45.526] (EE) Fatal server error:
[    45.526] (EE) Cannot run in framebuffer mode. Please specify busIDs        for all fra>
[    45.526] (EE)
[    45.526] (EE) Please consult the The X.Org Foundation support http://wiki.x.org for help.
[    45.526] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional i>
[    45.527] (EE)
[    45.685] (EE) Server terminated with error (1). Closing log file.

MichaIng · 2022-02-04T14:07:59Z

Okay, that is very strange. You do try to start it via startx as root user, right?

Another attempt would be to install the whole palette of possible DDX drivers, including the unaccelerated but very generic VESA driver:

apt install xserver-xorg-video-all

Also, while it should be all default, X11 could be explicitly configured to use modesetting:

cat << '_EOF_' > /etc/X11/xorg.conf.d/99-modesetting.conf
Section "Device"
    Identifier "Mali Graphics"
    Driver     "modesetting"
    Option     "AccelMethod"   "glamor"
EndSection
_EOF_

Also, since it is there, you can try to use the second DRI device by adding another line:

Option "kmsdev" "/dev/dri/card1"

to the section block of that file.

If it still does not work, would be interesting whether it does with the original Armbian image: https://dl.armbian.com/odroidc2/Bullseye_current
If this doesn't work either, it can be reported to the Armbian bug tracker: https://forum.armbian.com/forum/16-amlogic-s905x-s922x/

berni2a · 2022-02-10T10:49:04Z

Today I updated to version 8.1 - XSERVER still not starting.

Thank you for your support so far.

PD-Kerman · 2022-02-24T06:55:11Z

Has the problem solved? I have the same problem and i wanted to start LXDE desktop on k2, and after installation i've got this on my terminal:

root@DietPi:~# startx


X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
Build Operating System: linux Debian
Current Operating System: Linux DietPi 5.10.81-meson64 #21.08.6 SMP PREEMPT Mon                                                                                                     Nov 22 11:21:51 UTC 2021 aarch64
Kernel command line: root=UUID=17e9cd02-f1e8-4d56-b60e-bc7cc23604c9 rootwait roo                                                                                                    tfstype=ext4 console=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M                                                                                                     loglevel=4 ubootpart=2826a2a0-01 libata.force=noncq usb-storage.quirks=0x2537:0                                                                                                    x1066:u,0x2537:0x1068:u "net.ifnames=0"
Build Date: 16 December 2021  05:08:23PM
xorg-server 2:1.20.11-1+deb11u1 (https://www.debian.org/support)
Current version of pixman: 0.40.0
        Before reporting problems, check http://wiki.x.org
        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: "/var/log/Xorg.0.log", Time: Thu Feb 24 04:41:31 2022
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE)
Fatal server error:
(EE) Cannot run in framebuffer mode. Please specify busIDs        for all frameb                                                                                                    uffer devices
(EE)
(EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional info                                                                                                    rmation.
(EE)
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
root@DietPi:~# (EE) Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devices(EE) Cannot run in framebuffer mode. Please specify busIDs        for all framebuffer devicesdevices(EE) Cannot run in framebuffer mode. Please specify                                                                                                     xinit: giving upr all framebuffer devices
xinit: unable to connect to X server: Connection refused
xinit: server errornnect to X server: Connection refused
xinit: server error
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server errornnect to X server: Connection refused
xinit: server error
root@DietPi:~# (EE) Cannot run in framebuffer mode. Please specify busIDs                                                                                                            for all framebuffer devices(EE) Cannot run in framebuffer mode. Please specify                                                                                                     busIDs        for all framebuffer devices
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

PD-Kerman · 2022-02-24T06:58:52Z

and ive tried running lshw -c display and i cant see any thing about my display infomations , and then ive tried installing xserver-xorg-video-all on it but it didnt help

PD-Kerman · 2022-02-24T07:06:22Z

it looks like we're having a graphic card issue,(im using NanoPi K2, OS: DietPi v8.1.2, )(my lxde desktop was installed from dietpi-software), and ive been having this issue for a long time since i tried to install xfce4 on dietpi lastweek (ive tried both installation from dietpi-software and from apt, and ive got the same error)

MichaIng · 2022-02-24T15:07:22Z

Please test this:

cat << '_EOF_' > /etc/X11/xorg.conf.d/02-dietpi-aml-s905.conf
Section "OutputClass"
    Identifier "Amlogic"
    MatchDriver "meson"
    Driver "modesetting"
    Option "PrimaryGPU" "true"
EndSection
Section "Screen"
    Identifier "Default Screen"
    Device "Meson"
    Monitor "foo"
    DefaultDepth 24
    SubSection "Display"
        Depth 24
        Modes "1920x1080" "1440x900" "1280x720" "1280x1024" "1280x960" "1024x768" "800x600" "640x480" "720x400"
    EndSubSection
EndSection
_EOF_

- DietPi-Software | X.Org X Server: Resolved an issue on modern Odroid C2 and NanoPi K2 (Amlogic S905 SoC) images where the X server (desktop) failed to start. Many thanks to all users who reported and helped resolving this issue: #5234, https://dietpi.com/phpbb/viewtopic.php?t=10078

MichaIng · 2022-02-25T14:03:17Z

Solution implemented with: 572d1b3

PD-Kerman · 2022-02-26T12:19:37Z

OK i'll test that as soon as i can, and thank you for your reply btw

PD-Kerman · 2022-02-26T12:20:39Z

And One more issue by the way

PD-Kerman · 2022-02-26T12:28:13Z

we can not reach raw.githubusercontent.com in some area especially in china and for that reason, we can neither update nor initialize the dietpi system and use dietpi-software some times, so i hope we can have a solution on this issue

Joulinar · 2022-02-26T12:42:10Z

We are thinking to provide an image that contains a desktop ootb. But nothing we have a ETA for as it is just an idea. That you are not able to reach GitHub is a pity, as all our scripts are located there.

PD-Kerman · 2022-02-26T12:48:56Z

it is a pity...... but uhmm its strange that i can reach GitHub website BUT i cannot pulling scripts from raw.githubusercontent.com, and ive asked all my friends here and they cannot either

PD-Kerman · 2022-02-26T12:55:39Z

WOW so uhm dietpi is planning to build an image contains desktop ? Thats sooooo GOOD

MichaIng · 2022-02-26T13:07:54Z

it is a pity...... but uhmm its strange that i can reach GitHub website BUT i cannot pulling scripts from raw.githubusercontent.com, and ive asked all my friends here and they cannot either

That is a pity indeed, and if it was actively wanted, it doesn't make any sense either as any content can be seen here on GitHub the same way, only raw plain-text file downloads (which one can otherwise copy&paste) is done via raw.githubusercontent.com. I remember it was on some ad blocklist for e.g. Pi-hole a while back, but that seems to have been sorted.

At time of writing, we do not plan do host the DietPi repository at another place, or a mirror, where downloads could be done from when raw.githubusercontent.com is for whatever reason not available. Not sure whether using a different DNS nameserver is an option? This can be also done for the DietPi system only when assigning a static IP, or manually (and in case of DHCP temporarily), e.g. using Quad9 DNS:

echo 'nameserver 9.9.9.9' > /etc/resolv.conf

MichaIng · 2022-02-26T20:03:39Z

I'll mark this as closed. Initial issue solved for next release.

eevan78 · 2023-08-11T06:03:38Z

Yesterday I have tried to install LXDE on a freshly installed latest image for Odroid C2 and it didn't want to start. Upon finding this page and looking into commit 572d1b3 I spotted that because of the bad condition value in line 2725 it didn't install libegl1 and libgles2, and created the config file. After I did that manually, LXDE could start.

For my Odroid C2, the value of G_HW_MODEL is 12, and the condition in line 2725 reads:

elif (( $G_HW_ARCH < 10 && $G_HW_MODEL < 10 ))
			then
...

So it seems that the 10 in the second expression should be changed to 13.
But I haven't tried it.

MichaIng added Odroid C2 Investigating 🤔 labels Feb 3, 2022

MichaIng added this to the v8.1 milestone Feb 3, 2022

MichaIng added Bug 🐞 Solution available 🥂 Definite solution has been done Testing/testers required 🔽 and removed Investigating 🤔 labels Feb 3, 2022

MichaIng added Investigating 🤔 and removed Testing/testers required 🔽 Solution available 🥂 Definite solution has been done labels Feb 5, 2022

MichaIng modified the milestones: v8.1, v8.2 Feb 5, 2022

MichaIng changed the title ~~Odroid C2 X Server - does not start - failed to load module "fbturbo"~~ DietPi-Software | X.Org X Server: Start fails on Odroid C2 with mainline kernel Feb 5, 2022

MichaIng added Solution available 🥂 Definite solution has been done Testing/testers required 🔽 NanoPi K2 and removed Investigating 🤔 labels Feb 25, 2022

MichaIng mentioned this issue Feb 25, 2022

Beta v8.2.0 #5291

Merged

MichaIng unpinned this issue Feb 26, 2022

MichaIng removed the Testing/testers required 🔽 label Feb 26, 2022

MichaIng closed this as completed Feb 26, 2022

This was referenced Feb 26, 2022

Open Beta v8.2 | Please help testing and hardening the upcoming release #5319

Closed

Release v8.2 #5330

Merged

eevan78 mentioned this issue Aug 25, 2023

DietPi-Software | X.Org X Server: Start still fails on Odroid C2 with mainline kernel #6578

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

DietPi-Software | X.Org X Server: Start fails on Odroid C2 with mainline kernel #5234

DietPi-Software | X.Org X Server: Start fails on Odroid C2 with mainline kernel #5234

berni2a commented Feb 3, 2022

MichaIng commented Feb 3, 2022 •

edited

Loading

MichaIng commented Feb 3, 2022

MichaIng commented Feb 3, 2022

berni2a commented Feb 3, 2022

MichaIng commented Feb 3, 2022

berni2a commented Feb 3, 2022 •

edited by MichaIng

Loading

MichaIng commented Feb 3, 2022 •

edited

Loading

berni2a commented Feb 3, 2022 •

edited by Joulinar

Loading

MichaIng commented Feb 3, 2022

berni2a commented Feb 3, 2022

Joulinar commented Feb 3, 2022

MichaIng commented Feb 3, 2022

berni2a commented Feb 3, 2022 •

edited by Joulinar

Loading

MichaIng commented Feb 3, 2022

berni2a commented Feb 3, 2022 •

edited by Joulinar

Loading

MichaIng commented Feb 4, 2022 •

edited

Loading

berni2a commented Feb 10, 2022

PD-Kerman commented Feb 24, 2022 •

edited by Joulinar

Loading

PD-Kerman commented Feb 24, 2022

PD-Kerman commented Feb 24, 2022

MichaIng commented Feb 24, 2022 •

edited

Loading

MichaIng commented Feb 25, 2022

PD-Kerman commented Feb 26, 2022

PD-Kerman commented Feb 26, 2022

PD-Kerman commented Feb 26, 2022

Joulinar commented Feb 26, 2022

PD-Kerman commented Feb 26, 2022

PD-Kerman commented Feb 26, 2022

MichaIng commented Feb 26, 2022

MichaIng commented Feb 26, 2022

eevan78 commented Aug 11, 2023

DietPi-Software | X.Org X Server: Start fails on Odroid C2 with mainline kernel #5234

DietPi-Software | X.Org X Server: Start fails on Odroid C2 with mainline kernel #5234

Comments

berni2a commented Feb 3, 2022

Creating a bug report/issue

Required Information

Additional Information (if applicable)

Steps to reproduce

Expected behaviour

Actual behaviour

Extra details

MichaIng commented Feb 3, 2022 • edited Loading

MichaIng commented Feb 3, 2022

MichaIng commented Feb 3, 2022

berni2a commented Feb 3, 2022

MichaIng commented Feb 3, 2022

berni2a commented Feb 3, 2022 • edited by MichaIng Loading

MichaIng commented Feb 3, 2022 • edited Loading

berni2a commented Feb 3, 2022 • edited by Joulinar Loading

MichaIng commented Feb 3, 2022

berni2a commented Feb 3, 2022

Joulinar commented Feb 3, 2022

MichaIng commented Feb 3, 2022

berni2a commented Feb 3, 2022 • edited by Joulinar Loading

MichaIng commented Feb 3, 2022

berni2a commented Feb 3, 2022 • edited by Joulinar Loading

MichaIng commented Feb 4, 2022 • edited Loading

berni2a commented Feb 10, 2022

PD-Kerman commented Feb 24, 2022 • edited by Joulinar Loading

PD-Kerman commented Feb 24, 2022

PD-Kerman commented Feb 24, 2022

MichaIng commented Feb 24, 2022 • edited Loading

MichaIng commented Feb 25, 2022

PD-Kerman commented Feb 26, 2022

PD-Kerman commented Feb 26, 2022

PD-Kerman commented Feb 26, 2022

Joulinar commented Feb 26, 2022

PD-Kerman commented Feb 26, 2022

PD-Kerman commented Feb 26, 2022

MichaIng commented Feb 26, 2022

MichaIng commented Feb 26, 2022

eevan78 commented Aug 11, 2023

MichaIng commented Feb 3, 2022 •

edited

Loading

berni2a commented Feb 3, 2022 •

edited by MichaIng

Loading

MichaIng commented Feb 3, 2022 •

edited

Loading

berni2a commented Feb 3, 2022 •

edited by Joulinar

Loading

berni2a commented Feb 3, 2022 •

edited by Joulinar

Loading

berni2a commented Feb 3, 2022 •

edited by Joulinar

Loading

MichaIng commented Feb 4, 2022 •

edited

Loading

PD-Kerman commented Feb 24, 2022 •

edited by Joulinar

Loading

MichaIng commented Feb 24, 2022 •

edited

Loading