Nothing on screen after Kubuntu install
 

I have a brand-new HP ProDesk 600 G3 Microtower PC that I wanted to use for Kubuntu 16.04 LTS, but I'm having a strange problem.

The Kubuntu LiveCD ran normally through the installation process. Reboot proceeded normally, with the Kubuntu logo appearing on the screen. But this is where the problem arises: after that, NOTHING ELSE shows up on the monitor screen. It's as if the video signal had been lost, but the monitor doesn't complain about losing the signal: it simply stops showing me anything.

The monitor is a Hannspree HF205 and comes with DVI and VGA ports. The DVI port is in use by a Windows computer without issue. Before this, the VGA port had also been running fine, providing video for another Windows PC (DVI port from a GPU to a DVI-to-VGA adapter, then VGA cable into the monitor).

The ProDesk came with two DisplayPort ports and I bought a Rosewill DP-to-VGA cable to connect into the monitor's VGA port. The computer had FreeDOS installed and everything worked fine, but when I tried to install Kubuntu the process seemed to move forward (the light on the HDD was blinking), except that I couldn't see anything on the screen. So I installed a GeForce GTX 1050 from MSI that comes with DP, HDMI, and DVI ports, then plugged the adapter into the 1050's DP port, and ran through the OS installation process again. The computer POSTs fine (I can get into the startup menu), and I could see everything Kubuntu wanted to show me during installation, but after reboot the display disappears soon after the Kubuntu logo.

I'm hoping that someone with experience with this sort of thing will provide guidance. Thanks in advance.

Terminal
 

Are you able to get to a terminal?

CTRL-ALT-F1

?

Looks like I can, kind of. I hit those keys and reached a login command line. But the display is blinking annoyingly, and the computer won't register what I type while it's blinking.

Separately from login issues, I was going to add the following bit of information: when Kubuntu is in that "no display but monitor live" state, if I press the power button the Kubuntu logo comes back briefly, then at the top of the screen there's some numbers followed by the words "reboot: power down." Hope this helps in tracking down the problem.

nomodeset
 

What type of connection are you using? HDMI, DVI, VGA?

Can you try passing the kernel nomodeset from Grub2?

Something like this..

linux /boot/kernel nomodeset

Another one to try is....

linux /boot/kernel video=800x600

I've tried connecting to the VGA port on the monitor the following ways: 1) onboard DisplayPort (before the GPU was installed); 2) GPU DisplayPort; and 3) GPU DVI.

Since I can't log in due to the blinking display, unfortunately there's no question of entering any commands. I may re-install Kubuntu again just so that I can enter a single-character password, to make it easier to log in.

At some point, I tried loading a Mageia 5 Live CD from Linux Format magazine, to see if that one would display properly. It, too, failed, but this time I got an substantial list of messages. I wanted to attach a screenshot (smartphone photo) in case it helped us to figure out what's going on, but the original picture is 3.7MB and I could only reduce it (even after cropping) down to 355KB, while the maximum file size for attachments here is 256KB.

nomodeset
 

How about nomodeset?

Thanks. At what point in the process would I enter that command?

How To Grub nomodeset
 

Within Grub2

You can edit a menu entry by typing "e"

then look for the line that starts with linux

usually something like this....

linux /boot/vmlinux*****

you need to navigate to that line and at the end of it type "nomodeset"

linux /boot/vmlinux**** nomodeset

Then press F10 to boot into that entry

Let me know how it goes.

What graphics card is present in the computer? I'm aware some computers have issues due to having graphics cards that have ugh support for Linux.

I figured out that I had to keep the ESC key pressed after POST and before the Kubuntu splash screen came up, then I was able to get a "grub>" command prompt.

At that point, though, typing "e" (with or without the quotation marks) just gives an error saying there is no such command. And typing "linux /boot/vmlinux**** nomodeset" followed by the F10 key, didn't do anything.

I am really new at this and am not even sure that I ever reached the Grub menu, all I saw was a notice at the top about the Grub version, some language about minimal BASH, and then the grub> prompt. Nothing about menus, or lines in the Grub configuration file, or how to navigate to them.

Help!!!

