[Testing Update] 2023-03-11 - Kernels, Mesa 22.3.7, Phosh, LibreOffice 7.4.6

Just pushed 6.2.4-1 & 6.1.17-1.


I just swooped past the 6.2.3 and 6.1.17 release - just got 6.2.4 and 6.1.17 on unstable.

1 Like

for unstable version 6.2.5 & 6.1.19 ( all others series has been released )

The new point releases are building now. :wink:


G H for hotfix patch


Well, the wifi fix is coming … [pkg-upd] 6.2.5-1 (e66a84e7) · Commits · Packages / Core / linux62 · GitLab


Resolved by kernel update linux62 (6.2.3-1 → 6.2.4-1) and linux61 (6.1.16-1 → 6.1.17-1)

Thank you Yochanan for lightspeed reaction :+1: and stephane for finding the solution :+1:

thank team manjaro for responding so quickly

1 Like

May be linked to the problem I had with a previous unstable version. (did not test on this one)

Intel i915 hangs when booting kernel 5.15.99. I found that the bug has already been reported:

I’ll be using 5.15.98 for now (tried 5.15.100 on unstable - no fix there).

Just pushed the new kernel point releases:

  • linux419 4.19.276
  • linux54 5.4.235
  • linux510 5.10.173
  • linux515 5.15.100
  • linux61 6.1.18
  • linux62 6.2.5

Question: if our issue was resolved by a fast-tracked package update (like was done today), should we change our answer to the poll? Since it was an issue with the update, but is no longer.

I noticed a new warning:

WARNING: consolefont: no font found in configuration

Is that expected or something out of ordinary?

Doesn’t work for me as My Broadcom wifi adaptor is not working with these new releases.
I’m using Linux510-LTS kernel (Can’t upgrade because of old legacy NVidia driver 340.108)
Same with Linux54-LTS

Found this on Arch Forum:


How to understand a patch works

Most likely the developers doing the kernel work won’t get the info at all. Lets take a look at the patch header:

author	John Harrison <John.C.Harrison@Intel.com>	2023-02-15 17:11:01 -0800
committer	Greg Kroah-Hartman <gregkh@linuxfoundation.org>	2023-03-10 09:40:14 +0100
commit	4eb6789f9177a5fdb90e1b7cdd4b069d1fb9ce45 (patch)
tree	7f0259b02632bf92193b3b5aa5c45d6f0fa3ebdd
parent	64bcaffa2d5c88ddfe12d6019ad58986bd0e314c (diff)
download	linux-4eb6789f9177a5fdb90e1b7cdd4b069d1fb9ce45.tar.gz
drm/i915: Don't use BAR mappings for ring buffers with LLC
commit 85636167e3206c3fbd52254fc432991cc4e90194 upstream.

Direction from hardware is that ring buffers should never be mapped
via the BAR on systems with LLC. There are too many caching pitfalls
due to the way BAR accesses are routed. So it is safest to just not
use it.

Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Fixes: 9d80841ea4c9 ("drm/i915: Allow ringbuffers to be bound anywhere")
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Cc: <stable@vger.kernel.org> # v4.9+

We know that there was an author by Intel John Harrison doing the patch. If we look at the last CC we see that patch should be added to all kernels starting with 4.9 kernel. So most likely you might have similar issues with higher and lower kernel series than your used 5.15 series if the same patch gets applied there also. You can check that here @stasadev: kernel/git/stable/stable-queue.git - Linux kernel stable patch queue. More or less higher than 6.2.2 might also not work on your end: 6.2.3 « releases - kernel/git/stable/stable-queue.git - Linux kernel stable patch queue. So test that by checking which kernels we provide.

So check other kernel series if they also don’t boot as you still have 5.15.98 as your fallback one.

If it is true, simply check if other kernel series are affected too by this.

How to report properly

The first thing you can do is to add a confirm report similar as you have found already here [i915]drm:add_taint_for_CI [i915]] CI tainted:0x9 by intel_gt_init+0xae/0x2d0 [i915] (#8284) · Issues · drm / intel · GitLab by adding your own details of hardware and maybe the dmesg log of the 5.15.99 and 5.15.98 of your own system additionally to the already reported one.

Next step is simply to summarize the issue in an email and sent that to upstream. Which emails? Well you have all what you need in the patch itself. Simply send them to the email addresses exactly as given. Also include the stable@vger.kernel.org and intel-gfx@lists.freedesktop.org mailing lists, as some developers still work on email.

What I think personally

Well, most likely it also can be a missing patch within the 5.15 kernel series. For example I see this in all the other kernel series when the patch is applied, except 5.15, even it is tacked to be included: drm-i915-don-t-use-stolen-memory-for-ring-buffers-with-llc.patch « 6.2.3 « releases - kernel/git/stable/stable-queue.git - Linux kernel stable patch queue So test as recommended other kernel series and see if they work for you.

What Manjaro can do

We might revert the patch as of now and follow up with upstream.


Thanks. However, I’m not sure if I understand it. I don’t see any depreciated hooks in my case. And oh, this is a topic from 2012… so I’m not sure how relevant it is.

Here is mine grub file in/etc/default/ :

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash loglevel=3 udev.log_priority=3 vt.global_cursor_default=0 resume=/dev/sda4 resume_offset=1363968"
GRUB_CMDLINE_LINUX="rhgb quiet mitigations=off"

# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.

# Uncomment to disable submenus in boot menu

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable booting from LUKS encrypted devices

# Uncomment to use basic console

# Uncomment to disable graphical terminal

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'

# Uncomment to allow the kernel use the same resolution used by grub

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter 
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx" 

# Uncomment to disable generation of recovery mode menu entries

# Uncomment this option to enable os-prober execution in the grub-mkconfig command

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper 
# modes only.  Entries specified as foreground/background.

# Uncomment one of them for the gfx desired, a image background or a gfxtheme

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

# Uncomment to ensure that the root filesystem is mounted read-only so that
# systemd-fsck can run the check automatically. We use 'fsck' by default, which
# needs 'rw' as boot parameter, to avoid delay in boot-time. 'fsck' needs to be
# removed from 'mkinitcpio.conf' to make 'systemd-fsck' work.
# See also Arch-Wiki: https://wiki.archlinux.org/index.php/Fsck#Boot_time_checking

sudo vim /etc/vconsole.conf


sudo cp -p /etc/mkinitcpio.conf /etc/mkinitcpio_edit_consolefont.conf;sudo vim /etc/mkinitcpio.conf

remove consolefont from hooks line

sudo mkinitcpio -P;sudo grub-mkconfig -o /boot/grub/grub.cfg

v6.2.5 fixed the wifi issue :slight_smile:

I have now a minor silly issue. Whenever I update the nvidia driver I get this (harmless) error:

(4/5) reinstalling linux62-nvidia
cat: /usr/lib/modules/extramodules-6.1-MANJARO/version: No such file or directory
depmod: ERROR: Bad version passed 
error: command failed to execute correctly

I checked in /usr/share/libalpm and the post-transaction hooks seem correct to me. I also don’t have any trace left of kernel v6.1 - as far as I can see, at least.

Where else shall I look for left-overs?