[00:21] <MyComputer> Hello: I have an nvidia card - I just did an update and the package manager installed and uninstalled various drivers 15 times in a row -  now my machine is messed up.
[00:22] <MyComputer> I just built the machine.
[00:22] <MyComputer> 22.04
[00:22] <jean-loups> try with nouveau
[00:23] <MyComputer> it wont let me
[00:23] <jean-loups> $ sudo apt install nouveau
[00:23] <MyComputer> ok, ill try it
[00:24] <MyComputer> unable to locate package
[00:27] <sarnold> MyComputer: try sudo ubuntu-drivers install
[00:27] <MyComputer> ok
[00:27] <toddc> MyComputer: some else had the same issue ealier today 'sudo ubuntu-drivers install' seem to fix their issue
[00:28] <jean-loups> it's specific to ubuntu ?
[00:29] <jean-loups> un suppose, i don't know this commande
[00:29] <jean-loups> -e
[00:29] <sarnold> it *does* have 'ubuntu' right in the name :)
[00:29] <jean-loups> ok :-D
[00:32] <MyComputer> toddc - that fixed it -  but now it wont see other monitors
[00:38] <MyComputer> and nvidia settings doesnt know the name of monitor
[00:41] <logan__> Hello?
[00:41] <sarnold> pong
[00:55] <MyComputer> just did a check on another machine - synaptic wants to do the same thing - but, when i check for updates in terminal - it has nothing.
[00:55] <MyComputer> something isnt right.
[00:56] <MyComputer> is the package manager broken now ??
[00:57] <tekisui> Have You Tried Turning It Off And On Again?
[00:57] <MyComputer> turning what off  the machine?, yes.
[00:57] <tekisui> ok
[00:58] <MyComputer> it still has several and various kernel images it wants to install
[00:58] <MyComputer> but terminal has nothing
[00:59] <MyComputer> it just borked a brand new machine i just built -  so, i dont know whats up.
[00:59] <tekisui> hmm
[00:59] <tekisui> they say linux is a broken system
[00:59] <toddc> the drawback of nvida proprietary device drivers we cannot control what nvida does  I assume the drivers have a issue not related to the kernal
[01:00] <MyComputer> i see
[01:00] <MyComputer> so nvidia screwed up ?
[01:00] <tekisui> nvidia is not open source i think
[01:00] <sarnold> MyComputer: nvidia gives canonical blobs of stuff to rebuild along with the kernels
[01:00] <MyComputer> but, what i dont get is - synaptic has those updates but terminal does not.
[01:02] <MyComputer> on both machines
[01:02] <MyComputer> one is broke now.
[01:02] <toddc> that may be due to phazed updates https://ubuntu.com/server/docs/about-apt-upgrade-and-phased-updates
[01:02] <MyComputer> interesting
[01:03] <MyComputer> did someone miss the boat ?
[01:05] <MyComputer> evidently -  not many have updated or this room would be full of nvidia lovers
[01:06] <sarnold> MyComputer: nvidia and kernel updates were sent via security -- those aren't phased: https://ubuntu-archive-team.ubuntu.com/phased-updates.html
[01:06] <MyComputer> I have been with ubuntu since 6.06 and never have had these issues.
[01:06] <toddc> part the reason phased updates is used so IF there is a issue it can be pulled or fixed before mass rollout
[01:07] <MyComputer> arnold  i see.
[01:07] <MyComputer> so, should i wait a week to see if this is corrected before updating another machine ?
[01:08] <MyComputer> cuz, i have to rebuild my brand new one.
[01:13] <MyComputer> maybe nvidias A.I. is broke.
[01:13] <MyComputer> have a good day folks
[01:15] <morgan-u2> how can I get to the desktop without minimizing each individual window?  22.04  (easy in 20.04
[03:18] <alkisg1> morgan-u2: ctrl+win+d
[05:29] <chicken_m> https://www.youtube.com/shorts/cTEXI6hVYWM
[05:44] <webchat49> Hi
[05:46] <webchat49> is this support channel?
[05:46] <chicken_m> yes
[05:47] <webchat49> can i ask here any technical issue related to my pc?
[05:47] <chicken_m> no
[05:48] <webchat49> so what is this for?
[05:48] <thomasb9511> Support for Ubuntu related stuff
[05:49] <webchat49> my terminal not working
[05:49] <webchat49> in ubuntu system
[05:52] <mosfet> Ctrl + Alt + T?
[05:52] <mosfet> Alt+F2 gnome-terminal
[05:53] <mosfet> or xterm
[08:48] <bumblefuzz> so, how do I force password authentication during ssh authentication?
[08:49] <bumblefuzz> it keeps trying to default to key based and I know that's better but I'm doing something unique where it's ok
[08:49] <bumblefuzz> I just need it to connect to a machine that doesn't have the key on it
[08:58] <rony> hi
[12:20] <BluesKaj> Hi all
[12:21] <hid3> Hello. I am trying to use ununtu installer to install ubuntu server 22.04 LTS. However, I am really confused with the CLI partitioning guide. I need to create a non-LVM partition "/boot", then LVM for swap and LVM for root partition. However, if I create first local partition, then LVM option gets greyed out. If I create LVM first then creating a raw partition seems impossible. What am i doing wrong?
[12:37] <hid3> Anyone? Am I the only one finding ubuntu's installer super difficult?
[12:38] <BluesKaj> !UEFI
[12:44] <annexseven> bumblefuzz, try the AuthenticationMethods option in your /etc/ssh/sshd_config (or make a new file in /etc/ssh/sshd_config.d/).
[12:45] <annexseven> See man 5 sshd_config
[12:48] <tomreyn> hid3: configure things in layers: first create all the partitions on all drives you want to partition for the OS installation (keep in mind you could also do that later if it's not about the OS, such as pure data partitions). also set file systems for partitions which will not contain further layers. then do SW RAID, then crypto, then LVM, then the remaining file systems.
[12:49] <tomreyn> hid3: see also https://help.ubuntu.com for the server documentation
[12:49] <hid3> to me it looks like the installer is very limited (feature-wise), at least on partitioning
[12:50] <tomreyn> what are you missing?
[12:51] <hid3> as I said - I want to combine both, regular partition and LVM volume on one disk. It seems to be simply impossible to do that
[12:53] <tomreyn> hmm, i would think this should work, but not 100% sure. you can always use debootstrap or resort to autoinstall, where you have a lot more options
[12:53] <hid3> yeah, I know, but this is the 'hard way', or expert mode
[12:53] <hid3> I somehow expected simple things would be configurable out of the box with no sweat
[12:54] <tomreyn> there's also #ubuntu-server, maybe they can tell whether you use case is covered
[12:54] <hid3> thanks
[12:55] <tomreyn> though that can be more lively on business days.
[13:24] <kumaran> hi
[13:41] <throwthecheese> Is there any way to coax nautilus into exporting its menu and using a traditional header? I would like to take advantage of the touchscreen support it offers but it doesn't mesh well into my current desktop setup that uses global menus
[13:57] <tekisui> [print-screen] seems to be gone ?
[14:35] <jhutchins> hid3: Linux is like Ikea.  You get all the parts, but it's up to you to put it together.
[14:35] <tekisui> :)
[14:35] <tekisui> and one wrench for 2000 parts
[14:36] <ppw> which part allows me to extract video bioses?
[14:38] <ioria> https://unix.stackexchange.com/questions/613910/dump-vga-bios-from-linux
[14:58] <meta-coder> Where are different kernel flavours like linux-gkeop, linux-gke, etc documented?
[15:20] <jhutchins> meta-coder: You might check with kernel.org, but that sounds like it's an independent project.  There should be information in the README files.
[15:25] <meta-coder> jhutchins: I meant something like this https://ubuntu.com/kernel/variants but this list is not complete. There are more variants like linux-intel linux-iot etc
[15:26] <jhutchins> meta-coder: So who's responsibility is it to discover and document all of the independent kernel projects?
[15:56] <tekisui> [print-screen] seems to be gone ?
[16:00] <imi> hi, what are gnome-3-38-2004 and gnome-42-2204 snap packages good for? is my GDM shipped as a snap package? will my system run OK if I remove these?
[16:15] <tomreyn> imi: i think these are gnome libraries / runtime environments for previous gnome releases, so that you can run snaps which depend on those
[16:16] <tomreyn> if well done, "snap info <package>" will explain what a package is about
[16:38] <imi> when I remove a snap package it makes a snapshot of user settings. where are those stored at?
[16:45] <ravage> imi: /var/lib/snapd/snapshots
[17:46] <u8353v[m]> Is EXT4 the best file system for external SSD, SD Card, and flash drive, to use exclusively with Linux systems?
[17:47] <oerheks> ext4 is good enough.
[17:47] <cbreak> depends on what you're looking for
[18:05] <ogra> imi, if you do not want a snapchot taken just use --purge for the remove command ... also ... to find what used the gnome library snaps you can run "snap connections" ... and perhaps grep for gnome in the output if you have many snaps...
[18:06] <ogra> s/used/uses/
 "depends on what you're looking..." <- compatibility and stability!
[18:09] <u8353v[m]> not cutting edge or latest and greatest..
[18:09] <u8353v[m]> just what works 🙂
[18:15] <ravage> that is ext4
[18:16] <oerheks> +1
[18:28] <tekisui> screenshot is kaput ?
[18:28] <tekisui> print screen doesn´t work anymore
[18:28] <cbreak> works for me
[18:28] <tekisui> ah
[18:32] <jhutchins> tekisui: So that's what you were on about.  I thought someone stole a piece of your keyboard.
[18:32] <tekisui> i tried restting the key bindings but nope
[18:33] <jhutchins> tekisui: Do you have a screenshot tool in you application menu?
[18:33] <tekisui> flameshot
[18:33] <jhutchins> tekisui: Does it work?  (By the way, IRC does not charge by the word.)
[18:33] <tekisui> ?
[18:34] <tekisui> yes flameshot works
[18:34] <tekisui> :)
[18:34] <jhutchins> tekisui: You tried setting the ps key to launch flameshot?
[18:34] <tekisui> ps ?
[18:35] <tekisui> printscreen would work normally
[18:35] <jhutchins> Print Screen
[18:35] <tekisui> ahh so
[18:36] <jhutchins> I don't seem to have that enabled.
[18:37] <jhutchins> tekisui: I would check that the command launches from the launcher when you type it in, then paste that as a shortcut.  I don't know if gnome will allow that key as a shortcut.
[18:37] <tekisui> ah it worked a day ago
[18:38] <jhutchins> What changed?
[18:38] <tekisui> maybe i done an update
[18:40] <jhutchins> tekisui: https://en.wikipedia.org/wiki/GNOME_Screenshot
[18:40] <tekisui> merci
[18:41] <jhutchins> tekisui: Let me know if it helps.
[18:41] <tekisui> ok
[18:41] <jhutchins> tekisui: Otherwise you may be stuck until next week when people get back from their holiday.
[18:41] <tekisui> woohooo
[18:41] <tekisui> cool
[18:42] <tekisui> next week i might take a holliday to spain
[18:42] <cbreak> tried to reboot? :/
 "that is ext4" <- perfect 😉
