Nothing on screen after Kubuntu install

batman23 · 11-17-2017, 11:31 AM

Quote:

Originally Posted by Rodrigo7

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.

Rodrigo7 · 11-17-2017, 12:03 PM

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.

batman23 · 11-17-2017, 12:38 PM

Quote:

Originally Posted by Rodrigo7

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.

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.

TheEzekielProject · 11-17-2017, 03:33 PM

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

Rodrigo7 · 11-17-2017, 05:32 PM

Quote:

Originally Posted by batman23

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.

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

Code:

set envvar=value

and hitting Enter, next I typed "set" followed by Enter again and got the following:

Code:

grub> set
?=0
cmdpath=(hd0,gpt1)/EFI/ubuntu
color_highlight=black/light-gray
color_normal=light-gray/black
envvar=value
feature_200_final=y
feature_all_video_module=y
feature_chainloader_bpb=y
feature_default_font_path=y
feature_menuentry_id=y
feature_menuentry_options=y
feature_nativedisk_cmd=y
feature_ntldr=y
feature_platform_search_hint=y
feature_timeout_style=y
grub_cpu=x86_64
grub_platform=efi
lang=
locale_dir=
net_default_ip=(null)
net_default_mac=(null)
net_default_server=
pager=
prefix=(hd0,gpt2)/boot/grub
pxe_default_server=
root=hd0,gpt2
secondary_locale_dir=
grub>

batman23 · 11-17-2017, 05:35 PM

Quote:

Originally Posted by Rodrigo7

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

Code:

set envvar=value

and hitting Enter, next I typed "set" followed by Enter again and got the following:

You do not need to run this.
This is just how to set a variable with the set command.
The main thing was to see what the variables are currently set at.
This is what you posted with typing "set"

Code:

grub> set
?=0
cmdpath=(hd0,gpt1)/EFI/ubuntu
color_highlight=black/light-gray
color_normal=light-gray/black
envvar=value
feature_200_final=y
feature_all_video_module=y
feature_chainloader_bpb=y
feature_default_font_path=y
feature_menuentry_id=y
feature_menuentry_options=y
feature_nativedisk_cmd=y
feature_ntldr=y
feature_platform_search_hint=y
feature_timeout_style=y
grub_cpu=x86_64
grub_platform=efi
lang=
locale_dir=
net_default_ip=(null)
net_default_mac=(null)
net_default_server=
pager=
prefix=(hd0,gpt2)/boot/grub
pxe_default_server=
root=hd0,gpt2
secondary_locale_dir=
grub>

please run this and post

ls /boot/grub

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

Rodrigo7 · 11-17-2017, 05:37 PM

Quote:

Originally Posted by TheEzekielProject

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

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.

Rodrigo7 · 11-17-2017, 05:41 PM

Quote:

Originally Posted by batman23

please run this and post

ls /boot/grub

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

Here's what it gave me:

Code:

x86_64-efi/ unicode.pf2 locale/ fonts/ grubenv grub.cfg

batman23 · 11-17-2017, 05:44 PM

Quote:

Originally Posted by Rodrigo7

Here's what it gave me:

Code:

x86_64-efi/ unicode.pf2 locale/ fonts/ grubenv grub.cfg

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.

Rodrigo7 · 11-17-2017, 05:51 PM

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.)

batman23 · 11-17-2017, 05:52 PM

Quote:

Originally Posted by Rodrigo7

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

TheEzekielProject · 11-17-2017, 05:55 PM

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

Rodrigo7 · 11-17-2017, 05:59 PM

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:

Quote:

Active output terminals:
gfxterm
Available output terminals:
console spkmodem serial_* serial cbmemc audio
grub>

Rodrigo7 · 11-17-2017, 06:00 PM

Quote:

Originally Posted by TheEzekielProject

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

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

batman23 · 11-17-2017, 06:02 PM

Quote:

Originally Posted by Rodrigo7

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:

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