chimeraos
chimeraos copied to clipboard
ChimeraOS
Aya Neo Air Plus Orientation Issue
Hi all. I have an Aya Neo Air Plus, and I've flashed Chimera onto it. Unfortunately, the display in game mode is upside down and I can't find a way to fix it, or to reflash the ChimeraOS onto it. I've adjusted the orientation in desktop to Landscape, and Landscape flipped with no success. I was asked to check 'chimera/sys/devices/virtual/dmi/id/product_name` and the result came back as an Ayaneo 2S. So I assume Chimera is seeing the device as a 2s, rather than an air plus, and has adjusted the orientation accordingly.
I do have some tech knowledge, but not to this level. I can follow detailed step by step instructions though. I would be grateful of any help you can offer me and would be happy to offer any information required to solve this issue.
I don't see us doing anything in particular on the Ayaneo 2S so for whatever reason your BIOS is exposing the Air Plus as the Ayaneo 2S. You can use this kernel parameter to get the screen fixed, but this is a little concerning if this is indeed the case.
Add this to your kernel options at /boot/loader/entries/frzr.conf
video=eDP-1:panel_orientation=left_side_up
edited to remove a ' from the kernel parameter.
I don't see us doing anything in particular on the Ayaneo 2S so for whatever reason your BIOS is exposing the Air Plus as the Ayaneo 2S. You can use this kernel parameter to get the screen fixed, but this is a little concerning if this is indeed the case.
Add this to your kernel options at
/boot/loader/entries/frzr.confvideo=eDP-1:panel_orientation=left_side_up'
I added this text as you suggested, but the console still shows as being upside down, unfortunately.
Have you recently updated your BIOS?
No, I haven't done anything with the bios.
What is the output of this
cat /sys/class/dmi/id/product_name?
I found that folder in Chimera, as I couldn't find a "cat" entry. It output as being an Ayaneo 2S. The device is definitely an Ayaneo Air Plus Pro though.
I don't see us doing anything in particular on the Ayaneo 2S so for whatever reason your BIOS is exposing the Air Plus as the Ayaneo 2S. You can use this kernel parameter to get the screen fixed, but this is a little concerning if this is indeed the case. Add this to your kernel options at
/boot/loader/entries/frzr.confvideo=eDP-1:panel_orientation=left_side_up'I added this text as you suggested, but the console still shows as being upside down, unfortunately.
Oh this is the Air Plus Pro? Can you try using right_side_up instead of left?
I don't see us doing anything in particular on the Ayaneo 2S so for whatever reason your BIOS is exposing the Air Plus as the Ayaneo 2S. You can use this kernel parameter to get the screen fixed, but this is a little concerning if this is indeed the case. Add this to your kernel options at
/boot/loader/entries/frzr.confvideo=eDP-1:panel_orientation=left_side_up'I added this text as you suggested, but the console still shows as being upside down, unfortunately.
Oh this is the Air Plus Pro? Can you try using right_side_up instead of left?
I changed the text from left_side_up to right_side_up, but it still displays upside down.
I don't see us doing anything in particular on the Ayaneo 2S so for whatever reason your BIOS is exposing the Air Plus as the Ayaneo 2S. You can use this kernel parameter to get the screen fixed, but this is a little concerning if this is indeed the case. Add this to your kernel options at
/boot/loader/entries/frzr.confvideo=eDP-1:panel_orientation=left_side_up'I added this text as you suggested, but the console still shows as being upside down, unfortunately.
Oh this is the Air Plus Pro? Can you try using right_side_up instead of left?
I changed the text from left_side_up to right_side_up, but it still displays upside down.
I see..thanks. Can you provide the .gamescope-stdout.log and .gamescope-cmd.log logs created at your home directory?
I don't see us doing anything in particular on the Ayaneo 2S so for whatever reason your BIOS is exposing the Air Plus as the Ayaneo 2S. You can use this kernel parameter to get the screen fixed, but this is a little concerning if this is indeed the case. Add this to your kernel options at
/boot/loader/entries/frzr.confvideo=eDP-1:panel_orientation=left_side_up'I added this text as you suggested, but the console still shows as being upside down, unfortunately.
Oh this is the Air Plus Pro? Can you try using right_side_up instead of left?
I changed the text from left_side_up to right_side_up, but it still displays upside down.
I see..thanks. Can you provide the
.gamescope-stdout.logand.gamescope-cmd.loglogs created at your home directory?
wlserver: [backend/headless/backend.c:68] Creating headless backend wlserver: [libseat] [libseat/backend/seatd.c:64] Could not connect to socket /run/seatd.sock: No such file or directory wlserver: [libseat] [libseat/libseat.c:76] Backend 'seatd' failed to open seat, skipping wlserver: [libseat] [libseat/libseat.c:73] Seat opened with backend 'logind' wlserver: [backend/session/session.c:109] Successfully loaded libseat session ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment. ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment. ATTENTION: default value of option vk_xwayland_wait_ready overridden by environment. drm: warning: picking an arbitrary DRM device drm: Immediate flips are not supported by the KMS driver drm: found new connector 'DP-8' drm: found new connector 'DP-5' drm: found new connector 'DP-4' drm: found new connector 'DP-3' drm: found new connector 'DP-2' drm: found new connector 'DP-6' drm: found new connector 'DP-1' drm: found new connector 'DP-7' drm: Connector make AYA model AYANEOHD drm: [colorimetry]: EDID with colorimetry detected. Using it drm: [colorimetry]: r 0.648438 0.338867 drm: [colorimetry]: g 0.282227 0.602539 drm: [colorimetry]: b 0.142578 0.070312 drm: [colorimetry]: w 0.313477 0.329102 drm: found new connector 'eDP-1' drm: CRTC 72 has no VALVE1_CRTC_REGAMMA_TF support drm: CRTC 75 has no VALVE1_CRTC_REGAMMA_TF support drm: CRTC 78 has no VALVE1_CRTC_REGAMMA_TF support drm: CRTC 81 has no VALVE1_CRTC_REGAMMA_TF support drm: Connectors: drm: DP-8 (disconnected) drm: DP-5 (disconnected) drm: DP-4 (disconnected) drm: DP-3 (disconnected) drm: DP-2 (disconnected) drm: DP-6 (disconnected) drm: DP-1 (disconnected) drm: DP-7 (disconnected) drm: eDP-1 (connected) drm: selecting connector eDP-1 drm: selecting mode 1080x1920@60Hz vulkan: selecting physical device 'AMD Radeon Graphics (RADV REMBRANDT)': queue family 1 vulkan: physical device supports DRM format modifiers vulkan: supported DRM formats for sampling usage: vulkan: AR24 (0x34325241) vulkan: XR24 (0x34325258) vulkan: AB24 (0x34324241) vulkan: XB24 (0x34324258) vulkan: NV12 (0x3231564E) vulkan: AB4H (0x48344241) vulkan: XB4H (0x48344258) vulkan: AB48 (0x38344241) vulkan: XB48 (0x38344258) vulkan: AB30 (0x30334241) vulkan: XB30 (0x30334258) vulkan: AR30 (0x30335241) vulkan: XR30 (0x30335258) vulkan: 8945664 vs 8945664! vulkan: 8945664 vs 8945664! vulkan: 8945664 vs 8945664! wlserver: Running compositor on wayland display 'gamescope-0' wlserver: [backend/headless/backend.c:16] Starting headless backend wlserver: [backend/libinput/backend.c:87] Starting libinput backend wlserver: [backend/libinput/events.c:70] Adding Power Button [0:1] wlserver: [backend/libinput/events.c:70] Adding Video Bus [0:6] wlserver: [backend/libinput/events.c:70] Adding Lid Switch [0:5] wlserver: [backend/libinput/events.c:70] Adding Power Button [0:1] wlserver: [backend/libinput/events.c:70] Adding SIGMACH1P USB Keyboard [7247:21] wlserver: [backend/libinput/events.c:70] Adding SIGMACH1P USB Keyboard Consumer Control [7247:21] wlserver: [backend/libinput/events.c:70] Adding SIGMACH1P USB Keyboard System Control [7247:21] wlserver: [backend/libinput/events.c:70] Adding Logitech USB Optical Mouse [1133:49271] wlserver: [backend/libinput/events.c:70] Adding Goodix Capacitive TouchScreen [1046:911] wlserver: [backend/libinput/events.c:70] Adding AT Translated Set 2 keyboard [1:1] wlserver: [backend/libinput/backend.c:128] libinput successfully initialized wlserver: [xwayland/server.c:108] Starting Xwayland on :0 wlserver: [xwayland/server.c:108] Starting Xwayland on :1 ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. wlserver: [types/wlr_compositor.c:681] New wlr_surface 0x563cff24c9d0 (res 0x563cff403530) wlserver: [types/wlr_compositor.c:681] New wlr_surface 0x563cff1e64d0 (res 0x563cff38e720) wlserver: [xwayland/server.c:273] Xserver is ready wlserver: [xwayland/server.c:273] Xserver is ready pipewire: stream state changed: connecting pipewire: stream state changed: paused pipewire: stream available on node ID: 32 xwm: Embedded, no cursor set. Using left_ptr by default. xwm: Embedded, no cursor set. Using left_ptr by default. drm: [patched edid] Patching 1080x1920 -> 1920x1080 drm: [josh edid] BASE Checksum valid? Y drm: [josh edid] Wrote new edid to: /home/gamer/.config/gamescope/edid.bin wlserver: Updating mode for xwayland server #0: 1920x1080@60 vulkan: 8945664 vs 8945664! vulkan: 8945664 vs 8945664! vulkan: 8945664 vs 8945664! pipewire: renegotiating stream params (size: 1920x1080) wlserver: [types/wlr_compositor.c:681] New wlr_surface 0x563cff13d390 (res 0x563cff3c87d0) xwm: got the same buffer committed twice, ignoring. The XKEYBOARD keymap compiler (xkbcomp) reports: The XKEYBOARD keymap compiler (xkbcomp) reports:
Warning: Warning: Unsupported maximum keycode 708, clipping. Unsupported maximum keycode 708, clipping. X11 cannot support keycodes above 255. X11 cannot support keycodes above 255. Errors from xkbcomp are not fatal to the X server Errors from xkbcomp are not fatal to the X server wlserver: [backend/libinput/events.c:70] Adding Handheld Controller [1118:654] wlserver: [backend/libinput/events.c:140] Removing SIGMACH1P USB Keyboard [7247:21] wlserver: [backend/libinput/events.c:140] Removing SIGMACH1P USB Keyboard Consumer Control [7247:21] wlserver: [backend/libinput/events.c:140] Removing SIGMACH1P USB Keyboard System Control [7247:21] wlserver: [backend/libinput/events.c:70] Adding SIGMACH1P USB Keyboard [7247:21] wlserver: [backend/libinput/events.c:70] Adding SIGMACH1P USB Keyboard System Control [7247:21] wlserver: [backend/libinput/events.c:70] Adding SIGMACH1P USB Keyboard Consumer Control [7247:21] wlserver: [backend/libinput/events.c:140] Removing SIGMACH1P USB Keyboard [7247:21] wlserver: [backend/libinput/events.c:140] Removing SIGMACH1P USB Keyboard Consumer Control [7247:21] wlserver: [backend/libinput/events.c:140] Removing SIGMACH1P USB Keyboard System Control [7247:21] wlserver: [backend/libinput/events.c:70] Adding SIGMACH1P USB Keyboard System Control [7247:21] wlserver: [backend/libinput/events.c:70] Adding SIGMACH1P USB Keyboard [7247:21] wlserver: [backend/libinput/events.c:70] Adding SIGMACH1P USB Keyboard Consumer Control [7247:21] xwm: error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 2710 wlserver: [types/wlr_compositor.c:681] New wlr_surface 0x563cff1fc770 (res 0x563cff4366d0) xwm: Rejecting WM_CHANGE_STATE to ICONIC for window 0x400007 wlserver: [types/wlr_compositor.c:681] New wlr_surface 0x563cff13d390 (res 0x563cff30a4a0) xwm: got the same buffer committed twice, ignoring. drm: [patched edid] Patching 1080x1920 -> 1920x1080 drm: [josh edid] BASE Checksum valid? Y drm: [josh edid] Wrote new edid to: /home/gamer/.config/gamescope/edid.bin radv: Updated the per-vertex VRS rate to '0'. wlserver: [types/wlr_compositor.c:681] New wlr_surface 0x563cff4c2b30 (res 0x563cff1ec290) gamescope: received kill signal, terminating! xwm: Lost connection to the X11 server 0 xwm: X11 I/O error gamescope: received kill signal, terminating!
/usr/bin/gamescope -e --xwayland-count 2 -O *,eDP-1 --default-touch-mode 4 --hide-cursor-delay 3000 --fade-out-duration 200 -R /run/user/1000/gamescope.Xk2coej/startup.socket -T /run/user/1000/gamescope.Xk2coej/stats.pipe
They are going to have a lot more issues than just screen rotation with bad DMI data. HandyGCCS/OpenGamepadUI wont work right either. I think it is worth attempting to flash the BIOS to the one specified on the AYANEO website. https://www.ayaneo.com/support/download
There are three packages, one for the intel variant, one for the 6800U variant and one for the 7520/7320U variants. Be sure to verify your device CPU before flashing.
They are going to have a lot more issues than just screen rotation with bad DMI data. HandyGCCS/OpenGamepadUI wont work right either. I think it is worth attempting to flash the BIOS to the one specified on the AYANEO website. https://www.ayaneo.com/support/download
There are three packages, one for the intel variant, one for the 6800U variant and one for the 7520/7320U variants. Be sure to verify your device CPU before flashing.
My console is the 6800U variant. How can I flash the bios, given that I can't find a way to get into the recovery section? Or would I do better to try to get it back on to Windows and return it to the seller?
There are instructions in the BIOS flash download. You need a USB stick flashed to fat32 and you copy the files to the disk then boot from it.
There are instructions in the BIOS flash download. You need a USB stick flashed to fat32 and you copy the files to the disk then boot from it.
Thanks. I'll try this later as the battery is too low at the moment. Do I flash it with the console in desktop mode, gaming mode or from booting in?
There are instructions in the BIOS flash download. You need a USB stick flashed to fat32 and you copy the files to the disk then boot from it.
I've copied the files onto an SD card, but I've no idea what to do with them. There are no instructions in with them. There's a 16 and 32 version, but I've no idea which I need or how to use them. The SD card is formatted to FAT32.
There are instructions in the BIOS flash download. You need a USB stick flashed to fat32 and you copy the files to the disk then boot from it.
I've copied the files onto an SD card, but I've no idea what to do with them. There are no instructions in with them. There's a 16 and 32 version, but I've no idea which I need or how to use them. The SD card is formatted to FAT32.
Hmm, usually they have instructions. Copy the full contents of one of the two folders to the USB, making sure that the efi folder and bin file are the top level directory, don't just copy the folder itself but what is in it. reboot, enter the BIOS, and select the USB as the boot device.
There are instructions in the BIOS flash download. You need a USB stick flashed to fat32 and you copy the files to the disk then boot from it.
I've copied the files onto an SD card, but I've no idea what to do with them. There are no instructions in with them. There's a 16 and 32 version, but I've no idea which I need or how to use them. The SD card is formatted to FAT32.
Hmm, usually they have instructions. Copy the full contents of one of the two folders to the USB, making sure that the efi folder and bin file are the top level directory, don't just copy the folder itself but what is in it. reboot, enter the BIOS, and select the USB as the boot device.
I can't work out how to enter the bios. I don't know which button sequence gets me in. I have tried power and volume +, power and volume -, and also tried the R1 and R2 rear buttons in various combinations. It always boots to the desktop. I can copy the files OK. Does it matter if I use the 16 or 32 version?
I've managed to get to the bios and the device identifies as an S2 within the bios menu. I've changed the boot order to allow the SD card as first boot. It wouldn't boot from the card and just froze on the Ayaneo logo screen. I made sure the bios files were on the root of the card, and not in their folder. I also tried the same method with a card that has the ChimeraOS on it, but that hung on the Ayaneo logo as before.
I've got into recovery and flashed the bios, but the device won't boot at all now. It won't boot to the system or to the bios. It just gives a backlit screen whatever I do.
I've got into recovery and flashed the bios, but the device won't boot at all now. It won't boot to the system or to the bios. It just gives a backlit screen whatever I do.
Oh that's not good. You should contact the vendor you used.
I've contacted the vendor and they have agreed to exchange it. I'm sending it off to them today.