Message: previous - next
Month: July 2017

Re: [trinity-users] Nvidia Quadro M2000

From: Felix Miata <mrmazda@...>
Date: Fri, 21 Jul 2017 17:22:37 -0400
Peter Laws composed on 2017-07-21 15:46 (UTC-0500):

>> 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.
I would make the same assumption, but that's not what happened to you. :-(

>> 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 ..
You misinterpreted or missed the "large number of sequential lines" part:

[1638.579] (II) FBDEV(0): Creating default Display subsection in Screen section
        "Default Screen Section" for depth/fbbpp 24/32
[1638.579] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[1638.579] (==) FBDEV(0): RGB weight 888
[1638.579] (==) FBDEV(0): Default visual is TrueColor
[1638.579] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[1638.579] (II) FBDEV(0): hardware: EFI VGA (video memory: 3072kB)
[1638.579] (II) FBDEV(0): checking modes against framebuffer device...
[1638.579] (II) FBDEV(0): checking modes against monitor...
[1638.579] (--) FBDEV(0): Virtual size is 1024x768 (pitch 1024)
[1638.579] (**) FBDEV(0):  Built-in mode "current": 78.7 MHz, 59.9 kHz...

> [  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? 
FBDEV is being used. Why is the question I can't answer easily because I don't
use CentOS. OK, from your pastebin, here's why:

[1638.435] Kernel command line: BOOT_IMAGE=/vmlinuz-3.10.0-514.26.2.el7.x86_64
root=/dev/mapper/cl_ip--10--197--15--52-root ro crashkernel=auto
nomodeset rhgb quiet LANG

Your bootloader needs to have a less limiting selection made, or created, one
that at the very least lacks


which blocks use of modeset and nouveau drivers. rhgb and quiet prevent you from
seeing possibly helpful messages as init proceeds. They are typically not needed
by people who like to know how init is progressing. I'm not familiar with
"crashkernel". Likely that's only for a rescue stanza, not normally needed.

>> Share Xorg.0.log via pastebin if the above isn't enough help.

> Oh, good idea.  Hang on ...

> OK, see if this works: 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***