[SOLVED] Apt is broken and I can't figure out how to fix it
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Trying to upgrade as you see will tell me there's unmet dependencies and to try --fix-broken, trying that results in dpkg returning an error code (1).
I've tried deleting the mentioned packages in /var/cache/apt/archives/ and doing all that apt clean and dpkg --configure -a stuff that every search result tells me to do. Nothing works.
I'm no expert, but it looks like the xanmod kernel and some firmware packages are having a fight. I've got no idea how to fix it though.
I installed xanmod quite a long time ago and I know apt has been working fine up until now.
Location: as far S and E as I want to go in the U.S.
Distribution: Fossapup64
Posts: 224
Rep:
First of all, which kernel is in usage?
Code:
uname -a
Second, are the commands issued as root? or is sudo being used? Do you know the difference?
Your pastebin shows
Code:
firmware-linux : Depends: firmware-linux-free but it is not installed
firmware-linux-nonfree : Depends: firmware-misc-nonfree (= 20210208-2) but it is not installed
Depends: firmware-amd-graphics (= 20210208-2) but it is not installed
and command(s) issued are incorrect (remember that linux assumes user knows exactly what he is doing)
Tell us what kernel is used and we'll go from there.
But if the kernel is not the problem, install the dependencies first beginning with
Conflicting packages are linux-firmware and firmware-linux-free linux-firmware and firmware-misc-nonfree linux-firmware and firmware-amd-graphics
linux-firmware is the standard Ubuntu package. This commit tells me that it's also part of Pop!_OS. OTOH, firmware-* packages probably come from Debian.
Second, are the commands issued as root? or is sudo being used? Do you know the difference?
Linux pop-os 5.10.21-xanmod1 #0~git20210307.35fa437 SMP PREEMPT Sun Mar 7 15:26:50 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Quote:
Your pastebin shows
Code:
firmware-linux : Depends: firmware-linux-free but it is not installed
firmware-linux-nonfree : Depends: firmware-misc-nonfree (= 20210208-2) but it is not installed
Depends: firmware-amd-graphics (= 20210208-2) but it is not installed
and command(s) issued are incorrect (remember that linux assumes user knows exactly what he is doing)
Tell us what kernel is used and we'll go from there.
But if the kernel is not the problem, install the dependencies first beginning with
Conflicting packages are linux-firmware and firmware-linux-free linux-firmware and firmware-misc-nonfree linux-firmware and firmware-amd-graphics
linux-firmware is the standard Ubuntu package. This commit tells me that it's also part of Pop!_OS. OTOH, firmware-* packages probably come from Debian.
Try this
Code:
sudo apt purge firmware-linux
Code:
james@pop-os:~$ sudo apt purge firmware-linux
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
firmware-linux-nonfree : Depends: firmware-misc-nonfree (= 20210208-2) but it is not going to be installed
Depends: firmware-amd-graphics (= 20210208-2) but it is not going to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
james@pop-os:~$
No red text appeared for that command. But trying apt upgrade produces a ton of "Possible missing firmware" messages and it ends with a dpkg error code (1).
I noticed all the old kernel versions that it wanted to remove and I had got a message that /boot was full. Using autoremove halved the size of /boot and apt began working as normal again. Thank you for the help!
Last edited by TheJooomes; 03-13-2021 at 01:35 PM.
Well, RX 560 is a renewed Polaris 11. Polaris 11 firmware wasn't reported as missing. I guess it's provided by the package linux-firmware. Check it with
Well, RX 560 is a renewed Polaris 11. Polaris 11 firmware wasn't reported as missing. I guess it's provided by the package linux-firmware. Check it with
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
