View Issue Details

IDProjectCategoryView StatusLast Update
0004966Kali Linux[All Projects] Kali Package Bugpublic2018-10-12 17:28
ReporterMichael JAssigned Tosteev 
PrioritynormalSeverityminorReproducibilityhave not tried
Status assignedResolutionopen 
Product Version2018.3 
Target VersionFixed in Version 
Summary0004966: Raspberry Pi 3 / kali arm / apt-get upgrade - Errors were encountered while processing: raspi3-firmware
DescriptionWhen I do a apt-get upgrade I get this error --

###
The following packages have been kept back:
  libargon2-0 libcryptsetup12 libfile-mimeinfo-perl
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]

after that

Setting up raspi3-firmware (1.20180619-1) ...
Error: missing /boot/firmware, did you forget to mount it?
dpkg: error processing package raspi3-firmware (--configure):
 installed raspi3-firmware package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 raspi3-firmware
E: Sub-process /usr/bin/dpkg returned an error code (1)
####

Not sure how to fix it..

Activities

Michael J

Michael J

2018-09-09 08:29

reporter   ~0009617

I reproduced the error today

Format SD Card 32Gb Sony Class 10
>> SD Card Formater

Burn SD Card
>> Win32diskImager
kali-linux-2018.3-rpi3-nexmon.img

Boot
>> No Problem

Gparted
>>Available space on ext4 28Gb

Update: "In terminal"
>>apt-get update (No Problem)

Upgrade "In Terminal"
>>apt-get upgrade

Same error as described..

--

Next test..
>>apt-get update (No problem)

>>apt-get install kali-linux-full (no problem)

>>apt-get upgrade (same problem)
amo

amo

2018-09-09 21:04

reporter   ~0009618

I think this error explains your problem:

Error: missing /boot/firmware, did you forget to mount it?

Run the command:
 
mount | grep /boot

You should see something similar:

/dev/mmcblk0p1 on /boot (..snipped..)

If you don't see anything, mount the boot partition and run the upgrade command again:

mount /dev/mmcblk0p1 /boot
apt-get upgrade
Betyar

Betyar

2018-09-10 06:46

reporter   ~0009620

every time i try to upgrade i had the same problem
amo is this solve the problem?
Betyar

Betyar

2018-09-12 08:37

reporter   ~0009701

any solutions ?
Michael J

Michael J

2018-09-13 05:51

reporter   ~0009709

Didn't solve it..

###
>>mount | grep /boot
/dev/mmcblk0p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)

>>mount /dev/mmcblk0p1 /boot
mount: /boot: /dev/mmcblk0p1 already mounted on /boot

>>apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  libfile-mimeinfo-perl
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up raspi3-firmware (1.20180619-1) ...
Error: missing /boot/firmware, did you forget to mount it?
dpkg: error processing package raspi3-firmware (--configure):
 installed raspi3-firmware package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 raspi3-firmware
E: Sub-process /usr/bin/dpkg returned an error code (1)
####
Betyar

Betyar

2018-09-13 06:31

reporter   ~0009710

same with me or if i dind't get this firmware error the upgrade corrupt the filesystem
i don't know why we both just talking and the supports why won't help?
steev

steev

2018-09-13 16:52

developer   ~0009719

The error comes because of a change made in the 2018.3 release to use the Debian package for the firmware. Unfortunately, there was never an update during the process of adding it so I never ran into the issue before release.

There is a workaround, to at least get rid of the error.

You'll want to add the following to /etc/fstab:

tmpfs /boot/firmware tmpfs rw 0 0

At the bottom, and then simply run "mount /boot/firmware" (or reboot) and re-run the update.

This allows the package to update, which is good, but does not copy the new files into place.

Debian uses a different mounting layout than we do, and their check is for /boot/firmware to be mounted, instead of just /boot.

Once the update succeeds, you will want to

cp /usr/lib/raspi3-firmware/* /boot/

to use the new firmware.

I'm still working out a better long term solution.
Betyar

Betyar

2018-09-14 06:46

reporter   ~0009723

thank you for the reply if i finished at work i try it
Michael J

Michael J

2018-09-15 06:25

reporter   ~0009727

Thanks for the work around..

I tried the solution on a new install and there it worked like a charm...

 I'm not sure if it would work after an rpi-firmware upgrade but for now I can live with this solution.

So again, THANKS
steev

steev

2018-10-12 17:28

developer   ~0009812

The solution sticks around if you added the tmpfs one to /etc/fstab - otherwise, next time there's an upgrade, you'll have to do it again.

I still haven't worked out a good lasting solution yet, unfortunately, aside from going back to manually updating the firmware, but still trying to figure out the best path forward.

Issue History

Date Modified Username Field Change
2018-09-08 18:51 Michael J New Issue
2018-09-09 08:29 Michael J Note Added: 0009617
2018-09-09 21:04 amo Note Added: 0009618
2018-09-10 06:46 Betyar Note Added: 0009620
2018-09-12 08:37 Betyar Note Added: 0009701
2018-09-13 05:51 Michael J Note Added: 0009709
2018-09-13 06:31 Betyar Note Added: 0009710
2018-09-13 16:52 steev Note Added: 0009719
2018-09-13 16:53 steev Assigned To => steev
2018-09-13 16:53 steev Status new => assigned
2018-09-14 06:46 Betyar Note Added: 0009723
2018-09-15 06:25 Michael J Note Added: 0009727
2018-10-12 17:28 steev Note Added: 0009812