Mageia on GPD Win Max, can it?

This forum is dedicated to basic help and support :

Ask here your questions about basic installation and usage of Mageia. For example you may post here all your questions about getting Mageia isos and installing it, configuring your printer, using your word processor etc.

Try to ask your questions in the right sub-forum with as much details as you can gather. the more precise the question will be, the more likely you are to get a useful answer

Re: Mageia on GPD Win Max, can it?

Postby Sabungayam » Aug 29th, '20, 17:14

Ok, I see that, was trying in normal user but then when I logged out to go to classic mode... it died. Couldn't get X back.

I'll have to start again another time. It's late here. Thank you very much for you help.

IF there is an other advice to correct my errors from the output I sent above, I will look for them here tomorrow.

Thank you very much again.
Sabungayam
 
Posts: 173
Joined: Aug 18th, '20, 06:52

Re: Mageia on GPD Win Max, can it?

Postby Sabungayam » Aug 29th, '20, 17:19

I see, I was trying in nomral user, logging out to try to select classic mode lost X. It never came back and also only in the actual desktop session is it in a readable resolution. In login it's quad blurred again.

It is very late here. I will try to continue with this tomorrow. It would help if I can set that resolution at the start in grub2 parameters. I will try that later.

Thank you very much for you time. If there is anything from the shots above that also can help fix my errors here, I will look for that info tomorrow.

Thank you very much for you help.
Sabungayam
 
Posts: 173
Joined: Aug 18th, '20, 06:52

Re: Mageia on GPD Win Max, can it?

Postby Sabungayam » Aug 29th, '20, 18:16

These are the Grub2 boot setups in M7.1. You commented not knowing what the driver setup was. I actually tried passing the xdriver=free to M8 but it did not change anything and it just hung at a black screen with cursors.

Here I find myself confused & frustrated. 1st, vga=788 is the 800x600 that seems to work in Gnome. I tried 789 and 814 all associated with 800x600. It seems as if any parameters for VGA are being ignored.

When I use nomodesetting or xdriver=modesetting that will give a screen though rotated wrongly that can be read. But it will fail to finish the boot process and give you X.

Leaving it alone and just booting is the blurry screen issue and it will make it to the desktop. It seems to actually only accept this vga=788 parameter if those modesetting parameters are used which it doesn't ignore. Just as it ignored the rotation parameter when added.

It seems at least coming from live there is some limit to what can be done with Grub2 here? I think there is also a screenshot, grub will not accept those commands "videoinfo" or "vbeinfo".
Attachments
20200830_003917s.jpg
20200830_003917s.jpg (805.71 KiB) Viewed 3574 times
20200830_004444s.jpg
20200830_004444s.jpg (704.6 KiB) Viewed 3574 times
20200830_003940s.jpg
20200830_003940s.jpg (730.78 KiB) Viewed 3574 times
Sabungayam
 
Posts: 173
Joined: Aug 18th, '20, 06:52

Re: Mageia on GPD Win Max, can it?

Postby doktor5000 » Aug 29th, '20, 18:57

Sabungayam wrote:[root@DESKTOP-83KB56K live]# xrandr --addmode VGA0 "1280x800_59.70"
xrandr: cannot find output "VGA0"
[...]
I guess because it's not using "VGA"?


VGA0 would be the name of the output. As you're running wayland only output in your command is XWAYLAND0.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Mageia on GPD Win Max, can it?

Postby Sabungayam » Aug 30th, '20, 03:12

Ok, I will try to get into live again later today. I have meetings all day. So no chance until evening.

Is there anything that can solve the grub issue? As my images show. Parameters are not accepted or ignored.

If my observation is correct, vga=788 is used when I add 3 parameters that are not ignored.

they are:
nomodesetting
xdriver=modesetting
nokmsboot

when I add those parameters I won't make it to X but I will have until it crashes, legible framebuffer mode.

If I don't add those 3 parameters then it's all blurred with incorrect screen size apparently chosen/detected.

Any fixes, work arounds, or solutions?

Also as my image shows why are the apparent options at the grub2 prompt limited? It has no options for the vga?

I hope this is not jumping around. What process is used is I do a net install? How does that image detect? If I install from this method will it be the same as live or perhaps different?

Since everything seems to work it's the screen issue that needs to be overcome. Perhaps Live modes at this time can't detect this due to the irregular screen size.

I will check back later, thank you very much for your help.
Sabungayam
 
Posts: 173
Joined: Aug 18th, '20, 06:52

Re: Mageia on GPD Win Max, can it?

Postby Sabungayam » Aug 30th, '20, 06:54

Another thought, but maybe it is off the primary topic of the screen... sorry if it is.

In the link you gave me about the VESA BiOS extension, it mentions most modern hardware today responds well to modesetting. SO modesetting was briefly mentioned.

In this instance of Failure, when "nomodesetting" or xdriver=modesetting (which as I understand it makes it wait until X is starting) then it is giving an error about the codecs for sound as seen in one of my images earlier.

