No worries. I did manage to install it from my laptop. Seems it had Tow-Boot there, which allowed me to mount it on my laptop, and so the device I installed it to was /dev/sdc (where the phone was mounted on my laptop).
It hasn’t asked me to set up a new user or anything, which seems odd [edit: there is a user and a pin, apparently → the default 123456]. WiFi is working (this did require a set up with KDE Wallet), as is the browser Angelfish. [edit #2: I also did upgrade it after the fresh install, and this went fine.]
@Firewave that appears to be a different issue. That only affects booting after initial install, whereas the issue with the pinephone pro affects both initial install (from updated images) and updated existing installs.
To avoid the issue on the ppp, please don’t update the kernel package (linux-pinephonepro) past version 6.3 for the time being.
If you need to fresh install, you’ll need to use an image that comes with 6.3 instead of 6.4.
@lectrode The initial issue, yes. I just posted mine there as it “seemed” related and I didn’t find anything else related in recent forum posts.
I also just have a PinePhone - not a Pro.
Is there way to fix a broken system? Like putting the 6.3 image back into the root partition it and pointing the boot partition to it?
As mentioned in the other post I have data in there and have not yet been able to access all of it yet because of permissions. /boot for instance is just empty in all the images.
And something off-topic: I also tried to restore the backup to the phone but for some stupid reason it says the file is too big to fit on the same MicroSD I pulled the backup from. Is there some block/sector size stupidity going on here because different filesystems are involved?
Apologies for the delayed response - my focus has been elsewhere of late.
Interesting that you ran into that on a regular Pinephone. I tested the update on mine, and didn’t run into any issues. Did you use the installation image for the Pinephone? Or did you try using a different image?
The /boot folder on both the Pinephone and Pinephone Pro images should be it’s own partition. Unless you’re specifically mounting that other partition at that location, it’s going to be empty. The contents for me are as follows:
If you have another device of the same architecture (not sure if a pinebook would work - it might), you might be able to mount the partitions of that install, then chroot into it using manjaro-chroot (part of the manjaro-tools-base-git package). You would then be able to run the following commands under the context of that install:
(Please note that while I’ve run similar commands on x86_64 systems, I don’t have any means of doing this on different architectures and these commands are an educated guess, but untested)
As far as the backup is concerned, how did you take the backup? Was it via dd? Are you using that to restore it as well? (it looks like dd should truncate “extra” image data by default when writing it to “smaller” physical storage)
You can remove this after or leave it for next time
Optional: If DNS doesn’t work you can hardcode some nameservers with
$ echo 'nameserver 1.1.1.1' | sudo tee -a pinephone/etc/resolv.conf
Might want to clean this up after.
mount host devices (not really sure if theae are strictly necessary but I did it last time too, and truthfully I mounted these at step 4 but should be fine to do it here too)
$ sudo mount -t proc proc pinephone/proc
$ sudo mount -t sysfs sys pinephone/sys
$ sudo mount -o bind /dev pinephone/dev
chroot this will open a bash shell to execute the following commands in
This made my PinePhone Pro boot again but I seem to have laggy audio and my mic doesn’t seem to work in calls anymore…
Edit: I just needed to reinstall pipewire-pulse seems it was replaced with the not working pulseaudio and calls work again
linux-pinephonepro 6.4.12-0 boots successfully on the ppp. Unfortunately, the wifi adapter is not detected on that kernel (modem seems to be detected - running some tests). Downgrading to the 6.3 series works-around the issue.
Thank you - linux-pinepohonepro 6.4.14-1 from unstable has confirmed working wifi and modem. I haven’t come across any further issues with that kernel.
Found a few packages that need a rebuild in both testing and unstable:
It appears it is the missing kernel modules. I used the beta14 image and updated the kernel only and it is working. It also does not complain about missing modules when updating the kernel and lsmod shows a truck load of modules loaded. I cannot figure out where the module configuration is though.
Update: I found and checked countless configuration files, steps and log files - everything is identical. The broken system just doesn’t add the module dependencies when building the kernel.
Update 2: It is not an obvious issue with mkinitcpio either as I “downgraded” the script (only the script not the package) with the same result. I need to collect the set -x output on both systems and figure out what is the difference.
Update 3: It is caused by mkinitcpio. I updated it (only the script not the package - from version 33 to 36) on the system which was working and it no longer finds the modules. Unfortunately there were lots of changes in the scripts, which makes the diff extremely noisy.
Update 4: Ah - I see. That script is not standalone and has other scripts it depends on. So I have to up/downgrade the whole package. I don’t have the older one available (it’s a pain/impossible to somehow get the hold of older packages) and I didn’t have working internet on the chroot for some reason although it worked before.
Update 5: I updated the package to version 36 and the issue persists. So it appears to be caused by mkinitcpio. Unfortunately I don’t have the version 33 package to see if a downgrade fixes it.
Update 6: For some reason it is not adding any of the modules. It seems like it is not getting the modules at all!? I cannot figure out where it goes wrong. There’s just too many differences.
No. It seems it is not the modules. I was able to boot the system even with a kernel which complained about no modules being included.
Interestingly I am getting the warning when I am installing from a local package with pacman -U but not when I install the same package from the repo via pacman -S.
Also the kernel is built twice as there is linux-pinephone.hook and linux.hook.
I see now. The Warning was with building the initrd image. On some devices that is normal as modules are not needed to set things up to boot since they are built into the kernel. I would say if it boots and lsmod shows modules it is probably ok.
I do not know about your device but does not sound quite right. Sounds like parts of 2 different kernels.
It turns out I was on the completely wrong track. My issues were not related to the kernel at all. The filesystem was corrupt! After I ran fsck it started working again… I came across this by accident because updating a package complained about not being able to write a file.
But now it doesn’t start the UI. I just see some debugfs boot messages and no logs were written at all. I had the same earlier when I updated the beta14 image to the latest packages. So I ran into a different issue now…
Update: It appears to be the ICU issue. startplasma-wayland fails with not finding libicui18n.so.72 and icu is 73.2-2.
