Nothing on screen after Kubuntu install

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

Quote:

Originally Posted by batman23

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.

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

Quote:

Originally Posted by Rodrigo7

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.

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.

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

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

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

Quote:

Originally Posted by Rodrigo7

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.

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

Quote:

Originally Posted by batman23

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, 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

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

Quote:

Originally Posted by Rodrigo7

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

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

Quote:

Originally Posted by batman23

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.

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.

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

Wow -- it worked!!!

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!

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

Quote:

Originally Posted by Rodrigo7

Wow -- it worked!!!

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!

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.

Rodrigo7 · 11-17-2017, 10:38 PM

Great. Four questions:

1) That line you mentioned...

GRUB_CMDLINE_LINUX_DEFAULT=""

Currently reads as follows:

Quote:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

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

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

Quote:

GRUB_CMDLINE_LINUX=""

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.

batman23 · 11-18-2017, 06:25 AM

Quote:

Originally Posted by Rodrigo7

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"

Rodrigo7 · 11-18-2017, 10:11 AM

"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:

Code:

00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Sky Lake PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated Graphics (rev 06)
00:14.0 USB controller: Intel Corporation Device a2af
00:14.2 Signal processing controller: Intel Corporation device a2b1
00:16.0 Communication controller: Intel Corporation Device a2ba
00:16.3 Serial controller: Intel Corporation Device a2bd
00:17.0 SATA controller: Intel Corporation Device a282
00:1c.0 PCI bridge: Intel Corporation Device a296 (rev f0)
00:1f.0 ISA bridge: Inel Corporation Device a2c6
00:1f.2 Memory controller: Intel Corporation Device a2a1
00:1f.3 Audio device: Intel Corporation Device a2f0
00:1f.4 SMBus: Intel Corporation Device a2a3
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-LM
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c81 (rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 0fb9 (rev a1)
02:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)

And here's the output from lsmod:

Code:

Module                  Size  Used by
uas                    24576  0
usb_storage            69632  2 uas
btrfs                 987136  0
xor                    24576  1 btrfs
raid6_pq              102400  1 btrfs
ufs                    73728  0
qnx4                   16384  0
hfsplus               106496  0
hfs                    57344  0
minix                  36864  0
ntfs                   98304  0
msdos                  20480  0
jfs                   180224  0
xfs                   970752  0
libcrc32c              16384  1 xfs
hp_wmi                 16384  0
sparse_keymap          16384  1 hp_wmi
intel_rapl             20480  0
x86_pkg_temp_thermal    16384  0
intel_powerclamp       16384  0
coretemp               16384  0
kvm                   536576  0
nls_iso8859_1          16384  1
irqbypass              16384  1 kvm
crct10dif_pclmul       16384  0
crc32_pclmul           16384  0
aesni_intel           167936  0
aes_x86_64             20480  1 aesni_intel
lrw                    16384  1 aesni_intel
gf128mul               16384  1 lrw
glue_helper            16384  1 aesni_intel
ablk_helper            16384  1 aesni_intel
snd_hda_codec_hdmi     53248  2
cryptd                 20480  2 aesni_intel,ablk_helper
snd_hda_codec_conexant    24576  1
snd_hda_codec_generic    77824  1 snd_hda_codec_conexant
serio_raw              16384  0
snd_hda_intel          36864  5
snd_hda_codec         135168  4 snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_codec_generic,snd_hda_intel
snd_hda_core           73728  5 snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
snd_hwdep              16384  1 snd_hda_codec
snd_pcm               106496  4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_core
snd_seq_midi           16384  0
snd_seq_midi_event     16384  1 snd_seq_midi
input_leds             16384  0
joydev                 20480  0
snd_rawmidi            32768  1 snd_seq_midi
snd_seq                69632  2 snd_seq_midi_event,snd_seq_midi
snd_seq_device         16384  3 snd_seq,snd_rawmidi,snd_seq_midi
snd_timer              32768  2 snd_pcm,snd_seq
snd                    81920  21 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,snd_seq_device
soundcore              16384  1 snd
8250_fintek            16384  0
acpi_pad               20480  0
mac_hid                16384  0
shpchp                 36864  0
parport_pc             32768  0
ppdev                  20480  0
lp                     20480  0
parport                49152  3 lp,ppdev,parport_pc
autofs4                40960  2
hid_generic            16384  0
usbhid                 49152  0
hid                   118784  2 hid_generic,usbhid
psmouse               126976  0
nouveau              1495040  0
i915_bpo             1261568  0
igb                   196608  0
mxm_wmi                16384  1 nouveau
intel_ips              20480  1 i915_bpo
dca                    16384  1 igb
ttm                    94208  1 nouveau
ptp                    20480  1 igb
pps_core               20480  1 ptp
drm_kms_helper        147456  2 i915_bpo,nouveau
i2c_algo_bit           16384  3 igb,i915_bpo,nouveau
syscopyarea            16384  1 drm_kms_helper
ahci                   36864  3
sysfillrect            16384  1 drm_kms_helper
sysimgblt              16384  1 drm_kms_helper
libahci                32768  1 ahci
fb_sys_fops            16384  1 drm_kms_helper
drm                   360448  4 ttm,i915_bpo,drm_kms_helper,nouveau
wmi                    20480  3 hp_wmi,mxm_wmi,nouveau
video                  40960  2 i915_bpo,nouveau
fjes                   28672  0

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.

batman23 · 11-18-2017, 10:58 AM

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.

batman23 · 11-18-2017, 11:02 AM

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

Here is the steps to get Nvidia drivers working.

Rodrigo7 · 11-18-2017, 11:28 AM

Quote:

Originally Posted by batman23

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.

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.