If then it is possible to get a screen resolution that works with VGA=788, but we fail to make it to X, are there parameters than can, skip the sound issue, why should it freeze there? OR can be given to enable it to successfully do whatever it evidently can do in normal boot (but without vga=788.) to make it to X?

Probably specific to newer hardware. I don't know why it gives only the blank screen in M8/Cauldron if there are any suggested commands to seek details I will give them a try if I find them here. I will try a M8 Gnome-Live later just to see... but Plasma & Xfce didn't work. Just stuck at the black screen when X starts.
Sabungayam
 
Posts: 173
Joined: Aug 18th, '20, 06:52

Re: Mageia on GPD Win Max, can it?

Postby Sabungayam » Aug 30th, '20, 12:55

:o Gnome Cauldron/8 is up. Same issues but at the black screen with cursor just hit ctrl+alr+back and it started X?

Will have a try with Plasma. This is the lspcidrke output from M8 if it helps as it is different and recognizes more.

I have noted that in Gnome here, it's rotation is incorrect. I am using portrait because it thinks landscape is the way the screen is rotated incorrectly. Don't recall this with M7.1 Plasma.

Code: Select all
live@DESKTOP-83KB56K ~]$ lspcidrake -v
thunderbolt     : Intel Corporation|Ice Lake Thunderbolt 3 NHI #0 [SYSTEM_OTHER] (vendor:8086 device:8a17) (rev: 03)
i2c_i801        : Intel Corporation|Ice Lake-LP SMBus Controller [SERIAL_SMBUS] (vendor:8086 device:34a3 subv:8086 subd:7270) (rev: 30)
xhci_pci        : Intel Corporation|Ice Lake-LP USB 3.1 xHCI Host Controller [SERIAL_USB] (vendor:8086 device:34ed subv:8086 subd:7270) (rev: 30)
Card:Intel 810 and later: Intel Corporation|Iris Plus Graphics G7 [DISPLAY_VGA] (vendor:8086 device:8a52 subv:8086 subd:2212) (rev: 07)
unknown         : Intel Corporation|Device 34ef [MEMORY_RAM] (vendor:8086 device:34ef subv:8086 subd:7270) (rev: 30)
intel_lpss_pci  : Intel Corporation|Ice Lake-LP Serial IO SPI Controller #1 (vendor:8086 device:34ab subv:8086 subd:7270) (rev: 30)
unknown         : Intel Corporation|Device 34be [BRIDGE_PCI] (vendor:8086 device:34be) (rev: 30)
unknown         : Intel Corporation|Ice Lake-LP PCI Express Root Port #9 [BRIDGE_PCI] (vendor:8086 device:34b0) (rev: 30)
intel_lpss_pci  : Intel Corporation|Ice Lake-LP Serial IO I2C Controller #0 (vendor:8086 device:34e8 subv:8086 subd:7270) (rev: 30)
iwlwifi         : Intel Corporation|Wi-Fi 6 AX200 [NETWORK_OTHER] (vendor:8086 device:2723 subv:8086 subd:008c) (rev: 1a)
unknown         : Intel Corporation|Device 8a12 [BRIDGE_HOST] (vendor:8086 device:8a12 subv:8086 subd:7270) (rev: 03)
snd_hda_intel   : Intel Corporation|Smart Sound Technology Audio Controller [MULTIMEDIA_AUDIO_DEV] (vendor:8086 device:34c8 subv:10ec subd:111c) (rev: 30)
intel_lpss_pci  : Intel Corporation|Ice Lake-LP Serial IO UART Controller #0 [COMMUNICATION_OTHER] (vendor:8086 device:34a8 subv:8086 subd:7270) (rev: 30)
r8169           : Realtek Semiconductor Co., Ltd.|RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [NETWORK_ETHERNET] (vendor:10ec device:8168 subv:10ec subd:0123) (rev: 15)
unknown         : Intel Corporation|Ice Lake-LP SPI Controller (vendor:8086 device:34a4 subv:8086 subd:7270) (rev: 30)
unknown         : Intel Corporation|Ice Lake Thunderbolt 3 PCI Express Root Port #0 [BRIDGE_PCI] (vendor:8086 device:8a1d subv:0060 subd:0000) (rev: 03)
mei_me          : Intel Corporation|Management Engine Interface [COMMUNICATION_OTHER] (vendor:8086 device:34e0 subv:8086 subd:7270) (rev: 30)
unknown         : Silicon Motion, Inc.|Device 2263 (vendor:126f device:2263) (rev: 03)
Last edited by doktor5000 on Aug 30th, '20, 22:35, edited 1 time in total.
Reason: added code tags
Sabungayam
 
Posts: 173
Joined: Aug 18th, '20, 06:52

Re: Mageia on GPD Win Max, can it?

Postby Sabungayam » Aug 30th, '20, 14:49

My experiments today... I found Mageia 8/Cauldron does boot here but, not only in Gnome.

