(09-27-2020, 10:22 AM)laaglu Wrote: Hi megous,

Many thanks for your work, it is great and truly appreciated. The time from press-power-on to pboot-main-screen is so incredibly fast.

Currently my most wanted feature would be as bujiraso suggested 'Boot to eMMC' (either as an option in the menu or as a key combination or both). I have tried power+volume-up but that did not seem to work. So currently I do a lot of micro-sd shuffling to switch between eMMC and pboot (too bad the micro-sd is not accessible without opening the phone on the current model, I hope Pine will consider an external slot in a future design). Is there a way to get boot to eMMc to work with present version, maybe by patching a file or something other tweak?

Lukas

(09-26-2020, 11:03 AM)jmorris Wrote:

(09-26-2020, 09:38 AM)megous Wrote: For package managers that use signatures, you typically need to have time set up correctly on your phone, because certificates are issued for a certain time window.

Also apparently package managers don't like to hit files that I marked as unchangeable, and instead of ignoring them, they fail the whole update. Workaround is to remove immutable flag on those files, back them up before update, and copy my versions back after update. It's usually various modem scripts.

Better fix may be to use NoUpgrade NoExtract options of pacman and equivalent options for other package managers, next time.

---

Looks like pacman and dpkg have ways to ignore select files by specifying the ignored files in the configuration files. Alpine package manager doesn't even have a config file that I can find, and it doesn't look like it has this functionality, so not sure how to work around this issue on distros that use it. Maybe someone else has some suggestions?

PMOS-Plasma is hopeless, you can't set the timezone, changes just don't stick.  But the clock is right, correctly displayed in GMT.  PMOS-Phosh has the right time and timezone so that is where I started digging first.  Tracked it down.  /etc/apk/keys is empty.  You are defaulting to having device mapper claim /dev/mmcblk2, but I didn't bother encrypting my preload, so had to figure out a way around that.   Then it was easy enough to copy the keys from the preload install over and the error about untrusted repos went away. Now it has a dependency issue.

# apk upgrade
ERROR: unsatisfied constraints:
  cmd:kpartx (virtual)
  provided by: multipath-tools
  required by: postmarketos-mkinitfs-0.14.1-r1[cmd:kpartx]

Made any changes in any of that or is that just life on the edge and it will get fixed upstream in a few hours?

(09-28-2020, 06:44 PM)megous Wrote: All changes that I made have original files backed up in /.xnux dir. I didn't make any changes related to package management. If keys file is empty it was empty in the original image too.

I also don't use device mapper, so not sure what that comment is about.

(10-10-2020, 08:04 PM)Braveheart Wrote: Hi @megous. Thank you very much for your enormous work.

Will this be the last image of the multi-distro? In case it is not the last one, when will you update it?

I ask if I should download the image now or wait a bit for it to update.

Will you add more operating systems?

(10-13-2020, 05:22 AM)LinAdmin2 Wrote:

(10-10-2020, 08:04 PM)Braveheart Wrote: Hi @megous. Thank you very much for your enormous work.

Will this be the last image of the multi-distro? In case it is not the last one, when will you update it?

I ask if I should download the image now or wait a bit for it to update.

Will you add more operating systems?

Since you did not yet get an answer I assume that this multi boot has rather been an intersting one time gimmick.

(09-27-2020, 10:22 AM)laaglu Wrote: Hi megous,

Many thanks for your work, it is great and truly appreciated. The time from press-power-on to pboot-main-screen is so incredibly fast.

Currently my most wanted feature would be as bujiraso suggested 'Boot to eMMC' (either as an option in the menu or as a key combination or both). I have tried power+volume-up but that did not seem to work. So currently I do a lot of micro-sd shuffling to switch between eMMC and pboot (too bad the micro-sd is not accessible without opening the phone on the current model, I hope Pine will consider an external slot in a future design). Is there a way to get boot to eMMc to work with present version, maybe by patching a file or something other tweak?

Lukas

(10-13-2020, 10:49 AM)wibble Wrote:

(10-13-2020, 05:22 AM)LinAdmin2 Wrote:

(10-10-2020, 08:04 PM)Braveheart Wrote: Hi @megous. Thank you very much for your enormous work.

Will this be the last image of the multi-distro? In case it is not the last one, when will you update it?

I ask if I should download the image now or wait a bit for it to update.

Will you add more operating systems?

Since you did not yet get an answer I assume that this multi boot has rather been an intersting one time gimmick.

Or that megous only looks at the forum from time to time, in between doing other good things that benefit the rest of us. If you're interested in doing some of the work for an updated version yourself the toolchain is published, and not hard to understand:
https://megous.com/git/pinephone-multi-boot/tree/

(10-10-2020, 08:04 PM)Braveheart Wrote: Hi @megous. Thank you very much for your enormous work.

Will this be the last image of the multi-distro? In case it is not the last one, when will you update it?

I ask if I should download the image now or wait a bit for it to update.

Will you add more operating systems?

(10-01-2020, 12:20 PM)jmorris Wrote:

(09-28-2020, 06:44 PM)megous Wrote: All changes that I made have original files backed up in /.xnux dir. I didn't make any changes related to package management. If keys file is empty it was empty in the original image too.

I also don't use device mapper, so not sure what that comment is about.

Haven't used pmbootstrap yet, just been using the preload so far.  So can't say if it installs keys, but one would think so or it wouldn't work?  alpine-keys looks like where some of them should be installed from, not clear where the postmarketos key comes from.  Haven't found the apk equiv for rpm -qf <filename> to track down what package owns a file.

When pmos was running I couldn't mount /dev/mmcblk2p2, looking in /proc/partitions revealed dm-0 and dm-1, clearing those out allowed mounting the preload to get to the keys.  Something cranked up device mapper, so many layers to crawl through to figure out what and why. 

Also see another issue.  When running pmos from your kernel the only governors are menu and ladder, while preload pmos is running the options are "ondemand userspace conservative performance schedutil" and conservative is picked.  Difference is when connected to a USB 2.0 port the battery stays in Discharging state on your kernel because drain is always over 600mA.  On the preload it will charge to the high 90s and then begin flopping between discharging and charging.  And of course on all OS options tried to date there is nothing visible when plugged into a USB 3.0 port.  Fun.

And gotta ask a silly question.  What is the point of Arch on the image?  It boots to a text mode login and there isn't an onscreen keyboard.  Tapping the power button will do a clean shutdown to get out but can't see what else to do with it.  WiFi has to be configured first and it doesn't show a USB network device so can't ssh in.  Try a USB hub and keyboard?

EDIT:  Nope, confused on idle governors and cpufreq governors.  So back to looking for a difference between the kernels to explain the different battery behaviour.