> Peter Laws composed on 2017-07-21 14:29 (UTC-0500): > Sometimes "troubleshooting" instructions say to include nomodeset on the kernel > cmdline. You do not want to do that if you want an acceptable FOSS Xorg driver > to function. Nomodeset can work with the proprietary NVidia driver, but it > blocks use of modeset and nouveau Xorg drivers. The "Troubleshooting" menu item lets you select "basic graphics mode". After a day of futzing, this was the only way to get to the installation screen. Using the regular install selection yielded disk accesses (when I was trying with a DVD) and a black screen. > I couldn't find whatever doc you read that in, but "use a basic video driver" My assumption was that this would get me through the installation and not set it forever and ever. > happen. To find out which driver is being used, inspect /var/log/Xorg.0.log for > a large number of sequential lines beginning around two screens down from the > top of the file. Look for: > > fbdev(0) > vesa(0) > modeset(0) > nouveau(0) I've never been good at deciphering Xorg.0.log files, but ... [ 1638.443] (==) Matched nouveau as autoconfigured driver 0 [ 1638.443] (==) Matched modesetting as autoconfigured driver 1 [ 1638.443] (==) Matched fbdev as autoconfigured driver 2 [ 1638.443] (==) Matched vesa as autoconfigured driver 3 Who do I tell which one is being used and then how do I manipulate it? > Share Xorg.0.log via pastebin if the above isn't enough help. Oh, good idea. Hang on ... OK, see if this works: https://pastebin.com/bhnUCYSD --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
