[01:36] <user_anonym> The Holy Spirit IS a Spiritual Flame
[01:36] <user_anonym>  For the good that I would I do not: but the evil which I would not, that I do.
[01:36] <user_anonym>  —Romans 7:19
[01:36] <user_anonym> The Holy Spirit is also a spiritual flame. He alone can raise our worship to true spiritual levels. For we might as well know once for all that morality and ethics, however lofty, are still not Christianity.
[01:36] <user_anonym> The faith of Christ undertakes to raise the soul to actual communion with God, to introduce into our religious experiences a supra-rational element as far above mere goodness as the heavens are above the earth.…
[01:36] <user_anonym> The joy of the first Christians was not the joy of logic working on facts. They did not reason, “Christ is risen from the dead; therefore we ought to be glad.” Their gladness was as great a miracle as the resurrection itself; indeed these were and are organically related. The moral happiness of the Creator had taken residence in the breasts of redeemed creatures and they could not but be glad. POM103–104
[04:41] <Metamorphosis> noob question: how can one understand if their laptop has two graphic cards (one Intel and one AMD Radeon), when it is not advertised on laptop box etc
 Sduo lshw -C display to get what the computer is recognizing, and search the model number online to get what it actually has
 'sudo lshw -C display' to get what the computer is recognizing, and search the model number online to get what it actually has
[07:04] <alkisg> paculino, did you manage to modify grub.cfg and boot it?
 I managed to corrupt the shared partition, but I did get grub.cfg edited and it did not help
[07:15] <alkisg> The one under <efi partition>/BOOT/popos/grub.cfg ?
 Not that one; I will try that now
 The errors seem to go back to kernelstub.Drive Could not find a block device for the a partition and no such file or directory (failed to flushbinfmt_misc rules) and llvm13/14 failed to add binary (no such file or directory)
[07:18] <alkisg> The main problem is that you're booting a 5.19 kernel that you deleted from /lib/modules, so it cannot access anything, not even the efi partition
[07:19] <alkisg> By modifying the efi>grub.cfg to point to the sda4>grub.cfg you should boot with the 5.15 kernel
 There is no /boot/efi/popos/grub.cfg
[07:19] <alkisg> Are you on windows now, and have you mounted the efi partition?
 https://irc-attachments.kde.org/5692660d/file_61419.jpg
 Mount as mnt or root?
[07:20] <alkisg> You cannot access the efi partition because your 5.19 kernel doesn't have the modules
[07:21] <alkisg> You can only access it from the windows operating system
[07:21] <alkisg> I guess you didn't understand what I suggested yesterday :)
 I misunderstood
[07:22] <alkisg> IrcsomeBot: what's the output of this? ls /boot
[07:22] <alkisg> (before you reboot to windows...)
[07:23] <alkisg> paculino, ^
 How do I go to B:\ from windows?
 ls boot is in that screenshot
[07:25] <alkisg> OK so popos has put the kernel elsewhere, maybe in efi
[07:25] <alkisg> Did you run mountvol first?
[07:25] <alkisg> Do you want to anydesk so that we do this quicker?
 In windows CMD, I did mountvol b: s
[07:26] <alkisg> Did it mention an error?
[07:26] <alkisg> Because this is the wrong command, you didn't put /s
 Autocorrect changed it; I did in terminal. It left a blank line and then went to system32
 Is anydesk just a remote desktop connection?
[07:28] <alkisg> Yes
[07:28] <alkisg> To go to B:, type: B:
[07:28] <alkisg> It should change the drive
[07:28] <alkisg> Then: cd \
[07:28] <alkisg> Then: dir /s
[07:29] <alkisg> It should show all files and folders; copy them to a file and pastebin it
 https://pastebin.com/qtAXqaLh
[07:32] <alkisg> Ouch no that's the wrong EFI partitions. You have two, one in your internal disk and one in your external disk, we want the one from your external disk
[07:32] <alkisg> Check if you can see it in your file manager, as drive E: or F: or whatever
 It is drive B and not formatted for windows
 D
 "The volume does not contain a recognized file system"
[07:35] <alkisg> Do not format anything
 May I change letter?
[07:35] <alkisg> B: is the efi partition of your internal drive
[07:35] <alkisg> We want the efi partition of your external drive
 *: is the efi for ext according to partition tool
[07:35] <alkisg> Run `diskmgmt.msc`, maximize it, and upload a photo
 May I assign it a letter, or will that cause issue?
 https://irc-attachments.kde.org/60fd5736/file_61420.jpg
 https://irc-attachments.kde.org/e255ab7b/file_61421.jpg
 It is quite late here; I will go to bed once this step is done if that is alright
