[00:21] <nsh> Guest76, did you check secureboot?
[00:21] <Guest76> Secureboot is enabled
[00:21] <nsh> (that is if your bios is happy to boot things that aren't signed by our lord and saviour, sir jesus christ)
[00:22] <Guest76> But I didnt have password set on hard drive
[00:22] <Guest76> does that matter?
[00:22] <nsh> idk there's probably a manual or something
[00:22] <nsh> :)
[00:23] <nsh> advice here: https://forums.lenovo.com/t5/Linux-Discussion/New-T470-Trying-to-get-F12-menu-to-boot-Linux-from-USB-or-Second/td-p/3706396
[00:24] <nsh> '2) In BIOS disabled Secure Boot, set it to UEFI + Legacy Boot combo, and set it to boot from Legacy first / UEFI second.'
[00:25] <nsh> (but you will spend eternity in the burning hellfires of damnation. imho it's a price worth paying for the worldly power of penguins and terrible sound subsystems.)
[00:34] <Guest76>  @nsh will i need to reinstall Linux after all that is said and done?
[00:34] <arraybolt3> Guest76: What's happening?
[00:35] <Guest76> Boot loop...
[00:35] <arraybolt3> nsh: Please stick to support.
[00:35] <Guest76> on Lenovo T470s
[00:36] <arraybolt3> Guest76: Do you happen to have an option in your boot menu to boot from an EFI file?
[00:36] <arraybolt3> I've had certain systems have a bit of trouble booting a new Ubuntu installation, but if I can get them to boot an EFI file, I can point it to the shimx64.efi file and it works.
[00:37] <arraybolt3> And if that works, then you might be able to find a "Customized Boot" option in your BIOS that will allow you to get it to boot Ubuntu automatically.
[00:40] <arraybolt3> (I doubt that disabling Secure Boot will help here, it seems more likely that your system may be trying to boot with a "Windows Boot Manager" EFI entry, which caused a similar problem for me on an HP Elitebook.)
[00:41] <Guest76> What is "Enroll MOK"
[00:41] <Kreyren> hey
[00:41] <Kreyren> howddya do power management things
[00:42] <Kreyren> my friend's ubuntu starts to rush fans on 100% after he plugs in the charger and it's really annoying
[00:42] <arraybolt3> Guest76: You usually see that screen if you're trying to get third-party drivers working with Secure Boot.
[00:42] <Guest76> Oh ok
[00:42] <Guest76> So options are... "Continue Boot, Enroll MOK, Enroll key from disk, enroll hash from disk"
[00:42] <Guest76> which option do I pick? Enroll MOK?
[00:42] <arraybolt3> Guest76: I'd pick Enroll MOK.
[00:43] <arraybolt3> You will probably need to enter a password that you entered during the Ubuntu installation process.
[00:43] <Guest76> "View Key 0" or  "Continue"
[00:43] <arraybolt3> Guest76: Continue.
[00:43] <Guest76> enroll the keys? Yes/No?
[00:43] <arraybolt3> Guest76: I'd pick Yes.
[00:44] <arraybolt3> This is the point where it will ask you for the password.
[00:44] <Guest76> then reboot
[00:44] <arraybolt3> (If I'm remembering correctly.)
[00:44] <arraybolt3> Yep.
[00:44] <arraybolt3> I'm guessing you have a weird WiFi card or an NVIDIA card?
[00:44] <Guest76> who me?
[00:45] <Guest76> its still boot looping :(
[00:46] <arraybolt3> Guest76: Did you find a "Boot from EFI file" option?
[00:46] <Guest76> Where do I find that?
[00:46] <arraybolt3> Do you know how to find your system's boot menu?
[00:46] <Guest76> Yes "Choose a temporary start up device"?
[00:46] <arraybolt3> Usually there's a key you can press during early setup (a lot of times it's Esc) that will give you a menu of options.
[00:46] <arraybolt3> Yeah, select that, then is there a "Boot from File" option or something?
[00:47] <Guest76> Windows Boot Manager, NVME: Intel SSDPEKKF256G8L, PCI LAN
[00:47] <arraybolt3> Guest76: Yeah, that's probably what's causing your boot loop.
[00:47] <Guest76> Did I screw up the linux install?
[00:48] <Kreyren> omg..
[00:48] <arraybolt3> Nah. SOme hardward is just finicky.
[00:48] <arraybolt3> Kreyren: Sorry, was caught up in a previous support session, we can see you and hopefully try to help if possible.
[00:48] <Guest76> Wahts the issue? Linux don't play well with Intel brand SSDs?
[00:49] <Kreyren> arraybolt3, i was more like terrified about the suggestion you are giving to him and deciding if i want to help or not tbh~
[00:49] <arraybolt3> Guest76: No, there's some EFI implementations that can't figure out that you shouldn't keep trying to boot Windows when Linux is installed.
[00:50] <Guest76> Terrified? Why?
[00:50] <arraybolt3> Kreyren: How so?
[00:51] <arraybolt3> (fwiw I've done this a few times without problems, and we're not doing anything that we can't undo from the BIOS setup or a live ISO, in fact what I'm suggesting you do now won't even do anything permanent.)
[00:51] <Kreyren> from what i read you forgot to advise him to reconfigure grub so it's probably doing bad things bcs of it or tell him to send a screenshot of the kernel console unless ubuntu puts eye candy over it
[00:52] <arraybolt3> Kreyren: If Windows Boot Manager is causing a boot loop, GRUB and the Linux kernel aren't even loading, so that's not going to help us much.
[00:52] <Kreyren> replace the windows boot manager then bcs it's designed to mess with linux and impossible to make work
[00:53] <Kreyren> it will mess up with grub and linux too when kept in one system
[00:53] <Kreyren> the only good solution i am aware of is xen
[00:53] <arraybolt3> Kreyren: No offense, but do you even know what you're saying?
[00:54] <Kreyren> yesh i have 15 years of experience in computer science and deal with windows boot manager twice a week in linux room on matrix xD
[00:54] <arraybolt3> It seems like you've confused the operating system, the firmware, and a random hypervisor that isn't even involved here.
[00:55] <arraybolt3> Guest76: Are you still there?
[00:56] <arraybolt3> Guest76: Is there any entry other than "Windows Boot Manager" in your boot menu?
[00:56] <Kreyren> is that a windows issue? and if it's dual booting windows and linux distro then xen is the only robust solutio nthat doesn't break to my knowledge
[00:56] <Guest76> NVme: Intel SSD
[00:56] <Guest76> and PCI lan
[00:56] <arraybolt3> Kreyren: This is getting annoying. If you have a tangible suggestion to get things going, please share it. Otherwise, please stop interfering.
[00:56] <Kreyren> <Kreyren> howddya do power management things
[00:56] <Kreyren> <Kreyren> my friend's ubuntu starts to rush fans on 100% after he plugs in the
[00:56] <Kreyren> then tell me how to fix this~
[00:57] <arraybolt3> Guest76: Hmm. Try selecting the NVMe SSD and see if that works.
[00:57] <arraybolt3> Kreyren: Have you looked into TLP?
[00:57] <Guest76> issue persists...
[00:57] <Kreyren> arraybolt3, dunno what TLP is
[00:58] <arraybolt3> Kreyren: https://github.com/linrunner/TLP It's available in Ubuntu's software repositories.
[00:58] <Guest76> its a battery power management utility
[00:59] <arraybolt3> Guest76: Hmm. If you go into your BIOS setup, is there anything about the system's boot order in there? And if so, do you see an entry called "Customized Boot"?
[00:59] <Kreyren> told em to try thanku~
[00:59] <Guest76> loading up bios now
[00:59] <Guest76> Startup Tab...
[01:00] <Guest76> Boot Priority Order
[01:00] <Guest76> 1. Windows Boot Mgr
[01:00] <Guest76> 2. USB CD
[01:00] <Guest76> 3. USB FDD
[01:00] <Guest76> 4 NVME Intel SSD
[01:00] <Guest76> 5. ATA HDD0
[01:00] <arraybolt3> Oy. If you need to post multiple lines to the channel, you can use something like dpaste.com to store them and then send a link to them.
[01:01] <arraybolt3> (An anti-flooding bot muted you for 60 seconds, sorry for the inconvenience. Sometimes people paste HUUUUGE things that take hours to clear out, the bot helps with that.)
[01:02] <arraybolt3> OK, should be unmuted now.
[01:02] <Guest76> oops sorry about that lol
[01:03] <arraybolt3> Heh, no problem. If you could paste that same list into a pastebin and send it via a link, that would be awesome.
[01:03] <Guest76> Options are Windows Boot Mgr, USB CD, USB FDD, NVME0 Intel SSD, ATA HDD0, USB HDD, PCI LAN
[01:03] <arraybolt3> Hmm. Is there *anything* about "Customized Boot" in the BIOS? Even in a place other than the boot menu?
[01:04] <Guest76> I recall seeing that somewhere,... but not sure where to find it... one moment while I poke around
[01:04] <Guest76> There is a "Boot Order Lock"
[01:04] <arraybolt3> That's probably not what we want.
[01:04] <arraybolt3> In fact that might complicate things :P
[01:05] <arraybolt3> (also, is this a dual-boot configuration, or did you replace the existing OS with Ubuntu entirely?)
[01:05] <Guest76> Replacing entirely
[01:05] <Guest76> Not a dual boot
[01:05] <arraybolt3> K, then this should be doable without too much trouble once we find the right option. If it's really stubborn, there's another workaround.
[01:07] <Guest76> UEFI Bios Version N1WET68W 1.47
[01:07] <Guest76> Not sure if that helps
[01:08] <arraybolt3> Sigh. OK. Let's abandon this workaround and try to get the boot files where the EFI expects them to be, since it apparently can't figure out where they already are.
[01:08] <arraybolt3> Can you boot into a live ISO?
[01:09] <Guest76> Sure can
[01:09] <arraybolt3> Guest76: OK, oh wait before we do that...
[01:09] <arraybolt3> (sigh, I forgot a step :P)
[01:09] <arraybolt3> Guest76: This might require that we turn Secure Boot off.
[01:10] <arraybolt3> Is that possible on your system, or is Secure Boot locked on?
[01:10] <Guest76> not locked, just disabled it
[01:10] <Guest76> booting into live iso
[01:10] <arraybolt3> Nice, then hopefully this next workaround should work.
[01:11] <Guest76> Start Linux Mint 21.1 Cinnamon 64 Bit or Start Linux Mint 21.1 Cinnamon 64 bit (Compatability mode), OEM Install (for manufacturers) Boot from next volume, UEFI Firmware Settings?
[01:12] <Guest76> Oh, at the beginning I was trying to get it to work with kubuntu, so i gave up and tried it with Mint, but same issue, hence why at the beginning i mentioned i was installing kubuntu, and now its Mint
[01:13] <arraybolt3> Guest76: Hmm... this should be the same on either Ubuntu or Mint, but Mint *may* have some differences from Ubuntu that might make this not work.
[01:13] <Guest76> I can go flash the USB with Kubuntu again
[01:13] <Guest76> its no issue
[01:13] <arraybolt3> OK. If that's OK, that would make things more reliable.
[01:14] <Guest76> set rufus to GPT right?
[01:15] <arraybolt3> I don't use Rufus, so I don't really know that answer :P I think DD mode is supposedly the best way to do this though.
[01:16] <arraybolt3> (Though I don't know how to select DD mode in Rufus, I just know that that's an option at some point.)
[01:26] <Guest76> ok,... loading up kubuntu live iso
[01:27] <Guest76> are you wanting me to basically reinstall kubuntu?
[01:27] <Guest76> or try it?
[01:28] <arraybolt3> Guest76: Just try it.
[01:28] <LikWidChzz> Hello folks.
[01:28] <arraybolt3> We're just going to look at the EFI files and see what we need to do to make it boot.
[01:28] <arraybolt3> LikWidChzz: o/
[01:29] <Guest76> OK
[01:29] <LikWidChzz> You just said a word on why I joined, EFI. SO dumb question. How do you install ubuntu without UEFI enabled?
[01:29] <Guest76> open terminal?
[01:30] <arraybolt3> Guest76: Yep.
[01:30] <arraybolt3> LikWidChzz: Ubuntu installs on BIOS systems just fine. It will make an EFI partition for reasons I do not understand, but it should just install.
[01:30] <arraybolt3> LikWidChzz: If you want to install without UEFI, make sure that you have Legacy mode enabled in your BIOS so that the system can successfully boot from a BIOS installation of Ubuntu.
[01:30] <LikWidChzz> well it does just install, no issue there, however it doesnt boot :)
[01:31] <arraybolt3> LikWidChzz: Is your system BIOS?
[01:31] <Bashing-om> LikWidChzz: How the installers boot is determined by the firmware (Bios).
[01:31] <LikWidChzz> yeah ive been monkeying around with that all afternoon
[01:31] <LikWidChzz> usually installing any linux isnt this much of a PITA.
[01:31] <arraybolt3> LikWidChzz: Hmm... can you boot into a live ISO and run "[ -d /sys/firmware/efi ] && echo UEFI || echo BIOS" in a terminal (without the quote marks)?
[01:31] <arraybolt3> That will tell us if the system is booted in BIOS or EFI mode.
[01:32] <LikWidChzz> good call out, one sec
[01:32] <LikWidChzz> pr to set your expectations, give me multiple secs.
[01:32] <arraybolt3> :) No problem, booting an ISO always takes multiple secs.
[01:32] <LikWidChzz> jeebus what a time suck 2.0 today.
[01:33] <arraybolt3> Guest76: Once you have a terminal open, can you run "lsblk | nc termbin.com 9999" and send the link that spits out so I can see your partition layout?
[01:34] <LikWidChzz> its not how the usb bootable iso was built was it?
[01:35] <arraybolt3> LikWidChzz: No. It's always (that I've heard of) related to the boot mode used when you first boot the ISO.
[01:35] <LikWidChzz> my install failed fyi nothing new, booting into live again and ill open a shell.
[01:35] <LikWidChzz> okay this is an oldy laptop fyi
[01:35] <LikWidChzz> its funny, it booted ONCE in uefi mode on its own and I rebooted and the finger
[01:35] <arraybolt3> (EFI systems can oftentimes boot in BIOS mode on accident if you select the wrong option in the boot menu when booting the ISO. Basically if we see a mismatch between your system type and your partition layout, you should be able to boot using the right mode, then reinstall, and it should work.)
[01:36] <LikWidChzz> did something change between this version of unbuntu and the last?
[01:37] <arraybolt3> It depends on what version of Ubuntu you're booting.
[01:37] <LikWidChzz> 22.04
[01:37] <arraybolt3> In 22.04, there was a change made (I believe) that now both BIOS and EFI systems use GRUB to boot the ISO.
[01:37] <arraybolt3> Previously ISOLINUX was used for BIOS systems.
[01:37] <arraybolt3> However this shouldn't cause this problem.
[01:37] <LikWidChzz> I love antiquated shit thou.
[01:37] <LikWidChzz> okay booted into live and will run this command, one secs
[01:38] <arraybolt3> (Just as a sidenote, we generally try to keep the language family-friendly in here for the sake of other users.)
[01:38] <LikWidChzz> Appologies sir!
[01:40] <LikWidChzz> that command doesnt work, I run it and it just writes BIOS to the screen
[01:40] <LikWidChzz> [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS
[01:40] <arraybolt3> That actually did work :)
[01:40] <arraybolt3> It means your system is booted in BIOS mode.
[01:40] <LikWidChzz> lol well then.
[01:40] <arraybolt3> OK, can you run "lsblk | nc termbin.com 9999" and share the link it outputs?
[01:41] <arraybolt3> That will show me your partition layout and tell me if it installed in BIOS or EFI mode.
[01:41] <arraybolt3> (I'm suspecting it's installed in EFI mode.)
[01:42] <LikWidChzz> ooh hows about that
[01:42] <LikWidChzz> termbin.com/1bjw
[01:43] <LikWidChzz> this is the live boot enviroment btw
[01:43] <arraybolt3> Oh weird. That's a BIOS installation.
[01:43] <arraybolt3> (I can tell becaues of the tiny 1M partition at the beginning.)
[01:44] <LikWidChzz> well I made that with a custom install
[01:44] <LikWidChzz> frankly I am not attached to it and can start over.
[01:44] <arraybolt3> OK, lemme think...
[01:44] <LikWidChzz> want me to do the basic install wiping everything, then run this syntax again?
[01:44] <LikWidChzz> I did some custom partitions btw thinking it would be the fix
[01:44] <arraybolt3> Let's try a basic install wiping everything first, then reboot and see if it works.
[01:45] <LikWidChzz> sure
[01:45] <arraybolt3> (Also check and make very sure that EFI mode is disabled in your BIOS if it fails to boot.)
[01:45] <LikWidChzz> its an HP8560w
[01:46] <LikWidChzz> selecting the 3rd option "erase disk and install ubuntu"
[01:49] <LikWidChzz> well its choochin away now. Its kind of bonkers, I have never had this much problem installing ubuntu since its inception
[01:50] <Bashing-om> !uefi | LikWidChzz
[01:50] <LikWidChzz> I dont want anything to do with UEFI though.
[01:52] <Bashing-om> LikWidChzz: Uh Huh -- me 2, We gots to tell the firmware we wants to boot always non-EFI :D
[01:52] <LikWidChzz> maybe im old and I dont like a lot of new stuff or changes.
[01:52] <LikWidChzz> weak sauce.
[01:53] <arraybolt3> EFI would be great if it didn't break so frequently :P
[01:53] <LikWidChzz> hah someone should contact them and have them make a new iso that has nothing to do with it for us old farts.
[01:54] <LikWidChzz> arraybolt3, its installing btw, shouldnt be too much longer before I try and reboot.
[01:55] <arraybolt3> Nice :)
[01:55] <arraybolt3> LikWidChzz: btw if you want an ISO that might handle BIOS a bit better, Lubuntu uses a more traditional method of installation for BIOS systems that might work if this fails.
[01:55] <LikWidChzz> whats that?
[01:56] <Bashing-om> LikWidChzz: Got this Asus box I moved my old drives from obsolete system - took me some time to figure out how to set to boot CCSM mode.
[01:56] <arraybolt3> It's an official flavor of Ubuntu that uses the LXQt desktop rather than GNOME.
[01:56] <arraybolt3> https://lubuntu.me/
[01:56] <LikWidChzz> Oh well the gnome desktop is fine
[01:57] <arraybolt3> It also features a different installer that does things a bit differently (for instance it uses a traditional MBR partition table and doesn't make an EFI partition on BIOS systems).
[01:57] <arraybolt3> Whereas Ubuntu's installer will try and make BIOS systems work with GPT (which usually works), and also makes an EFI partition for reasons I do not understand.
[01:57] <arraybolt3> Anyway, we'll try and make Ubuntu work first, Lubuntu is just a possible other solution if this doesn't work.
[01:58] <LikWidChzz> well the other option is an older version and never upgrade
[01:58] <LikWidChzz> getting into the live boot again, one momento
[02:00] <pycurious> My bluetooth mouse stopped working on 20.04LTS after the last reboot. The gnome bluetooth dialog shows bluetooth to be off. On dmesg I see the following error : [    6.772914] Bluetooth: hci0: Reading Intel version command failed (-110), [    6.772920] Bluetooth: hci0: command 0xfc05 tx timeout - systemctl status bluetooth.service - shows service running. Any ideas on how to fix this and what went wrong?
[02:02] <LikWidChzz> arraybolt3, -- take a look at this. From an Ubuntu installed on the HDD (neither liveCD nor liveUSB), open a terminal (Ctrl+Alt+T), then type the following command:
[02:02] <LikWidChzz>  [ -d /sys/firmware/efi ] && echo "EFI boot on HDD" || echo "Legacy boot on HDD
[02:03] <LikWidChzz> I am in the live envbiroment and cant boot off a drive after install.
[02:03] <arraybolt3> LikWidChzz: OK, so it still won't work, hmm...
[02:04] <LikWidChzz> there is no change, it cant boot on its own so not sure if that command you had me run is of any use.
[02:04] <arraybolt3> It just showed whether it was a BIOS or EFI boot for debugging.
[02:05] <arraybolt3> I'm guessing something about the "bios_grub" partition just isn't working on this system.
[02:06] <arraybolt3> Let me see if there's a way to install Ubuntu Desktop with a normal MBR setup.
[02:08] <LikWidChzz> gracias
[02:10] <arraybolt3> Gah. I don't have an Ubuntu 22.04 ISO downloaded >_< Hold on, this may take a while...
[02:10] <LikWidChzz> https://termbin.com/r1wfx
[02:12] <LikWidChzz> what a pain
[02:14] <Guest76> back
[02:14] <Guest76> sorry
[02:14] <Guest76> had to feed my toddler and change his diaper
[02:15] <Bashing-om> LikWidChzz: My obsevation - if ya booting bios mode then that sda1 partition is not needed. Is that the issue here ?
[02:15] <arraybolt3> Guest76: No problem :)
[02:16] <arraybolt3> Bashing-om: Isn't that sda1 partition the bios_grub partition? I thought that was required with GPT systems.
[02:16] <Guest76> https://termbin.com/o9bw
[02:16] <LikWidChzz> I have no idea Bashing-om im just doing the default install
[02:17] <Bashing-om> arraybolt3: That is a thought ~ not sure as I have not done a GPT install :(
[02:17] <LikWidChzz> Ill just install UEFI and try booting again to it
[02:18] <LikWidChzz> or enable UEFI and try it again with the install
[02:18] <logranrun> I have a weird one, I just installed Ubuntu 22.04, with the lvm option and chose encrypted disk. when I switch to the NVIDIA drivers, I can't see the prompt after grub launched the OS. If I type in the password it does in fact boot, but I can't see the prompt. is there any work around for this?
[02:18] <arraybolt3> LikWidChzz: I'm downloading the 22.04.1 ISO at the moment and seeing if I can make things work.
[02:18] <LikWidChzz> okay cool thank you so much for your assistance.
[02:20] <logranrun> I tried the disable graphical terminal line, GRUB_TERMINAL=console, but that didn't do anything
[02:22] <Guest76> arraybolt3 did you check out the termbin?
[02:24] <arraybolt3> Guest76: Not yet, actually ,lemme do that.
[02:24] <arraybolt3> (Sorry, got distracted.)
[02:25] <Guest76> no its fine, i just didnt know if you saw I posted it
[02:26] <arraybolt3> Guest76: OK, so I'm thinking, let's just do this the easy way. Can you do "sudo mount /dev/nvme0n1p1 /mnt" and then "ls -R /mnt"?
[02:27] <arraybolt3> Er, "ls -R /mnt | nc termbin.com 9999"
[02:29] <Guest76> "/,mnt: (Next Line) EFI
[02:30] <Guest76> arraybolt3 https://termbin.com/zzsb7
[02:31] <arraybolt3> Guest76: OK, this may be a bit drastic, but can you now do "sudo mv /mnt/EFI/BOOT /mnt/EFI/bootBackup"?
[02:31] <Guest76> What does that do?
[02:32] <Guest76> done
[02:32] <LikWidChzz> it makes a copy of your boot file.
[02:32] <arraybolt3> That should get old, possibly interfering boot files out of the way without deleting them.
[02:32] <Guest76> Ok now what?
[02:32] <arraybolt3> Next, can you do "efibootmgr | nc termbin.com 9999" and send that link?
[02:33] <arraybolt3> That will let me see if the next step is likely to work or not.
[02:33] <Guest76> https://termbin.com/xkgc
[02:35] <arraybolt3> Holy smoke.
[02:35] <arraybolt3> Umm... ok so we will have to do something different here.
[02:35] <Guest76> what happened?
[02:36] <arraybolt3> Lenovo overloaded the NVRAM of your system and looks like it didn't let the ubuntu boot entry get in.
[02:37] <arraybolt3> OK, can you do "cp -R /mnt/EFI/ubuntu /mnt/EFI/BOOT"?
[02:37] <arraybolt3> And then "cp /mnt/EFI/BOOT/grubx64.efi /mnt/EFI/BOOT/bootx64.efi".
[02:37] <LikWidChzz> So the thing boots in UEFI mode now, but you have to select the boot EFI file
[02:38] <arraybolt3> LikWidChzz: Do you have a Customized Boot option in your BIOS?
[02:38] <LikWidChzz> like to select the boot file at boot?
[02:38] <arraybolt3> LikWidChzz: It might be possible to point the EFI to the EFI\ubuntu\shimx64.efi file and get it to boot automatically.
[02:38] <arraybolt3> Yeah.
[02:38] <LikWidChzz> ehhh good q, lemme poke.
[02:39] <arraybolt3> Guest76: After executing the commands I sent to you, try rebooting and see what happens. It *should* boot into Ubuntu.
[02:40] <Guest76> Hmmmmm
[02:40] <Guest76> its booting into Linux mint
[02:41] <Guest65> Hello, is there a reason why steam takes a very long time to 'process shaders'? It takes half an hour and the computer throws errors during the process, is generally unresponsive. If I click skip the computer locks up completely and I have to unplug it.
[02:41] <Guest76> yeah thats right, i forgot to install kubuntu before i loaded into that live environment
[02:41] <Guest76> but its still working, im at the login screen
[02:41] <LikWidChzz> arraybolt3, doesnt look like it
[02:41] <Guest76> Im OK with Mint :)
[02:42] <LikWidChzz> im up for your idea to try non EFI boot setup, I dont like how this works even though it does boot
[02:42] <arraybolt3> Guest76: Meh, no problem, if it boots, it boots :)
[02:42] <Guest76> So what did I do wrong when initially installing these linux distros?
[02:42] <arraybolt3> Guest76: No, waht you did was probably fine.
[02:42] <arraybolt3> Hardware manufacturers frequently don't adhere to standards that make things work right.
[02:43] <arraybolt3> Basically we just had to make Mint put its files where the UEFI can find them, since the UEFI refused to do things the right way.
[02:43] <Guest76> If I ever have to reinstall the linux distro again... do I have to repeat all the same commands? Which commands are the most relevant commands so I can save it for my own personal KB?
[02:43] <LikWidChzz> arraybolt3, did you get anywhere with making an MBR bootable 22.04?
[02:43] <arraybolt3> Guest76: I'll send a pastebin with the relevant "fix it" commands.
[02:44] <Guest76> (I have a webserver running at home, and on the locally served site, I have webpages for how to do certain complicated tasks that I might occasionally have to do, but might forget how to)
[02:44] <arraybolt3> LikWidChzz: Still downloading :(
[02:44] <LikWidChzz> on your question about pointing to the right file you made a comment about the bootable file
[02:44] <Guest76> Most of my KBs articles I wrote for myself are for fixing issues with HomeAssistant
[02:45] <Guest76> BTW, Thank you so much for your help :D
[02:45] <Guest76> I wonder if Linux mint supports the fingerprint reader on this badboy
[02:46] <LikWidChzz> so in the EFI directory do I need to make a symbolic link to this shimx64.efi file?
[02:47] <arraybolt3> Guest76: https://dpaste.com/9FKHNN57D
[02:47] <arraybolt3> LikWidChzz: You can't do symbolic links sadly, the EFI partition is FAT32.
[02:47] <arraybolt3> LikWidChzz: You can copy stuff if you need it elsewhere.
[02:48] <LikWidChzz> okay so in the EFI directory is there a file that I can copy to auto load
[02:48] <arraybolt3> LikWidChzz: You might try just enabling EFI mode and then reinstalling, so that the right entry is made in your system's NVRAM to boot Ubuntu automatically. That will save you (hopefully) from having to repeat what me and Guest76 just had to do because of his buggy UEFI.
[02:48] <LikWidChzz> I did that.
[02:48] <arraybolt3> LikWidChzz: Oh.
[02:48] <arraybolt3> OK, well: https://dpaste.com/9FKHNN57D
[02:48] <arraybolt3> LikWidChzz: ^ That has the instructions for putting the GRUB bootloader where even buggy EFI systems can find it.
[02:49] <LikWidChzz> ahh okay lemme give this a whirl
[02:49] <LikWidChzz> if it fails im installing 21.10
[02:49] <Guest65> How do I troubleshoot performance problems? I had no problem playing bannerlord yesterday before I rebooted, but today it is hitching and skipping constantly
[02:50] <arraybolt3> LikWidChzz: This shouldn't fail - if the EFI can't find the file where those instructions put it, it shouldn't even call itself a UEFI BIOS.
[02:50] <LikWidChzz> well it seems like the folks who put together this installed kind of hosed it :\
[02:50] <LikWidChzz> *installer.
[02:51] <arraybolt3> The installer works just fine on most systems. Manufacturers are just really bad at following standards, leading to these kinds of hacks.
[02:52] <LikWidChzz> on your pastebin link it sounds like I can just do the last two commands
[02:52] <arraybolt3> LikWidChzz: You have to mount the installed system's EFI system partition to be able to modify it.
[02:52] <LikWidChzz> right I already did that
[02:52] <arraybolt3> And if /mnt/EFI/BOOT already exists (which it probably will), you have to move it.
[02:52] <LikWidChzz> oh well lol ignore what I said before :)
[02:52] <arraybolt3> If you've already done that, then yeah, the last two commands are all you need.
[02:54] <LikWidChzz> btw I dont have a grub file listed in /boot
[02:54] <Guest65> I have run the top command, it is the closest thing I can find to the task manager in windows. there is a program called apport-gtk  taking up 100% of cpu
[02:54] <arraybolt3> LikWidChzz: On the installed system, or the live ISO?
[02:55] <LikWidChzz> the installed system
[02:55] <arraybolt3> ?!
[02:55] <arraybolt3> So /boot/grub doesn't exist?
[02:55] <LikWidChzz> no
[02:55] <arraybolt3> Alright, hold up. Something's wrong then.
[02:55] <arraybolt3> You might have a corrupted ISO.
[02:55] <LikWidChzz> root@elitebook:/mnt/EFI/BOOT# ls
[02:55] <LikWidChzz> BOOTX64.EFI  fbx64.efi  mmx64.efi  ubuntu
[02:55] <LikWidChzz> root@elitebook:/mnt/EFI/BOOT#
[02:55] <arraybolt3> Oh. That's actualy normal.
[02:55] <arraybolt3> LikWidChzz: You're looking at the installed system's EFI system partition.
[02:55] <LikWidChzz> right
[02:56] <arraybolt3> /boot/grub should be located in the /boot partition or the / partition, which are different.
[02:56] <arraybolt3> You're looking at what usually is /boot/efi.
[02:56] <LikWidChzz> look at your pastebin link again
[02:57] <LikWidChzz> it doesnt show you copying files from /boot
[02:57] <Guest65> I tried running a few commands that apparently stop the apport-gtk 'service', but it is still running and consuming all the system resources
[02:58] <arraybolt3> LikWidChzz: Right. We are intentionally changing things in /boot/efi, because that's where the bootloader is installed on EFI systems.
[02:58] <arraybolt3> You're used to BIOS systems, which work very differently in this regard.
[02:58] <LikWidChzz> Right, I am booted in EFI boot mode now
[02:59] <arraybolt3> We're just taking the bootloader from the location where it should work, and putting it in a different location so that the UEFI can find it since it seems reluctant to find it in the normal location.
[02:59] <arraybolt3> LikWidChzz: Are you booted into the main system, or an ISO file?
[02:59] <LikWidChzz> Right right I get that.
[02:59] <arraybolt3> I thought you were in an ISO file.
[02:59] <Guest76> Does Libera.chat do registered usernames?
[03:00] <LikWidChzz> I am booted in UEFI mode now on its own power. BUT the problem is I have to select a bunch of junk within the boot menu of my laptop and navigate to a UEFI file and boot to it in order for my system to start
[03:00] <arraybolt3> Guest76: You can register a username if you wish, and some channels require that you be registered in order to join, though not all of them.
[03:00] <arraybolt3> LikWidChzz: Oh, OK.
[03:00] <arraybolt3> LikWidChzz: So what commands have you run so far?
[03:00] <Guest76> Just making sure, its done at https://libera.chat/ right?
[03:00] <arraybolt3> Guest76: That's their website, you can find registration instructions there.
[03:00] <arraybolt3> The actual registration process is done in your IRC client.
[03:01] <arraybolt3> https://libera.chat/guides/registration
[03:01] <LikWidChzz> so what I am asking is, is there a default file name that boots in UEFI mode because if there is, Ill just copy the shimx64.efi
[03:01] <LikWidChzz>  to the "Default.file.that.boots.without.me.pressing.buttons"
[03:01] <LikWidChzz> grubx64.efi also exists
[03:01] <arraybolt3> LikWidChzz: Yes, it's /boot/efi/EFI/BOOT/bootx64.efi.
[03:01] <arraybolt3> However, SHIM looks for grubx64.efi in the same folder.
[03:01] <LikWidChzz> Im asking something dumb
[03:02] <arraybolt3> No, not at all.
[03:02] <LikWidChzz> Im sure the answer is so easy once I figure out how to ask it.
[03:02] <arraybolt3> Nah, I get it.
[03:02] <LikWidChzz> okay
[03:02] <LikWidChzz> which folder is it looking in?
[03:02] <arraybolt3> So the /boot/efi/EFI/BOOT folder is an "ultimate fallback" where the UEFI can find files if all else fails.
[03:02] <arraybolt3> And the file it will look for is /boot/efi/EFI/BOOT/BOOTX64.EFI.
[03:03] <arraybolt3> So if you copy shimx64.efi to there, it will find it.
[03:03] <arraybolt3> shimx64.efi requires grubx64.efi be in the same folder as it.
[03:03] <arraybolt3> So since /boot/efi/EFI/ubuntu is already set up all correct, you just copy /boot/efi/EFI/ubuntu to /boot/efi/EFI/BOOT.
[03:03] <LikWidChzz> copy the entire folder to the boot folder?
[03:03] <arraybolt3> Then you can copy /boot/efi/EFI/shimx64.efi to /boot/efi/EFI/bootx64.efi, and then the UEFI can find the shim.
[03:03] <arraybolt3> Yes. The entire folder.
[03:03] <LikWidChzz> thats free, I can do that one sec
[03:03] <arraybolt3> Then once the UEFI can find the shim, it can boot it, and then the shim can find GRUB and boot it.
[03:04] <Guest76> There.... now I got Synergy set up so I can control my laptop with the keyboard/
[03:04] <LikWidChzz> wait its already there
[03:04] <arraybolt3> And then GRUB can find the configuration file in the same folder and use it to find the real configuration file.
[03:04] <Guest76> and mouse from my desktop pc
[03:04] <arraybolt3> LikWidChzz: /mnt/efi/EFI/BOOT will probably have stuff there already.
[03:04] <LikWidChzz> root@elitebook:/mnt/EFI/BOOT/ubuntu# ls
[03:04] <LikWidChzz> BOOTX64.CSV  grub.cfg  grubx64.efi  mmx64.efi  shimx64.efi
[03:04] <Guest76> Literally like having another monitor, except that other monitor runs linux
[03:04] <arraybolt3> LikWidChzz: BOOTX64.**CSV**, not .EFI.
[03:04] <LikWidChzz> AHHHHHHH okay
[03:04] <LikWidChzz> blind.
[03:05] <arraybolt3> You need to do "sudo cp /boot/efi/EFI/BOOT/shimx64.efi /boot/efi/EFI/BOOT/bootx64.efi" and then POOF it should work.
[03:07] <LikWidChzz> whoosh I think your file names are incorrect.
[03:07] <arraybolt3> I mean this just worked a second ago for another user.
[03:07] <LikWidChzz> I am either dense or hangry.
[03:07] <arraybolt3> Did I typo?
[03:07] <arraybolt3> ls /boot/efi/EFI/BOOT
[03:07] <LikWidChzz> pause. doing now
[03:08] <LikWidChzz> root@elitebook:/boot/efi/EFI/BOOT# ls
[03:08] <LikWidChzz> BOOTX64.EFI  fbx64.efi  mmx64.efi  ubuntu
[03:08] <arraybolt3> Umm...
[03:08] <arraybolt3> ubuntu shouldn't be there :)
[03:09] <arraybolt3> ubuntu is supposed to *replace* /boot/efi/EFI/BOOT, not be inside it.
[03:09] <LikWidChzz> hold up a sec I am getting dumb
[03:09] <LikWidChzz> when the machine boots isnt it looking at /SDA2 the EFI partition?
[03:09] <arraybolt3> I believe so.
[03:10] <LikWidChzz> okay thats what I booted the system on but I had to select an EFI file manually with HPs stupid menu
[03:10] <arraybolt3> I think we got confused - the ubuntu folder contains an EFI bootloader "realm", if you will.
[03:10] <arraybolt3> The UEFI can't find that realm for some reason, because it's broken.
[03:10] <arraybolt3> However it can find the /boot/efi/EFI/BOOT realm.
[03:11] <arraybolt3> So we need to move whatever's at /boot/efi/EFI/BOOT out of the way, and then rename /boot/efi/EFI/ubuntu to /boot/efi/EFI/BOOT, so that the bootloader can find it.
[03:11] <arraybolt3> So, execute these commands, one at a time, and I think it should fix things.
[03:12] <LikWidChzz> so confused here.
[03:12] <arraybolt3> EFI is confusing.
[03:12] <LikWidChzz> your pastebin link look at line 2
[03:12] <arraybolt3> The pastebin was designed for if you were in a live ISO.
[03:12] <arraybolt3> Forget the pastebin for now, the paths are going to be wrong if you're not in a live ISO.
[03:12] <LikWidChzz> okay pause.
[03:12] <LikWidChzz> I have /dev/sda2 mounted to /mnt
[03:13] <arraybolt3> Yes.
[03:13] <LikWidChzz> one line at a time, what do I need to do?
[03:13] <arraybolt3> ls /mnt
[03:13] <arraybolt3> Let's see what's in there so we know what we have mounted there.
[03:13] <LikWidChzz> I have a single folder called EFI there
[03:14] <arraybolt3> ls /boot/efi
[03:14] <arraybolt3> Does that look the same?
[03:14] <LikWidChzz> lemme pastebin
[03:14] <LikWidChzz> https://pastebin.com/Xusq29Uq
[03:15] <arraybolt3> OK, very good.
[03:15] <arraybolt3> Alright, a few more commands to take stock of what we're looking at:
[03:15] <arraybolt3> ls /boot/efi/EFI
[03:15] <LikWidChzz> sure
[03:15] <arraybolt3> ls /mnt/EFI
[03:15] <arraybolt3> lsblk
[03:15] <arraybolt3> Pastebin the terminal after running those.
[03:16] <arraybolt3> (I want to be absolutely sure that any deletion commands or whatnot are safe so that we don't break things.)
[03:16] <LikWidChzz> https://pastebin.com/51nSmB4Q
[03:16] <arraybolt3> Oh, perfect.
[03:16] <LikWidChzz> Im confused what files do what here once I nail that im sure ill be laughing because im just derping out here.
[03:17] <arraybolt3> I think I see everything that needs done, I'll just send the commands one at a time and hopefully it should work.
[03:17] <LikWidChzz> yes deals
[03:17] <arraybolt3> I'll send comments with each command so that you can see what it does.
[03:17] <arraybolt3> sudo rm -rf /mnt/EFI/BOOT/ubuntu   # Remove the copied folder since we put it in the wrong location - DO NOT MAKE A TYPO HERE
[03:17] <johnny_Linux> wow, lot goin there
[03:18] <LikWidChzz> done
[03:18] <LikWidChzz> the ubuntu folder in mnt is removed
[03:18] <arraybolt3> sudo mv /mnt/EFI/BOOT /mnt/EFI/bootBackup   # The current contents of the BOOT folder are probably not correct, but they might be useful later, so move them without deleting them.
[03:19] <LikWidChzz> dpme
[03:19] <LikWidChzz> done.
[03:19] <LikWidChzz> frankly I didnt need to back it up but okay.
[03:19] <arraybolt3> sudo cp /mnt/EFI/ubuntu /mnt/EFI/BOOT   # The UEFI can't seem to find the ubuntu boot files, so put them in the BOOT location where the bootloader absolutely can find them.
[03:19] <arraybolt3> Er...
[03:19] <arraybolt3> I missed an -R :-/
[03:19] <arraybolt3> sudo cp -R /mnt/EFI/ubuntu /mnt/EFI/BOOT   # The UEFI can't seem to find the ubuntu boot files, so put them in the BOOT location where the bootloader absolutely can find them.
[03:20] <LikWidChzz> the ubuntu directory dosent exist you had me RM RF it above
[03:20] <arraybolt3> LikWidChzz: It's /mnt/EFI/ubuntu, not /mnt/EFI/BOOT/ubuntu.
[03:20] <LikWidChzz> lolol I hosed it
[03:20] <arraybolt3> :) No problem, we have a backup! \o/
[03:21] <arraybolt3> sudo cp -R /mnt/EFI/bootBackup/ubuntu /mnt/EFI/BOOT   # Get the ubuntu boot files out of the backup and put them in the BOOT location where the UEFI can find them.
[03:21] <arraybolt3> (And now am I so glad we moved that folder rather than nuking it)
[03:22] <johnny_Linux> interesting
[03:22] <LikWidChzz> okay thats it
[03:22] <LikWidChzz> reboot?
[03:22] <arraybolt3> LikWidChzz: Not yet.
[03:22] <arraybolt3> ls /mnt/EFI/BOOT   # Pastebin this so I can see if things look right
[03:22] <LikWidChzz> sure
[03:23] <LikWidChzz> root@elitebook:/mnt/EFI/BOOT# ls
[03:23] <LikWidChzz> BOOTX64.EFI  fbx64.efi  mmx64.efi  ubuntu
[03:23] <arraybolt3> ls /mnt/EFI/BOOT/ubuntu   # Pastebin this too please
[03:23] <LikWidChzz> BOOTX64.CSV  grub.cfg  grubx64.efi  mmx64.efi  shimx64.efi
[03:23] <arraybolt3> OK.
[03:24] <LikWidChzz> is that good or bad
[03:24] <arraybolt3> Please read the commands carefully and type them exactly, because it looks like you're probably typing things you think I should have typed that I intentionally didn't type.
[03:24] <arraybolt3> We have all the files, we just still don't have them in the right places.
[03:25] <arraybolt3> sudo mv /mnt/EFI/BOOT/ubuntu /mnt/EFI/ubuntu   # Move the ubuntu boot files to where they used to be temporarily
[03:25] <LikWidChzz> done
[03:25] <arraybolt3> ls /mnt/EFI    # Paste into chat so I can see what things look like currently
[03:26] <LikWidChzz> BOOT  BOOTBackup  ubuntu
[03:27] <arraybolt3> ls /mnt/EFI/BOOTbackup   # Just to be sure before we nuke this folder since we probably don't need it
[03:27] <LikWidChzz> okay
[03:27] <LikWidChzz> BOOTX64.EFI  fbx64.efi  mmx64.efi  ubuntu
[03:27] <arraybolt3> ls /mnt/EFI/BOOT   # Also would like to check this folder
[03:28] <LikWidChzz> BOOTX64.EFI  fbx64.efi  mmx64.efi
[03:28] <arraybolt3> Ok, interesting. That changes things a bit.
[03:29] <arraybolt3> sudo rm -rf /mnt/EFI/BOOT   # This doesn't appear to have anything we need. Please be careful to delete exactly this folder, not BOOTBackup or ubuntu.
[03:29] <LikWidChzz> done
[03:30] <arraybolt3> sudo cp -R /mnt/EFI/ubuntu /mnt/EFI/BOOT   # Now we can put the ubuntu boot files where the UEFI can find them.
[03:30] <LikWidChzz> done
[03:30] <johnny_Linux> killer
[03:30] <arraybolt3> ls /mnt/EFI/BOOT   # One more check to see if we need to copy a boot file
[03:31] <LikWidChzz> BOOTX64.CSV  grub.cfg  grubx64.efi  mmx64.efi  shimx64.efi
[03:31] <arraybolt3> sudo cp /mnt/EFI/BOOT/shimx64.efi /mnt/EFI/BOOT/BOOTX64.EFI   # Copy the shim to the fallback bootloader location - this should finally be the last step.
[03:32] <LikWidChzz> done
[03:32] <arraybolt3> reboot   # And let's see if it worked!
[03:32] <johnny_Linux> woohoo
[03:32] <johnny_Linux> great job
[03:32] <LikWidChzz> SO question now. It seems like the default EFI file that boots is BOOTX64.EFI correct?
[03:32] <arraybolt3> johnny_Linux: Well don't congradulate me yet - we still have to see if it worked.
[03:33] <LikWidChzz> lemme see if this dumb thing works now.
[03:33] <arraybolt3> LikWidChzz: Correct. EFI\BOOT\BOOTX64.efi is an ultimate fallback file that is booted if no other boot file can be found.
[03:33] <LikWidChzz> and when the normal installer installed it its a .csv file in that location correct?
[03:33] <arraybolt3> It wasn't installed as a .CSV file, that's a data file used by BOOTX64.efi, I believe.
[03:34] <johnny_Linux> I have a new tomahawk 550 board.. and those people told me >this bios is as is and if you dont like it.. too bad.
[03:34] <arraybolt3> BOOTX64.EFI is the fallback boot file, BOOTX64.CSV is a data file it can use depending on what exactly that bootloader is, IIUC.
[03:35] <LikWidChzz> Yeah looks like its booting now
[03:35] <arraybolt3> \o/
[03:35] <LikWidChzz> I feel like I need to do that another 10x tommrow on my own
[03:35] <arraybolt3> Use a VM with EFI mode enabled (GNOME Boxes is great for this), that wasy you can break things without fear.
[03:36] <LikWidChzz> well I can break things with a real laptop too lol.
[03:36] <arraybolt3> Heh, true.
[03:36] <LikWidChzz> okay so serious business now.
[03:36] <johnny_Linux> I appreciate the info, i am still learning the bios t from hell.. so. thanks.
[03:36] <LikWidChzz> when I got this thing installed the first time what file was missing?
[03:36] <arraybolt3> LikWidChzz: OK, so this answer is a bit complex.
[03:36] <johnny_Linux> very strange bios.. it changes with the wind.
[03:37] <arraybolt3> Technically, *nothing* was missing, except for the manufacturer's willingness to adhere to standards.
[03:37] <arraybolt3> What's supposed to happen is, there's some storage in the UEFI (called NVRAM) that holds boot entries.
[03:37] <LikWidChzz> can you put together like a tree diagram of what it looks like not working and then one that looks like working?
[03:37] <arraybolt3> Yeah, sure, one moment...
[03:37] <arraybolt3> Actually, this might take a bit, stay with me and I'll give you a pastebin when done.
[03:38] <LikWidChzz> cause I think thats where Im missing the thing. It sounds like my bios craps the bed because some default UEFI executable is not present and when we moved it all around from other spots it fixes itself
[03:38] <LikWidChzz> I should say the UEFI file is present, just not in the directory it needs to be.
[03:39] <johnny_Linux> good info folks.. have a great nite.. tootles. Ubuntu ROCKS. thanks
[03:42] <LikWidChzz> I agree good info, I need to break my system again and make sure I understand how it broke.
[03:43] <arraybolt3> Still putting together the tree, bear with me
[03:45] <LikWidChzz> You are good.
[03:47] <arraybolt3> Thanks, still building, this is coming out good.
[03:47] <LikWidChzz> I expect it to look like a 1995 webpage with every animated gif available on the internet.
[03:57] <LikWidChzz> with this thing we just got done doing, it seems as if the people who coded this ubuntu iso should impliment this automaticly.
[03:57] <arraybolt3> Whew. OK, here's the tome:
[03:58] <arraybolt3> https://dpaste.com/CS6ATCJ7B
[03:58] <pareidoliaC> Hello
[03:58] <LikWidChzz> Okay that looks great im going to stare at it a bit later.
[03:58] <LikWidChzz> TAB WILL REMAIN OPEN!
[03:59] <arraybolt3> LikWidChzz: :) Hope it helps! I told dpaste to not delete it for a year so hopefully it will stick around for you.
[03:59] <arraybolt3> You might want to save it if you want to refer to it after a year though.
[03:59] <LikWidChzz> lol they should fix it in ubuntu
[03:59] <LikWidChzz> seriously
[03:59] <arraybolt3> I don't disagree... BUT...
[03:59] <arraybolt3> Windows sometimes puts files in EFI\BOOT too. :-(
[04:00] <LikWidChzz> how many burritos do I have to buy someone
[04:00] <arraybolt3> So Ubuntu can't really just plow over that directory indiscriminately, or it could wreak havoc on Windows.
[04:00] <arraybolt3> LikWidChzz: As many as you want to eat. For yourself.
[04:00] <LikWidChzz> well I dont dual boot anything
[04:00] <arraybolt3> Yeah but lots of people do.
[04:00] <LikWidChzz> thats for the birds
[04:00] <LikWidChzz> BIRDS!
[04:00] <arraybolt3> :P
[04:00] <LikWidChzz> you going to be around tommrow?
[04:01] <arraybolt3> Maybe. I hope so.
[04:01] <LikWidChzz> okay cool, well thank you much for your assistance and dealing with me.
[04:01] <arraybolt3> Sure thing! Glad to be able to help!
[04:01] <LikWidChzz> are the files in /boot/efi like a backup?
[04:01] <arraybolt3> (You should have seen my first fights with Ubuntu and EFI, back with KXStudio 14.04. Oh my gosh, it took me days of agony.)
[04:01] <arraybolt3> LikWidChzz: /boot/efi is the entire EFI system partition.
[04:01] <LikWidChzz> that is old old version
[04:02] <arraybolt3> You'll notice I talk about the EFI directory - that's /boot/efi/EFI on a Linux system.
[04:02] <LikWidChzz> hold up
[04:02] <LikWidChzz> there is a partition with those files in it along with within root filesystem.
[04:02] <arraybolt3> Yes.
[04:02] <LikWidChzz> so which one is needed?
[04:02] <arraybolt3> OK, so things were a bit messy there...
[04:02] <LikWidChzz> my guess the partition
[04:03] <arraybolt3> When you boot from an ISO, /boot/efi has the ISO's EFI files. So to get to the system's EFI files, I had us mounting the system's EFI partition to /mnt.
[04:03] <arraybolt3> But when you boot an installed system, the files are automatically mounted to /boot/efi.
[04:03] <arraybolt3> So we actually had the EFI partition mounted *twice*, once in /boot/efi and once in /mnt.
[04:03] <LikWidChzz> oh they are like symlinked or something?
[04:03] <arraybolt3> Nope.
[04:04] <LikWidChzz> they are indeed two files though right?
[04:04] <LikWidChzz> copies?
[04:04] <arraybolt3> This is where Linux is a bit tricky.
[04:04] <arraybolt3> Directories just contain a part of a filesystem.
[04:04] <arraybolt3> So if you mount the same filesystem to two different directories...
[04:04] <arraybolt3> ...both directories show the same files and interacting with one will change the other.
[04:04] <LikWidChzz> ahh okay
[04:04] <arraybolt3> We could have just not mounted the EFI partition to /mnt and worked with /boot/efi the whole time.
[04:05] <arraybolt3> But I didn't realize you were in an installed system for a *while* and was acting as if we were in the ISO.
[04:05] <arraybolt3> Thus why we ended up working with /mnt.
[04:05] <LikWidChzz> no worries at all, it ended up working.
[04:05] <LikWidChzz> I need to stare at your diagram
[04:08] <arraybolt3> LikWidChzz: One thing you should be aware of....
[04:08] <arraybolt3> ...when you get a GRUB or shim update, it will probably put it under /boot/efi/EFI/ubuntu, since that's where things usually go.
[04:09] <arraybolt3> But that won't automatically copy to /boot/efi/EFI/BOOT, where you need them.
[04:09] <arraybolt3> So... lemme see how to add a script to automatically do that as needed.
[04:09] <LikWidChzz> lemme pause there for a bit I need go to bed. ill be around later.
[04:09] <pareidoliaR> hello
[04:09] <LikWidChzz> Again thank you much.. I need food, step away and come back to this when im a bit more recharged.
[04:10] <arraybolt3> LikWidChzz: Sure thing!
[04:10] <arraybolt3> Glad to help, good luck, and get good food!
[04:10] <LikWidChzz> thank you thankyou.
[04:24] <arraybolt3> I bet I understand why the system wasn't booting before - I think Ubuntu actually is designed to cope with a messed-up EFI, but that it doesn't cope well with a broken one.
[04:25] <arraybolt3> It looks like the fallback.efi file (or fbx64.efi) builds the boot entries, then tries to boot one, but in the event the UEFI doesn't allow it to create the boot entries, it fails to boot any of them. And then it boot loops.
[04:37] <massovittorio> test
[04:38] <arraybolt3> Tesu successful!
[04:40] <arraybolt3> *Test successful!
[04:41] <massovittorio> can't see what i'm typingneed to change color
[04:42] <massovittorio> thaank you
[04:56] <maximiliano> hello
[05:23] <pickanick> does ubuntu apt install {ssh,mosh,...} open ports in the devices' firewall or does that have to be done separately?
[05:44] <SuperLag> oerheks: re: age of my Ubuntu box, I should have just looked at my Digital Ocean panel for the VPS. It's existed for 6 years.
[07:12] <cyberwolf> hi, I block the update of the package "ubuntu-advantage-tools" so that Ubuntu Pro does not install on how much is it correct? :)
[07:28] <cyberwolf> m?
[08:01] <oerheks> !info ubuntu-advantage-tools
[08:02] <oerheks> if you have no wish for ESM or the kernel patch, not sure disabling is a good idea
[08:12] <cyberwolf> this package changes one file /etc/ubuntu-advantage/uaclient.conf to https://raw.githubusercontent.com/canonical/ubuntu-advantage-client/main/uaclient.conf
[08:14] <cyberwolf> as they say, you can disable sudo mkdir /etc/apt/apt.conf.d/off; and then sudo mv /etc/apt/apt.conf.d/20apt-esm-hook.conf /etc/apt/apt.conf.d/off;
[08:36] <pareidoliaR> hi
[08:41] <cyberwolf> hi
[08:50] <pareidoliaL> hi
[09:27] <billybob> Hi All
[09:27] <billybob> I am looking for some assistance in fixing a key binding. I have a bluetooth connected logitech MX keys for business - Swedish layout. All keys seem to be working fine apart from the print screen button which for some reason is registering as <Shift>S (from xev ) - Keycode 99 as seen on this link https://github.com/spxak1/weywot/blob/main/guides/mxkeys_linux.md
[09:27] <billybob> I am using ubuntu 22.04.
[09:27] <billybob> the problem seems to be very similar to this here :
[09:27] <billybob> https://askubuntu.com/questions/1291337/mixed-up-keys-on-a-scandinavian-keyboard-on-ubuntu-20-04.
[09:27] <billybob> I have been trying to look in dconf-editor for something but I am not exactly sure what I am looking for there.
[10:16] <Guest5> I cannot Switch User in Ubuntu 20.04. It takes me back to the login screen, but no other account can succesfully log in from there. It just cycles back the login screen.
[11:15] <inscw00table> So, I am having a surprising amount of difficulty dropping into a shell once an autoinstall is kicked off, I have tried any number of things.  What is the right way to do this?  Basically I just want to get in and see what it is doing so I can figure out why it's stalling.
[11:21] <adhi> test
[11:21] <inscw00table> pong
[11:21] <adhi> what is this?
[11:22] <adhi> i just try in my apps
[11:22] <inscw00table> This is IRC.
[11:23]  * inscw00table chuckles.  I appreciate that nick,  p y c u r i o u s.
[11:23] <adhi> oohh i see
[11:27] <tomreyn> inscw00table: you mentioned "autoinstall" without providing any context. i think autoinstall is currently only supported by the ubuntu server installer. there is #ubuntu-server.
[11:28] <inscw00table> Roger; yeah, sorry.  You are correct.
[11:28] <inscw00table> I will move my question, thank you.
[11:29] <sg17qzx> is most of people using IRC here?
[11:29] <sg17qzx> i just notice this apps in my xubuntu, and try to open it. and found this server
[11:30] <respawn> sg17qzx: this is ubuntu help channel if you need help ask here
[11:30] <respawn> sg17qzx: for general chat go to #ubuntu-offtopic
[11:30] <sg17qzx> okay thank you, i will explore it. feel's interesting
[12:19] <billybob> Can anyone help with the keyboard issue I have ?
[12:26] <WaV> If it appears to be an issue with Ubuntu, ask your question and if someone is around who is able to guide you in the right direction, they will answer.
[12:33] <Bugies> HI billybob what is a ps/2 keyboard?
[12:35] <billybob> not sure what you mean Bugies. Can you see my message above? i posted at around 3 hours ago
[12:38] <tomreyn> Bugies: ps/2 is an older keyboard connector (and i think signalling protocol, too)
[12:38] <tomreyn> it was common before usb
[12:40] <Bugies> ok , I'm thinking of something else
[12:41] <oerheks> billybob, you pasted multiple lines, we only got 3 or so, use a pastebin
[12:41] <oerheks> !paste
[12:41] <billybob> ok will do
[12:49] <WeeBey> Morning! Do you guys recommend upgrading from 22.04 to 22.10? I know it's not LTS but the new gnome sounds interesting--especially since I still have some of the bugs from 22.04 almost a year in.
[12:51] <oerheks> WeeBey, sure, but there is no rolling back.
[12:51] <WeeBey> oerheks, just in case I cloned my nvme last night with dd
[12:52] <WeeBey> I have never had to load an .img though so I have to assume that it works.
[12:58] <mario_> HAVING SOME PROBLEMS WITH WINE SOFTWARE CAN ANYONE HELP ME ONE ON ONE?
[12:58] <BluesKaj> Hi all
[12:59] <mario_> PLEASE
[12:59] <respawn> mario_: dont use caps
[12:59] <WeeBey> sounds like a problem with hardware too :D
[12:59] <respawn> mario_: and install from wine webpage the stable one
[12:59] <mario_> I HAVE VISION PROBLEMS
[12:59] <WeeBey> See? told you.
[13:00] <mario_> incredibly rude
[13:01] <WeeBey> Now I feel bad. I was joking </3
[13:02] <respawn> just some kid dont know how to fix problem and being anoying
[13:05] <WeeBey> So, when Ubuntu started using snap for Firefox, a lot people were upset. Including me. lol Now, I'm I am starting to like Snaps. What are your feelings about that?
[13:05] <WeeBey> I'm making a list of the software I have in case I need to format completely.
[13:06] <oerheks> snaps are great.
[13:06] <oerheks> and this channel is not suitable for such polls/discussion, join #ubuntu-discuss for that
[13:06] <WeeBey> I guess there's a performance decrease? Was that the main thing?
[13:06] <WeeBey> oerheks, so this is support-related questions? Ok. got it.
[13:08] <WeeBey> Ok, then. As part of my backups, if I want to save the added repos that i am using, I would make a backup of /etc/apt/sources.list.d/ ?
[13:09] <WeeBey> if I add the file into a clean install, will I be able to use it right away or does it need additional configuration?
[13:12] <oerheks> add those repos like you did the 1st time, if those are hosted on launchpad,  add-apt-repository ppa:something is enough to add and add the key.
[13:13] <oerheks> just a backup of  /etc/apt/sources.list.d/ is not enough, then you need to backup those keys too
[13:13] <WeeBey> oerheks, Yeah. I just saw that they were pointing to the key /usr/share/keyrings
[13:13] <WeeBey> Ok, perfect
[13:13] <oerheks> sudo apt-key list
[13:14] <WeeBey> oerheks, oh cool. Lots of keys in there that I don't need.
[13:14] <oerheks> https://help.ubuntu.com/community/Repositories/Ubuntu
[13:16] <WeeBey> Last question. I went from 21.10 to 22.04. Now I'm thinking of going to 22.10. The support will be 1 year, I believe correct? After which I would have 24.04  available ?
[13:16] <WeeBey> (LTS)
[13:17] <WeeBey> oh wait, no. I would have to upgrade to 23.10 I guess.
[13:24] <billybob> oerhek, ubottu here is the dpaste link https://dpaste.com/HGGSMM4BD
[13:25] <billybob> Ubuntu 22.04 - Logitech MX keys business (Swedish layout) - Print button not registering - Showing as Shift + S in xev
[13:27] <billybob> screenshot of xev - https://imgur.com/a/r3sLVGa
[13:31] <joo_> shortly after installing ubuntu on two different machines (with gnome3) i am experiencing that on login it is asking me to give access to an unknown application to the keyring with password, - thats on every login on both matchines (version 22.04) - any advice ?
[13:33] <WeeBey> joo_, did it crash maybe at some point?
[13:33] <WeeBey> I found that sometimes something crashes and it tries to report the crash.. then asks for password.
[13:34] <WeeBey> when i clear /var/crash the issue disappears.
[13:37] <joo_> WeeBey: that didnt happen ever as far as i remember, also the /var/crash fold is empty
[13:38] <WeeBey> hmm, dang. that was the low hanging fruit.
[14:59] <billybob> Hey. Anyone around to help with the keyboard issue i shared above ?
[15:00] <lotuspsychje> billybob: its okay to re-ask your issue once in a while so newly joined volunteers can pickup your question
[15:02] <billybob> Issue dpaste: https://dpaste.com/HGGSMM4BD
[15:02] <billybob> Ubuntu 22.04 - Logitech MX keys business (Swedish layout) - Print button not registering - Showing as Shift + S in xev
[15:02] <billybob> screenshot of xev - https://imgur.com/a/r3sLVG
[15:31] <kovital> Maybe the print button is just a shortcut to shift+s keycodes in fact.
[15:32] <kovital> if the layout detect the button press in xev, i'd say changing to another layout won't change that, but i can be wrong tho, you can still try another one and see in xev if it returns the same keycode.
[15:32] <FKAShinobi> Is there a way to setup a remote display like in Windows 10/11? The use case is casting to a TV in a board room.
[15:33] <kovital> billybob, try your keyboard on a android device since it's bluetooth like your phone to see if the keycode is the same, i think there must be an app on the playstore or f-droid or apkpure to display that.
[15:33] <kovital> or on another linux live USB distrib.
[15:34] <kovital> also on android, in a text editor: if you press the print button you should see an 'S' then
[15:34] <kovital> as long the layout is detected like on ubuntu.
[15:34] <kovital> +as
[15:34] <billybob> kovital, thanks for responding. I don't actually have an android device to hand. I do have another old laptop though, or a mac i could test on
[15:34] <billybob> would that work
[15:35] <lucas-arg> its compiz still developed?
[15:35] <kovital> yeah try on them, in a text editor the print button, maybe xev or alike is available on your mac too.
[15:35] <billybob> i could live boot another distro on the old laptop. Any specific one worth testing with ?
[15:37] <kovital> mint? or another popular one that has all the layout and things out of the box.
[15:37] <billybob> was thinking mint. but wasn't sure if it needed to be a totally different flavour.
[15:37] <billybob> as in, non debian based
[15:39] <Jeremy31> Mint should behave like Ubuntu for a keyboard
[15:55] <jhutchins> FKAShinobi: That's usually something that the browser handles.  My chrome browser will often be able to screencast to my Roku TV box.
[15:56] <jhutchins> FKAShinobi: AFIK "forwarding" the desktop is only possible with a VPN or with two Xwindows sessions.
[15:56] <jhutchins> (I don't think Wayland supports forwarding.)
[15:56] <FKAShinobi> jhutchins: Fair enough, but what if it's not a web site. I have some other applications that I want to display...
[15:57] <jhutchins> FKAShinobi: It would most likely be up to the application to support that.
[15:57] <jhutchins> When I forward YouTube video, the Roku actually connects to the stream and bypasses my computer.
[15:58] <amazoniantoad> I just want to game on ubuntu D:
[15:58] <amazoniantoad> Stupid nvidia drivers
[15:58] <jhutchins> amazoniantoad: You should demand your money back.
[15:58] <FKAShinobi> So I if I want to put in an enhancement to a team, would that be the Gnome Team, Wayland team, etc.?
[15:58] <amazoniantoad> UBUNTU GIVE ME MY MONEY BACK
[15:58] <amazoniantoad> oh wait...
[15:58] <leftyfb> amazoniantoad: would you like help with something?
[15:58] <amazoniantoad> nah. I really love ubuntu, actually. I just updated drivers and am using a variant of wine to run overwatch 2
[15:59] <leftyfb> !wine | amazoniantoad
[15:59] <jhutchins> FKAShinobi: You could try.  You might learn about X11 forwarding first.  It's not just the app you're sending from, it's whatever is receiving and displaying it remotely.
[15:59] <kovital> Yeah wine have full page of compatibily config and tricks for running windows games and app on their site.
[16:07] <billybob> Jeremy31, kovital different result on linux mint. it still doesn't act as print screen. but it has a different keycode, resulting in the start menu flashing up and also the sound control from bottom right. nothing comes up in text editor
[16:09] <billybob> When bringing up the keyboard layout on ubuntu i can see shift + s flashing when hitting the print key on logitech keyboard. on linux mint i do not see any key flash but its clear its doing something. but its a different result
[16:11] <kovital> billybob, on Ubuntu if you press shift+s in a texteditor it displays: "S" ?
[16:12] <kovital> i mean if you press 'print'
[16:12] <kovital> (not shift+s)
[16:13] <kovital> I think you need to find a layout for the exact model of your keyboard but it's maybe not available or only with wrong keycodes, do you load it with setxkbmap ?
[16:14] <billybob> no but i can try that
[16:14] <billybob> i couldnt find an exact layout
[16:15] <oerheks> https://www.reddit.com/r/logitech/comments/sz70ug/screenshot_for_ubuntu_2004_with_mx_keys_keyboard/
[16:15] <oerheks> maybe the last answer on that page..
[16:15] <oerheks> or https://github.com/spxak1/weywot/blob/main/guides/mxkeys_linux.md
[16:16] <oerheks> both answers need Solaar
[16:16] <oerheks> !info solaar
[16:16] <kovital> check 'man setxkbmap' i think you can modify an exiting compatible keymap with the physical codes to the keycodes reported in xev (by xorg or wayland)
[16:16] <oerheks> this was so easy to find, ..
[16:20] <kovital> Well if the issue is just the wrong keymap you wouldn't want a logitech manager on top of the normal bluetooth service.
[16:20] <kovital> i mean its supposed to work out of the box for Android or other i guess, anyway.
[16:20] <oerheks> that manager is specially written for logitech
[16:21] <oerheks> iirc there are more key combo's not working on that MX
[16:22] <kovital> Yeah i know it can report battery status or more things that the device does that is not supported with basic BT support etc maybe.
[16:22] <cats3d_1> I also have a keyboard mystery: I'm getting a 3rd layout in my input method cycle, but it's not defined anywhere
[16:22] <kovital> anyway ok, tell us if it works good with the logitech manager.
[16:23] <cats3d_1> it's not in gnome-control-center, not in ibus, not in xkb. Is another place that overrides all these?
[16:24] <Remy>  /msg NickServ IDENTIFY Remy reem
[16:25] <amazoniantoad> lol
[16:25] <amazoniantoad> Hey remy
[16:25] <oerheks> time to change password, Remy
[16:25] <amazoniantoad> might wanna change your pw
[16:25] <amazoniantoad> hahaha
[16:25] <Remy> hehe shit :)
[16:26] <oerheks> not sure you can have spaces in it..
[16:26] <oerheks> ask #libera
[16:26] <Remy> dank oerheks
[16:38] <jhutchins> I think leading spaces will escape the /msg
[17:04] <maxzor> Hello, have you got an idea why my webcam which is registered as a usb device does not show up in any videoconferencing browser software?
[17:05] <maxzor> jitsi, zoom, teams... firefox, chromium... no avail. I am on ubu 20 and standard gnome wayland
[17:06] <ioria> i'am not good with wc,but usually you start the app from terminal and check the output
[17:06] <rbox> what does dmesg say when you plug it in
[17:06] <maxzor> rbox, if that was for me the webcam appears in lsusb, but I cannot play with the connector easily as this is a sealed laptop
[17:07] <rbox> great
[17:07] <rbox> now to answer the question...
[17:09] <oerheks> what is the 8 digit hex id from the lsusb output?
[17:10] <maxzor> 0bda:58f3
[17:14] <oerheks> " webcam is working with the 1.0 firmware, but not with the 1.5 firmware that the Dell XPS 13 9370 ships right now  "  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763748
[17:14] -ubottu:#ubuntu- Launchpad bug 1763748 in Dell Sputnik "Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50" [Undecided, New]
[17:15] <LikWidChzz> arraybolt3, you around? more EFI discussions
[17:23] <MASDR> After upgrading to 22.04 from 20.04 my wi-fi adapter stop working and when I try see the setting it tells there is no wi-fi adapter. But I can share LAN network through the adapter (hotspot). Any idea?
[17:24] <lucas-arg> MASDR: how did you upgrade
[17:24] <Jeremy31> MASDR: Can you run the 2 commands at https://gist.github.com/jeremyb31/a2bee9856d8c13f42f1835bc31bf9480 in terminal and only post the termbin.com URL after the second command is done
[17:25] <MASDR> lucas-arg: by sudo do-release-upgrade
[17:27] <lucas-arg> MASDR: i would do, sudo apt update && sudo apt dist-upgrade -y && sudo apt autoremove -y in order to be as clean as possible, then reboot and see if wifi is working... maybe a kernel issue
[17:29] <MASDR> Jeremy31: https://termbin.com/qno8
[17:31] <maxzor> oerheks, thank you, should I look into installing one of the linux-oem packages?
[17:32] <oerheks> maxzor, make sure you have firmware 1.51 or higher, as i understand. and oem kernel might fix it then.
[17:33] <MASDR> lucas-arg: nothing just happened, actually I did almost the same, I just sent you the upgrade command
[17:34] <Jeremy31> MASDR: Check>  iwconfig and use the wlx********(the script strips the mac address)  listed there for this command>  sudo ifconfig wlx******** up
[17:42] <MASDR> Jeremy31: when I used sudo ifconfig wlx********* up, I can scan network using iwlist wlx******* scanning, but still no wi-fi adapter in wi-fi setting
[17:46] <lucas-arg> ubuntu mate with compiz, beautiful... reminds me to old gnome2
[17:47] <rbox> lucas-arg: i mean... thats kinda the point of mate
[17:47] <Jeremy31> MASDR: edit /etc/NetworkManager/NetworkManager.conf
[17:49] <Jeremy31> MASDR: Remove the [keyfile] and the line below it
[17:51] <MASDR> Jeremy31: Thanks a lot! working now
[17:51] <Jeremy31> That line below keyfile told Network Manager to ignore that wifi device
[17:51] <MASDR> I see
[18:00] <maxzor> Sep 30 15:21:23 mada kernel: uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (0bda:58f3)
[18:01] <maxzor> oerheks, this is my last uvcvideo entry in journalctl
[18:01] <maxzor> oO is this module superseded by a new one?
[18:02] <arraybolt3> LikWidChzz: Heya, you still around?
[18:06] <LikWidChzz> yeah I am
[18:08] <arraybolt3> LikWidChzz: You were asking if I was still around for more EFI discussion, I believe.
[18:08] <LikWidChzz> Yeah, so I'm trying to wrap my head around this EFI boot bs. gimme a sec and ill type out a paragraph
[18:08] <LikWidChzz> bs = Bachelor of Science btw.
[18:11] <LikWidChzz> I guess as far as directorys go and their contents. when the EFI boot is executed it looks for these .EFI files correct?
[18:11] <arraybolt3> Yes.
[18:11] <LikWidChzz> so whats the mechanism used to determine which one is executed first?
[18:11] <LikWidChzz> i looking in BOOT and unbuntu directories
[18:12] <arraybolt3> OK, so you know how BIOS systems have a CMOS chip for storing settings?
[18:12] <LikWidChzz> sure
[18:12] <arraybolt3> EFI systems have a similar chip, but in addition they have this thing called NVRAM, which is basically a small piece of memory outside of the system's hard drive that stores certain EFI-related info.
[18:12] <arraybolt3> A lot of that info is "boot entries", each one of which instructs the EFI what it should do to "boot" the system.
[18:12] <arraybolt3> So when you install Ubuntu, usually a boot entry is made for ubuntu in the NVRAM.
[18:13] <arraybolt3> That boot entry then points to EFI\ubuntu\shimx64.efi.
[18:13] <arraybolt3> Then when the computer boots, it sees Ubuntu's boot entry, which points it to the shim.
[18:13] <LikWidChzz> btw are the directories sort of ... not important?
[18:13] <arraybolt3> Technically they might be able to be done away with, but they do exist for a good reason.
[18:14] <LikWidChzz> mainly used for logical organization but when booted it just kind of looks everywhere
[18:14] <arraybolt3> A lot of times the EFI files inside the directories will look for *other* files in the same directory that will influence their behavior.
[18:14] <arraybolt3> Yeah, mainly for logical organization.
[18:14] <LikWidChzz> okay
[18:14] <arraybolt3> The system initially looks in its boot entries to find what to boot.
[18:14] <LikWidChzz> so in the grand scheme of things my system wouldnt boot yesterday because the shimx64EFI didnt exist?
[18:14] <arraybolt3> And if there are no boot entires (or if they all don't work), then it gives up and goes for EFI\BOOT\BOOTX64.EFI.
[18:15] <arraybolt3> LikWidChzz: The problem was that your UEFI wassn't letting Ubuntu make a boot entry in the NVRAM.
[18:15] <arraybolt3> Without that boot entry, the EFI has *no clue* that there are Ubuntu boot files on the disk.
[18:15] <LikWidChzz> I guess I need to see my system broken again
[18:15] <Jeremy31> Some HP allow the EFI entry to be made but don't allow the boot order change
[18:16] <arraybolt3> Jeremy31: I've experienced this on my Elitebook.
[18:16] <LikWidChzz> Jeremy31, this is an older system and in bios it even says "UEFI booting isnt supported"
[18:16] <arraybolt3> lol
[18:16] <LikWidChzz> which is why I would not even want to deal with UEFI since its for the birds
[18:17] <arraybolt3> Sounds like the manufacturer boffod its EFI implementation and knew it.
[18:17] <LikWidChzz> frankly unbuntu should make this a menu item during user install and not change anything to be honest.
[18:17] <north> Hi
[18:17] <LikWidChzz> Linux has always been one of those things that just works on old crusty hardware without issue
[18:17] <arraybolt3> LikWidChzz: Might be possible, maybe some "force install to the fallback EFI directory" option.
[18:18] <LikWidChzz> arraybolt3, so technically if i understand this right *Ignore multi boot systems* If I only had bootx64.efi and shimx64.efi in a BOOT directory and nothing else, my system would boot?
[18:20] <arraybolt3> If you only had bootx64.efi and grubx64.efi and grub.cfg in your BOOT and nothing else, *that* would boot.
[18:20] <LikWidChzz> oh wait the bootx64.CSV file points to the SHIMX64.efi file
[18:20] <arraybolt3> (Assuming that bootx64.efi is simply a copy of shimx64.efi)
[18:21] <arraybolt3> LikWidChzz: Right, those .CSV files are for fixing busted boot entries. Only your system's boot entry subsystem is totally broken so those don't actually help you, they help other situations :P
[18:21] <LikWidChzz> the grub.cfg has this in it --search.fs_uuid d4365ad7-db27-474f-b530-24414d006a80 root hd0,gpt3
[18:21] <arraybolt3> Correct.
[18:21] <north> I am wondering is there a way to fix dell vostro 15 3515 ,micron kingston AMD CPU and GPU driver in ubuntu 22.04
[18:21] <LikWidChzz> okay I didnt know that bootx64.efi and shim efi files are duplicates of eachother
[18:22] <arraybolt3> LikWidChzz: That file is a very simple GRUB configuration file that tells GRUB where to find the main HDD (that's that UUID you see) and the actual configuration file.
[18:22] <arraybolt3> They aren't guaranteed to be, but in a working Linux setup they are.
[18:22] <arraybolt3> (If I'm understanding correctly.)
[18:22] <LikWidChzz> that uuid is the SDA block device? or is that the UUID of SDA2 where my boot partition lives
[18:22] <arraybolt3> That UUID is the boot partition's ID.
[18:22] <LikWidChzz> okay so SDA2?
[18:22] <arraybolt3> I think so.
[18:23] <arraybolt3> Though... maybe not...
[18:23] <arraybolt3> There's a difference between the EFI System Partition and the boot partition.
[18:23] <arraybolt3> :-/
[18:23] <LikWidChzz> well there is 3 here theres a 1mb partition, then 1 gig partition then "the rest" aka SDA3
[18:23] <arraybolt3> The EFI System Partition contains *just* the EFI boot files. It takes the place of the Master Boot Record and junk from BIOS systems.
[18:23] <arraybolt3> Yeah then that UUID is probably pointing to SDA3, your root partition which also is doubling as a boot partition.
[18:24] <LikWidChzz> ahh okay well whatever then..
[18:24] <arraybolt3> EFI partition has the bootloader, the boot partition has the Linux system's kernel.
[18:24] <LikWidChzz> bring back lilo.
[18:24] <arraybolt3> :P
[18:24] <arraybolt3> Not necessarily a bad idea.
[18:24] <LikWidChzz> someone got into a discussion with me ages ago about why grub was better than lilo and I told him "who gives a rip..."
[18:25] <LikWidChzz> its like what color of toothbrush is the best.
[18:25] <north> :)
[18:25] <arraybolt3> Sometimes these fine details are important to people with weird setups. But most of us don't have setups that are all that weird.
[18:25] <EriC^^> LikWidChzz: that 1mb partition is probably the bios_boot partition, it's just a place to put some grub bootloader code to be able to use legacy booting + gpt partition
[18:26] <arraybolt3> Which apparently doesn't work on some BIOS systems :(
[18:26] <LikWidChzz> heh
[18:26] <EriC^^> if you're booting in legacy mode right now, it's probably what's helping you boot "ls /sys/firmware/efi" should give an idea which mode you're using
[18:26] <LikWidChzz> well whatever I have one other thing I know know when I need to complain about something.
[18:26] <arraybolt3> EriC^^: No, we're booted into EFI mode.
[18:26] <arraybolt3> We *installed* in BIOS mode, but we're *booted* into EFI mode.
[18:26] <north> did you check bios settings
[18:27] <arraybolt3> north: We don't actually have a problem at the moment, we're trying to understand how things are working now that they wrk.
[18:27] <arraybolt3> LikWidChzz: Perhaps #ubuntu-discuss would be a better channel for this, this is usually a tech support channel and while I feel this is tech support, we may be giving those nearby the wrong idea.
[18:27] <north> ok @arraybolt3
[18:27] <LikWidChzz> yeah I checked the bios settings, the expiration date of the cheese, the temp in my house, the price of bitcoin, the cable is the right length and in the correct usb port, my harddrive is big enough and its not making any weird noises.
[18:27] <arraybolt3> lol
[18:28] <north> :)
[18:28] <LikWidChzz> however I am not surprised this day that a lot of people do not know how to troubleshoot.
[18:28] <LikWidChzz> I think thats what I hate a lot about these tests kids are taking these days to get into tech.
[18:29] <LikWidChzz> the answer is wrong if you dont do A, then B then C. Someone does B then A then C. In the end they both solved the issue but one person did the incorrect order. That's garbage in my mind.
[18:30] <north> i gtg
[18:31] <LikWidChzz> they praise high ability to memorize things, but anyone that critically thinks is out of line.
[18:32] <LikWidChzz> btw if any of you need to create multi boot USB sticks, take a look at Ventoy multiboot its pretty genius
[18:32] <arraybolt3> I've looked at Ventoy before, it looks pretty slick.
[18:32] <arraybolt3> (I've been too scared to try it though :P)
[18:33] <LikWidChzz> Its one of those tools that should have existed 10+ years ago
[18:39] <maxzor> oerheks, thank you again, I juste modprobed uvcvideo and I got the webcam working back. I don't understand what did bring this module out of the autoload wagon
[18:44] <LikWidChzz> I got another one for someone. I'm bulding a 12x orange pi5 cluster. I'm a little curious as to how I would manage it.. I want to run some apps on it that i'll need to run on all of them
[19:03] <billybob> kovital, sorry for the delay had to pop out.
[19:03] <billybob> Yes a capital S prints out in text editor
[19:04] <billybob> I typed in setxkbmap but nothing happens.
[19:05] <billybob> i tried dpkg-reconfigure keyboard-configuration before but not really sure exactly what I am supposed to change it to in there
[19:06] <billybob> same with xkeycaps
[19:07] <Al3ksandar9> k
[19:09] <billybob> Trying to solve this if anyone else has any ideas. https://dpaste.com/HGGSMM4BD
[19:09] <billybob> https://imgur.com/a/r3sLVGa
[19:24] <billybob> here is the result of setxkbmap -query -v 10 - https://dpaste.com/DEPD74BLB
[19:31] <billybob> not really sure what I am supposed to load it to with setxkbmap ?
[19:52] <pareidoliathink> Hello
[19:53] <BarnabasDK> pareidoliathink, If you have a question just shoot
[19:57] <billybob> kovital, tested with fedora live too and got the same result as with ubuntu.
[20:13] <LikWidChzz> https://dpaste.com/9FKHNN57D --- arraybolt3 Looking at this again, I am thinking your last line should not be bootx64.efi but BOOTX64.EFI different case... unless persay that does not matter? Also installed MINT linux and lol they do exactly the same thing as ubuntu breaks the EFI boot
[20:14] <Habbie> case does not matter
[20:14] <Habbie> also, you can tell grub to do this, which is more robust than doing it by hand once
[20:19] <arraybolt3> LikWidChzz: Case does not matter I believe.
[20:19] <LikWidChzz> okay well I was able to fix another borked install
[20:23] <billybob> Not sure what i did now. I changed something and reverted it in solaar. button still not working but now it only registers as Shift being pressed. Removed device from bluetooth, factory reset. removed solaar, deleted solaar config. reinstalled solaar.
[20:52] <pareidoliathink> billybob, maybe try installing the OS again.
[20:57] <BarnabasDK> billybob, I disagree with that - just reinstalling the os teaches nothing always try to analyze a problem
[21:09] <billybob> pareidoliathink - Not sure why i would re-installing the Os when i've tried 2 different OS live boots and the problem has persisted
[21:10] <billybob> BarnabasDK - Agreed.
[21:10] <billybob> I am not really sure what to do about this problem. Been googling and testing all day.
[21:13] <thekingofbandit> ±3*
[21:15] <BarnabasDK> billybob, since the problem persistst across os'es, ( and I am new to the chat here ), maybe bios flash?
[21:15] <BarnabasDK> or flash of other hw
[21:16] <arraybolt3> billybob: You messed up a Logitech device with Solaar I'm guessing?
[21:17] <pareidoliathink> billybob, the reason is that it could've got corrupted. Like reinstalling the ISO.
[21:17] <arraybolt3> I missed what happened
[21:17] <arraybolt3> pareidoliathink: If multiple separate operating systems all show the same problem, the fault is not in the OS.
[21:17] <BarnabasDK> yeah - be carefull with solaar
[21:18] <arraybolt3> Oh, I see what happened.
[21:18] <arraybolt3> It's not that he broke something, it's that the keyboard is just weird.
[21:18] <pareidoliathink> oh ok
[21:18] <arraybolt3> (he sent this as a pastebin earlier: https://dpaste.com/HGGSMM4BD)
[21:19] <BarnabasDK> so a key edit binding on a logitech device gone haywire?
[21:20] <arraybolt3> Meh, I don't actually know what to do about that, that looks very odd.
[21:20] <BarnabasDK> if you have problems with a perifial device across different os'es no amount of re installs will every save you - just for the record here
[21:21] <billybob> BarnabasDK - the 2 tests on live OS's were on different spare laptop
[21:22] <pareidoliathink> billybob, did you enable third party sources on Software & Updates?
[21:22] <BarnabasDK> yeah - I know this is probably lame to suggest in a Ubuntu channel, but you can probably reset your hw on a mac or windows laptop using the logitech software
[21:22] <arraybolt3> That's actually sorta what I was thinking, sadly.
[21:22] <BarnabasDK> how it goes
[21:23] <billybob> arraybolt3 - No the problem was there before i even installed solaar. But i was trying to test the button deviation thing. and somehow changed the config. I set it back to how it was before, but still i get a different result now. whats odd is that it seems sonaar knew it was the snipping tool key
[21:23] <BarnabasDK> logitech makes exeptionally good hid devices, but the support for linux is non existant on their part
[21:24] <bougyman> Like mice?
[21:24] <bougyman> They seem to work fine here.
[21:25] <BarnabasDK> yeah, but if you screw around with the button assignment, dont expect to be able to reset it from anywhere else than the official software
[21:25] <billybob> pareidoliathink - Not sure actually about the software and updates. need to check. But i have secure boot and sometimes things can be a pain
[21:26] <arraybolt3> If you can't get a Windows machine to use to try and reset the device, you might be able to install Windows into a VM for just long enough to install Logitech's official software and then use it to fix the keyboard.
[21:26] <arraybolt3> If you use GNOME Boxes, you should be able to just pass through the Logitech receiver to the VM for that.
[21:27] <billybob> i have tested on windows machine too and reset the device. also followed logitechs guide on resetting - disconnect from bluetooth, esc + o, esc + o, esc +b
[21:27] <billybob> Log Options + didn't offer me any help
[21:27] <BarnabasDK> .. or you may be able to just take your HID device to someone with a ms box
[21:27] <arraybolt3> Have you tried switching receivers by any chance?
[21:27] <billybob> Keyboard is connected via bluetooth and not 1 of their receivers
[21:27] <arraybolt3> Oh tar.
[21:28] <arraybolt3> And it misbehaves on Windows too?
[21:28] <billybob> Haven't got a receiver to hand unfortunately
[21:28] <billybob> you know what, im sure it did, but now ive forgotten, let me double check. Windows laptop right next to me
[21:29] <BarnabasDK> solution right next to you ;-) - its like that and always have been
[21:29] <BarnabasDK> at least with hw from logitech
[21:29] <billybob> never
[21:29] <BarnabasDK> as musch as I like them
[21:30] <BarnabasDK> ah. no sw for logitech devices for any linux I think - sadly
[21:30] <billybob> ive got another keyboard so its not the end of the world.i just want to use this logitech 1 as its the most comfortable. only problem is i need the print screen button
[21:30] <BarnabasDK> at least not made by them
[21:30] <billybob> its required a lot in my job
[21:30] <arraybolt3> billybob: If it misbehaves on Windows too, then it's almost certainly the keyboard's fault.
[21:30] <billybob> not official.
[21:30] <arraybolt3> And if even Logitech's software doesn't have a way of resetting it, then I'm not sure what to say.
[21:31] <BarnabasDK> arraybolt3, agree - it could also be a hw malfunction
[21:31] <arraybolt3> Except bummer :(
[21:31] <billybob> yes agreed, which makes me believe it did work on windows otherwise i wouldn't still be troubleshooting it
[21:31] <pareidoliathink> it could be some function missing on a driver.
[21:31] <billybob> arraybolt3 yeah you can factory reset it. and i tried that already
[21:31] <billybob> it feels like i don't have the correct layout
[21:31] <BarnabasDK> pareidoliathink, across linux and windows at the same time?
[21:31] <billybob> same layout as here
[21:31] <billybob> https://github.com/spxak1/weywot/blob/main/guides/mxkeys_linux.md
[21:32] <pareidoliathink> BarnabasDK, is billybob running a VM?
[21:33] <pareidoliathink> nvm
[21:33] <arraybolt3> billybob: Did you select the Print Screen key in Logitech's software and set its function to "Print Screen"?
[21:33] <arraybolt3> "Key diversion is the complete key customisation feature. In Windows this is done typically from the Options software by clicking on a key and selecting its use from a drop down menu"
[21:33] <pareidoliathink> BarnasbasDK, exactly like that.
[21:33] <BarnabasDK> pareidoliathink, I got the impression the error was in a host os
[21:33] <BarnabasDK> that is - straight on the hw
[21:34] <BarnabasDK> if not I apologize for the confusion
[21:34] <billybob> tested on windows and works fine
[21:34] <billybob> the issue is on host Os
[21:35] <arraybolt3> Oh, OK, interesting.
[21:35] <arraybolt3> billybob: In that instance, can you use Solaar to add a rule for the Print Screen key so that it sends a Print Screen event?
[21:36] <pareidoliathink> <pareidoliathink, across linux and windows at the same time?> BarnabasDK, I was talking about this. Also exactly like using linux and windows at the same time.
[21:36] <arraybolt3> I think you said you tried that.
[21:36] <arraybolt3> And that's when things went weird.
[21:36] <arraybolt3> But it looks like the key diversion feature might be what will fix the problem.
[21:36] <BarnabasDK> pareidoliathink, but not in a vm?
[21:36] <BarnabasDK> that is multibooting between ms and linux
[21:37] <billybob> arraybolt3 yeah I was trying to work out how to do that
[21:37] <pareidoliathink> BarnabasDK, there is VM tools.
[21:37] <billybob> i can try again
[21:37] <BarnabasDK> in either case som sort of state is resitual in the HID device it seems?
[21:38] <billybob> arraybolt3 i tried the key deviation thing. not the same as a rule apparently
[21:38] <BarnabasDK> I am now unsure and will keep quiet :-)
[21:38] <billybob> when testing on windows with the on screen keyboard up, i see it acts as windows + shift - not as though the printscreen key is being pressed. but it does give expected functionality
[21:39] <arraybolt3> Oh no, lol, they made Print Screen the Snipping Tool key?!
[21:40] <arraybolt3> Hah, that explains a lot.
[21:40] <arraybolt3> Now I realize what you said earlier.
[21:41] <arraybolt3> Yeah, I think you may want to look at the Solaar Rule Editor and see if that gives you what you need.
[21:41]  * arraybolt3 has to go afk
[21:42] <BarnabasDK> also - I think the rule editor in apple and ms will probably nuke any rule solaar has made --
[21:43] <BarnabasDK> in the logitech sw
[21:47] <billybob> There is a huge list of keys to choose from to set the rule. i have no idea what i should set the key as
[21:49] <BarnabasDK> maybe some obscure key combination?
[21:49] <BarnabasDK> just to fix it
[21:55] <billybob> yeah but its not clear which key is the problematic one
[21:55] <billybob> i can't like press the key and it fills in automatically
[22:06] <billybob> BarnabasDK - My god - that was it
[22:07] <billybob> configured a rule for the snipping tool button to act as action 'Print' instead
[22:07] <billybob> and now it works
[22:07] <arraybolt3> \o/
[22:08] <billybob> Thanks all for the assistance, kovital, BarnabasDK, arraybolt3,pareidoliathink
[22:08] <billybob> so first I had to goto key / button deviation - Set snipping tool button to diverted then add a rule for it
[22:10] <billybob> pic of config here: https://imgur.com/a/r3sLVGa
[22:13] <arraybolt3> I wonder if it would also have worked to set the screenshot tool's keyboard shortcut to Win+Shift+S.
[22:14] <billybob> possible to do that in linux ?
[22:15] <arraybolt3> Pretty sure that's possible, but you have things working now, don't mess with them :D
[22:15] <arraybolt3> I probably shouldn't think out loud like that in here :P
[22:16] <billybob> yeah i won't mess now
[22:16] <billybob> anyway.problem solved and i can now sleep peacefully. im on european time
[22:16] <billybob> thanks all!
[23:10] <lubuntu> seriously irc
[23:11] <lubuntu> can someone help me install lubuntu
[23:11] <arraybolt3> Yeah, what's going wrong?
[23:11] <lubuntu> it's stuck at loading modules
[23:12] <arraybolt3> What version of Lubuntu are you trying to install?
[23:12] <lubuntu> 20.04
[23:12] <arraybolt3> By "stuck", I assume you mean that the "loading modules" spinner is just going and going and not ever finishing?
[23:12] <lubuntu> yep you are right
[23:13] <arraybolt3> OK. Could you make sure the system is connected to the Internet, then open a terminal window (QTerminal) and run "journalctl | nc termbin.com 9999" (without the quote marks)? Then send the link that outputs - that will allow me to check some logs and see if I can see what's going wrong.
[23:14] <lubuntu> hey how are we communicating if i am not connected to the internet
[23:14] <arraybolt3> Sometimes people will talk on IRC from one device while trying to install on a different device.
[23:15] <arraybolt3> And it's difficult to tell which from our end :)
[23:15] <lubuntu> hehe yeah true
[23:17] <lubuntu> https://termbin.com/ze9i
[23:18] <arraybolt3> OK, which particular module is it trying to load when it gets stuck?
[23:19] <lubuntu> it loaded now
[23:19] <arraybolt3> (I looked to see if there was evidence of a corrupted ISO or flash drive and didn't see anything amiss.)
[23:19] <arraybolt3> Oh. So it was just slow I'm guessing?
[23:19] <lubuntu> Yeah i guess
[23:19] <lubuntu> but i took like 10 mins
[23:19] <lubuntu> thanks much anyway
[23:19] <arraybolt3> Glaod to help!
[23:19] <lubuntu> i appreciate the help
[23:19] <arraybolt3> *Glad
[23:19] <arraybolt3> Hey, before you go...
[23:19] <lubuntu> ?
[23:19] <arraybolt3> Lubuntu 20.04 is not going to be supported for a whole lot longer (it reaches it's end-of-life date in a few months).
[23:20] <arraybolt3> You might want to look at Lubuntu 22.04, which has a lot more support on it.
[23:20] <arraybolt3> 20.04 will still be usable for a couple of years after it goes end-of-life, however, so if you like it more, you should be able to use it anyway.
[23:20] <lubuntu> ok great thanks for the info. I will download the latest now.
[23:20] <arraybolt3> Good luck!
[23:20] <lubuntu> :D
[23:20] <lubuntu> thanks