Message: previous - next
Month: July 2017

Re: [trinity-users] Nvidia Quadro M2000

From: Peter Laws <plaws@...>
Date: Fri, 21 Jul 2017 17:06:14 -0500
On Fri, Jul 21, 2017 at 4:22 PM, Felix Miata <mrmazda@...> wrote:
> Your bootloader needs to have a less limiting selection made, or created, one
> that at the very least lacks
>         nomodeset
> 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.

(Damn gmail used to have Quote Selected Text and they pulled it a
couple weeks ago so now I have to do it manually - grumble.  Not
paying my Google bill this month)

Pulling nomodeset gets me lots of stuff that looks exciting in
Xorg.0.log but leaves me with a black display after spitting out the
now-displayed boot messages (which go by far too quickly to read -
maybe I'll video with my phone).

Assuming that nomodeset really is what I want and that now I need to
get the card configured for some mode I can see, how would I do that?

I'm also seeing that tdm.log has unhappiness in it, namely:

(==) Using system config directory "/usr/share/X11/xorg.conf.d"
nvc0_screen_create:762 - Error allocating PGRAPH context for M2MF: -16
EGL_MESA_drm_image required.
Jul 21 16:53:18 tdm[1812] error: X server startup timeout, terminating
(II) Server terminated successfully (0). Closing log file.
Jul 21 16:54:13 tdm[1812] error: X server for display :0 can't be
started, session disabled

The line with the PGRAPH thing turned up a bug against Puppy linux at that seems similar
... ick.

I really regret dumping the Ubuntu 14.04LTS image that was
pre-installed on this system because while not configured for TDE, it
was driving the card/display correctly.  :-)