[07:44] <alkisg> paculino, you mounted the 100 mb partition, while you should mount the 15 gb partition of the second disk
[07:44] <alkisg> That's where you grub.cfg is, in the 15 gb partition
 Will it hurt to assign it a letter so I can do that?
[07:45] <alkisg> No, it won't hurt
[07:46] <alkisg> The weird thing is that I do not see your ext4 partition
 The directory is not empty
[07:47] <alkisg> Which directory?
 K
 The efi one
[07:47] <alkisg> Yes, it should have files there
[07:47] <alkisg> In the cmd prompt, type:
[07:47] <alkisg> K:
[07:47] <alkisg> cd \
[07:47] <alkisg> dir /s > \list.txt
[07:48] <alkisg> It will create a file K:\list.txt
[07:48] <alkisg> Upload it to pastebin
 https://pastebin.com/tRJcRBT7
[07:50] <alkisg> So popos is using systemd-boot instead of grub
[07:50] <alkisg> That's why you couldn't see the grub menu
[07:51] <alkisg> Make a copy of Pop_OS-current.conf to keep its contents
 From windows?
[07:51] <alkisg> Then upload Pop_OS-current.conf and Ubuntu-current.conf to pastebin
[07:51] <alkisg> Yes, in the same folder, ctrl+c and ctrl+v
 https://pastebin.com/2giREU6V
 Okay, when I edited grub.cfg I just used the UUID, but it appears the UUID is the same for each
[07:56] <alkisg> paculino did you install kernel 5.19 in ubuntu, or was it only in popos?
[07:57] <alkisg> popos has kernel 5.19, ubuntu has 5.15
[07:57] <alkisg> If you installed kernel 5.19 in ubuntu then you'll need to use the shared partition to get the 5.15 one
 I'm not sure
[07:59] <alkisg> OK then do this. In both of these files, replace the word "quiet" with "break=bottom"
[07:59] <alkisg> And save them
[07:59] <alkisg> When you reboot, you'll get a different shell than usual, the "initramfs" shell
[08:00] <alkisg> There you should be able to load the nls module to access the efi partition from linux, to copy the 5.15 kernel etc
 Okay, is that all to do before rebooting?
[08:00] <alkisg> Yes
[08:00] <alkisg> These are 2 different boot managers
[08:00] <alkisg> The problem happened because popos was using systemd-boot and ubuntu was using grub, and things got messy
 Okay, it says it is in busybox 1.35.0
[08:02] <alkisg> OK, type: ls /lib/modules; ls /root
[08:02] <alkisg> And upload a photo
 https://irc-attachments.kde.org/3fc67944/file_61422.jpg
[08:04] <alkisg> now type: cp -a /lib/modules/5* /root/lib/modules/
[08:04] <alkisg> Did it succeed?
 Is there a space before the five?
[08:04] <alkisg> With this, you copied some of the 5.19 modules that are available in the initramfs, to the real file system.
[08:04] <alkisg> With this, you should be now able to mount the efi partition later on
[08:05] <alkisg> No space
[08:05] <alkisg> cp    -a     /lib/modules/5*    /root/lib/modules/
[08:05] <alkisg> I added more spaces so that it's more visible ^
 It is read only and did not work.
[08:05] <alkisg> mount -o remount,rw /root
[08:05] <alkisg> Then again the cp command
 It works now
[08:06] <alkisg> OK now type: exit 0
[08:06] <alkisg> This will continue to the old shell prompt you had previously
 Do I reboot?
[08:07] <alkisg> No
[08:07] <alkisg> Did you get the normal shell prompt that you had yesterday?
 I have the normal login menu
[08:08] <alkisg> Text or graphics?
 Gui
[08:08] <alkisg> OK, login there and open a GUI terminal
[08:09] <alkisg> Do you have internet there now?
 It takes a bit to load
 It does not, but since it is really late here and it is mostly fixed, I will go to bed now. Thank you so much for patiently helping me; I never would have gotten it fixed.
[08:14] <alkisg> Cheers; remember that now you need to type "exit 0" to continue booting
[08:14] <alkisg> We can fix that tomorrow, good night
[08:15] <alkisg> So the things left to do are to remove systemd-boot and remove grub and delete all boot entries and reinstall grub
 I assume getting more packages will require downloading them into a spare partition like before (unless networking can be repaired without that)?
[08:16] <alkisg> networking can be repaired
[08:16] <alkisg> By booting with the 5.15 kernel
[08:16] <alkisg> More on that tomorrow, go to bed
 Alright, thank you so much!
