similar to: 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

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

Can you try something very simple - unplug the cable, and plug it back in, while the TV is on, and set to the HDMI input? That should ensure that the SCDC write can go through at modeset time. You can also force nouveau to avoid any modes that require scrambling by booting with nouveau.hdmimhz=340. Cheers, -ilia On Tue, Aug 6, 2019 at 1:15 PM James <bjlockie at lockie.ca> wrote: >

This is the beginnings of HDMI 2.0 support. All of the "extra" features are left out, such as 12/16bpc, YUV420, etc. I've verified that with this code, a GP108 (GT1030) can switch between 4k at 60 and 1920x1080 at 60 on a LG 4K TV. Further, I've verified via i2c tools, that the SCDC writes really do happen. I suspect that the patch for keeping track of the high-speed TMDS

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.

On August 6, 2019 1:36:09 p.m. Ilia Mirkin <imirkin at alum.mit.edu> wrote: > Can you try something very simple - unplug the cable, and plug it back > in, while the TV is on, and set to the HDMI input? I still only get 30Hz. I did just update the tv firmware s9 maybe that is why I can't get it 60Hz anymore. I wish I kept better track of the timeline. With the new HDMI 2 cable I

From: Ville Syrj?l? <ville.syrjala at linux.intel.com> Get rid of mode->vrefresh and just calculate it on demand. Saves a bit of space and avoids the cached value getting out of sync with reality. Mostly done with cocci, with the following manual fixups: - Remove the now empty loop in drm_helper_probe_single_connector_modes() - Fix __MODE() macro in ch7006_mode.c - Fix DRM_MODE_ARG()

On 2017-06-19 01:18 PM, Ilia Mirkin wrote: > cat /sys/kernel/debug/dri/0/pstate > > AC (or DC) line shows the current state. > > On Mon, Jun 19, 2017 at 1:00 PM, James <bjlockie at lockie.ca> wrote: >> I have a NVE7 (GK107). >> How do I see the current memory/CPU speed? $ sudo cat /sys/kernel/debug/dri/0/pstate 07: core 324 MHz memory 648 MHz 0a: core 540 MHz

From: Ville 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. Cc: Alex Deucher <alexander.deucher at amd.com> Cc: "Christian König" <christian.koenig at amd.com>

On 2017-06-19 01:38 PM, Ilia Mirkin wrote: > On Mon, Jun 19, 2017 at 1:32 PM, James <bjlockie at lockie.ca> wrote: >> On 2017-06-19 01:18 PM, Ilia Mirkin wrote: >>> cat /sys/kernel/debug/dri/0/pstate >>> >>> AC (or DC) line shows the current state. >>> >>> On Mon, Jun 19, 2017 at 1:00 PM, James <bjlockie at lockie.ca> wrote:

On 05/04/2017 04:00 AM, Pierre Moreau wrote: > Hello, > > Acceleration for Pascal cards is coming in Linux 4.12, support for Pascal cards > in xorg-video-nouveau is in 1.0.15, and if I remember correctly, on the > Mesa-side, you will need >=17.0. Thanks - I suspected it was too new. I'm finding the monitor capabilities miss identified even if I use an older card - I'm

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. >>

On 07/14/10 11:27, Arjen de Korte wrote: > the UPS should power off(and restart when the power comes back Can I set any UPS to only provide power after the battery is charged to a certain level? Or better yet, a certain length on consecutive time when the power has been on. I'd be worried about flapping, where the power goes on and off.

I have a NVE7 (GK107). How do I see the current memory/CPU speed?

https://bugs.freedesktop.org/show_bug.cgi?id=93405 Bug ID: 93405 Summary: nouveau: Xorg crashes sooner or later in 3840x2160 mode Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component:

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: koutput Type: application/x-java-vm Size: 2881 bytes Desc: not available Url : http://www.winehq.org/pipermail/wine-users/attachments/20021128/a81741b4/koutput.class

https://bugs.freedesktop.org/show_bug.cgi?id=94342 Bug ID: 94342 Summary: Nvidia G96GLM 3840x2160 at 30 not functional with nouveau Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

My UPS has an LCD that says the battery is 100% and the estimated run time is 12min. The uspc has similar results. The problem is when line power is lost the UPS batter goes to 0% very quickly (seconds). It charged to 85% when power was restored. 86-100% is slower. I did: $ upscmd desktop_ups test.battery.start.deep Username (admin): Password: OK Now the ups.test.result says there is a

Was /etc/nut/upssched-cmd automatically installed? I don't have it on my raspberry pi. :-( On 2019-04-03 1:54 p.m., Mike wrote: > I figured this out and it is working now.  This fix seems strange to me > and is possibly a bug.  I'm sharing in case it might help others. > > I had to uncomment all of the NOTIFYFLAG statements whether I was > changing them or not. 

Let us consider the current uniform sampling without replacement algorithm. It resides in function do_sample in https://svn.r-project.org/R/trunk/src/main/random.c Its complexity is obviously O(n), where the sample is selected from 1...n, since the algorithm has to create a vector of length n. So when the sample size is much lesser than n, the algorithm is not effective. Algorithms with