(old)Puppy Linux Discussion Forum

jamesbond wrote:No new machines needed. "UEFI" is just firmware, just like BIOS is. Qemu can support both regular BIOS firmware and UEFI firmware.

That's interesting. Never thought of using Qemu to test UEFI (would certainly be interested to try Secure Boot too).

William

jamesbond how do you release the mouse Grab bollocks. If I press Ctrl+Alt+G it only releases it until I click on the desktop then I have to repeat the procedure.

TIA

I have reported this (several times) before and I will report again: Running FATDOG as the PC's distro, if anyone starts a Virtual Machine (VM) running the FATDOG distro, you will notice that the distro runs much faster than the main FD7.

Try it yourself for observation using the command that @JamesBond shows earlier; namely Of course, you can boot any compliant ISO not just FD7.

For Non-EFI (BIOS) VM Guests this works Cheers

smokey01 wrote:jamesbond how do you release the mouse Grab bollocks. If I press Ctrl+Alt+G it only releases it until I click on the desktop then I have to repeat the procedure.

You can't. But you can simplify that if you add the "-sdl" parameter - then you only need to press Ctrl+Alt to release the grab.

Puppylinux blog has an interesting entry about UEFI: http://blog.puppylinux.com/?viewDetailed=00009

Hi @JamesBond. Should "step 6" read?

• - mkdir -p /EFI/boot

The process shows, there, is clear, IMHO.

Thanks for the heads-up.

Cheers!

Thanks, jamesbond. It's nice that your EFI bootloader solution can be simply added to a standard BIOS puppy USB stick so it will boot on BIOS or UEFI. Adding EFI doesn't change the stick's MBR, so it still boots normally on a BIOS computer.

It works for me booting Precise puppy on a Dell Optiplex 3020 with UEFI.

For my more complicated multiboot USB stick with a syslinux bootloader, I added the rEFInd bootloader that provides a menu to select a legacy bootloader (described here). That allows using the existing syslinux multiboot menu on a EFI computer, as long as it has CSM enabled. I couldn't manage figuring out how to convert the complicated syslinux.cfg items to grub.cfg.

cimarron wrote:Thanks, jamesbond. It's nice that your EFI bootloader solution can be simply added to a standard BIOS puppy USB stick so it will boot on BIOS or UEFI. Adding EFI doesn't change the stick's MBR, so it still boots normally on a BIOS computer.

Yes, thank you for mentioning that: a point I forgot to say, that aside from being UEFI simple, it will not affect / change existing solutions for BIOS systems too.

It works for me booting Precise puppy on a Dell Optiplex 3020 with UEFI.

Thank you for the confirmation.

For my more complicated multiboot USB stick with a syslinux bootloader, I added the rEFInd bootloader that provides a menu to select a legacy bootloader (described here). That allows using the existing syslinux multiboot menu on a EFI computer, as long as it has CSM enabled. I couldn't manage figuring out how to convert the complicated syslinux.cfg items to grub.cfg.

rEFInd is nice. And yes Fatdog also uses rEFInd too. The blog post is a start, once people are familiar with UEFI boot process, they can proceed to use other, more featured bootloaders like rEFInd (or any other combination). I'm not sure if grub2 EFI can chainload to legacy bootloader, I never tested that because the Qemu UEFI BIOS doesn't have CSM.

My hope is that the post will bring an avalanche of UEFI-enabled Puppies in near future.

Slacko64 with UEFI support now testing: http://murga-linux.com/puppy/viewtopic.php?t=106337

jamesbond wrote:Slacko64 with UEFI support now testing: http://murga-linux.com/puppy/viewtopic.php?t=106337

Originally was 64 only but 32 bit is now also available.

Are there any modern boards still being manufactured that don't use UEFI ??

zakjoh wrote:Are there any modern boards still being manufactured that don't use UEFI ??

I wish.

zakjoh wrote:Are there any modern boards still being manufactured that don't use UEFI ??

I think that generic motherboards with a BIOS from Phoenix Technologies (American Megatrends or Award) will work in either mode. The issue here is: how to use Puppy without reformatting a drive that is already using UEFI, and also the case of a proprietary BIOS in some laptops.

In principle an IBM BIOS should be able to boot an MBR partition or a GPT partition. The same applies to a UEFI BIOS. In practice the BIOS setup screen doesn't give you the option

With my ASRock Intel Braswell N3150 motherboard, that I bought in November, I partitioned the new SSD with MBR and there was no need to mess about with UEFI and it worked exactly like motherboards have for decades.

The only noticeable difference comes with SATA. There isn't the same fixed relationship between drive letter and connectors that there used to be with IDE drives.

Without checking further into what steve actually does this quote sounds interesting to me?

Could be worth a look!

rmprep wrote:You may find that some ISOs that do not contain UEFI
boot files (\EFI\boot\bootx64.efi and bootia32.efi) will still boot via the
grub2 menu system!

Read more: http://www.easy2boot.com/uefi-grub2-ptn2/

rmprep wrote:By adding a special FAT32 .imgPTN partition image file
containg grub2 to the E2B USB drive, it is possible to UEFI-boot directly from
many linux ISOs and .EFI boot files (such as Memtest and KonBoot EFI files)
all from one menu system (no need to reboot and load a different .imgPTN
file each time!).

Hi, instead of going into details again of what works, you can read all about it in my thread - where I have tried to get allot of different puppies to work on my x86 Tablet with UEFI - there are also the solution to booting and KMS settings to get to the desktop.

