Raspberry Pi 4 doesnt boot after apt full-upgrade
Raspberry Pi 4 v1.2 4GB
Steps to reproduce bug:
1. Install latest image 32bits recommended from Pi imager 1.3 , from zero.
2. run sudo apt update && sudo apt full-upgrade -y
Result intermmitent booting.
Official power supply, tested various sd cards, latest critical firmware (and latest stable too).
Bug dont occurs with original image (without update) or other distros and 64 bits.
Steps to reproduce bug:
1. Install latest image 32bits recommended from Pi imager 1.3 , from zero.
2. run sudo apt update && sudo apt full-upgrade -y
Result intermmitent booting.
Official power supply, tested various sd cards, latest critical firmware (and latest stable too).
Bug dont occurs with original image (without update) or other distros and 64 bits.
Last edited by melqui on Mon Aug 17, 2020 11:58 am, edited 2 times in total.
- HawaiianPi
- Posts: 6126
- Joined: Mon Apr 08, 2013 4:53 am
- Location: Aloha, Oregon USA
Re: Raspberry Pi 4 doesnt boot after apt upgrade
I restored my 4B4 to the default "critical" firmware, and I can confirm this problem.
Starting with a freshly written card (RaspiOS32 from Raspberry Pi Imager) I went through the Welcome to Raspberry Pi startup configuration script, and initially it rebooted fine. However attempting several more reboots resulted in a few boot failures.
The system seemed to shutdown fine, and my monitor would go to sleep then wake up again as it usually does when the system reboots, but then nothing. Monitor remained live as if it was receiving a signal, but there was no activity indicated by the ACT LED and nothing on the screen.
My USB-SSD booted 4B2 on the latest "stable" firmware rebooted fine (many times) after update/full-upgrade (RaspiOS32).
Gonna try the 4B4 card in that system... (will report back).
EDIT
Happens with the "stable" firmware as well. Not sure why it hasn't affected my SSD (as far as I can tell).
I'll see if enabling the serial console output shows anything interesting...
EDIT-2
Well that's unfortunate. It seems that enabling the serial console output fixes the issue. Rebooted a couple of dozen times with no failures. Disabled the serial console and got a boot failure after a few reboots. So nothing interesting to capture and post (I hate this intermittent stuff). But at least it explains why my SSD wasn't encountering this problem.
I did capture output from the bootloader itself, and it shows nothing interesting (successful and failed boot outputs are identical).
Starting with a freshly written card (RaspiOS32 from Raspberry Pi Imager) I went through the Welcome to Raspberry Pi startup configuration script, and initially it rebooted fine. However attempting several more reboots resulted in a few boot failures.
The system seemed to shutdown fine, and my monitor would go to sleep then wake up again as it usually does when the system reboots, but then nothing. Monitor remained live as if it was receiving a signal, but there was no activity indicated by the ACT LED and nothing on the screen.
My USB-SSD booted 4B2 on the latest "stable" firmware rebooted fine (many times) after update/full-upgrade (RaspiOS32).
Gonna try the 4B4 card in that system... (will report back).
EDIT
Happens with the "stable" firmware as well. Not sure why it hasn't affected my SSD (as far as I can tell).
I'll see if enabling the serial console output shows anything interesting...
EDIT-2
Well that's unfortunate. It seems that enabling the serial console output fixes the issue. Rebooted a couple of dozen times with no failures. Disabled the serial console and got a boot failure after a few reboots. So nothing interesting to capture and post (I hate this intermittent stuff). But at least it explains why my SSD wasn't encountering this problem.
I did capture output from the bootloader itself, and it shows nothing interesting (successful and failed boot outputs are identical).
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?
lots of pop-ups...and where is that annoying music coming from?
Re: Raspberry Pi 4 doesnt boot after apt upgrade
Looks like bug in kernel. I had to reconfigure all my software and stay in original image, without apt upgrade. Please, someone let me know when i can update system again!
Re: Raspberry Pi 4 doesnt boot after apt full-upgrade
Any update for solve this?
How to downgrade to latest 4.19 kernel?
How to downgrade to latest 4.19 kernel?
Re: Raspberry Pi 4 doesnt boot after apt full-upgrade
I am also having the same problem. Everything was since Feb 2020. Just a few days ago another update - I do it at 8PM every day. When booting it's just a blank screen.
Fortunately I have a second SD card which I use as backup and this one runs fine.
The boot eventually does seem to work, but after 3-4 power-off/power-on attempts.
Regards,
Richard
Fortunately I have a second SD card which I use as backup and this one runs fine.
The boot eventually does seem to work, but after 3-4 power-off/power-on attempts.
Regards,
Richard
Re: Raspberry Pi 4 doesnt boot after apt full-upgrade
Critical bug!richlion2 wrote: ↑Tue Aug 18, 2020 5:34 pmI am also having the same problem. Everything was since Feb 2020. Just a few days ago another update - I do it at 8PM every day. When booting it's just a blank screen.
Fortunately I have a second SD card which I use as backup and this one runs fine.
The boot eventually does seem to work, but after 3-4 power-off/power-on attempts.
Regards,
Richard
- HawaiianPi
- Posts: 6126
- Joined: Mon Apr 08, 2013 4:53 am
- Location: Aloha, Oregon USA
Re: Raspberry Pi 4 doesnt boot after apt full-upgrade
Not so sure about that...
I have tried to reproduce the problem again, starting over with a freshly imaged card, and I have not been successful.
Only difference was the first time I used a 16GB card and this time it was 32GB. So I re-wrote the exact same 16GB card I used the first time, and it's working fine now ...
As far as I can tell, anyway. I've lost count of how many dozen successful reboots and power off/on restarts I've had. But with this intermittent stuff ...

