kernel updates not appearing (until grub repair tool used)

[a2z]

have several partitions on a single HDD laptop ;

partition 'A' : mx19, via windows dual boot install selection, and then windows was removed.

partition 'B' : mx23 , installed from usb after windows was removed

took some guessing, but mx23 would not show for boot until one time i booted into mx19 and ran the grub repair tool.
since then, prior installed kernel updates are not appearing without running the grub repair tool (which i can run after booting into any mx version)

i would like to fix this kernel update problem, and later wipe partition 'A' (mx19) to use for data or another linux flavor.
it seems i cannot do the later safely yet, help requested.

[dolphin_oracle]

all you actually need on that mx19 is "sudo update-grub", which updates the menus.

you should be able to run the grub repair tool from your mx23 install, and then mx23's grub will take over boot chores. once that is complete, you can do what you want with the mx19 partition, but there is no need to remove it first.

[a2z]

sorry, for the delay, i was waiting for a new kernel and then hit the mxlinux.org captcha problem for weeks.
(the latter which i was able to work through on the default firefox by using incognito mode here)
although the solution offered worked once, i would mark this solution as fail.

new linux kernels (e.g., 6.....0.26) show up in mx23 grub repair for 'B' ('A' grub repair is not being allowed) and also can be selected in the mx23 boot option tool.
but they are NOT actually appearing for selection after power-up.

so on re-start, i am back to selecting the earlier release (6....0.25) for mx23, which itself only became available only after running mx19 on 'A' and then grub update as you instructed.

there does not seem a trustworthy way to re-using the 'A' partition while this problem occurs.

[Eadwine Rose]