I was beginning to think it only liked Wayland. However in the 3 images attached.

Rotation is way off. It does not seem to actually accept that the screen is rotated and takes the screens portrait default as the corret. I roated it here as said before to portrate. Due to how LIVE does not set up X, perhaps the only way yo fix this is in an install where Xorg can be given specific settings.

attempts with xrandr and Gnome still didn't work in Live. I also did not find the classic setting.

I am out of time to try here since Xfce is not Wayland. Another thing is Xfce has a slighty off sync 60hz but it seems to be the odd sync of 58.70.

The grayed out blob is Plasma it has the worse sync, so bad that you get white blobs and the screen is flickering.Here in M8, nothing I can do with Plasma.

The oher thing learned is to get X in Live here is to hold ctrl+alt+bksp to reset X to get into a desktop. Totally wrong time and region but that's how to get here. Nothing can be done with frame buffer so far...

It seems beyond my knowledge... any suggestions how to correct the way it sees the screen?

I will do an install using net installer. I suspect more control over parametrs will be available then as well as attempts with xrander etc. Suggestions welcome, have not had to mess with xorg in years.
Attachments
20200830_212353_Burst01s.jpg
Xfce M8
20200830_212353_Burst01s.jpg (428.47 KiB) Viewed 3556 times
20200830_204200s.jpg
Plasma M8 really off with the sync
20200830_204200s.jpg (477.2 KiB) Viewed 3556 times
20200830_193332_HDRs.jpg
Gnome M8
20200830_193332_HDRs.jpg (1.01 MiB) Viewed 3556 times
Sabungayam
 
Posts: 173
Joined: Aug 18th, '20, 06:52

Re: Mageia on GPD Win Max, can it?

Postby doktor5000 » Aug 30th, '20, 22:36

doktor5000 wrote:Sidenote, you're also jumping too much between topics, you should probably concentrate on one issue at a time.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Mageia on GPD Win Max, can it?

Postby Sabungayam » Aug 31st, '20, 06:22

ah haha... I apologize again. I am not aware of changing the topic. Sorry.
Sabungayam
 
Posts: 173
Joined: Aug 18th, '20, 06:52

Re: Mageia on GPD Win Max, can it?

Postby Sabungayam » Aug 31st, '20, 06:46

1. In Mageia 8 Grub 2 I can use the command "videoinfo"

Now how can I use that info?

2. Same behavior as Mageia 7.1 parameters seem to be ignored. Concerning vga=

3. I connected the Max via HDMI to my projector.
No problem. Screen was still garbage but projector output very good & normal.

4. I conclude maybe erroneously, that everything works & the problem with the screen is it's odd size.
1280x800

5. It appears that in Live modes, there is no way to tell it to use specific frame buffer settings. The detection isn't using the size available that fits.

6. It appears that X sessions when active are unable to detect the refresh rate & proper size of this screen or do not have the size for this screen as an option.

7. All xrandr options seem unavailable in live mode.

8. Screen size is not only odd, so is refresh rate which only Wayland seemed to get successfully. It is 59.70

Xfce at 60 was ok.

Plasma seems unable to have a good refresh rate at all even though 60 is an option.

These are my observations they may be incorrect. But in short, how to deal with this screen.

Please advise. If not live mode, then in an install which is what I am aiming for.

Thank you for your help.
Attachments
Screenshot_2020-08-31-13-25-14.png
videoinfo in grub2 prompt M8/Cauldron
Screenshot_2020-08-31-13-25-14.png (4.39 MiB) Viewed 3536 times
Sabungayam
 
Posts: 173
Joined: Aug 18th, '20, 06:52

Re: Mageia on GPD Win Max, can it?

Postby Sabungayam » Sep 1st, '20, 16:20

:?: :?: This is an install. :?: :?:

These are the errors same as from Live mode.

Code: Select all
xrandr --addmode eDP1 "1280x800_60.00"
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  18 (RRAddOutputMode)
  Serial number of failed request:  37
  Current serial number in output stream:  38

I do not understand what this means. I do not understand why I cannot add a video
mode this screen supports.

Code: Select all
xrandr
Screen 0: minimum 8 x 8, current 600 x 800, maximum 32767 x 32767
eDP1 connected primary 600x800+0+0 right (normal left inverted right x axis y axis) 0mm x 0mm
   800x600       94.87*+ 186.01    94.87*   85.14    72.19    75.00    60.32    56.25 
   1024x768      98.16    74.81    60.00    60.00 
   1024x768i     86.96 
   1024x576      59.90    59.82 
   832x624       74.55    74.18 
   960x540       59.63    59.82 
   768x576       99.99    79.37 
   864x486       59.92    59.57 
   848x480       60.00 
   640x480      116.65    85.01    72.81    75.00    59.94 
   720x405       59.51    58.99 
   720x400       85.04 
   640x400       85.08 
   640x360       59.84    59.32 
   640x350       85.08 
   400x300       94.87 
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
  1280x800_59.70 (0x212) 83.050MHz -HSync +VSync
        h: width  1280 start 1344 end 1480 total 1680 skew    0 clock  49.43KHz
        v: height  800 start  801 end  804 total  828           clock  59.70Hz
  1280x800_60.00 (0x218) 83.460MHz -HSync +VSync
        h: width  1280 start 1344 end 1480 total 1680 skew    0 clock  49.68KHz
        v: height  800 start  801 end  804 total  828           clock  60.00Hz

