Activity for Roderick W. Smith
-
Roderick W. Smith posted a comment on discussion General Discussion
If your kernel is the Linux/kde-linux_202501310256+3.efi file on your ESP, then setting the following line in refind.conf should get it detected: also_scan_dirs +,Linux Be sure that there's no later also_scan_dirs line in refind.conf. If this doesn't work, then you might try installing and launching an EFI shell. You can then poke around in the shell to see if that file really is a kernel with an EFI stub loader; you should be able to launch it by typing its name, and if it doesn't launch, you may...
-
That's not really possible. rEFInd runs under EFI, which has a completely different naming convention from Linux. That is, /dev/sda1 is a Linux partition name that is not retrievable from EFI. In theory, I could poach the Linux kernel's naming code for use in rEFInd, in the hopes of getting the same results; but even that would not be guaranteed to work because of differences in drivers -- a disk might show up in Linux but not the EFI, which would throw off the naming convention. Even the partition...
-
I don't think the problem is an encrypted /boot partition, since rEFInd does work when loaded from an external USB flash drive. What filesystem is used for the rEFInd install (the ESP)? On a Mac, that must be FAT or HFS+, and it must not be encrypted. Kali should have set it up correctly, but it's worth double-checking. Also, what partition table is used on the disk, GPT or MBR? If it's MBR, then the Mac's firmware will default to BIOS/CSM/legacy mode and won't load any EFI-mode boot program. Macs,...
-
rEFInd relies on the EFI to set the screen resolution, and the EFI in turn relies on whatever video drivers it can find (typically in the motherboard or video card). These resolutions are limited in number, and aren't guaranteed to match your monitor's optimal resolution (although that's usually one of the ones that's available); you can't just set an arbitrary resolution. If you're using a UEFI-based PC, the failure message when you try to use an unsupported video mode should show a list of supported...
-
This is almost certainly a filesystem issue -- either damage to the filesystem caused by the resize or restore operation or a bug in the filesystem driver. I recommend running disk checks (with fsck) on the filesystems you modified. If that doesn't help, then as a diagnostic measure, try removing the rEFInd filesystem drivers (from the ESP's EFI/refind/drivers_x64 directory). If that helps, then you can try restoring only the one that you need to read the kernel. If the problem recurs, then it's...
-
Fixed incorrect terminology about the Windows fast startup feature in documentation
-
The volume line must come before the loader line in manual boot stanzas. Chances are that's the problem; your configuration put them in the wrong order.
-
I'm afraid that's not supported at the moment; it would require significant changes to rEFInd's screen-display code.
-
Enough. I won't tolerate this sort of disrespectful exchange. If there's another such disrespectful post and I'll delete the whole thread.
-
That sort of conversion is certainly possible, but would add code complexity that I'd prefer to avoid. That said, I'm willing to consider a patch/merge request; but at the moment I'm pretty busy with other matters, so I don't have much time to devote to this issue.
-
Make write of LoaderDevicePartUUID non-persistent
-
rEFInd relies upon the EFI to read the kernel file. If the EFI cannot read a device natively, it requires a driver, such as the ext4fs and other Linux filesystem drivers provided with rEFInd. AFAIK, there's no EFI driver to read LUKS devices, so AFAIK, at present, rEFInd doesn't support reading kernels from them. In theory, this limitation could be fixed by writing an EFI LUKS driver. A more practical workaround at the moment is to store your kernel and initramfs on a partition that rEFInd can read....
-
You can set any unique part of the description as the default_selection to have rEFInd use that; for instance: default_selection = preboot Assuming there's only one preboot option, this example should cause it to be used as the default selection on every boot.
-
To boot in BIOS/CSM/legacy mode, you must install a BIOS-mode boot loader on the disk. This is normally the BIOS version of GRUB; and to install that, you'll need to boot a Linux recovery tool or OS installer and then issue appropriate commands to do the installation. The easiest way to do this is likely to be to use the Boot Repair tool: https://help.ubuntu.com/community/Boot-Repair That said, in this case your ultimate end state will be to use BIOS-mode GRUB 2 to boot a single OS (Linux Mint),...
-
Sorry; I failed to push the changes. They should be there now.
-
The --usedefault {target-device} option to refind-install should do what you want, provided the target device contains a FAT filesystem. Type man refind-install and search on usedefault for details.
-
This feature already exists in rEFInd, but is disabled by default so as to minimize wear on the NVRAM. (I've seen systems fail with worn-out NVRAM in the past, so I prefer to minimize NVRAM writes, when possible.) To enable it, uncomment the write_systemd_vars token in refind.conf and set the value to true.
-
Added ArcaOS icon
-
Do more to fix the refind-mkdefault bug involving a bad BootOrder variable
-
rEFInd 0.14.2 introduced some significant changes to the way it scans for disk-based tools. I did this for various reasons -- partly to simplify the code, partly to deal with changes in the names and locations of some tools (most notably, various memtest tools). One consequence, however, is that rEFInd may detect a slightly different set of tools, potentially increasing or decreasing the number of tools, depending on what's available on a system. That said, some of what you've reported seems strange,...
-
Fixed bug in refind-mkdefault if BootOrder has invalid entry.
-
rEFInd relies on various on-disk files for much of its functionality, so if it's started over a network, it won't know where to look to find those files -- and they may not be available at all. I tested this years ago, and IIRC, at the time it would sort-of work, but without icons and with only the defaults from refind.conf (since of course it couldn't load that file). It may be that it's gotten worse -- or maybe not. What happens when you do as you're prompted and press a key to continue? If rEFInd...
-
rEFInd automatically filters out duplicate partitions based on the filesystem's UUID or serial number. This is done so as to prevent the display of duplicate entries in software RAID 1 arrays. Chances are this is what's causing your issue -- your backup partition likely contains a duplicate serial number. You might want to check your backup software to see if it has an option to not duplicate the serial number when cloning a partition. As the point of a filesystem serial number is to uniquely identify...
-
I do use git tag on release versions; the latest has a tag of "v.0.14.2".
-
First, you can always set icons_dir in refind.conf to point to a replacement or supplemental directory for icons. These will not be replaced when rEFInd is updated. This option is most commonly used in theming operations, but you can use it to add one or two icons, if you like. Second, I've just added an ArcaOS icon to the rEFInd git repository. I picked a different one than you presented for licensing reasons and because it better fills the square; however, the original was just 80x80, and so it...
-
Version 0.14.2 release
-
Makefile changes for GNU-EFI:
-
Theoretically add gzip.lib to 'make tiano' build target; but that target is deprecated and doesn't work for me.
-
Remove commented-out code; reformat a few lines.
-
I've pushed my changes to the git repository. Could you please try them, @nl6720? They work for me on Ubuntu 22.04 on x86-64, Ubuntu 24.04 pre-release on ARM64, and Arch Linux on ARM64. Both the Ubuntus used a locally-built GNU-EFI 3.0.18, but the Arch used the Arch GNU-EFI 3.0.18 package. I'm afraid I don't have a working Arch installation on x86-64 for testing. Note that the ARM64 build change requires editing Make.common or passing GNUEFI_ARM64_TARGET_SUPPORT=y when using GNU-EFI 3.0.17 or later;...
-
Accommodate change in GNU-EFI 3.0.17 and later build options for ARM64
-
Worked around problems with GNU-EFI 3.0.18
-
I think I've got this sorted out. There are actually three problems: * The change you identified that causes failures to launch if -j .rodata is not used with objcopy. This was the easiest to deal with. * The commit I identified, which changed the way CopyMem() was defined. This one's weird; it was as if the rEFInd build process was ignoring the EFIAPI option on that function, thus calling it with the wrong ABI. Maybe it was; the rEFInd build process is pretty convoluted. I've worked around the problem...
-
Further information: It's also necessary to add -j .rodata as an objcopy option. This may well be related to the commit you identified, @nl6720. (I'd been experimenting with that and forgot I had it set when I found the EFIAPI commit.)
-
To quote Marge Gunderson ("Fargo"), "I'm not sure I agree with you a hundred percent on your police work there, Lou." Poking through the Sourceforge git repo for GNU-EFI, I find that the following commit is the troublesome one: https://sourceforge.net/p/gnu-efi/code/ci/deb8a7f267d96299b9aa41300539f617db54c2a9 All commits prior to that one work fine for me, but once I build with that one, it fails in the way you describe. The commit in question changes SetMem() and CopyMem() to use the EFIAPI calling...
-
Fixed 'fat' Apple binary detection bug
-
Minor logging bug fix & optimization in IsValidLoader()
-
Fix typo in refind-sb-healthcheck message
-
Forgot to save NEWS.txt after editing it....
-
Added Shim information to Info/About screen
-
Code optimizations, mostly in scan.c's FindTool() and IsValidTool()
-
Restructured tool-scanning code; added also_scan_tool_dirs token
-
Remove a few commented-out lines
-
Improved RPM & Debian packaging, particularly related to Secure Boot
-
Version 0.14.1 final release
-
Updated LodePNG to version 20230410
-
Remove bootx64.efi (etc.) as valid memtest filenames
-
Update of copyright dates in multiple files
-
Remove duplicate tools caused by duplicate tool locations
-
Move memtest from boot loader to tools menu if found in a boot loader location
-
Fixed bug in refind-install that caused --ownhfs option to fail
-
Fixed bug in display of Unicode characters greater than 0x10000
-
Thanks for the submission. I've accepted it, but added a drop shadow to the icon, to match other rEFInd icons.
-
Adds icon for EndeavourOS
-
add the EndeavourOS icon
-
Document recent Btrfs RAID code submission in NEWS.txt
-
Thanks for the contribution!
-
port RAID1C3/4 support from grub2
-
Version 1.0.10 release
-
implement k/--move-backup-table/MoveSecondTable
-
Sorry for the late reply; I've been pretty busy lately. I've merged this and added the changes I've suggested myself.
-
Fine-tuning and documentation of new function to move the secondary/backup partition table
-
implement k/--move-backup-table/MoveSecondTable
-
Fixed accidental inclusion of stray code lines
-
New partition type codes from the Discoverable Partitions Specification
-
Updated NEWS for recent merge
-
Minor enhancments
-
Thanks for the submission; however, I see two problems with it as-is: I don't see an obvious way to detect when the backup partition table is in an odd location. When parted is fed a partition table that's been moved by your code, for instance, it warns that this has been done and offers to fix it. Currently, gdisk includes no such checks, so it won't detect such a move, even though improper use of the facility might result in severely reduced available disk space. I suggest adding a check to the...
-
Add linux_prefixes config file option & change bzImage to Image as kernel ID on ARM64 systems
-
More logging about finding filesystem types
-
Fixed bug that could cause freeze when doing a self-install
-
Excise CSM boot support from non-x86/x86-64 builds
-
Improve log file rotation error checking
-
Properly log gDS warning
-
Improve detection of EFI program validity
-
Revert most of the previous commit, since it turns out it doesn't work. :(
-
Fixed problems with Tow-Boot that could cause crashes when loading drivers or re-scanning for boot loaders
-
Minor code cleanup based on valgrind analysis
-
Fixed JPEG problems: Memory leak & garbled JPEG when compiled on some distributions
-
I have essentially no experience with BitLocker, so I can't offer anything more than speculative advice. That said, my questions and thoughts are these: What happens if you boot from rEFInd to a Linux kernel, vs. rEFInd to GRUB to a Linux kernel? I wouldn't expect there to be a difference, but if there is, that would be informative. Does booting Windows through rEFInd, and then rebooting Windows again through rEFInd, without booting Fedora, cause the recovery key to be needed? In normal operation...
-
Fix bug in refind-install discovered after major release.
-
Added information on Fedora's rEFInd package to the documentation
-
To quote Homer Simpson, "d'oh!" That bug actually existed in 0.13.3 and forced the release of 0.13.3.1. It recurred because, in both cases, it was caused by my accepting bad advice from the shellcheck shell script analysis tool. I've just released a 0.14.0.2 version to address this problem. I've also added comments to the script to deter me from making the same mistake a third time.
-
Document previous merge
-
Truncate decimal inputs (e.g., '9.5G' becomes '9G')
-
Do some explicit casts in gptcurses.cc to eliminate compiler warnings.
-
You launch gdisk against the whole disk (e.g., /dev/sda in Ubuntu or /dev/disk0 is macOS), NOT against an individual partition (e.g., /dev/sda1 in Ubuntu or /dev/disk0s1 in macOS). You did the latter, so gdisk gave no useful output. If Ubuntu is installed on your /dev/disk0 (in macOS), then the diskutil output makes it look like it's correctly marked, but I'm less familiar with what diskutil works, so I can't be sure of that; I'd still like to see confirmation from gdisk. Another possibility is that...
-
Document recent mergest
-
Thanks for the improvement!
-
Allow partition dynamically allocated by --largest-new to be referenced by other options
-
Thanks for the submission; however, it's not acceptable as-is. It works fine for gdisk, but the cgdisk, the prompt is ugly and accepts no input, thus freezing the program; and it breaks the flow in the command-line, non-interactive sgdisk with an unacceptable prompt. You'll need to change the structure of the prompting for each program (although it's possible you could create one to work for both cgdisk and gdisk and another for sgdisk). For sgdisk in particular, you'll need to add a new command-line...
-
Use 64bit off_t on 32bit linux systems
-
LGTM. Thanks.
-
Document recent merge.
-
Fix NULL dereference when duplicating string argument
-
LGTM. Thanks!
-
Bump the version up artificially to make Launchpad happy
-
Fixed missing refind-sb-healthcheck from .zip and native .deb packages
-
I've just released rEFInd 0.14.0. It's available from the downloads section here on Sourceforge, and should be available soon from the Ubuntu PPA (it's built there for Ubuntu 22.04, as of 3:54 PM US Eastern Time on March 4; but builds for other versions are still pending). See the revisions page of the documentation for details of the changes. In brief, new features include: the ability to launch gzipped kernels (which is important on ARM64, but not on x86 or x86-64) Secure Boot Advanced Targeting...
-
Final changes for version 0.14.0
1 >