similar to: [Bug 101368] Nouveau regression GT218M in Kernel 4.11 Won't Boot

Displaying 20 results from an estimated 40000 matches similar to: "[Bug 101368] Nouveau regression GT218M in Kernel 4.11 Won't Boot"

2017 Jun 21
0
[Bug 101368] Nouveau regression GT218M in Kernel 4.11 Won't Boot
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
2017 Jun 23
0
[Bug 101368] Nouveau regression GT218M in Kernel 4.11 Won't Boot
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
2017 Jun 23
0
[Bug 101368] Nouveau regression GT218M in Kernel 4.11 Won't Boot
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
2017 Jun 13
0
[Bug 101368] Nouveau regression GT218M in Kernel 4.11 Won't Boot
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
2017 Jun 20
0
[Bug 101368] Nouveau regression GT218M in Kernel 4.11 Won't Boot
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.
2017 Jun 26
0
[Bug 101368] Nouveau regression GT218M in Kernel 4.11 Won't Boot
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 --
2017 Jun 14
0
[Bug 101368] Nouveau regression GT218M in Kernel 4.11 Won't Boot
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,
2017 Sep 03
5
[Bug 102528] New: Display messed up shortly after boot on laptop with GT218M
https://bugs.freedesktop.org/show_bug.cgi?id=102528 Bug ID: 102528 Summary: Display messed up shortly after boot on laptop with GT218M Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: medium
2017 Sep 19
0
nVidia GT218M [GeForce 315M] issues on kUbuntu 17.04 x86-64.
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. > >
2017 Oct 10
0
nVidia GT218M [GeForce 315M] issues on kUbuntu 17.04 x86-64.
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
2017 Sep 19
2
nVidia GT218M [GeForce 315M] issues on kUbuntu 17.04 x86-64.
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) [
2017 Jun 25
4
[Bug 101587] New: [BISECTED][REGRESSION] Nouveau kernel module (>4.10) on NVA8 renders the system unusable
https://bugs.freedesktop.org/show_bug.cgi?id=101587 Bug ID: 101587 Summary: [BISECTED][REGRESSION] Nouveau kernel module (>4.10) on NVA8 renders the system unusable Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal
2017 Sep 19
0
nVidia GT218M [GeForce 315M] issues on kUbuntu 17.04 x86-64.
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
2017 Sep 19
2
nVidia GT218M [GeForce 315M] issues on kUbuntu 17.04 x86-64.
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
2017 Jun 08
0
nouveau "eDP-1: EDID is invalid" regression after 4.11 with HP ZBook 15 G3
Ben, I think I'm being hit with this bug (I see EDID is invalid in dmesg), is there any workaround outside of recompiling without that commit and can I give any information to help? Max -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20170608/de78457c/attachment.html>
2017 Jun 02
3
Kernel panic on nouveau during boot on NVIDIA NV118 (GM108)
We are working with new desktop that have the NVIDIA NV118 chipset. During boot, the display becomes unusable at the point where the nouveau driver loads. We have reproduced on 4.8, 4.11 and linux master (4.12-rc3). Dmesg log is attached. Is this a known issue? Anything we can do to help? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL:
2017 Jun 07
0
Kernel panic on nouveau during boot on NVIDIA NV118 (GM108)
It looks similiar to this one: https://bugs.freedesktop.org/show_bug.cgi?id=101322 please provide a dmesg booted with "nouveau.debug=debug" as well 2017-06-02 12:01 GMT+02:00 Chris Chiu <chiu at endlessm.com>: > We are working with new desktop that have the NVIDIA NV118 > chipset. > > During boot, the display becomes unusable at the point where the > nouveau driver
2017 Aug 14
0
nouveau driver locks up with 4.11 kernel
On Mon, Aug 14, 2017 at 4:29 PM, Michal Hocko <mhocko at kernel.org> wrote: > On Mon 14-08-17 15:27:20, Ilia Mirkin wrote: >> On Mon, Aug 14, 2017 at 3:18 PM, Michal Hocko <mhocko at kernel.org> wrote: > [...] >> > nouveau 0000:03:00.0: fifo: channel 6 [mpv/vo[3535]] kick timeout >> > nouveau: mpv/vo[3535]:00000000:0000906f: detach gr failed, -110 >>
2017 May 14
0
nouveau "eDP-1: EDID is invalid" regression after 4.11 with HP ZBook 15 G3
Hi, Bisected this to: commit df8dc97cd17269474344d73cc02739532c468d04 Author: Ben Skeggs <bskeggs at redhat.com> Date: Wed Mar 1 09:42:04 2017 +1000 drm/nouveau/kms/nv50: use drm core i2c-over-aux algorithm I'm not entirely sure NVKM needs to support this now, but I haven't removed it as of yet just in case it's needed from DEVINIT scripts where DRM isn't
2017 May 15
0
nouveau "eDP-1: EDID is invalid" regression after 4.11 with HP ZBook 15 G3
2017-05-15 3:03 GMT+03:00 Ben Skeggs <bskeggs at redhat.com>: > On 05/15/2017 01:10 AM, Tommi Rantala wrote: >> >> Hi, > > Hey Tommi, > > Thanks for bisecting this. It's rather unexpected that you should be seeing > problems here, but, the commit makes sense for it at least. > > Are you able to get me new kernel logs of both before and after this