:?: I did newmode and it created this virtual? Why did it not put it under eDP1? I do not understand and Goggling does not provide anything that I can make sense f. Anyone hae any clue what the problem is here? :?:

This is original output before I tried the xrandr commands.

Code: Select all
xrandr -q
Screen 0: minimum 8 x 8, current 600 x 800, maximum 32767 x 32767
eDP1 connected primary 600x800+0+0 right (normal left inverted right x axis y axis) 0mm x 0mm
   800x600       94.87*+ 186.01    94.87*   85.14    72.19    75.00    60.32    56.25 
   1024x768      98.16    74.81    60.00    60.00 
   1024x768i     86.96 
   1024x576      59.90    59.82 
   832x624       74.55    74.18 
   960x540       59.63    59.82 
   768x576       99.99    79.37 
   864x486       59.92    59.57 
   848x480       60.00 
   640x480      116.65    85.01    72.81    75.00    59.94 
   720x405       59.51    58.99 
   720x400       85.04 
   640x400       85.08 
   640x360       59.84    59.32 
   640x350       85.08 
   400x300       94.87 
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
[introvertx95@introvertx95 ~]$ gtf 1280 800 59.70

  # 1280x800 @ 59.70 Hz (GTF) hsync: 49.43 kHz; pclk: 83.05 MHz
  Modeline "1280x800_59.70"  83.05  1280 1344 1480 1680  800 801 804 828  -HSync +Vsync


any clue why it stuck them under virtual? Why they're not available under the actual screen that's connected?
Last edited by isadora on Sep 1st, '20, 18:19, edited 1 time in total.
Reason: Please place command-output between [CODE]-tags, to improve readability, thanks ahead!!! ;)
Sabungayam
 
Posts: 173
Joined: Aug 18th, '20, 06:52

Re: Mageia on GPD Win Max, can it?

Postby isadora » Sep 1st, '20, 18:21

Sabungayam, it would be greatly appreciated you place command-output between [code]-tags.
We have done this now for several of your messages, please do this in following messages yourself.
..........bird from paradise..........

Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.
—Antoine de Saint-Exupéry
User avatar
isadora
 
Posts: 2742
Joined: Mar 25th, '11, 16:03
Location: Netherlands

Re: Mageia on GPD Win Max, can it?

Postby doktor5000 » Sep 1st, '20, 23:12

And also please don't crosspost this thread into new threads.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Mageia on GPD Win Max, can it?

Postby Sabungayam » Sep 2nd, '20, 00:19

@isadora: I apologize, for the extra trouble. I thought it was automatic. I really am not very familiar with forums. Can you please tell me how to do that for future reference? Thank you.

@doktor5000 I thought I would concentrate only on asking about things that deal with the screen and xrandr and things that effect it, that's why I posted it separately only about the screen and resolution.

You have reminded me several times here that I jump around too much. I am sorry and do not comprehend that I am doing so. I admit that likely I don't know how to post appropriately. I apologize again.
I am trying not only on my own but also any suggestions given by experienced members such as yourself.

I have tried the commands you suggested and they didn't work in Live. I thought maybe it was the way Live was set up. As I read it does not create a xorg.conf file. That happens on install.

I did install and put the commands but can't understand the output or why again it is no working.

I have installed Plasma and Xfce but am using Xfce. It has not been able to actually open Plasma.

Info as above. If there is other info I can provide to help you all help me. Please let me know. As found, in Mageia 7 "videoinfo" in Grub command does not work nor "vbeinfo". They do work in Mageia 8/Cauldron.

Thank you everyone for you help.
Sabungayam
 
Posts: 173
Joined: Aug 18th, '20, 06:52

Re: Mageia on GPD Win Max, can it?

Postby isadora » Sep 2nd, '20, 11:41

For a great overview of existing BB-codes of which code-tags are part of, have a look at:
https://en.wikipedia.org/wiki/BBCode
..........bird from paradise..........

Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.
—Antoine de Saint-Exupéry
User avatar
isadora
 
Posts: 2742
Joined: Mar 25th, '11, 16:03
Location: Netherlands

Re: Mageia on GPD Win Max, can it?

Postby doktor5000 » Sep 2nd, '20, 20:44

For one, you're jumping between topics. You try to change framebuffer settings, then you try to change xorg settings.
Then you try with gnome, then plasma, then xfce, all back and forth. Everything mixed between mga7 and mga8. How is anyone supposed to reproduce that, even more so if you seem to be the only one with that hardware?

