I purchased the following PC Case, which comes with a built-in Screen, and I have been facing screen rotation problems. I am hoping for some light at the end of the tunnel
According the manual you need a second display. And on MS Windows you need an additional tool (you need to pay for it) to setup this thing.
According your second screenshot, the display is following your settings of orientation when the OS is up. What happens when you chose to rotate it 90° in systemsettings?
Hi @hui thanks for reaching out.
Leaving the bios rotation aside, I should’ve made a note, but yes - 90° displays the monitor correctly in the real world but not virtually, thus giving the wrong rotation on Moonlight for gameplay streaming.
This is not an issue with remote protocols like vnc. It mirrors the correct aspect ratio.
The built-in screen needs connected for sunshine to mirror the display for game streaming via moonlight. Sunshine is the server installed on openSUSE and Moonlight is the client on Android, macOS, etc. There are no options in sunshine to fix rotation leaving me with having to fix it at the os level.
But the main problem is that I can’t move further since the Driver value is empty, as described in the original post.
Would leaving it blank or using amdgpu be okay for writing the rule under /lib/udev/hwdb.d/61-sensor-local.hwdb or similar .hwdb?
Also, would it even be 61-sensor-local.hwdb since they are using debian based distributions, openSUSE does not have a /dev/iio path. I can’t and will not switch to a debian based distribution. All of my work requires an rpm distribution (Autodesk Maya, rpm builds, etc).
Hi @malcolmlewis ! thanks for reaching out. Sadly I don’t have this. Could it be that its only available on tablets and not desktops? The monitor connects via HDMI via the external amdgpu.
Screen 0: minimum 16 x 16, current 1280 x 800, maximum 32767 x 32767
HDMI-A-1 connected primary 1280x800+0+0 left (normal left inverted right x axis y axis) 800mm x 1280mm
800x1280 59.93*+
I’m actually on Wayland for this specific machine. If running xrandr on x11 we get a slightly different output.
xrandr on x11
Screen 0: minimum 320 x 200, current 1280 x 800, maximum 16384 x 16384
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
HDMI-1 connected primary 1280x800+0+0 left (normal left inverted right x axis y axis) 800mm x 1280mm
800x1280 59.97*+
Doing xrandr --output HDMI-1 --rotate normal provides:
I dug into the BIOS, along with the manual and some research online, and am reviewing it again after your advice.
There are no options for changing the screen rotations. Only options are for selecting if the graphics adapter that I want to use are the CPU built in or my dedicate graphics via PCI-E and the speeds for it.
$ sudo demidecode -t 2
# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.2.1 present.
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ROG STRIX Z390-I GAMING
Version: Rev X.0x
Serial Number: 180835233601485
Asset Tag: Default string
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: Default string
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0
$ sudo demidecode -t bios
# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.2.1 present.
Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: 2812
Release Date: 10/12/2020
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 16 MB
Characteristics:
PCI is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 5.13
As for arandr, it seems like a front end for the xrandr cli, thus re-creating the same effect as if I were using regular xrandr on the command line.
$ sudo zypper search arandr
S | Name | Summary | Type
---+--------------------------------+--------------------------------------------------------------+--------
i+ | arandr | Visual Front End for XRandR | package
@hui I’m going to sit down now regarding the fbcon discussion on reddit (I also replied and shared this post there just in case anyone wants to shed some light into this).
Kernel Level Mastery it is! Let’s get dirty
First steps taken so far have been to check whether or not KMS is enabled which it is assumed to be enabled on Intel, AMD and nouveau type of GPU builds so I have no issues with with KMS (please confirm). I even went down in history lane memory for when SUSE first implemented fbcon
I will proceed replacing my current nvme storage so I don’t mess up my working install while attempting all this and get back to this post with results.
Please post any other findings you might find useful/supportive while I experiment on my end.
@mikeyjoel so no sort of monitor menu from those buttons, as in pressing the power button after it powers on? What if you plug the hdmi into a laptop or other system, is the orientation correct?
Update: The following statement cannot be more true after crack opening regardless of warranty. The ROM for the monitor itself was setup at factory 800x1280 instead of 1280x800.
I don’t have the original firmware for this nor could I find it anywhere. Might have to bring this up at one of the homebrew monitor forums to bring some monitor gurus up to speed to see if this can be modified.
