Bug#833895: nvidia-legacy-340xx-driver: blank screen after upgrade

[Luis Mochan]

Dear Luca,
As your comments hinted at a misconfiguration and it had been a very
long time since I had used that machine, I ran a live jessie debian
distribution and the X-windows system worked with the nvidia driver,
but only in the failsafe mode. I decided then to make a fresh install of
jessie and later upgraded to stretch. I haven't installed nvidia yet,
but nouveau hadn't worked and it is working properly now, so the
crisis of my T61 is over. I still don't know if nvidia-legacy would
work now in my machine. I'll try it later. 
Thanks.
Luis


On Mon, Aug 15, 2016 at 07:24:42PM -0500, Luis Mochan wrote:
> Hi Luca,
> 
> On Mon, Aug 15, 2016 at 10:10:29PM +0100, Luca Boccassi wrote:
> > Control: severity -1 important
> > Control: tags -1 moreinfo
> > ...
> > I cannot reproduce on a fresh amd64 sid install with a gtx 780, so
> > downgrading severity as most likely cause is hardware or setup
> > dependent.
> OK. It is critical for me though... 
> > I notice in the device permissions that there is no user ACL bit set:
> > 
> > Device node permissions:
> > crw-rw---- 1 root video 226,   0 Aug  9 21:32 /dev/dri/card0
> > crw-rw-rw- 1 root root  195,   0 Aug  9 21:32 /dev/nvidia0
> > crw-rw-rw- 1 root root  195, 255 Aug  9 21:32 /dev/nvidiactl
> 
> Should there? 
> 
> > video:x:44:mochan,david,luquesnel,elias,gatis,david,irina
> > 
> > Is your user one of those listed in the "video" group?
> 
> Yes. Nevertheless, I don't even get to the login screen, so the
> problem appears before I'm become user.  I tried adding lightdm to the
> group video, but it didnt work either.
> 
> > What is the output of "getfacl /dev/dri/card0"?
> 
> mochan at fmunu:~$ getfacl /dev/dri/card0
> getfacl: Removing leading '/' from absolute path names
> # file: dev/dri/card0
> # owner: root
> # group: video
> user::rw-
> group::rw-
> other::---
> 
> > Are you running systemd + logind?
> 
> Running ps -e returns the lines:
> 
> mochan at fmunu:~$ ps -e|grep systemd
>   862 ?        00:00:00 systemd-udevd
>  4288 ?        00:00:00 systemd-logind
> but the program with pid=1 is init.
> Is there another test to better find out?
> 
> Thanks and best regards,
> Luis
> 
> 
> -- 
> 
>                                                                   o
> W. Luis Mochán,                      | tel:(52)(777)329-1734     /<(*)
> Instituto de Ciencias Físicas, UNAM  | fax:(52)(777)317-5388     `>/   /\
> Apdo. Postal 48-3, 62251             |                           (*)/\/  \
> Cuernavaca, Morelos, México          | mochan at fis.unam.mx   /\_/\__/
> GPG: 791EB9EB, C949 3F81 6D9B 1191 9A16  C2DF 5F0A C52B 791E B9EB
> 
> 

-- 

                                                                  o
W. Luis Mochán,                      | tel:(52)(777)329-1734     /<(*)
Instituto de Ciencias Físicas, UNAM  | fax:(52)(777)317-5388     `>/   /\
Apdo. Postal 48-3, 62251             |                           (*)/\/  \
Cuernavaca, Morelos, México          | mochan at fis.unam.mx   /\_/\__/
GPG: 791EB9EB, C949 3F81 6D9B 1191 9A16  C2DF 5F0A C52B 791E B9EB