[Unstable Update] February 2024 Edition

All true.
I’ll try to refrain from using humor every now and then.

Lastly, there’s this:

Build problems don’t depend on exact make or model of any graphics card AFAIK.

1 Like

I’ll add the necessary patch. The precompiled linux6X-nvidia and linux6X-nvidia-470xx modules already include it.

3 Likes

@Yochanan ,

I think the @straycat problem’ come from the mkinitcpio.conf
I’m waiting for him to share it here that way I may help him to make some modifications and success the last updates.

Wish You well

Yes I have an older nvidia card here’s the info on that.

Graphics:
  Device-1: NVIDIA GP107 [GeForce GTX 1050] driver: nvidia v: 545.29.06
  Display: server: X.Org v: 21.1.11 driver: X: loaded: nvidia gpu: nvidia
    resolution: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: kms_swrast,nvidia,swrast
    platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 545.29.06
    renderer: NVIDIA GeForce GTX 1050/PCIe/SSE2
  API: Vulkan v: 1.3.276 drivers: nvidia surfaces: xcb,xlib

Just to add virtualbox-host-dkms also did not build.I reinstalled it and it seemed to build but I did not try virtualbox before restoring to an earlier snapshot.While I do not think mkinitcpio.conf is the issue here’s the file.

MODULES=()
BINARIES=()
FILES=()
HOOKS=(systemd autodetect modconf kms keyboard keymap sd-vconsole block filesystems fsck)

Thanks @Yochanan for the patch I will update later and check back.

1 Like

May I ask as one of those who don’t use grub… Could you please update mhwd’s dependencies removing update-grub? I don’t need grub auto-installing and adding itself to nvram. It comes with the default Manjaro ISO, okay, but it should be possible to remove it upon user discretion and not make user remove mhwd or whatnot else that would become dependent on {update-}grub in future.

Parts of mhwd need it.
Until that is fixed to use grub-mkconfig (and/or whatever else) its sorta required.
ex:

1 Like

I’d rather expect grub requiring update-grub and them mutually requiring each other. But not mwhd or some other arbitrary package containing grub-specific commands, since such commands only make sense when grub is installed and are not needed when using rEFInd or systemd-boot. Why not issue a minor update to grub with a new dependency update-grub?

That doesnt make sense in this context.
mhwd-kernel runs update-grub to finalize its actions.
Whether or not grub is installed this will fail unless update-grub is available.

While manjaro has moved away from the largely superfluous update-grub … there still exists these lines in mhwd. grub does not require update-grub in the least.

Arguably mhwd does not need to either, and arguably it should be more agnostic in general.

But right now mhwd relies explicitly on update-grub, and the dependencies now correctly reflect that.

In the future I would argue a handful of rewrites to mhwd is what should be done, culminating in it no longer using update-grub, and hence the pursuant removal of the dependency.

PS.
Also, they arent my tools, and I have no say in any of these decisions or developments.
I have mentioned before that mhwd-kernel fails to function properly if non-manjaro kernels are installed, which has never been taken as a serious flaw. And thats about where my involvement has ended. :person_shrugging:

Just updated and the new version of nvidia-dkms worked fine and both kernels installed with no issues.
Thanks very much. :smiley:

1 Like

Will there be a chance to include the Nvidia 550.40 version which supports the RTX4070Ti SUPER which is currently in beta status for Linux?

1 Like

@straycat ,

I suggest You that :

HOOKS=(systemd autodetect modconf kms keyboard sd-vconsole block filesystems fsck)

then mkinitcpio -P

Instead of : HOOKS=(systemd autodetect modconf kms keyboard keymap sd-vconsole block filesystems fsck) because keymap is already incuded in sd-vconsole.

Take a look in the Arch wiki regarding mkinitcpio

You can also use :

COMPRESSION=(zstd)
COMPRESSION_OPTIONS=(-T0)
MODULE_DECOMPRESS=(yes)

Wish You well

2 Likes

I raised the issue about the missing update-grub package at gitlab - based on an issue where a member used mhwd-kernel to update the kernel and was stuck in rescue mode because update-grub was missing.

Actually the dependency is necessary when using mhwd-kernel as this process will not update kernels if update-grub is not present.

I have been thinking the same thought … that having update-grub as dependency will pull in grub.

Perhaps changing mhwd-kernel to to check for grub and only if present either use update-grub or – as I see it more correct - use grub-mkconfig to update grub.

I don’t want this on my laptop with secure boot using efi-stub - the laptop is an Intel based system -no dGPU so I have removed mhwd completely.

1 Like

Last package upgrades are from Saturday 3.2.24
Normally in unstable there are upgrades nearly every day…?
LibreOffice-fresh 24.2.0-1 is already in arch-extra repos (since 01.02.24)
(Mirror) Problems?

It’s literally in the 2nd sentence of this thread. Maybe read before posting?

2 Likes

Ah sorry, you’re right…

2 Likes

on second thoughts, if you are as impatient as i was to check wassup with LO, you can take it off arch. beware this is only intended for LO package which “i think” is fairly isolated enough to supplant from arch without other dependencies wrecking it. any such practices on other packages can put your system in a “partial upgrade” situation. you are forewarned.

to get LO off arch;

sudo pacman -U  https://archlinux.org/packages/extra/x86_64/libreoffice-fresh/download/

Yes, it is a manual task. Depending what packages are included in the sync, we may need to update or rebuild some of our overlays and/or our own packages.

Sorry, missed your question earlier.

1 Like

Due to this even unstable branch is still affected by the last glibc vulnerability CVE-2023-6246 (Local Privilege Escalation, from any unprivileged user to full root):
https://www.qualys.com/2024/01/30/cve-2023-6246/syslog.txt
I’ve rolled out Arch’s fixed packages 2.38-8 on my systems last week (2024-02-02) but they’ve moved on to 2.39-1 since.
Manjaro is is still affected across all branches with version 2.38-7.

edit:

24-01-30: Coordinated Release Date (18:00 UTC).

4 Likes

When this surfaced however long ago, I tried and could repeat its findings for anyone who wants to know. :wink:

+1. from what i remember moving to 2.38-8 only required *gcc-libs* rebuilt package in my case. however moving to 2.39-1 effectively requires rebuilt packages of everything from kernels on it, so stopped short f it.