It's been a whole month since I got my system working with my superwide display and the newest Nvidia drivers.
All was well until today, when it got past the GRUB2 boot and began to run Plymouth. At that point, the screen freezes in the top third and fills the bottom third with either a splatter of dashes [-] or a solid color, blue so far...
I can see my custom gfxboot image for a second in the bottom third of the screen, then the dashes.
I ignored the display and was able to log in as root and force a shutdown, so I may have partial control of the command line.
I haven't tried startx yet because I don't know if X is even running. I doubt it.
Is this another nvidia problem, or possibly related to the GRUB2 boot issue?
Anyone else have this behavior? I'm stuck for now...
I edited the GRUB2 script, removing quiet and splash with no change.
I know the command line is still working, but I am blind, since the display is only showing garbage characters.
If I switch to TTY7, the bottom third of the screen turns blue, so X is running. I still can't see anything since the display is not working.
This machine is working fine running Win10 with no issues....
I seem to have control on the CL by logging in as root and sending various commands, such as halt and reboot. I tried XFdrake and the bottom third went blank, indicating the text (gibberish) had switched to the ncurses.
The only further steps I can think of would be to ssh into the box and poke around, buy I don't know what I am looking for! Why would the graphics be broken before the X session starts?
I don't want to reinstall, but I can handle lots of surgery to get this figured out...
Thanks for any insights
All was well until today, when it got past the GRUB2 boot and began to run Plymouth. At that point, the screen freezes in the top third and fills the bottom third with either a splatter of dashes [-] or a solid color, blue so far...
I can see my custom gfxboot image for a second in the bottom third of the screen, then the dashes.
I ignored the display and was able to log in as root and force a shutdown, so I may have partial control of the command line.
I haven't tried startx yet because I don't know if X is even running. I doubt it.
Is this another nvidia problem, or possibly related to the GRUB2 boot issue?
Anyone else have this behavior? I'm stuck for now...
I edited the GRUB2 script, removing quiet and splash with no change.
I know the command line is still working, but I am blind, since the display is only showing garbage characters.
If I switch to TTY7, the bottom third of the screen turns blue, so X is running. I still can't see anything since the display is not working.
This machine is working fine running Win10 with no issues....
I seem to have control on the CL by logging in as root and sending various commands, such as halt and reboot. I tried XFdrake and the bottom third went blank, indicating the text (gibberish) had switched to the ncurses.
The only further steps I can think of would be to ssh into the box and poke around, buy I don't know what I am looking for! Why would the graphics be broken before the X session starts?
I don't want to reinstall, but I can handle lots of surgery to get this figured out...
Thanks for any insights