[12:06] <user__> hello
[12:57] <BluesKaj> Hi all
[14:39] <user|72> good ver. kubuntu 22.10 no sound on huawei notebook d 14 . no output to laptop speakers. bluetooth and hdmi have sound. what could be the problem?
[14:44] <oerheks> user|72, i remember that notebook, no sound is an linux wide issue
[14:48] <oerheks> sof-firmware issue; https://github.com/thesofproject/linux/issues/3350 .. no fix
[14:48] -ubottu:#kubuntu- Issue 3350 in thesofproject/linux "[BUG]  Huawei Matebook 14s headphone / speaker problem (CX8070 codec)" [Open]
 Hello house
 I connected an airpod to my laptop, it was well connected but there was no sound coming out from the airpod
[16:50] <heathcliff> Good evening! Does anyone else have issues with ipv6 on kubuntu 22.10?
[16:53] <heathcliff> I tried to ping the same things from a nas connected to the same netwrok and it was able, the problematic machine just returns "Destination unreachable: Address unreachable". Cant even ping router...... (yes the machine has proper global address)
 I went back to an old kernel (after confirming it worked in a VM) and rebooted with it using grub2. This worked, so I tried to remove the kernel I was no longer using with muon. I messed up here by not looking carefully enough; in addition to the headers and modules extra, muon removed linux-generic, which it viewed as autoinstalled for the unused kernel. I again messed up by not running update-grub.
 Now I cannot download from any repo in emergency mode, modifying grub configs does not work (I revert them with update-grub after failures)
 I downloaded the missing package and dependencies to a shared partition, mounted it, and used dpkg -i *.debEarly I got exit status 2, but it continued afterwards without issue until the very end here. : https://irc-attachments.kde.org/547f42fc/file_61402.jpg
[19:34] <arraybolt3> @paculino: That shouldn't have rendered your system unbootable... what *else* did you do?
[19:35] <arraybolt3> The linux-generic package is a metapackage, removing it shouldn't have caused damage like that.
[19:35] <arraybolt3> Did you also do an autoremove?
[19:35] <arraybolt3> (DO NOT do an autoremove, btw.)
 I autoremoved before, and sddm went away, but I fixed that.
 Here Iremoved the kernel I wasn't using, and that happened to be the one which grub had as a default and thinks it is booting into
 Uname -r returns the deleted kernel
[19:36] <arraybolt3> ...?!
[19:36] <arraybolt3> OK that's seriously weird.
[19:36] <arraybolt3> Oh wait I get it.
[19:37] <arraybolt3> You removed only the modules, modules-extra, and headers?
 That's what I intended to do, but the issues are I forgot to update grub (it refuses to change the default) and I overlooked the selection of the linux-generic
[19:38] <arraybolt3> If so, you forgot to remove the image too. In which case you should be able to run "sudo apt remove linux-image-$(uname -r)" and have it fixed. (Make good and sure that you have backup kernels first, if you only have one kernel left, this will make your system very tricky to boot.)
 I ran the dpkg -i *.deb ; apt-get install -f and here is the ending error from that
[19:38] <arraybolt3> @paculino: The linux *image* is probably still there, if so, GRUB will detect it when running update-grub and think it can boot it. You uninstalled about 70% of the kernel, but left the bootable part.
 https://irc-attachments.kde.org/b00f07c3/file_61403.jpg
[19:40] <arraybolt3> Oh shoot. That's... I dunno how to fix that...
[19:41] <arraybolt3> @paculino: Hold on, I see something.
 dpkg --list | grep linux-image does not show the 5.19 kernel I deleted which uname-r does, but after the dpkg -i *.deb ; apt-get install -f it does have the one I just installed despite the exit status errors
[19:42] <arraybolt3> @paculino: What do you see if you run "ls /dev/sd*"?
[19:42] <arraybolt3> (The photo of the screen worked fine for me.)
 Uname -r and dpkg list stuffBefore the dpkg stuff, the list only had 5.15.0-52 : https://irc-attachments.kde.org/52766c94/file_61405.jpg
[19:45] <arraybolt3> ...ok that's weird.
 https://irc-attachments.kde.org/d563e084/file_61406.jpg
[19:45] <arraybolt3> Are you able to boot normally if you can get into GRUB and boot one of the older, properly installed kernels?
 I cannot access grub when booting, at least not before the dpkg install