For the framebuffer settings in grub with vga= or video= where you can query with either vbeinfo or videoinfo, those are mostly only for framebuffer, i.e. anything up until xorg is started.
Afterwards only the default settings in xorg.conf apply, or dynamic changes, e.g. via xrandr.

For xrandr, about the VIRTUAL1 output (which was also present prior to you adding the mode) see e.g. https://unix.stackexchange.com/question ... -come-from
This could come from the fact that you had another output connected already.

I'd say you might need to reverse the resolution, so 800x1280 - as eDP1 also shows your normal resolution as 600x800, and grub also shows the first mode as 800 x 1280.
You may need to search about some older tablets, as those also seem to have an 800x1280 resolution.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Mageia on GPD Win Max, can it?

Postby Sabungayam » Sep 3rd, '20, 00:34

As you suggest, I can choose for example 8/Cauldron and work only with it. I can select then 1 desktop and we can process through with it. With suggestions.

I have 8 installed with Xfce and Plasma. I had to try all those different desktops as far as I am concerned because some, Plasma are in such an unreadable state that I can't do anything.

After trying Gnome I did find that Xfce was able to manage to get me the 800x600.

The reason it says 800x600 is because that is what I have to select to make it fit and be readable and be able to try anything. The system always selects 1024x786 actually. To maintain focus I will not discuss other distros, but note that they all do select this.

I probably did confuse all with my comment about the projector. I only did that once because Plasma my preferred desktop is the "most" unreadable. It is just a mess. I used the monitor output which was clean so I could see and try to adjust the settings of Plasma. As we will now focus on Xfce to make things clear, I will only just state here that Plasma crashed when I tried to adjust the refresh rate.

Since some basic results are reproducible across all desktops and 7 or 8. I will only mention those that seem to be the issues we can try to solve.

1. Refresh rate. I still am not sure what it is but it seem like an odd number. Between 59.70 to 60. Since we will focus on Xfce it tends to use 60 and come out ok. Fuzzy around the edges but I do not honestly know if that is due to wrong screen size or wrong refresh. I think it's shown in some of the images.

2. Yes, FB and X are different but, it seems that the login screen is FB? I will try to now move the .xml file from my Xfce configuration to the sdm file. I need to sort out where that is. Mistake, it isn't SDDM. I forget which it is at the moment.

3. What I have changed in the install. I edited grub.conf file. When I looked it was now configured with

Code: Select all
 set gfxpayload=keep


I added a line.

Code: Select all
 set gfxmode=1280x800


no effect on restart. I also then added

Code: Select all
 fbconf=rotate:1


No change.

I will try to have a look as you suggest about dealing with tablet screens but it seems any changes I make do not take effect.

Since at this time despite the difficulty in reading the login screen and trying to make selections I can get into X. Let's try to solve and focus on X then we can go back to framebuffer.

The reason again I thought fb was important is the reason I tried several DEs because it can be so bad that at login I can't see what to select. Like with Gnome live. I tried to find the "classic" but I could see nothing on the login screen.

So with X. I saw the 1280x800 setting in MCC and I set it. And... it did nothing on restart though it says it's set.
I have as posted earlier tried the xrandr commands.

Code: Select all
xrandr --addmode eDP1 "1280x800_60.00"
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  18 (RRAddOutputMode)
  Serial number of failed request:  37
  Current serial number in output stream:  38


This error is across the board reproducible. In all the distros I have tried. It does seem to be maybe because it is detected as 800x1280 due to the screens size? But I do not understand enough about xrandr or xorg to know fully.

There is another reason I tried all the DEs as well.
https://bugs.mageia.org/show_bug.cgi?id=26829#c6

This link here in the Mageia bugs is why because I was wondering it it was this bug or variation because it talks about G1 intel and this shows as G7.

I tried to edit the xorg.conf and just add a new mode there but it does not seem available as a selection.

I have referred to several different sources on setting up a GPD WIN with the rotated screen. They all hinge around the screen being detected properly. So you just rotate it.

https://www.reddit.com/r/gpdwin/comment ... r_running/

https://davejansen.com/installing-ubunt ... -pocket-2/

Non of this seem effective because the changes seem to be ignored and of course because xrandr is giving that error.

That error will show when I type:
Code: Select all
 xrandr -o right


So maybe it revolves around what that error means. Goggling it, some think it means that the screen can't accept that resolution. Which means, detection? In live mode when I type

Code: Select all
 videoinfo


in grub command it actually says that it has selected 800x1280. Says it's preferred. I have no idea why then in shows up as blurred in fb but we will focus only on X now.

So is the fault with xrandr a detection matter? Because in the video I linked to earlier he said he just upgraded to kernel 5.7 and he had all working except the bad refresh rate.
Current Kernel installed is 5.8.x (I think 5.8.5 but I am not on the unit now).

So focusing on X and xrandr error. any suggestions on what to do to bypass the error or what it means or how to edit xorg to give the correct results?

