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

It’s a variant of the same.
A different method - to access the mirrors which are fastest and closest to your location.

… not even the wiki?
mkay
… then don’t (trust) and don’t just try - figure it out yourself :man_shrugging:

Sarcasm is the lowest form of wit and your updates are not appreciated. Just answer the question would suffice???

… I noticed that, believe it or not

I did.
If the answer was somehow unclear,
use some more words to ask for clarification.

It’s all I could muster at this time.
Perhaps I’m just not a very witty person? …
Not sorry for it though.



addition for clarification from my side - and I mentioned this in my post already:

these are two commands, one after another, separated by &&
the second will only run when the first has completed without error

  • first command updates the mirrors
  • second then does the update, using the updated mirrors
1 Like

The number — as an argument to the -f option of pacman-mirrors — limits the number of mirrors to be checked to the number specified.

These mirrors all do however by default come from the worldwide pool. By supplying --continent, you are restricting the mirror list to only the mirrors on the continent where you reside (as per your time zone), or a continent of choice supplied as an argument to that option.

All commands in a UNIX system have a man page. In this case, see… :point_down:

man pacman-mirrors

If you are not familiar with how to navigate man pages, you can use the arrow keys and/or PgUp/PgDn, and q for exiting the pager.

2 Likes

Perhaps the wiki page will be beneficial:

Interestingly, the wiki example uses the 5 quantifier. This isn’t used much in practice, as most might prefer a greater amount of mirrors to be included when the sort takes place;

Generally, just using sudo pacman-mirrors --fasttrack (without the quantifier) will sort available mirrors; and, as mentioned earlier, sudo pacman-mirrors --continent is often preferred, depending upon which continent one happens to reside on.

1 Like

you are too kind :grinning:

thank you, though

I got the following messages related to the above command which is the same as I had before.

 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)
:: 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

Thanks

these are actually two commands - one after the other
sudo pacman-mirrors --continent
is the first
sudo pacman -Syu
is the second

Did you follow the Manjaro wiki procedure to change the Manjaro branch that you are using?

… details are in your other posts …

I’m tired of
figuratively and actually
blaming user mistake on distro config mistake

This is the command I issued first as directed which completed sucessfully.

sudo pacman-mirrors --api --set-branch testing

I know.
This is the first step.
In the wiki as well.

… and what was the next step?

What did you do?

What did it say in response?

Where does a problem arise?

Are we perhaps in Kindergarten here?

2 Likes

It is pretty strange. Did you actually force refresh the database after switching the branch? I am on the testing branch myself, but I didn’t get such a conflict.

sudo pacman -Syy
# and then:
sudo pacman -Syuu

Double y means force refresh and double u means also downgrade if necessary,

You can also ignore it for now by adding

--ignore ppp,networkmanager-l2tp,networkmanager-pptp

for example, after the parameters.

1 Like

… he didn’t yet successfully change branch - it’s where he is kind of stuck at still
and we as well )

1 Like

Let’s take a ‘pot shot’ that might help, shall we?

The process of changing to the testing branch can usually be achieved with the following commands (as can be found in the Switching Branches wiki article ‘Changing to another branch’);


The recommended series of commands:


1. Change to the testing branch:

sudo pacman-mirrors --api --set-branch testing

2. Rebuild the mirrorlist:

sudo pacman-mirrors --fasttrack

3. Perform a full system update:
This allows your system to fully sync with the testing branch.

sudo pacman -Syu

However you seem to be having difficulty with dependencies, so I might suggest a slight deviation from the norm; :eyes:


A suggested series of commands:


1. Change to the testing branch:

sudo pacman-mirrors --api --set-branch testing

2. Rebuild the mirrorlist:
This time we limit mirrors to those available to your continent (optional).

sudo pacman-mirrors --continent

3. Perform a full system update:
This allows your system to fully sync with the testing branch.

sudo pacman -Syyuu

Notice the change in the update command. :eyes:
This variation allows downgrading packages (as needed) and may be helpful to resolve your dependency issues in the process.


I note that most of this information has already been given (in varying shapes and forms) by other Members.

This post basically consolidates that into a more coherent and readable format.

I trust it may be useful. :cowboy_hat_face:

Regards.


See also:


3 Likes

I want to document what out I get from each command as I run so there can be no misunderstanding.

