Complete these tasks...
select "Ubuntu" environment at the login screen cogwheel
upgrade the BIOS to 313/314 https://www.asus.com/ph/Laptops/ASUS-Vivobook-X556UQ/HelpDesk_BIOS/
memtest from a Ubuntu Live DVD/USB (complete 4/4 passes, if you have the time)
disable the discrete video card, as it's broken (disable the driver, or in the BIOS)
disable wayland, like so...
You may have a problem with an older computer, with an older GPU. Try this...
- boot to recovery mode
- choose root access
sudo mount -o remount,rw / # to remount the disk r/w
sudo pico /etc/gdm3/custom.conf # edit this file
We booted to a Ubuntu Live 18.10 USB, and no problems were seen.
Before upgrading to 18.10, to see if that fixes the problem with the desktop, we should do a
fsck first to check your file system, then you can use
Software Updater to do the upgrade. Of course... having a good backup never hurts... just in case something goes wrong :-)
For 18.04 or newer...
- boot to a Ubuntu Live DVD/USB
- open a
sudo fdisk -l
- identify the /dev/XXXX device name for your "Linux Filesystem"
sudo fsck -f /dev/XXXX # replacing XXXX with the number you found earlier
- repeat the fsck command if there were errors
To eliminate the possibility of bad blocks on your HDD causing your problem, we'll test to find any bad blocks.
First, start the
Disks app, select your HDD, then go to the "hamburger" icon, and select
SMART Data & Tests. Review the data, pay attention to items that include the word "sector". Then run the tests.
Also, lets check syslog for disk errors...
grep -i sda /var/log/syslog*. Copy/paste that output into imgur.com (or paste.ubuntu.com) if they're lengthy.
Note: It's always a good idea to have backup of your important Ubuntu files.
So do this to test for bad blocks... (this may take a while)...
Boot to a Ubuntu Live DVD/USB.
Use the fdisk method from Update #2 to figure out
sudo e2fsck -fcky /dev/sdaX # read-only test
sudo e2fsck -fccky /dev/sdaX # non-destructive read/write test (recommended)
The -k is important, because it saves the previous bad block table, and adds any new bad blocks to that table. Without -k, you loose all of the prior bad block information.
The -fccky parameter...
-f Force checking even if the file system seems clean.
-c This option causes e2fsck to use badblocks(8) program to do a
read-only scan of the device in order to find any bad blocks.
If any bad blocks are found, they are added to the bad block
inode to prevent them from being allocated to a file or direc‐
tory. If this option is specified twice, then the bad block
scan will be done using a non-destructive read-write test.
-k When combined with the -c option, any existing bad blocks in the
bad blocks list are preserved, and any new bad blocks found by
running badblocks(8) will be added to the existing bad blocks
-y Assume an answer of `yes' to all questions; allows e2fsck to be
used non-interactively. This option may not be specified at the
same time as the -n or -p options.
During/after the bad block scan, the drive died. Will require replacement.