Problems with kernel 6.6.10-1 on Dell XPS 9730 and VMWare

Comming from linux61 which was pretty stable but did not work with VMware Workstation 17.5, now it’s really f…up and I like to go back to 61 or if no other way possible will do a reinstall. What do you guys think ?

Here the outcome of System:

  Kernel: 6.6.10-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=84aa4b83-101b-47c4-8122-508caa2eef10 rw quiet splash
  Console: pty pts/1 DM: SDDM Distro: Manjaro Linux base: Arch Linux
  Type: Laptop System: Dell product: XPS 17 9730 v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Dell model: 0MW4M4 v: A00 serial: <superuser required> UEFI: Dell
    v: 1.8.0 date: 11/10/2023
  ID-1: BAT0 charge: 95.1 Wh (100.0%) condition: 95.1/95.1 Wh (100.0%)
    volts: 12.7 min: 11.4 model: BYD DELL F8CPG33 type: Li-poly serial: <filter>
    status: not charging cycles: 11
  Info: model: 13th Gen Intel Core i9-13900H bits: 64 type: MST AMCP
    arch: Raptor Lake gen: core 13 level: v3 note: check built: 2022+
    process: Intel 7 (10nm) family: 6 model-id: 0xBA (186) stepping: 2
    microcode: 0x411C
  Topology: cpus: 1x cores: 14 mt: 6 tpc: 2 st: 8 threads: 20 smt: enabled
    cache: L1: 1.2 MiB desc: d-8x32 KiB, 6x48 KiB; i-6x32 KiB, 8x64 KiB
    L2: 11.5 MiB desc: 6x1.2 MiB, 2x2 MiB L3: 24 MiB desc: 1x24 MiB
  Speed (MHz): avg: 421 high: 740 min/max: 400/5200:5400:4100 scaling:
    driver: intel_pstate governor: powersave cores: 1: 400 2: 400 3: 400 4: 400
    5: 494 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 13: 740 14: 400
    15: 400 16: 400 17: 400 18: 400 19: 400 20: 400 bogomips: 119840
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data 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
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS, IBPB: conditional,
    RSB filling, PBRSB-eIBRS: SW sequence
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
  Device-1: Intel Raptor Lake-P [Iris Xe Graphics] vendor: Dell driver: i915
    v: kernel arch: Gen-13 process: Intel 7 (10nm) built: 2022+ ports:
    active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4 bus-ID: 00:02.0
    chip-ID: 8086:a7a0 class-ID: 0300
  Device-2: NVIDIA AD106M [GeForce RTX 4070 Max-Q / Mobile] vendor: Dell
    driver: nvidia v: 545.29.06 alternate: nouveau,nvidia_drm non-free: 545.xx+
    status: current (as of 2023-11) arch: Lovelace code: AD1xx
    process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 8
    bus-ID: 01:00.0 chip-ID: 10de:2820 class-ID: 0302
  Device-3: Microdia Integrated_Webcam_HD driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-6:2 chip-ID: 0c45:6748
    class-ID: fe01 serial: <filter>
  Display: server: Xorg v: with: Xwayland v: 23.2.3
    compositor: kwin_x11 driver: X: loaded: modesetting,nvidia unloaded: nouveau
    alternate: fbdev,nv,vesa dri: iris gpu: i915 tty: 127x32
  Monitor-1: eDP-1 model: Sharp 0x1517 built: 2021 res: 3840x2400 dpi: 266
    gamma: 1.2 size: 366x229mm (14.41x9.02") diag: 432mm (17") ratio: 16:10
    modes: 3840x2400
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
    drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia inactive: wayland,x11,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: mesa v: 23.3.3-manjaro1.1
    note: console (EGL sourced) renderer: NVIDIA GeForce RTX 4070 Laptop
    GPU/PCIe/SSE2, Mesa Intel Graphics (RPL-P), llvmpipe (LLVM 16.0.6 256
  API: Vulkan v: 1.3.274 layers: 1 device: 0 type: discrete-gpu name: NVIDIA
    GeForce RTX 4070 Laptop GPU driver: nvidia v: 545.29.06
    device-ID: 10de:2820 surfaces: N/A device: 1 type: integrated-gpu
    name: Intel Graphics (RPL-P) driver: mesa intel v: 23.3.3-manjaro1.1
    device-ID: 8086:a7a0 surfaces: N/A
  Device-1: Intel Raptor Lake-P/U/H cAVS vendor: Dell
    driver: sof-audio-pci-intel-tgl
    alternate: snd_hda_intel,snd_sof_pci_intel_tgl bus-ID: 00:1f.3
    chip-ID: 8086:51ca class-ID: 0401
  API: ALSA v: k6.6.10-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.0.0 status: off with: wireplumber status: active
    tools: pw-cli,wpctl
  Server-3: PulseAudio v: 16.1 status: active with: pulseaudio-alsa
    type: plugin tools: pacat,pactl,pavucontrol
  Device-1: Intel Raptor Lake PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:51f1 class-ID: 0280
  IF: wlp0s20f3 state: up mac: <filter>
  Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:4 chip-ID: 8087:0033
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
  Local Storage: total: 2.75 TiB used: 1.44 TiB (52.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 990 PRO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 0B2QJXG7 temp: 27.9 C
    scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:2 vendor: Western Digital model: PC SN810
    NVMe WDC 1024GB size: 953.87 GiB block-size: physical: 512 B logical: 512 B
    speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: 61912523
    temp: 27.9 C scheme: GPT
  ID-1: / raw-size: 953.57 GiB size: 937.53 GiB (98.32%)
    used: 410.84 GiB (43.8%) fs: ext4 dev: /dev/nvme1n1p2 maj-min: 259:4
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 18.8 MiB (6.3%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:3
  Kernel: swappiness: 10 (default 60) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: file size: 16 GiB used: 512 KiB (0.0%) priority: -2
    file: /swapfile
  System Temperatures: cpu: 33.0 C mobo: 26.0 C gpu: nvidia temp: 32 C
  Fan Speeds (rpm): cpu: 0
  Processes: 344 Uptime: 6h 9m wakeups: 0 Memory: total: 32 GiB note: est.
  available: 31.04 GiB used: 3.27 GiB (10.5%) Init: systemd v: 255
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
  Packages: pm: pacman pkgs: 1302 libs: 400 tools: pamac,yay pm: flatpak
  pkgs: 0 Shell: Bash v: 5.2.21 running-in: pty pts/1 (SSH) inxi: 3.3.31

If you didn’t remove linxu61, then you should be able to choose it on the grub boot loader. Type ESC on boot time to unhide it.

thanks megavolt. 61 is still installed,

Currently running: 6.6.10-1-MANJARO (linux66)
The following kernels are installed in your system:

  • linux61
  • linux66

I tried esc or F8 at startup and changed the behaviour in the timout-style, but it does not show the grub menue. Are there other options to switch the kernel or how do I get the grub menue up ?

The Grub menu is (or should be) the first thing you boot into without touching any keys. When you reach it, you can use up/down arrow keys to move between menu items.

No, try to type ESC very fast, multiple times, right after powered it on.

Nope, only if changed it to menu or having a dual boot.

I’ve never known Grub without a menu. However, I do multiboot. :wink:

Thank you all, I am up and running again. I was running it without grub, I think, which was an mistake. Installed grub and was enable to switch back to 61.

Me neither and I haven’t dual-booted any of my Manjaro systems. Maybe later ISOs; will have to check this. I know with Mint I had to modify /etc/default/grub accordingly to enable the GRUB menu.

I somehow doubt this, unless you have another bootloader installed or you’re booting directly to a kernel using some UEFI option. Do you actually mean you updated GRUB e.g. sudo update-grub? This will help to clarify things for other readers of this thread. :smiling_face:

I guess the GRUB menu was just being bypassed in your case.

There was a thread a few weeks ago; complaints ran amok about a problem with Grub. It turns out he had installed rEFInd, and simply didn’t know the difference. With rEFInd, one can bypass Grub completely, and boot directly to the kernel stub, which was obviously what he had been doing. :facepalm:

1 Like

hm, weird, I did a pacman -Syu grub and I can see now the partition it is using for grub in /etc/fstab which I did not had before

1 Like

I think I have found my issue too, it was the linux66 and my VMware Workstation installation, will follow up on that

VMware rarely play nice with bleeding edge Linux - neither as host nor as guest.

On some systems Esc key opens firmware settings - in that case use Shift

got it working linux66 and VMware Workstation 17.5, no issues anymore.