Trying to move to Testing Branch for Ryzen 9 Support has caused errors

I was asked to trying the testing branch to improve shutdown and boot times and get better support for my Ryzen 9 CPU.

When trying to run the last command sudo pacman -Syu linux613 I get errors on two packages. Network Manager and Nivida.


sudo pacman -Syu linux613                                                                                                   
[sudo] password for raymond: 
:: Synchronising package databases...
 core is up to date
 extra is up to date
 multilib is up to date
:: Starting full system upgrade...
:: Replace linux419 with core/linux-lts-meta? [Y/n] y
:: Replace linux419-headers with core/linux-lts-headers-meta? [Y/n] y
resolving dependencies...
looking for conflicting packages...
**error: failed to prepare transaction (could not satisfy dependencies)**
:: removing linux419 breaks dependency 'linux419' required by linux419-nvidia
:: removing linux419 breaks dependency 'linux419' required by linux419-virtualbox-host-modules
:: installing ppp (2.5.2-1) breaks dependency 'ppp=2.5.1' required by networkmanager-l2tp
:: installing ppp (2.5.2-1) breaks dependency 'ppp=2.5.1' required by networkmanager-pptp

As far as I can see, one step in the process given was missing.
An oversight, perhaps - the full process is described here:

Switching Branches - Manjaro

The missing step seems to be:
after switching branch, you need to update the mirrors,
after that you run the sync to the new branch.

eg:
sudo pacman-mirrors --fasttrack 5

then:
sudo pacman -Syu

It looks like you missed the first step of the two above.

In that guide, they combined the two commands into one line via the use of &&:

sudo pacman-mirrors --fasttrack 5 && sudo pacman -Syu


update your mirrors before you try to sync from them

3 Likes

remove linux-meta

sudo pacman -Rns linux-meta

remove all kernels except 6.12

sudo mhwd-kernel -r linux419

sudo mhwd-kernel -r linux419                                                                                             

This is the output of this command which seems to have worked:-

checking dependencies...
:: base optionally requires linux: bare metal support
:: dkms optionally requires linux-headers: build modules against the Manjaro kernel
:: r8125-dkms optionally requires linux-headers: Build the module for Arch kernel

Packages (2) linux419-4.19.325-1  linux419-headers-4.19.325-1

Total Removed Size:  167.94 MiB

