Not booting after latest update
#1
Hi, 

I issued an

Code:
apt update && apt upgrade

a few hours ago and since then it's not booting anymore. I just see the LED shining in white. The screen remains black.

I saw that it was installing the 5.7 kernel, so I guess it messed up u-boot. 

I had it installed to EMMC, so I hope I will be able to restore everything by booting from SD. Can I just reinstall u-boot? What are the commands to do so?
I'm also still on the old version where /boot was on the root partition. Maybe it is also because of that. I guess, when I'm already in the process of repairing I could also repartition.
  Reply
#2
(06-25-2020, 03:13 PM)Boern Wrote: Hi, 

I issued an

Code:
apt update && apt upgrade

a few hours ago and since then it's not booting anymore. I just see the LED shining in white. The screen remains black.

I saw that it was installing the 5.7 kernel, so I guess it messed up u-boot. 

I had it installed to EMMC, so I hope I will be able to restore everything by booting from SD. Can I just reinstall u-boot? What are the commands to do so?
I'm also still on the old version where /boot was on the root partition. Maybe it is also because of that. I guess, when I'm already in the process of repairing I could also repartition.

ditto! Also on old single partition version. Have backed up my user directory and figure I will start from a new 2 partition download.

1 thing I have noticed - on my trial Mobian/jwm version the screen is flashing like a disco light after the 5.7 upgrade, virtually unusable. Hope the Mobian/phosh version is OK.

OK, installed 20200625 nightly and it seemed OK. Did the upgrade to 5.7 and after reboot have dark screen - can't find a way to get it legible.

Suspect for now avoid 5.7 kernel?
  • ROCKPro64 v2.1 2GB, 16Gb eMMC for rootfs, SX8200Pro 512GB NVMe for /home, HDMI video & sound, Bluetooth keyboard & mouse. Started Bionic minimal - now "groovy", Openbox desktop for general purpose daily PC.
  • PinePhone BraveHeart now v1.2b 3/32Gb daily driver, dual boot via p-boot with Mobian on eMMC, Arch/f2fs/Phosh on SDcard
  • PinePhone v1.2a 2G/16Gb that needs USB board replaced
  Reply
#3
Yep, should have checked here first Tongue
Have been updating daily for the last few weeks without too many issues.
After todays update noticed the same problem. Going to go back to testing the update on the sd card and doing the update to the emmc if the update goes well.
  Reply
#4
OK - running 5.7 kernel OK.
Installed 20200625 nightly
Settings, Power, Disable automatic brightness and Disable Dim screen when inactive
Then upgrade to 5.7
:-)
  • ROCKPro64 v2.1 2GB, 16Gb eMMC for rootfs, SX8200Pro 512GB NVMe for /home, HDMI video & sound, Bluetooth keyboard & mouse. Started Bionic minimal - now "groovy", Openbox desktop for general purpose daily PC.
  • PinePhone BraveHeart now v1.2b 3/32Gb daily driver, dual boot via p-boot with Mobian on eMMC, Arch/f2fs/Phosh on SDcard
  • PinePhone v1.2a 2G/16Gb that needs USB board replaced
  Reply
#5
(06-25-2020, 03:13 PM)Boern Wrote: I had it installed to EMMC, so I hope I will be able to restore everything by booting from SD. Can I just reinstall u-boot? What are the commands to do so?

To reinstall u-boot to the eMMC, the command is:
Code:
sudo u-boot-install-sunxi64 /dev/mmcblk2

Please let me know if it solves your problem.

(06-25-2020, 04:51 PM)dukla2000 Wrote: Settings, Power, Disable automatic brightness and Disable Dim screen when inactive

Interesting, that means the brightness scale (changed in pine64's 5.7 kernel) does not work that well for all devices... I'll have a look
  Reply
#6
I tried running
Code:
sudo u-boot-install-sunxi64 /dev/mmcblk2
from a chroot, that just made everything worse and it wouldn't boot at all. But running it from within a fresh mobian-pinephone-20200615.img.gz installation worked.

But now I have the problems with automatic brightness. But I do have ssh-access. Can I somehow do the necessary settings from the command line?
Edit: The screen lit up for about 2 seconds every time I put in a charging cable and so I was able to make the necessary changes.
  Reply
#7
To disable auto-brightness:
Code:
gsettings set org.gnome.settings-daemon.plugins.power ambient-enabled false

To set a correct brightness value (as root)
Code:
echo 400 > /sys/class/backlight/backlight/brightness

I'm working on a new kernel version which should (hopefully) get the brightness scale right...

(06-26-2020, 08:33 AM)Boern Wrote: from a chroot, that just made everything worse and it wouldn't boot at all. But running it from within a fresh mobian-pinephone-20200615.img.gz installation worked.
yes, I wouldn't have tried that from a chroot, only from a running system (whether it runs from SD or eMMC doesn't matter)
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  no camera,streaming after update rvh 0 150 03-21-2021, 08:02 AM
Last Post: rvh
  Phone won't boot after update: red LED 3x5co 7 714 02-16-2021, 01:34 PM
Last Post: 3x5co
  Mobian phone app update 2-14 mw4jet 8 949 02-16-2021, 06:53 AM
Last Post: a-wai
  Modem Firmware: update manually or wait? sfb 4 1,062 02-06-2021, 05:14 AM
Last Post: sfb
  Geary crashes during start after recent update p1trson 2 532 01-16-2021, 04:49 AM
Last Post: p1trson
  Status update 2020-12-15 a-wai 34 10,331 01-13-2021, 07:14 AM
Last Post: scott_VYuCAbn3k1NFK
  Modem firmware update SocialNetworkingWasAMistake 8 1,888 01-03-2021, 06:58 PM
Last Post: dcinoz
  Latest build, cant use top menu Cree 0 319 12-26-2020, 07:40 PM
Last Post: Cree
  Status update 2020-11-15 a-wai 17 5,582 12-05-2020, 05:58 PM
Last Post: bcnaz
  PSA: Transition in progress - don't update ! a-wai 46 13,431 11-20-2020, 10:37 AM
Last Post: Gribouille

Forum Jump:


Users browsing this thread: 1 Guest(s)