Open nevyn opened 6 years ago
I solved this by removing all the kernels, then installing the newest one. At least, that's what my rather flaky memory tells me. It was a scary time, no rebooting the system while it was in progress!
On 2 July 2018 at 04:13, Nevyn Bengtsson notifications@github.com wrote:
At some point where I didn't notice, I lost the ability to install packages. Maybe I did a apt update upgrade? I'm also not good enough at debian packaging to really understand what's going on. Here's the first time I noticed the problem today:
Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: arandr : Depends: python-gtk2 but it is not going to be installed linux-image-generic-hwe-16.04 : Depends: amd64-microcode but it is not going to be installed linux-signed-image-generic-hwe-16.04 : Depends: amd64-microcode but it is not going to be installed
I followed advice on the internet and got this far:
! ~ sudo apt-get install -f Sun 01 Jul 2018 07:56:41 PM CEST Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: amd64-microcode The following NEW packages will be installed: amd64-microcode 0 upgraded, 1 newly installed, 0 to remove and 44 not upgraded. 92 not fully installed or removed. Need to get 0 B/32.9 kB of archives. After this operation, 75.8 kB of additional disk space will be used. Do you want to continue? [Y/n] debconf: unable to initialize frontend: Dialog debconf: (Dialog frontend requires a screen at least 13 lines tall and 31 columns wide.) debconf: falling back to frontend: Readline (Reading database ... 257820 files and directories currently installed.) Preparing to unpack .../amd64-microcode_3.20180524.1~ubuntu0.16.04.1_amd64.deb ... Unpacking amd64-microcode (3.20180524.1~ubuntu0.16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/amd64-microcode_3.20180524.1~ubuntu0.16.04.1_amd64.deb (--unpack): trying to overwrite '/lib/firmware/amd-ucode/microcode_amd_fam15h.bin', which is also in package linux-firmware 1.999.2-gpdpocket Errors were encountered while processing: /var/cache/apt/archives/amd64-microcode_3.20180524.1~ubuntu0.16.04.1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1)
I read linux-firmware 1.999.2-gpdpocket and its conflicting with the amd64 thing, and figured it might be related to the GPD-specific packaging of ubuntu. Please help?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/nexus511/gpd-ubuntu-packages/issues/53, or mute the thread https://github.com/notifications/unsubscribe-auth/AM84bHFKooCJ6Wx1su9SnpV_nbqQwHJRks5uCRFFgaJpZM4U-ai- .
--
"I and the public know what all schoolchildren learn Those to whom evil is done Do evil in return" W.H. Auden, "September 1, 1939"
@stephen-hocking that sounds scary :S but I'll try it... which kernel did you install? Or how do I find which one to install? Thanks!!!
I think it came about when I did a do-release-upgrade to 18.04, or shortly thereafter. Interestingly, the latest stock kernel from ubuntu seems to work fine on the box.
On 2 July 2018 at 17:58, Nevyn Bengtsson notifications@github.com wrote:
@stephen-hocking https://github.com/stephen-hocking that sounds scary :S but I'll try it... which kernel did you install? Or how do I find which one to install? Thanks!!!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nexus511/gpd-ubuntu-packages/issues/53#issuecomment-401703020, or mute the thread https://github.com/notifications/unsubscribe-auth/AM84bIeb4aghdzSNI8dv4C0DuO1Uwjnrks5uCdKmgaJpZM4U-ai- .
--
"I and the public know what all schoolchildren learn Those to whom evil is done Do evil in return" W.H. Auden, "September 1, 1939"
At some point where I didn't notice, I lost the ability to install packages. Maybe I did a
apt update upgrade
? I'm also not good enough at debian packaging to really understand what's going on. Here's the first time I noticed the problem today:I followed advice on the internet and got this far:
I read
linux-firmware 1.999.2-gpdpocket
and its conflicting with the amd64 thing, and figured it might be related to the GPD-specific packaging of ubuntu. Please help?