- - mkdir -p /EFI/boot
Thanks for the heads-up.
Cheers!
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.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.
Thank you for the confirmation.It works for me booting Precise puppy on a Dell Optiplex 3020 with UEFI.
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.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.
Originally was 64 only but 32 bit is now also available.jamesbond wrote:Slacko64 with UEFI support now testing: http://murga-linux.com/puppy/viewtopic.php?t=106337
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.zakjoh wrote:Are there any modern boards still being manufactured that don't use UEFI ??
Read more: http://www.easy2boot.com/uefi-grub2-ptn2/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!
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!).
Real:TL;DR: Works, but incredibly unreliably. Needs a workaround, and hangs for long periods most of the time before booting.
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.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.
It is still an issue, but I have even had this in Ubuntu 16.04.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.
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.
There is a possible fix for ubuntu trusty tahr that may address your issue.Limbomusic wrote:Well, u asked what works and what doesnt, so here's my contribution
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.