On Wednesday, January 16, 2019 5:43:02 PM PST Dick Steffens wrote: > On 1/16/19 4:23 PM, Dick Steffens wrote: > > On 1/16/19 4:12 PM, Ben Koenig wrote: > >> You are trying to fix the problem without any knowledge of what the > >> problem is. > >> This is why I constantly tell people to slow down. The log you just > >> posted > >> hits on multiple topics in one single braindump. > >> > >> To break it down into 3 topics... > >> > >> First, Go back to nvidia-390, there was never a reason to downgrade. > >> > >> Second, boot errors about a VGA console are normal. The Nvidia module > >> complains, but it is a meaningless error and can be ignored. > >> > >> Third, I don't think you ever told us what exactly you are trying to > >> do with > >> your multi-monitor config. I remember a lot of confusion and chaos about > >> getting X started and using xorg.config files in your home directory > >> (which does > >> not work, X doesn't load config files from $HOME..). > >> > >> Since your driver packages are now FUBAR, run the following steps to > >> get back > >> to a working display: > >> - Uninstall any nvidia driver packages on your system > > > > Do I run nvidia-switch --remove, slackpkg remove > > nvidia-legacy340-driver ... (both driver and kernel), or all of the > > above? > > > > And, do I need to restart at run level 3 to do these? > > > >> - reinstall the base distribution packages that were overwritten > >> slackpkg reinstall xorg-server libdrm mesa > >> > >> - Make sure you DON'T have a file named /etc/X11/xorg.conf > >> - delete the nouveau blacklist file in /etc/modprobe.d/ > >> - reboot > >> > >> After you reset back to the sane defaults, you can explain to us what > >> it is > >> you are trying to do and maybe someone can advise a path forward. > > > > I'll give that a shot when time permits, possibly tomorrow. > > Time permitted this afternoon. > > I rebooted to run level 3.
How are you rebooting to runlevel 3? > I ran nvidia-switch --remove > > I ran slackpkg remove nvidia-legacy390-driver ... > I ran slackpkg remove nvidia-legacy390-kernel ... > I ran slackpkg remove nvidia-legacy340-driver ... > I ran slackpkg remove nvidia-legacy340-kernel ... > All four completed, although the 390 kernel complained that some files > were in use. I assume they were also there as part of the 340 package. > > I deleted /etc/X11/xorg.conf, and a few backups with that name included. > > I deleted the nouveau blacklist file from /etc/modprobe.d > > Then I rebooted, or at least tried to. > > I watched as the system shut itself down. But when I started it back up, > I saw a little graphic in the upper left corner of my DVI monitor blink > between Analog and Digital a few times, and then stop. No response to > the keyboard. When trying to ssh in, I got the message: > > dick@ENU-1:~$ ssh [email protected] > ssh: connect to host 192.168.0.134 port 22: No route to host Make sure your host really is at 192.168.0.134. That looks like a DHCP address, so it can change unless you configured it specifically not to on your router. > > I can still boot from the install USB stick, which is what I expect I'll > need to do next. > > Recommendations on what else to do next? I really want to know what you mean by "rebooted to runlevel 3". What is inittab currently set to? _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