I have also listed which puppies that didn't work.

I spent several months on trying to get this to work and I'm not done yet.

Maybe you can contribute:)

http://www.murga-linux.com/puppy/viewtopic.php?t=108295

Hope that helps:)

JBJ

X-Slacko Slim works fine on UEFI, even on Secure Boot mode. Vesa may not work on UEFI, use fbdev instead

My build of Lightweight Trusty are be works at UEFI too... (but it's a oldest anyway) -> murga-linux.com/puppy/viewtopic.php?t=108681 [Non-Rationalise for Now at Stable only']

Well, u asked what works and what doesnt, so here's my contribution
PC: Lenovo Ideapad 100. SSD drive, 4gb ram. (bought new a year ago)
UEFI.
Have a remastered version of tahr 6.0.5 with the 4.1.11 (or something) kernel.
(had to use the newer kernel or else wifi card was not found)

Boots from usb as long as secure boot is turned off.
As mentioned earlier in the thread, its easy to make a bootable usb on uefi machine.
Explained at http://blog.puppylinux.com/?viewDetailed=00009
and also on my own posting at http://murga-linux.com/puppy/viewtopic.php?t=109702

I coulnd't install to disk tho, using the SETUP->PUPPY INSTALLER because Grub4dos wouldn't install - just got the error message:
"somewhat error occured" - I assume bacause of some windows 10 thing.
What DID work - was to install LICK - in win10 - dragged the .iso over and machine now works fine with dual-boot puppytahr/windows.

Whats NOT so good is my wifi connection just stops working. (have to setup wifi network again to get it going again)
Have researched this and there is apparently problems with the driver-modules for the Realtek8723be wifi card.
I have tried the rtlwifi-new-something.pet (which I mirrored on
http://helledussen.com/linux/tahr/) but it doesnt seem to work - same problem with connection.
I would really appreciate help from any puppy users with dealings with the rtl8723be wifi card.

MacBook5,2 (MacBook non-Pro, non Air (13", Mid-2009)

Built-in EFI (not rEFInd, rEFIt, etc), on its latest El Capitan version (this Puppy didn't get Sierra).
I can put the version up if you wish.

Tried slacko 6.3.2, slacko64 6.3.2, and the test tahr64 6.0.6 UEFI build.

Old:

TL;DR: Works, but incredibly unreliably. Needs a workaround, and hangs for long periods most of the time before booting.

Real:
TL;DR: Works, needs workaround. Also hangs while booting if the built-in SuperDrive is broken.

OS X will only recognize a USB if the efi files are in a directory on the root of the partition. efi.img won't work, unless Puppy is directly burned to a CD.

This is what mostly works on a fat32 partition on GPT and MBR. I haven't tested hybrid MBR or the steps in this guide (but I want to boot Windows off it as well).

So, for a frugal install, instead of

---- /efi.img

it must be

---- /efi/
--------- /boot/
-------------- /bootx64.efi

After doing this, holding Option at boot will show "EFI Boot" as a boot option.

My MacBook seems to be very finicky. It prefers to boot from 64-bit (which is what I have heard a lot). When it isn't working, most issues arise from inability to find VESA BIOS extensions, mainly with "Mac Linux USB Installer".

I looked into the problem I had in the quote below and it seems to only happen because my SuperDrive is busted.

So ignore this quote, this has to be just me.

However, the main issue is that for some reason, about 75% of the time, it doesn't matter if it is on a live CD/DVD or a USB drive, you start the boot from GRUB, and it will hang on a black screen for 10 minutes plus before booting. The flash drive or DVD drive will go silent after a moment when it does that.

Out of that 75%, about 10% will just do nothing.

It seems to be related to unplugging the flash drive and plugging it back in, but I can't reliably get it to work.

I have tried pmediatype=whatever, pfix=ram, nomodeset, noefi, acpi=force, acpi=off, and noexec=off, but none of them do the trick.

It is still an issue, but I have even had this in Ubuntu 16.04.

The dmesg shows multiple attempts of accessing ata2, the device where the SuperDrive is internally connected, but reporting
"ata2: COMRESET failed (errno=32)"
repeatedly until it gives up. Then it boots.

I might have a faulty connection internally. I did get the thing used, and out of the box, it had an upgraded hard drive to 1TB, but the case was obviously pried off unprofessionally, as the edges are chipped off and some screws were missing.

I could try taking it apart later this month once finals are over and I don't have to rely on my MacBook for college work.

I don't know if this is directly related to EFI, but on Slacko (and Slacko64) 6.3.2, battery stats are only reported in /sys/class/power_supply/BAT0, not /proc/acpi/battery/BAT0. I have tried everything, trust me.

In tahr64, oddly, the battery stats work perfectly.

As a result of this, there is no battery icon in Slacko.

I modded powerapplet_tray 2.6 (can't find 2.7.x sources) to make it work with power_supply here. Sorry, no PETs, just source code.

It also has a lot of other issues, mostly with drivers. But these were simple to fix once you found the solution.

(in case you are wondering, WiFi, brightness control, trackpad, and standby mode were the main ones).

Another thing:

Removed the boot hang which was a problem with my already broken hardware.

Slacko64-6.9.6.4-uefi.iso boots with no battery stats, but WiFi works…:D
Ubuntu 16.04 doesn't have battery stats either.

diggin this right now
http://helledussen.com/mp3/2017/Sheryl% ... t%20up.mp3