Unsolved

This post is more than 5 years old

5 Posts

9680

July 30th, 2018 10:00

G7

No G7 sub threads to post within. Please move to proper section.

 

Bought a G7 two days ago and tried to install ubuntu 18.04.1. There were issues. Followed community posts for initializing to nvme and xps uefi installations. Installer failed to find the installed windows system despite following these tutorials. Bios was set to ahci and I tried to force an install several times using both gpt and dos style partition tables. Installer thinks its a bios based system based on dmesg | grep as well as one other method. Tried installing boot-repair after install to clean up the boot issue (grub-install failed on both sda and sdb. Curiously the ssd shows as /dev/sdb each time. Even after installing and running boot-repair from yannubuntu ppa it fails to install grub in a way that puts shimx64.efi in to the FSO. I should mention that while windows was installed I ran the dell bios update and I am on the most current as of this post.

 

So then I downloaded the usb os recovery tool from dell and tried three times to restore what it came with for windows installation. The os-recovery usb did its job but it installed windows to the 5400rpm 1tb drive each time. On the last try I even went in and pre formatted the disk back to all ntfs before running the recovery tool but it still mis allocated the partitions.

 

So Dell I am looking for two things. A way to recover this computer that sets it back to how it came. OS-recovery needs work for this to happen. Also we need a bios update for this laptop. This laptop received certification from ubuntu but I think it was determined by running the live os and not installing it. Ubuntu fails to see the installed system even with "load_nvme=YES" on the boot line. Grub fails to install to /dev/sda and /dev/sdb in either gpt or dos partition tables and with both raid and ahci set in bios. Yannubuntu/boot-repair - boot-repair indicates that the computer is uefi based but bootloader is dos assumed. It did a lot of work with boot-sav while it was mounted and it had me make an ESP directory but this also did not work. Possibly someone can take on a personal project and see if they can get further than I and report back on how they did? I think that the os-recovery and the ubuntu installer not doing their jobs correctly may be the same issue within the existing bios.

9 Legend

 • 

33.4K Posts

July 31st, 2018 06:00

5 Posts

July 31st, 2018 11:00

Thank you for the link. I followed three of those. One on basic Ubuntu, another describing efi installation exampling the xps and one more on a precision with raid. My report was to indicate while those have useful data it's still not possible. Hinting that their own recovery took (os-recovery) failed to install windows to the correct dive. I think that these issues are related to the fact that we can't set hard drive order in bios. That and there is no way for Ubuntu to see that itsaefi based machine. The Ubuntu installer assumed this laptop to be bios based even when booting with load_nvme=YES. Yes, I've seen all the documentation but on this particular laptop they do not apply. 

5 Posts

August 7th, 2018 19:00

Original post: here

 

This is how I did it:

 

To install Ubuntu...

Had to set the bios to the standard plus one. Get a Ubuntu USB installer plugged in and get in to bios.

Make sure safe boot is off as well as tpm. Bios check I set to audit mode. We need to have legacy roms and enabled boot to legacy... Enabled or checked. Last normal bios setting is to make sure that raid is off and ahci is on.

With an ubuntu usb plugged in, make a new boot entry in the boot settings. Call it UbuntuUSBInstall or what you want and in file field aim to the /efi/boot/grubx64.efi file. Save and let it boot to usb via efi. Just to be sure hit f12 as it's booting and look for UbuntuUSBInstall or what you named the boot entry.

You should see what looks like and old grub prompt with three lines. Leave selected the line for try Ubuntu. Hit E for edit boot line. Find kernel line (starts with linux) in grub entry and add "nomodeset" without quotes. I added just before quiet. Hit f10 to boot.

Once in Ubuntu live open a terminal and cd in to /sys/firmware/efi/efivars and see if you have any efivars files. If you do then Ubuntu "probably" booted properly and sees the system as efi based. All my past attempts failed as it prob hit the wrong boot file and defaulted to legacy boot from installer USB. I say probably on seeing efivars files as this is not a guaranteed method. Please Consult Ubuntu forums for checking if efi boot took place.

I was going to try to dual boot to test but installer wanted 5400 rpm drive and would not let me select ssd. That being said the ssd was available for taking the whole disk so that is what I did. I just completed the installation taking the whole disk and on reboot I went in to look at boot entries. It set itself up well. The shimx64.efi file that ubuntu uses was in as the only available boot option as internal.

So in summary by setting bios as we should and adding a boot entry aiming at grubx64 I was able to boot the system to the Ubuntu 18.04.1 installer in a way that let it see my G7 as efi based and the installer worked wonderfully.

Before doing this I highly recommend installing virtualbox on windows and taking a vdi image of your ssd. Google around for taking physical to vdi on virtualbox. I don't have the tutorial handy but I remember changing directory in to c:\programfiles\virtualbox and using a command prompt to issue an internal command that called \physicaldisk\0 and in order for it to work right I had to change the 0 to a 1 so it imaged the second hard disk and not the first. If you get that far you WI need to have a windows 10 install iso handy. Add this iso as another hard disk on your virtual machine settings and set your vdi of your ssd as the second drive in order. As windows is booting to the installer press f6 and get in to a prompt or command terminal through safe mode. Going from memory but we need to fix the mbr... Select repair my computer and repair boot. Manual method from terminal would be bootrec.exe /fixmbr. Def double check me on this. Idea being is that we just moved the operating system off of physical metal and it probably won't boot until we fix the boot record from within virtualbox. This allows us to keep windows as a file on the 1tb drive (if wanted) and run it inside a virtual machine. We paid for it! Might as well keep it. We can later change a vdi to a vhd and restore windows if needed. Finding a tutorial on this may be key as there are more settings that I am failing to recall that one needs to set in the machine settings to get windows to boot.

That should let your windows ten boot properly in a virtual environment. Now on to Nvidia, setting up prime for on the fly gpu switching and adjusting fstab to include the 1tb drive and of course game installation. Please let me know if I **bleep** anything up in this post and I'll fix. If anyone needs help doing the rest let me know and I'll hop on a pc and do a better job formatting the steps.

5 Posts

August 7th, 2018 19:00

https://www.reddit.com/r/linuxquestions/comments/91rzc1/installing_linux_on_a_dell_g7/

 

Solution. Now running Ubuntu on my G7 and windows 10 that came installed from a virtual machine within.

April 19th, 2019 16:00

I also with a G7 7588 with Ubuntu 16.04LTS, I had problems after upgrading to 18.04LTS and when I tried to use Factory Recovery it tried to install Windows. Now I also can not install Ubuntu 16.04 without locking the machine

9 Legend

 • 

47K Posts

April 23rd, 2019 06:00

18.04.2 and latest bios and I have no issues.

I still recommend installing ALONGSIDE windows rather than clean install.

https://certification.ubuntu.com/hardware/201801-26082/

 

http://releases.ubuntu.com/18.04/ubuntu-18.04.2-desktop-amd64.iso

 

Hardware summary

This system was tested with these key components:

Processor

Intel Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz

Video

nVidia GP106M [GeForce GTX 1060]

Intel UHD Graphics 630 (Mobile)

Ethernet

Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller

Wireless

Qualcomm Atheros Killer N1525 Wireless-AC

Hardware details

Audio

Intel Cannon Lake PCH cAVS

Intel Unknown

Bluetooth

Atheros Communications 0cf3:e007

Disk

Toshiba America Info Systems nvme0n1

ST1000LX015-1U7172

Keyboard

AT Translated Set 2 keyboard

Network

Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller

Processor

Intel Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz

Touchpad

DELL0825:00 06CB:7E92 Touchpad

Usb

Intel Cannon Lake PCH USB 3.1 xHCI Host Controller

Video

nVidia GP106M [GeForce GTX 1060]

Intel UHD Graphics 630 (Mobile)

Wireless

Qualcomm Atheros Killer N1525 Wireless-AC

Other

Dell WMI hotkeys

HDA Intel PCH HDMI/DP,pcm=10

HDA Intel PCH HDMI/DP,pcm=3

HDA Intel PCH HDMI/DP,pcm=7

HDA Intel PCH HDMI/DP,pcm=8

HDA Intel PCH HDMI/DP,pcm=9

HDA Intel PCH Headphone Mic

Intel HID 5 button array

Intel HID events

Lid Switch

Power Button

Sleep Button

Video Bus

Intel nvme0

Intel Sky Lake PCIe Controller (x16)

Intel Skylake Processor Thermal Subsystem

Intel Sky Lake Gaussian Mixture Model

Intel Unknown

Linux Foundation 2.0 root hub

Linux Foundation 3.0 root hub

Aquantia Corp. 27c6:5381

 

No Events found!

Top