similar to: 4k tv and UEFI Ultra Fast Boot

Displaying 20 results from an estimated 10000 matches similar to: "4k tv and UEFI Ultra Fast Boot"

2019 Aug 06
2
unstable refresh rate
I have a Gigabyte GeForce 1050 connected by DVI to a monitor (1920x1200 resolution @ 59.9502 Hz) and a TV via HDMI (3840x2160 @30 Hz). The problem is the TV used to work at 59.9685 Hz but then it started showing "No signal" on the TV. I was changing settings trying to get it to work again and I happened to change it to 30Hz and it worked. The specs are here:
2019 Aug 06
2
unstable refresh rate
On 2019-08-06 12:32 p.m., Ilia Mirkin wrote: > Hi James, > > I semi-recently added support for HDMI 2.0 (in 4.20+, so you're good), > which is why you got 60Hz in the first place. In order for the high > rates to work, something called "scrambling" must be enabled. This is > done by 2-party agreement between the sink and the source. The sink > will inform the
2019 Aug 12
0
limited resolution on DVI and HDMI at the same time
I got 1920x1200 at 59.95Hz via DVI and 3840x2160 at 60.00Hz via HDMI at the same time with the proprietary nvidia driver. I get flickering on the 1920x1200 at 59.95 with the nouveau driver (it doesn't flicker if I lower it to 1920x1080 at 59.96). Any idea why? proprietary: $ xrandr Screen 0: minimum 8 x 8, current 5760 x 2160, maximum 32767 x 32767 DVI-D-0 connected primary 1920x1200+0+0
2019 Aug 06
0
unstable refresh rate
Hi James, I semi-recently added support for HDMI 2.0 (in 4.20+, so you're good), which is why you got 60Hz in the first place. In order for the high rates to work, something called "scrambling" must be enabled. This is done by 2-party agreement between the sink and the source. The sink will inform the source that it's about to use scrambling (by writing to the SCDC register on
2008 Oct 15
1
[Bug 18071] New: Interlaced DVI on NV34M doesn't work properly.
http://bugs.freedesktop.org/show_bug.cgi?id=18071 Summary: Interlaced DVI on NV34M doesn't work properly. Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org
2014 Nov 28
0
[Bug 70389] [prime] unsynchronised rendering on secondary displays
https://bugs.freedesktop.org/show_bug.cgi?id=70389 Dennis Favro <dfavro at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dfavro at gmail.com --- Comment #3 from Dennis Favro <dfavro at gmail.com> --- Getting what appears to be a
2018 Sep 23
0
Strange monitor behavior on forced DVI-D output
Am Sonntag, den 23.09.2018, 12:55 -0400 schrieb Ilia Mirkin: > On Sun, Sep 23, 2018 at 12:26 PM, Wolfgang Rißler > <wolle321 at freenet.de> wrote: [snip] > > That's not extremely surprising ... force-enabling an output I think > might kill the resolution detection, and 1024x768 is the default. Why > are you force-enabling/disabling video outputs? That should not >
2016 Sep 21
0
Quadro 4000 with iiyama B2783QSU should be 2560x1440 but detected as 1920x1080.
I think you want the reduced blanking modeline: $ cvt -r 2560 1440 # 2560x1440 59.95 Hz (CVT 3.69M9-R) hsync: 88.79 kHz; pclk: 241.50 MHz Modeline "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync This matches your monitor's detailed timings: [ 55.220] (II) NOUVEAU(0): Supported detailed timing: [ 55.220] (II) NOUVEAU(0): clock: 241.5 MHz Image
2019 Aug 06
2
unstable refresh rate
I think I may have updated the tv firmware between when it worked and when it didn't. I wonder it it has to do with bit depth. I use lubuntu and it doesn't let me pick the bit depth so I don't know what it using.
2016 Sep 21
2
Quadro 4000 with iiyama B2783QSU should be 2560x1440 but detected as 1920x1080.
Hi, Distribution: openSUSE 42.2 Beta, Kernel: 4.4. The box is a Dell Precision T7500 with an nVidia Quadro 4000 card and a displayport connected iiyama B2783QSU 2560x1440 monitor identified as DP-1. Problem: The monitor is detected as 1920x1080 and not 2560x1440. See Xorg log file at http://rogerprice.org/Xorg.0.log . There is no file /etc/X11/xorg.conf and in the directory
2017 Dec 31
0
LUT update skipped on first modeset?
Hi Ben, I was looking into some of the LUT-related modesetting issues. I've noticed the following... after I load nouveau, one of my secondary GPUs shows this on first modeset (with drm.debug=4): [ 2368.081307] [drm:drm_helper_probe_single_connector_modes [drm_kms_helper]] [CONNECTOR:44:DVI-I-1] [ 2368.113148] [drm:drm_add_display_info [drm]] non_desktop set to 0 [ 2368.113183]
2011 Aug 05
11
[Bug 39866] New: Incorrectly detects Analog outputs as TV out on Apple Cards
https://bugs.freedesktop.org/show_bug.cgi?id=39866 Summary: Incorrectly detects Analog outputs as TV out on Apple Cards Product: xorg Version: git Platform: PowerPC OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at
2018 Sep 23
0
Strange monitor behavior on forced DVI-D output
Am Freitag, den 07.09.2018, 22:11 +0200 schrieb wolle321 at freenet.de: > Hello , > > I'm new here but I hope I can describe my problem exactly. > > I'm trying to get my DVI-Monitor to work with nouveau. The monitor > is > automatically reported as not connected. LVDS is detected. Forcing it > on Xorg.conf didn't work, KMS does: > >
2018 Sep 24
11
[Bug 108047] New: No recognition of DVI-D monitor
https://bugs.freedesktop.org/show_bug.cgi?id=108047 Bug ID: 108047 Summary: No recognition of DVI-D monitor Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at
2018 May 01
2
libva problem?
On 2018-05-01 06:00 PM, Ilia Mirkin wrote: > What GPU do you have? For video acceleration (i.e. va-api and vdpau), > did you install the necessary firmware? > > On Tue, May 1, 2018 at 5:53 PM, James <bjlockie at lockie.ca> wrote: >> I am playing videos from my lubuntu computer to my tv through the hdmi >> interface on my video card. >> It mostly works. >>
2018 Sep 07
2
Strange monitor behavior on forced DVI-D output
Hello , I'm new here but I hope I can describe my problem exactly. I'm trying to get my DVI-Monitor to work with nouveau. The monitor is automatically reported as not connected. LVDS is detected. Forcing it on Xorg.conf didn't work, KMS does: video=DVI-D-1:1920x1200e video=LVDS-1:d X started with 1024x768, but could switch by xrandr to 1920x1200. The viewed picture now is
2019 Jun 19
0
Instable graphics with GeForce GT 730M, especially on external monitor
Sigh ... you're on wayland. xrandr is just showing you what's passed through via Xwayland, which is not the connector names. Let's try something else... grep . /sys/class/drm/card*-*/status Should give you the status of each connector. Is it the DP-* ones that are connected, or are e.g. VGA-1 or DVI-D-1/etc connected? -ilia On Wed, Jun 19, 2019 at 2:03 AM Harald Harders
2018 Aug 24
0
Nouveau doesn't detect DVI - Monitor
Hello, I'm new here, and I hope I can get any help. At first I thought this is a support mailing list, but it looks more like one for developers. I'm using Nouveau in ubuntu bionic. My problem is, when I connect a second Monitor to my Laptop on DVI-D connector, the monitor is not detected, Nouveau reports it as "disconnected". The Hardware works, because the BIOS uses the
2016 Jan 04
1
Nouveau support for GeForce GT 730 or GTX 750 Ti or AMD Radeon R7 240 and AMD ATI RADEON R7 260X ??
2016-01-03 20:11 GMT+01:00 Ilia Mirkin <imirkin at alum.mit.edu>: > On Sun, Jan 3, 2016 at 1:52 PM, Csányi Pál <csanyipal at gmail.com> wrote: >> So there is an AMD card too: >> VGA ASUS AMD Radeon R7 240, R7240-2GD3-L, 2GB DDR3, 128bit, >> 730/1800MHz, HDMI, DVI-D, D-sub >> >> What would be the best choice here: >> GEFORCE GT 730 >> or
2014 Mar 03
2
TV-Out on a GeForce 2MX supported?
Hello, I have here a GeForce 2MX (NV10) with a Brooktree BT869 chip for the TV-Out. Is the TV-Out on this card supported by Nouveau? I read on the feature matrix something that the TV-Out is only supported for some Chrontel chips, furthermore xrandr -q shows me only the DVI connection (in fact it's VGA, not DVI), but not the S-Video connection. If not supported, is this planned for future