Last night I fired up my PineTab after not having used it in some time. After having solved apt-get update "The following signatures were invalid..." Mobian had a ton (a little over a 1000) updates to install, after that was done I entered the reboot command.
Since then the only sign of life is the occasional clicking of the camera's when holding the power button (from 2-3 up to 10s), other than that nothing happens. No error, nothing.
Besides reflashing Mobian, are there any ways of figuring out why Mobian won't boot?
i have concluded at this point that this bug is in two parts, powersaving part and frequency change part. practically all gnu/linux distributions and plasma and phosh are affected.
powersaving part seems to be more straightforward and more rare. this can be avoided by following.
however, in my situtation, frequency bug happens only in 1.2a hardware version and not in 1.2b. so i don't rule out possible hardware problem in 1.2a version or my specfic individual phone.
if you tech savvy enough and you have pinephone regular. could you test frequency part of this bug and say your hardware version (1.2 1.2a 1.2b etc). you only set powersaving part, then run glxgears in user interfaces without auto suspend, sreenlocks and screen saving. then run following script in background.
Code:
while true
do echo 432000000 > /sys/class/devfreq/1c40000.gpu/min_freq
echo 432000000 > /sys/class/devfreq/1c40000.gpu/max_freq
echo 312000000 > /sys/class/devfreq/1c40000.gpu/max_freq
done
generic copy paste:
Code:
# udev rule. this prevent flipping frames bug
# example file location /lib/udev/rules.d/98-preventflippingbug.rules
# powersaving part
KERNEL=="1c40000.gpu", SUBSYSTEM=="platform", DRIVER=="lima", ATTR{power/autosuspend_delay_ms}="-1"
KERNEL=="1c40000.gpu", SUBSYSTEM=="platform", DRIVER=="lima", ATTR{power/control}="on"
# frequency part, may not be needed
KERNEL=="1c40000.gpu", SUBSYSTEM=="devfreq", ATTR{min_freq}="432000000"
KERNEL=="1c40000.gpu", SUBSYSTEM=="devfreq", ATTR{max_freq}="432000000"
What is new with NemoMobile in December? Huge step forward in porting to Qt6. Updating UX. Fixes in pinquery, lipstick, usb-moded, tuning messages app and polkit-agent.
CPU: Allwinner A64 (SUN50I)
Model: SoPine with baseboard
DRAM: 2 GiB
Core: 73 devices, 22 uclasses, devicetree: separate
WDT: Not starting watchdog@1c20ca0
MMC: mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 1:1...
In: serial
Out: serial
Err: serial
Net: phy interface11
eth0: ethernet@1c30000
MMC: no card present
** Bad device specification mmc 0 **
Couldn't find partition mmc 0
MMC: no card present
** Bad device specification mmc 0 **
Couldn't find partition mmc 0
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3259 bytes read in 2 ms (1.6 MiB/s)
## Executing script at 4fc00000
U-boot loaded from eMMC or secondary SD
Boot script loaded from mmc
155 bytes read in 2 ms (75.2 KiB/s)
MMC: no card present
** Bad device specification mmc 0 **
41777 bytes read in 4 ms (10 MiB/s)
3821 bytes read in 3 ms (1.2 MiB/s)
Applying kernel provided DT fixup script (sun50i-a64-fixup.scr)
## Executing script at 45000000
17114760 bytes read in 393 ms (41.5 MiB/s)
21934088 bytes read in 504 ms (41.5 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=41750000
## Loading init Ramdisk from Legacy Image at 4ff00000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 17114696 Bytes = 16.3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
Booting using the fdt blob at 0x4fa00000
Loading Ramdisk to 48fad000, end 49fff648 ... OK
Loading Device Tree to 0000000048f3a000, end 0000000048facfff ... OK
Starting kernel ...
done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.36.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk2p1] fsck.ext4 -a -C0 /dev/mmcblk2p1
armbi_root: clean, 69593/130816 files, 435596/523264 blocks
My questions are:
- should I change any configuration files from the Armbian_22.11.1_Pine64so_bullseye_current_5.15.80.img.xz's image?
- should I try another image?
I flashed my eMMC Module and mounted it on the Sopine baseboard, I connected my USB serial console/programmer and I power on the Sopine.
My problem is during the boot, nothing happen after the `Starting kernel ...` line.
Quote:% sudo screen /dev/ttyUSB0 115200
U-Boot SPL 2022.04-2 (May 05 2022 - 08:29:42 +0000)
DRAM: 2048 MiB
Trying to boot from MMC2
NOTICE: BL31: v2.6(release):
NOTICE: BL31: Built : 08:29:42, May 5 2022
NOTICE: BL31: Detected Allwinner A64/H64/R18 SoC (1689)
NOTICE: BL31: Found U-Boot DTB at 0x209c938, model: SoPine with baseboard
SCP/INF: Crust v0.5.10000
U-Boot 2022.04-2 (May 05 2022 - 08:29:42 +0000) Manjaro Linux ARM
CPU: Allwinner A64 (SUN50I)
Model: SoPine with baseboard
DRAM: 2 GiB
Core: 39 devices, 17 uclasses, devicetree: separate
WDT: Not starting watchdog@1c20ca0
MMC: mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to read "uboot.env" from mmc1:1...
In: serial
Out: serial
Err: serial
Net: phy interface10
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
1: Manjaro ARM
Retrieving file: /initramfs-linux.img
Retrieving file: /Image
append: initrd=/initramfs-linux.img console=ttyS0,115200 root=PARTUUID=1f2fe968-00ee-4b00-ad77-12e7c5c80fac rw rootwait audit=0 splash plymouth.ignore-serial-consoles
Retrieving file: /dtbs/allwinner/sun50i-a64-pine64-lts.dtb
Moving Image from 0x40080000 to 0x40200000, end=419e0000
## Flattened Device Tree blob at 4fa00000
Booting using the fdt blob at 0x4fa00000
Loading Ramdisk to 497f6000, end 49fff57e ... OK
Loading Device Tree to 00000000497e9000, end 00000000497f5dd7 ... OK
Starting kernel ...
My questions are:
- Manjaro Arm isn't yet compatible with Sopine Baseboard?
- Should I change any files of configuration from the Manjaro Arm image?
Please let me know the most recent Mobian image or Mobian installer image which you personally know works on the PP!
I'm having trouble getting a fresh install of Mobian to boot. I've used the Mobian image from 12/28 AND the Mobian installer image from that same date. I'm trying to troubleshoot where the problem lies; could it be with my install of tow-boot? The images from that date? Hardware? To isolate these effects and diagnose the problem, I'd like to use an image which is known to work. Thank you; you're really helping me out!
Some additional info: I have reason to believe tow-boot was installed correctly: I installed the 2021/10-005 installer of tow-boot to an SD card and used the tow-boot installation GUI to flash it to the eMMC boot partition. Since then, the power on, volume up, and volume down behavior and LED lights has been consistent with tow-boot's docs, suggesting that tow-boot is functioning correctly. I followed the instructions and didn't make any of the following obvious errors: I verified the sha256 checksums of all images. I unzipped them before dd'ing them. I flashed the right image to the right medium: Mobian image to eMMC via tow-boot's jumpdrive mode, Mobian installer image to SD card. Please do not post a link to the tow-boot or Mobian installation instructions. If you don't trust that I was following those, why bother responding at all? The order of events is as follows: I try to boot from eMMC, and the LED stays yellow. Nothing ever displays on the screen. I try to boot from the SD card, and the LED stays cyan. Nothing ever displays on the screen. These behaviors are different if there is no SD card, or if the eMMC has been erased: Then it vibes and blinks red. So the phone is recognizing in some manner that the images are bootable in some way, it just never displays anything on the screen of the phone.