Grub2 Manual

https://www.gnu.org/software/grub/manual/grub/grub.html

There are 2 modes in grub.

Command Interface and an edit for the menuentry

When your in the command interface...

try pressing ESC key once.
Then press "e"

That should take you to the editor for the menu entries.

If you get that far, paste all the information from the default menuentry here.

It's a GeForce GTX 1050. If you need the info, the first post up above has a link to the exact model I bought.

But note that I was having the problem even before the graphics card went into the computer. In fact, the reason I put it in is that I already wasn't getting any display off the Live CD past the "Try Kubuntu" screen.

I'm wondering if the issue has to do with this DisplayPort stuff, the computer came with two of them and no other kind. Since the graphics card has not only a DP port but also DVI and HDMI, my next move will be to try connecting the computer to the monitor via an HDMI-to-VGA adapter.

Thanks for the manual, I'll check it out.

Pressing ESC behaved like the Enter key: it went to a new "grub>" line before I got to do anything else like typing "e". I tried keeping ESC pressed, but that just gives me more new blank grub> lines, exactly as if I kept hitting Enter.

Please paste a picture if you can.

Reading around the Grub manual, I saw this:

>>GRUB looks for its configuration file as soon as it is loaded. If one is found, then the full menu interface is activated using whatever entries were found in the file. If you choose the command-line menu option, or if the configuration file was not found, then GRUB drops to the command-line interface. <<

So I'm thinking that there may just not be a configuration file present, since I'm not getting an option to choose between command-line or menu interface, it's taking me directly to the CL.

hmmm

you don't get anything to choose from initially?

what does "ls" return

This is directly from grub manual.

-- Command: ls [arg ...]
List devices or files.

With no arguments, print all devices known to GRUB.

Thanks, here's the output from ls:

