Woohoo! It finally did something useful. To get dual monitors working, you need to think about your options. Either force the setup via xorg.conf, or let your desktop handle it via xrandr.
I think that you might have accidentally configured a combo of xorg/xrandr that sent us down this rabbit hole in the first place... So for right now, try startx, and see if it brings up the second display. This might be something we need to mess with at a PLUG clinic. Using your config from Ubuntu should work, but it gets cranky and I need to actually see how it fails before I can help. TBH I don't think it's possible to troubleshoot multimonitor problems with email. The errors are always visual. On Wed, Jan 16, 2019, 9:18 PM Dick Steffens <[email protected] wrote: > On 1/16/19 6:50 PM, Ben Koenig wrote: > > On Wednesday, January 16, 2019 6:38:09 PM PST Dick Steffens wrote: > >> On 1/16/19 5:56 PM, Ben Koenig wrote: > >>> Time permitted this afternoon. > >>> > >>>> I rebooted to run level 3. > >>> How are you rebooting to runlevel 3? > >> Powering down and back up. > >> > >>>> 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 have that set in the 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? > >> You had me set inittab to 3 several threads ago and said I should leave > >> it there until things work right. > >> > >>> - reinstall the base distribution packages that were overwritten > >>> slackpkg reinstall xorg-server libdrm mesa > >> I also did that before powering down the last time. > > Ok that's odd. > > > > When you boot up, does it go straight to a black screen? > > > > You need to sit there and watch it. Either it boots, gives you a wall of > > scrolling text and then a black screen.. > > > > OR, it boots, and immediately goes to a black screen after the kernel > loads. > > > > If the former, then I know what's going on. > > Well, it heard you talking about it, booted normally and gave me a login > prompt. I logged in as rsteff and the DVI monitor came up with the > normal stuff. The VGA monitor remains blank, as in no signal. I don't > recall that happening before. > > So, is there a way to get two monitors working at this point? > > -- > Regards, > > Dick Steffens > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
