Open m4rk0Kruz opened 6 months ago
s390x? That is unusual, it will be good to hear how well things work on that architecture.
Anyway, it looks like the problem is failing to find a cursor theme installed. I think that apt install dmz-cursor-theme
should resolve that for you. If you don't have cursors installed, then you might well be missing fonts. So I'd recommend something like:
apt install dmz-cursor-theme fonts-freefont-ttf fonts-font-awesome
Good luck!
s390x every time is getting more support but unfortunately is still a long way to be completely stable... After isntalling the fonts and cursors, this time shows a adifferent error:
[2024-05-01 13:28:40.050459] <information> platform-generic-egl: Cannot enable linux-dmabuf import support: EGL_EXT_image_dma_buf_import_modifiers not supported
[2024-05-01 13:28:40.050519] < - debug - > platform-generic-egl: Detailed error: : /home/linux1/mir/src/platform/graphics/egl_extensions.cpp(225): Throw in function mir::graphics::EGLExtensions::EXTImageDmaBufImportModifiers::EXTImageDmaBufImportModifiers(EGLDisplay)
Dynamic exception type: boost::wrapexcept<std::runtime_error>
std::exception::what: EGL_EXT_image_dma_buf_import_modifiers not supported
[2024-05-01 13:28:40.496023] < - debug - > x11-error: Detected 0.00Hz host output refresh rate.
ERROR: /home/linux1/mir/src/platforms/renderer-generic-egl/buffer_allocator.cpp(178): Throw in function virtual std::shared_ptr<mir::graphics::Buffer> mir::graphics::egl::generic::BufferAllocator::alloc_software_buffer(mir::geometry::Size, MirPixelFormat)
Dynamic exception type: boost::wrapexcept<std::runtime_error>
std::exception::what: Trying to create SHM buffer with unsupported pixel format
Hopefully it can be solved installing a compatible component...
Can you provide a bit more information on the environment you are running in?
The "Selected display driver: mir:x11" indicates Mir is trying to run hosted by some existing X11 server you are using, is that GNOME?
The recent Trying to create SHM buffer with unsupported pixel format
error sounds like graphics hardware behaving in a way we didn't anticipate. Can you...
snap install graphics-test-tools
graphics-test-tools.drm-info
And post the output?
Actually, there's probably a shortage of snaps packaged for s390x...
sudo apt install drm-info
drm_info
The output shows
drmGetDevices: No such file or directory
Checking the list of defined devices, seems that there is no video device defined in the system, so, that might be the reason of the problem...
tenoch
description: Computer
width: 64 bits
capabilities: smp
*-core
description: Motherboard
physical id: 0
*-memory
description: System memory
physical id: 0
size: 4GiB
*-cpu:0
vendor: IBM/S390
physical id: 1
bus info: cpu@0
capabilities: esan3 zarch stfle msa ldisp eimm dfp edat etf3eh highgprs te vx vxd vxe gs vxe2 vxp sort dflt sie
*-cpu:1
vendor: IBM/S390
physical id: 2
bus info: cpu@1
capabilities: esan3 zarch stfle msa ldisp eimm dfp edat etf3eh highgprs te vx vxd vxe gs vxe2 vxp sort dflt sie
*-device:0
description: 3215 terminal
physical id: 1
bus info: ccw@0.0.0009
configuration: driver=3215
*-device:1
description: Card reader/punch
physical id: 2
bus info: ccw@0.0.000c
configuration: driver=vmur
*-device:2 DISABLED
description: Card reader/punch
physical id: 3
bus info: ccw@0.0.000d
configuration: driver=vmur
*-device:3 DISABLED
description: Line printer
physical id: 4
bus info: ccw@0.0.000e
configuration: driver=vmur
*-device:4
description: Direct attached storage device (FBA mode)
product: 9336/10
physical id: 5
bus info: ccw@0.0.0100
logical name: /dev/dasda
size: 50GiB (53GB)
configuration: driver=dasd-fba logicalsectorsize=512 sectorsize=512
*-device:5
description: Ethernet interface
product: 1732/01
physical id: 6
bus info: ccw@0.0.1000
logical name: enc1000
serial: 02:02:12:68:66:fb
size: 10Gbit/s
capabilities: ethernet physical fibre autonegotiation
configuration: autonegotiation=on broadcast=yes driver=qeth_l2 driverversion=5.15.0-105-generic duplex=full firmware=V730 ip=148.100.76.204 link=yes multicast=yes port=fibre speed=10Gbit/s
*-device:6
description: OSA-Express QDIO channel
product: 1732/01
physical id: 7
bus info: ccw@0.0.1001
configuration: driver=qeth
*-device:7
description: OSA-Express QDIO channel
product: 1732/01
physical id: 8
bus info: ccw@0.0.1002
configuration: driver=qeth
*-hvc_iucv0
description: z/VM IUCV device
physical id: 9
I'm new in the Linux world, so, I'm not sure how is the current X11 configuration, but definetly GNOME is not installed since it is the server version of Ubuntu, besides, the s390x runs in a hardware that doesnt have hardware dedicated for graphics. I will have to check the documentation to know if I can define video devices directly in ubuntu or if it will be needed a configuration at hardware level...
Thanks a lot for the provided support.
This seems like an odd system (no display hardware) to use Mir on. And running Mir on an X11 host is primarily for testing. What are you hoping to achieve?
So, at least one of the problems here is going to be that s390x is a big-endian architecture, and this affects the memory-layout of pixel data in a way that we don't support.
I think this is actually the only place this applies; if you wanted to check you could remove the #ifdef
and keep only the little-endian branch. Colours would be wrong, but you could see if the rest of Mir works.
After building mir in a s390x ubuntu OS following the instructions in this link I get the following output issuing the miral-shell command:
Any advises in how to get the miral shell running?
Thanks in advance.