similar to: [Bug 102528] New: Display messed up shortly after boot on laptop with GT218M

Hello looks like the device is not supported, the logs are as follows: --- # dmesg | grep nouve [ 2.789899] fb: switching to nouveaufb from VESA VGA [ 2.790060] nouveau 0000:01:00.0: NVIDIA GT218 (0a8d00b1) [ 2.815596] nouveau 0000:01:00.0: bios: version 70.18.7f.00.14 [ 2.816421] nouveau 0000:01:00.0: bios: OOB 1 01452301 01452301 [ 2.816427] nouveau 0000:01:00.0: bios: OOB 1

I will update the thread as soon as I get the hardware back. It was something serious like artifacts or no video in X so that I had to resort to proprietary drivers. So the question is whether this hardware is supported or not. On 2017-09-18 21:31, Ilia Mirkin wrote: > What seems to be the problem? I think you forgot to include a > description of the issues you're seeing. > >

https://bugs.freedesktop.org/show_bug.cgi?id=101368 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact| |xorg-team at lists.x.org Product|DRI |xorg Assignee|dri-devel at

https://bugs.freedesktop.org/show_bug.cgi?id=101368 --- Comment #8 from Ben Skeggs <skeggsb at gmail.com> --- I investigated an issue a while back that I believe is likely the same as what you're experiencing. I'm, unfortunately, not able to reproduce properly (long story) on any hardware I own. I've identified a few issues that could result in what you're seeing, however,

https://bugs.freedesktop.org/show_bug.cgi?id=101368 --- Comment #9 from wilrikerDE+freedesktop at gmail.com --- I have the same issue on an Asus PL80Jt which has the same Nvidia Chip built in. Using modprobe.blacklist=nouveau let's me but just fine (except that PRIME won't be enabled and the card will not be disabled by vgaswitcheroo). Otherwise I experience what has been described here.

https://bugs.freedesktop.org/show_bug.cgi?id=101368 --- Comment #10 from Ben Steel <bhs_suse at precisionforesight.com> --- Thank you Mr. Coenen. I agree. Kernel 4.12.0-rc6 does not exhibit the problem on a Lenovo T510 either. Between a fix already in the pipeline and a modeset workaround in the meantime, I'm happy. Does anyone still need the bisection completed? -- You are receiving

https://bugs.freedesktop.org/show_bug.cgi?id=101368 Ben Steel <bhs_suse at precisionforesight.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED -- You are receiving this mail

https://bugs.freedesktop.org/show_bug.cgi?id=101368 --- Comment #11 from Ben Skeggs <skeggsb at gmail.com> --- (In reply to Ben Steel from comment #10) > Thank you Mr. Coenen. I agree. Kernel 4.12.0-rc6 does not exhibit the > problem on a Lenovo T510 either. > Between a fix already in the pipeline and a modeset workaround in the > meantime, I'm happy. Does anyone still need

https://bugs.freedesktop.org/show_bug.cgi?id=101368 --- Comment #12 from Ben Steel <bhs_suse at precisionforesight.com> --- Yikes. I only waited about 28 hours before completely restoring that machine from backup and putting it back in service. Food for thought: my greatest fear is that the problem may have been illuminated by the change to GCC 7, which doesn't like compiling 4.10

https://bugs.freedesktop.org/show_bug.cgi?id=101368 Daniel Otero <otero.o.daniel at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freedesktop.or | |g/show_bug.cgi?id=101587 --

OK I got access to the hardware, it's Toshiba Satellite L730. One of the obvious problems is that there's no video in VLC nor in Dragon Player. Is this expected? Some output: --- yuriy at yuriy-Satellite-L730:~$ dmesg | grep NVID [ 2.752675] nouveau 0000:01:00.0: NVIDIA GT218 (0a8d00b1) ... root at yuriy-Satellite-L730:/home/yuriy# dpkg -l | grep nouv ii libdrm-nouveau2:amd64

What seems to be the problem? I think you forgot to include a description of the issues you're seeing. On Sep 18, 2017 11:23 PM, <ygrishin-lists at mail2.ca> wrote: Hello looks like the device is not supported, the logs are as follows: --- # dmesg | grep nouve [ 2.789899] fb: switching to nouveaufb from VESA VGA [ 2.790060] nouveau 0000:01:00.0: NVIDIA GT218 (0a8d00b1) [

Generically, yes, the hardware is supported. On Mon, Sep 18, 2017 at 11:42 PM, <ygrishin-lists at mail2.ca> wrote: > I will update the thread as soon as I get the hardware back. It was > something serious like artifacts or no video in X so that I had to resort to > proprietary drivers. > So the question is whether this hardware is supported or not. > > > On 2017-09-18

Commit df8dc97cd17 (drm/nouveau/kms/nv50: use drm core i2c-over-aux algorithm) switched things over to the drm algo. Unfortunately it generates address-only transactions. Prior to GF119, the hardware had no support for such things, and GF119+ the nouveau code did not handle these properly. The result of this bug is that EDID doesn't make it over for DP (and eDP) screens, which in turn wreaks

https://bugs.freedesktop.org/show_bug.cgi?id=70972 Priority: medium Bug ID: 70972 Assignee: nouveau at lists.freedesktop.org Summary: Nouveau fails with broken screen on nv40 with kernel 3.12 QA Contact: xorg-team at lists.x.org Severity: major Classification: Unclassified OS: Linux (All)

No. It would be helpful to understand what you are trying to accomplish overall, which may help people give you details about the best way to accomplish it. For example, if you are trying to understand or recover array indexes from GEP's, that is non-trivial. On Sat, Sep 2, 2017 at 3:53 AM, Anastasiya Ruzhanskaya via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Is there a way

Hi Joshua, Not a fix for your issue, but Ben noticed this (and fixed it): https://github.com/skeggsb/nouveau/commit/024bda7d2b0c3b0731433d60a494c78ab58cb216 which is what causes us to even try 540MB/s link training. However with this fix applied, it'll just give up faster. I'm told eDP is generally a single lane, and you're trying to get more than 270MB/s. So ... the question is ...

Another log, per Lyude on #nouveau. j On Tuesday, January 14, 2020 8:52:51 AM AKST Joshua J. Kugler wrote: > Here we go! > > j > > On Tuesday, January 14, 2020 7:08:20 AM AKST Ilia Mirkin wrote: > > Hi Joshua, > > > > Not a fix for your issue, but Ben noticed this (and fixed it): > > > >

Hi! I have a very strange problem with a recently purchased ViewSonic 4k display connected via display port to a Thinkpad 410 with nvidia gt218m (nvs 3100m). Every time the mouse pointer touches the left edge of the screen, the display becomes a block of solid color and freezes. Suspend/resume of the laptop reanimates the display. I suspected a bug in the handling of the hardware cursor, so

I've added debugging command-line parameters to the kernel command line, per skeggsb and imirkin on #nouveau. root at joyful:~# cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro quiet splash log_buf_len=8M nouveau.debug=disp=trace,bios=trace,i2c=trace 3 On this particular run, closing the lid and then opening got me back to the console, but then I