Author |
Message |
mikeslr

Joined: 16 Jun 2008 Posts: 3540 Location: 500 seconds from Sol
|
Posted: Fri 25 Mar 2016, 22:10 Post subject:
Booting UEFI/EFI Computers - What Works, What Doesn't |
|
Hi All,
Many of us "old-timers" --myself, in particular-- don't have any computer which requires or even permits booting via UEFI/EFI. But sensing that many new-comers to Puppy would have such computers --and all of us will probably acquire one in the future-- I started this thread http://murga-linux.com/puppy/viewtopic.php?p=858159#858159 in the hope of providing information about how to go about deploying Puppies on them. I chose the Beginner's SubForum as the location most likely to attract the intended audience.
Several different methods were suggested. But It has only today occurred to me that receiving feed-back would be useful. I draw my inspiration from the thread associated with the "Puppy on Laptops" Wiki.
If you have a UEFI/EFI computer please post to this thread what worked. Please be specific giving us the make and model of the computer, the Puppy which you were able to boot, and the technique you employed.
If you have difficulty booting a Puppy specifically built to boot from UEFI/EFI computers, such as FatDog64, please first seek advise on that Puppy's thread, and then post a link here to the discussion there.
Similarly, if you've run into a problem using either noryb009's "Lick", http://murga-linux.com/puppy/viewtopic.php?p=462720#462720 or Ted Dog's "No Format Install", http://murga-linux.com/puppy/viewtopic.php?p=818727#818727 please try to resolve any issues on their respective threads and then post a link to the discussion.
Thanks in advance,
mikesLr
|
Back to top
|
|
 |
James C

