search for: kugel

Hi Thomas, On Mon, Oct 01, 2018 at 04:25:06PM +0200, Thomas Martitz wrote: > Am 01.10.18 um 06:57 schrieb Daniel Drake: > > On Sun, Sep 30, 2018 at 5:07 AM Thomas Martitz <kugel at rockbox.org> wrote: > > > The latest iteration does not work on my HP system. The GPU fails to > > > power up just like the unpatched kernel. > > > > That's weird, I would not expect a behaviour change in the latest > > patch. pci_restore_config_dword(...

On Sun, Sep 30, 2018 at 5:07 AM Thomas Martitz <kugel at rockbox.org> wrote: > The latest iteration does not work on my HP system. The GPU fails to > power up just like the unpatched kernel. That's weird, I would not expect a behaviour change in the latest patch. pci_restore_config_dword() has some debug messages, could you please make t...

Am 31. Dezember 2015 03:54:43 MEZ, schrieb Karol Herbst <nouveau at karolherbst.de>: >> Thomas Martitz <kugel at rockbox.org> hat am 30. Dezember 2015 um 23:53 >> geschrieben: >> >> Am 25.12.2015 um 18:43 schrieb Pierre Moreau: >> > Hello, >> > >> > Maybe my e-mail client is messing with me, but I couldn't find any >dmesg >> > output >>...

Am 25.12.2015 um 18:43 schrieb Pierre Moreau: > Hello, > > Maybe my e-mail client is messing with me, but I couldn't find any dmesg output > attached to your e-mail. Could you please try to attach it again? > > By the way, since you have a Kepler, you should try booting with > "nouveau.War00C800_0=1". That workaround is enabled by default in 4.4-rc5 > (IIRC),

> Thomas Martitz <kugel at rockbox.org> hat am 30. Dezember 2015 um 23:53 > geschrieben: > > Am 25.12.2015 um 18:43 schrieb Pierre Moreau: > > Hello, > > > > Maybe my e-mail client is messing with me, but I couldn't find any dmesg > > output > > attached to your e-mail. Could...

Am 01.10.18 um 06:57 schrieb Daniel Drake: > On Sun, Sep 30, 2018 at 5:07 AM Thomas Martitz <kugel at rockbox.org> wrote: >> The latest iteration does not work on my HP system. The GPU fails to >> power up just like the unpatched kernel. > > That's weird, I would not expect a behaviour change in the latest > patch. pci_restore_config_dword() has some debug messages,...

Am 02.10.18 um 22:03 schrieb Bjorn Helgaas: > Hi Thomas, > > On Mon, Oct 01, 2018 at 04:25:06PM +0200, Thomas Martitz wrote: >> Am 01.10.18 um 06:57 schrieb Daniel Drake: >>> On Sun, Sep 30, 2018 at 5:07 AM Thomas Martitz <kugel at rockbox.org> wrote: >>>> The latest iteration does not work on my HP system. The GPU fails to >>>> power up just like the unpatched kernel. >>> >>> That's weird, I would not expect a behaviour change in the latest >>> patch. pci_restore_c...

...in-game Product: Mesa Version: 11.0 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at lists.freedesktop.org Reporter: kugel at rockbox.org QA Contact: nouveau at lists.freedesktop.org Created attachment 121072 --> https://bugs.freedesktop.org/attachment.cgi?id=121072&action=edit glxinfo I've got a GeForce 650 Ti, and when I'm using the SW cursor (either manually through xorg.conf, or enforced...

[+cc LKML] On Tue, Sep 18, 2018 at 04:32:44PM -0500, Bjorn Helgaas wrote: > On Thu, Sep 13, 2018 at 11:37:45AM +0800, Daniel Drake wrote: > > On 38+ Intel-based Asus products, the nvidia GPU becomes unusable > > after S3 suspend/resume. The affected products include multiple > > generations of nvidia GPUs and Intel SoCs. After resume, nouveau logs > > many errors such

this series solves different issues we encounter on kepler cards while reclocking: 1. core clock doesn't change at all and produces a volting error (patch 1) this can happen when the voltage table has only 0ed values in the header so we have to parse the entries itself, which contain the right voltages 2. kepler won't clock to highest cstates (patch 2) this happens, because there are

Am 25.12.2015 um 18:43 schrieb Pierre Moreau: > Hello, > > Maybe my e-mail client is messing with me, but I couldn't find any dmesg output > attached to your e-mail. Could you please try to attach it again? > > By the way, since you have a Kepler, you should try booting with > "nouveau.War00C800_0=1". That workaround is enabled by default in 4.4-rc5 > (IIRC),

Hello, first of all, I'm new to this list, so please beer with me. On the other hand, I'm a graduate computer systems engineer with experience in Linux kernel code, so I can hopefully provide useful input/assistance on this topic. I'm replying because I tried your patches on my setup in the hope they'd fix my lockups. Unfortunately they didn't, so I'm offering debug

Am 25.12.2015 um 19:37 schrieb Karol Herbst: > Hi Thomas, > > thanks for trying the branch out. Could you please send me your vbios? > > You can get it through installing envytools and nvagetbios or inside > /sys/kernel/debug/dri/*/vbios.rom > > The lookups can actually happen due to undervolting, my branch just fix the > issue that nouveau doesn't reclock at all.

Hello, i'm trying to configure a host SCSI device (tape drive) so that it is available in a KVM guest VM, but am receiving an error when attempting to attach the device. My guest xml has the following scsi controller defined: <controller type='scsi' index='0' model='virtio-scsi'> <alias name='scsi0'/> <address type='pci'

...changer devices from physical host, and use ISCSI client on KVM guest to access. We were successful using option 2 even though there is performance penalty for bridging with ISCSI. It gives us greater flexibility, we don't have to dedicate a PCI card to the KVM guest. ----- Forwarded by jkugel us ibm com on 07/10/2015 01:50 PM ----- jkugel us ibm com wrote on 07/06/2015 10:23:45 AM: > From: jkugel us ibm com > To: libvirt-users@redhat.com > Date: 07/06/2015 10:23 AM > Subject: Error attaching tape drive device to KVM guest > > Hello, > > i'm trying to conf...

Am 27.09.18 um 22:52 schrieb Bjorn Helgaas: > [+cc LKML] > > On Tue, Sep 18, 2018 at 04:32:44PM -0500, Bjorn Helgaas wrote: >> On Thu, Sep 13, 2018 at 11:37:45AM +0800, Daniel Drake wrote: >>> On 38+ Intel-based Asus products, the nvidia GPU becomes unusable >>> after S3 suspend/resume. The affected products include multiple >>> generations of nvidia GPUs

Hello, following up on myself, it was suggested on IRC that I better attach a dmesg output. Here's the output of a clean boot & echo 0f > /sys/.../pstate cycle. I can't spot a message that relates to the reclock action, and there's only one weird "nouveau 0000:04:00.0: clk: base: 7 MHz, boost: 7 MHz" message. On the other hand: # cat