[SOLVED] Seeing minimal bash-like line editing is supported when booting to grub for lubuntu 20.4
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Distribution: Antix 19.2, Androidx86, Windows, MX linux
Posts: 29
Rep:
Seeing minimal bash-like line editing is supported when booting to grub for lubuntu 20.4
I have successfully installed lubuntu 20.4 on unallocated space and grub is installed, I just have to change to ubuntu in boot options. unfortunately, grub says Seeing minimal bash-like line editing is supported. I don't know what to do because it is completely unusable and I cant get to lubuntu but I know it is installed. Any help would be appreciated.
Take a screen shot upload it to OneDrive, Google Drive, Pastebin (set proper permissions of course only the folder with that pic and not expose your whole drive ) or other sources, it would be easier for others to figure out what is on your screen.
the ? represents the partition number counting from 1, If it is on a different drive, drives count from 0.
Then once booted in open a terminal run if this is an efi system.
Quote:
sudo grub-install
If not add /dev/sda, this may be different.
Last edited by colorpurple21859; 07-01-2020 at 05:34 AM.
Distribution: Antix 19.2, Androidx86, Windows, MX linux
Posts: 29
Original Poster
Rep:
Quote:
Originally Posted by cordx
this page has a description of how to boot from the grub prompt.
Thanks I think it is because I rebooted without removing the usb because after I removed it and it worked. I would however still learn about this issue so thanks again.
Distribution: Antix 19.2, Androidx86, Windows, MX linux
Posts: 29
Original Poster
Rep:
Quote:
Originally Posted by colorpurple21859
If you know what drive/partition lubuntu is on
Code:
configfile (hd0,?)/boot/grub/grub.cfg
the ? represents the partition number counting from 1, If it is on a different drive, drives count from 0.
Then once booted in open a terminal run if this is an efi system.
If not add /dev/sda, this may be different.
I understand the second part, but what does the first code mean. Is it for a terminal or a file location? thanks
I tried run grub-install, boot-repair but not solve my problems.
I have a double boot system with debian distro and with signed packages for boot security.
With signed image and grub-install (signed too) no error appear, but grub console appear again.
To solve, in my case: grub-install write in /dev/sda2 your files in /EFI/grub folder (in sda2 windows SO put efi files in EFI folder)
Shutdown and Power on again
In grub console bash-like
ls command to view partition with efi files (hd0,gpt2). The first grub.cfg file is in grub folder extract_entries_configfile (hd0,gpt2)/EFI/grub/grub.cfg command to run grub.cfg (firt grub config file)
then new error appear: "error: search.fs_uuid is not allowed to execute in an extractor"
The problem is the $prefix variable. echo $prefix to view it's content: (hd0,gpt2)/EFI/debian
debian folder not exist!! That is the problem
I created debian folder in EFI folder and copy grub.cfg (file in EFI/grub) in debian folder.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.