[mythtv-users] New Mythbuntu 14.04 battle with nvidia boot up

[Craig Huff]

On Fri, Oct 17, 2014 at 7:17 AM, Craig Huff <huffcslists at gmail.com> wrote:
> Thanks!  I'll give that a try, but I suspect I'll get the same display
> as I do if I hit the escape key when the splash screen first appears.
> Here's hoping that is not the case and this works.
>
> --
> Craig.


I was wrong about it showing only the same info as results after
hitting the escape key.  Sadly, I still have lockup problems.

The symptom is still that on cold boots it gets just so far then
nothing works, not even ctrl+alt+F1 or ctrl+alt+del.  Note that the
problem is only on cold boots -- several tests of warm boots have all
succeeded -- go figure.  (Where by warm boot I mean either issuing the
command "sudo shutdown -r now" or going through the menu system to
choose a system restart.)

On failures, the following line is always the last line on the screen:
* Stopping System V runlevel compatibility.............[ OK ]

On successful bootups, the above line may/may not have others that
follow before the screen switches over to X and the desktop gets
displayed, then hidden by the frontend window, but that disappears and
I get a B&W diagonal pinstripe desktop with no toolbar or icons until
I hit alt+tab.  Doing so results in the frontend window displaying.
That means I have another problem to look into once I get this one
resolved.  This is on a vanilla Mythbuntu 14.04.1 install (so far) and
there are no other applications being started up that open a window,
so I don't know why the FE window loses focus.

I just tried another time (not sure it matters, but from frozen system
I hit the front panel reset button and hit return in the grub menu to
retry the default boot option) and got something different that I see
rarely.  After the "Stopping System V runlevel" line there were a
number of lines associated with [Hardware Error].  The first reported
watchdog timeout due to lack of progress and about a dozen lines later
it reported kernel panic and shutting down cpus with NMI.

Anyone with an insight into what the heck is going (not going) on?

--
Craig.