Cannot install on EFI

Questions about SolydX and SolydK installation.
mhoude
Posts: 9
Joined: 29 Nov 2013 22:38

Cannot install on EFI

Postby mhoude » 02 Jul 2017 15:43

Hi,

First I cannot boot the install usb on UEFI, there isn't such an option on the ISO.

I tried multiple times installing SolydK on an EFI system (I created a 512MB fat32 partition for it) and everything installs with no complaint but as soon as it reboots, I'm facing a grub prompt >.

Any ideas on how to install this system on EFI ?

Right now I'm using mint but would rather use SolydK.

Thanks in advance.

Regards.

User avatar
Schoelje
Site Admin
Posts: 8340
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: Cannot install on EFI

Postby Schoelje » 02 Jul 2017 17:08

Simply use dd:

Code: Select all

dd if=path_to_iso of=path_to_usbstick bs=4M && sync


SolydXK needs you!
Development | Testing | Translations

mhoude
Posts: 9
Joined: 29 Nov 2013 22:38

Re: Cannot install on EFI

Postby mhoude » 02 Jul 2017 17:18

I used dd mode from rufus, I guess that wasn't enough. Will try that tonight.

Thanks

mhoude
Posts: 9
Joined: 29 Nov 2013 22:38

Re: Cannot install on EFI

Postby mhoude » 02 Jul 2017 18:59

