Selecting Kernel Issues (stuck on 6.1.0-17)

[Keleth]

Hey there, I'm still pretty new to Linux Mint, especially LMDE 6 in general.
I had problems with nvidia on the 6.1.18 kernel and when I went to revert it, ended up using the 6.1.0-17-amd64 via one of the guides I found.
But I'm noticing some issues with flatpaks/nvidia drivers/NVENC encoders.
And noticing that some things aren't showing up in the update manager since I did it.

My question is, can you select kernels in LMDE 6 like you can in the main edition of Mint?

Or is there a reset configurations of the update manager so it'll pull proper supported by mint kernel packages?
Or is this a "Reinstall from a live USB drive" kind of deal?

Here's the system info I got from the System Info App:

Code: Select all

System:
  Kernel: 6.1.0-17-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 Desktop: Cinnamon v: 6.0.4
    tk: GTK v: 3.24.38 wm: muffin vt: 7 dm: LightDM v: 1.26.0 Distro: LMDE 6 Faye
    base: Debian 12.1 bookworm
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME X570-P v: Rev X.0x serial: <superuser required>
    UEFI: American Megatrends v: 5003 date: 10/07/2023
CPU:
  Info: 6-core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP smt: enabled arch: Zen 2 rev: 0 cache:
    L1: 384 KiB L2: 3 MiB L3: 32 MiB
  Speed (MHz): avg: 2449 high: 4189 min/max: 2200/4208 boost: enabled cores: 1: 2192 2: 2060
    3: 2200 4: 4049 5: 2074 6: 2033 7: 2189 8: 2064 9: 2196 10: 4189 11: 2094 12: 2059
    bogomips: 86245
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA TU116 [GeForce GTX 1660 Ti] vendor: Micro-Star MSI driver: nvidia v: 525.147.05
    arch: Turing pcie: speed: 8 GT/s lanes: 16 bus-ID: 08:00.0 chip-ID: 10de:2182 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa alternate: nv gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x1080 s-dpi: 101 s-size: 966x272mm (38.03x10.71")
    s-diag: 1004mm (39.51")
  Monitor-1: DP-1 pos: left res: 1920x1080 hz: 60 dpi: 102 size: 480x270mm (18.9x10.63")
    diag: 551mm (21.68") modes: N/A
  Monitor-2: DP-3 pos: primary,right res: 1920x1080 hz: 60 dpi: 102 size: 480x270mm (18.9x10.63")
    diag: 551mm (21.68") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 525.147.05 renderer: NVIDIA GeForce GTX 1660 Ti/PCIe/SSE2
    direct-render: Yes
Audio:
  Device-1: NVIDIA TU116 High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel
    v: kernel bus-ID: 1-2:6 chip-ID: 0d8c:0134 pcie: class-ID: 0300 speed: 8 GT/s lanes: 16
    bus-ID: 08:00.1 chip-ID: 10de:1aeb class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
    speed: 16 GT/s lanes: 16 bus-ID: 0a:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: C-Media USB PnP Audio Device type: USB driver: hid-generic,snd-usb-audio,usbhid
  API: ALSA v: k6.1.0-17-amd64 status: kernel-api
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK PRIME B450M-A
    driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 04:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: TP-Link UB500 Adapter type: USB driver: btusb v: 0.8 bus-ID: 3-1:2 chip-ID: 2357:0604
    class-ID: e001 serial: <filter>
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.1
    sub-v: 8a6b hci-v: 5.1 rev: 9a9
Drives:
  Local Storage: total: 3.64 TiB used: 769.74 GiB (20.7%)
  ID-1: /dev/nvme0n1 vendor: Sabrent model: Rocket 4.0 500GB size: 465.76 GiB speed: 63.2 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: RKT401.2 temp: 33.9 C scheme: GPT
  ID-2: /dev/sda vendor: Hitachi model: HUA721010KLA330 size: 931.51 GiB speed: 3.0 Gb/s
    type: N/A serial: <filter> rev: AB0A scheme: GPT
  ID-3: /dev/sdb vendor: Western Digital model: WD10EZEX-22MFCA0 size: 931.51 GiB speed: 6.0 Gb/s
    type: HDD rpm: 7200 serial: <filter> rev: 1A01 scheme: GPT
  ID-4: /dev/sdc vendor: Western Digital model: WD5000AAKX-75U6AA0 size: 465.76 GiB
    speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: 1H20 scheme: GPT
  ID-5: /dev/sdd vendor: Western Digital model: WD10EZEX-22BN5A0 size: 931.51 GiB speed: 6.0 Gb/s
    type: HDD rpm: 7200 serial: <filter> rev: 1A01 scheme: GPT
Partition:
  ID-1: / size: 907.47 GiB used: 119.48 GiB (13.2%) fs: ext4 dev: /dev/sdb3
  ID-2: /boot/efi size: 285.4 MiB used: 5.8 MiB (2.0%) fs: vfat dev: /dev/sdb1
Swap:
  ID-1: swap-1 type: partition size: 8.2 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdb2
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-2:6 info: C-Media USB PnP Audio Device type: Audio,HID
    driver: hid-generic,snd-usb-audio,usbhid interfaces: 3 rev: 1.1 speed: 12 Mb/s power: 100mA
    chip-ID: 0d8c:0134 class-ID: 0300
  Hub-2: 2-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 3-1:2 info: TP-Link UB500 Adapter type: Bluetooth driver: btusb interfaces: 2
    rev: 1.1 speed: 12 Mb/s power: 500mA chip-ID: 2357:0604 class-ID: e001 serial: <filter>
  Device-2: 3-2:3 info: DragonRise MAGIC-NS type: <vendor specific> driver: xpad interfaces: 1
    rev: 2.0 speed: 12 Mb/s power: 500mA chip-ID: 0079:18d3 class-ID: ff00 serial: <filter>
  Device-3: 3-6:4 info: ASUSTek AURA LED Controller type: HID driver: hid-generic,usbhid
    interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 16mA chip-ID: 0b05:18f3 class-ID: 0300
    serial: <filter>
  Hub-4: 4-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-5: 5-0:1 info: Hi-speed hub with single TT ports: 2 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-6: 6-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-7: 7-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 7-3:2 info: X-BOWS NATURE type: Keyboard,HID driver: hid-generic,usbhid interfaces: 2
    rev: 1.1 speed: 12 Mb/s power: 500mA chip-ID: feed:1226 class-ID: 0300
  Hub-8: 8-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 38.1 C mobo: N/A gpu: nvidia temp: 32 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 43%
Repos:
  Packages: 3018 pm: dpkg pkgs: 3011 pm: flatpak pkgs: 7
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http: //mirror.scd31.com/mint faye main upstream import backport
    2: deb https: //deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    3: deb https: //deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
    4: deb http: //security.debian.org/ bookworm-security main contrib non-free non-free-firmware
    5: deb https: //deb.debian.org/debian bookworm-backports main contrib non-free non-free-firmware
  No active apt repos in: /etc/apt/sources.list.d/steam-beta.list
  Active apt repos in: /etc/apt/sources.list.d/steam-stable.list
    1: deb [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https: //repo.steampowered.com/steam/ stable steam
    2: deb-src [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https: //repo.steampowered.com/steam/ stable steam
  Active apt repos in: /etc/apt/sources.list.d/winehq-bookworm.sources
    1: deb [arch=amd64 i386] https: //dl.winehq.org/wine-builds/debian bookworm main
Info:
  Processes: 352 Uptime: 3h 53m wakeups: 0 Memory: 31.25 GiB used: 6.88 GiB (22.0%) Init: systemd
  v: 252 target: graphical (5) default: graphical Compilers: gcc: 12.2.0 alt: 12 Client: Cinnamon
  v: 6.0.4 inxi: 3.3.26

Edit: My bad, forgot the code tags.

[gw18k]

Reverting to a previous kernel and removing a current kernel will also remove the meta package that keeps track of the kernel updates.
You can re-install the 6.1.0-18(or whatever is current kernel) and choose the -17 from the grub menu as your boot choice. Then the meta package will install the next update.
OR
You can just wait and check every week or so for the next kernel version and install it when it is available thus putting back on the auto update schedule.

[Keleth]

Alright, That sounds great.

But where do I find the instructions to do that?

That's kinda what I mean, linux mint main edition has options you select in the update manager.

But I'm not sure how to install the kernel packages to get LMDE's update manager back in line. That's the whole question I got.

[all41]

sudo apt-get update
will show what's available
inxi -S
will show what you are using.
If you suspect a kernel issue reboot, and at the grub screen choose 'Advanced options'
drop down to choose the previous working kernel. If that helps use Update Manager to
remove the newer offending kernel.
Grub will always choose the latest installed kernel.

[Keleth]

Just like in the initial Post I'm running off of 6.1.0-17AMD but do not see any updates show up in the manager.

The apt-get update shows this

Code: Select all

Ign:1 http://mirror.scd31.com/mint faye InRelease
Hit:2 http://mirror.scd31.com/mint faye Release
Hit:4 http://security.debian.org bookworm-security InRelease                   
Hit:5 https://deb.debian.org/debian bookworm InRelease                         
Hit:6 https://dl.winehq.org/wine-builds/debian bookworm InRelease              
Hit:7 https://deb.debian.org/debian bookworm-updates InRelease
Hit:8 https://deb.debian.org/debian bookworm-backports InRelease
Hit:9 https://repo.steampowered.com/steam stable InRelease

inxi -S shows this

Code: Select all

~$ inxi -S
System:
  Host: DergTower Kernel: 6.1.0-17-amd64 arch: x86_64 bits: 64
    Desktop: Cinnamon v: 6.0.4 Distro: LMDE 6 Faye

Again, it's not showing the updated kernel and no visible updates in the update manager. So How do you properly reinstall the meta package?

Tho again this is just the first post over again and I feel I'm not explaining what's going on to a sufficient degree for people to understand.

[gw18k]

Alright, That sounds great.

But where do I find the instructions to do that?

That's kinda what I mean, linux mint main edition has options you select in the update manager.

But I'm not sure how to install the kernel packages to get LMDE's update manager back in line. That's the whole question I got.

I don't see the kernel in the software manager. So, looking in synaptic package manager, search for 6.1.0-18
(Based on your previous system info, I've listed the amd64 version of the kernels)
linux-headers-6.1.0-18-amd64
linux-image-6.1.0-18-amd64
linux-image-amd64 <---this is the meta package to track updates. It is dependent on the current kernel version and is updated when the kernel is updated.
Edit: This will require reboot to use the current kernel. Use the Grub menu during boot to choose the -17 version for running if you choose. Keep them this way will get you the update with update manager.

[Keleth]

Much appreciated.

My google fu for this kinda info over the last few weeks didn't get me much headway so I made an account just for this.

Thanks, and I'll try to remember this for the future as well. Maybe I'll write a little tutorial for it, or at least notes for myself if it comes up again.

[Keleth]

Just as a little update or an aside.
There hasn't been any updates through the Update manager since last posting.

Discord shows up from a manual package install. But there hasn't been any listings of any updated packages in the manager.

I'm mostly just curious as usually some packages seemed to show up every few days prior to the little fiasco I had with the kernel.

Screenshot of the update manager and the history of updates screen.

[SMG]

Moderator note: este.el.paz's issue about getting a backported kernel to boot can now be found here Selecting Kernel Issues (stuck on 6.1.0-18 even though I want 6.5).

Please create new topics for new issues and do not add your issue to someone else's topic.

[este.el.paz]

Moderator note: este.el.paz's issue about getting a backported kernel to boot can now be found here Selecting Kernel Issues (stuck on 6.1.0-18 even though I want 6.5).

Please create new topics for new issues and do not add your issue to someone else's topic.

@SMG:

Thanks for that assist . . . it doesn't seem like this sub-forum is so over-active that piggy-backing into a similar issue, "how to change the kernel" could not have been discussed in the same thread?? Trying to save on the cyber space, etc.

I now can look forward to the discussion on the new thread.

[SMG]

Thanks for that assist . . . it doesn't seem like this sub-forum is so over-active that piggy-backing into a similar issue, "how to change the kernel" could not have been discussed in the same thread?? Trying to save on the cyber space, etc.

You are adding confusion to someone else's topic. Do not "piggy-back".
Per forum rules [2] New Questions Deserve New Topics

• Do not add new questions to existing topics, start your own instead! This will make it easier for other members to provide support. This includes hijacking, do not ask unrelated questions in a user's existing support topic.
• Do not resurrect support topics others have created. The automated topic-locking system closes topics six months after they were created so you could be locked out of a response if you resurrect someone else's topic.