Page 1 of 1

Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 12:55 am
by MikeR
Running "sudo apt update" daily, should I not be upgraded to 6.1.0-13?
(Or is something missing in my sources.list?)
$ uname -r
6.1.0-12-amd64
$

Code: Select all

Snapshot created on: 20231101_1114
System:
  Kernel: 6.1.0-12-amd64 [6.1.52-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-12-amd64 root=UUID=<filter> ro quiet splash
  Desktop: GNOME v: 43.9 info: gnome-panel wm: Metacity v: 3.46.1 dm: LightDM v: 1.26.0
    Distro: MX-23.1_x64 Libretto July 31 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop System: HP product: HP ProDesk 400 G4 DM (TAA) v: SBKPF
    serial: <superuser required> Chassis: type: 6 serial: <superuser required>
  Mobo: HP model: 83F3 v: KBC Version 07.D2.00 serial: <superuser required> UEFI: HP
    v: Q23 Ver. 02.25.00 date: 09/28/2023
CPU:
  Info: model: Intel Core i5-8500T bits: 64 type: MCP arch: Coffee Lake gen: core 8 level: v3
    note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 0xA (10)
    microcode: 0xF4
  Topology: cpus: 1x cores: 6 smt: <unsupported> cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB
    L2: 1.5 MiB desc: 6x256 KiB L3: 9 MiB desc: 1x9 MiB
  Speed (MHz): avg: 1666 high: 2100 min/max: 800/3500 scaling: driver: intel_pstate
    governor: powersave cores: 1: 2100 2: 2100 3: 2100 4: 800 5: 800 6: 2100 bogomips: 25199
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: disabled, RSB filling,
    PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: Hewlett-Packard driver: i915
    v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: DP-1 empty: DP-2,
    DP-3, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:3e92 class-ID: 0300
  Device-2: Jieli USB PHY 2.0 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-2.3:10
    chip-ID: 1224:2a25 class-ID: 0102
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X: loaded: modesetting
    unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1280x1024 s-dpi: 192 s-size: 169x127mm (6.65x5.00") s-diag: 211mm (8.32")
  Monitor-1: DP-1 model: Dell E1913S serial: <filter> built: 2012 res: 1280x1024 hz: 60 dpi: 86
    gamma: 1.2 size: 376x301mm (14.8x11.85") diag: 482mm (19") ratio: 5:4 modes: max: 1280x1024
    min: 720x400
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Cannon Lake PCH cAVS vendor: Hewlett-Packard driver: snd_hda_intel bus-ID: 1-1:2
    v: kernel chip-ID: 08bb:2902 alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3
    class-ID: 0300 chip-ID: 8086:a348 class-ID: 0403
  Device-2: Texas Instruments PCM2902 Audio Codec type: USB
    driver: hid-generic,snd-usb-audio,usbhid
  Device-3: Jieli USB PHY 2.0 type: USB driver: snd-usb-audio,uvcvideo bus-ID: 1-2.3:10
    chip-ID: 1224:2a25 class-ID: 0102
  API: ALSA v: k6.1.0-12-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 02:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 238.47 GiB used: 22.66 GiB (9.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: MZVLB256HAHQ-000H7 size: 238.47 GiB
    block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: EXD70H2Q temp: 31.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 40 GiB size: 39.07 GiB (97.68%) used: 8.12 GiB (20.8%) fs: ext4
    dev: /dev/nvme0n1p5 maj-min: 259:5
  ID-2: /home raw-size: 40 GiB size: 39.08 GiB (97.69%) used: 14.54 GiB (37.2%) fs: ext4
    dev: /dev/nvme0n1p6 maj-min: 259:6
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 4 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p7
    maj-min: 259:7
Sensors:
  System Temperatures: cpu: 34.0 C pch: 40.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2469 libs: 1196 tools: apt,apt-get,aptitude,gnome-software,nala,synaptic
    pm: rpm pkgs: 0 pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  No active apt repos in: /etc/apt/sources.list.d/archive_uri-http_security_debian_org_debian-security-bookworm.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
    3: deb http://deb.debian.org/debian bookworm-backports main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb https://mirror.23m.com/mx-packages/mx/repo/ bookworm main non-free
Info:
  Processes: 249 Uptime: 1h 59m wakeups: 1 Memory: 7.6 GiB used: 2.2 GiB (28.9%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 1:44 am
by Mauser
You should see after updating and rebooting your computer the following.

Code: Select all

Kernel: 6.1.0-15-amd64 [6.1.66-1] arch: x86_64 bits:

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 2:16 am
by MikeR
following your advice, I did the following:
mike@mxprodesk:~$ sudo apt update
[sudo] password for mike:
Hit:1 http://security.debian.org/debian-security bookworm-security InRelease
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
Hit:3 http://deb.debian.org/debian bookworm InRelease
Hit:4 http://deb.debian.org/debian bookworm-backports InRelease
Get:5 https://mirror.23m.com/mx-packages/mx/repo bookworm InRelease [25.2 kB]
Get:6 https://mirror.23m.com/mx-packages/mx/repo bookworm/main amd64 Packages [154 kB]
Get:7 https://mirror.23m.com/mx-packages/mx/repo bookworm/main i386 Packages [152 kB]
Get:8 https://mirror.23m.com/mx-packages/mx/repo bookworm/main i386 Contents (deb) [1,128 kB]
Get:9 https://mirror.23m.com/mx-packages/mx/repo bookworm/main amd64 Contents (deb) [1,131 kB]
Fetched 2,591 kB in 11s (234 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
mike@mxprodesk:~$ apt list --upgradable
Listing... Done
mx-conky-data/mx,mx 20231201 all [upgradable from: 20230701]
N: There is 1 additional version. Please use the '-a' switch to see it
mike@mxprodesk:~$ sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
mx-conky-data
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 8,230 kB of archives.
After this operation, 9,216 B of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 https://mirror.23m.com/mx-packages/mx/repo bookworm/main amd64 mx-conky-data all 20231201 [8,230 kB]
Fetched 8,230 kB in 29s (283 kB/s)
(Reading database ... 326523 files and directories currently installed.)
Preparing to unpack .../mx-conky-data_20231201_all.deb ...
Unpacking mx-conky-data (20231201) over (20230701) ...
Setting up mx-conky-data (20231201) ...
mike@mxprodesk:~$
and rebooted.
The result was (still):
mike@mxprodesk:~$ uname -r
6.1.0-12-amd64
mike@mxprodesk:~$

Code: Select all

 Kernel: 6.1.0-12-amd64 [6.1.52-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
Sorry, no cigar. :bawling:
... Apologies for the long post.

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 2:32 am
by Mauser
You have something seriously wrong with your MX-23.1 installation. Try updating from a different location or different mirrors because what you posted there doesn't show that you downloaded an updated kernel. This means you must have other packages that are out of date as well.

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 2:48 am
by MikeR
Went to "MX Repo manager" and changed mirror at random.
New update shows a different mirror, but with a similar result:
Nothing to update.

I really do not feel up to re-installing from scratch, so any further advice would be gratefully accepted.
$ sudo apt update
Hit:1 http://security.debian.org/debian-security bookworm-security InRelease
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
Hit:3 http://deb.debian.org/debian bookworm InRelease
Hit:4 http://deb.debian.org/debian bookworm-backports InRelease
Get:5 http://ftp.ntua.gr/pub/linux/mxlinux/mx/repo bookworm InRelease [25.2 kB]
Get:6 http://ftp.ntua.gr/pub/linux/mxlinux/mx/repo bookworm/main amd64 Packages [154 kB]
Get:7 http://ftp.ntua.gr/pub/linux/mxlinux/mx/repo bookworm/main i386 Packages [152 kB]
Get:8 http://ftp.ntua.gr/pub/linux/mxlinux/mx/repo bookworm/main amd64 Contents (deb) [1,131 kB]
Get:9 http://ftp.ntua.gr/pub/linux/mxlinux/mx/repo bookworm/main i386 Contents (deb) [1,128 kB]
Get:10 http://ftp.ntua.gr/pub/linux/mxlinux/mx/repo bookworm/non-free amd64 Packages [44.9 kB]
Get:11 http://ftp.ntua.gr/pub/linux/mxlinux/mx/repo bookworm/non-free i386 Packages [36.3 kB]
Get:12 http://ftp.ntua.gr/pub/linux/mxlinux/mx/repo bookworm/non-free amd64 Contents (deb) [26.7 kB]
Get:13 http://ftp.ntua.gr/pub/linux/mxlinux/mx/repo bookworm/non-free i386 Contents (deb) [15.1 kB]
Fetched 2,714 kB in 43s (62.5 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 2:57 am
by Mauser
Post "Quick System Info" because maybe there is something in there will tell everyone what is causing that.

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 3:26 am
by MikeR
Quick System info is in my original post.

I also tried changing the address for the Debian repositories, and upon update (several attempts) saw:
$ sudo apt update
[sudo] password for mike:
Hit:1 http://ftp.ntua.gr/pub/linux/mxlinux/mx/repo bookworm InRelease
Hit:2 http://deb.debian.org/debian bookworm-backports InRelease
Hit:3 https://deb.debian.org/debian bookworm-updates InRelease
Hit:4 https://deb.debian.org/debian bookworm InRelease
Ign:5 https://deb.debian.org/debian bookworm-security InRelease
Err:6 https://deb.debian.org/debian bookworm-security Release
404 Not Found [IP: 146.75.122.132 443]
Reading package lists... Done
E: The repository 'https://deb.debian.org/debian bookworm-security Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
When I unchecked the relevant line in Synaptic --> Settings --> Repositories the error did not appear.
Is the repository 'https://deb.debian.org/debian bookworm-security Release' necessary? And if it is, where can it be found?

On the page https://mxlinux.org/uncategorized/repos-mx-21/ (Where the latest version that appears is MX21)
the line 'deb http://security.debian.org/debian-security bullseye-security main contrib non-free' DOES appear
Is the equivalent line for bookworm needed?
Many thanks for any advice!!

P.S. in debian security I see
If you are using apt you can use this entry in /etc/apt/sources.list:

deb http://security.debian.org/debian-security stable-security main
Does this apply to MX23? Perhaps the Repo web page could be updates

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 10:00 am
by Mauser
MikeR "Quick System info is in my original post." Sorry that I missed that because it was around 3:00AM where I am which is way past my bedtime and I went to sleep right after my last post.

Based on my installation:
"https://deb.debian.org/debian" Is correct.
"When I unchecked the relevant line in Synaptic --> Settings --> Repositories the error did not appear.
Is the repository 'https://deb.debian.org/debian bookworm-security Release' necessary? And if it is, where can it be found?" All those boxes should have a check in them except for Source code.
In the "Other Software" tab you should have checks on these. https://imgur.com/JtEobJp

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 10:46 am
by MXRobo
I'm on MX-21.3 and I don't really know this stuff, but do you have the metapackages installed, or did you somehow delete them?
linux-image-amd64
linux-headers-amd64


These auto update the kernels.

I ask because you may have deleted them to avoid the 6.1.whatever number kernel problem.
I don't know the details because I'm not affected.

And if you do install them, you should get the updates, but you may not want every kernel update because of that kernel issue – again I don't know the details because I'm not affected. But if that's the problem, you and maybe I can get it working from there.

"Just doing "apt-get upgrade" held back the kernel and header" from: viewtopic.php?p=756471#p756471

I could be wrong because I can't really check this on my MX-21.3 but – anyway.

Good Luck.

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 11:09 am
by j2mcgreg
@MikeR

Your main repo likely isn't as up to date as it should be, so your first step should be to use Repo Manager in MX Tools to switch to Milan, Italy which isthe closest one we own and operate to you. At the same time you should then access the Individual Sources tab and enable the AHS repo (should be the bottom entry on the list). Now log out / in and use MXPI to install the Liquorix 6.6.6-1 kernel and then reboot. Finally apply all the updates. The reason for installing the Liquorix kernel is that there is a major bug playing havoc with our stock kernels at the moment.

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 11:48 am
by MikeR
@j2mcgreg

Sorry, but the list in Individual Sources seemed to consist of only the repos I already have.
So I stopped the process where was: No AHS, No Liquorix.

OTOH, seeing as how the current installed version offers no problems, perhaps I should stay with it until whatever problems you are having are cleared up. (They will eventually be cleared up -- He says hopefully)
My main worry was that I had setup something wrong, and as long as it's someone else's problem - so be it.

As a final question: How important i it that I do eventually upgrade?

Thank you for taking the time, and for you clear suggestions.

Mike

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 12:01 pm
by MXRobo
:bagoverhead:

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 12:05 pm
by j2mcgreg
Screenshot_2023-12-14_12-03-41.png
MXRobo wrote: Thu Dec 14, 2023 12:01 pm MX Repo, not Individual Sources.

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 12:10 pm
by MXRobo
My fault, I did not read the second sentence. :bagoverhead:

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 12:24 pm
by MikeR
@j2mcgreg
@MXRobo

This is all I saw on the Individual Sources page

x.jpg

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 12:51 pm
by Stevo
It might be related to you having bookworm-backports enabled, contrary to the MX recommendations.

You can see what may be available for 6.1 kernels by (I use this because it's architecture-independent, so no different commands for i386 or arm installs) So we can see that Bookworm still does not have the 6.1.67 kernels available--maybe they are "twice burned, quadruple shy"?

Code: Select all

$ apt policy linux-source-6.1

linux-source-6.1:
  Installed: (none)
  Candidate: 6.1.66-1
  Version table:
     6.1.66-1 500
        500 http://deb.debian.org/debian bookworm/main amd64 Packages
        500 http://deb.debian.org/debian bookworm/main i386 Packages
     6.1.55-1 500
        500 http://deb.debian.org/debian bookworm/main amd64 Packages
        500 http://deb.debian.org/debian bookworm/main i386 Packages
     6.1.52-1 500
        500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages
        500 http://security.debian.org/debian-security bookworm-security/main i386 Packages
     6.1.38-4 500
        500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages
        500 http://security.debian.org/debian-security bookworm-security/main i386 Packages

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 1:10 pm
by MikeR
@Stevo

I unchecked bookworm-backports in Synaptic --> Settings --> Repositories --> Other Software
Reloaded, ran sudo apt update .... No visible results

By the way, I didn't know bookworm-backports was disparaged, I don't think I actively added it, IIRC.
Leaving it unchecled meanwhile. Can that hurt?

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 5:51 pm
by MXRobo
It should NOT be checked, neither should the testing.

Both the Test and Backport tabs in MXPI are TEMPORARILY enabled to install these packages, then disabled after installing to avoid dependency conflicts.
The devs, (maybe Stevo) does his thing and also checks for dependency conflicts before adding them.

I assumed, or guessed, or made some of that up - - but I think it suffices for the concept. :p

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 7:57 pm
by Stevo
The apt system itself handles dependency issues, but a packager can also give it extra instructions when setting up the package build.

Our testing repo really never generated problems if left on all the time, but as it expanded to thousands of packages, it became very difficult, if not impossible, to help users that automatically upgraded all of those by leaving it on, and then had some sort of problem that might be due to one.

Dolphin_oracle lowered the test repo's priority so upgrades aren't automatic any longer to keep that from happening, but that means you need special commands to get a newer package installed from it, which MXPI does automatically for you. The Debian backports repo has the same setup, as we pretty much copied it, but MXPI makes it much easier to search and manage both.

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 7:59 pm
by Stevo
Also, could you run "apt policy linux-source-6.1" and see if your output matches mine in the above example?

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Thu Dec 14, 2023 11:58 pm
by figueroa
@MikeR, apt upgrade won't upgrade the kernel or kernel headers at this time. Had you run apt full-upgrade, apt would have offered to upgrade both the kernel and headers.

I suggest you use "apt-get -s full-upgrade" which will "simulate" the upgrade process. This will let you SEE in advance what will be upgraded without any pressure to pull the trigger. If it offers you 6.1.0.15, you may want to wait as 6.1.0.15 has caused some users problems with their ext4 file systems.

ADDED: Why don't you just use the updater in the panel?

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Fri Dec 15, 2023 1:19 am
by asqwerth
good catch, @figueroa .

@MikeR

In fact,
sudo apt update is equivalent to the reloading of package lists in Synaptic.

you should be typing UPGRADE, not UPDATE.

But take note:
sudo apt upgrade will only upgrade packages that don't involve the installing (or removal) of additional packages to facilitate the upgrade.

If you want your upgrade to be able to install additional packages (in this case, latest kernels/headers in the 6.1 series), you need

sudo apt full-upgrade

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Fri Dec 15, 2023 2:13 am
by MikeR
@Stevo
$ apt policy linux-source-6.1
linux-source-6.1:
Installed: (none)
Candidate: 6.1.66-1
Version table:
6.1.66-1 500
500 https://deb.debian.org/debian bookworm/main amd64 Packages
500 https://deb.debian.org/debian bookworm/main i386 Packages
6.1.55-1 500
500 https://deb.debian.org/debian bookworm/main amd64 Packages
500 https://deb.debian.org/debian bookworm/main i386 Packages
using eyeball-diff, not quite the same as your result.

@figueroa
$ sudo apt-get -s full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
ADDED: Why don't you just use the updater in the panel?
Actually, I do, but that only shows when there are impending updates (IIRC)

@asqwerth
sudo apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Thank you all for your efforts.
What is your opinion of the possibility that I install 6.1.0-13 from MX Package Installer --> Enabled Repos --> linux-image-6.1.0-13-amd64 ?

Mike

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Fri Dec 15, 2023 12:05 pm
by MXRobo
Not sure, but FYI R-Click on green updater box avails:
Upgrade with Snynaptic
also,
Preferences - GUI
full upgrade (recommended)
basic upgrade
update automatically (will not add new or remove existing packages), assume it's sudo apt upgrade.

Not absolutely sure what basic upgrade does, maybe add equivalent command in parenthesis? - thought?

Others with more knowledge, but I'm guessing they'll agree that it's fine IF it's not a kernel that is causing problems.

Also, once you get what you want installed, either figueroa's method with simulate, or via the one of the later two? MX-Updater>Preferences options, I'd change it back to the recommended once this issue it resolved by Debian of the devs.

fugueroa's method seems to be the better one, although I've not use simulate yet.

Re: Why am I stuck in 6.1.0-12 kernel  [Solved]

Posted: Fri Dec 15, 2023 12:34 pm
by Charlie Brown
@MikeR If I'm not missing something you didn't reply/check this (which's responsible of auto-upgrading job for the default kernel):
MXRobo wrote: Thu Dec 14, 2023 10:46 am ... but do you have the metapackages installed, or did you somehow delete them?
linux-image-amd64
linux-headers-amd64

Code: Select all

apt list linux-image-amd64 linux-headers-amd64
If the output is like this (without [installed] )

Code: Select all

Listing... Done
linux-headers-amd64/stable 6.1.66-1 amd64
linux-image-amd64/stable 6.1.66-1 amd64
just install them:

Code: Select all

sudo apt update ; sudo apt install linux-image-amd64 linux-headers-amd64 -y
now you can either use the MX Updater, or apt / apt-get / aptitude , even nala:

Code: Select all

sudo nala upgrade

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Fri Dec 15, 2023 11:35 pm
by Stevo
At this point, 6.1.66 is known to cause wi-fi problems for a host of users, so I would hold off any updates until you see 6.1.67 available, which should be very soon.

If you don't use wi-fi, you could go ahead with the updates.

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Sat Dec 16, 2023 12:42 am
by MikeR
Deleted post

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Sat Dec 16, 2023 12:55 am
by MikeR
@Charlie Brown
$ apt list linux-image-amd64 linux-headers-amd64
Listing... Done
linux-headers-amd64/stable-updates 6.1.67-1 amd64 [residual-config]
linux-image-amd64/stable-updates 6.1.67-1 amd64 [residual-config]
As I didn't understand the 'residual-config' bit, I decided to continue with the rest of your advice:
(Very long quote follows)
$ sudo apt update ; sudo apt install linux-image-amd64 linux-headers-amd64 -y
[sudo] password for mike:
Hit:1 http://it.mxrepo.com/mx/repo bookworm InRelease
Hit:2 https://deb.debian.org/debian bookworm-updates InRelease
Hit:3 https://deb.debian.org/debian bookworm InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
apparmor linux-headers-6.1.0-16-amd64 linux-headers-6.1.0-16-common
linux-image-6.1.0-16-amd64
Suggested packages:
apparmor-profiles-extra apparmor-utils linux-doc-6.1 debian-kernel-handbook
The following NEW packages will be installed:
apparmor linux-headers-6.1.0-16-amd64 linux-headers-6.1.0-16-common
linux-headers-amd64 linux-image-6.1.0-16-amd64 linux-image-amd64
0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
Need to get 80.6 MB of archives.
After this operation, 472 MB of additional disk space will be used.
Get:1 https://deb.debian.org/debian bookworm/main amd64 apparmor amd64 3.0.8-3 [616 kB]
Get:2 https://deb.debian.org/debian bookworm-updates/main amd64 linux-headers-6.1.0-16-common all 6.1.67-1 [9,928 kB]
Get:3 https://deb.debian.org/debian bookworm-updates/main amd64 linux-headers-6.1.0-16-amd64 amd64 6.1.67-1 [1,289 kB]
Get:4 https://deb.debian.org/debian bookworm-updates/main amd64 linux-headers-amd64 amd64 6.1.67-1 [1,420 B]
Get:5 https://deb.debian.org/debian bookworm-updates/main amd64 linux-image-6.1.0-16-amd64 amd64 6.1.67-1 [68.7 MB]
Get:6 https://deb.debian.org/debian bookworm-updates/main amd64 linux-image-amd64 amd64 6.1.67-1 [1,476 B]
Fetched 80.6 MB in 3min 4s (438 kB/s)
Preconfiguring packages ...
Selecting previously unselected package apparmor.
(Reading database ... 326678 files and directories currently installed.)
Preparing to unpack .../0-apparmor_3.0.8-3_amd64.deb ...
Unpacking apparmor (3.0.8-3) ...
Selecting previously unselected package linux-headers-6.1.0-16-common.
Preparing to unpack .../1-linux-headers-6.1.0-16-common_6.1.67-1_all.deb ...
Unpacking linux-headers-6.1.0-16-common (6.1.67-1) ...
Selecting previously unselected package linux-headers-6.1.0-16-amd64.
Preparing to unpack .../2-linux-headers-6.1.0-16-amd64_6.1.67-1_amd64.deb ...
Unpacking linux-headers-6.1.0-16-amd64 (6.1.67-1) ...
Selecting previously unselected package linux-headers-amd64.
Preparing to unpack .../3-linux-headers-amd64_6.1.67-1_amd64.deb ...
Unpacking linux-headers-amd64 (6.1.67-1) ...
Selecting previously unselected package linux-image-6.1.0-16-amd64.
Preparing to unpack .../4-linux-image-6.1.0-16-amd64_6.1.67-1_amd64.deb ...
Unpacking linux-image-6.1.0-16-amd64 (6.1.67-1) ...
Selecting previously unselected package linux-image-amd64.
Preparing to unpack .../5-linux-image-amd64_6.1.67-1_amd64.deb ...
Unpacking linux-image-amd64 (6.1.67-1) ...
Setting up linux-image-6.1.0-16-amd64 (6.1.67-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.1.0-12-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-6.1.0-12-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-6.1.0-16-amd64
I: /initrd.img is now a symlink to boot/initrd.img-6.1.0-16-amd64
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-16-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.1.0-16-amd64
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
grep: /lib/modules/6.1.0-12-amd64/build/.config: No such file or directory
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
grep: /lib/modules/6.1.0-12-amd64/build/.config: No such file or directory
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area...
make -j6 KERNELRELEASE=6.1.0-16-amd64 KVER=6.1.0-16-amd64....
Signing module /var/lib/dkms/broadcom-sta/6.30.223.271/build/wl.ko
Cleaning build area...

wl.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-16-amd64/updates/dkms/
depmod...
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area...
'make' all KVER=6.1.0-16-amd64...........................
Signing module /var/lib/dkms/rtl8188fu/1.0/build/rtl8188fu.ko
Cleaning build area...

rtl8188fu.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-16-amd64/updates/dkms/
depmod...
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)

Building module:
Cleaning build area...
'make' -j6 KVER=6.1.0-16-amd64 USER_MODULE_NAME=rtl8821ce CONFIG_RTW_DEBUG=n.............
Signing module /var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/build/rtl8821ce.ko
Cleaning build area...

rtl8821ce.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-16-amd64/updates/dkms/
depmod...
Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area...
'make' all KVER=6.1.0-16-amd64..........................................................
Signing module /var/lib/dkms/rtl8821cu/5.12.0/build/8821cu.ko
Cleaning build area...

8821cu.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/6.1.0-16-amd64/updates/dkms/
depmod...
dkms: autoinstall for kernel: 6.1.0-16-amd64.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-16-amd64
I: The initramfs will attempt to resume from /dev/nvme0n1p7
I: (UUID=deff4166-e794-41be-b529-8b2a44a031c0)
I: Set the RESUME variable to override this.
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found theme: /boot/grub/themes/mx_linux/theme.txt
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-6.1.0-16-amd64
Found initrd image: /boot/initrd.img-6.1.0-16-amd64
Found linux image: /boot/vmlinuz-6.1.0-12-amd64
Found initrd image: /boot/initrd.img-6.1.0-12-amd64
Found linux image: /boot/vmlinuz-6.1.0-11-amd64
Found initrd image: /boot/initrd.img-6.1.0-11-amd64
Found mtest-64.efi image: /boot/uefi-mt/mtest-64.efi
Found Windows Boot Manager on /dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for EFI firmware configuration
done
Setting up linux-headers-6.1.0-16-common (6.1.67-1) ...
Setting up linux-image-amd64 (6.1.67-1) ...
Setting up apparmor (3.0.8-3) ...
Created symlink /etc/systemd/system/sysinit.target.wants/apparmor.service → /lib/systemd/system/apparmor.service.
Reloading AppArmor profiles
Skipping profile in /etc/apparmor.d/disable: usr.bin.thunderbird
Setting up linux-headers-6.1.0-16-amd64 (6.1.67-1) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-16-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.1.0-16-amd64
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
grep: /lib/modules/6.1.0-12-amd64/build/.config: No such file or directory
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf)
dkms: autoinstall for kernel: 6.1.0-16-amd64.
Setting up linux-headers-amd64 (6.1.67-1) ...
Processing triggers for man-db (2.11.2-2) ...
HOORAY!! This seems to have unplugged the jam!!
I'll try rebooting, and hopefully come back here to mark this topic SOLVED

Many, many thanks to all who participated :number1:
[/quote]

EDIT:
after reboot:
$ uname -r
6.1.0-16-amd64
Seems O.K. If there are WiFi issues I can work around them (Ethernet is up)
Once again -- Many thanks to all!!
~Mike

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Sat Dec 16, 2023 5:39 am
by Charlie Brown
:biggrin: :biggrin: :biggrin: :biggrin: :biggrin: :number1:

Also salute @MXRobo

The residual config thing is that the configuration files were still there for it was just removed but not purged. (I had purged mine, therefore it doesn't show that, too).

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Sat Dec 16, 2023 6:09 am
by MikeR
@MXRobo
Also salute @MXRobo
Too true. mea culpa.
MANY THANKS!! :yourock:

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Sun Dec 17, 2023 2:35 am
by Stevo
Your QSI shows that you aren't using any of those dkms wi-fi driver packages that make up most of your output above, so I'd recommend removing them. Let's see, I'm not great at the CLI. You could search for installed -dkms packages using "Status" in Synaptic, or in MXPI, or simulate removal with apt:

Code: Select all

sudo apt remove -s *-dkms
The stuff that will actually be removed appears at the end of that long output. You can run the command for reals by removing the "-s" (simulate) flag in that command.

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Sun Dec 17, 2023 12:57 pm
by l0dr3
Stevo wrote: Sun Dec 17, 2023 2:35 am Your QSI shows that you aren't using any of those dkms wi-fi driver packages that make up most of your output above, so I'd recommend removing them. Let's see, I'm not great at the CLI. You could search for installed -dkms packages using "Status" in Synaptic, or in MXPI, or simulate removal with apt:

Code: Select all

sudo apt remove -s *-dkms
The stuff that will actually be removed appears at the end of that long output. You can run the command for reals by removing the "-s" (simulate) flag in that command.
;) Heres what i always do in a fresh VM ...

Code: Select all

apt policy rtl8812au-dkms &&	apt purge rtl8812au-dkms
apt policy rtl8821cu-dkms &&	apt purge rtl8821cu-dkms
apt policy rtl8821ce-dkms &&	apt purge rtl8821ce-dkms
apt policy broadcom-sta-dkms && apt purge broadcom-sta-dkms

Re: Why am I stuck in 6.1.0-12 kernel

Posted: Mon Dec 18, 2023 2:04 am
by Stevo
Thanks! Though I'm pretty sure you can also just "sudo apt purge package1 package2 package3..." instead.