[lubuntu-devel] "TTY" goes to black screen, then doesn't come out of it?

[Fritz Hudnut]

WxL:

Thanks for taking the time to look at it . . . I don't think I registered
as a dev, but obviously I did register with their forum . . . and the
guy/gal did reply and look into it.  One thing I learned years ago is to
listen to what people say, and they said literally, "I filed the bug, don't
hold your breath, we ain't going to fix legacy hardware . . . " and indeed
there never was any follow up on the bug as sometimes happens in the
launchpad zone . . . .

It's kind of a double whammy going into the Nvidia card, which I did to get
a "metal friendly" card that would meet the requirements for OSX 10.14 . .
. which it did, but that brought me into a struggle between Apple and
Nvidia as far as, Apple not giving Nvidia the permission to use the drivers
for it, and Nvidia not releasing them even though they have them . . . so
10.14 runs on my computer, but just like it was in "nouveau" the computer
won't "sleep" . . . it just blinks black.

So, the Nvidia card was a "better" card than the radeon that was OEM, but
it has been "finicky" . . . and in some of the cases going proprietary
"fixed" the "suspend" issue, but . . . then opened the TTY problem . . .
and now Apple says this '12 MPro doesn't qualify for 10.15 . . . so I'd
have to go hacker on it if I wanted to move up . . . .

Which is why having some linux options makes that whole "EFI" problem less
of a worry . . . .  I'll fiddle around with the ubuntu distros and see how
things fare in 20.04 with nouveau . . . since I like "bleeding edge" linux
distros Nvidia is probably never going to be right there for it . . . .  If
you looked at the "linux" sub-forum you might have seen a post about
"Nvidia drivers not working in ubuntu 19.04?" . . . on a Dell . . . ????

F

On Tue, Jan 28, 2020 at 1:24 PM Walter Lapchynski <wxl at ubuntu.com> wrote:

> On Tue, Jan 28, 2020 at 12:36:36PM -0800, Fritz Hudnut wrote:
> > Well, I couldn't find the link to their bug number
>
> You have to have a [NVIDIA developer account to access the bugs][1].
>
> >
> https://devtalk.nvidia.com/default/topic/1063182/nvidia-drivers-don-t-include-access-to-tty-terminal-/?offset=1#5383801
>
> Looks like they're indeed blaming your EFI, which is strange. If nouveau
> works with the TTY, that might be the extra information they need. In
> fact, the "code" quoted there by the NVIDIA rep is actually a line from
> your `dmesg` output. If you could fine the parts that deal with the
> framebuffer when running nouveau, that might help them figure out how to
> fix their stuff. Chances are, they won't spend much time on it, though.
>
> Either way, this demonstrates a big issue with proprietary hardware and
> software. With proprietary hardware, it's difficult to provide open
> source software solutions like drivers, because the hardware is
> ultimately unknown and can be (at best) reverse engineered. And when the
> makers of the proprietary hardware produce proprietary software, then
> you're beholden to them to fix any problems. No one else outside of the
> company, regardless of their skill level or understanding, can help
> improve the situation. Similarly, since these are ultimately employees
> of a for-profit business, at some point, they're forced to cut their
> losses and stop supporting products they have discontinued.
>
> And that's why you hear so many people in the open source world crying
> so desperately for more open source solutions, especially in hardware
> where such solutions are so rare.
>
> [1]:
>
> https://devtalk.nvidia.com/default/topic/1044668/cuda-programming-and-performance/-how-to-report-a-bug/
> --
>        @wxl | polka.bike
> C563 CAC5 8BE1 2F22 A49D
> 68F6 8B57 A48B C4F2 051A
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/lubuntu-devel/attachments/20200128/070c34df/attachment-0001.html>