[08:18] <alkisg> 👍️
[11:15] <Guest4435> give me a hiya
[11:16] <tobyp__> hi
[12:58] <BluesKaj> Hi all
[14:13] <lsd|2> BluesKaj: actually IRC its not used for badoo or datezone
[14:14] <BluesKaj> lsd|2, ?
[16:38] <Luziffer> Ist deutsch schreiben okay? falls deutsche hier sind.
[16:39] <alkisg> !de
[16:41] <Luziffer> Okay. da weiß ich bescheid. danke!
 alkisg, sorry to continue bothering you, but is it safe to purge systemd-boot and then reboot, or do I need to copy a kernel or mount anything first?
[17:53] <alkisg> paculino, first we need to get you network; I'll be online in 10 minutes, wait
 Okay, thank you
[17:59] <alkisg> paculino, upload a screenshot of `sudo lsblk --fs` please
 Sorry, I wasted time trying to use kdeconnect : https://irc-attachments.kde.org/53420e0c/file_61431.jpg
[18:06] <alkisg> OK, now: find /boot/efi -name 'vmlinuz' -ls
[18:06] <alkisg> (and screenshot)
 It output nothing
[18:08] <alkisg> Hmm I think matrix trimmed my asterisks, retrying...
[18:08] <alkisg> find /boot/efi -name '*vmlinuz*' -ls
 Asterisks vanishing are annoying. My normal client shows them faintly : https://irc-attachments.kde.org/fa6264af/file_61432.jpg
[18:11] <alkisg> paculino, also this: ls -l /boot
[18:11] <alkisg> Then backup your efi dir: sudo cp -a /boot/efi /boot/efi.bak
 https://irc-attachments.kde.org/a713f771/file_61433.jpg
[18:14] <alkisg> Now we want to copy your 5.15 kernel and initrd over the other 3 ones that are in the efi partition
[18:15] <alkisg> That way after rebooting you'll get the 5.15 kernel which will have the wifi module and you'll have networking
 43.46 or 52.52?
[18:16] <alkisg> sudo cp -a /boot/vmlinuz-5.15-0-52-generic /boot/efi/EFI/Ubuntu-*/vmlinuz.efi
[18:16] <alkisg> It's better to use tab for autocomplete instead of my asterisk there
[18:17] <alkisg> To copy the initrd, first run: find /boot/efi -name '*initrd*'
 Cannot stat, no such file or directory. Should I remount?
[18:17] <alkisg> To copy the initrd, first run: find /boot/efi -name '*initrd*' -ls
[18:17] <alkisg> No, do not remount anything, you probably gave a wrong filename
[18:18] <alkisg> Run the find initrd command above, then screenshot
[18:18] <alkisg> It'll also show the error
 15.0 not 15-0, but now it has the same error for the second directory
[18:19] <alkisg> Screenshot
 https://irc-attachments.kde.org/552039d9/file_61434.jpg
[18:21] <alkisg> Run sudo -i
[18:21] <alkisg> This way you'll be root and you won't need sudo anymore and you'll be able to use tab
[18:22] <alkisg> Then type: cp -a /boot/vmlinuz-5.15-0-52-generic /boot/efi/EFI/Ubuntu
[18:22] <alkisg> And at that point press <tab> on the keyboard to autocomplete the filename. Do not use asterisks at all
[18:22] <alkisg> So the final command should be: cp -a /boot/vmlinuz-5.15-0-52-generic /boot/efi/EFI/Ubuntu-the-long-number-here/vmlinuz.efi
 Okay
[18:23] <alkisg> And: cp -a /boot/vmlinuz-5.15-0-52-generic /boot/efi/EFI/Pop_OS-the-long-number-here/vmlinuz.efi
[18:23] <alkisg> And: cp -a /boot/initrd.img-5.15.0-52-generic /boot/efi/EFI/Ubuntu-the-long-number-here/initrd.img
[18:24] <alkisg> And: cp -a /boot/initrd.img-5.15.0-52-generic /boot/efi/EFI/Pop_OS-the-long-number-here/initrd.img
 Okay
[18:24] <alkisg> When you've done all four of them without errors, upload a screenshot for me to verify it, and then we'd be able to reboot
 https://irc-attachments.kde.org/5d699735/file_61435.jpg
 I did 15.0 instead of 15-0 since the latter had errors
[18:25] <alkisg> No
[18:26] <alkisg> The last two are wrong
[18:26] <alkisg> You copied vmlinuz instead of initrd.img
 Remove and redo?
[18:26] <alkisg> No, just redo
[18:26] <alkisg> It'll overwrite the bad one
[18:26] <alkisg> cp -a /boot/initrd.img-5.15.0-52-generic /boot/efi/EFI/Ubuntu-the-long-number-here/initrd.img
[18:26] <alkisg> cp -a /boot/initrd.img-5.15.0-52-generic /boot/efi/EFI/Pop_OS-the-long-number-here/initrd.img
[18:27] <alkisg> Then run this to verify: ls -l /boot/efi/EFI/*/*initrd.img* /boot/efi/EFI/*/*vmlinuz*
[18:27] <alkisg> Then screenshot
 https://irc-attachments.kde.org/f81b827e/file_61436.jpg
[18:28] <alkisg> It looks good, but let's verify it with the last ls command above ^, and screenshot. Then we'll be able to reboot
 Sorry, I was uploading that before you told the last one : https://irc-attachments.kde.org/c2ca0cef/file_61437.jpg
[18:30] <alkisg> You put an extra / before the initrd.img, but anyway it should be fine
[18:30] <alkisg> Go ahead and reboot, remember to type exit 0 when needed
 Okay, it is loading
[18:32] <alkisg> Check if you have WiFi now
 I will once it finishes in about five minutes
[18:33] <alkisg> Haha, it takes a lot of time!
[18:33] <alkisg> I guess you have something in /etc/fstab that's missing
 Probably, I've had issues with fstab before
 The first few times I booted this it took way longer, and each time it got better, then it went back to five minutes after a few boots taking three.
 HDD problems
 I can do the systemd and grub parts myself; I've done that before
 (Assuming networking is fixed)
 Networking works; thank you for all the help. It is better than all prior tech support I've had combined.
[18:38] <alkisg> A UTP cable would be so much easier :D
[18:38] <alkisg> Now the idea is to remove the systemd-boot bits and grub-efi and reinstall grub-efi and run grub-update and grub-install
[18:38] <alkisg> You're sure you know how to do all this?
 I've done it before
[18:39] <alkisg> OK, good luck then!
 Purge systemd, search for remnants and RM rf them if they exist, then use apt on grub, install/update grub
 Right?
[18:41] <alkisg> Hopefully not `apt purge systemd` as that will remove most of ubuntu
[18:42] <alkisg> Just remove the efi bits that the popos systemd-boot created, like the directories, entries, grub.cfg etc
[18:42] <alkisg> And use efibootmgr to adjust the nvram entries
 Alright
[18:42] <alkisg> What's the output of this? sudo ls -l /boot/efi |  nc termbin.com 9999
[18:44] <alkisg> Sorry, this one: sudo ls -lR /boot/efi |  nc termbin.com 9999
[18:44] <alkisg> R=Recursive..
 https://termbin.com/0eflb first and https://termbin.com/n0qj
[18:45] <alkisg> Great, so, if you're sure you can properly reinstall grub, just remove everything under efi
[18:45] <alkisg> sudo find /boot/efi/ -delete
[18:46] <alkisg> But before rebooting, make sure everything is back in place, that grub-install did put a grub.cfg there
 Device or resource busy
[18:46] <alkisg> I guess it tried to remove the mount point, ok my bad but you can ignore that
[18:46] <alkisg> Now ls -l /boot/efi ==> is empty?
[18:47] <alkisg> sudo ls -l /boot/efi
[18:47] <alkisg> (just run a sudo -i so that we don't need to type sudo all the time)
 It is, and now I will reinstall grub, install grub, update grub, and check grub.cfg
[18:47] <alkisg> What's the output of this: dpkg -l | grep grub | nc termbin.com 9999
[18:47] <alkisg> And this: dpkg -l | grep shim | nc termbin.com 9999
 https://termbin.com/oc7nu and https://termbin.com/eudo
 What did you use to learn all of this so well?
[18:50] <alkisg> 14 years of post high school studies :D
[18:50] <alkisg> And 30 years of practise :D
[18:50] <alkisg> OK remove all these packages but make sure nothing more is removed. Then reinstall shim-signed, it will automatically reinstall grub-efi
 Alright, I don't need any more help now
[18:53] <alkisg> 👍️
[18:53] <alkisg> Ping me before rebooting
[18:54] <alkisg> (to check the output of efibootmgr)
 That may not be for several hours; I have to take a relative somewhere in half an hour, and then have to finish harvesting sweet potatoes before the frost/storm tomorrow
 I'm sorry
[18:58] <alkisg> No need to be sorry, my own PC is fine! :)
[18:58] <alkisg> Just make sure you don't reboot before fixing all the efi stuff otherwise it won't boot anymore...