Also I Software Manager is telling me I have 68 updates that are waiting to be installed which I assume is linked to at least one of the commands I issued yesterday. What do I do about the 68 updates?

Command 1

sudo pacman-mirrors --api --set-branch testing                                                                              
[sudo] password for raymond: 
::INFO Branch in config is changed
::INFO Downloading mirrors from Manjaro
::INFO => Mirror pool: https://repo.manjaro.org/mirrors.json
::INFO => Mirror status: https://repo.manjaro.org/status.json
::INFO Using custom mirror file
::INFO Querying mirrors - This may take some time
  0.246 Austria        : https://mirror.easyname.at/manjaro/
  0.209 Austria        : https://mirror.alwyzon.net/manjaro/
  0.485 Belarus        : http://mirror.datacenter.by/pub/mirrors/manjaro/
  0.147 Belgium        : https://mirror.futureweb.be/manjaro/
  0.388 Bulgaria       : https://mirror.telepoint.bg/manjaro/
  0.569 Bulgaria       : https://manjaro.ipacct.com/manjaro/
  0.478 Czechia        : https://mirror.dkm.cz/manjaro/
  0.459 Czechia        : https://mirrors.nic.cz/manjaro/
  0.773 Czechia        : https://mirror.it4i.cz/manjaro/
  0.356 Denmark        : https://mirrors.dotsrc.org/manjaro/
  0.111 France         : https://mirrors.eric.ovh/manjaro/
  0.136 France         : http://ftp.free.org/mirrors/repo.manjaro.org/repos/
  0.232 France         : https://mirror.ibakerserver.pt/manjaro/
  ..... France         : https://manjaro.ynh.ovh/

