1

I have been trying to get Ubuntu 16.04 to work on my computer alongside Windows 10. I followed the instructions for how to install it (I used the option to "install alongside Windows").

The Problem

The problem is really bizarre: When I first suspended Ubuntu and then tried to start up the computer again, it completely froze and I had to hard-reset the computer. Once I rebooted Ubuntu, it just loops forever with a blank screen and the "Ubuntu drum sound", occasionally blinking the login screen every once in a while.

My Attempts at Fixing it

There is one weird "fix" to this that I figured out; if I boot Windows 10, restart from there, and then choose to boot Ubuntu after the restart, then everything works smoothly. There seems to be something wrong connected to "booting the computer from after being turned off".

Another "fix" I had to do before discovering the above was to reinstall Ubuntu, in which case it works normally until I try to suspend it again.

My Question

Does anyone know what might be causing this? It is rather annoying to have to boot Windows, restart it and boot Ubuntu everytime I want to use it, let alone have to reinstall it.

In case this is helpful: I tried to install to Ubuntu 18.04 instead, but I receive similar problems -- the system breaks after trying to suspend, locking me at login.

Thanks in advance!


Here are the contents of /etc/default/grub:

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
16
  • Have you tried to off secure boot in BIOS settings and fast boot in windows?
    – PRATAP
    Sep 15, 2018 at 15:20
  • I tried it now -- unfortunately it does not work :( Sep 15, 2018 at 15:30
  • When you are in Ubuntu Can you open /etc/default/grub file and show the content?
    – PRATAP
    Sep 15, 2018 at 15:42
  • Added contents of the file in the question now! Sep 15, 2018 at 19:37
  • file seems OK. I think you are never shown with grub rite? Can you check in bios boot menu options if it is showing windows boot manager and Ubuntu?
    – PRATAP
    Sep 15, 2018 at 19:44

1 Answer 1

1

your graphics card might be causing this.

try to enter into ubuntu with "nomodeset"

  1. when you see the grub, highlight to "Ubuntu" and press e to edit the kernal parameters.
  2. go to the line starting with "linux" and find the string ro quiet splash
  3. add the text nomodeset in between "ro quiet splash". now it should look like this ro nomodeset quiet splash
  4. press Ctrl+x or F10 to boot.
  5. Once you enter into Ubuntu.. try to install the rite drivers for your graphics card.

enter image description here

enter image description here

enter image description here

enter image description here

2
  • This worked, but instead of the last step I simply added nomodeset to the string you mentioned in /etc/default/grub and performed sudo update-grub :) thanks! Sep 16, 2018 at 7:52
  • Oh, ok, thats good. some times, booting with nomodeset will make lower resolutions. if you are satisfied after step 4. changing the values permenant via /etc/default/grub is a good idea.
    – PRATAP
    Sep 16, 2018 at 8:01

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .