[06:00] <lordievader> Good morning
[06:02] <alkisg> o/
[07:05] <Travelinrob> Greetings. I made a mistake and need help fixing grub. I have an nvme drive that had Windows 10 and Kubuntu. I installed the new beta Mint on an empty partition there but when it overwrote grub it did not include my Kubuntu partition. I've been Googling and trying to fix the issue without success. I am currently booted into a live Kubuntu environment.
[07:06] <Travelinrob> Actually, I've been Duck Duck Go'ing...
[07:07] <alkisg> Travelinrob: what's the output of `sudo fdisk -l` ?
[07:07] <alkisg> sudo fdisk -l | nc termbin.com 9999
[07:08] <Travelinrob> https://termbin.com/zfp8
[07:09] <alkisg> Travelinrob: when your computer boot,  what are you seeing now, can you boot any OS, do you see grub at all?
[07:09] <alkisg> *boots
[07:09] <Travelinrob> Mint is on /dev/nvme0n1p5 and Kubuntu is on /dev/nvme0n1p6
[07:11] <Travelinrob> Yes. I can boot and see grub. I can boot into Mint or Windows. But, most distibutions give me a hard time with my vega radeon and i can only boot into safe mode, as I am now. Kubuntu worked for some reason though, but not working live.
[07:11] <alkisg> It's easier to fix grub if you're booted into mint
[07:12] <alkisg> From a live cd, you have to chroot etc; while from mint, you can just run `update-grub`
[07:12] <Travelinrob> it seems to ignore the kubuntu partition
[07:12] <Travelinrob> I tried that.
[07:12] <alkisg> Can you reboot into mint, and come here again?
[07:12] <alkisg> We'll troubleshoot it from there, it's better that way
[07:12] <Travelinrob> ok. i just need to figure out how to get back to libera.chat and this channel...
[07:13] <Travelinrob> Thank you. Hopefully see you shortly...
[07:13] <alkisg> 👍️
[07:27] <travelinrob> alkisg: I'm back.
[07:27] <alkisg> travelinrob: nice. Can you run `sudo update-grub`, and then upload both the terminal output, and the generated /boot/grub/grub.cfg, into pastebin?
[07:28] <travelinrob> alkisg: Can I pipe it directly into pastebin or I have to copy and paste?
[07:29] <alkisg> ( sudo update-grub 2>&1; cat /boot/grub/grub.cfg ) | nc termbin.com 9999
[07:30] <travelinrob> alkisg: That did not return a termbin link.
[07:31] <alkisg> Strange, oh well ok do copy/paste then
[07:33] <travelinrob> alkisg: https://pastebin.com/HDGfYJ1J
[07:34] <travelinrob> alkisg: I wonder if it's an issue because it's on the nvme drive?
[07:35] <travelinrob> alkisg: or it gets confused with 2 "Ubuntu's"?
[07:35] <alkisg> travelinrob: no this isn't a problem
[07:35] <alkisg> It's possible that kubuntu wasn't properly installed and generated no grub.cfg for mint to find it
[07:36] <alkisg> Run:  sudo mount /dev/nvme0n1p6 /mnt; cat /mnt/boot/grub/grub.cfg
[07:36] <travelinrob> alkisg: It was only Windows and Kubuntu booting from grub before I just installed Mint
[07:36] <alkisg> And put the result to pastebin again (or use  | nc termbin 9999)
[07:37] <alkisg> Hmm, it may be possible that linuxmint doesn't want to find other devices, blocking the usual update-grub proper
[07:37] <alkisg> *prober
[07:37] <alkisg> Linuxmint in general does a lot of broken things, I've only used it for a couple of hours before giving up on its lack of debian policy respect
[07:38] <alkisg> What are the contents of: /etc/default/grub.d/50_linuxmint.cfg
[07:39] <travelinrob> alkisg: Oh.One other thing. Kubuntu is on a btrfs partition. Could that be the issue?
[07:39] <alkisg> Yes, try to mount it first or at least modprobe the btrfs module
[07:40] <travelinrob> This is what happened when I applied you previous request: https://pastebin.com/AYqrgRJX
[07:41] <alkisg> btrfs indeed looks like the issue here. Maybe you need to mount some default snapshot or however else is called; sorry, while I do know enough about grub, I don't know enough about btrfs to help there
[07:43] <travelinrob> Well, I don't think a snapshot will help because I allowed Mint to overwrite grub at the root of the drive.
[07:43] <alkisg> In EFI, there's a minimal grub.cfg in the efi partition
[07:43] <alkisg> While the real grub.cfg is inside /boot/grub, which you didn't overwrite
[07:43] <alkisg> Try this: ls /mnt/@
[07:43] <alkisg> Does this show the root fs contents?
[07:44] <alkisg> I.e. try to locate the /boot/grub directory of your kubuntu partition; I don't know how to do this with btrfs
[07:44] <alkisg> It should have a proper grub.cfg inside it
[07:44] <alkisg> Maybe it is: ls /mnt/@/boot/grub/grub.cfg
[07:44] <travelinrob> it does show the root contents
[07:45] <alkisg> Then you should be able to find grub.cfg inside there
[07:45] <alkisg> I don't know how you would tell os-prober (that runs inside mint) to find it though
[07:45] <travelinrob> yes
[07:46] <alkisg> Try this
[07:46] <alkisg> Reboot, go into grub
[07:46] <alkisg> then press c for a command line
[07:46] <alkisg> there, type: set root=(hd0,gpt6)
[07:46] <alkisg> (or wherever your kubuntu is)
[07:46] <alkisg> and from there: configfile /boot/grub/grub.cfg
[07:46] <alkisg> This way you'll manually load the kubuntu grub.cfg, and you'll be able to boot into kubuntu
[07:47] <alkisg> Once you boot into kubuntu, you'll be able to run grub-install, and have kubuntu's grub shown on boot, instead of mint's grub
[07:47] <alkisg> As kubuntu's grub will be able to detect mint, as mint doesn't have btrfs
[07:48] <travelinrob> that all makes sense other than me getting the drive part correct! Should I save this grub to an external drive?
[07:50] <alkisg> No, don't complicate it more than it is. Leave your dummy grub.cfg in your efi partition, and your two real grub.cfg in your OS partitions
[07:50] <alkisg> Ah
[07:50] <alkisg> Sure you can also do this:
[07:51] <alkisg> copy grub.cfg from kubuntu into /boot/grub/grub-kubuntu.cfg in your mint root partition
[07:51] <alkisg> Then you can type "c" for console in grub, and "configfile /boot/grub/grub-kubuntu.cfg"
[07:51] <alkisg> Without having to type "root" etc
[07:52] <alkisg> (note that you can use tab in grub console, for autocompletion)
[07:52] <alkisg> (both for directories and partitions)
[07:56] <travelinrob> alkisg: Ok. I'm going to try this. I'll report back. I appreciate your time. Thank you.
[07:57] <alkisg> np
[08:21] <travelinrob> alkisg: Well, it almost worked! I was able to boot into the grub-kubuntu.cfg file from the Mint grub via configfile. But, I think we need to somehow edit the EFI grub to point to the grub on the kubuntu partition. I think when it looks for the grub parameters from the file it does not see it because it's not on the same partition as the grub-kubuntu.cfg on the mint partition.
[08:22] <travelinrob> wait... forget that.
[08:22] <alkisg> travelinrob: did you manage to boot into kubuntu?
[08:22] <alkisg> The grub-kubuntu.cfg has the correct uuids, of the kubuntu partition
[08:22] <travelinrob> i was able to boot into kubuntu. I was able to update grub from kubuntu. but, rebooting, it still boots to the mint grub.cfg from EFI.
[08:23] <alkisg> You must not run update-grub
[08:23] <alkisg> Like I said, you need grub-install there
[08:23] <alkisg> So that it rewrites the small central grub.cfg in the efi partition
[08:24] <alkisg> Want me to see over vnc? sudo apt install x11vnc; x11vnc -connect alkisg.ltsp.org; do that from kubuntu
[08:24] <travelinrob> I did that from Kubuntu, and I saw that it saw and added the Mint partition, but it did not update the EFI boot to point to it instead of the Mint cfg
[08:24] <alkisg> update-grub is one command
[08:24] <alkisg> install-grub is another
[08:25] <travelinrob> Oh. I didn't catch that. My bad.
[08:26] <alkisg> *grub-install, not install-grub, sorry
[08:27] <alkisg> # cat /boot/efi/EFI/ubuntu/grub.cfg
[08:27] <alkisg> search.fs_uuid 3f3a98a2-5a94-496f-bd99-243e3e0529bd root hd0,gpt5
[08:27] <alkisg> This uuid there shows which configfile will be loaded
[08:27] <travelinrob> the other problem I have, and I don't know if there is a problem with my hardware. I can always boot into Windows, but it will only sometimes boot into Linux. Specifically, it seems to be an issue with the AMD GPU. Sometimes it boots into Linux without issue and other times the fan revs high and I never see the spash. But, if I keep rebooting, eventually I get the splash. Otherwise, nomodeset will always get me in with
[08:27] <travelinrob> crappy graphics.
[08:27] <alkisg> This is the "small master grub.cfg" that I was talking about
[08:28] <alkisg> You can either edit it manually, or you can run grub-install to overwrite it
[08:28] <alkisg> It needs to point to your kubuntu
[08:28] <alkisg> Which kernel do you have? uname -r
[08:29] <alkisg> Sometimes newer kernels/xorgs resolve such issues, especially with recent GPUs
[08:31] <travelinrob> well, I'm currently in mint so it's 5.4.0-74-generic. But, I believe Kubuntu is 5.11-19?
[08:34] <travelinrob> I'm going to try to get back into Kubuntu and run grub-install. I'm confused about the efi grub, though. /boot/efi/EFI... must live on this Mint partition, no?
[08:34] <alkisg> Ubuntu 20.04.1 has 5.4, 20.04.2 has 5.8, while 21.04 has 5.11
[08:34] <alkisg> Same for kubuntu and mint
[08:34] <travelinrob> my kubuntu is 21.04
[08:34] <alkisg> ...although mint has some weirdness again about held kernels, so not sure about how to do it properly there
[08:35] <alkisg> Does it have the same problem with kubuntu?
[08:36] <travelinrob> Yes. I had to use nomodeset after I set the configfile. But, in general, once I get the splash and it boots, it works until the next reboot, where it may or may not work.
[08:36] <alkisg> I would remove "quiet splash" from the grub options, so that when the problem happens, a kernel crash will be shown on the screen, so that you could photograph it and upload it to a kernel bug report
[08:38] <alkisg> With the crash text, you could even google for existing workarounds
[08:40] <travelinrob> I ran hardware tests on Windows and it never found an error and I never have issues booting Windows. But, it behaves like a hardware issue since it sometimes works and sometimes doesn't. I spent days trying different amdgpu versions with mint originally, with help from them via IRC, but eventually gave up when Kubuntu 21.04 booted. That is until the new beta came out. Right now Mint is working, but I had to reboot about 10
[08:40] <travelinrob> times because of it failing
[08:41] <alkisg> Oh I've seen such issues dozens of times and they always were kernel/xorg issues
[08:41] <alkisg> Half of the times, a newer or older kernel resolves them. Sometimes a kernel parameter (not as drastic as nomodeset) works around them.
[08:41] <alkisg> I don't think it's a hardware issue you're facing
[08:43] <travelinrob> It's frustrating because this is the first decent, not super old machine I've purchased and I chose it because I read so many good things about AMD and I found something that said this machine was Linux compatible. I never had these issues with my other Intel machines. I've been running Linux since 2006? I can't remember anymore.
[08:46] <travelinrob> Anyway, I'm going to try grub-install and we'll see how it goes.
[08:58] <Travelinrob> alkisg: Well, it worked!! I can now choose all 3 from the grub menu. Thank you, again. Unfortunately, I've been up all night and have to get up for work in 2 hours. Goodnight!!
[08:59] <alkisg> Travelinrob: I still prefer intel to amd
[08:59] <alkisg> I had too many overheating problems to trust amd. Maybe in a few years I'll trust it again.
[08:59] <alkisg> Good night!
[09:01] <Travelinrob> alkisg: Again, I just heard so many good things on my Linux podcasts. But, I've had a bad experience witht this machine. But, again, once it's working, it does work well.
[09:02] <Travelinrob> Keep up the good work, everyone!! It is appreciated!!
[09:02] <alkisg> I've heard a lot of good things too, but my personal experience says otherwise :)
[13:09] <BluesKaj> Hi all
[16:04] <RikMills> ping
 pong
 pong^2