:: Do you want to remove these packages? [Y/n] y
:: Running pre-transaction hooks...
(1/2) Removing linux initcpios...
(2/2) Remove DKMS modules
==> dkms remove --no-depmod r8125/9.014.01 -k 4.19.325-1-MANJARO
==> depmod 4.19.325-1-MANJARO
:: Processing package changes...
(1/2) removing linux419-headers                                                     [################################################] 100%
(2/2) removing linux419                                                             [################################################] 100%
:: Running post-transaction hooks...
(1/4) Arming ConditionNeedsUpdate...
(2/4) Updating module dependencies...
(3/4) Updating Kernel initcpios for Nvidia-DRM...
(4/4) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.12-x86_64
Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-6.12-x86_64.img
Found initrd fallback image: /boot/initramfs-6.12-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done

When I tried to reboot my system after performing the above commands my whole system would not reboot. I started the book process and got stuck on just after the message

Terminate Plymouth Boot Screen

So I used timeshift and went back to yesterdays daily backup.

So I have a lot to say about how people try and help you on this forum. There are too many people who are taking pot shots of what might help and then expecting me to respond back to various edit that are done as well to what I have put on the issue.

It is like the wild west and very unprofessional in my opinion.

I had one person tell me that I should not question why one application would not install using the standard method and then install the binary version not knowing how this would impact software updates and overall maintaining my system.

I thought Manjaro was intended as the user friendly version of Arch Linux with GUI interfaces for most regular processes so I dont need to know the command line versions upfront.

I have been given time and again command line commands not knowing what they are going to do.

I have worked in support in the Corporate world for many years including being a European Support Manager overseeing all issues for the software I was supporting.

To this end we had one routine to run to collect all the information we needed to solve a problem which would ask our customers to run and send to us.

I have been asked to run commands and then expected to edit them to just show the needed information only, without know what is important and what is not.

If I had the time I would write a routine to this myself which could be a script which ask certain questions about what the error is related to and then the routine would collect and supply the appropriate information and logs etc.

Thanks
Raymond

This is a non-solution.

This topic will ultimately be closed as it no longer serves a purpose for anyone that happens to find it.

You realise this is a Manjaro user forum, don’t you? You cannot possibly dictate that every forum user will meet your expectations of professionality.

Your opinion suggests a sense of entitlement which seems out of place; perhaps in a corporate customer service scenario this might be expected and tolerated, but in this (like so many Linux forums) you’re dealing mainly with volunteers who have donated their personal time and effort; to the extent they can.

The community is comprised of a variety of people from all walks of life; some with a solid grounding in open source software; and others without such an advantage but still willing to help wherever they can.

So, if that’s the wild west, then, so be it.

I suppose you thought wrong (you’re not the first).

The following contributed topic might surprise you:

Regards.

4 Likes

There is no reason for this thread to be closed prematurely.

Furthermore closing would not hide it from the public, so this intention is misplaced.

2 Likes

I would like to get the Ryzen 9 7900X support by going to the testing branch but obviously properly and without causing my system not to reboot.

Sorry you have had so much trouble up til this point @RaymondTheBrave

As to your notion of a common starting point for troubleshooting - we do have those.

They usually include commands such as inxi - ‘command line system information tool for console…’;

inxi -Farz

And guides that expound on those methods as well as outline other things like how to format code in the forum like this this one;

To your issue

combined with the previous steps and outcomes leads me to believe there may be conflicting/compounding issues - the *meta packages, various kernels, and as any yet unidentified problems with the system packages, support of the device under different kernels, and the state of different kernels in the different branches.

Let us first print all installed kernels;

pacman -Qsq '^linux[0-9][0-9]?[0-9]$'

Similarly let us double check on any linux-meta packages;

pacman -Qsq 'linux-meta|linux-lts-meta'

No one knows what you did and why your system didn’t / doesn’t reboot.

It could even be because of ignoring what I said above:

the process you followed to change branch …
you where missing a critical part of it

whatever …

chroot (manjaro-chroot) can almost always fix almost any … thing …

ps:

you’d have been in charge above people who actually knew what they where doing? :grimacing:

Installing Linux 6.13 is “not exactly” changing branch, so at least you mixed two things which should have better done step by step. Also, why not using mhwd-kernel to install another kernel which would automatically update a newly installed kernel with any modules currently used in your existing kernel?

I was told this by someone on the slow shutdown issue that I logged.

That is why I am calling as testing branch and it shows what commands I was asked to run. I also shows why I have said some of my things above.

Thanks Raymond

… and I have tried to make you aware that this was not a full description of the procedure,
described it in full (second post in this thread)
and linked you to the forum wiki where it is also described.

One crucial step was missing: the refreshing of the mirrors

3 Likes

Are you sure? :slight_smile:

I have done this only one time just to try it - that was some time ago.
The wiki procedure states that after switching the mirrors to the new branch, one is supposed to update them and then, after that explicit mirror list update, run a full sync.

sudo pacman-mirrors --api --set-branch {branch}

After you changed the branch, rebuild the mirrorlist and update your packages:
user $ sudo pacman-mirrors --fasttrack 5 && sudo pacman -Syu

1 Like

Though Continent is my current favourite:

sudo pacman-mirrors --continent && sudo pacman -Syu

So what commands should I actual issue and what should I do after each?

Thanks

… what is it that you struggle with when following the advice from the wiki on how to change branches? :thinking:

direct link to the relevant portion of it:

Switching Branches - Manjaro

… I reiterated the process in my post as well.

1 Like

Someone put on the issue this:-

sudo pacman-mirrors --continent && sudo pacman -Syu

without a number 5 like the other one and I should I take a backup before I go ahead etc as I dont trust you guys very much at the moment.