Radeon firmware actualization problem

This forum is dedicated to basic help and support :

Ask here your questions about basic installation and usage of Mageia. For example you may post here all your questions about getting Mageia isos and installing it, configuring your printer, using your word processor etc.

Try to ask your questions in the right sub-forum with as much details as you can gather. the more precise the question will be, the more likely you are to get a useful answer

Radeon firmware actualization problem

Postby hemm » Nov 27th, '21, 15:19

Seven days ago, actualization of radeon-firmware don't finish.
The error is:
package radeon-firmware-20211112-1.mga8.nonfree.noarch does not verify: Payload SHA256 ALT digest: BAD (Expected 81492d0a407d20399aeb284c469f84eadffb7d63071ec734bc0be2842dd06010 != 69f7bab55fe5e92eadcbc2b5c97224a623a6cf3b18642adacb6bc40a9348216d)
hemm
 
Posts: 2
Joined: Nov 27th, '21, 15:16

Re: Radeon firmware actualization problem

Postby sturmvogel » Nov 27th, '21, 17:03

Issue following command as root to clear you cache:
Code: Select all
urpmi --clean


Try to update again.
If it won't work: remove your set of repositorys and add a new set. After that issue following command again and update afterwards:
Code: Select all
urpmi --clean
sturmvogel
 
Posts: 678
Joined: Jul 30th, '12, 00:39

Re: Radeon firmware actualization problem

Postby hemm » Nov 27th, '21, 17:49

Corrected
Thanks!
hemm
 
Posts: 2
Joined: Nov 27th, '21, 15:16

Re: Radeon firmware actualization problem

Postby doktor5000 » Nov 27th, '21, 19:02

Please don't forget to mark the thread as solved, by editing the subject of the first post and prefix it with [SOLVED], thanks in advance.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17629
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Radeon firmware actualization problem

Postby benmc » Nov 29th, '21, 10:15

if the package is a single failure of a massive group update, you could save some bandwidth / download time by just removing the defective package rather than completely emptying the download cache. I am on slow ADSL. :(
changing of the mirror can be performed before or after package removal.
as root:
Code: Select all
rm  /var/cache/urpmi/rpms/name_of_package

then
Code: Select all
urpmi --auto update

care should be taken to ensure the correct name_of_package is entered !
at completion, run
Code: Select all
urpmi --clean
just in case some packages have been updated between the failure and completion of the update, and are left in the cache.
benmc
 
Posts: 1175
Joined: Sep 2nd, '11, 12:45
Location: Pirongia, New Zealand


Return to Basic support

Who is online

Users browsing this forum: No registered users and 1 guest

cron