Can anyone help me out, I’m getting a pile of errors during update/upgrade, this is happening on both my uConsole and on an x86 computer that also has Parrot running.
The uConsole also has several lines where it says it can not connect to deb.parrot.sh and spits out an IP, which is odd because it connects to the same IP address for some other things.
The downloads of Debian and Kali for uconsole claim they are broken, I haven’t looked into that yet (Etcher, Rufus, and 7zip throw an error trying to decompress the xz archive). I’ll get back to those later with peazip and see if they extract. And yes I know, neither Rufus nor Etcher require extracting to an image first, but when they throw errors, sometimes it works after extraction.
Back to the problem, I feel there may be a repo list problem and I’m not sure what to change and certainly can’t remember how to update the public key. Seems like Parrot is just having a problem lately. Attached image with the errors from x86.
[edit] the x86 works, but the really odd part is that I downloaded and installed this after the date listed in the blog post. Now I need to get out the uconsole and see if this might fix some of the issues I was having with the tftp software.
[edit 2] yes that worked on the uconsole as well, upgrading now. Did a parrot-upgrade this time and it seems to be upgrading more things, or it was just that far behind.
I really wish the error message would have been something like, “hey stupid, you need to go back to the distro and update your keys”, or something else that could have got me there a few days ago. Even the gui package manager should have been able to give me something, but it gave even less information. I think this is one case that would just turn a lot of people off of Linux permanently, certainly has troubled me a few times throughout the years.
Currently having issues when trying to install sudo apt install sdrpp
It shows
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libasound2-dev : Depends: libasound2 (= 1.2.8-1+b1) but 1.2.8-1+rpt1 is to be installed
E: Unable to correct problems, you have held broken packages.
My repo is already added to parrot os. Parrot os can’t correct the problem because of a package that is not available to parrot or parrot has it’s own different package. You can try adding the rpi repos to parrot and see if you can install it then or download it from the package from the debian repos.
Thank man, I added the rpi repos but get same error. I was going to remove libasound2 but it gives me a large list of packages it would remove along with it. I thought maybe re-installing libasound2 might be ok but maybe your last suggestion is best eh?
Well replacing packages can cause problem but the worst outcome is you have to reflash. I compiled and packaged sdrpp for bookworm so on anything else YMMV.
Does anyone else have the issue where the screen brightness randomly switches to low ? But like not only from high to low, but even from 50% switches back to a lower value. Didn’t quite figure out if somethings triggers it or not … but so far, it happens even when absolutely nothing is running.
Everything works with Parrot on my uConsole except when you boot it, it does not automatically connect to my WiFi network, I have to do it manually but if I plug in a USB WiFi it finds it on boot and automatically connects. Is this a common problem?
Hi @Rex - Thank you for your efforts in getting this image working for CM5. I’m running into a weird issue and would appreciate any help!
I flashed the latest Parrot Security image to my uConsole running on a CM5, and it worked fine for a couple of sessions. Then I updated Wifi details using raspi config, and upon next reboot the device booted onto a blank screen.
I had to remove batteries to turn it off, and subsequent reboots resulted in same issue.
I then tried with another SD card running your latest bookworm image, and it landed on blank screen as well. When I connected to monitor using HDMI, it complained about unable to read SD card.
Now, the device is not powering on and am worried if it could be a hardware failure. I tried booting into emergency and rescue targets, which did not help either.