[00:17] <user|40> I am trying to dual boot with win10. I have multiple drives windows is on sde, kubuntu will go on sdd, with a few storage drives in there. I tried using guided(entire disk) it failed at install grub. At first i looked at manual but it recommeded putting the bootloader on sda (a storage drive) assuming i need to do manual where do i put the boot
[00:17] <user|40> loader (the efi partition?). I cannot loose my windows drive due to work. Any help is appreciated.
[00:17] <arraybolt3> user|40: What was the exact error message from the install attempt?
[00:18] <arraybolt3> (It shouldn't matter what drive the bootloader goes on, so long as the firmware of the computer can find it.)
[00:18] <user|40> Executing 'grub-install /dev/sda' failed this is a fatal error
[00:19] <arraybolt3> Hmm... well that isn't very descriptive, but I guess we can work with it.
[00:19] <arraybolt3> OK, are you at a desktop where you can run commands in Konsole?
[00:20] <user|40> I am in this chat on my phone with the live cd running on my desktop
[00:20] <arraybolt3> First I'll have you run some stuff so I can see some info about your computer, which may provide hints as to what's happening, then we'll try to fix the problem and hopefully be able to try the installation again.
[00:20] <arraybolt3> (If it's easier for you, you could also join the chat using Quassel on the live CD, but this is fine too.)
[00:20] <arraybolt3> Er, Konversation, not Quassel.
[00:21] <arraybolt3> OK, so firstly, can you open Konsole, and then run "ls /sys/firmware/efi | nc termbin.com 9999", then provide the link that is spit out from that? That will tell me whether you're using a BIOS or UEFI system.
[00:23] <user|40> No such file how would i join with konversation i have the app open
[00:24] <arraybolt3> Just press the Connect button, then run "/nick yourNickHere" to change your nickname (you can put whatever you want in "yourNickHere").
[00:25] <arraybolt3> Looks like you are successful, though you probably want to change the nick to something other than "kubuntu", since I think someone else uses that one already.
=== kubuntu is now known as Fantom
[00:25] <arraybolt3> Nice.
[00:25] <arraybolt3> I'm still here.
[00:25] <user|40> Ok
[00:25] <arraybolt3> (The part message was just me closing Konversation on my end since I use a different chat client.)
[00:25] <arraybolt3> OK, so you're using a BIOS system... and it says that the installation failed... hmm.
[00:25] <Fantom> ok i have konversation running
[00:26] <arraybolt3> Alright, can you do "lsblk | nc termbin.com 9999" this time? That will help me see your drive layout, which may provide some hints. "sudo fdisk -l | nc termbin.com 9999" might also be helpful, that will give me more detailed disk info.
[00:27] <arraybolt3> (Please do NOT post the output of the commands directly in the chat, use termbin and send the link.)
[00:27] <arraybolt3> (Otherwise a flood prevention bot might mute you.)
[00:28] <Fantom> the first one gave me a site termbin.com/xeyp
[00:28] <arraybolt3> Perfect, looking.
[00:29] <Fantom> the second one gave me a site termbin.com/kae
[00:29] <arraybolt3> That second one looks like a typo, I just get a 404 Not Found page on it.
[00:29] <Fantom> you are right termbin.com/kae
[00:30] <Fantom> you are right termbin.com/5kae
[00:30] <Fantom> sorry numlock got me
[00:30] <arraybolt3> lol happens to me to
[00:30] <arraybolt3> *too
[00:30] <arraybolt3> Ah, problem solved. sda is using a GPT partition table, which won't work unless there's a bios-grub partition.
[00:31] <Fantom> so what do i do to fix this?
[00:31] <arraybolt3> Though... wait a minute here, your Windows installation seems to use EFI...
[00:32] <arraybolt3> I'm still troubleshooting, so give me a sec, we're not far from success.
[00:32] <Fantom> gotcha
[00:32] <arraybolt3> What is the exact manufacturer and model of your PC? Something like "HP Z220 SFF Workstation" is what I'm looking for.
[00:32] <arraybolt3> (I'm assuming this is a desktop since I've never seen a laptop with five drives in it :P)
[00:32] <Fantom> home built but yes desktop
[00:33] <arraybolt3> Ah, OK. Motherboard info would be sufficient then.
[00:33] <arraybolt3> (I just am looking to see whether your system supports EFI or not - if it does, somehow the installer has booted in BIOS mode, and we should probably fix that. If not, then we can just install Kubuntu again using manual partitioning.)
[00:34] <Fantom> msi motar bx something give me a second ill find the model number
[00:35] <Fantom> msi z270m
[00:35] <arraybolt3> I don't see any way this thing could not support EFI. Can you run the "ls /sys/firmware/efi" one more time just to confirm that you didn't make a typo and that it really says "No such file or directory"?
[00:36] <Fantom> copy and pasted this time no such file or directory
[00:36] <arraybolt3> OK. Did you do anything special to boot the installer?
[00:37] <arraybolt3> It should boot in EFI mode, not BIOS mode like it is currently booted into.
[00:37] <Fantom> no, i havent done any thing aside from windows on this machine so far
[00:37] <arraybolt3> K. What software did you use to flash the ISO to the USB drive?
[00:37] <Fantom> rufus
[00:38] <arraybolt3> OK. Did you make sure to use DD mode to flash the ISO?
[00:38] <arraybolt3> If not, that may be the problem.
[00:38] <Fantom> i did not. so reflash and try again?
[00:38] <arraybolt3> That's what I would do.
[00:38] <arraybolt3> It should let you select DD mode at some point.
[00:39] <arraybolt3> If you aren't able to get it to do it right, try flashing the ISO with balenaEtcher.
[00:39] <arraybolt3> Also it would be worth doing the SHA256 verification on the ISO to make sure that it's not corrupted before flashing it again.
[00:40] <Fantom> i remeber it asking and i just went with what it recomended which wasnt dd. will try again.
[00:40] <Fantom> will do thanks for the help
[00:40] <arraybolt3> Sounds good. Good luck!
[00:40] <Fantom> thanks
=== nate_ is now known as nate__
[02:19] <nate__> hi
[02:20] <nate__> v
[02:29] <arraybolt3> Hi!
[02:33] <nate__> yay
[03:23] <IrcsomeBot> <Omar> Any help here? (re @Omar: )
[03:28] <IrcsomeBot> <Arthur> Kubuntu random freeze returns for 2204.
[03:28] <IrcsomeBot> <Arthur> Such freeze commences from release of KDE plasma 5.0, disappeared for a while in 20.04 and reappeared now in 2004.
[03:28] <IrcsomeBot> <Arthur> It is the same for Cinnamon Linux mint.
[03:29] <IrcsomeBot> <Arthur> Reappeared in 2204
[03:35] <IrcsomeBot> <Arthur> I am using Intel  i5-3540, and displayed card Intel on board +nividia 650
[08:52] <Guest62> i cant sudo apt update i get and error saying The repository 'http://us.archive.ubuntu.com/ubuntu hirsute Release' no longer has a Release file.
[08:52] <Guest62> N: Updating from such a repository can't be done securely, and is therefore disabled by default. can i fix this?
[08:56] <Guest62> i even have trouble downloading app from the discover store b/c something happen to my repositorys
[09:00] <Guest62> hello?
[09:01] <Guest62> maybe everyone is asleep....
[09:02] <Guest62> i guess ill try again some other time
[09:33] <oerheks> !hirsute
[09:33] <ubottu> Ubuntu 21.04 (Hirsute Hippo) was the 34th release of Ubuntu, support ended on January 20, 2022. See !eol and https://lists.ubuntu.com/archives/ubuntu-announce/2022-January/000276.html
[09:33] <oerheks> EOL, upgrade to a supported version please
[10:08] <user|6> Buenas por algún motivo que desconozco mi kubuntu al iniciar me abre sin interfaz gráfica solo en terminal y de esta manera no me deja ejecutar startx por qué no se encuentra ns que hacer
[10:09] <alkisg> !es
[10:09] <ubottu> En la mayoría de los canales de Ubuntu, se habla sólo en inglés. Si busca ayuda en español entre al canal #ubuntu-es; escriba " /join #ubuntu-es " (sin comillas) y presione intro.
[13:37] <BluesKaj> Hi all
=== peter_ is now known as Guest6422
[23:58] <keithzg[m]> Hmm. So if I've got a session going under X11/Plasma and I leave it long enough on my 22.10 desktop, when I return it's unresponsive. That doesn't seem to happen if I use X11/Openbox, but I run into another problem I also saw under Plasma and also when using Wayland rather than X11: networking dies.