| === Lord_of_Life_ is now known as Lord_of_Life | ||
| carlos | carlos23123 | 02:19 |
|---|---|---|
| === marce_ is now known as marce_45 | ||
| === TomTom_ is now known as TomTom | ||
| === ferenc_ is now known as ferenc | ||
| pickanick | In the KUbuntu 22.04.3 installer, using manual partitioning, if there is already a partition of type linuxswap on the drive, do I need to explicitly inform the installer to use it? | 10:08 |
| pickanick | Oh its easy to do, nvm | 10:14 |
| pickanick | The installer for "Boot Loader" asks which device to use. The initial setting is the entire drive. Is that the right answer if there is already an EFI partition? Or should I choose the EFI partition? What's the difference? | 10:17 |
| pickanick | the Installation Guide for 22.04 is still unpublished, according to https://help.ubuntu.com/ | 10:20 |
| pickanick | Hi I notice on one Kubuntu system upgraded to Ubuntu 22.04.3 LTS I do not have a Kubuntu Secure Boot Signing Key, while on a freshly installed Kubuntu, I do. | 12:45 |
| pickanick | what's it used to sign? Why might it be missing on the first computer and should I try to get it there? | 12:47 |
| BluesKaj | Hi all | 12:53 |
| === warmana1 is now known as warmana | ||
| Guest61 | Hi, I am running Kubuntu 23.04 and want to upgrade to 23.10, is that possible? sudo do-release-upgrade reports "no new release found" | 13:42 |
| nescius | yes, but it always failed for me and I had to fix a lot of stuff, I'd suggest to install anew | 13:49 |
| nescius | ..feel free to test it and refer back! | 13:50 |
| nescius | Guest61: ⬆ | 13:50 |
| Guest61 | How do I upgrade then please? | 13:52 |
| Guest61 | These instructions do not work https://help.ubuntu.com/community/ManticUpgrades/Kubuntu | 13:52 |
| nescius | sudo do-release-upgrade -m desktop should work, and if not, it tells you why it failed. | 14:05 |
| === jj5_ is now known as jj5 | ||
| pickanick | Does Kubuntu have an interface for installing third-party drivers? Like nvidia? | 15:38 |
| pickanick | "Installing Restricted Drivers" -- there are instructions for GNOME | 15:39 |
| tomreyn | Section "4.7.1 Drivers" of the Kubuntu manual refers to a "Driver Manager" (but i'm not sure how to access it, maybe you can search for it on a menu?) | 15:41 |
| pickanick | Yes it does not appear to exist on my system as "Driver Manager" | 16:11 |
| pickanick | Does anyone here have a "Driver Manager" in Kubuntu 22.04 ? (I'm on 22.04.3) | 16:13 |
| pickanick | tomreyn I have downloaded the 22.04.2 manual and there is no section 4.7 | 16:15 |
| tomreyn | pickanick: oh right, i was looking at 20.04's | 16:17 |
| tomreyn | pickanick: apparently this paragraph moved to section 3.2.7 on the 22.04 manual | 16:19 |
| pickanick | I do see a greyed out "Driver Manager" tab in System Settings. On two different computers" | 16:20 |
| tomreyn | the manual suggests it is part of the "discover" application on 22.04 | 16:21 |
| user|56 | When would it be possible to upgrade to 23.10? | 16:26 |
| pickanick | Unfortunately (1) discover no longer runs on the newly installed laptop. On the command line plasma-discover just returns with return value 0 (via echo $? ) | 16:31 |
| pickanick | and (2) Discover on another machine I can find firmware updates lvfs and vendor-directory, but I do not see drivers | 16:32 |
| tomreyn | does the other machine have hardware installed which proprietary drivers are available for? | 16:40 |
| pickanick | not that I am aware | 16:41 |
| tomreyn | well then it has nothing to show there, that's fine | 16:41 |
| === jp is now known as jp__ | ||
| === jp__ is now known as jp_ | ||
| tomreyn | i wrote this in #ubuntu after you stated that discover does not run: | 16:42 |
| tomreyn | <tomreyn> pickanick: does sudo apt update && sudo apt upgrade && sudo apt dist-upgrade run without errors or warnings on a terminal emulator, though? | 16:42 |
| === jp_ is now known as jp | ||
| === jp is now known as jp__ | ||
| pickanick | hmm the first two run, I have not tried dist-upgrade | 16:42 |
| tomreyn | do they run without warnings or errors, though? | 16:42 |
| pickanick | so I've installed ubuntu-gnome-desktop, and I'm being required to choose between gdm3 and sddm, which do I choose and how do I change back to KDE later? | 16:42 |
| pickanick | yes they run normally. | 16:43 |
| pickanick | Oh no wait on the first apt upgrade there were many missing firmware warnings as I mentioned initially, but not since then. | 16:43 |
| tomreyn | i would not recommend installing kubuntu and gnome on the same system, but YMMV. sddm is the default login manager for kdm, gdm3 that of gnome. theoretically, they should both work for either desktop, but i don't know this for sure. | 16:44 |
| pickanick | I've resigned myself to reinstalling once I get a working system | 16:45 |
| tomreyn | if there were missing firmware warnings when you ran apt upgrade this suggests you got a kernel upgrade since. but i'm just guessing, looking at the actual output would be much better. | 16:46 |
| pickanick | tomreyn: output of apt upgrade at bpa.st/COXA | 16:54 |
| tomreyn | oh you were missing all those upgrades | 16:57 |
| tomreyn | do apt dist-upgrade, too, then | 16:59 |
| tomreyn | then a reboot and look for proprietary drivers again | 17:00 |
| pickanick | tomreyn: apt dist-upgrade reports nothing to do. Re your Q: yes, sudo apt update && sudo apt upgrade && sudo apt dist-upgrade runs without errors or warnings on a terminal emulator. | 17:00 |
| tomreyn | nice | 17:00 |
| pickanick | requested reboot. Video switched to text mode displaying what looks like dmesg from 2. to 7. and blinking cursor. Cntl-Alt-F2+ give blank screen | 17:02 |
| pickanick | Cntl-Alt-F2+ give blank screen with blinking cursor upper left. | 17:03 |
| pickanick | ah sysreq H gives help. | 17:04 |
| pickanick | but that seem to be the only option that gives a response | 17:09 |
| tomreyn | 's' and 'u' should provide a written response, 'b' would just reboot | 17:10 |
| pickanick | some buttons give the same result as 'h' | 17:13 |
| pickanick | Hard Powered off. Booted into GNOME. Software and Updates "additional drivers" reports "No additional drivers available" and "No proprietary drivers are in use" | 17:14 |
| tomreyn | did you upgrade this dell precision from bios version 1.22.1 to the latest available, version 1.26.0 ? | 17:15 |
| tomreyn | journalctl -b | grep DMI: would tell | 17:15 |
| tomreyn | which apt repositories are enabled? apt policy | nc termbin.com 9999 | 17:16 |
| pickanick | I was offered 1.23 by fwupdmgr | 17:16 |
| pickanick | Where do you see 1.26 available? | 17:17 |
| tomreyn | https://www.dell.com/support/home/en-uk/product-support/product/precision-17-7760-laptop/drivers | 17:17 |
| tomreyn | or this for a more direct link https://www.dell.com/support/home/en-uk/drivers/driversdetails?driverid=xtkgx&oscode=wt64a&productcode=precision-17-7760-laptop | 17:18 |
| tomreyn | Refer to the "Installation instructions" below, section "Updating the BIOS from BIOS Boot Menu (independent of operating system)" | 17:19 |
| pickanick | Hot off the presses. This didn't exist yesterday when I looked. | 17:21 |
| pickanick | as requested termbin.com/4o2f | 17:23 |
| tomreyn | i don't know whether the bios upgrade will help you, after all nouveau did detect an installed NVIDIA GA104 (b74000a1) dGPU previously. so apprently you just need to enable the system to install nvidia drivers | 17:24 |
| tomreyn | you only have security update repositories configured | 17:24 |
| tomreyn | not the base repositories | 17:25 |
| tomreyn | you can edit /etc/apt/sources.list to fix this, or use "software-properties-qt" if that's still available, or discover, if this starts by now. | 17:26 |
| pickanick | I'm not aware that I changed anything from the defaults | 17:26 |
| tomreyn | can you share sources.list ? maybe i'm misinterpreting the output i saw | 17:27 |
| pickanick | termbin.com/a15o | 17:29 |
| tomreyn | hmm this actually looks fine, sorry | 17:30 |
| tomreyn | well, i guess you can just try to install the nvidia-driver release which nvidia recommends for your hardware and reboot and see what you get | 17:31 |
| tomreyn | !nvidia | 17:33 |
| ubottu | Drivers for Nvidia graphics cards: (A) No gaming/CAD/CUDA needed or legacy hardware? Use "nouveau" (open source, lacks many features). (B) Otherwise, "nvidia" (proprietary driver, fully featured). Install using "ubuntu-drivers" CLI or apt - not from nvidia.com. Driver series, hardware support (release notes): https://www.nvidia.com/en-us/drivers/unix/ - Latest drivers !PPA: https://pad.lv/ppa/graphics-drivers | 17:33 |
| pickanick | When does one use PPA vs the existing repos I already have? | 17:35 |
| tomreyn | only if you have very recent hardware and the default ones don't work | 17:36 |
| pickanick | looking at NVIDIA URL ... So do I just take the 535 "Latest Production Branch" Version? | 17:37 |
| tomreyn | according to nvidia.com, driver series 535 or 530 seem to be suitable for GeForce RTX 3070 Ti | 17:37 |
| tomreyn | you would check "supported products" for each, too | 17:38 |
| tomreyn | they also have a search for recommended drivers per model somewhere. | 17:38 |
| pickanick | Yes, their tool says 535.113.01 | 17:40 |
| tomreyn | so try installing nvidia-driver-535 or nvidia-driver-535-open | 17:42 |
| pickanick | apt info descriptions seem identical for the two, any idea between them? | 17:45 |
| pickanick | "open kernel" ? | 17:49 |
| pickanick | I'll try the nvidia-driver-535 | 17:50 |
| tomreyn | nvidia-driver-535 is the proprietary one, nvidia-driver-535-open is the liberally licensed one where nvidia moved most driver code into the (proprietary) firmware and just left the driver initialization and basic functionality in the kernel module code. | 17:55 |
| tomreyn | there seem to be quality issues with some of the -open variants, still from what i read, but i don't care much about nvidia, so this may just be hearsay. | 17:56 |
| pickanick | The intended advantage of -open is what ? can skip the dkms patching? | 17:57 |
| tomreyn | possibly, at some point. also nvidia would be able to use kernel ABIs as they're intended to be used instead of constantly work around them to overcome their restrictions against proprietary drivers. | 17:59 |
| tomreyn | i.e. users might get a better user experience at some point in the future | 18:00 |
| tomreyn | because things might start to 'just' work as they do for other open grphics drivers | 18:00 |
| pickanick | if a MOK key has been queued up for the reboot is it bad to update the BIOS on the same reboot? | 18:06 |
| tomreyn | i would not recommend it | 18:07 |
| pickanick | yes I decided that the BIOS update might result in another reboot and then the MOK enrollment might not be available | 18:10 |
| cbreak_ | I wouldn't use anything other than drivers directly from nvidia in production | 18:17 |
| cbreak_ | even the ones packaged with ubuntu can cause problems sometimes | 18:17 |
| === cbreak_ is now known as cbreak | ||
| tomreyn | or the other way around | 18:18 |
| pickanick | hmm now ubuntu-drivers devices reports the NVIDIA device | 18:18 |
| tomreyn | due to the bios upgrade? | 18:18 |
| pickanick | no postponed bios update to next reboot. | 18:19 |
| tomreyn | or the mok enrollment? | 18:19 |
| pickanick | Now I have *two* Kubuntu & an ubuntu SecBoot Module Signature Keys & a Canonical Master Sign. Authority | 18:20 |
| pickanick | The recent MOK enrollment added the second Kubuntu key | 18:21 |
| pickanick | odd. If something had gone wrong with the first enrollment, it seems there would not be the other keys listed | 18:22 |
| tomreyn | a couple certificates had to be replaced somewhat recetnly because secure boot turned out not to be secure boot | 18:24 |
| tomreyn | it might be related to that, but i'm speculating | 18:24 |
| pickanick | how to (1) check whether the driver is working as expected and (2) activate hibernation? My swap space is the size of RAM. | 18:26 |
| pickanick | oh dmesg says hibernation is restricted, maybe because of Secure Boot and the hibernation image not being signed | 18:27 |
| === vcxza is now known as faLUKE | ||
| tomreyn | you should notice the difference if the driver works. you can also check xorgs logs again as you did initially. | 18:29 |
| pickanick | dmesg does not have obvious crash but it does have ~ 13X "nvidia-drm ERROR .... failed to grab modeset ownership" | 18:30 |
| tomreyn | did you install ubuntu's nvidia driver? | 18:31 |
| tomreyn | that should have disabled nouveau and thus allow the proprietary driver to handle mode setting | 18:33 |
| pickanick | nvidia-driver-535 | 18:33 |
| pickanick | installed before reboot | 18:34 |
| tomreyn | maybe that's another secureboot restriction, not sure. does it seem to work, though? do youget accelerated graphics? | 18:34 |
| pickanick | How to test it? | 18:36 |
| tomreyn | run some game, install mesa-utils and run glxinfo -B | 18:38 |
| pickanick | reboot now works. Suspend works. glxinfo does not seem to mention NVIDIA, but the intel UHD graphics | 18:51 |
| pickanick | The NVIDIA settings app recognizes the NVIDIA device. | 18:53 |
| cbreak | do you have nvidia-smi? | 18:55 |
| cbreak | if so, run it | 18:55 |
| cbreak | and if you really care, get nvtop :) | 18:55 |
| pickanick | How to switch back to the other desktop greeter? (for KDE) | 19:00 |
| pickanick | Installed nvtop. I could not find nvidia-smi, so installed gpustat | 19:03 |
| pickanick | or can I just uninstall ubuntu-gnome-desktop ? | 19:08 |
| pickanick | How can I switch back to the KDE desktop greeter, or is it best to uninstall ubuntu-gnome-desktop ? | 19:08 |
| cbreak | pickanick: you want to use SDDM? | 19:12 |
| pickanick | I suppose so | 19:13 |
| cbreak | I thought that was done with update-alternatives somehow, but it seems x-session-manager is something else | 19:15 |
| cbreak | sudo dpkg-reconfigure sddm apparently | 19:16 |
| pickanick | cbreak, thanks! how might I find that solution the next time when I've forgotten in? | 19:19 |
| cbreak | I duck-go-ed for "ubuntu change sddm" :) | 19:20 |
| pickanick | Is there a way to have the login screen let user choose GNOME or KDE? | 19:23 |
| pickanick | Fedora had this at some point | 19:23 |
| pickanick | oh sddm has it on the lower left! | 19:26 |
| cbreak | yes. | 19:27 |
| cbreak | the one from gnome does too somewhere | 19:27 |
| cbreak | you only see it if you have multiple DEs installed | 19:27 |
| cbreak | (you can also switch between the x11 and the wayland one, but I've not had much success with wayland) | 19:28 |
| cbreak | looks like 2310 isn't in do-release-upgrade yet :( | 19:30 |
| pickanick | Thank you cbreak for this solution! | 19:32 |
| pickanick | Thank you to tomreyn for your extensive help! | 19:33 |
| pickanick | So it turns out that in KDE Discover the drivers configuration is found via the "Software Sources" button. | 19:35 |
| cbreak | if you want a gui, there's `software-properties-kde` (run it via sudo) | 19:42 |
| cbreak | on the CLI, you can use ubuntu-drivers to select different ones. But as I mentioned before, if this is anything professional, I'd recommend getting the drivers from nvidia, via the cuda package | 19:43 |
| cbreak | I install that on all my servers | 19:44 |
| cbreak | much less problematic than the ubuntu one, since it doesn't break every time it decides to update | 19:44 |
| cbreak | (but doesn't do secure boot... so... your pick :/ ) | 19:44 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!