Did I mention that I hate this intermittent stuff.

My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?
lots of pop-ups...and where is that annoying music coming from?
Re: Raspberry Pi 4 doesnt boot after apt full-upgrade
I tested with a 16GB SanDisk Ultra and 32GB Kingston Canvas SelectHawaiianPi wrote: ↑Tue Aug 18, 2020 11:54 pmNot so sure about that...
I have tried to reproduce the problem again, starting over with a freshly imaged card, and I have not been successful.
Only difference was the first time I used a 16GB card and this time it was 32GB. So I re-wrote the exact same 16GB card I used the first time, and it's working fine now ...
As far as I can tell, anyway. I've lost count of how many dozen successful reboots and power off/on restarts I've had. But with this intermittent stuff ...
Did I mention that I hate this intermittent stuff.![]()
-
- Posts: 25179
- Joined: Tue Mar 25, 2014 12:40 pm
- Location: Delightful Dorset
Re: Raspberry Pi 4 doesnt boot after apt full-upgrade
melqui wrote: ↑Sun Aug 16, 2020 8:50 pmRaspberry Pi 4 v1.2 4GB
Steps to reproduce bug:
1. Install latest image 32bits recommended from Pi imager 1.3 , from zero.
2. run sudo apt update && sudo apt full-upgrade -y
Result intermmitent booting.
Official power supply, tested various sd cards, latest critical firmware (and latest stable too).
Bug dont occurs with original image (without update) or other distros and 64 bits.
I grabbed an old SD Card and created a bootable RaspiOS ARMHF with Pi-Imager, booted no issues, configured, rebooted, fully updated, rebooted, eeprom to stable, rebooted, rebooted, rebooted.
The information is out there....you just have to let it in.
Re: Raspberry Pi 4 doesnt boot after apt full-upgrade
"I hate this intermittent stuff."
Re: Raspberry Pi 4 doesnt boot after apt full-upgrade
If you see an intermittent issue please can you post 'vcgencmd version' and 'uname -a' here on the occasions where it does boot so that we can more accurately track versions with intermittent issues.
Other information which might be relevant is the display(s) resolution and any overclocking settings in config.txt because these change clock speeds.
The most stable Raspberry Pi OS nightly is 2020-08-12 available here http://downloads.raspberrypi.org/nightlies/ for test purposes so it would be good to know if that fails. I'm guessing you have the same firmware and kernel as the newer 2020-08-18 image.
Other information which might be relevant is the display(s) resolution and any overclocking settings in config.txt because these change clock speeds.
The most stable Raspberry Pi OS nightly is 2020-08-12 available here http://downloads.raspberrypi.org/nightlies/ for test purposes so it would be good to know if that fails. I'm guessing you have the same firmware and kernel as the newer 2020-08-18 image.
Re: Raspberry Pi 4 doesnt boot after apt full-upgrade
Overclock: Never
Resolution: 1080p
All OK with this (factory image):
pi@Pi4:~ $ vcgencmd version
May 11 2020 18:59:41
Copyright (c) 2012 Broadcom
version 21bfdeee3a6ea823e2113b983390acd1eec8edfb (clean) (release) (start)
pi@Pi4:~ $ uname -a
Linux Pi4 4.19.118-v7l+ #1311 SMP Mon Apr 27 14:26:42 BST 2020 armv7l GNU/Linux
pi@Pi4:~ $ sudo rpi-eeprom-update
BCM2711 detected
BOOTLOADER: up-to-date
CURRENT: qui abr 16 17:11:26 UTC 2020 (1587057086)
LATEST: qui abr 16 17:11:26 UTC 2020 (1587057086)
FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 000137ad
LATEST: 000137ad
Intermittent boot:
pi@Pi4:~ $ vcgencmd version
Aug 6 2020 16:22:25
Copyright (c) 2012 Broadcom
version af3edc2de473197cdfe1ff5a8ff2d34095d5b336 (clean) (release) (start)
pi@Pi4:~ $ uname -a
Linux Pi4 5.4.51-v7l+ #1333 SMP Mon Aug 10 16:51:40 BST 2020 armv7l GNU/Linux
pi@Pi4:~ $ sudo rpi-eeprom-update (critical or latest stable, doesn't matter)
BCM2711 detected
BOOTLOADER: up-to-date
CURRENT: qui abr 16 17:11:26 UTC 2020 (1587057086)
LATEST: qui abr 16 17:11:26 UTC 2020 (1587057086)
FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 000137ad
LATEST: 000137ad
If i do sudo rpi-update 866751bfd023e72bd96a8225cf567e03c334ecc4 , OK again.
Latest Kernel (https://github.com/Hexxeh/rpi-firmware/ ... 506a1ebeb9) don't solve, intermittent booting.
Resolution: 1080p
All OK with this (factory image):
pi@Pi4:~ $ vcgencmd version
May 11 2020 18:59:41
Copyright (c) 2012 Broadcom
version 21bfdeee3a6ea823e2113b983390acd1eec8edfb (clean) (release) (start)
pi@Pi4:~ $ uname -a
Linux Pi4 4.19.118-v7l+ #1311 SMP Mon Apr 27 14:26:42 BST 2020 armv7l GNU/Linux
pi@Pi4:~ $ sudo rpi-eeprom-update
BCM2711 detected
BOOTLOADER: up-to-date
CURRENT: qui abr 16 17:11:26 UTC 2020 (1587057086)
LATEST: qui abr 16 17:11:26 UTC 2020 (1587057086)
FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 000137ad
LATEST: 000137ad
Intermittent boot:
pi@Pi4:~ $ vcgencmd version
Aug 6 2020 16:22:25
Copyright (c) 2012 Broadcom
version af3edc2de473197cdfe1ff5a8ff2d34095d5b336 (clean) (release) (start)
pi@Pi4:~ $ uname -a
Linux Pi4 5.4.51-v7l+ #1333 SMP Mon Aug 10 16:51:40 BST 2020 armv7l GNU/Linux
pi@Pi4:~ $ sudo rpi-eeprom-update (critical or latest stable, doesn't matter)
BCM2711 detected
BOOTLOADER: up-to-date
CURRENT: qui abr 16 17:11:26 UTC 2020 (1587057086)
LATEST: qui abr 16 17:11:26 UTC 2020 (1587057086)
FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 000137ad
LATEST: 000137ad
If i do sudo rpi-update 866751bfd023e72bd96a8225cf567e03c334ecc4 , OK again.
Latest Kernel (https://github.com/Hexxeh/rpi-firmware/ ... 506a1ebeb9) don't solve, intermittent booting.
Re: Raspberry Pi 4 doesnt boot after apt full-upgrade
Might be related: I also noticed intermittent boot issues with the latest rpi-update firmwarre when testing on LibreELEC.
I didn't get anything from earlycon but adding uart_2ndstage=1 showed some interesting things: loaded kernel.img size was 0x0 and I got a bunch of "SDCARD_CONTROL_POWER"/"SDCARD_CONTROL_WRITE_PROTECTED" not defined lines from the firmware.
Successful boot:
unsuccessful boot:
Sometimes cold-boot (power unplugged) failed, sometimes reboot failed, most of the time boot works.
so long,
Hias
Code: Select all
LibreELEC:~ # vcgencmd version
Aug 17 2020 15:29:08
Copyright (c) 2012 Broadcom
version 1e1fc5688314d8d9935e272ce8e1c2259890a654 (clean) (release) (start_x)
Successful boot:
Code: Select all
PM_RSTS: 0x00001020
RPi: BOOTLOADER release VERSION:45291ce6 DATE: Jul 16 2020 TIME: 16:15:51 BOOTMO
DE: 0x00000006 part: 0 BUILD_TIMESTAMP=1594912546 0x8eb25f41 0x00c03111
uSD voltage 1.8V
GLOBAL_RESET: 01 0
PM_RSTS: 0x00001000
RPi: BOOTLOADER release VERSION:45291ce6 DATE: Jul 16 2020 TIME: 16:15:51 BOOTMO
DE: 0x00000006 part: 0 BUILD_TIMESTAMP=1594912546 0x8eb25f41 0x00c03111
uSD voltage 3.3V
Initialising SDRAM 'Micron' 16Gb x2 total-size: 32 Gbit 3200
Boot mode: SD (01) order f24
SD HOST: 250000000 CTL0: 0x00000000 BUS: 100000 Hz actual: 100000 HZ div: 2500 (
1250) status: 0x1fff0000 delay: 1080
SD HOST: 250000000 CTL0: 0x00000f00 BUS: 100000 Hz actual: 100000 HZ div: 2500 (
1250) status: 0x1fff0000 delay: 1080
CID: 000353445345333247808b4f24d30122
CSD: 400e00325b590000edc87f800a404000
SD: bus-width: 4 spec: 2 SCR: 0x02358443 0x00000000
SD HOST: 250000000 CTL0: 0x00000f04 BUS: 50000000 Hz actual: 41666666 HZ div: 6
(3) status: 0x1fff0000 delay: 2
MBR: 0x00002000, 1048576 type: 0x0c
MBR: 0x00102000,61277184 type: 0x83
MBR: 0x00000000, 0 type: 0x00
MBR: 0x00000000, 0 type: 0x00
lba: 8192 oem: 'MTOO4023' volume: ' '
rsc 1 fat-sectors 256 c-count 65501 c-size 16 r-dir 1 r-sec 32
PM_RSTS: 0x00001000
Partition: 0
lba: 8192 oem: 'MTOO4023' volume: ' '
rsc 1 fat-sectors 256 c-count 65501 c-size 16 r-dir 1 r-sec 32
Read config.txt bytes 1894 hnd 0x00004757 hash '5c9ecdf72f41e737'
recover4.elf not found (6)
recovery.elf not found (6)
start4.elf not found (6)
Read start.elf bytes 3043624 hnd 0x00004189 hash 'a1546dd527978662'
Read fixup.dat bytes 8429 hnd 0x000042fd hash '289357044699105c'
0x00c03111 0x00000000 0x0000001f
MEM GPU: 320 ARM: 704 TOTAL: 1024
Starting start.elf @ 0xfec00200 partition 0
MESS:00:00:04.394211:0: arasan: arasan_emmc_open
MESS:00:00:04.578265:0: brfs: File read: /mfs/sd/config.txt
MESS:00:00:04.581257:0: brfs: File read: 1894 bytes
MESS:00:00:04.585737:0: brfs: File read: /mfs/sd/distroconfig.txt
MESS:00:00:04.591491:0: brfs: File read: 228 bytes
MESS:00:00:04.651484:0: brfs: File read: /mfs/sd/config.txt
MESS:00:00:04.654482:0: brfs: File read: 1894 bytes
MESS:00:00:04.658963:0: brfs: File read: /mfs/sd/distroconfig.txt
MESS:00:00:05.728051:0: gpioman: gpioman_get_pin_num: pin DISPLAY_DSI_PORT not d
efined
MESS:00:00:05.735304:0: *** Restart logging
MESS:00:00:05.736767:0: brfs: File read: 228 bytes
MESS:00:00:05.783363:0: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_di
splay_state instead
MESS:00:00:05.789304:0: HDMI0: hdmi_pixel_encoding: 300000000
MESS:00:00:05.794772:0: HDMI1: hdmi_pixel_encoding: 300000000
MESS:00:00:05.805172:0: dtb_file 'bcm2711-rpi-4-b.dtb'
MESS:00:00:05.813107:0: brfs: File read: /mfs/sd/bcm2711-rpi-4-b.dtb
MESS:00:00:05.816350:0: Loading 'bcm2711-rpi-4-b.dtb' to 0x100 size 0xa0e1
MESS:00:00:05.832670:0: brfs: File read: 41185 bytes
MESS:00:00:05.894923:0: brfs: File read: /mfs/sd/config.txt
MESS:00:00:05.897902:0: brfs: File read: 1894 bytes
MESS:00:00:05.902404:0: brfs: File read: /mfs/sd/distroconfig.txt
MESS:00:00:05.907853:0: brfs: File read: 228 bytes
MESS:00:00:05.923541:0: brfs: File read: /mfs/sd/overlays/vc4-fkms-v3d.dtbo
MESS:00:00:05.940585:0: Loaded overlay 'vc4-fkms-v3d'
MESS:00:00:05.965668:0: brfs: File read: 1255 bytes
MESS:00:00:05.978226:0: brfs: File read: /mfs/sd/overlays/disable-bt.dtbo
MESS:00:00:06.013822:0: Loaded overlay 'disable-bt'
MESS:00:00:06.073467:0: brfs: File read: 954 bytes
MESS:00:00:06.078899:0: brfs: File read: /mfs/sd/cmdline.txt
MESS:00:00:06.081535:0: Read command line from file 'cmdline.txt':
MESS:00:00:06.087390:0: 'boot=UUID=2907-5719 disk=UUID=cf0bbd10-802c-41cf-bb8b-3
bbe78425239 console=serial0,115200 earlycon=pl011,mmio32,0xfe201000 systemd.debu
g_shell'
MESS:00:00:07.370308:0: brfs: File read: 143 bytes
MESS:00:00:08.900249:0: brfs: File read: /mfs/sd/kernel.img
MESS:00:00:08.902771:0: Loading 'kernel.img' to 0x8000 size 0x7e0010
MESS:00:00:08.908861:0: Device tree loaded to 0x2bfe5a00 (size 0xa5ef)
MESS:00:00:08.915342:0: uart: Set PL011 baud rate to 103448.300000 Hz
MESS:00:00:08.924214:0: uart: Baud rate change done...
MESS:00:00:08.926281:0: uart: Baud rate change done...
MESS:00:00:08.935916:0: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_POWER n
ot defined
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.19.127 (hias@tv) (gcc version 8.3.0 (GCC)) #1 SMP
Mon Aug 17 12:11:25 CEST 2020
...
Code: Select all
PM_RSTS: 0x00001020
RPi: BOOTLOADER release VERSION:45291ce6 DATE: Jul 16 2020 TIME: 16:15:51 BOOTMO
DE: 0x00000006 part: 0 BUILD_TIMESTAMP=1594912546 0x8eb25f41 0x00c03111
uSD voltage 1.8V
GLOBAL_RESET: 01 0
PM_RSTS: 0x00001000
RPi: BOOTLOADER release VERSION:45291ce6 DATE: Jul 16 2020 TIME: 16:15:51 BOOTMO
DE: 0x00000006 part: 0 BUILD_TIMESTAMP=1594912546 0x8eb25f41 0x00c03111
uSD voltage 3.3V
Initialising SDRAM 'Micron' 16Gb x2 total-size: 32 Gbit 3200
Boot mode: SD (01) order f24
SD HOST: 250000000 CTL0: 0x00000000 BUS: 100000 Hz actual: 100000 HZ div: 2500 (
1250) status: 0x1fff0000 delay: 1080
SD HOST: 250000000 CTL0: 0x00000f00 BUS: 100000 Hz actual: 100000 HZ div: 2500 (
1250) status: 0x1fff0000 delay: 1080
CID: 000353445345333247808b4f24d30122
CSD: 400e00325b590000edc87f800a404000
SD: bus-width: 4 spec: 2 SCR: 0x02358443 0x00000000
SD HOST: 250000000 CTL0: 0x00000f04 BUS: 50000000 Hz actual: 41666666 HZ div: 6
(3) status: 0x1fff0000 delay: 2
MBR: 0x00002000, 1048576 type: 0x0c
MBR: 0x00102000,61277184 type: 0x83
MBR: 0x00000000, 0 type: 0x00
MBR: 0x00000000, 0 type: 0x00
lba: 8192 oem: 'MTOO4023' volume: ' '
rsc 1 fat-sectors 256 c-count 65501 c-size 16 r-dir 1 r-sec 32
PM_RSTS: 0x00001000
Partition: 0
lba: 8192 oem: 'MTOO4023' volume: ' '
rsc 1 fat-sectors 256 c-count 65501 c-size 16 r-dir 1 r-sec 32
Read config.txt bytes 1894 hnd 0x00004757 hash '5c9ecdf72f41e737'
recover4.elf not found (6)
recovery.elf not found (6)
start4.elf not found (6)
Read start.elf bytes 3043624 hnd 0x00004189 hash 'a1546dd527978662'
Read fixup.dat bytes 8429 hnd 0x000042fd hash '289357044699105c'
0x00c03111 0x00000000 0x0000001f
MEM GPU: 320 ARM: 704 TOTAL: 1024
Starting start.elf @ 0xfec00200 partition 0
MESS:00:00:04.394195:0: arasan: arasan_emmc_open
MESS:00:00:04.578128:0: brfs: File read: /mfs/sd/config.txt
MESS:00:00:04.581120:0: brfs: File read: 1894 bytes
MESS:00:00:04.587276:0: brfs: File read: /mfs/sd/distroconfig.txt
MESS:00:00:04.591346:0: brfs: File read: 228 bytes
MESS:00:00:04.651352:0: brfs: File read: /mfs/sd/config.txt
MESS:00:00:04.654350:0: brfs: File read: 1894 bytes
MESS:00:00:04.658832:0: brfs: File read: /mfs/sd/distroconfig.txt
MESS:00:00:05.727915:0: gpioman: gpioman_get_pin_num: pin DISPLAY_DSI_PORT not d
efined
MESS:00:00:05.735168:0: *** Restart logging
MESS:00:00:05.736631:0: brfs: File read: 228 bytes
MESS:00:00:05.783232:0: hdmi: HDMI:hdmi_get_state is deprecated, use hdmi_get_di
splay_state instead
MESS:00:00:05.789173:0: HDMI0: hdmi_pixel_encoding: 300000000
MESS:00:00:05.794641:0: HDMI1: hdmi_pixel_encoding: 300000000
MESS:00:00:05.805045:0: dtb_file 'bcm2711-rpi-4-b.dtb'
MESS:00:00:05.812974:0: brfs: File read: /mfs/sd/bcm2711-rpi-4-b.dtb
MESS:00:00:05.816217:0: Loading 'bcm2711-rpi-4-b.dtb' to 0x100 size 0xa0e1
MESS:00:00:05.832536:0: brfs: File read: 41185 bytes
MESS:00:00:05.894786:0: brfs: File read: /mfs/sd/config.txt
MESS:00:00:05.897765:0: brfs: File read: 1894 bytes
MESS:00:00:05.902267:0: brfs: File read: /mfs/sd/distroconfig.txt
MESS:00:00:05.907716:0: brfs: File read: 228 bytes
MESS:00:00:05.923412:0: brfs: File read: /mfs/sd/overlays/vc4-fkms-v3d.dtbo
MESS:00:00:05.940450:0: Loaded overlay 'vc4-fkms-v3d'
MESS:00:00:05.965440:0: brfs: File read: 1255 bytes
MESS:00:00:05.977995:0: brfs: File read: /mfs/sd/overlays/disable-bt.dtbo
MESS:00:00:06.013691:0: Loaded overlay 'disable-bt'
MESS:00:00:06.073334:0: brfs: File read: 954 bytes
MESS:00:00:06.078770:0: brfs: File read: /mfs/sd/cmdline.txt
MESS:00:00:06.081405:0: Read command line from file 'cmdline.txt':
MESS:00:00:06.087260:0: 'boot=UUID=2907-5719 disk=UUID=cf0bbd10-802c-41cf-bb8b-3
bbe78425239 console=serial0,115200 earlycon=pl011,mmio32,0xfe201000 systemd.debu
g_shell'
MESS:00:00:07.369901:0: brfs: File read: 143 bytes
MESS:00:00:08.902826:0: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_POWER n
ot defined
MESS:00:00:08.908092:0: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_POWER n
ot defined
MESS:00:00:09.016034:0: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_POWER n
ot defined
MESS:00:00:09.067979:0: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_WRITE_P
ROTECTED not defined
MESS:00:00:10.604565:0: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_POWER n
ot defined
MESS:00:00:10.609827:0: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_POWER n
ot defined
MESS:00:00:10.717767:0: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_POWER n
ot defined
MESS:00:00:10.769403:0: gpioman: gpioman_get_pin_num: pin SDCARD_CONTROL_WRITE_P
ROTECTED not defined
MESS:00:00:10.786556:0: Loading 'kernel.img' to 0x8000 size 0x0
MESS:00:00:10.789436:0: Device tree loaded to 0x2bfe5a00 (size 0xa5ef)
MESS:00:00:10.795885:0: uart: Set PL011 baud rate to 103448.300000 Hz
MESS:00:00:10.804782:0: uart: Baud rate change done...
MESS:00:00:10.806845:0: uart: Baud rate change done...
so long,
Hias
Re: Raspberry Pi 4 doesnt boot after apt full-upgrade
Thanks @HiassofT that's very useful
Re: Raspberry Pi 4 doesnt boot after apt full-upgrade
BTW: earliest firmware with intermittent boot issues so far seems to be Jul 31 which failed to boot on second try - haven't noticed anything unusual yet on Jul 17 and before.
so long,
Hias
so long,
Hias
Re: Raspberry Pi 4 doesnt boot after apt full-upgrade
If i run sudo rpi-update 866751bfd023e72bd96a8225cf567e03c334ecc4 (latest 4.19), i can upgrade to a new fixed kernel in future simply run sudo apt update and full-upgrade ?
or better
Can I
sudo apt-mark hold raspberrypi-kernel
and
sudo apt-mark hold raspberrypi-bootloader
For maintain the 4.19 kernel and do all other upgrades normally, without issues?
or better
Can I
sudo apt-mark hold raspberrypi-kernel
and
sudo apt-mark hold raspberrypi-bootloader
For maintain the 4.19 kernel and do all other upgrades normally, without issues?
Re: Raspberry Pi 4 doesnt boot after apt full-upgrade
I was able to reproduce something with similar symptoms but only with one board + SD combination. Which board(s) / SD(s) failed for you?
Would you be able to try this experimental firmware fix?
https://drive.google.com/drive/folders/ ... sp=sharing
Re: Raspberry Pi 4 doesnt boot after apt full-upgrade
Here Raspberry Pi 4B v1.2 4GB RAMtimg236 wrote: ↑Wed Aug 19, 2020 2:51 pmI was able to reproduce something with similar symptoms but only with one board + SD combination. Which board(s) / SD(s) failed for you?
Would you be able to try this experimental firmware fix?
https://drive.google.com/drive/folders/ ... sp=sharing
uSD Kingston Canvas Select 32GB or Sandisk Ultra 16GB
Re: Raspberry Pi 4 doesnt boot after apt full-upgrade
I tested on a 4GB RPi4 prototype board with B1 silicon stepping and a Sandisk Extreme 32GB card.
Code: Select all
Hardware : BCM2835
Revision : c03111
Serial : 100000008eb25f41
Model : Raspberry Pi 4 Model B Rev 1.1
Code: Select all
[ 1.970354] mmc0: new ultra high speed DDR50 SDHC card at address aaaa
[ 1.971206] mmcblk0: mmc0:aaaa SE32G 29.7 GiB
sure, I'll give it a try!Would you be able to try this experimental firmware fix?
https://drive.google.com/drive/folders/ ... sp=sharing
so long,
Hias
Re: Raspberry Pi 4 doesnt boot after apt full-upgrade
Testing is looking good so far, RPi survived about 30 reboots. I'll keep an eye on it and see if I can make it fail.timg236 wrote: ↑Wed Aug 19, 2020 2:51 pmWould you be able to try this experimental firmware fix?
https://drive.google.com/drive/folders/ ... sp=sharing
Code: Select all
LibreELEC:/ # vcgencmd version
Aug 19 2020 15:25:00
Copyright (c) 2012 Broadcom
version d77c9f060557f7fb03f2053236858be5358c89f3 (tainted) (release) (start_x)
Hias
Re: Raspberry Pi 4 doesnt boot after apt full-upgrade
What was the issue/fix? If I copy this files to /boot, can I upgrade normally (apt full-upgrade) firmware in future?timg236 wrote: ↑Wed Aug 19, 2020 2:51 pm
Would you be able to try this experimental firmware fix?
https://drive.google.com/drive/folders/ ... sp=sharing
Re: Raspberry Pi 4 doesnt boot after apt full-upgrade
There's a firmware tweak for a subtle timing issue in the FW SD driver. You can copy the files to /boot but don't do this on a card which contains important data because you are probably only the third person to test thismelqui wrote: ↑Wed Aug 19, 2020 4:40 pmWhat was the issue/fix? If I copy this files to /boot, can I upgrade normally (apt full-upgrade) firmware in future?timg236 wrote: ↑Wed Aug 19, 2020 2:51 pm
Would you be able to try this experimental firmware fix?
https://drive.google.com/drive/folders/ ... sp=sharing

It might be better to wait for the APT update
Re: Raspberry Pi 4 doesnt boot after apt full-upgrade
At moment, my pi4 is in factory image (2020-05-27) without update/upgradetimg236 wrote: ↑Wed Aug 19, 2020 4:45 pmThere's a firmware tweak for a subtle timing issue in the FW SD driver. You can copy the files to /boot but don't do this on a card which contains important data because you are probably only the third person to test thismelqui wrote: ↑Wed Aug 19, 2020 4:40 pmWhat was the issue/fix? If I copy this files to /boot, can I upgrade normally (apt full-upgrade) firmware in future?timg236 wrote: ↑Wed Aug 19, 2020 2:51 pm
Would you be able to try this experimental firmware fix?
https://drive.google.com/drive/folders/ ... sp=sharing
It might be better to wait for the APT update
If I run
sudo apt-mark hold raspberrypi-bootloader
and upgrade kernel and all other packages, will prevent this issue?