[16:11] <RikMills> we have the telegram bridge back
 ah
 Love it or hate it 😉
[16:25] <Mekaneck> i LoHa it
 \o/
[21:45] <Guest5430> Hi. I would like to install Kubuntu on my laptop.  I downloaded 20.04.2.LTS from kubuntu.org. When I am installing I see that it has hardwired a user 'oem' which I cannot change. It used to be that I could set my admin username. How do I set my own admin username and password and get rid of this 'oem' user?
[21:50] <Guest5430> I may have found the answer here and am going to try it now - https://userbase.kde.org/Neon/Installation/OEM
[21:52] <Eickmeyer> Guest5430: The OEM installer option is only for OEMs to install prior to sale for a customer. You should've just used the "Install Kubuntu" option.
[21:52] <Eickmeyer> Also,
[21:52] <Eickmeyer> !neon | Guest5430
[22:01] <Guest5430> @Eickmeyer - I was doing a google search and stumbled on to the neon site. I am going to restart and try the "Install Kubuntu" option (I was looking for something like that and must have missed it in the boot menu?).
[22:02] <Eickmeyer> Guest5430: It's the top, default connection.
[22:02] <Eickmeyer> *option
[22:02] <Guest5430> ok. trying it now. thx!
[22:02] <Eickmeyer> :)
[22:03] <Guest5430> The top option is "Start Kubuntu". This is not the "Live CD" option but will actually let me install?
[22:04] <Eickmeyer> Guest5430: Oh, that should be it.
[22:04] <Guest5430> I picked it. Let's see how it goes :)
[22:05] <Eickmeyer> You'll get two options: Install Kubuntu or Try Kubuntu
[22:05] <Eickmeyer> Either one will let you install.
[22:05] <Guest5430> I have been using ubuntu server for a while and doing a kubuntu install after y-e-a-r-s. So, things have changed...
[22:05] <Eickmeyer> Well, Ubuntu Server's installer is quite different, so the comparison doesn't exactly work, but sure.
[22:06] <Guest5430> Yep!
[22:31] <genii> I actually prefer to do a minimal server install with RAID then install kubuntu-desktop afterwards
[22:36] <Guest5430> @genii what is the benefit of installing server first and then kubunu-desktop?
[22:37] <genii> Guest5430: Default Kubuntu and other *buntu desktop installs do not offer RAID as an option
[22:38] <genii> I have 3 SSD in my laptop which I have set as RAID1 with hot spare, which I configure with the server install, and then later install the desktop
[22:52] <Guest5430> Ah, makes sense. I am building a cheap laptop to run my (really old) Drupal 6 website for testing/pre-prod