Re: [gentoo-user] radeon screen resolution
On Wed, 30 Dec 2015 04:54:48 +0100 wrote: > john wrote: > > > On Tue, 29 Dec 2015 11:05:12 +0200 > > Alan McKinnon wrote: > > > > > On 29/12/2015 11:01, Mick wrote: > > > > On Tuesday 29 Dec 2015 02:00:33 waben...@gmail.com wrote: > > > > > > > >> There is a kernel option DRM_LOAD_EDID_FIRMWARE. It allows you > > > >> to specify an EDID data set instead of probing for it. If your > > > >> problem is caused by broken EDID data, this option maybe will > > > >> help you to run the monitor at its full resolution. > > > >> > > > >> -- > > > >> Regards > > > >> wabe > > > > > > > > How would you know what to specify for EDID data, unless the > > > > monitor told you what it is? > > > > > > > > > > or if the monitor manufacturer told you what it should be > > > > > > /alanm > > > > > > > I have had a play with that but no success yet. I have followed the > > howto but no success yet but I think now I will have to find .bin > > file or settings from manufacturer. > > > > Darn these gaming monitors! > > > > Thanks > > > > John > > When you install x11-misc/read-edid you will get the programs > get-edid and parse-edid. If you type > > get-edid | parse-edid > > you will get something like this: > > === > > 256-byte EDID successfully retrieved from i2c bus 8 > Looks like i2c was successful. Have a good day. > Checksum Correct > > Section "Monitor" > Identifier "U32D970" > ModelName "U32D970" > VendorName "SAM" > # Monitor Manufactured week 20 of 2014 > # EDID version 1.4 > # Digital Display > DisplaySize 700 390 > Gamma 2.20 > Option "DPMS" "true" > Horizsync 30-134 > VertRefresh 56-75 > # Maximum pixel clock is 540MHz > #Not giving standard mode: 1152x864, 75Hz > #Not giving standard mode: 1280x800, 60Hz > #Not giving standard mode: 1280x720, 60Hz > #Not giving standard mode: 1280x1024, 60Hz > #Not giving standard mode: 1440x900, 60Hz > #Not giving standard mode: 1600x900, 60Hz > #Not giving standard mode: 1680x1050, 60Hz > > #Extension block found. Parsing... > Modeline"Mode 2" 148.500 1920 2008 2052 2200 1080 > 1084 1089 1125 +hsync +vsync Modeline "Mode 0" +hsync -vsync > Modeline"Mode 1" +hsync -vsync > Modeline"Mode 3" +hsync +vsync > Option "PreferredMode" "Mode 2" > EndSection > > === > > In former times it was possible to insert these informations into > /etc/X11/xorg.conf. But I'm not sure if this still works nowadays, > in particular the Modeline definition. > > But maybe you can see if something is wrong with the EDID data of > your monitor. > > I could also provide you the EDID data from my monitor. Maybe you > can use it with the DRM_LOAD_EDID_FIRMWARE kernel option. But this > is just an idea. I have no clue how to do this in detail. :-) > > P.S.: > When you have only tried x11-drivers/xf86-video-ati then you should > also try x11-drivers/xf86-video-amdgpu. Maybe this driver works > better with your monitor. > > -- > Regards > wabe > > Using get-edid | parse-edid gives the following: This is read-edid version 3.0.1. Prepare for some fun. Attempting to use i2c interface No EDID on bus 1 1 potential busses found: 0 Bus 0 doesn't really have an EDID... Couldn't find an accessible EDID on this computer. Attempting to use the classical VBE interface Partial Read... Try again interesting. Not sure here about 12c interface but have i2c module loaded (if that's the correct one???). I have tried DRM_LOAD_EDID_FIRMWARE (drs_kms_helper.edid_firmare=edid/mon.bin) kernel option and created the .bin file from a utility from AMD and still screen resolution is small and also tried amdgpu with no joy there. Think I'll just use another monitor for time being. I only want to play with weston to see if enlightenment works ok at version 20. John
Re: [gentoo-user] radeon screen resolution
john wrote: > On Tue, 29 Dec 2015 11:05:12 +0200 > Alan McKinnon wrote: > > > On 29/12/2015 11:01, Mick wrote: > > > On Tuesday 29 Dec 2015 02:00:33 waben...@gmail.com wrote: > > > > > >> There is a kernel option DRM_LOAD_EDID_FIRMWARE. It allows you to > > >> specify an EDID data set instead of probing for it. If your > > >> problem is caused by broken EDID data, this option maybe will > > >> help you to run the monitor at its full resolution. > > >> > > >> -- > > >> Regards > > >> wabe > > > > > > How would you know what to specify for EDID data, unless the > > > monitor told you what it is? > > > > > > > or if the monitor manufacturer told you what it should be > > > > /alanm > > > > I have had a play with that but no success yet. I have followed the > howto but no success yet but I think now I will have to find .bin file > or settings from manufacturer. > > Darn these gaming monitors! > > Thanks > > John When you install x11-misc/read-edid you will get the programs get-edid and parse-edid. If you type get-edid | parse-edid you will get something like this: === 256-byte EDID successfully retrieved from i2c bus 8 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "U32D970" ModelName "U32D970" VendorName "SAM" # Monitor Manufactured week 20 of 2014 # EDID version 1.4 # Digital Display DisplaySize 700 390 Gamma 2.20 Option "DPMS" "true" Horizsync 30-134 VertRefresh 56-75 # Maximum pixel clock is 540MHz #Not giving standard mode: 1152x864, 75Hz #Not giving standard mode: 1280x800, 60Hz #Not giving standard mode: 1280x720, 60Hz #Not giving standard mode: 1280x1024, 60Hz #Not giving standard mode: 1440x900, 60Hz #Not giving standard mode: 1600x900, 60Hz #Not giving standard mode: 1680x1050, 60Hz #Extension block found. Parsing... Modeline"Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 0" +hsync -vsync Modeline"Mode 1" +hsync -vsync Modeline"Mode 3" +hsync +vsync Option "PreferredMode" "Mode 2" EndSection === In former times it was possible to insert these informations into /etc/X11/xorg.conf. But I'm not sure if this still works nowadays, in particular the Modeline definition. But maybe you can see if something is wrong with the EDID data of your monitor. I could also provide you the EDID data from my monitor. Maybe you can use it with the DRM_LOAD_EDID_FIRMWARE kernel option. But this is just an idea. I have no clue how to do this in detail. :-) P.S.: When you have only tried x11-drivers/xf86-video-ati then you should also try x11-drivers/xf86-video-amdgpu. Maybe this driver works better with your monitor. -- Regards wabe
Re: [gentoo-user] radeon screen resolution
john wrote: > On Tue, 29 Dec 2015 11:05:12 +0200 > Alan McKinnon wrote: > > > On 29/12/2015 11:01, Mick wrote: > > > On Tuesday 29 Dec 2015 02:00:33 waben...@gmail.com wrote: > > > > > >> There is a kernel option DRM_LOAD_EDID_FIRMWARE. It allows you to > > >> specify an EDID data set instead of probing for it. If your > > >> problem is caused by broken EDID data, this option maybe will > > >> help you to run the monitor at its full resolution. > > >> > > >> -- > > >> Regards > > >> wabe > > > > > > How would you know what to specify for EDID data, unless the > > > monitor told you what it is? > > > > > > > or if the monitor manufacturer told you what it should be > > > > /alanm > > > > I have had a play with that but no success yet. I have followed the > howto but no success yet but I think now I will have to find .bin file > or settings from manufacturer. Maybe you can somehow extract it (hexedit?) from the windows monitor driver that was probably delivered with the monitor. After I installed the driver for the LG monitor, I was able to use it at full resolution under windows. So I think that the EDID data (or something equivalent) was included in the driver. I never used that kernel option. So I can't tell you more. -- Regards wabe
Re: [gentoo-user] radeon screen resolution
On Tue, 29 Dec 2015 11:05:12 +0200 Alan McKinnon wrote: > On 29/12/2015 11:01, Mick wrote: > > On Tuesday 29 Dec 2015 02:00:33 waben...@gmail.com wrote: > > > >> There is a kernel option DRM_LOAD_EDID_FIRMWARE. It allows you to > >> specify an EDID data set instead of probing for it. If your problem > >> is caused by broken EDID data, this option maybe will help you to > >> run the monitor at its full resolution. > >> > >> -- > >> Regards > >> wabe > > > > How would you know what to specify for EDID data, unless the > > monitor told you what it is? > > > > or if the monitor manufacturer told you what it should be > > /alanm > I have had a play with that but no success yet. I have followed the howto but no success yet but I think now I will have to find .bin file or settings from manufacturer. Darn these gaming monitors! Thanks John
Re: [gentoo-user] radeon screen resolution
On 29/12/2015 11:01, Mick wrote: On Tuesday 29 Dec 2015 02:00:33 waben...@gmail.com wrote: There is a kernel option DRM_LOAD_EDID_FIRMWARE. It allows you to specify an EDID data set instead of probing for it. If your problem is caused by broken EDID data, this option maybe will help you to run the monitor at its full resolution. -- Regards wabe How would you know what to specify for EDID data, unless the monitor told you what it is? or if the monitor manufacturer told you what it should be /alanm
Re: [gentoo-user] radeon screen resolution
On Tuesday 29 Dec 2015 02:02:52 waben...@gmail.com wrote: > Mick wrote: > > On Monday 28 Dec 2015 21:05:56 john wrote: > > > Hmm, > > > thanks, I have now tried an old monitor and its screen > > > resolution was good (ie 1920x1080) so I think it's the monitor. > > > I have a R9 280 radeon card which is pretty new but the monitor is > > > very new (display port only, acer xb240h model) so I guess it's > > > something do do with that, perhaps EDID but not really sure. The > > > whole graphics stack is pretty bemusing and I would love to make > > > sense of it all. > > > > Have a look here for setting up your card: > > > > https://wiki.gentoo.org/wiki/Amdgpu > > > > > > and here for setting up the driver > > 'x11-drivers/xf86-video-displaylink' to get your DP going: > > > > https://wiki.gentoo.org/wiki/DisplayLink > > I don't think that this is necessary. The Acer XB240H doesn't have a > DisplayLink connector. It has a DisplyPort connector and for this you > don't need a special driver. > > IIRC you also don't need a special kernel option to use DisplayPort. > > -- > Regards > wabe I beg your pardon! It was getting late and I got DisplayLink and DisplayPort mixed up. What Wabe says stands. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] radeon screen resolution
On Tuesday 29 Dec 2015 02:00:33 waben...@gmail.com wrote: > There is a kernel option DRM_LOAD_EDID_FIRMWARE. It allows you to > specify an EDID data set instead of probing for it. If your problem > is caused by broken EDID data, this option maybe will help you to run > the monitor at its full resolution. > > -- > Regards > wabe How would you know what to specify for EDID data, unless the monitor told you what it is? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] radeon screen resolution
Mick wrote: > On Monday 28 Dec 2015 21:05:56 john wrote: > > > Hmm, > > thanks, I have now tried an old monitor and its screen > > resolution was good (ie 1920x1080) so I think it's the monitor. > > I have a R9 280 radeon card which is pretty new but the monitor is > > very new (display port only, acer xb240h model) so I guess it's > > something do do with that, perhaps EDID but not really sure. The > > whole graphics stack is pretty bemusing and I would love to make > > sense of it all. > > Have a look here for setting up your card: > > https://wiki.gentoo.org/wiki/Amdgpu > > > and here for setting up the driver > 'x11-drivers/xf86-video-displaylink' to get your DP going: > > https://wiki.gentoo.org/wiki/DisplayLink I don't think that this is necessary. The Acer XB240H doesn't have a DisplayLink connector. It has a DisplyPort connector and for this you don't need a special driver. IIRC you also don't need a special kernel option to use DisplayPort. -- Regards wabe
Re: [gentoo-user] radeon screen resolution
john wrote: > On Mon, 28 Dec 2015 13:41:57 + > Mick wrote: > > > On Monday 28 Dec 2015 09:11:10 john wrote: > > > Hello, > > > > > > I have installed Gentoo on to another partition in order to use > > > radeon drivers for desktop instead of fglrx. > > > > > > When I start my resolution is very small (1280x600) and only uses > > > half the screen. My max resolution is 1920*1080 so I have a big > > > black border around my screen. I can startx which works but cannot > > > change the resolution to anything bigger. GRUB splash uses full > > > screen but when the kernel loads it switches to small resolution. > > > > > > The only thing I can think of which is causing this issue is UEFI. > > > In my other set (fglrx) up I have simple framebuffer enabled which > > > works when I set up resolution in grub default. > > > > > > Strangely enough when I start system rescue cd in UEFI mode I get > > > the same problem with small resolution but not if I do not boot in > > > UEFI mode. > > > > Hmm ... I don't get such problems here on 3 PCs running different > > amd/radeon cards and all with radeon drivers. > > > > You haven't said which card you're running. If it is a very recent > > model the radeon drivers may not have caught up with it yet? > > > > If you need to compare kernel settings let me know, although there > > are wiki pages that are quite detailed on this topic. > > > > > > > Anyone come across this or got this to work properly with > > > radeon/UEFI? > > > > > > Moral, don't use UEFI I guess but that's the future???!! > > > > > > John > > > > On PC boots in UEFI (directly boots the efi binary, no boot > > managers) and it has no such problems on 2 x 1920*1080 monitors. > > > > Hmm, > thanks, I have now tried an old monitor and its screen > resolution was good (ie 1920x1080) so I think it's the monitor. > I have a R9 280 radeon card which is pretty new but the monitor is > very new (display port only, acer xb240h model) so I guess it's > something do do with that, perhaps EDID but not really sure. The > whole graphics stack is pretty bemusing and I would love to make > sense of it all. Several months ago I was thinking about buying a LG monitor with Cinema4k (4096x2160) resolution. The monitor that I received had some firmware bugs. One bug was that the monitor shows a broken (somewhat incomplete) EDID block. So it was not possible to use the full resolution with the radeon driver but only UHD resolution (3840x2160). I read somewhere that this monitor maybe would run fine with the fglrx driver. But because I don't like proprietary software and because the monitor also had some other bugs and IMHO also a poor picture quality, I decided to sent it back. There is a kernel option DRM_LOAD_EDID_FIRMWARE. It allows you to specify an EDID data set instead of probing for it. If your problem is caused by broken EDID data, this option maybe will help you to run the monitor at its full resolution. -- Regards wabe
Re: [gentoo-user] radeon screen resolution
On Monday 28 Dec 2015 21:05:56 john wrote: > Hmm, > thanks, I have now tried an old monitor and its screen > resolution was good (ie 1920x1080) so I think it's the monitor. > I have a R9 280 radeon card which is pretty new but the monitor is very > new (display port only, acer xb240h model) so I guess it's something do > do with that, perhaps EDID but not really sure. The whole graphics > stack is pretty bemusing and I would love to make sense of it all. Have a look here for setting up your card: https://wiki.gentoo.org/wiki/Amdgpu and here for setting up the driver 'x11-drivers/xf86-video-displaylink' to get your DP going: https://wiki.gentoo.org/wiki/DisplayLink -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] radeon screen resolution
On Mon, 28 Dec 2015 13:41:57 + Mick wrote: > On Monday 28 Dec 2015 09:11:10 john wrote: > > Hello, > > > > I have installed Gentoo on to another partition in order to use > > radeon drivers for desktop instead of fglrx. > > > > When I start my resolution is very small (1280x600) and only uses > > half the screen. My max resolution is 1920*1080 so I have a big > > black border around my screen. I can startx which works but cannot > > change the resolution to anything bigger. GRUB splash uses full > > screen but when the kernel loads it switches to small resolution. > > > > The only thing I can think of which is causing this issue is UEFI. > > In my other set (fglrx) up I have simple framebuffer enabled which > > works when I set up resolution in grub default. > > > > Strangely enough when I start system rescue cd in UEFI mode I get > > the same problem with small resolution but not if I do not boot in > > UEFI mode. > > Hmm ... I don't get such problems here on 3 PCs running different > amd/radeon cards and all with radeon drivers. > > You haven't said which card you're running. If it is a very recent > model the radeon drivers may not have caught up with it yet? > > If you need to compare kernel settings let me know, although there > are wiki pages that are quite detailed on this topic. > > > > Anyone come across this or got this to work properly with > > radeon/UEFI? > > > > Moral, don't use UEFI I guess but that's the future???!! > > > > John > > On PC boots in UEFI (directly boots the efi binary, no boot managers) > and it has no such problems on 2 x 1920*1080 monitors. > Hmm, thanks, I have now tried an old monitor and its screen resolution was good (ie 1920x1080) so I think it's the monitor. I have a R9 280 radeon card which is pretty new but the monitor is very new (display port only, acer xb240h model) so I guess it's something do do with that, perhaps EDID but not really sure. The whole graphics stack is pretty bemusing and I would love to make sense of it all. It's good to know you got it running on other monitors which gave me the idea to try it on an older monitor. I will continue to tweak but Thanks John
Re: [gentoo-user] radeon screen resolution
On Monday 28 Dec 2015 09:11:10 john wrote: > Hello, > > I have installed Gentoo on to another partition in order to use radeon > drivers for desktop instead of fglrx. > > When I start my resolution is very small (1280x600) and only uses half > the screen. My max resolution is 1920*1080 so I have a big black border > around my screen. I can startx which works but cannot change the > resolution to anything bigger. GRUB splash uses full screen but when the > kernel loads it switches to small resolution. > > The only thing I can think of which is causing this issue is UEFI. In > my other set (fglrx) up I have simple framebuffer enabled which works > when I set up resolution in grub default. > > Strangely enough when I start system rescue cd in UEFI mode I get the > same problem with small resolution but not if I do not boot in UEFI > mode. Hmm ... I don't get such problems here on 3 PCs running different amd/radeon cards and all with radeon drivers. You haven't said which card you're running. If it is a very recent model the radeon drivers may not have caught up with it yet? If you need to compare kernel settings let me know, although there are wiki pages that are quite detailed on this topic. > Anyone come across this or got this to work properly with radeon/UEFI? > > Moral, don't use UEFI I guess but that's the future???!! > > John On PC boots in UEFI (directly boots the efi binary, no boot managers) and it has no such problems on 2 x 1920*1080 monitors. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] radeon screen resolution
Hello, I have installed Gentoo on to another partition in order to use radeon drivers for desktop instead of fglrx. When I start my resolution is very small (1280x600) and only uses half the screen. My max resolution is 1920*1080 so I have a big black border around my screen. I can startx which works but cannot change the resolution to anything bigger. GRUB splash uses full screen but when the kernel loads it switches to small resolution. The only thing I can think of which is causing this issue is UEFI. In my other set (fglrx) up I have simple framebuffer enabled which works when I set up resolution in grub default. Strangely enough when I start system rescue cd in UEFI mode I get the same problem with small resolution but not if I do not boot in UEFI mode. Anyone come across this or got this to work properly with radeon/UEFI? Moral, don't use UEFI I guess but that's the future???!! John