I usually do NOT buy NEW hardware to avoid exactly these issues but this is the only thing this size with that kind of decent power and portable. Unfortunately the video that linux works fine is quite misleading. He didn't give any details what he did at all.

Thank you for you help and I apologize if it seems I was being difficult or obstinate. Thank you for making it clear what you mean by jumping topics because to me they're all the same. It seems that everything is based on detection to me and that's why parameters are ignored and of course unable to read or see clearly.

So let's focus on x and framebuffer. Is there any output you can use to help determine more what is going on?

Thank you again for you patience and help.
Sabungayam
 
Posts: 173
Joined: Aug 18th, '20, 06:52

Re: Mageia on GPD Win Max, can it?

Postby Sabungayam » Sep 3rd, '20, 08:44

I have found something...

https://www.reddit.com/r/gpdwin/comment ... max_linux/

Linked from this post, this person found or had the same experiences as I. Commands didn't really work. Extreme screen distortion.

Solution seems to be here...

https://www.reddit.com/r/gpdwin/comment ... _in_linux/

I cannot understand all that... I humbly request someone to help me understand how to achieve this process in Mageia.


The EDID information identifying the display isn't in ACPI


From the 2nd link, aside from his work around is there any other way to get Mageia to find it?
Sabungayam
 
Posts: 173
Joined: Aug 18th, '20, 06:52

Re: Mageia on GPD Win Max, can it?

Postby doktor5000 » Sep 3rd, '20, 18:59

Sabungayam wrote:So let's focus on x and framebuffer.

You're jumping between x and framebuffer all the time with no focus at all. As mentioned, either focus on framebuffer OR on X server.
I'd not care about the framebuffer resolution, because you only see that during bootup. I'd primarly focus on X.

The last link https://www.reddit.com/r/gpdwin/comment ... ux/g3nkw5r contains a modeline which should be working.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Mageia on GPD Win Max, can it?

Postby Sabungayam » Sep 4th, '20, 09:30

Sorry? I am certainly confused.

It is the solution to the screen problem? The 1st link the person tried everything here you suggested and I tried.

Though I said we can concentrate on X I have found the screen fix and it is above my understanding how to implement it. I humbly request help in doing so.

In addition it's the solution. It will fix all the issues and that will happen to include frame buffer as well I guess.

GPD Win Max display fix in Linux
GPD Win MAX
The EDID information identifying the display isn't in ACPI like on the Win 2. I extracted it from Windows (still not sure what the source is, it could be only in the registry) and saved the copy in /lib/firmware/edid/gpdwinmax.bin, then passed the kernel parameters to load it: video=eDP-1:800x1280 drm.edid_firmware=eDP-1:edid/gpdwinmax.bin fbcon=rotate:1. This sets the console rotation and video mode, but not the GUI rotation; in gnome, this had to be set to "Portrait Left". The kernel parameters were in my case stored in /etc/default/grub.

If you want a copy of my EDID, paste the following into base64 --decode > /lib/firmware/edid/gpdwinmax.bin:

AP///////wAJ5QMAAwAAAAEdAQOACxF4LwAAoFdJmyYQSE8AAAABAQEBAQEBAQEBAQEBAQEBwhog
UDAAEFAQEDIAbKwAAAAYAAAA/ABUVjA4MFdVTS1OTDAKAAAA/QA8PBAQBwAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAMM=

If your system starts DRM early, as mine does, you'll want to have the EDID in the initramfs to get the console mode right. I did this using a hook /etc/initramfs-tools/hooks/edid, so update-initramfs -u would add the EDID file. Contents of the hook script:

#!/bin/sh

case $1 in
prereqs)
exit 0
;;
esac

. /usr/share/initramfs-tools/hook-functions

copy_file EDID /lib/firmware/edid/gpdwinmax.bin


This is what is in the link:

https://www.reddit.com/r/gpdwin/comment ... _in_linux/

I did say I did not fully understand all the information, if there is anything in there about frame buffer, then that is not something I am not clear about.

Just that if you do what this said it will fix all the problems. That is why I humbly requested info to understand.

This method is probably the best way to handle this, but if you need a modeline for xorg/xrandr:

Code: Select all
"800x1280_60.06" 68.500 800 816 832 880 1280 1283 1285 1296 -HSync -VSync




Yes I saw this at the end a comment added by someone else. once again I said I did not fully comprehend the info. The way both accounts are written it indicates to me someone without
advanced knowledge that everything before the modeline comment is necessary. I shall try to add that line tonight when I am home.

I will report here what the result is.

If you have advise on properly adding that modeline it would be welcome. I only tried what I did before from reading other things online. Not sure I tried it properly.

Also again thank you for your help, it is invaluable. If all the other info is about FB then and just this line is all that's needed I had no clue... thank you & I shalll try it.

Can I try with:
Code: Select all
xrandr --newmode
Sabungayam
 
Posts: 173
Joined: Aug 18th, '20, 06:52

