/srv/irclogs.ubuntu.com/2022/11/11/#kubuntu.txt

user__hello12:06
BluesKajHi all12:57
user|72good 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:39
oerheksuser|72, i remember that notebook, no sound is an linux wide issue14:44
oerhekssof-firmware issue; https://github.com/thesofproject/linux/issues/3350 .. no fix14:48
-ubottu:#kubuntu- Issue 3350 in thesofproject/linux "[BUG] Huawei Matebook 14s headphone / speaker problem (CX8070 codec)" [Open]14:48
IrcsomeBot<PJtunes> Hello house15:36
IrcsomeBot<PJtunes> I connected an airpod to my laptop, it was well connected but there was no sound coming out from the airpod15:36
heathcliffGood evening! Does anyone else have issues with ipv6 on kubuntu 22.10?16:50
heathcliffI 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)16:53
IrcsomeBot<paculino> 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
IrcsomeBot<paculino> 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:31
IrcsomeBot<paculino> 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.jpg19:34
arraybolt3@paculino: That shouldn't have rendered your system unbootable... what *else* did you do?19:34
arraybolt3The linux-generic package is a metapackage, removing it shouldn't have caused damage like that.19:35
arraybolt3Did you also do an autoremove?19:35
arraybolt3(DO NOT do an autoremove, btw.)19:35
IrcsomeBot<paculino> I autoremoved before, and sddm went away, but I fixed that.19:36
IrcsomeBot<paculino> 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 into19:36
IrcsomeBot<paculino> Uname -r returns the deleted kernel19:36
arraybolt3...?!19:36
arraybolt3OK that's seriously weird.19:36
arraybolt3Oh wait I get it.19:36
arraybolt3You removed only the modules, modules-extra, and headers?19:37
IrcsomeBot<paculino> 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-generic19:38
arraybolt3If 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
IrcsomeBot<paculino> I ran the dpkg -i *.deb ; apt-get install -f and here is the ending error from that19: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.19:38
IrcsomeBot<paculino> https://irc-attachments.kde.org/b00f07c3/file_61403.jpg19:40
arraybolt3Oh shoot. That's... I dunno how to fix that...19:40
arraybolt3@paculino: Hold on, I see something.19:41
IrcsomeBot<paculino> 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 errors19: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.)19:42
IrcsomeBot<paculino> 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.jpg19:44
arraybolt3...ok that's weird.19:45
IrcsomeBot<paculino> https://irc-attachments.kde.org/d563e084/file_61406.jpg19:45
arraybolt3Are you able to boot normally if you can get into GRUB and boot one of the older, properly installed kernels?19:45
IrcsomeBot<paculino> I cannot access grub when booting, at least not before the dpkg install19:46
arraybolt3what 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.)19:46
IrcsomeBot<paculino> I thought it was ext4 when I installed kubuntu, and I thought it said it was yesterday, but it does not today.19:48
IrcsomeBot<paculino> I hope no one went and reformatted my drive (this should affect all partitions though, right?)19:48
arraybolt3No, it would be possible to reformat just a partition...19:48
IrcsomeBot<paculino> Oh, apt-get now works and can access repos19:48
arraybolt3OK so let's try something new. Something is very awry, let's try to diagnose it.19:49
arraybolt3(Oh that's good.)19:49
IrcsomeBot<paculino> I am running upgrade now19:49
IrcsomeBot<paculino> Unless that's a bad idea?19:49
arraybolt3The fact that you're at a shell at all means that your OS should still be there.19:49
arraybolt3The upgrade should be fine.19:49
IrcsomeBot<paculino> Initramfs is updating again19:50
arraybolt3OK, don't reboot yet.19:50
arraybolt3When it finishes, can you tell me what "ls /boot" shows?19:50
IrcsomeBot<paculino> Yes, thank you for being so helpful19:50
arraybolt3Glad 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 :P19:51
IrcsomeBot<paculino> https://irc-attachments.kde.org/3855a6ee/file_61407.jpg19:52
alkisgpaculino, what's the output of `sudo lsblk --fs` ?19:52
arraybolt3OK, 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...)19:53
IrcsomeBot<paculino> https://irc-attachments.kde.org/b32c2c3b/file_61408.jpg19:54
IrcsomeBot<paculino> /boot/efi appears empty19:54
arraybolt3Probably isn't mounted, then.19:55
arraybolt3"mount /dev/sda3 /boot/efi && ls /boot/efi"19:55
IrcsomeBot<paculino> Should I now unmount the shared drive I put the package .debs on?19:55
arraybolt3I don't think you need to but it probably won't hurt.19:56
alkisgpaculino, was sda4 initially ntfs, and then you formatted it with linux without re-creating the partition?19:56
alkisgBecause now it's "microsoft basic data" and "ext4"...19:56
IrcsomeBot<paculino> https://irc-attachments.kde.org/e1e52bd1/file_61409.jpg19:57
* arraybolt3 throws up my hands19:58
arraybolt3Something is very wrong with your partition table...19:58
arraybolt3Is this an EFI system?19:58
arraybolt3I'm starting to think maybe it's not.19:58
arraybolt3What does "ls /sys/firmware/efi" show?19:59
IrcsomeBot<paculino> config_table efivars esrt fw_platform_size fw_vendor runtime runtime-map systab vars20:00
IrcsomeBot<paculino> This is on an originally Microsoft format 2 TB HDD btw20: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.20:01
IrcsomeBot<paculino> 💀20:02
IrcsomeBot<paculino> Shall I reboot?20:03
alkisgAnd the purpose is to back it up, or revive it?20:03
arraybolt3I have no clue.20:03
alkisgI would definitely change the wrong partition type of sda420:03
IrcsomeBot<paculino> Shall I reboot after updating grub?20:03
arraybolt3I don't think that would work.20:03
IrcsomeBot<paculino> So, mount sda4?20:03
arraybolt3You're *in* sda4.20:04
arraybolt3I mean... I guess you can try to reboot and hope it works.20:04
alkisgDo you have a live usb stick to revive it if it doesn't boot?20:05
IrcsomeBot<paculino> I do not, but I do have home files backed up on the shared partition20:05
alkisgIf you have a usb stick, make it a live one before you reboot :D20:06
arraybolt3+120:06
alkisg(or if it boots windows, ok you can make it from windows later)20:06
IrcsomeBot<paculino> Yeah, I have Windows on the main drive and a shared backup and linux in the external20:07
IrcsomeBot<paculino> I'm rebooting20:07
arraybolt3Good luck!20:07
IrcsomeBot<paculino> No change20:09
IrcsomeBot<paculino> I will purge and reinstall grub220:09
arraybolt3Are you still on that 5.19 kernel?20:10
IrcsomeBot<paculino> I somehow am20:10
alkisgpaculino, would you like to post a small summary of the problem? You removed packages and now the system only boots to emergency?20:10
IrcsomeBot<paculino> 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 fo20:15
alkisgAnd all this is one drive? Because you also mentioned an external linux drive20:16
IrcsomeBot<paculino> That is the drive I am using.20:17
alkisgAlso, is that stock kubuntu 22.10 or something else?20:17
IrcsomeBot<paculino> External has four partitions (three for linux and one for backuo), and internal is just windows.20:17
IrcsomeBot<paculino> 22.04 with plasma from 22.1020:18
alkisgAnd how did you get kernel 5.19?20:18
alkisg22.04 has 5.15...20:18
IrcsomeBot<paculino> Muon or discover said I could update kernel to the latest compatible and I did20:19
IrcsomeBot<paculino> That was weeks ago20:19
arraybolt3alkisg: That sounds to me like they're using the HWE kernel.20:19
arraybolt322.04 *might* have 5.19 available now that 22.10 has been released.20:20
IrcsomeBot<paculino> It was 5.19-many digits20:20
alkisgI guess something strange goes on there, but anyway,20:20
alkisgso 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
IrcsomeBot<paculino> External; internal is windows alone20:20
alkisgAnd you have 2 ntfs partitions and one big fat partition for linux?20:21
IrcsomeBot<paculino> I can't seem to purge grub220:21
alkisgAnd why didn't `sudo lsblk --fs` show your internal drive? It only showed one drive20:21
arraybolt3alkisg: I think they have some small partition at the start that may be Windows' doing, then NTFS, then EFI, then ext4 for Linux.20:21
IrcsomeBot<paculino> The fat32 is just for boot20:22
alkisgI do not see two disks in the screenshots. I see one disk.20:22
IrcsomeBot<paculino> Windows did the small partition in order to store letter names20:22
IrcsomeBot<paculino> My external drive cannot recognize the windows one in order to ensure no corruption of the internal drive20:22
alkisgHow do you achieve that?20:23
alkisgAre you blacklisting some module?20:23
IrcsomeBot<paculino> I have no clue how I did it20:24
alkisgSo you have two EFI partitions, one on each disk?20:24
IrcsomeBot<paculino> Internal disk is all windows without any efi20:24
IrcsomeBot<paculino> What would be the correct way to reinstall grub2?20:25
alkisgThat doesn't sound right at all :)20:25
alkisgBut anyway, can we see the contents of your partitions?20:25
alkisgPlease run:20:25
alkisgmount /dev/sda1 /mnt; ls /mnt20:25
alkisgumount /mnt20:25
alkisgmount /dev/sda2 /mnt; ls /mnt; umount /mnt20:26
alkisgmount /dev/sda3 /mnt; ls /mnt; umount /mnt20:26
alkisgAnd send a screenshot20:26
alkisgReinstalling grub blindly won't help if you haven't first found out what you want to put and where20:26
IrcsomeBot<paculino> SDA2 is just backups of photos, ebooks, documents, and the package.deb : https://irc-attachments.kde.org/82f1c9b3/file_61411.jpg20:30
IrcsomeBot<paculino> It won't fit on the screen20:30
alkisgYou're lacking the nls module to mount the efi partition, so you won't be able to write to it20:31
alkisg(because you're booting with 5.19 and it doesn't exist in /lib/modules)20:32
IrcsomeBot<paculino> Is that fixable?20:32
alkisgSo even grub-install won't be able to write there. Anyway, do you have networking?20:32
IrcsomeBot<paculino> I am connected to internet and can access repos20:33
alkisgOK, can you show us your grub.cfg? cat /boot/grub/grub.cfg | nc termbin.com 999920:33
IrcsomeBot<paculino> Temporary failure in name resolution20:35
IrcsomeBot<paculino> I can copy grub.cfg to the shared partition20:35
alkisgNo, let's fix dns20:35
alkisgrm /etc/resolv.conf; echo nameserver 8.8.8.8 > /etc/resolv.conf20:36
alkisgThen retry the cat ... | nc command20:36
IrcsomeBot<paculino> Same issue20:37
alkisgDoes `ping 8.8.8.8` work?20:37
=== fusionnewbie1181 is now known as fusion1181
IrcsomeBot<paculino> Unreachable20:38
alkisgThen you don't have networking20: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?20:39
IrcsomeBot<paculino> Yes20:39
alkisgAre you using a VM now, or bare metal?20:39
IrcsomeBot<paculino> No vm20:39
alkisgOK, let's get you some networking, you'll need it20:40
alkisgtouch /test20:40
IrcsomeBot<paculino> I have wsl and I have virtualbox, but neither will be useful now20:40
alkisgDoes that work?20:40
alkisg(i.e. is your root mounted rw?)20:40
IrcsomeBot<paculino> No errors20:40
alkisgOK, now: ip a20:40
alkisgWhat's the name of your ethernet, e.g. enp1s0?20:41
IrcsomeBot<paculino> https://irc-attachments.kde.org/dea63b85/file_61412.jpg20:42
alkisgNext: /usr/lib/klibc/bin/ipconfig enp1s020:42
alkisgAnd: ping 8.8.8.820:42
alkisgDoes it ping now?20:43
IrcsomeBot<paculino> It is loading20:44
alkisgIt's replying? OK then show us your grub.cfg now, with the nc | cat command20:45
alkisgcat /boot/grub/grub.cfg | nc termbin.com 999920:45
IrcsomeBot<paculino> It has not returned/continued to show root@ubuntu:~#20:46
alkisgThe ping command? You need to press Ctrl+C to stop it20:47
IrcsomeBot<paculino> Temporary failure again20:48
alkisgcat /etc/resolv.conf20:48
alkisgdoes it show: nameserver 8.8.8.820:49
IrcsomeBot<paculino> Command not found20:49
alkisgcat /etc/resolv.conf20:49
alkisgThe cat command is there, you mistyped something20:49
IrcsomeBot<paculino> Right20:50
IrcsomeBot<paculino> It returns correctly20:50
alkisgWait 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
alkisgDid you see something like this? 64 bytes from 8.8.8.8: icmp_seq=3 ttl=115 time=38.8 ms20:50
IrcsomeBot<paculino> No, just the IP config20:51
alkisgAnd is your ethernet connected to a router?20:51
IrcsomeBot<paculino> I'm using wifi20:52
alkisgThere's no wifi driver in the screenshot20:52
alkisgIt's probably missing from your 5.19 kernel (without the /lib/modules dir)20:52
alkisgYou'll need a live usb, go to windows and create one20:52
IrcsomeBot<paculino> I'm sorry; I have no USB drive, but I can borrow a live USB next week.20:53
IrcsomeBot<paculino> I'm sorry; I have no USB stick, but I can borrow a live USB next week.20:54
alkisgOK. 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 usb20:54
alkisgAh one last thing,20:54
alkisgtype this and send us a photo:20:54
alkisggrep vmlinuz /boot/grub/grub.cfg20:54
IrcsomeBot<paculino> Thank you for all the help : https://irc-attachments.kde.org/9ee77b55/file_61414.jpg20:56
alkisgAnd this: cat /proc/cmdline20:57
alkisg(photo again)20:57
IrcsomeBot<paculino> And this may be the root problem. I installed pop-plymouth at one point : https://irc-attachments.kde.org/71b7e158/20221111_155809.jpg20:59
alkisgYou cut the screenshot too much, the kernel version doesn't show up21:00
alkisgtype this as well: uname -a21:00
IrcsomeBot<paculino> It doesn't show the kernel version21:00
alkisgAnd uname -r says 5.19?21:01
IrcsomeBot<paculino> https://irc-attachments.kde.org/3daee874/file_61416.jpg21:02
alkisgOK, now reboot, and when you see the grub menu, press the down arrow to prevent it from booting21:02
IrcsomeBot<paculino> I never see the grub menu21:03
alkisgSend us a screenshot from there21:03
alkisgEven if you click esc many times?21:03
alkisgOr even if you hold down shift?21:03
IrcsomeBot<paculino> Escape did not work since this issue came up, but I have not tried since installing the linux-image again21:03
alkisgCopy your grub.cfg to the shared partition, then reboot. See if you can make "Esc" or "Left shift" work, otherwise go to Windows21:05
alkisgYou can mount the efi partition from there, and change grub.cfg to point to ubuntu instead of popos21:05
IrcsomeBot<paculino> Esc failed, but this time emergency mod started with the journal (all I can see is green OK)21:05
alkisgIf `uname -r` says 5.19, there's nothing you can do, you don't have the modules21:06
alkisgSo copy grub.cfg to the shared partition and go to windows21:06
IrcsomeBot<paculino> A storm just arrived; power/internet may go out, but I am working on retrieving grub21:15
alkisgIt'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 uuid21:17
alkisgThen it would load your ext4 /boot/grub/grub.cfg, and it will load the 5.15 kernel21:17
IrcsomeBot<paculino> Okay, thank you so much!21:17
alkisg👍️21:17

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!