Joined: 26 Mar 2009 Posts: 6734 Location: Kentucky
|
Posted: Sat 26 Mar 2016, 01:17 Post subject:
|
|
I have a couple of fairly new desktops with the same UEFI motherboard.
Code: | root# inxi -Fxx
System: Host: puppypc12956 Kernel: 4.1.11 x86_64 (64 bit, gcc: 4.6.4) Desktop: JWM 2.3.4 dm: N/A Distro: tahrpup64 6.0.5
Machine: Mobo: ASUSTeK model: M5A97 LE R2.0 version: Rev 1.xx serial: 150545593600028
Bios: American Megatrends version: 2601 date: 03/24/2015
CPU: Hexa core AMD FX-6300 Six-Core (-MCP-) cache: 12288 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 42158.8
Clock Speeds: 1: 2000.00 MHz 2: 1400.00 MHz 3: 1400.00 MHz 4: 2000.00 MHz 5: 1400.00 MHz 6: 3000.00 MHz
Graphics: Card: NVIDIA GT218 [GeForce 210] bus-ID: 01:00.0 chip-ID: 10de:0a65
X.org: 1.15.1 drivers: nouveau (unloaded: vesa) tty size: 68x23 Advanced Data: N/A for root
Audio: Card-1: NVIDIA High Definition Audio Controller driver: snd_hda_intel bus-ID: 01:00.1 chip-ID: 10de:0be3
Card-2: Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA)
driver: snd_hda_intel bus-ID: 00:14.2 chip-ID: 1002:4383
Sound: Advanced Linux Sound Architecture ver: k4.1.11
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driver: r8169 ver: 2.3LK-NAPI port: d000 bus-ID: 02:00.0 chip-ID: 10ec:8168
IF: eth0 state: up speed: 100 Mbps duplex: full mac: 1c:87:2c:5a:bb:e2
Drives: HDD Total Size: 1120.2GB (6.5% used)
1: id: /dev/sda model: KINGSTON_SV300S3 size: 120.0GB serial: N/A
2: id: /dev/sdb model: WDC_WD10EZEX size: 1000.2GB serial: N/A
Partition: ID: swap-1 size: 8.60GB used: 0.00GB (0%) fs: swap
RAID: System: supported: linear raid0 raid1 raid10 raid6 raid5 raid4
No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Unused Devices: none
Sensors: None detected - is lm-sensors installed and configured?
Info: Processes: 153 Uptime: 22 min Memory: 519.2/15927.3MB Runlevel: 5 Gcc sys: N/A
Client: Shell (bash 4.3.42 running in urxvt) inxi: 1.9.17 |
This box has 6 cores,the other 8.This box is Linux only.
All I did was turn off secure boot in the bios and i can boot anything just as I did on older hardware with the traditional non-UEFI bios.
Windows 7,8 and 8.1 no problem. Every linux distro I/ve tried boots without problem whether installed ,or booted from USB or cd/dvd.( I have Windows 10 downloaded but it sucks so bad I can't make myself install it)
Good old legacy Grub to the mbr booting everything installed.
Have had no problems.
|
Back to top
|
|
 |
bark_bark_bark
Joined: 05 Jun 2012 Posts: 1935 Location: Wisconsin USA
|
Posted: Sat 26 Mar 2016, 07:25 Post subject:
|
|
What works: Disable Secure Boot
What doesn't work: smashing your computer through a window.
_________________ ....
|
Back to top
|
|
 |
BarryK
Puppy Master

Joined: 09 May 2005 Posts: 9083 Location: Perth, Western Australia
|
Posted: Sun 27 Mar 2016, 04:55 Post subject:
|
|
My new Asus Vivobook E200HA baby laptop boots Quirky Linux from USB Flash-stick.
The only thing had to do is disable secure-boot.
I have documented it here:
http://barryk.org/quirky/uefi.htm
Note, the Quirky installer script creates a bootable USB Flash stick that uses Syslinux, and will boot on ye olde MBR BIOS PCs as well as UEFI PCs -- it is a chameleon.
_________________ https://bkhome.org/news/
|
Back to top
|
|
 |
Burn_IT

Joined: 12 Aug 2006 Posts: 3600 Location: Tamworth UK
|
Posted: Sun 27 Mar 2016, 09:18 Post subject:
|
|
Remember Microsoft and Red Hat are pushing to make secure boot compulsory and not able to be turned off.
Since they control the standards it is pretty much a done deal.
_________________ "Just think of it as leaving early to avoid the rush" - T Pratchett
|
Back to top
|
|
 |
gcmartin
Joined: 14 Oct 2005 Posts: 6730 Location: Earth
|
Posted: Mon 28 Mar 2016, 17:43 Post subject:
|
|
Disable secure-boot: Chameleons boot too.
Current PCs which do not/will not upgrade their BIOS/UEFI/EFI will not be affected by future policy changes.
_________________ Get ACTIVE Create Circles; Do those good things which benefit people's needs!
We are all related ... Its time to show that we know this!
3 Different Puppy Search Engines or use DogPile
Last edited by gcmartin on Mon 28 Mar 2016, 18:18; edited 2 times in total
|
Back to top
|
|
 |
Burn_IT

Joined: 12 Aug 2006 Posts: 3600 Location: Tamworth UK
|
Posted: Mon 28 Mar 2016, 17:55 Post subject:
|
|
MS and Red Hat are going to force all machines that use either Windows or Red Hat to NOT have that option.
See:
http://www.pcworld.com/article/2901262/microsoft-tightens-windows-10s-secure-boot-screws-where-does-that-leave-linux.html
_________________ "Just think of it as leaving early to avoid the rush" - T Pratchett
|
Back to top
|
|
 |
mcewanw
Joined: 16 Aug 2007 Posts: 3200
|
Posted: Tue 29 Mar 2016, 17:04 Post subject:
|
|
A few years ago, lots of Linux people were panicking about Secure Boot. However, it doesn't seem to be the nightmare people imagined it would be. I can't myself yet confirm that since I have no Secure Boot capable machine but this guy's informed opinion seems to confirm that it is no big deal really. First he discusses disabling secure boot on machines that allow that, but he also opinions that keeping secure boot enabled is not such a huge issue (particularly for those Linux distributions that provide their own signed keys, which includes Ubuntu):
http://www.rodsbooks.com/efi-bootloaders/secureboot.html
I'm not worried anyway.
William
_________________ github mcewanw
|
Back to top
|
|
 |
cthisbear
Joined: 29 Jan 2006 Posts: 4455 Location: Sydney Australia
|
Posted: Tue 29 Mar 2016, 22:51 Post subject:
|
|
" but this guy's informed opinion seems to confirm that it is no
big deal really. "
Wait until you come onto a HP crapset machine.
Toshiba aren't too hot either.
Stepping on dog doo is enjoyable compared to Microsoft's antics.
Chris.
|
Back to top
|
|
 |
smokey01

Joined: 30 Dec 2006 Posts: 2811 Location: South Australia :-(
|
Posted: Wed 30 Mar 2016, 03:54 Post subject:
|
|
Unfortunately I have a HP probook 4540s which is a pretty good laptop but it does have UEFI. It was a pain to getting it to work with Linux, Fatdog in particular. I had to turn off secure boot.
I have to delve through 5 levels of menus before the UEFI boot manager is displayed. Once I get there I have a nice graphical menus that works but it is a pain to modify. It's just so different to GRUB and Grub4Dos.
Does anyone know how to bypass the first 5 menus and boot straight to the graphics/final menu?
Here is a video I made to explain the problem to Rod Smith previously mentioned in this thread. http://smokey01.com/grant/uefi.mp4 43M
_________________ Software <-> Distros <-> Tips <-> Newsletters
|
Back to top
|
|
 |
ozsouth
Joined: 01 Jan 2010 Posts: 593 Location: S.E Australia
|
Posted: Wed 30 Mar 2016, 20:09 Post subject:
|
|
My 1 yr old HP laptop allows me to disable secure boot, but I can't get any Puppy bootloader to work for dual-boot (likely my inability, but several tries failed). Barry's previous 'Quirky on a stick' booted directly. Wish I could do dual booting (& HDD install) with that. I'm using my 6 yr old win 7 Toshiba laptop which dual boots - HP sits in a cupboard as swapping out the hardrive takes ages.
|
Back to top
|
|
 |
d4p

Joined: 12 Mar 2007 Posts: 436
|
Posted: Wed 30 Mar 2016, 21:28 Post subject:
|
|
You can find some information:
http://rmprepusb.blogspot.com/2015/07/using-easy2boot-with-uefi-only-systems.html
In my experience using Easy2boot on UEFI machine.
You dont need to turn off the secure boot.
Fatdog works fine.
|
Back to top
|
|
 |
mpanek60
Joined: 11 Apr 2015 Posts: 12 Location: california USA
|
Posted: Wed 30 Mar 2016, 23:48 Post subject:
I read today that GPT "sticks"may boot better on UEFI. Subject description: Gparted is capable of doing GPT, |
|
"DebianDog" install deleted a GPT flashstick. Slacko32 install wouldn't install to a GPT stick.
|
Back to top
|
|
 |
mcewanw
Joined: 16 Aug 2007 Posts: 3200
|
Posted: Thu 31 Mar 2016, 06:24 Post subject:
Re: I read today that GPT "sticks"may boot better on UEFI. Subject description: Gparted is capable of doing GPT, |
|
mpanek60 wrote: | "DebianDog" install deleted a GPT flashstick. Slacko32 install wouldn't install to a GPT stick. |
As far as I know it, DebianDog install has only been designed for traditional MBR and not GPT. Assuming I am correct about that, these alternative partition systems (as well as UEFI booting) needs to be looked into in future DebianDog developments. Trouble is, I'm not sure if Fred or Toni have UEFI booting machines available. I don't and can't see me obtaining one in the near future at least.
William
_________________ github mcewanw
|
Back to top
|
|
 |
jamesbond
Joined: 26 Feb 2007 Posts: 3384 Location: The Blue Marble
|
Posted: Thu 31 Mar 2016, 06:49 Post subject:
|
|
No new machines needed. "UEFI" is just firmware, just like BIOS is. Qemu can support both regular BIOS firmware and UEFI firmware. Here's one you can use: http://distro.ibiblio.org/fatdog/source/700/patches/uefi-bios.bin. If you don't trust my copy then get it from the horse's mouth: http://www.tianocore.org/ovmf/ - comes with 32-bit and 64-bit UEFI firmware (64-bit is more common).
If you can't be bothered, just get latest Fatdog64 and its devx. Boot it, and load its devx. You can then emulate UEFI with qemu like this: "qemu-system-x86_64 -enable-kvm -m 1024 -bios uefi-bios.bin -cdrom your-test.iso -vga cirrus".
You can even emulate secure boot if you want to, but it's a bit tedious because you need to do the secure boot setup every time (qemu doesn't support NVRAM so any changes you need will be wiped out as soon as you quit qemu).
EDIT:
If you need EFI bootloaders for testing, I have grub2.efi for both 32-bit and 64-bit UEFI (64-bit UEFI is more common), get it from here: http://distro.ibiblio.org/fatdog/packages/710/grub2-efi32-2.00-i686-1.txz and http://distro.ibiblio.org/fatdog/packages/710/grub2-efi64-2.00-x86_64-1.txz. There are 32-bit and 64-bit syslinux UEFI bootloaders as well from the same place. And of course, when talking about UEFI bootloaders, one must not forget rEFInd (I have refind package too, but you'd probably better off with the official binary from the site). Lots of choices.
_________________ Fatdog64 forum links: Latest version | Contributed packages | ISO builder
|
Back to top
|
|
 |
|