With all help requests, as per forum rules (which, if you haven't, please read), please share your full Quick System Info, do not edit.
If need be, you can do this using the LiveUSB, thanks.

[fehlix]

new linux kernels (e.g., 6.....0.26) show up in mx23 grub repair for 'B' ('A' grub repair is not being allowed) and also can be selected in the mx23 boot option tool.
but they are NOT actually appearing for selection after power-up.

so on re-start, i am back to selecting the earlier release (6....0.25) for mx23, which itself only became available only after running mx19 on 'A' and then grub update as you instructed.

there does not seem a trustworthy way to re-using the 'A' partition while this problem occurs.

Probably a misunderstanding how grub works. Also running "MX Boot Repair" will not do anything until you select the right "tasks",
and selecting the wrong option may also result in surprises.
But perhaps, better first show QSI "Quick System Info" of the systems involved, otherwise I guess any attempt of detailed explanation, may be too theoretical - but can be given if desired.

[a2z]

thx all. the quick sys info tool does not seem to detail all partitions, but all been set to automount via the checkbox on disks tool. am also attaching the boot repair log file.

below is info when selecting mx23 boot from 'B' partition (which formerly housed windows for dual boot configured with original mx19 installed on 'A' partition). mx19 option can still be selected at boot.

Code: Select all

System:
  Kernel: 6.1.0-25-amd64 [6.1.106-3] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-25-amd64 root=UUID=<filter> ro quiet
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.4_minimal_x64 Libretto May 19  2024 base: Debian GNU/Linux
    12 (bookworm)
Machine:
  Type: Laptop System: ASUSTeK product: K55VD v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: K55VD v: 1.0 serial: <superuser required> UEFI: American Megatrends
    v: K55VD.406 date: 11/09/2012
Battery:
  ID-1: BAT0 charge: 23.3 Wh (98.7%) condition: 23.6/51.7 Wh (45.6%) volts: 12.2 min: 10.8
    model: ASUSTeK K55--47 type: Li-ion serial: N/A status: not charging
CPU:
  Info: model: Intel Core i7-3630QM bits: 64 type: MT MCP arch: Ivy Bridge gen: core 3 level: v2
    built: 2012-15 process: Intel 22nm family: 6 model-id: 0x3A (58) stepping: 9 microcode: 0x21
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 1273 high: 1400 min/max: 1200/3400 scaling: driver: intel_cpufreq
    governor: ondemand cores: 1: 1300 2: 1281 3: 1289 4: 1400 5: 1300 6: 1209 7: 1200 8: 1209
    bogomips: 38314
  Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  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: Retpolines; IBPB: conditional; IBRS_FW; STIBP: conditional; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Vulnerable: No microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel 3rd Gen Core processor Graphics vendor: ASUSTeK driver: i915 v: kernel
    arch: Gen-7 process: Intel 22nm built: 2012-13 ports: active: LVDS-1 empty: DP-1,HDMI-A-1,VGA-1
    bus-ID: 00:02.0 chip-ID: 8086:0166 class-ID: 0300
  Device-2: NVIDIA GF119M [GeForce 610M] vendor: ASUSTeK driver: N/A alternate: nouveau non-free:
    series: 390.xx+ status: legacy-active (EOL~late 2022) arch: Fermi code: GF1xx process: 40/28nm
    built: 2010-16 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:1058
    class-ID: 0300
  Device-3: Chicony UVC 1.00 device HD WebCam type: USB driver: uvcvideo bus-ID: 1-1.3:3
    chip-ID: 04f2:b354 class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31")
  Monitor-1: LVDS-1 model: AU Optronics 0x26ec built: 2009 res: 1366x768 hz: 60 dpi: 101
    gamma: 1.2 size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9 modes: 1366x768
  API: OpenGL v: 4.2 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 4000 (IVB GT2)
    direct-render: Yes
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: ASUSTeK 7
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20 class-ID: 0403
  API: ALSA v: k6.1.0-25-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: off with: 1: pipewire-pulse status: off 2: wireplumber
    status: off tools: pw-cat,pw-cli,wpctl
  Server-2: PulseAudio v: 16.1 status: active tools: pacat,pactl,pavucontrol
Network:
  Device-1: Qualcomm Atheros AR9485 Wireless Network Adapter vendor: AzureWave AW-NE186H
    driver: ath9k v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 168c:0032
    class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 04:00.2 chip-ID: 10ec:8168
    class-ID: 0200
  IF: eth0 state: down mac: <filter>
Drives:
  Local Storage: total: 698.64 GiB used: 181.87 GiB (26.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: HGST (Hitachi) model: HTS541075A9E680 size: 698.64 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: A560 scheme: GPT
Partition:
  ID-1: / raw-size: 165 GiB size: 161.35 GiB (97.79%) used: 30.64 GiB (19.0%) fs: ext4
    dev: /dev/sda2 maj-min: 8:2
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 41.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 2300
Repos:
  Packages: pm: dpkg pkgs: 1611 libs: 874 tools: apt,apt-get,aptitude,synaptic
  No active apt repos in: /etc/apt/sources.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
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mirror.cogentco.com/pub/linux/mxlinux/mx/repo/ bookworm main non-free
  Active apt repos in: /etc/apt/sources.list.d/opera-stable.list
    1: deb https://deb.opera.com/opera-stable/ stable non-free
  Active apt repos in: /etc/apt/sources.list.d/syncthing.list
    1: deb https://apt.syncthing.net/ syncthing stable
Info:
  Processes: 298 Uptime: 2d 4h 36m wakeups: 15 Memory: 5.67 GiB used: 4.06 GiB (71.5%)
  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

[fehlix]

The issue is about: When you boot int MX-23 and install/upgrade a new kernel, "update-grub get's triggered and generates a new grub-menu including the new kernel entry. This GRUB menu is located in the MX-23 /boot/grub/grub.cfg.
But this GRUB menu will only be "displayed" / "shown" after reboot, if you choose the GRUB bootloader which relates to the MX-23 installation.
So if you just reboot/power on, and you have choosen to boot int the GRUB bootloader of the MX-19 installtion,
the GRUB menu on MX-19 does have now "idea" what was done on MX-23.
The GRUB menu on MX-19 is located on the partition under /boot used by MX-19 on /boot/grub/grub.cfg,
and is a completely separate grub menu.
So yes, installing a new kernel on on MX Installtions, reuqires to boot into the other installation an regenrate the grub-menu again.

You mention also that you cannot select something within MX Boot Repair when booted into MX-23, but trying to re-generate
the GRUB menu on MX-19. This may be related to /etc/fstab on MX-19 or something else.
But maybe you show some pictures, what is actually not working.

OK, the main point was about when in MX-23 a new GRUB menu get genrated, it will only be seen
when you also boot into MX-23 generated efi GRUB loader, not when you boot int the MX-19 efi grub-loader.
During Boot up you can with e.g F12 (or another F-key select the efi-GRUB loader) select the fi-GRUB loader.
In addition you can set the default "fallback" efi loader, thats the one, if you boot from the "drive",
or incase not efi-loader are stored any more with the NVRAM.
So not sure why you defaults to boot into MX-19 and not in MX-23.
Suggest to chacge this.
Also notr the MX-23 is a minimal (respin) version, and not really supported,
so may well be that something else is missing on this installation, which create surprises.

[a2z]

thx for the reply, but unsure what you want me to try.
there is no selection for different grub screens upon boot, but the one and only grub screen shows all installed linux options EXCEPT the latest kernel installed.

maybe info below helps :

there are 2 .efi files, located in :
/media/SYSTEM/EFI/MX19/grubx64.efi
/boot/uefi-mt/mtest-64.efi

when mx23 booted and running :
all mx23 linux kernels are in
/boot/
and there is no grub folder under /boot/

also, when mx23 running, mx19 linux kernels are all in
/media/rootMX19/boot/
and efi files in
/media/rootMX19/boot/grub/x86_64-efi/

[fehlix]

TBH, based on the provided information it is not really clear to me what's going on.
Suggest this: We prepare completely fresh reinstall of GRUB so it will provide the default GRUB menu,
where you should have both the MX-23 and the MX-19 kernels listed,
and kernel upgrade/ installation would be automatic seen within the GRUB menu
But in order to do this, I'd suggest you run a couple of terminal commands,
in order to get a better picture, what's missing. And we could go from there to get prepared.
Let me know if you want to go that route and when you are ready to perform this exercise,
so I will send you the commands, which may help to find the show stopper, so we can get it done.

[a2z]

since this problem was not solved for my laptop, and i am soon doing another mx install for a different machine, am hoping for some further comments.

i suspect the problem arose due to my selection of grub options during the mx23 install (via usb) on a different partition.
(e.g., this step from a generic install website...note, this is NOT my screenshot when i installed)
https://www.linuxtechi.com/wp-content/u ... ebp/ngcb22
i confess i didnt know exactly what grub options to choose here during the mx23 install, and the help sidepane did not seem very guiding.
as noted earlier, i removed\unistalled windows once mx23 was running, but it took some months to realize the sucessfully installed mx23 new kernels were not appearing on grub boot menu.
on a possibly related note, it is unclear whether cpu microcode updates are also going into affect.

could it be that my grub choice during the initial mx install (windows dual boot option for mx19) determined what i should have used for grub options when installing mx23 on a different partion?

i will soon install the latest mx on a unbuntu desktop machine , but will first install a 2nd sata drive. am hoping to avoid situation above by knowing what is\was going on.