::ERROR Connection: HTTPSConnectionPool(host='manjaro.ynh.ovh', port=443): Max retries exceeded with url: /testing/core/x86_64/core.db.tar.gz (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x705176757770>: Failed to establish a new connection: [Errno 111] Connection refused'))

  0.328 Germany        : https://mirror.alpix.eu/manjaro/
  0.372 Germany        : https://ftp.gwdg.de/pub/linux/manjaro/
  0.405 Germany        : https://mirror.23m.com/manjaro/
  0.192 Germany        : https://ftp.halifax.rwth-aachen.de/manjaro/
  0.246 Germany        : http://ftp.tu-chemnitz.de/pub/linux/manjaro/
  0.205 Germany        : https://mirror.netcologne.de/manjaro/
  ..... Germany        : http://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/

::ERROR Connection: HTTPConnectionPool(host='ftp.rz.tu-bs.de', port=80): Read timed out.

  0.548 Greece         : https://fosszone.csd.auth.gr/manjaro/
  1.619 Greece         : https://ftp.cc.uoc.gr/mirrors/linux/manjaro/
  0.509 Hungary        : https://quantum-mirror.hu/mirrors/pub/manjaro/
  0.371 Italy          : https://manjaro.mirror.garr.it/manjaro/
  0.480 Italy          : https://ba.mirror.garr.it/mirrors/manjaro/
  0.483 Italy          : https://ct.mirror.garr.it/mirrors/manjaro/
  0.234 Netherlands    : https://manjaro.mirror.wearetriple.com/
  0.600 Netherlands    : https://manjaro.mirrors.lavatech.top/
  0.255 Netherlands    : http://ftp.snt.utwente.nl/pub/linux/manjaro/
  0.231 Netherlands    : https://mirror.koddos.net/manjaro/
  0.176 Netherlands    : https://mirror.bouwhuis.network/manjaro/
  0.419 Poland         : https://ftp.psnc.pl/linux/manjaro/
  0.503 Portugal       : https://mirror.leitecastro.com/manjaro/
  0.373 Russia         : https://mirror.yandex.ru/mirrors/manjaro/
  1.495 Russia         : https://mirror.kamtv.ru/manjaro/
  0.952 Russia         : https://mirror.truenetwork.ru/manjaro/
  0.399 Serbia         : https://mirror1.sox.rs/manjaro/
  0.317 Spain          : https://mirror.raiolanetworks.com/manjaro/
  0.675 Spain          : https://ftp.caliu.cat/pub/distribucions/manjaro/
  0.258 Sweden         : https://ftp.lysator.liu.se/pub/manjaro/
  0.565 Sweden         : https://mirror.zetup.net/manjaro/
  0.566 Sweden         : https://ftpmirror1.infania.net/mirror/manjaro/
  0.188 Switzerland    : https://mirror.init7.net/manjaro/
  0.217 Switzerland    : https://ipng.mm.fcix.net/manjaro/
  0.421 Ukraine        : https://fastmirror.pp.ua/manjaro/
  0.393 Ukraine        : https://mirror.hostiko.network/manjaro/
  0.097 United_Kingdom : https://www.mirrorservice.org/sites/repo.manjaro.org/repos/
  0.100 United_Kingdom : http://manjaro.mirrors.uk2.net/
  0.119 United_Kingdom : https://mirror.vinehost.net/manjaro/
  0.135 United_Kingdom : https://ask4.mm.fcix.net/manjaro/
::INFO Writing mirror list
::United_Kingdom  : https://www.mirrorservice.org/sites/repo.manjaro.org/repos/testing/$repo/$arch
::United_Kingdom  : http://manjaro.mirrors.uk2.net/testing/$repo/$arch
::France          : https://mirrors.eric.ovh/manjaro/testing/$repo/$arch
::United_Kingdom  : https://mirror.vinehost.net/manjaro/testing/$repo/$arch
::United_Kingdom  : https://ask4.mm.fcix.net/manjaro/testing/$repo/$arch
::France          : http://ftp.free.org/mirrors/repo.manjaro.org/repos/testing/$repo/$arch
::Belgium         : https://mirror.futureweb.be/manjaro/testing/$repo/$arch
::Netherlands     : https://mirror.bouwhuis.network/manjaro/testing/$repo/$arch
::Switzerland     : https://mirror.init7.net/manjaro/testing/$repo/$arch
::Germany         : https://ftp.halifax.rwth-aachen.de/manjaro/testing/$repo/$arch
::Germany         : https://mirror.netcologne.de/manjaro/testing/$repo/$arch
::Austria         : https://mirror.alwyzon.net/manjaro/testing/$repo/$arch
::Switzerland     : https://ipng.mm.fcix.net/manjaro/testing/$repo/$arch
::Netherlands     : https://mirror.koddos.net/manjaro/testing/$repo/$arch
::France          : https://mirror.ibakerserver.pt/manjaro/testing/$repo/$arch
::Netherlands     : https://manjaro.mirror.wearetriple.com/testing/$repo/$arch
::Austria         : https://mirror.easyname.at/manjaro/testing/$repo/$arch
::Germany         : http://ftp.tu-chemnitz.de/pub/linux/manjaro/testing/$repo/$arch
::Netherlands     : http://ftp.snt.utwente.nl/pub/linux/manjaro/testing/$repo/$arch
::Sweden          : https://ftp.lysator.liu.se/pub/manjaro/testing/$repo/$arch
::Spain           : https://mirror.raiolanetworks.com/manjaro/testing/$repo/$arch
::Germany         : https://mirror.alpix.eu/manjaro/testing/$repo/$arch
::Denmark         : https://mirrors.dotsrc.org/manjaro/testing/$repo/$arch
::Italy           : https://manjaro.mirror.garr.it/manjaro/testing/$repo/$arch
::Germany         : https://ftp.gwdg.de/pub/linux/manjaro/testing/$repo/$arch
::Russia          : https://mirror.yandex.ru/mirrors/manjaro/testing/$repo/$arch
::Bulgaria        : https://mirror.telepoint.bg/manjaro/testing/$repo/$arch
::Ukraine         : https://mirror.hostiko.network/manjaro/testing/$repo/$arch
::Serbia          : https://mirror1.sox.rs/manjaro/testing/$repo/$arch
::Germany         : https://mirror.23m.com/manjaro/testing/$repo/$arch
::Poland          : https://ftp.psnc.pl/linux/manjaro/testing/$repo/$arch
::Ukraine         : https://fastmirror.pp.ua/manjaro/testing/$repo/$arch
::Czechia         : https://mirrors.nic.cz/manjaro/testing/$repo/$arch
::Czechia         : https://mirror.dkm.cz/manjaro/testing/$repo/$arch
::Italy           : https://ba.mirror.garr.it/mirrors/manjaro/testing/$repo/$arch
::Italy           : https://ct.mirror.garr.it/mirrors/manjaro/testing/$repo/$arch
::Belarus         : http://mirror.datacenter.by/pub/mirrors/manjaro/testing/$repo/$arch
::Portugal        : https://mirror.leitecastro.com/manjaro/testing/$repo/$arch
::Hungary         : https://quantum-mirror.hu/mirrors/pub/manjaro/testing/$repo/$arch
::Greece          : https://fosszone.csd.auth.gr/manjaro/testing/$repo/$arch
::Sweden          : https://mirror.zetup.net/manjaro/testing/$repo/$arch
::Sweden          : https://ftpmirror1.infania.net/mirror/manjaro/testing/$repo/$arch
::Bulgaria        : https://manjaro.ipacct.com/manjaro/testing/$repo/$arch
::Netherlands     : https://manjaro.mirrors.lavatech.top/testing/$repo/$arch
::Spain           : https://ftp.caliu.cat/pub/distribucions/manjaro/testing/$repo/$arch
::Czechia         : https://mirror.it4i.cz/manjaro/testing/$repo/$arch
::Russia          : https://mirror.truenetwork.ru/manjaro/testing/$repo/$arch
::Russia          : https://mirror.kamtv.ru/manjaro/testing/$repo/$arch
::Greece          : https://ftp.cc.uoc.gr/mirrors/linux/manjaro/testing/$repo/$arch
::INFO Mirror list generated and saved to: /etc/pacman.d/mirrorlist
::INFO To reset custom mirrorlist 'sudo pacman-mirrors -id'
::INFO To remove custom config run  'sudo pacman-mirrors -c all'
https://ftp.cc.uoc.gr/mirrors/linux/manjaro/testing/$repo/$arch
::INFO Mirror list generated and saved to: /etc/pacman::INFO To reset custom mirrorlist 'sudo pacman-mirrors -id'
::INFO To remove custom config run  'sudo pacman-mirrors -c all'
.d/mirrorlist
::INFO To reset custom mirrorlist 'sudo pacman-mirrors -id'
::INFO To remove custom config run  'sudo pacman-mirrors -c all'

Mod edit:- In future please format all code and command output according to forum requirements.

I notice you’re having difficulty formatting your posts as per forum requirements. We have established guidelines in the form of tutorials, at least one of which was given to you much earlier in the this topic. Among them are instructions on how to format command output as preformatted text (a scrollable text box).

I will fix your post for you in this instance, but in future you are expected to render appropriate formatting yourself.

Here are some links that will generally help;

Remember seeing this one?


You might continue with the update command already given. Re-read my post (above) with all the commands clearly listed, numbered, and explained.

If you recall, I noted the usual commands (from the wiki) on how to switch branches - specifically, to testing.

And I also suggested an alternate series of commands; specifically, the modified pacman command intended to help with your dependency issues;

A direct link to the post with those suggested commands:

Regards.

1 Like

I have completed all three commands and rebooted with no obvious problems.

So I am on the testing branch now.

Then, your issue is solved.

The usual procedure is to mark the post that helped you the most as the Solution; this is helpful to others who might find this topic in the future.

Cheers. :partying_face:


If you find you have further issues, feel free to create a new topic in the appropriate Support category.

1 Like

Changing to Testing branch was suggested in previous so that OP could install kernel 6.13.0-1 instead of 6.13.0rc2-1 on stable branch
Branch compare - linux613

OP should have been suggested to use mhwd-kernel (or Manjaro Settings Manager GUI) instead of using pacman, but there was no data to suggest that OP would also need to install llinux613-headers and rebuild DKMS driver
(pacman was the 2nd of 9 suggested commands and probably an honest mistake)


[Testing Update] 2025-01-25 - Kernels, Deepin, Firefox, VirtualBox, Mesa

Does kernel v6.13 support Ryzen CPU and resolve errors and delays?

I cant tell. It was performing well before changing to the testing branch as I had implemented a number of the suggestions made in that issue.

My understanding was that that the testing branch had specific named support for Ryzen 9 CPU and thus would be beneficial overall. It sounds like I did not need to go this route and could have stayed on the stable branch. I had made a specific note in the other issue that boot and shutdown were performing really well taking just a few seconds most of the time.
Thanks

Switching to Testing branch was suggested to install stable version of latest kernel (6.13.0)
rather than installing Release Candidate version on Stable branch (6.13.0rc2)
Or waiting for stable version to be released on Stable branch