search for: hdmi2

Hi, my primary monitor is a LCD HDMI2 and the secondary monitor is a CRT VGA1. The CRT monitor is only turned on on demand, but always connected by VGA. The BIOS is shown on both monitors, but the syslinux menu only on the CRT, as long as the CRT is connected by VGA. Even if it's turned off, the syslinux menu isn't shown on th...

On Wed, 16 Aug 2017 12:46:46 -0700, H. Peter Anvin via Syslinux wrote: >Is that true for vesamenu only, or even for text mode syslinux? Hi, I'm using menu.c32 (text mode only), this is the complete config: [root at archlinux ~]# cat /boot/syslinux/syslinux.cfg # http://syslinux.zytor.com/wiki/index.php/Doc/menu PROMPT 0 TIMEOUT 600 UI menu.c32 MENU HIDDEN MENU CLEAR MENU COLOR screen

On 08/15/17 04:53, Ralf Mardorf via Syslinux wrote: > Hi, > > my primary monitor is a LCD HDMI2 and the secondary monitor is a CRT > VGA1. The CRT monitor is only turned on on demand, but always connected > by VGA. > > The BIOS is shown on both monitors, but the syslinux menu only on the > CRT, as long as the CRT is connected by VGA. Even if it's turned off, > the sysli...

...LINUX ../vmlinuz-linux-rt-pussytoes APPEND root=LABEL=archlinux ro INITRD ../initramfs-linux-rt-pussytoes.img Do you see anything with just this? On Tue, Aug 15, 2017 at 7:53 AM, Ralf Mardorf via Syslinux <syslinux at zytor.com> wrote: > Hi, > > my primary monitor is a LCD HDMI2 and the secondary monitor is a CRT > VGA1. The CRT monitor is only turned on on demand, but always connected > by VGA. > > The BIOS is shown on both monitors, but the syslinux menu only on the > CRT, as long as the CRT is connected by VGA. Even if it's turned off, > the syslin...

...0.0] unknown chipset, 0x137000a1 May 3 16:44:45 kernel: [ 7.068401] nouveau E[ DRM] failed to create 0x80000080, -22 May 3 16:44:45 kernel: [ 7.068723] nouveau: probe of 0000:08:00.0 failed with error -22 I can make this card available - if you can tell me an older card that can do the hdmi2 480x1200 60hz 4:4:4 output that is in xserver-xorg-video-nouveau 1:1.0.13-3 -- -------------------------------------------------------------------------------- Karl Schmidt EMail Karl at xtronics.com Transtronics, Inc. WEB http://secu...

...19.024] (II) intel(0): Enabled output DP1 [ 19.024] (II) intel(0): Output HDMI1 has no monitor section [ 19.025] (II) intel(0): Enabled output HDMI1 [ 19.025] (II) intel(0): Output DP2 has no monitor section [ 19.026] (II) intel(0): Enabled output DP2 [ 19.026] (II) intel(0): Output HDMI2 has no monitor section [ 19.027] (II) intel(0): Enabled output HDMI2 [ 19.027] (--) intel(0): Using a maximum size of 256x256 for hardware cursors [ 19.027] (II) intel(0): Output VIRTUAL1 has no monitor section [ 19.027] (II) intel(0): Enabled output VIRTUAL1 [ 19.028] (--) intel(0):...

...both monitors, the HDMI monitor doesn't receive a signal, as soon as the syslinux menu comes into play + the VGA monitor is connected with or without power on. >It's a BIOS situation really. But the BIOS is shown on both monitors at the same time. >> FWIW xrandr shows HDMI1 and HDMI2, but there is only one HDMI output >> assigned to HDMI2. > >Sometimes other outputs might be labeled strangely like a DVI as HDMI1. The back panel of the mobo, a Gigabyte GA-B85M-D3H (Intel CPU/GPU), provides D-Sub, DVI-D and HDMI. The CRT monitor D-Sub only. The LCD monitor in addit...

...is is what xrandr is giving me... xrandr --query Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 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) HDMI2 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 120.00*+ 100.00 119.88 60.00 50.00 59.94 30.00 25.00 24.00 29.97 23.98 3840x2160 30.00 25.00 24.00 29.97 23.98 1920x1080i 60.00 50.00 59.9...

...vers/gpu/drm/drm_edid.c > >>>>> @@ -4830,19 +4830,32 @@ void drm_set_preferred_mode(struct drm_connector *connector, > >>>>> } > >>>>> EXPORT_SYMBOL(drm_set_preferred_mode); > >>>>> > >>>>> +static bool is_hdmi2_sink(struct drm_connector *connector) > >>>> You're usually known for adding const all around, why not const pointer > >>>> here and in all the other drm_* functions that call this? > >>> My current approach is to constify states/fbs/etc. but not so muc...

https://bugs.freedesktop.org/show_bug.cgi?id=54512 Bug #: 54512 Summary: xrandr does not detect screen Classification: Unclassified Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