Re: Mageia on GPD Win Max, can it?

Postby Sabungayam » Sep 4th, '20, 11:23

I tried adding the modeline:

Code: Select all
xrandr --newmode "800x1280_60.06" 68.500 800 816 832 880 1280 1283 1285 1296 -HSync -VSync
[introvertx95@introvertx95 Desktop]$ xrandr -q
Screen 0: minimum 8 x 8, current 600 x 800, maximum 32767 x 32767
eDP1 connected primary 600x800+0+0 right (normal left inverted right x axis y axis) 0mm x 0mm
   800x600       94.87*+ 186.01    94.87*   85.14    72.19    75.00    60.32    56.25 
   1024x768      98.16    74.81    60.00    60.00 
   1024x768i     86.96 
   1024x576      59.90    59.82 
   832x624       74.55    74.18 
   960x540       59.63    59.82 
   768x576       99.99    79.37 
   864x486       59.92    59.57 
   848x480       60.00 
   640x480      116.65    85.01    72.81    75.00    59.94 
   720x405       59.51    58.99 
   720x400       85.04 
   640x400       85.08 
   640x360       59.84    59.32 
   640x350       85.08 
   400x300       94.87 
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
  800x1280_60.06 (0x1fc) 68.500MHz -HSync -VSync
        h: width   800 start  816 end  832 total  880 skew    0 clock  77.84KHz
        v: height 1280 start 1283 end 1285 total 1296           clock  60.06Hz
[introvertx95@introvertx95 Desktop]$ xrandr --addmode eDP1 "800x1280_60.06"
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  18 (RRAddOutputMode)
  Serial number of failed request:  37
  Current serial number in output stream:  38
[introvertx95@introvertx95 Desktop]$ gtf 800 1280 60.06

  # 800x1280 @ 60.06 Hz (GTF) hsync: 79.58 kHz; pclk: 86.58 MHz
  Modeline "800x1280_60.06"  86.58  800 856 944 1088  1280 1281 1284 1325  -HSync +Vsync

[introvertx95@introvertx95 Desktop]$ xrandr --newmode "800x1280_60.06"  86.58  800 856 944 1088  1280 1281 1284 1325  -HSync +Vsync
X Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  16 (RRCreateMode)
  Serial number of failed request:  37
  Current serial number in output stream:  37
Sabungayam
 
Posts: 173
Joined: Aug 18th, '20, 06:52

Re: Mageia on GPD Win Max, can it?

Postby Sabungayam » Sep 4th, '20, 11:51

This is my xorg.conf in case I didn't put the modeline in the correct place. In that case
humbly request advice. Thank you.

Code: Select all
Section "ServerFlags"
    #DontZoom # disable <Ctrl><Alt><KP_+>/<KP_-> (resolution switching)
    AllowMouseOpenFail # allows the server to start up even if the mouse does not work
    Option "DontZap" "False" # disable <Ctrl><Alt><BS> (server abort)
EndSection

Section "Module"
    Load "v4l" # Video for Linux
EndSection

Section "Monitor"
    Identifier "monitor1"
    VendorName "Plug'n Play"
    Option "PreferredMode" "800x1280"
   
    ModeLine "800x1280_60.06" 68.500 800 816 832 880 1280 1283 1285 1296 -hsync -vsync
   
    # Apple iMac modes
    ModeLine "1024x768"   78.525 1024 1049 1145 1312   768  769  772  800 +hsync +vsync
    ModeLine "800x600"    62.357  800  821  901 1040   600  601  604  632 +hsync +vsync
    ModeLine "640x480"    49.886  640  661  725  832   480  481  484  514 +hsync +vsync
   
    # Apple monitors tend to do 832x624
    ModeLine "832x624"    57      832  876  940 1152   624  625  628  667 -hsync -vsync
   
    # Apple PowerBook G3
    ModeLine "800x600"    100     800  816  824  840   600  616  624  640 -hsync -vsync
   
    # Apple TI Powerbook
    ModeLine "1152x768"   78.741 1152 1173 1269 1440   768  769  772  800 +vsync +vsync
   
    # Pismo Firewire G3
    ModeLine "1024x768"   65     1024 1032 1176 1344   768  771  777  806 -hsync -vsync
   
    # iBook2
    ModeLine "1024x768"   65     1024 1048 1184 1344   768  771  777  806 -hsync -vsync
   
    # 17" Apple Studio Display
    ModeLine "1024x768"   112.62 1024 1076 1248 1420 768 768 780 808 +hsync +vsync
   
    # HiRes Apple Studio Display
    ModeLine "1280x1024"  135    1280 1288 1392 1664  1024 1027 1030 1064
   
    # Another variation
    ModeLine "1280x1024"  134.989 1280 1317 1429 1688  1024 1025 1028 1066 +hsync +vsync
   
    # TV fullscreen mode or DVD fullscreen output.
    # 768x576 @ 79 Hz, 50 kHz hsync
    ModeLine "768x576"     50.00  768  832  846 1000   576  590  595  630
   
    # 768x576 @ 100 Hz, 61.6 kHz hsync
    ModeLine "768x576"     63.07  768  800  960 1024   576  578  590  616
   
    # modeline generated by gtf(1) [handled by XFdrake]
    ModeLine "1280x800_120"  181.21  1280 1376 1520 1760  800 801 804 858  -HSync +Vsync
   
    # modeline generated by gtf(1) [handled by XFdrake]
    ModeLine "1280x800_100"  147.89  1280 1376 1512 1744  800 801 804 848  -HSync +Vsync
   
    # modeline generated by gtf(1) [handled by XFdrake]
    ModeLine "1280x800_85"  123.38  1280 1368 1504 1728  800 801 804 840  -HSync +Vsync
   
    # modeline generated by gtf(1) [handled by XFdrake]
    ModeLine "1280x800_75"  107.21  1280 1360 1496 1712  800 801 804 835  -HSync +Vsync
   
    # modeline generated by gtf(1) [handled by XFdrake]
    ModeLine "1280x800_60"  83.46  1280 1344 1480 1680  800 801 804 828  -HSync +Vsync
   
    # modeline generated by gtf(1) [handled by XFdrake]
    ModeLine "1280x800_50"  68.56  1280 1336 1472 1664  800 801 804 824  -HSync +Vsync
