Re: [PLUG] Slackware login pain

2019-01-08 Thread Dick Steffens
On 1/8/19 8:22 PM, Ben Koenig wrote: I'm trying to figure out what's broken here and I just can't see it. The subject of this thread was something about problems logging in. Turned out to be an issue with having the wrong nvidia driver installed. I should have started a new thread. I'll do

Re: [PLUG] Slackware login pain

2019-01-08 Thread Ben Koenig
I'm trying to figure out what's broken here and I just can't see it. The subject of this thread was something about problems logging in. Turned out to be an issue with having the wrong nvidia driver installed. And now you say that X launches the nvidia-settings program runs as expected. Looks

Re: [PLUG] Slackware login pain

2019-01-08 Thread Dick Steffens
On 1/7/19 3:37 PM, Ben Koenig wrote: Wait a second why is nvidia-settings trying to create an xorg.conf file? I thought the program was nvidia-xconfig .. It occurred to me that if I have a correct nVidia setup on my Ubuntu machine, which has a very similar monitor setup, I could compare

Re: [PLUG] Slackware login pain

2019-01-07 Thread Dick Steffens
On 1/7/19 3:37 PM, Ben Koenig wrote: Wait a second why is nvidia-settings trying to create an xorg.conf file? I thought the program was nvidia-xconfig .. Are you running nvidia-settings from a graphical terminal? With X running? Yes. It's available from the Applications > Settings menu

Re: [PLUG] Slackware login pain

2019-01-07 Thread Ben Koenig
Wait a second why is nvidia-settings trying to create an xorg.conf file? I thought the program was nvidia-xconfig .. Are you running nvidia-settings from a graphical terminal? With X running? On Mon, Jan 7, 2019 at 3:15 PM Dick Steffens wrote: > On 1/7/19 2:59 PM, Ben Koenig wrote: > >

Re: [PLUG] Slackware login pain

2019-01-07 Thread Dick Steffens
On 1/7/19 2:59 PM, Ben Koenig wrote: the blacklist file prevents Nouveau from loading, but if you need to double check that it actually worked you use 'lsmod' I pipe the output to grep to shorten the list: $ lsmod |grep nouveau root@ENU-2:~# lsmod | grep nouveau root@ENU-2:~# This will

Re: [PLUG] Slackware login pain

2019-01-07 Thread Ben Koenig
the blacklist file prevents Nouveau from loading, but if you need to double check that it actually worked you use 'lsmod' I pipe the output to grep to shorten the list: $ lsmod |grep nouveau This will output a single line if it finds the nouveau kernel module, or do nothing if nouveau is not

Re: [PLUG] Slackware login pain

2019-01-07 Thread Dick Steffens
On 1/5/19 8:30 PM, King Beowulf wrote: <...> (stuff I did yesterday) now comment out the nouveau blacklist in /etc/modprobe.d/BLACKLIST-nouveau.conf: # Do not load the kernel nouveau dri module, since it interferes with both # the nv and binary nvidia drivers. #blacklist nouveau (once you

Re: [PLUG] Slackware login pain

2019-01-06 Thread Dick Steffens
On 1/6/19 12:51 AM, Ben Koenig wrote: No, that looks fine. Don't delete them. Most of those files should have been replaced when you reinstalled the packages as suggested by Ed. All you need to do is reboot so that nouveau loads properly and everything should be set. Reboot, see what it gives

Re: [PLUG] Slackware login pain

2019-01-06 Thread Dick Steffens
On 1/5/19 9:46 PM, Daniel Johnson wrote: On Slackware does run level 3 start sshd? Just making sure so he doesn't kill a secondary login. Also are you sure none of the libGL and glx stuff is part of mesa or X? I'm used to package managers doing the right thing, and if I have to touch a system

Re: [PLUG] Slackware login pain

2019-01-05 Thread Dick Steffens
On 1/5/19 8:30 PM, King Beowulf wrote: Hello Dick, The other replies have some good ideas, but lets go back to basics since you can ssh in. I do not think there is a need to reinstall from scratch just yet. When you leave the login manager, X tries to load all the other stuff and can't, so

Re: [PLUG] Slackware login pain

2019-01-05 Thread Daniel Johnson
On Slackware does run level 3 start sshd? Just making sure so he doesn't kill a secondary login. Also are you sure none of the libGL and glx stuff is part of mesa or X? I'm used to package managers doing the right thing, and if I have to touch a system .so that usually means a third party

Re: [PLUG] Slackware login pain

2019-01-05 Thread King Beowulf
On 1/5/19 7:52 PM, wes wrote: > On Sat, Jan 5, 2019 at 6:18 PM Dick Steffens wrote: > >> Would the >> solution there of deleting all .serverauthXXX and .Xauthority files as >> root be something I should do here? >> > > Yes, you should try this. Also look for a .ICEauthority file to delete or >

Re: [PLUG] Slackware login pain

2019-01-05 Thread wes
On Sat, Jan 5, 2019 at 6:18 PM Dick Steffens wrote: > Would the > solution there of deleting all .serverauthXXX and .Xauthority files as > root be something I should do here? > Yes, you should try this. Also look for a .ICEauthority file to delete or rename. -wes

Re: [PLUG] Slackware login pain

2019-01-05 Thread Daniel Johnson
I need an email app for my phone that doesn't force top posting. Gah! Anyways. Ok you can login to VT2. Startx doesn't work. Could be the display manager is locking a resource you need. startxfce4: X server already running on display :1 Is a clue. Could maybe only need to tell it to use display

Re: [PLUG] Slackware login pain

2019-01-05 Thread Dick Steffens
On 1/5/19 5:12 PM, Daniel Johnson wrote: If your goal is learning then it's worth it. If your goal was just having it work I'm not sure you would have picked Slackware as your distro so I'm going with learning. A little of both. I've been using the easy to install and run stuff for something

Re: [PLUG] Slackware login pain

2019-01-05 Thread Daniel Johnson
If your goal is learning then it's worth it. If your goal was just having it work I'm not sure you would have picked Slackware as your distro so I'm going with learning. Being able to login via ssh means the password isn't corrupted. Being able to type a username probably means the keyboard input