(hd0) (hd0,gpt3) (hd0,gpt2) (hd0,gpt1) (cd0) error: failure reading sector 0x0 from `cd0'.

ADDED: I forgot to answer your question. Nope, there's nothing to choose from initially.

set command
 

Please type "set" and post the result of that command.

Command: set [envvar=value]

Set the environment variable ENVVAR to VALUE. If invoked with no
arguments, print all environment variables with their values.

You should normally be able to bring up the Grub menu by holding shift when booting the computer. If that works, try selecting Advanced and selecting the kernel with "(Recovery)" at the end and see if that boots with picture.
Sometimes there are issues with Nvidia drivers that cause a problem like your describing. Booting with Recovery option should make it boot with nouveau drivers instead

It was rather laborious as the PC where I'm typing this is on the same monitor and I had to keep switching the display source. But here goes. After entering
and hitting Enter, next I typed "set" followed by Enter again and got the following:

please run this and post

ls /boot/grub

The "grub.cfg" file should be in this path.

When researching how to get into the Grub menu, the Web told me it could be the Shift key, the Space key, or the Escape key. On the first two bootup tries, Shift or Space didn't seem to do anything. But pressing Escape finally took me to the Grub prompt (and nothing else, unfortunately).

Note that I was having the same sort of problem even before installing the GTX 1050, when the computer was relying on the integrated graphics.

Here's what it gave me:

type

configfile /boot/grub/grub.cfg

what happens?

It should bring up some menu entries.
Please post what it brings up.

If it does bring up menu entries.

press "e"

That should take you to the commands in that menuentry.

Then you can find the command "linux"

Curious to see what happens.

Huh -- when I typed that in and hit Enter, the screen went dark, then the Kubuntu logo appeared, and then the screen went blank again. This is exactly what happens when I'm trying to boot the normal way into Kubuntu. (I suspect it IS actually booting properly, just not displaying anything. But of course I could be wrong.)

please type

terminal_output

post the result please

Idk if Kubuntu enables ssh by default or not but you could try ssh just to see if it's booted properly or not

Before continuing, I want to add that I just noticed that when the screen goes what I've been calling "black" or "blank," is not totally black as if the monitor were turned off. If I switch the lights off in the room, you can see a slight glow coming off the "black" screen.

Now on to the results of terminal_output:

Thanks, can I do that from Grub? It's the only spot where I get to see and do anything.

lets try something else first

set gfxmode=800x600
save_env gfxmode

set timeout=10
save_env timeout

then reboot and tell me if the screen resolution is different

The screen resolution seems to be unchanged, but now if I time right hitting the Escape key I can get into what looks like a Grub menu. It's inside a solid square going around the edges of the screen.

I had actually seen something like this before (before we started all this troubleshooting), but I did not realize that it was the Grub menu. Or at least, if it wasn't a Grub menu, then at least it looked very similar.

However, and FWIW, whereas before the first option on the menu used to be "Kubuntu", now the first option is "Ubuntu". The other options also seem to be different. I can't remember what the middle option used to be, but the third option used to be something like "system diagnostics" or something like that. Now, the last two options on the menu are "Advanced options for Ubuntu" and "System setup". Weird, not sure what would have made the options change.

ADDED: I missed the new part about the additional settings. I'll enter them and put up a new post.

Wow
The timeout was set to not display the menu entries.
At least now you see them.

Press "e"

To edit a menu entry

Please post the commands from the highlighted menuentry.

OK, adding the timeout setting didn't make a visible difference, at least at this stage.

Grub is sourcing the file "grub.cfg"

That file has commands to display menu entries.

If the timeout is not set to a number of seconds. Then you don't see the menu entries.

It sounds to me that now you can see them and now you need to press "e" to edit an entry.

Special Note, editing a menuentry cannot be saved here. You can only edit it and then boot by pressing "F10" after you edit the entry.

Please post all the commands from the highlighted menuentry.

OK, I got "e" to work. I'm assuming that I should be doing that for the Ubuntu (top) line and not one of the other two lines. Here's the output:

recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hdo,gpt2 --hint-baremetal=ahci0,gpt2 \{what looks like a key of some sort; not sure if it's safe to post}
else
search --no-floppy --fs-uuid --set=root {same alphanumerical sequence as above}
fi
linux /boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID={same alphanumeric sequence as above} ro quiet \splash $vt_handoff
initrd /boot/initrd.img-4.4.0-31-generic

edit the linux command line to the following and then press "f10"

linux /boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID={same alphanumeric sequence as above} ro \splash $vt_handoff nomodeset

I can see the menu entries if I press Escape at the right moment, otherwise it proceeds to loading Kubuntu into the blank screen, or if I keep it pressed too long then it goes into the Grub command prompt.

Wow -- it worked!!! :party:

I reached the Kubuntu login screen. Hallelujah!!

Given the changes we've made, are there any limitations I should take into account with respect to the display (resolution, etc.)? How about when rebooting, next time I launch Kubuntu?

Thank you so much! :hattip:

Not really limitations. The problem here is the following below.


nomodeset

The newest kernels have moved the video mode setting into the kernel. So all the programming of the hardware specific clock rates and registers on the video card happen in the kernel rather than in the X driver when the X server starts.. This makes it possible to have high resolution nice looking splash (boot) screens and flicker free transitions from boot splash to login screen. Unfortunately, on some cards this doesnt work properly and you end up with a black screen. Adding the nomodeset parameter instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded.

You can edit the file....

/etc/default/grub

The line is...

GRUB_CMDLINE_LINUX_DEFAULT=""

edit this to

GRUB_CMDLINE_LINUX_DEFAULT="nomodeset"

Then run...

update-grub

There are still things you probably need to do to configure your video card.

Please post the result of "lspci"

lspci

The grub2 manual explains most of this stuff.
I have been going through it page by page and really trying to understand how grub2 works.
Thanks for taking the time to respond.

Let me know how things are going.

Great. Four questions:

1) That line you mentioned...

GRUB_CMDLINE_LINUX_DEFAULT=""

Currently reads as follows:

Should I remove the "quiet splash" altogether and replace it with "nomodeset"?

2) Also, the line just below that is currently:

Should I leave that line untouched?

And,

3) The resolution right now looks pretty low (big, fuzzy characters). Can I change it without risking a return to the black screen, and if so, can I change the resolution via the Kubuntu desktop (in Kate)?

4) Finally, should I run "lspci" from the Grub menu like we did the "set timeout" and "set gfxmode", or from somewhere else?

Thanks again.

Answer to 1

What "quiet" does

Disable most log messages

What "splash" does

Displays a Splash screen

What "nomodeset" does

Disables the kernel from setting up the driver at this stage

I would suggest you use "splash nomodeset"

Leaving "quiet" as a parameter being passed is fine too. I personally like to see the other messages.

Answer to 2

You can leave this untouched.

/etc/default/grub file is getting sourced by another script to setup the proper /boot/grub/grub.cfg file.

You need to edit the changes in "/etc/default/grub", then run "update-grub"

Answer to 3

Yes try changing the resolution within Kubuntu. I do not know what display control panel Kubuntu has.
I used Debian 9 currently on most of my systems.

I was just wanting to verify what video card you have.

What "lspci" does

lspci - list all PCI devices

Check out more details with "man lspci"

grub2 has several commands available to it in command mode for gathering information

kubuntu also has this same command

It is just listing your PCI devices.

Answer to 4

grub2 has many variables that can be "set" and "unset"

You can type "set" to see the current variables and what there values are withing grub2 command line mode.

The commands that grub2 offers is documented in their manual.

Note:

try installing "info" in Kubuntu

then type "info grub"

I find it a neat way to read manuals with "info" program. Once you get used to the hotkeys, you can zip around and get information quickly. :)

Request:

Please post your "lspci" and "lsmod"

I am curious to see what video module is running in your setup. I have a suspicion that is is nouveau.

One thing at a time, but I think the nvidia driver is much better to get full use out of your graphics card, assuming it is nvidia. I just like verifying it with the outputs of "lspci"

"Info"I greatly appreciate your taking the time to provide all this information. It's been a real learning experience.

Here's the output for lspci:


And here's the output from lsmod:
ADDED: You suggested that I install Info to make it easier to read manuals. Looks like it was already installed, as the Synaptic Package Manager only give an option to "mark for reinstallation" while the "mark for installation" option is grayed out. So I tried it in the Konsole terminal (info grub as you suggested), and it worked. Pretty cool.

00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated Graphics (rev
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c81 (rev a1)

You have 2 graphics cards?

How many displays do you currently have connected?
What type of connection? vga, dvi, hdmi, display port?

I am guessing your connected to one of the nvidia video ports.

nouveau module is what is being used for the nvidia card.

BinaryDriverHowto Nvidia
 

https://help.ubuntu.com/community/Bi...erHowto/Nvidia

Here is the steps to get Nvidia drivers working.

There's the integrated graphics from Intel that came with the PC, and then there's also the GTX 1050 that I put in.

The computer came with two DisplayPort ports, while the 1050 has DVI, HDMI, and DisplayPort (one of each). Right now the monitor (there's only one) is connected via the 1050's DP port. I'm using a DP-to-VGA cable to connect the 1050 to the monitor's VGA port.

Looks like I may have to do the manual driver installation, as I'm not getting the automated notice about drivers being available.

In addition, Kubuntu's System Settings > Driver Manager doesn't list anything at all (claims to be collecting info but never actually shows anything), and neither the Update Manager nor the Synaptic Package Manager seem to show anything related to NVIDIA.

curious

Can you plug it into the onboard video card and boot up?

Curious to see the result.

This is an older version of Kubuntu.

Are you set on this version?

This is going to be my work computer (making the switch from Windows), so I'd rather it were the LTS version instead of one of those that quickly stops getting updates.

Funny thing is, I used the same Kubuntu Live CD (with the same version of course) to install on an SSD for an old HP laptop, and it worked fine. I also used the same CD to install Kubuntu on another older PC that already had XP and Vista on it (triple-booting). In neither of those cases (both of them earlier this year) was there any problem at all, certainly nothing like what I've been going through with this brand-new machine. So I had no reason to think that things would go any different this time. Grrr!!! :banghead:

The computer is currently downloading Kubuntu updates. I'll try that first chance I get.

In Windows, my understanding is that if there's a discrete GPU then the onboard graphics are disabled. But we'll try it and see what happens.