Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Below are the files as far as I know that play a role in this. I have omitted comments contained in the files and have only shown what is relevant. The custom.cfg file has been newly added due to the new OpenBSD menu entry, and the rest has been returned to its original state as shown.
If you create a custom.cfg file that loads the BSD kernel directly instead of chainloading, are the arrows still inoperable? Does a stab or two or three of NUM produce any difference?
I don't know how to address the OpenBSD kernel directly instead of via chainloading.
When 'c' is pressed I don't get a command line. If I press 'c' in the grub menu, the menu bar jumps to OpenBSD and stays there, neither the arrow keys, some TABs, or any other keys can move the menu bar. The latter also applies if I don't press 'c'. Both OS's can be booted, only the arrow keys do not work. As the article indicated, I created a /grub directory in OpenBSD and placed the suggested file in it. After a reboot, nothing has changed, so the error remains as it is.
Are we dealing with an MBR installation here, or UEFI? If UEFI, what does tree -ha /boot/efi report? (adjust location as required if rescue booted.)
Is Mint's (Ubuntu's) current Grub 2.06 the only Grub that has ever written to disk? If not, what did, and how long ago? Maybe it's time to reinstall Grub, not just update grub.cfg, custom.cfg and/or /etc/grub.conf.d/. ???
Are we dealing with an MBR installation here, or UEFI? If UEFI, what does tree -ha /boot/efi report? (adjust location as required if rescue booted.)
This is a MBR install, not an UEFI.
Quote:
Is Mint's (Ubuntu's) current Grub 2.06 the only Grub that has ever written to disk? If not, what did, and how long ago? Maybe it's time to reinstall Grub, not just update grub.cfg, custom.cfg and/or /etc/grub.conf.d/. ???
Its grub v 2.04. It is a fresh install, Linux mint 20.2, then upgrated to 21.2. How do I install grub v 2.06?
Did you try plugging the keyboard into various USB ports? Check they were all unobstructed? Using a USB3 keyboard? USB3 port? Enable Legacy USB support or USB keyboard support in the BIOS? Do the Page UP/Down keys work? Do the arrow keys work when you access the BIOS?
Did you try plugging the keyboard into various USB ports? Check they were all unobstructed? Using a USB3 keyboard? USB3 port? Enable Legacy USB support or USB keyboard support in the BIOS? Do the Page UP/Down keys work? Do the arrow keys work when you access the BIOS?
The arrow keys work in the BIOS, as well as in programs such as nano and less in OpenBSD and Linux. Other keys also work normally. USB is V2.0, both keyboard and connections. Therefore, it cannot be due to the USB connection or the keyboard.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.