Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #197137 > unrolled thread
| Started by | Erwan David <erwan@rail.eu.org> |
|---|---|
| First post | 2018-07-02 20:10 +0200 |
| Last post | 2018-07-02 20:50 +0200 |
| Articles | 4 — 2 participants |
Back to article view | Back to linux.debian.user
Kernel 4.16.16-2 and nvidia 390.48-3 Erwan David <erwan@rail.eu.org> - 2018-07-02 20:10 +0200
Re: Kernel 4.16.16-2 and nvidia 390.48-3 davidson <davidson@freevolt.org> - 2018-07-02 20:20 +0200
Re: Kernel 4.16.16-2 and nvidia 390.48-3 Erwan David <erwan@rail.eu.org> - 2018-07-02 20:40 +0200
Re: Kernel 4.16.16-2 and nvidia 390.48-3 davidson <davidson@freevolt.org> - 2018-07-02 20:50 +0200
| From | Erwan David <erwan@rail.eu.org> |
|---|---|
| Date | 2018-07-02 20:10 +0200 |
| Subject | Kernel 4.16.16-2 and nvidia 390.48-3 |
| Message-ID | <w7bqX-1DN-13@gated-at.bofh.it> |
Hi, Since upgrade to kernel 4.16.16-2 I cannot get X11 (not even SDDM), everything blocks with a black screen (event the numlock does not work). On another PC with Intel driver, no problem, so I suspect it might be a problem between this kernel and the nvidia driver (I have version 390.48-3 from testing). Is it a known issue ? What should I do to help debug ? (I did not find anythingin the logs, just it stopped logging same time it stopped everything).
[toc] | [next] | [standalone]
| From | davidson <davidson@freevolt.org> |
|---|---|
| Date | 2018-07-02 20:20 +0200 |
| Message-ID | <w7bAB-1Hi-5@gated-at.bofh.it> |
| In reply to | #197137 |
On Mon, 2 Jul 2018, Erwan David wrote: > Hi, > > Since upgrade to kernel 4.16.16-2 I cannot get X11 (not even SDDM), > everything blocks with a black screen (event the numlock does not > work). On another PC with Intel driver, no problem, so I suspect it > might be a problem between this kernel and the nvidia driver (I have > version 390.48-3 from testing). > > Is it a known issue ? What should I do to help debug ? (I did not > find anythingin the logs, just it stopped logging same time it > stopped everything). This sounds familiar. Problem posed... https://lists.debian.org/msgid-search/23c30419-939a-100a-9850-d44d271ade59@panix.com https://lists.debian.org/debian-user/2018/07/msg00059.html ...answer suggested: https://lists.debian.org/msgid-search/2264791.P37jLuWAQ5@kazoo https://lists.debian.org/debian-user/2018/07/msg00067.html
[toc] | [prev] | [next] | [standalone]
| From | Erwan David <erwan@rail.eu.org> |
|---|---|
| Date | 2018-07-02 20:40 +0200 |
| Message-ID | <w7bTX-1Ny-1@gated-at.bofh.it> |
| In reply to | #197139 |
Le 07/02/18 à 20:15, davidson a écrit : > On Mon, 2 Jul 2018, Erwan David wrote: > >> Hi, >> >> Since upgrade to kernel 4.16.16-2 I cannot get X11 (not even SDDM), >> everything blocks with a black screen (event the numlock does not >> work). On another PC with Intel driver, no problem, so I suspect it >> might be a problem between this kernel and the nvidia driver (I have >> version 390.48-3 from testing). >> >> Is it a known issue ? What should I do to help debug ? (I did not >> find anythingin the logs, just it stopped logging same time it >> stopped everything). > > This sounds familiar. > > Problem posed... > > https://lists.debian.org/msgid-search/23c30419-939a-100a-9850-d44d271ade59@panix.com > > https://lists.debian.org/debian-user/2018/07/msg00059.html > > ...answer suggested: > > https://lists.debian.org/msgid-search/2264791.P37jLuWAQ5@kazoo > https://lists.debian.org/debian-user/2018/07/msg00067.html > > Thanks it was indeed the solution
[toc] | [prev] | [next] | [standalone]
| From | davidson <davidson@freevolt.org> |
|---|---|
| Date | 2018-07-02 20:50 +0200 |
| Message-ID | <w7c3E-1QY-7@gated-at.bofh.it> |
| In reply to | #197141 |
[Multipart message — attachments visible in raw view] — view raw
On Mon, 2 Jul 2018, Erwan David wrote: > Le 07/02/18 à 20:15, davidson a écrit : >> On Mon, 2 Jul 2018, Erwan David wrote: >> >>> Hi, >>> >>> Since upgrade to kernel 4.16.16-2 I cannot get X11 (not even SDDM), >>> everything blocks with a black screen (event the numlock does not >>> work). On another PC with Intel driver, no problem, so I suspect it >>> might be a problem between this kernel and the nvidia driver (I have >>> version 390.48-3 from testing). [snip] >> >> Problem posed... >> >> https://lists.debian.org/msgid-search/23c30419-939a-100a-9850-d44d271ade59@panix.com >> https://lists.debian.org/debian-user/2018/07/msg00059.html >> >> ...answer suggested: >> >> https://lists.debian.org/msgid-search/2264791.P37jLuWAQ5@kazoo >> https://lists.debian.org/debian-user/2018/07/msg00067.html >> >> > Thanks it was indeed the solution For the record, a link to bug report: #901919 - nvidia-driver: black screen with the latest Linux kernel - general protection fault https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901919
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web