similar to: Possible nouveau driver problem?

I have a Dell XPS 13 (9360) with Fedora 26 installed. Very happy with it. UEFI boot from flash drive works out of the box. For install I needed to change the drive settings in the BIOS from the default of RAID (what ever that means on a laptop) to AHCI. No need to turn off secure boot. If you want to use a DisplayLink USB display adaptor like the D3100 (commonly sold with this laptop), you

Hello there, I've just got a Dell XPS 15 (9590) at work and need to set up a stable GNU/Linux system on it. I thought of CentOS7, but.. obviously its kernel can't run on this hardware. What would you recommend? Waiting for CentOS8 is not an option unless it's a question of few weeks. Are there respins of the CentOS7 DVDs w/ more top-recent kernels? I'm know of Fedora 26 or

https://bugs.freedesktop.org/show_bug.cgi?id=112197 Bug ID: 112197 Summary: Black screen after resume Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: not set Component: Driver/nouveau Assignee: nouveau at

Hi, I am trying to configure my Tripp Lite SU5000RT3U on Ubuntu 18.04 as I am not able to completely get all the data from the UPS. After installing all required packages from the Ubuntu repos (had to run sudo apt-get install dkms, I had to install the displaylink drivers from displaylink.org by doing sudo ./displaylink-driver-4.2.29.run, and I created a sim link by doing the following: sudo ln

I installed C7 along with MATE desktop... My monitor is a 4K unit but when I goto the System -> preferences -> hardware -> Displays there is selection for the 4K display. It stops at 1920x1080. The var log x file shows the 4K resolutions in the file so that is good. How do I get the selections for 4K to show up? Thanks, Jerry

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()

Hello all, I just installed CentOS 7.8 on ASRock B460M Pro4 board. CPU is i5-10400. The display device is inside the CPU and the max resolution is 4096x2160 for HDMI. But when I connect my small screen (max full HD), the display resolution is only 800x600. >From seeing some info here, I installed EPEL for yum, and inxi. The "inxi -G" command's output is like this :

Hello all, I just installed CentOS 7.8 on ASRock B460M Pro4 board. CPU is i5-10400. The display device is inside the CPU and the max resolution is 4096x2160 for HDMI. But when I connect my small screen (max full HD), the display resolution is only 800x600. >From seeing some info here, I installed EPEL for yum, and inxi. The "inxi -G" command's output is like this :

[adding various lists and the two other nouveau maintainers to the list of recipients] For the rest of this mail: [TLDR: I'm adding this report to the list of tracked Linux kernel regressions; the text you find below is based on a few templates paragraphs you might have encountered already in similar form. See link in footer if these mails annoy you.] On 18.01.23 21:59, Chris Clayton 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

https://bugs.freedesktop.org/show_bug.cgi?id=104621 Bug ID: 104621 Summary: Nouveau prevents booting on Pascal Gpu Product: Mesa Version: 17.3 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at

Hi All - Has anyone tried using a USB 4K adapter ? Something like Startech USB32HD4K? Are these devices on option for linux ? Thanks Jerry

Fixes runpm breakage mainly on Nvidia GPUs as they are not able to resume. Works perfectly with this workaround applied. RFC comment: We are quite sure that there is a higher amount of bridges affected by this, but I was only testing it on my own machine for now. I've stresstested runpm by doing 5000 runpm cycles with that patch applied and never saw it fail. I mainly wanted to get a

On Tue, Sep 4, 2018 at 2:43 PM, Mika Westerberg <mika.westerberg at linux.intel.com> wrote: > Yes, can you check if the failing device BAR is included in any of the > above entries? If not then it is probably not related. mtrr again for reference: reg00: base=0x0c0000000 ( 3072MB), size= 1024MB, count=1: uncachable reg01: base=0x0a0000000 ( 2560MB), size= 512MB, count=1: uncachable

Hi, I have a computer with an integrated graphic card and a discrete graphic card, namely: # lspci | grep -E "VGA|3D" 00:02.0 VGA compatible controller: Intel Corporation Broadwell-U Integrated Graphics (rev 09) 03:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 840M] (rev a2) This is confirmed by vgaswitcheroo: xray:/ # cat /sys/kernel/debug/vgaswitcheroo/switch

Hi, On 2023/9/5 22:52, Alex Williamson wrote: > On Tue, 5 Sep 2023 03:57:15 +0800 > Sui Jingfeng <sui.jingfeng at linux.dev> wrote: > >> From: Sui Jingfeng <suijingfeng at loongson.cn> >> >> On a machine with multiple GPUs, a Linux user has no control over which >> one is primary at boot time. This series tries to solve above mentioned >>

https://bugs.freedesktop.org/show_bug.cgi?id=100423 Bug ID: 100423 Summary: MMIO read of 00000000 FAULT at 022554 [ IBUS ] Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

On Wed, Nov 20, 2019 at 11:52:22AM +0100, Rafael J. Wysocki wrote: > On Wed, Nov 20, 2019 at 11:18 AM Mika Westerberg > <mika.westerberg at intel.com> wrote: > > > > Hi Karol, > > > > On Tue, Nov 19, 2019 at 11:26:45PM +0100, Karol Herbst wrote: > > > On Tue, Nov 19, 2019 at 10:50 PM Bjorn Helgaas <helgaas at kernel.org> wrote: > > > >