[19:46] <arraybolt3> what in creation... did you install Ubuntu to an NTFS partition?
[19:46] <arraybolt3> (I'm not upset, I'm just seriously confused since I don't know what to make of what I'm looking at.)
 I thought it was ext4 when I installed kubuntu, and I thought it said it was yesterday, but it does not today.
 I hope no one went and reformatted my drive (this should affect all partitions though, right?)
[19:48] <arraybolt3> No, it would be possible to reformat just a partition...
 Oh, apt-get now works and can access repos
[19:49] <arraybolt3> OK so let's try something new. Something is very awry, let's try to diagnose it.
[19:49] <arraybolt3> (Oh that's good.)
 I am running upgrade now
 Unless that's a bad idea?
[19:49] <arraybolt3> The fact that you're at a shell at all means that your OS should still be there.
[19:49] <arraybolt3> The upgrade should be fine.
 Initramfs is updating again
[19:50] <arraybolt3> OK, don't reboot yet.
[19:50] <arraybolt3> When it finishes, can you tell me what "ls /boot" shows?
 Yes, thank you for being so helpful
[19:51] <arraybolt3> Glad to help! Not sure how much help I've been being, though, it looks like it's gone haywire and now is suddenly resolving itself :P
 https://irc-attachments.kde.org/3855a6ee/file_61407.jpg
[19:52] <alkisg> paculino, what's the output of `sudo lsblk --fs` ?
[19:53] <arraybolt3> OK, what does "ls /boot/efi/EFI/ubuntu" show?
[19:53] <arraybolt3> (Somewhere it's finding that 5.19 kernel, but I have no clue where now...)
 https://irc-attachments.kde.org/b32c2c3b/file_61408.jpg
 /boot/efi appears empty
[19:55] <arraybolt3> Probably isn't mounted, then.
[19:55] <arraybolt3> "mount /dev/sda3 /boot/efi && ls /boot/efi"
 Should I now unmount the shared drive I put the package .debs on?
[19:56] <arraybolt3> I don't think you need to but it probably won't hurt.
[19:56] <alkisg> paculino, was sda4 initially ntfs, and then you formatted it with linux without re-creating the partition?
[19:56] <alkisg> Because now it's "microsoft basic data" and "ext4"...
 https://irc-attachments.kde.org/e1e52bd1/file_61409.jpg
[19:58]  * arraybolt3 throws up my hands
[19:58] <arraybolt3> Something is very wrong with your partition table...
[19:58] <arraybolt3> Is this an EFI system?
[19:58] <arraybolt3> I'm starting to think maybe it's not.
[19:59] <arraybolt3> What does "ls /sys/firmware/efi" show?
 config_table efivars esrt fw_platform_size fw_vendor runtime runtime-map systab vars
 This is on an originally Microsoft format 2 TB HDD btw
[20:01] <arraybolt3> ...ok so it *is* an EFI system, but the EFI partition is unmountable, way too big, yet the system somehow boots, but it boots into a kernel that doesn't even appear to exist any longer.
 💀
 Shall I reboot?
[20:03] <alkisg> And the purpose is to back it up, or revive it?
[20:03] <arraybolt3> I have no clue.
[20:03] <alkisg> I would definitely change the wrong partition type of sda4
 Shall I reboot after updating grub?
[20:03] <arraybolt3> I don't think that would work.
 So, mount sda4?
[20:04] <arraybolt3> You're *in* sda4.
[20:04] <arraybolt3> I mean... I guess you can try to reboot and hope it works.
[20:05] <alkisg> Do you have a live usb stick to revive it if it doesn't boot?
 I do not, but I do have home files backed up on the shared partition
[20:06] <alkisg> If you have a usb stick, make it a live one before you reboot :D
[20:06] <arraybolt3> +1
[20:06] <alkisg> (or if it boots windows, ok you can make it from windows later)
 Yeah, I have Windows on the main drive and a shared backup and linux in the external
 I'm rebooting
[20:07] <arraybolt3> Good luck!
 No change
 I will purge and reinstall grub2
[20:10] <arraybolt3> Are you still on that 5.19 kernel?
 I somehow am
[20:10] <alkisg> paculino, would you like to post a small summary of the problem? You removed packages and now the system only boots to emergency?
 Read specific 5.19 kernel I had may cause issues -> install 5.15 after checking it works in VM -> install grub2, reboot, and check it works -> try to use muon to remove all trace of 5.19 (overlook linux-generic removal) -> forget to update-grub = cannot access repos, can only boot to recovery, no changes to grub configs seem to change anything -> get linux-generic and dependencies for 22.04 LTS (not 22.04 update) and put in partition used fo
[20:16] <alkisg> And all this is one drive? Because you also mentioned an external linux drive
 That is the drive I am using.
[20:17] <alkisg> Also, is that stock kubuntu 22.10 or something else?
 External has four partitions (three for linux and one for backuo), and internal is just windows.
 22.04 with plasma from 22.10
[20:18] <alkisg> And how did you get kernel 5.19?
[20:18] <alkisg> 22.04 has 5.15...
 Muon or discover said I could update kernel to the latest compatible and I did
 That was weeks ago
[20:19] <arraybolt3> alkisg: That sounds to me like they're using the HWE kernel.
[20:20] <arraybolt3> 22.04 *might* have 5.19 available now that 22.10 has been released.
 It was 5.19-many digits
[20:20] <alkisg> I guess something strange goes on there, but anyway,
[20:20] <alkisg> so the drive you were showing us, where sda1=ntfs, sda2=ntfs, sda3=fat, and sda4=ext4, which one is it, the internal or the external?
 External; internal is windows alone
[20:21] <alkisg> And you have 2 ntfs partitions and one big fat partition for linux?
 I can't seem to purge grub2
[20:21] <alkisg> And why didn't `sudo lsblk --fs` show your internal drive? It only showed one drive
[20:21] <arraybolt3> alkisg: I think they have some small partition at the start that may be Windows' doing, then NTFS, then EFI, then ext4 for Linux.
 The fat32 is just for boot
[20:22] <alkisg> I do not see two disks in the screenshots. I see one disk.
 Windows did the small partition in order to store letter names
 My external drive cannot recognize the windows one in order to ensure no corruption of the internal drive
[20:23] <alkisg> How do you achieve that?
[20:23] <alkisg> Are you blacklisting some module?
 I have no clue how I did it
[20:24] <alkisg> So you have two EFI partitions, one on each disk?
 Internal disk is all windows without any efi
 What would be the correct way to reinstall grub2?
[20:25] <alkisg> That doesn't sound right at all :)
[20:25] <alkisg> But anyway, can we see the contents of your partitions?
[20:25] <alkisg> Please run:
[20:25] <alkisg> mount /dev/sda1 /mnt; ls /mnt
[20:25] <alkisg> umount /mnt
[20:26] <alkisg> mount /dev/sda2 /mnt; ls /mnt; umount /mnt
[20:26] <alkisg> mount /dev/sda3 /mnt; ls /mnt; umount /mnt
[20:26] <alkisg> And send a screenshot
[20:26] <alkisg> Reinstalling grub blindly won't help if you haven't first found out what you want to put and where
 SDA2 is just backups of photos, ebooks, documents, and the package.deb : https://irc-attachments.kde.org/82f1c9b3/file_61411.jpg
 It won't fit on the screen
[20:31] <alkisg> You're lacking the nls module to mount the efi partition, so you won't be able to write to it
[20:32] <alkisg> (because you're booting with 5.19 and it doesn't exist in /lib/modules)
 Is that fixable?
[20:32] <alkisg> So even grub-install won't be able to write there. Anyway, do you have networking?
 I am connected to internet and can access repos
[20:33] <alkisg> OK, can you show us your grub.cfg? cat /boot/grub/grub.cfg | nc termbin.com 9999
 Temporary failure in name resolution
 I can copy grub.cfg to the shared partition
[20:35] <alkisg> No, let's fix dns
[20:36] <alkisg> rm /etc/resolv.conf; echo nameserver 8.8.8.8 > /etc/resolv.conf
[20:36] <alkisg> Then retry the cat ... | nc command
 Same issue
[20:37] <alkisg> Does `ping 8.8.8.8` work?
 Unreachable
[20:39] <alkisg> Then you don't have networking
[20:39] <alkisg> "I can copy grub.cfg to the shared partition" ==> and then how would you put it to the internet? By rebooting to windows?
 Yes
[20:39] <alkisg> Are you using a VM now, or bare metal?
 No vm
[20:40] <alkisg> OK, let's get you some networking, you'll need it
[20:40] <alkisg> touch /test
 I have wsl and I have virtualbox, but neither will be useful now
[20:40] <alkisg> Does that work?
[20:40] <alkisg> (i.e. is your root mounted rw?)
 No errors
[20:40] <alkisg> OK, now: ip a
[20:41] <alkisg> What's the name of your ethernet, e.g. enp1s0?
 https://irc-attachments.kde.org/dea63b85/file_61412.jpg
[20:42] <alkisg> Next: /usr/lib/klibc/bin/ipconfig enp1s0
[20:42] <alkisg> And: ping 8.8.8.8
[20:43] <alkisg> Does it ping now?
 It is loading
[20:45] <alkisg> It's replying? OK then show us your grub.cfg now, with the nc | cat command
[20:45] <alkisg> cat /boot/grub/grub.cfg | nc termbin.com 9999
 It has not returned/continued to show root@ubuntu:~#
[20:47] <alkisg> The ping command? You need to press Ctrl+C to stop it
 Temporary failure again
[20:48] <alkisg> cat /etc/resolv.conf
[20:49] <alkisg> does it show: nameserver 8.8.8.8
 Command not found
[20:49] <alkisg> cat /etc/resolv.conf
[20:49] <alkisg> The cat command is there, you mistyped something
 Right
 It returns correctly
[20:50] <alkisg> Wait when you said "it is loading", did you mean the ipconfig command didn't return to the shell prompt, or that the ping command was replying?
[20:50] <alkisg> Did you see something like this? 64 bytes from 8.8.8.8: icmp_seq=3 ttl=115 time=38.8 ms
 No, just the IP config
[20:51] <alkisg> And is your ethernet connected to a router?
 I'm using wifi
[20:52] <alkisg> There's no wifi driver in the screenshot
[20:52] <alkisg> It's probably missing from your 5.19 kernel (without the /lib/modules dir)
[20:52] <alkisg> You'll need a live usb, go to windows and create one
 I'm sorry; I have no USB drive, but I can borrow a live USB next week.
 I'm sorry; I have no USB stick, but I can borrow a live USB next week.
[20:54] <alkisg> OK. It would be possible to solve this via virtualbox as well (it can be configured to boot a physical disk), but it's not worth the trouble, just wait until you get the live usb
[20:54] <alkisg> Ah one last thing,
[20:54] <alkisg> type this and send us a photo:
[20:54] <alkisg> grep vmlinuz /boot/grub/grub.cfg
 Thank you for all the help : https://irc-attachments.kde.org/9ee77b55/file_61414.jpg
[20:57] <alkisg> And this: cat /proc/cmdline
[20:57] <alkisg> (photo again)
 And this may be the root problem. I installed pop-plymouth at one point : https://irc-attachments.kde.org/71b7e158/20221111_155809.jpg
[21:00] <alkisg> You cut the screenshot too much, the kernel version doesn't show up
[21:00] <alkisg> type this as well: uname -a
 It doesn't show the kernel version
[21:01] <alkisg> And uname -r says 5.19?
 https://irc-attachments.kde.org/3daee874/file_61416.jpg
[21:02] <alkisg> OK, now reboot, and when you see the grub menu, press the down arrow to prevent it from booting
 I never see the grub menu
[21:03] <alkisg> Send us a screenshot from there
[21:03] <alkisg> Even if you click esc many times?
[21:03] <alkisg> Or even if you hold down shift?
 Escape did not work since this issue came up, but I have not tried since installing the linux-image again
[21:05] <alkisg> Copy your grub.cfg to the shared partition, then reboot. See if you can make "Esc" or "Left shift" work, otherwise go to Windows
[21:05] <alkisg> You can mount the efi partition from there, and change grub.cfg to point to ubuntu instead of popos
 Esc failed, but this time emergency mod started with the journal (all I can see is green OK)
[21:06] <alkisg> If `uname -r` says 5.19, there's nothing you can do, you don't have the modules
[21:06] <alkisg> So copy grub.cfg to the shared partition and go to windows
 A storm just arrived; power/internet may go out, but I am working on retrieving grub
[21:17] <alkisg> It's late here, I'll leave, but the idea is that you get an administrator cmd window on windows, you run `mountvol b: /s` to mount the efi partition on B:, and then you go to B:\ and edit grub.cfg, and change the UUID there from the popos to the ubuntu sda4 uuid
[21:17] <alkisg> Then it would load your ext4 /boot/grub/grub.cfg, and it will load the 5.15 kernel
 Okay, thank you so much!
[21:17] <alkisg> 👍️