I didn't know this was a forum. I didn't expect a reply. Anyway I did figure that was why. Although I had another computer from the same era with a NVIDIA card, and it still gets driver updates in Windows using GeForce Experience. This one dual booting Linux and Windows however does not even get NVIDIA driver updates for Windows anymore either though.
This is an old computer. I'm installing various Linux distros on it to make sure their live installers can copy the GRUB .efi files to the correct partition on an external USB HDD, before I try the same sort of install with a more modern Intel laptop and my USB drive. I usually CSM boot, but most PCs don't have CSM/Legacy mode anymore, therefore I am having to use UEFI natively. There was a bug with Ubiquity. When selected to install /mount/EFI to a FAT32 partition on a SSD or HDD (such as my USB HDD) different to the main SSD on which Windows Boot Manager is installed - so you can dual boot without modifying the Windows EFI partition (avoid boot coups from either OS) - If you did this, Ubiquity without asking or telling you would automatically install GRUB to the EFI partition on the main drive's EFI partition, sharing it with Windows Boot Manager, and possibly overwriting the fallback /EFI/BOOT/bootx64.efi copy of BOOTMGR with Grub. This PC is old, and the CMOS battery is out of power, so if that file gets overwritten it wouldn't be possible to get back into Windows without changing the battery or restoring the fallback copy of BOOTMGR somehow. Not that it matters. But if the CMOS on any of my more modern laptops were to run out for some reason I would have to boot windows using the install USB. I was also concerned about the way native EFI would interact with the firmware and NVRAM, I thought it might do something stupid like cause all the variables to be cleared. I have another Lenovo laptop from the same era. Apparently people have found if you install a Linux distro on this in any way, the boot menu and novo button options are no longer there afterwards. So I want to make sure my older computers work ok in native EFI mode before running Linux that way on a more modern computer. Anyway that's another problem. Kubuntu 24.10 uses Calamares I believe which works fine. Not sure what 24.04 uses, is it Ubiquity or Subiquity? And does it still have that problem? I want to know before I use the live installer booted on my modern PCs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2089456 Title: no sound after installing nvidia 550 driver using synaptic Status in alsa-driver package in Ubuntu: Invalid Bug description: I am using Kubuntu 24.10. I had some problems installing the nvidia 550 driver. Additional drivers din't tell me I could install it so I looked in Synaptic and found the package. Since then I have haf no sound when using the hdmi output from py gra[hics card. Aside from that i also found I cannot change resolution. The resolutioon is stuck at 1920 x 1080 pixels. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.8.0-49.49-generic 6.8.12 Uname: Linux 6.8.0-49-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/seq: andrew 1370 F.... pipewire /dev/snd/controlC1: andrew 1372 F.... wireplumber /dev/snd/controlC0: andrew 1372 F.... wireplumber CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Nov 23 21:05:51 2024 InstallationDate: Installed on 2024-11-20 (3 days ago) InstallationMedia: Kubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827) MachineType: Hewlett-Packard 500-368na PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2014 dmi.bios.release: 4.6 dmi.bios.vendor: AMI dmi.bios.version: 80.16 dmi.board.name: 2AF7 dmi.board.vendor: Hewlett-Packard dmi.board.version: 1.04 dmi.chassis.asset.tag: CZC4260JJQ dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr80.16:bd05/12/2014:br4.6:svnHewlett-Packard:pn500-368na:pvr1.00:rvnHewlett-Packard:rn2AF7:rvr1.04:cvnHewlett-Packard:ct3:cvr:skuG9C73EA#ABU: dmi.product.family: 103C_53316J G=D dmi.product.name: 500-368na dmi.product.sku: G9C73EA#ABU dmi.product.version: 1.00 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2089456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