[18:45] <vershan> running ubuntu 22.04. my system used to take 20 sec to boot now for the last week I have to wait between 4 to 5 minutes before I get to the login screen
[18:48] <oerheks> journalctl -b # would show your boottimes
[18:49] <ravage> vershan: sudo systemd-analyze blame | nc termbin.com 9999
[18:50] <ravage> paste the URL that outputs. it shows the times your services need to start uo
[18:50] <ravage> up
[18:50] <vershan> @ravage, one moment getting this now
[18:52] <vershan> @ravage, https://pastebin.com/zXmZHi1K
[18:52] <ravage> that all looks great
[18:53] <ravage> you try press "ESC" while the ubuntu logo is showing
[18:53] <ravage> maybe it helps you to see whats going on. or what exactly is visisble on the screen while you are waiting?
[18:54] <vershan> @ravage, thank  you ill reboot and hit the esc to see whats halting the system
[18:54] <vershan> thank you kindly :)
[18:57] <jhutchins> I've actually been able to get a linux boot process to pause with the "Pause" key.  It was SysV but it's worth a try.
[18:58] <jhutchins> (Of course, the whole point of systemd is that it's non-linear.)
[18:58] <ppw> ooh non-linear
[18:58] <vershan> @ravage, a start stop has started for a disk and it gives the UUID. Any reason why this will happen on every reboot. It halts the system by 3 to 4 minutes
[18:58] <vershan> job
[19:09] <jhutchins> Vercas: Can you un-mount the disk before shutdown?
[19:09] <jhutchins> Vercas: Bah, sorry.  Impatient children.
[19:10] <jhutchins> Usually the device is un-reachable and the system can't get a clean shutdown reply.
[19:10] <jhutchins> Often happens with net shares when networking goes down before they're unmounted.
[19:18] <x7upLime> can snap whatsapp post notifications to the system notification list?
[19:20] <jhutchins> x7upLime: Does it?
[19:20] <x7upLime> jhutchins That's what I was hoping
[19:20] <oerheks> check settings <>  notifications??
[19:21] <jhutchins> x7upLime: Try it, report back, and we'll all know.
[19:22] <jhutchins> x7upLime: https://www.livemint.com/technology/tech-news/how-to-enable-whatsapp-notifications-on-your-laptop-11663157696131.html
[19:22] <x7upLime> I have all options crossed for notifications inside the app
[19:22] <jhutchins> x7upLime: Containers are meant to prevent applications from accessing the system.  Yours appears to have succeeded.
[19:23] <oerheks> or settings <> applications <> permissions ans access
[19:23] <x7upLime> So far I have only notifications sound
[19:23] <x7upLime> I'd like whatsapp to post notifications also
[19:23] <oerheks> where applications is whatsapp desktop, i guess
[19:23] <x7upLime> jhutchins are you saying it is not possible ?
[19:24] <x7upLime> oerheks yes
[19:24] <jhutchins> x7upLime: Unless you can figure out otherwise.  It's possible that it just doesn't have access.
[19:24] <oerheks> so, 2 places to check
[19:24] <jhutchins> x7upLime: You could try a normal non-snap install and see how that works, see if the knowledge transfers to the snap.
[19:36] <eraste> hi
[19:40] <cbreak> yeah, snap is a pain :(
[19:40] <cbreak> it's sad that the devs didn't think of making it properly configurable
[19:41] <oerheks> or the whatsapp prop software developer and packager..
[19:41] <cbreak> in my case, I'm annoyed with the firefox snap
[19:42] <cbreak> 1password extension still can't communicate with the outside 1password application, and it's been over a year
[19:42] <cbreak> the sad thing is that all of this worked fine, until snap broke it
[19:43] <oerheks> same for the Belgium electronic ID
[19:43] <oerheks> sad
[19:43] <oerheks> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1971594
[19:43] -ubottu:#ubuntu- Launchpad bug 1741074 in firefox (Ubuntu) "[snap] chrome-gnome-shell extension fails to detect native host connector" [High, In Progress] [duplicate: 1971594]
[19:47] <cbreak> it's not even been assigned to anyone... guess they don't care
[19:49] <jhutchins> The whole point of systems like snap is that they DON'T touch anything on the main system.
[19:50] <jhutchins> It's like docker, they built the system to be impenetrable on a networked system, and the first thing everybody asked for was access to and from the network.
[19:51] <cbreak> it's as if it was a dumb idea :)
[19:51] <jhutchins> The most secure system is powered off, disconnected, and unassembled.  All storage should be wiped.
[21:19] <UdderlyEvelyn> heya.. i have a ubuntu install and i didn't realize it was sharing EFI partition with an old copy of another linux (on a different drive from the actual copy of ubuntu) which i blew away yesterday. how can i create a new EFI partition/grub/etc. for that copy of ubuntu on the disk that it's actually installed on? easy enough to shrink the ubuntu
[21:19] <UdderlyEvelyn> partition and make a new partition fot the EFI, and i know how to do grub stuff, but i've never actually set up the EFI partition or done the grub from scratch before. assistance?
[21:22] <toddc> UdderlyEvelyn: you can manually set it or boot repair usually worls well https://help.ubuntu.com/community/Boot-Repair
[21:27] <cbreak> https://askubuntu.com/questions/1281256/help-avoiding-ubuntu-installer-bug-where-grub-installs-to-wrong-disk strikes again?
[21:27] <UdderlyEvelyn> it was a triple boot situation with an existing linux
[21:27] <UdderlyEvelyn> and it hijacked the other linux's existing EFI and stuck its stuff in there
[21:28] <UdderlyEvelyn> it was a few years ago, idr how/why it did that or if it was my own fault
[21:28] <oerheks> it takes the EFI partition of the disk it boots from, logical
[21:28] <UdderlyEvelyn> was trying to set it up on its own disk, each OS has its own physical disk
[21:29] <UdderlyEvelyn> anyway im a bit nervous to use a tool that purports to sort something out automatically when the situation is a bit more complex
[21:29] <UdderlyEvelyn> ..and i wouldn't learn if it did
[21:30] <toddc> https://help.ubuntu.com/community/UEFI
[21:30] <oerheks> every disk its own EFI partition... then you need to change manually every boot
[21:32] <toddc> normally i use one efi boot partition for all mutiboot so no need to set the boot path each time    last linux install will usually take control of all other bootable os's
[21:32] <cbreak> I think it's a well known bug in the installer
[21:33] <cbreak> despite it offering selection of the efi to target, it completely seems to ignore the user choice and pick a random other efi partition, sometimes
[21:34] <UdderlyEvelyn> the copy of ubuntu is unlikely to stick around forever, and the other linux is QubesOS which doesn't easily play ball with other OSes and needs custom grub entries written by hand
[21:34] <UdderlyEvelyn> but i need it bootable for now until i have everything set up
[21:34] <cbreak> you can have multiple copies of grub in the same EFI
[21:34] <cbreak> (in different subdirectories)
[21:34] <cbreak> if you want
[21:34] <oerheks> good luck with bootrepair
[21:35] <UdderlyEvelyn> cbreak: i guess that's what it had set up before, it was like /boot/efi/EFI/qubes and /boot/efi/EFI/ubuntu
[21:35] <cbreak> probably.
[21:36] <EriC^^> UdderlyEvelyn: i can walk you through it if you want
[21:36] <UdderlyEvelyn> ok so i have the EFI partition created per those instructions, how do i perform an install of grub/etc. to this partition for the copy of ubuntu in question from elsewhere
[21:37] <EriC^^> (manually setting up a separate efi partition)
[21:37] <UdderlyEvelyn> yeah would appreciate
[21:37] <UdderlyEvelyn> i have a 200MB fat32 esp boot partition made
[21:37] <UdderlyEvelyn> just need to populate it now, am booted into qubes atm.
[21:38] <EriC^^> you're creating it for ubuntu or qubes?
[21:39] <UdderlyEvelyn> for a copy of ubunu on another disk
[21:39] <UdderlyEvelyn> separate EFI, separate everything
[21:39] <UdderlyEvelyn> i can mount the disk in a debian or fedora VM to work with, or if need be i could set up a ubuntu VM but that'd take a little longer
[21:40] <EriC^^> i'm just confused, why dont you boot into ubuntu to set it up?
[21:40] <UdderlyEvelyn> u mean a live or smth? don't have one made
[21:40] <UdderlyEvelyn> thought i could do it from the other linux
[21:40] <EriC^^> didnt you install ubuntu and turned out it used a shared efi and want it to have its own?
[21:41] <EriC^^> you could i mean, you could chroot into the ubuntu install from qubes if you want
[21:42] <UdderlyEvelyn> i installed windows, then qubes, bricked qubes, put ubuntu where windows was, reinstalled qubes on a third disk, then wiped the old qubes partition to put windows on again not realizing the EFI for ubuntu was there
[21:42] <UdderlyEvelyn> over a 2 year period :p
[21:42] <EriC^^> oh ok
[21:43] <EriC^^> ok, type "sudo parted -ls | nc termbin.com 9999"
[21:44] <EriC^^> (so we're making a separate efi partition for ubuntu on its disk, booted from qubes right now)
[21:44] <cbreak> wonder what's on your current efi partitions. You deleted their contents too?
[21:45] <UdderlyEvelyn> huh never seen that, a term-based pastebin eh?
[21:45] <UdderlyEvelyn> cbreak: well i deleted the one
[21:45] <EriC^^> yeah
[21:45] <oerheks> cbreak, from the 2nd disk, reading from the beginning
[21:46] <UdderlyEvelyn> the way qubes works i cant actually do that from the host linux, i can do it in a VM with the disk in question attached, however.
[21:46] <EriC^^> i see, that works
[21:46] <UdderlyEvelyn> lol netcat not installed, rofl..
[21:46] <UdderlyEvelyn> makes sense for a sec-oriented distro *installs*
[21:47] <UdderlyEvelyn> https://termbin.com/dlrg
[21:47] <UdderlyEvelyn> xvdi is the disk in question
[21:48] <EriC^^> aha, type "sudo mount /dev/xvdip1 /mnt"
[21:49] <EriC^^> er, it might be /dev/xvdi1
[21:50] <UdderlyEvelyn> mk mounted
[21:50] <UdderlyEvelyn> im not a total noob ya know, just havent ever installed an efi partition by hand or messed with grub w/o the automated tools xD
[21:50] <UdderlyEvelyn> well aware how to mount partitions x3
[21:51] <EriC^^> gotcha
[21:51] <UdderlyEvelyn> ok so we're gonna chroot into it? been a minute since i used chroot.
[21:51] <EriC^^> type "for i in /dev /proc /sys /run; do sudo mount -R $i /mnt$i; done"
[21:51] <EriC^^> yeha
[21:52] <UdderlyEvelyn> ran that.. looks odd.
[21:52] <UdderlyEvelyn> no output
[21:52] <EriC^^> great
[21:53] <EriC^^> type "sudo chroot /mnt"
[21:54] <EriC^^> all good?
[21:55] <UdderlyEvelyn> mhm
[21:56] <EriC^^> ok, type "blkid /dev/xvdi2"
[21:56] <EriC^^> then "nano /etc/fstab"
[21:57] <EriC^^> add the following line
[21:57] <EriC^^> UUID=5EA9-7663  /boot/efi       vfat    umask=0077      0       1
[21:57] <EriC^^> replace the UUID=numbers with the numbers you got from blkid's output
[21:58] <EriC^^> probably you already have a line there for the efi, so just replace the uuid in that line
[21:58] <UdderlyEvelyn> uuid or partuuid?
[21:58] <EriC^^> uuid
[21:59] <EriC^^> after saving the file, try "mount /boot/efi"
[22:01] <UdderlyEvelyn> "/boot/efi was left on /dev/sdc1 during installation" yeah..
[22:01] <UdderlyEvelyn> done
[22:01] <EriC^^> ok, type "grub-install"
[22:02] <UdderlyEvelyn> install device isn't specified
[22:02] <UdderlyEvelyn> grub-install /dev/xvdi?
[22:02] <EriC^^> no
[22:02] <EriC^^> usually the efi grub doesnt take an argument
[22:02] <UdderlyEvelyn> dunno what to tell ya on that
[22:03] <UdderlyEvelyn> it said "installing for i386-pc platform" which sounds very 32-bit of it too
[22:03] <EriC^^> i wonder something, just quickly try "dpkg -l | grep grub | nc termbin.com 9999"
[22:03] <UdderlyEvelyn> possible there's two copies of gru?
[22:03] <UdderlyEvelyn> b
[22:04] <UdderlyEvelyn> https://termbin.com/n3om
[22:04] <UdderlyEvelyn> that took a sc
[22:04] <UdderlyEvelyn> def two copies from the looks of it
[22:04] <UdderlyEvelyn> not sure why, probably some reason in the deep past
[22:04] <EriC^^> these days ubuntu seems to install both *shrug*
[22:05] <EriC^^> anyways, type "grub-install --target=x86_64-efi"
[22:06] <UdderlyEvelyn> error, cannot find EFI directory
[22:06] <UdderlyEvelyn> guessin i need to mount the new EFI post-fstab manually?
[22:06] <UdderlyEvelyn> since it didn't "boo"
[22:06] <UdderlyEvelyn> boot*
[22:07] <EriC^^> no, running "mount /boot/efi" should have mounted it
[22:07] <UdderlyEvelyn> was just scrolling up, yeah, mb i forgot o
[22:07] <UdderlyEvelyn> to*
[22:07] <UdderlyEvelyn> yup
[22:07] <EriC^^> no worries
[22:07] <UdderlyEvelyn> sorry i was cooking dinner at the same time until just the last min
[22:07] <UdderlyEvelyn> xD
[22:07] <EriC^^> :D
[22:07] <UdderlyEvelyn> efi variables cannot be set on this system
[22:07] <UdderlyEvelyn> you will have to complete the grub setup manually
[22:08] <UdderlyEvelyn> no error reported
[22:08] <EriC^^> ouch
[22:08] <EriC^^> i think it's not booted in uefi mode
[22:08] <UdderlyEvelyn> i mean it's a VM
[22:08] <EriC^^> try "ls /sys/firmware/efi"
[22:08] <UdderlyEvelyn> so that'd.. make sense
[22:08] <EriC^^> aha
[22:09] <EriC^^> i honestly dont know what qubes is
[22:09] <UdderlyEvelyn> it routes everything through vms for isolation and maximal security
[22:09] <UdderlyEvelyn> shud take a peek it's neat
[22:09] <UdderlyEvelyn> xD
[22:09] <EriC^^> we could copy the efi file to the default paths, if you select the hdd in the bios it should look there and boot it, then you could run grub-install again when it's booted in uefi mode
[22:09] <UdderlyEvelyn> sounds good
[22:10] <UdderlyEvelyn> it looks like it has the files in the right spots tbh
[22:10] <EriC^^> type "mkdir -p /boot/efi/efi/boot /boot/efi/efi/microsoft/boot"
[22:10] <UdderlyEvelyn> microsoft? wat
[22:10] <UdderlyEvelyn> lol
[22:11] <EriC^^> i'm secretly converting you to the light
[22:11] <EriC^^> j/k
[22:11] <UdderlyEvelyn> in a linux help channel
[22:11] <UdderlyEvelyn> blasphemous behavior
[22:11] <UdderlyEvelyn> it has /boot/efi/EFI/ubuntu with what appear at a glance to be the correct files
[22:11] <UdderlyEvelyn> grub.cfg and a few .efi files
[22:12] <UdderlyEvelyn> might already be done and was lying?
[22:12]  * cbreak uses refind to select which bootloader to boot from, less trouble than manipulating efi directly
[22:12] <EriC^^> nah, the last step is to add those files to the uefi list in the mobo, but it couldnt, so mobo has no idea where they are to boot them
[22:13] <UdderlyEvelyn> alright, ran the mystery mkdir command
[22:13] <cbreak> you could do the last step manually with efibootmgr, but that also requires access to efi, so probably won't work in vm
[22:13] <EriC^^> alright
[22:13] <EriC^^> yeah cbreak
[22:13] <UdderlyEvelyn> lemme see if the base system has that tool accessible, maybe could do it in that then
[22:13] <EriC^^> actually does qubes have access to the uefi list?
[22:13] <EriC^^> yeah
[22:13] <UdderlyEvelyn> it oes
[22:13] <UdderlyEvelyn> efibootmgr is accessible from dom0
[22:13] <EriC^^> nice
[22:13] <UdderlyEvelyn> so i can detach it from the VM and finish it there
[22:13] <UdderlyEvelyn> if i dont have to be chrooted
[22:14] <EriC^^> wlel,
[22:14] <UdderlyEvelyn> tho maybe i can do that there anyway
[22:14] <UdderlyEvelyn> sec
[22:14] <UdderlyEvelyn> no internet in dom0
[22:14] <EriC^^> we need qubes to see the efi partition though
[22:14] <UdderlyEvelyn> yeah that's not a problem
[22:14] <EriC^^> ok cool
[22:14] <UdderlyEvelyn> same process but diff device address, ill be a sec, will let u know when im chrooted in and ready
[22:15] <EriC^^> ok
[22:16] <UdderlyEvelyn> can't find the UUID on the disk.. im guessing cuz it was virtualized before
[22:16] <UdderlyEvelyn> so ill go redo that
[22:17] <cbreak> UdderlyEvelyn: you don't really need to know it
[22:17] <cbreak> (but blkid or lsblk with some parameters should show it)
[22:17] <UdderlyEvelyn> mmm
[22:18] <EriC^^> yeah we just need to pass it the /dev/blabla of the partition
[22:18] <UdderlyEvelyn> isnt showing sdb2 because it was made in the DM
[22:18] <UdderlyEvelyn> how can i uh.. refresh that
[22:18] <cbreak> I think it can even work with the mountpoint, not sure
[22:18] <UdderlyEvelyn> i guess i can reboot if need be, but then ill have to rejoin this webchat heh
[22:21] <EriC^^> as you wish UdderlyEvelyn
[22:22] <EriC^^> copying and renaming efi file to those dirs we created should also get it booted, if that's easier at this point
[22:23] <UdderlyEvelyn> that sounds easier than rebooting and setting the environment up again yeah
[22:23] <UdderlyEvelyn> tho i did take down the instructions for future reference either way just now
[22:24] <EriC^^> ok, copy /boot/efi/efi/ubuntu/shimx64.efi to /boot/efi/efi/boot/bootx64.efi and /boot/efi/efi/microsoft/boot/bootmgfw.efi
[22:26] <UdderlyEvelyn> target is busy when trying to unmount gah.
[22:26] <UdderlyEvelyn> reboot it is
[22:26] <UdderlyEvelyn> bbiab
[22:29] <UdderlyEvelyn> guess it was already fine, noticed ubuntu was in the list, half-expected it to fail to boot, but it works now anyway
[22:30] <UdderlyEvelyn> it has come back from the dead
[22:30] <EriC^^> great!
[22:30] <UdderlyEvelyn> much thanks, and learned stuff which will make me less needy in future EFI situations.
[22:31] <EriC^^> you're welcome, could you type "sudo efibootmgr -v | nc termbin.com 9999" just to confirm it's using the new one?
[22:31] <MrMobius> where does ubuntu desktop mount additional hard drives? I can open them in the GUI but /mnt is empty
[22:31] <UdderlyEvelyn> https://termbin.com/ijek
[22:32] <UdderlyEvelyn> i was looking at the EFI entries earlier in some windows tools and noticed that *somewhere* a bunch of old entries exist
[22:32] <cbreak> MrMobius: try running `findmnt` on the command line, it'll show all mountpoints
[22:32] <UdderlyEvelyn> for operating systems that haven't been installed on here for ages
[22:32] <EriC^^> ok, type "sudo blkid | nc termbin.com 9999"
[22:33] <UdderlyEvelyn> https://termbin.com/tradi
[22:33] <UdderlyEvelyn> guessing the uuid was in fact genuine
[22:33] <MrMobius> cbreak: thanks. they are in /media
[22:33] <EriC^^> this was the UUID="BCFD-7D4F" you used before in fstab right UdderlyEvelyn ?
[22:34] <UdderlyEvelyn> yeah
[22:34] <UdderlyEvelyn> and it lines up with /dev/sdb2
[22:34] <UdderlyEvelyn> with the partuuid
[22:34] <UdderlyEvelyn> so looks good
[22:34] <EriC^^> yup
[22:34] <EriC^^> all good
[22:34] <UdderlyEvelyn> any idea how i can clear out all the random junk in my EFI list?
[22:34] <UdderlyEvelyn> kali and debian and such
[22:34] <EriC^^> sudo efibootmgr -B -b <number>
[22:35] <UdderlyEvelyn> what are VenHw entries?
[22:35] <UdderlyEvelyn> vendor.. hardware..?
[22:36] <UdderlyEvelyn> *pokes at the efi specification*
[22:36] <UdderlyEvelyn> hardware device path
[22:36] <UdderlyEvelyn> mm
[22:37] <UdderlyEvelyn> why do i have three of these with the same uuid and different OS names
[22:37] <UdderlyEvelyn> Boot0000* Windows Boot Manager	HD(1,GPT,570f307e-6f38-49a4-9785-b619833bae54,0x800,0x12c000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a................
[22:37] <UdderlyEvelyn> Boot0001* kali	VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
[22:37] <UdderlyEvelyn> Boot0002* debian	VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
[22:37] <UdderlyEvelyn> Boot0003* Qubes	VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
[22:37] <UdderlyEvelyn> Boot0004* ubuntu	VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)
[22:37] <UdderlyEvelyn> Boot0005* Qubes OS	HD(1,GPT,570f307e-6f38-49a4-9785-b619833bae54,0x800,0x12c000)/File(\EFI\QUBES\GRUBX64.EFI)
[22:37] <EriC^^> hmm, no idea
[22:37] <cbreak> UdderlyEvelyn: try efibootmgr -v
[22:38] <UdderlyEvelyn> yeah that's what im talking about, https://termbin.com/ijek
[22:39] <EriC^^> maybe it's the partuuid of the hdd?
[22:40] <EriC^^> sudo blkid /dev/sd{a,b,c}
[22:40] <UdderlyEvelyn> i did blkid | grep <that uuid> and nothin
[22:41] <EriC^^> try with "blkid /dev/sdX"
[22:41] <UdderlyEvelyn> doin that yields nothing on any hdd
[22:41] <UdderlyEvelyn> even w/o the grep
[22:41] <EriC^^> use sudo
[22:42] <UdderlyEvelyn> it is not any of those
[22:43] <EriC^^> *shrug*
[22:44] <tomreyn> https://blog.m.fago.me/2020/08/05/venhw99e275e7-75a0-4b37-a2e6-c5385e6c00cb-indicates-broken-boot-entry-in-gigabyte-uefi/
[22:44] <tomreyn> note the identical uuid
[22:45] <UdderlyEvelyn> interesting
[22:45] <UdderlyEvelyn> so i can yeet any entries, right, cuz they're just old junk?
[22:45] <UdderlyEvelyn> anything with that id
[22:45] <UdderlyEvelyn> good thought googling that specific id, assumed it was unique to me
[22:45] <EriC^^> i'm guessing yeah, cause it's using this boot successfully
[22:47] <UdderlyEvelyn> nice and clean now
[22:47] <EriC^^> i wonder if it's a refind thing, did you have it installed?
[22:47] <UdderlyEvelyn> ive never heard of refind
[22:47] <EriC^^> ah nevermind
[22:48] <UdderlyEvelyn> thank u btw tomreyn :)
[22:48] <cbreak> refind is great :)
[22:48] <cbreak> it's an efi boot chooser
[22:48] <UdderlyEvelyn> everything happy and clean here - except windows, it's broken because it's windows so that's normal
[22:49] <UdderlyEvelyn> yeah i looked it up after that exchange
[22:49] <UdderlyEvelyn> looks interesting
[22:50] <UdderlyEvelyn> time for a break after that, then ill go fix windows too (well, as much as one can fix it.. heheh)
[23:01] <Jaffo> Good evening. Cn someone tell me if i change my hostname on my ubuntu 22.04 linode instance do i need to do something to make SSH work again. I can no longer connect
[23:03] <EriC^^> how are you connecting Jaffo ? did you change anything else?
[23:05] <Jaffo> I am trying to connect via putty. I was connected via putty and changed hostname via hostnamectl and rebooted. now i cant get in from putty. I can connect using the LISH console
[23:05] <Jaffo> linodes own terminal web app
[23:06] <cbreak> can you ping it? do you know its ip address? (if you can connect via that other way, 'ip a' will show it)
[23:07] <Jaffo> disregard. i'm in need of coffee
[23:08] <Jaffo> I forgot to 'enable' port 22 on the firewall after adding it to the instance
[23:08] <Jaffo> I'm back in business.
[23:08] <N3X15> Any guides on how to make blacklisting kernel modules stick?  I made /etc/modprobe.d/blacklist-audio.conf with a list of blacklist directives (blacklist something\nblacklist something_else) and it doesn't seem to be taking effect, even after sudo update-initramfs -u. I can see the added entries in modprobe -c
[23:09] <jeremy31> Do the modules load at boot?
[23:09] <N3X15> Yep.
[23:10] <jeremy31> What modules
[23:11] <N3X15> snd, snd_compress, etc
[23:12] <jeremy31> Check modinfo modulename and see if they are built-in the kernel
[23:12] <N3X15> Will do, thanks.
[23:15] <jeremy31> Post URL from terminal for> cat /etc/modprobe.d/blacklist-audio.conf|nc termbin.com 9999
[23:34] <takatzu> hola algun latino en la sala
[23:35] <tomreyn> !es | takatzu
[23:36] <takatzu> hello
[23:36] <takatzu> help in repository