...m_edid.c >>>>>>> @@ -4830,19 +4830,32 @@ void drm_set_preferred_mode(struct drm_connector *connector, >>>>>>> } >>>>>>> EXPORT_SYMBOL(drm_set_preferred_mode); >>>>>>> >>>>>>> +static bool is_hdmi2_sink(struct drm_connector *connector) >>>>>> You're usually known for adding const all around, why not const pointer >>>>>> here and in all the other drm_* functions that call this? >>>>> My current approach is to constify states/fbs/etc. but n...

...m/drm_edid.c > >>> +++ b/drivers/gpu/drm/drm_edid.c > >>> @@ -4830,19 +4830,32 @@ void drm_set_preferred_mode(struct drm_connector *connector, > >>> } > >>> EXPORT_SYMBOL(drm_set_preferred_mode); > >>> > >>> +static bool is_hdmi2_sink(struct drm_connector *connector) > >> You're usually known for adding const all around, why not const pointer > >> here and in all the other drm_* functions that call this? > > My current approach is to constify states/fbs/etc. but not so much > > crtcs/connec...

...;>>>> @@ -4830,19 +4830,32 @@ void drm_set_preferred_mode(struct drm_connector *connector, > >>>>>>> } > >>>>>>> EXPORT_SYMBOL(drm_set_preferred_mode); > >>>>>>> > >>>>>>> +static bool is_hdmi2_sink(struct drm_connector *connector) > >>>>>> You're usually known for adding const all around, why not const pointer > >>>>>> here and in all the other drm_* functions that call this? > >>>>> My current approach is to constify states...

...e Syrjälä <ville.syrjala at linux.intel.com> > > > > Make life easier for drivers by simply passing the connector > > to drm_hdmi_avi_infoframe_from_display_mode() and > > drm_hdmi_avi_infoframe_quant_range(). That way drivers don't > > need to worry about is_hdmi2_sink mess. > > Overall looks about right and nice, > > Reviewed-by: Jani Nikula <jani.nikula at intel.com> > > But please do take that with a grain of salt for everything outside of > i915 and drm core. > > Please also find a few comments inline below. > &gt...

...37000a1 > May 3 16:44:45 kernel: [ 7.068401] nouveau E[ DRM] failed to create 0x80000080, -22 > May 3 16:44:45 kernel: [ 7.068723] nouveau: probe of 0000:08:00.0 failed with error -22 > > I can make this card available - if you can tell me an older card that can do the > hdmi2 480x1200 60hz 4:4:4 output that is in > > xserver-xorg-video-nouveau 1:1.0.13-3 > > -- > -------------------------------------------------------------------------------- > Karl Schmidt EMail Karl at xtronics.com > Transtronics, Inc....

...axis) 698mm x 392mm 1920x1080 60.0* 59.9 24.0 24.0 1920x1080i 60.1 60.0 1280x720 60.0 59.9 1440x480i 60.1 60.1 60.1 720x480 60.0 59.9 640x480 60.0 59.9 DP1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) HDMI3 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) DP3 disconnected (normal left inverted right x axis y axis) # xrandr -display \:0 --output HDMI1 --mode 640x480 # echo $...

...are headed to 40G (need 18G+overhead or 20G for 12bit 3840x2160 60hz RGB or only 12G+ for 8bit(24)) > only RGB. Also there's no > HDMI 2.0 support in nouveau as yet, mostly due to lack of interest and > hardware. However you should still see a 4k at 30 mode exposed > (probably). HDMI2 does support RGB - see: http://www.hdmi.org/manufacturer/hdmi_2_0/hdmi_2_0_faq.aspx#146 The main wiki page probably ought to say what subsets of HDMI nouveau supports. Some of the chip sets from back in the 900 series support hdmi2.0 - so to say nouveau supports that chip sort of implies that i...

...;>> --- a/drivers/gpu/drm/drm_edid.c >>> +++ b/drivers/gpu/drm/drm_edid.c >>> @@ -4830,19 +4830,32 @@ void drm_set_preferred_mode(struct drm_connector *connector, >>> } >>> EXPORT_SYMBOL(drm_set_preferred_mode); >>> >>> +static bool is_hdmi2_sink(struct drm_connector *connector) >> You're usually known for adding const all around, why not const pointer >> here and in all the other drm_* functions that call this? > My current approach is to constify states/fbs/etc. but not so much > crtcs/connectors/etc. Too much c...

...gt;>>> +++ b/drivers/gpu/drm/drm_edid.c >>>>> @@ -4830,19 +4830,32 @@ void drm_set_preferred_mode(struct drm_connector *connector, >>>>> } >>>>> EXPORT_SYMBOL(drm_set_preferred_mode); >>>>> >>>>> +static bool is_hdmi2_sink(struct drm_connector *connector) >>>> You're usually known for adding const all around, why not const pointer >>>> here and in all the other drm_* functions that call this? >>> My current approach is to constify states/fbs/etc. but not so much >>>...

This is sort of working -- but I can't get it to do a 4k output. Not sure how the monitor resolution is detected - This monitor is supposed to do 3480x1200 60hz 4:4:4 But the info I get from hwinfo is different. How does nouveau get this information? If it is from an ID - with a list - the list is probably is wrong. # hwinfo --monitor 95: None 00.1: 10002 LCD Monitor [Created at