Used dd and still cannot boot from uefi :(

User avatar
ilu
Posts: 1480
Joined: 09 Oct 2013 12:45

Re: Cannot install on EFI

Postby ilu » 02 Jul 2017 21:11

Without knowing anything about your hardware or the ISO you tried we can't help. Boot the live system and provide details.

simonsaysthis
Posts: 2
Joined: 27 Jun 2017 11:56

Re: Cannot install on EFI

Postby simonsaysthis » 20 Jul 2017 06:04

Hi all,

also having issues getting the USB to boot. Strangely enough it was working with the Beta ISO. Method used: Fedora Media Writer. Will try good old dd now and report back.

Current system

Code: Select all

System:    Host: Fedora Kernel: 4.11.10-300.fc26.x86_64 x86_64 (64 bit gcc: 7.1.1)
           Desktop: KDE Plasma 5.10.1 (Qt 5.7.1) Distro: Fedora release 26 (Twenty Six)
Machine:   Device: laptop System: LENOVO product: 20FAS2P905 v: ThinkPad T460s
           Mobo: LENOVO model: 20FAS2P905 v: SDK0J40705 WIN UEFI: LENOVO v: N1CET57W (1.25 ) date: 05/25/2017
Battery    BAT0: charge: 1.1 Wh 5.2% condition: 21.2/23.5 Wh (90%) model: SMP 00HW023 status: N/A
           BAT1: charge: 6.4 Wh 29.1% condition: 22.0/26.3 Wh (83%) model: SANYO 01AV405 status: Discharging
CPU:       Dual core Intel Core i5-6300U (-HT-MCP-) cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9984
           clock speeds: max: 3000 MHz 1: 500 MHz 2: 499 MHz 3: 485 MHz 4: 476 MHz
Graphics:  Card: Intel HD Graphics 520 bus-ID: 00:02.0
           Display Server: x11 (Fedora X.org 119.3) drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1920x1080@60.00hz
           OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
           version: 4.5 Mesa 17.1.4 Direct Render: Yes
Audio:     Card Intel Sunrise Point-LP HD Audio driver: snd_hda_intel bus-ID: 00:1f.3
           Sound: Advanced Linux Sound Architecture v: k4.11.10-300.fc26.x86_64
Network:   Card-1: Intel Ethernet Connection I219-LM driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6
           IF: enp0s31f6 state: down mac: <filter>
           Card-2: Intel Wireless 8260 driver: iwlwifi bus-ID: 04:00.0
           IF: wlp4s0 state: up mac: <filter>
Drives:    HDD Total Size: 264.1GB (21.5% used)
           ID-1: /dev/sda model: LITEON_L8H size: 256.1GB
           ID-2: USB /dev/sdb model: Flash_Disk size: 8.1GB
Partition: ID-1: / size: 49G used: 8.3G (18%) fs: ext4 dev: /dev/dm-0
           ID-2: /boot size: 976M used: 169M (19%) fs: ext4 dev: /dev/sda2
           ID-3: /home size: 174G used: 36G (22%) fs: ext4 dev: /dev/dm-2
           ID-4: swap-1 size: 10.52GB used: 0.00GB (0%) fs: swap dev: /dev/dm-1
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 37.5C mobo: N/A
           Fan Speeds (in rpm): cpu: 0
Info:      Processes: 197 Uptime: 15 min Memory: 1347.2/19934.7MB Init: systemd runlevel: 5 Gcc sys: 7.1.1
           Client: Shell (bash 4.4.121) inxi: 2.3.23

User avatar
Schoelje
Site Admin
Posts: 8340
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: Cannot install on EFI

Postby Schoelje » 20 Jul 2017 06:32

Try different flash drives. I have about 5 different brands and sizes. Two of them never worked and one stopped working after a few times testing.


SolydXK needs you!
Development | Testing | Translations

User avatar
ilu
Posts: 1480
Joined: 09 Oct 2013 12:45

Re: Cannot install on EFI

Postby ilu » 20 Jul 2017 13:34

I just installed on a Lenovo T440P and couldn't get USB to work. DVD worked immediately though. Ironically, the biggest pain was to install Win7 - I tried 4 different boot ISOs on USB and DVD and it took an old Win7Ultimate to finally get results (which I had to downgrade to pro afterwards). I had to enable CSM (? - that 3-letter-mode for compatibility) but got an EFI install in the end. The Lenovo Bios/Setup is a pita and I'm seriously reconsidering my strangely good opinion of that company.

/rant off

Anyway, try different boot media. Also try DVD, if you have an external one. Try different setup settings (both, UEFI first, CSM on worked for me). And secure boot off. And feel comforted by the idea that you are not alone.

_q_
Posts: 73
Joined: 21 Apr 2014 10:02

Re: Cannot install on EFI

Postby _q_ » 07 Aug 2017 03:54

had similar problems with SolydK9 and Siduction on a Asus laptop...

the solution for me was to actually reformat the boot and root partitions with gparted.

BIOS (or whatever they call it these days) set the same as ilu's.

trying multiple USB sticks did not make a difference, and to make sure, i went back and did it all again with a previously failed USB stick.

fdisking the MBR also failed... as well as synching the dd... they did not hurt, but they didnt do beans.

gparted and just reformat those slices and you should be good to go.

SolydXK is such a delicious flavor of Debian!

User avatar
trinidad
Posts: 21
Joined: 23 Jul 2016 20:59

Re: Cannot install on EFI

Postby trinidad » 08 Aug 2017 23:13

Generally if your Windows system is EFI it is using a GUID partition table for the disk. Some OEM system setup utilities allow you to enable Legacy mode however this can make some Windows installations unbootable afterwards, and you will find yourself having to switch between Legacy and EFI in the bios depending on which system you intend to boot. I'm not particualrly sure why, but Debian has made dealing with some some EFI situations very difficult. The easiest solution to some of these nagging firmware bugs is to install Ubuntu LTS first to such systems. Be sure to always defragment and shrink your Windows partition from Windows first to create unallocted unformatted disk space for future Linux installations.

Install Ubuntu LTS to the free disk space. Use the whole free space. You can repartition afterwards. When Ubuntu boots up download and install grml-rescueboot. Run sudo update-grub. Next download whatever distro ISO you want to install. As root (sudo) move the ISO file from downloads to /boot/grml Run sudo update-grub again. Shut down Ubuntu. Reboot and select your ISO from the grub menu. Install your distro of choice to the HDD from there. If it's MBR (Legacy) *** MAKE SURE to put its grub on its own partition. You do not want to replace the Ubuntu grub. Shut down when complete do not reboot from install. Reboot Ubuntu and run sudo update-grub. Shut down Ubuntu and reboot and select your newly installed distro from the Ubuntu grub menu. This works for many ISOs.

6gig is enough for the Ubuntu partition if you only going to use for this purpose. I have tried this with several other distros and Ubuntu seems to be the only one that sorts this out wihtout a commandline. *grml-rescueboot does not work in Debian 9 this way either even though it generates the correct ISO boot menu.

TC
You can't believe your eyes if your imagination is out of focus.

User avatar
ilu
Posts: 1480
Joined: 09 Oct 2013 12:45

Re: Cannot install on EFI

Postby ilu » 09 Aug 2017 14:04

I can't imagine what kind of magic an Ubuntu system does here and, even if for some reason it's needed for the install, why it should remain on the disk with several places where grub is installed? That just asks for problems if anything happens later on and the user doesn't remember which is which.


Return to “Installation”

Who is online

Users browsing this forum: Milen and 1 guest