EndSection

Section "Device"
    Identifier "device1"
    VendorName "Intel Corporation"
    BoardName "Intel 810 and later"
    Driver "intel"
    Option "DPMS"
EndSection

Section "Screen"
    Identifier "screen1"
    Device "device1"
    Monitor "monitor1"
    DefaultColorDepth 24
   
    Subsection "Display"
        Depth 8
        Modes "1280x800"
    EndSubsection


EndSection

Section "ServerLayout"
    Identifier "layout1"
    Screen "screen1"
EndSection

Note: I just changed it to 800x1280 under preferredmode. I think that is from my changing it in MCC to 1280x800. That's what it said before I changed it.

This is where I inserted the modeline thinking it should be there.
Sabungayam
 
Posts: 173
Joined: Aug 18th, '20, 06:52

Re: Mageia on GPD Win Max, can it?

Postby doktor5000 » Sep 4th, '20, 18:33

regarding the custom EDID data:

As root run
Code: Select all
mkdir -p /lib/firmware/edid/
base64 --decode > /lib/firmware/edid/gpdwinmax.bin

then paste the EDID data below, afterwards press Ctrl+D to write it to the file.

Code: Select all
AP///////wAJ5QMAAwAAAAEdAQOACxF4LwAAoFdJmyYQSE8AAAABAQEBAQEBAQEBAQEBAQEBwhog
UDAAEFAQEDIAbKwAAAAYAAAA/ABUVjA4MFdVTS1OTDAKAAAA/QA8PBAQBwAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAMM=


If you try to parse that EDID data, this is what it should look like:
Code: Select all
[doktor5000@Mageia7]─[18:24:15]─[~] /usr/bin/monitor-parse-edid gpdwinmax.bin
Name: TV080WUM-NL0
EISA ID: BOE0003
EDID version: 1.3
EDID extension blocks: 0
Screen size: 10.8 cm x 17.2 cm (8.00 inches, aspect ratio 0.63)
Gamma: 2.2
Digital signal
Max video bandwidth: 70 MHz

        HorizSync 16-16
        VertRefresh 60-60

        # Monitor preferred modeline (60.1 Hz vsync, 77.8 kHz hsync, ratio 0.62, 188 dpi)
        ModeLine "800x1280" 68.5 800 816 832 880 1280 1283 1285 1296 -hsync -vsync


Then create a dracut droplet so this will be added to your initrd when it is recreated next time:

Code: Select all
echo 'install_items+=" /lib/firmware/edid/gpdwinmax.bin "' >  /etc/dracut.conf.d/99-edid.conf


Then recreate the initrd for your currently running kernel:
Code: Select all
dracut -f


Then double-check if the EDID definition is now included in your initrd:
Code: Select all
lsinitrd /boot/initrd-$(uname -r).img|grep -iE "gpdwinmax|edid"


Then adjust your kernel boot options to load that EDID data. In /etc/defaults/grub append to GRUB_CMDLINE_LINUX
Code: Select all
drm_kms_helper.edid_firmware=:edid/gpdwinmax.bin

Afterwards update your grub configuration
Code: Select all
update-grub2


Then reboot.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Mageia on GPD Win Max, can it?

Postby Sabungayam » Sep 5th, '20, 03:21

:D Thank you very much, I will do this ASAP...

I apologize again for my bad posting and I shall try very hard in the future to make it more direct for others to help me.

Report back after I do this.
Sabungayam
 
Posts: 173
Joined: Aug 18th, '20, 06:52

PreviousNext

Return to Basic support

Who is online

Users browsing this forum: No registered users and 1 guest

cron