[12:06] hello [12:57] Hi all [14:39] 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] user|72, i remember that notebook, no sound is an linux wide issue [14:48] 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] [15:36] Hello house [15:36] I connected an airpod to my laptop, it was well connected but there was no sound coming out from the airpod [16:50] Good evening! Does anyone else have issues with ipv6 on kubuntu 22.10? [16:53] 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) [19:31] 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. [19:31] Now I cannot download from any repo in emergency mode, modifying grub configs does not work (I revert them with update-grub after failures) [19:34] 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] @paculino: That shouldn't have rendered your system unbootable... what *else* did you do? [19:35] The linux-generic package is a metapackage, removing it shouldn't have caused damage like that. [19:35] Did you also do an autoremove? [19:35] (DO NOT do an autoremove, btw.) [19:36] I autoremoved before, and sddm went away, but I fixed that. [19:36] 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 [19:36] Uname -r returns the deleted kernel [19:36] ...?! [19:36] OK that's seriously weird. [19:36] Oh wait I get it. [19:37] You removed only the modules, modules-extra, and headers? [19:38] 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] 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.) [19:38] I ran the dpkg -i *.deb ; apt-get install -f and here is the ending error from that [19:38] @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. [19:40] https://irc-attachments.kde.org/b00f07c3/file_61403.jpg [19:40] Oh shoot. That's... I dunno how to fix that... [19:41] @paculino: Hold on, I see something. [19:42] 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] @paculino: What do you see if you run "ls /dev/sd*"? [19:42] (The photo of the screen worked fine for me.) [19:44] 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] ...ok that's weird. [19:45] https://irc-attachments.kde.org/d563e084/file_61406.jpg [19:45] Are you able to boot normally if you can get into GRUB and boot one of the older, properly installed kernels? [19:46] I cannot access grub when booting, at least not before the dpkg install [19:46] what in creation... did you install Ubuntu to an NTFS partition? [19:46] (I'm not upset, I'm just seriously confused since I don't know what to make of what I'm looking at.) [19:48] I thought it was ext4 when I installed kubuntu, and I thought it said it was yesterday, but it does not today. [19:48] I hope no one went and reformatted my drive (this should affect all partitions though, right?) [19:48] No, it would be possible to reformat just a partition... [19:48] Oh, apt-get now works and can access repos [19:49] OK so let's try something new. Something is very awry, let's try to diagnose it. [19:49] (Oh that's good.) [19:49] I am running upgrade now [19:49] Unless that's a bad idea? [19:49] The fact that you're at a shell at all means that your OS should still be there. [19:49] The upgrade should be fine. [19:50] Initramfs is updating again [19:50] OK, don't reboot yet. [19:50] When it finishes, can you tell me what "ls /boot" shows? [19:50] Yes, thank you for being so helpful [19:51] 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 [19:52] https://irc-attachments.kde.org/3855a6ee/file_61407.jpg [19:52] paculino, what's the output of `sudo lsblk --fs` ? [19:53] OK, what does "ls /boot/efi/EFI/ubuntu" show? [19:53] (Somewhere it's finding that 5.19 kernel, but I have no clue where now...) [19:54] https://irc-attachments.kde.org/b32c2c3b/file_61408.jpg [19:54] /boot/efi appears empty [19:55] Probably isn't mounted, then. [19:55] "mount /dev/sda3 /boot/efi && ls /boot/efi" [19:55] Should I now unmount the shared drive I put the package .debs on? [19:56] I don't think you need to but it probably won't hurt. [19:56] paculino, was sda4 initially ntfs, and then you formatted it with linux without re-creating the partition? [19:56] Because now it's "microsoft basic data" and "ext4"... [19:57] https://irc-attachments.kde.org/e1e52bd1/file_61409.jpg [19:58] * arraybolt3 throws up my hands [19:58] Something is very wrong with your partition table... [19:58] Is this an EFI system? [19:58] I'm starting to think maybe it's not. [19:59] What does "ls /sys/firmware/efi" show? [20:00] config_table efivars esrt fw_platform_size fw_vendor runtime runtime-map systab vars [20:01] This is on an originally Microsoft format 2 TB HDD btw [20:01] ...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. [20:02] 💀 [20:03] Shall I reboot? [20:03] And the purpose is to back it up, or revive it? [20:03] I have no clue. [20:03] I would definitely change the wrong partition type of sda4 [20:03] Shall I reboot after updating grub? [20:03] I don't think that would work. [20:03] So, mount sda4? [20:04] You're *in* sda4. [20:04] I mean... I guess you can try to reboot and hope it works. [20:05] Do you have a live usb stick to revive it if it doesn't boot? [20:05] I do not, but I do have home files backed up on the shared partition [20:06] If you have a usb stick, make it a live one before you reboot :D [20:06] +1 [20:06] (or if it boots windows, ok you can make it from windows later) [20:07] Yeah, I have Windows on the main drive and a shared backup and linux in the external [20:07] I'm rebooting [20:07] Good luck! [20:09] No change [20:09] I will purge and reinstall grub2 [20:10] Are you still on that 5.19 kernel? [20:10] I somehow am [20:10] paculino, would you like to post a small summary of the problem? You removed packages and now the system only boots to emergency? [20:15] 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] And all this is one drive? Because you also mentioned an external linux drive [20:17] That is the drive I am using. [20:17] Also, is that stock kubuntu 22.10 or something else? [20:17] External has four partitions (three for linux and one for backuo), and internal is just windows. [20:18] 22.04 with plasma from 22.10 [20:18] And how did you get kernel 5.19? [20:18] 22.04 has 5.15... [20:19] Muon or discover said I could update kernel to the latest compatible and I did [20:19] That was weeks ago [20:19] alkisg: That sounds to me like they're using the HWE kernel. [20:20] 22.04 *might* have 5.19 available now that 22.10 has been released. [20:20] It was 5.19-many digits [20:20] I guess something strange goes on there, but anyway, [20:20] 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? [20:20] External; internal is windows alone [20:21] And you have 2 ntfs partitions and one big fat partition for linux? [20:21] I can't seem to purge grub2 [20:21] And why didn't `sudo lsblk --fs` show your internal drive? It only showed one drive [20:21] alkisg: I think they have some small partition at the start that may be Windows' doing, then NTFS, then EFI, then ext4 for Linux. [20:22] The fat32 is just for boot [20:22] I do not see two disks in the screenshots. I see one disk. [20:22] Windows did the small partition in order to store letter names [20:22] My external drive cannot recognize the windows one in order to ensure no corruption of the internal drive [20:23] How do you achieve that? [20:23] Are you blacklisting some module? [20:24] I have no clue how I did it [20:24] So you have two EFI partitions, one on each disk? [20:24] Internal disk is all windows without any efi [20:25] What would be the correct way to reinstall grub2? [20:25] That doesn't sound right at all :) [20:25] But anyway, can we see the contents of your partitions? [20:25] Please run: [20:25] mount /dev/sda1 /mnt; ls /mnt [20:25] umount /mnt [20:26] mount /dev/sda2 /mnt; ls /mnt; umount /mnt [20:26] mount /dev/sda3 /mnt; ls /mnt; umount /mnt [20:26] And send a screenshot [20:26] Reinstalling grub blindly won't help if you haven't first found out what you want to put and where [20:30] SDA2 is just backups of photos, ebooks, documents, and the package.deb : https://irc-attachments.kde.org/82f1c9b3/file_61411.jpg [20:30] It won't fit on the screen [20:31] You're lacking the nls module to mount the efi partition, so you won't be able to write to it [20:32] (because you're booting with 5.19 and it doesn't exist in /lib/modules) [20:32] Is that fixable? [20:32] So even grub-install won't be able to write there. Anyway, do you have networking? [20:33] I am connected to internet and can access repos [20:33] OK, can you show us your grub.cfg? cat /boot/grub/grub.cfg | nc termbin.com 9999 [20:35] Temporary failure in name resolution [20:35] I can copy grub.cfg to the shared partition [20:35] No, let's fix dns [20:36] rm /etc/resolv.conf; echo nameserver 8.8.8.8 > /etc/resolv.conf [20:36] Then retry the cat ... | nc command [20:37] Same issue [20:37] Does `ping 8.8.8.8` work? === fusionnewbie1181 is now known as fusion1181 [20:38] Unreachable [20:39] Then you don't have networking [20:39] "I can copy grub.cfg to the shared partition" ==> and then how would you put it to the internet? By rebooting to windows? [20:39] Yes [20:39] Are you using a VM now, or bare metal? [20:39] No vm [20:40] OK, let's get you some networking, you'll need it [20:40] touch /test [20:40] I have wsl and I have virtualbox, but neither will be useful now [20:40] Does that work? [20:40] (i.e. is your root mounted rw?) [20:40] No errors [20:40] OK, now: ip a [20:41] What's the name of your ethernet, e.g. enp1s0? [20:42] https://irc-attachments.kde.org/dea63b85/file_61412.jpg [20:42] Next: /usr/lib/klibc/bin/ipconfig enp1s0 [20:42] And: ping 8.8.8.8 [20:43] Does it ping now? [20:44] It is loading [20:45] It's replying? OK then show us your grub.cfg now, with the nc | cat command [20:45] cat /boot/grub/grub.cfg | nc termbin.com 9999 [20:46] It has not returned/continued to show root@ubuntu:~# [20:47] The ping command? You need to press Ctrl+C to stop it [20:48] Temporary failure again [20:48] cat /etc/resolv.conf [20:49] does it show: nameserver 8.8.8.8 [20:49] Command not found [20:49] cat /etc/resolv.conf [20:49] The cat command is there, you mistyped something [20:50] Right [20:50] It returns correctly [20:50] 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] Did you see something like this? 64 bytes from 8.8.8.8: icmp_seq=3 ttl=115 time=38.8 ms [20:51] No, just the IP config [20:51] And is your ethernet connected to a router? [20:52] I'm using wifi [20:52] There's no wifi driver in the screenshot [20:52] It's probably missing from your 5.19 kernel (without the /lib/modules dir) [20:52] You'll need a live usb, go to windows and create one [20:53] I'm sorry; I have no USB drive, but I can borrow a live USB next week. [20:54] I'm sorry; I have no USB stick, but I can borrow a live USB next week. [20:54] 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] Ah one last thing, [20:54] type this and send us a photo: [20:54] grep vmlinuz /boot/grub/grub.cfg [20:56] Thank you for all the help : https://irc-attachments.kde.org/9ee77b55/file_61414.jpg [20:57] And this: cat /proc/cmdline [20:57] (photo again) [20:59] 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] You cut the screenshot too much, the kernel version doesn't show up [21:00] type this as well: uname -a [21:00] It doesn't show the kernel version [21:01] And uname -r says 5.19? [21:02] https://irc-attachments.kde.org/3daee874/file_61416.jpg [21:02] OK, now reboot, and when you see the grub menu, press the down arrow to prevent it from booting [21:03] I never see the grub menu [21:03] Send us a screenshot from there [21:03] Even if you click esc many times? [21:03] Or even if you hold down shift? [21:03] Escape did not work since this issue came up, but I have not tried since installing the linux-image again [21:05] 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] You can mount the efi partition from there, and change grub.cfg to point to ubuntu instead of popos [21:05] Esc failed, but this time emergency mod started with the journal (all I can see is green OK) [21:06] If `uname -r` says 5.19, there's nothing you can do, you don't have the modules [21:06] So copy grub.cfg to the shared partition and go to windows [21:15] A storm just arrived; power/internet may go out, but I am working on retrieving grub [21:17] 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] Then it would load your ext4 /boot/grub/grub.cfg, and it will load the 5.15 kernel [21:17] Okay, thank you so much! [21:17] 👍️