[07:33] <thedoctar> Hi
[07:33] <arraybolt3[m]> Hello!
[07:33] <thedoctar> I'm having trouble installing Lubuntu 22.04
[07:33] <thedoctar> At first the bootloader step of calamares failed
[07:34] <thedoctar> I fixed this by adding the option --no-nvram in the bootloader/main.py calamares module
[07:34] <arraybolt3[m]> What system are you installing it on?
[07:34] <arraybolt3[m]> Dell Inspiron 7000 or something like that is the info I'm looking for.
[07:34] <thedoctar> But then later a step failed when it tried to install grub-efi-amd64-signed
[07:34] <thedoctar> Acer Aspire 4750
[07:35] <arraybolt3[m]> Hmm, OK, are you trying to install it alongside an existing OS?
[07:35] <thedoctar> I previously was dual-booting Windows 7 and Lubuntu 16.04
[07:35] <thedoctar> I was trying to upgrade Lubuntu
[07:35] <thedoctar> I thought it would be simple but it seems the bootloader doesn't work out of the box :(
[07:36] <arraybolt3[m]> Hmm, do you know if your system boots in EFI or BIOS mode?
[07:36] <thedoctar> I'm not really sure to be honest. The first two partition are Windows related, and one of them has an EFI folder, so I assumed EFI
[07:37] <arraybolt3[m]> Also, if you could pop open a terminal with Ctrl+Alt+T, then run "cat ~/.cache/calamares/session.log | nc termbin.com 9999", then send the link, that may be helpful (this will give me your installation log).
[07:37] <thedoctar> But in the BIOS there are literally no options regarding legacy/EFI mode for booting
[07:37] <thedoctar> https://termbin.com/45tx
[07:37] <arraybolt3[m]> To me it sounds like some sort of conflict is happening between already existing bootloader stuff, I'm not quite sure yet.
[07:38] <thedoctar> It used to load with GRUB on Lubuntu 16.04
[07:38] <arraybolt3[m]> Oy, I think I found it.
[07:38] <thedoctar> Oh, so quick?
[07:38] <arraybolt3[m]> grub-install: error: failed to register the EFI boot entry: Operation not permitted.
[07:38] <thedoctar> Yes that is the error
[07:38] <thedoctar> And below it says something about the terminal
[07:39] <thedoctar> But I don't know how to fix it
[07:39] <arraybolt3[m]> So I think what's happened is that your laptop has too many boot entries in the firmware. This can happen sometimes, and the solution is to delete some of the older entries.
[07:39] <thedoctar> How do I do that?
[07:39] <thedoctar> That makes sense
[07:39] <thedoctar> Because on the boot loader when I press F12, I get repeated ubuntu options
[07:39] <arraybolt3[m]> I'm looking it up right now.
[07:39] <thedoctar> And then a HDD option
[07:40] <thedoctar> You're good!
[07:40] <thedoctar> But my bios is really basic
[07:40] <arraybolt3[m]> thedoctar: Can you run "sudo efibootmgr" and tell me if you see anything when you do that? (Please don't paste the output into IRC, I just want to know if efibootmgr is installed or not.)
[07:40] <thedoctar> no. I can install it if it helps
[07:41] <arraybolt3[m]> Yeah, just "sudo apt install efibootmgr".
[07:41] <arraybolt3[m]> That will allow us to see the boot entries, determine the obsolete ones, and delete them.
[07:41] <thedoctar> I have 12 boot options
[07:41] <arraybolt3[m]> Yikes.
[07:42] <arraybolt3[m]> OK, so, in order to let me see them, can you do "sudo efibootmgr | nc termbin.com 9999" and send that link too?
[07:42] <thedoctar> I sent you a personal message via   “start query”
[07:44] <arraybolt3[m]> OK, it's not come through yet, one moment...
[07:44] <arraybolt3[m]> Argh, Matrix isn't letting it through, one moment while I join via IRC...
[07:44] <arraybolt3[m]> OK, you should see a user called "arraybolt3" (without the [m] part) that you can query and I'll get it.
[07:45] <arraybolt3> That's me!
[07:45] <thedoctar> Got it?
[07:45] <arraybolt3[m]> Yep, got it.
[07:45] <thedoctar> Yay!
[07:46] <arraybolt3[m]> OK, I'd delete both 000B and 000C from there, which you can do with "sudo efibootmgr -b 000B -B && sudo efibootmgr -b 000C -B".
[07:46] <arraybolt3[m]> Then the bootloader can make a new one for "ubuntu" during the installation procedure.
[07:47] <thedoctar> HDD0 was the original bootloader, should I delete that too?
[07:47] <arraybolt3[m]> Nah, I'd leave it.
[07:47] <thedoctar> Okay
[07:47] <arraybolt3[m]> Anything we can leave safely, I'd leave. You can mess stuff up if you delete too much.
[07:47] <thedoctar> Ok great, I will try again
[07:48] <thedoctar> Also, do you know why I need to --no-nvram option, and should I report this as a bug?
[07:48] <thedoctar> Because once the installer fails, you can't restart from the previous position
[07:48] <arraybolt3[m]> I do not know, but I suspect it's related to the UEFI problem, and I'd remove it now that we've done this trick.
[07:48] <thedoctar> Also a really annoying anti-feature
[07:48] <thedoctar> Hm okay
[07:56] <thedoctar> I still get the same error
[07:56] <thedoctar> grub-install: error: failed to register the EFI boot entry: Operation not permitted.
[07:56] <thedoctar> Unknown terminal: qterminal
[07:56] <thedoctar> Check the TERM environment variable.
[07:56] <thedoctar> Also make sure that the terminal is defined in the terminfo database.
[07:56] <thedoctar> Alternatively, set the TERMCAP environment variable to the desired
[07:57] <arraybolt3> thedoctar: Oy. There's a bot in here that will automute you if you paste a bunch of stuff into IRC, so you probably won't be able to send anything for another 60 seconds, sorry about that.
[07:57] <arraybolt3> thedoctar: You can use Pastebin.com to send large amounts of data without that happening.
[07:58] <arraybolt3> thedoctar: Can you run "sudo efibootmgr" again and see if the old entries that we deleted actually got deleted or not?
[07:58] <arraybolt3> (Also the bot just unmuted you \o/)
[07:58] <thedoctar> Yay!
[07:58] <thedoctar> What does the unknown terminal error mean?
[07:59] <arraybolt3> I don't know, sadly. But the error with grub-install eems to be the root of our problems.
[07:59] <arraybolt3> *seems
[08:00] <arraybolt3> I'm gonna search that error and see what known solutions there are.
[08:00] <thedoctar> Okay thanks
[08:01] <arraybolt3> thedoctar: Can you poke around inside your BIOS settings for anything called "Fast Boot"? I see reports that it might be causing trouble.
[08:01] <arraybolt3> If you see it and it's enabled, turn it off and try again.
[08:05] <thedoctar> brtb
[08:05] <thedoctar> brb*
[08:10] <thedoctar> I don't have a fastboot option
[08:10] <thedoctar> I don't have any boot options actually
[08:10] <arraybolt3[m]> Blah.
[08:10] <thedoctar> Maybe my BIOS is just shit.
[08:10] <thedoctar> It's from 2011
[08:11] <arraybolt3[m]> And you're sure the old boot entries are gone? The two we deleted?
[08:11] <thedoctar> Yeah. One is back because I did the install again
[08:11] <arraybolt3[m]> thedoctar: OK that is really odd. How did the install fail this time then?
[08:11] <thedoctar> It was the Unknown Terminal error
[08:12] <arraybolt3[m]> Did it give a specific error message on screen?
[08:12] <arraybolt3[m]> And if so, it was that Unknown Terminal thing?
[08:12] <thedoctar> The installer tries to upgrade/install the package grub-efi-amd64 on the target system, and then the configuration script fails.
[08:13] <thedoctar> I copy pasted it but maybe I was blocked before it reached here. I will run it again. But basically itw as saying qterminal was unknown and I should modify the variables TERM or TERMCAPS
[08:13] <arraybolt3[m]> That's just so weird. Did you check your ISO to make sure it wasn't corrupted during the download?
[08:13] <thedoctar> I've already used it twice, but maybe it got corrupted in between?
[08:14] <arraybolt3[m]> thedoctar: And those two times it worked?
[08:14] <thedoctar> Yeah
[08:14] <arraybolt3[m]> I guess maybe it got corrupted in between. I just can't imagine how on earth qterminal would have anything to do with installing EFI variables.
[08:15] <thedoctar> Hmm okay I will try rewrite the startup disc
[08:18] <thedoctar> @arraybolt3, when I tried to run qterminal on the target system after it gave the “Unknown Terminal” error message, qterminal failed to run, saying it couldn't find the display or something.
[08:19] <arraybolt3[m]> Very interesting. That sounds like a corrupted installer to me.
[08:19] <arraybolt3[m]> qterminal is just the terminal app that you run commands in with Lubuntu.
[08:19] <arraybolt3[m]> But... we were able to run commands a bit ago, so...?
[08:24] <thedoctar> @arraybolt3[m] I meant in the target system. So this is after I run chroot /tmp/calamares-root-ID
[08:25] <arraybolt3[m]> Oh. If you did a chroot, that explains it. Graphical apps like QTerminal have a hard time dealing with chroots.
[08:46] <thedoctar> I rewrote the USB startup disc, but I get the same unknown terminal error. The thing is, is calamares is chroot'ing into the /tmp/calamares-root folder, and then trying to upgrade grub-efi-amd64. The configure script for this calls the terminal program, which is set to qterminal, which fails to run.
[08:47] <thedoctar> @arraybolt3[m] Any ideas?
[08:53] <arraybolt3[m]> Sorry, I'm really not sure. I'd suspect a firmware bug.
[08:53] <arraybolt3[m]> When you boot the ISO, what mode are you booting it in?
[08:54] <arraybolt3[m]> (I just had an idea, LOL)
[08:55] <thedoctar> You mean EFI vs BIOS?
[08:55] <thedoctar> It's EFI
[08:56] <thedoctar> BTW, the terminal stuff I think is because when I tried doing the commands by hand, the apt command prints out a text-based window thing, maybe that's why that error is there
[08:56] <thedoctar> But I still get the “can't add this to EFI boot menu” problem
[08:56] <arraybolt3[m]> Yes. I know the firmware is EFI, but are you booting the ISO from a boot menu, and if so, are you selecting the EFI entry?
[08:58] <thedoctar> Yes there is a boot menu. There's no option regarding EFI or otherwise. But the installer says EFI in the upper left-hand corner on the partition page
[08:58] <thedoctar> I can complete the grub-install command with the --no-nvram option after the package installation though. Coudl it be something to do with that?
[08:59] <arraybolt3[m]> Hmm... yeah I think that's the problem. The thing is the --no-nvram option basically tells GRUB to not mess with the firmware, which isn't really how it's supposed to work.
[09:00] <arraybolt3[m]> And even if you could force it to work somehow this way, the package itself appears to run the command normally, so you'd need to hack the packaging every single time GRUB updated, which could be an ordeal.
[09:02] <arraybolt3[m]> Oh hey wait! If you open up KDE Partition Manager, can you tell me what partition table your disk is using? MBR or GPT?
[09:02] <arraybolt3[m]> (Actually, it may not tell you, but I can probably find a tool that will...)
[09:02] <arraybolt3[m]> thedoctar: Can you run "sudo parted -l | nc termbin.com 9999" and send the link?
[09:11] <thedoctar> It's MBR
[09:11] <thedoctar> But I managed to get it working, but manually running grub-install --no-nvram and update-grub. But I never completed the installation process.
[09:11] <thedoctar> Probably my firmware is broken, right?
[09:11] <arraybolt3[m]> thedoctar: MBR is your problem.
[09:12] <arraybolt3[m]> EFI isn't designed to work with MBR at all.
[09:12] <arraybolt3[m]> Do you need to keep the Windows install you currently have on this system?
[09:12] <thedoctar> Preferably
[09:12] <arraybolt3[m]> And also, can you set your laptop into Legacy mode or BIOS mode?
[09:12]  * arraybolt3[m] looks up BIOS options
[09:12] <thedoctar> No, the BIOS has no problems
[09:12] <thedoctar> options*
[09:15] <arraybolt3[m]> Hmm. I'm guessing Windows is probably booting in BIOS mode, but the firmware supports EFI.
[09:15] <thedoctar> Can I get the Windows version into the GRUB menu for booting with the current setup?
[09:15] <thedoctar> How do I get the BIOS version of Lubuntu 22.04?
[09:15] <arraybolt3[m]> The problem is that you'll run into future errors down the road when updating, and it will probably break your package setup.
[09:16] <arraybolt3[m]> thedoctar: One moment, I have an idea for that...
[09:18] <arraybolt3[m]> thedoctar: OK, so try turning the laptop all the way off, then insert the USB drive with the Lubuntu installer and turn it back on. Immediately after you hit the power button, start pressing F12 over and over until the boot menu shows up. If it gives you an option to boot the USB stick in Legacy mode or something like that, use that option.
[09:22] <thedoctar> Nah, that's how I normally boot the USB
[09:22] <thedoctar> I'll try update the BIOS
[09:22] <thedoctar> Maybe then I get more options
[09:22] <arraybolt3[m]> thedoctar: Crummy. By "no options" do you mean that you're not finding the options, or that there's a password set?
[09:22] <thedoctar> I can't find the options
[09:23] <arraybolt3[m]> thedoctar: A photo would be nice, since everything I see says there's plenty of options.
[09:23] <thedoctar> I got to go for now, thanks for the help. I'll keep you updated if I make more progress later
[09:23] <arraybolt3[m]> thedoctar: Can you try using the right arrow key when you first boot into the BIOS? The BIOS setup on the Acer looks like it's one of those where you change menus with the left and right arrow keys and then enter the options in the menus with the up and down keys.
[09:23] <arraybolt3[m]> thedoctar: OK, see you later! Hope we can get this sorted out.