1 |
Okay I got you, sure! |
2 |
|
3 |
|
4 |
|
5 |
Aug 8, 2022, 13:18 by ebo@×××××××.com: |
6 |
|
7 |
> When you get the draft of step-by-step doc, sit down and do a clean install and follow the step-by-step to verify that it works as documented. Maybe if you have someone that can beta test things, they can verify the final docs. |
8 |
> |
9 |
> Anyway, that is all I meant. |
10 |
> |
11 |
> EBo -- |
12 |
> |
13 |
> |
14 |
> On Aug 8 2022 6:58 AM, cat@××××××××.org wrote: |
15 |
> |
16 |
>> Yes! I have week 12 fully dedicated to writing documentation actually. |
17 |
>> I have written some notes but I'll also use my daily blogs to remind |
18 |
>> me of what to write about :) |
19 |
>> |
20 |
>> What do you mean by "and verification that they are really up to |
21 |
>> date", like so the older docs are really up to date? For the PinePhone |
22 |
>> Pro in particular I'd like to do something like this |
23 |
>> https://wiki.gentoo.org/wiki/PinePhone but with a lot more |
24 |
>> information. |
25 |
>> |
26 |
>> |
27 |
>> |
28 |
>> Aug 8, 2022, 02:33 by ebo@×××××××.com: |
29 |
>> |
30 |
>>> I'm not one of your mentors (I am a former GSOC intern and mentor; which explains why I am still on the lists). |
31 |
>>> |
32 |
>>> All of this sounds like wonderful progress. The one thing I have not seen you mention is documentation, quick-starts, and verification that they are really up to date. Spending a week or two on those to polish then up would be a wonderful addition. |
33 |
>>> |
34 |
>>> EBo -- |
35 |
>>> |
36 |
>>> On Aug 7 2022 8:01 PM, cat@××××××××.org wrote: |
37 |
>>> |
38 |
>>>> This week I've spent most of my time getting Gentoo musl to run on my |
39 |
>>>> PinePhone Pro and packaging mauikit apps. I have also done some minor |
40 |
>>>> testing on KDE applications and some other miscellaneous things. |
41 |
>>>> |
42 |
>>>> In my proposal I had initially planned on porting KDE applications and |
43 |
>>>> making them build on Gentoo musl the following two weeks, and then |
44 |
>>>> making sure test suites run the week following that. But I've already |
45 |
>>>> gotten kde-apps-meta installed and the programs are working well for |
46 |
>>>> the most part. Though I haven't enabled every use flag for the KDE |
47 |
>>>> apps and I haven't ran every test suite so there's definitely work to |
48 |
>>>> do left, just not 3 weeks work. So instead I asked Sam if I could |
49 |
>>>> spend some time working on getting Gentoo musl to run on my PinePhone |
50 |
>>>> Pro with Plasma Mobile as a side project. |
51 |
>>>> <!--more--> |
52 |
>>>> |
53 |
>>>> Starting with the PinePhone. The Gentoo install itself was pretty |
54 |
>>>> smooth and I didn't run into any major issues. But I really got stuck |
55 |
>>>> on some other more low level and non-Gentoo bits. |
56 |
>>>> The first issue I ran into was when I installed a new kernel onto it. |
57 |
>>>> Apparently a single developer called Megi does most of the PPP kernel |
58 |
>>>> development so I installed his kernel. Confusingly his development |
59 |
>>>> branch is called "orange-pi-5.x" and it took me some time figuring |
60 |
>>>> that out :D. Anyways, the compilation itself was straight forward, and |
61 |
>>>> the defconfig _almost_ worked well. I stole the bootloader |
62 |
>>>> configuration from PostmarketOS, rsync:ed the kernel + dtbs, and then |
63 |
>>>> changed some relevant parts in the bootloader config. Sadly the phone |
64 |
>>>> did not boot, and there was no output to be seen on the screen :/. |
65 |
>>>> After reading the wiki I found out that I could connect via serial |
66 |
>>>> through the headphone jack. I used an RS232-to-USB adapter and |
67 |
>>>> soldered it onto the internal wires of a 3.5mm cable. For output this |
68 |
>>>> did work, but when connecting TX to also get input, the output just |
69 |
>>>> got messed up and I couldn't read it. I tried to debug this and also |
70 |
>>>> seeked help from others, but ultimately couldn't get it to work. |
71 |
>>>> Luckily the only thing I needed was output because I saw in the |
72 |
>>>> bootlog that EFI stub was missing from the kernel. Enabling that and |
73 |
>>>> generating an initramfs made the phone boot! |
74 |
>>>> |
75 |
>>>> Then I started emerging some packages, and even though I had the |
76 |
>>>> charger plugged in, the phone completely discharged after a while. |
77 |
>>>> After that the phone did not want to boot and I tried all kinds of |
78 |
>>>> things, like booting from SD card, reflashing bootloader, trying |
79 |
>>>> different cables and nothing worked ... It turned out that the |
80 |
>>>> bootloader (Tow-boot) had a bug that made the phone not charge after |
81 |
>>>> the battery as emptied, and I needed to boot it into a special mode |
82 |
>>>> holding a button with a sim card opener. |
83 |
>>>> |
84 |
>>>> After that I set up distcc with cross compilation, and there came the |
85 |
>>>> second issue. "__aarch64_cas4_sync undefined symbol". I asked Sam and |
86 |
>>>> he said it probably was a distcc issue. Because of me not wanting to |
87 |
>>>> run into this again I tried the aarch64-gentoo-linux-musl-emerge |
88 |
>>>> wrapper instead. This worked for the most part, but I had trouble with |
89 |
>>>> copying over my phones configuration to /usr/.../etc/portage. |
90 |
>>>> I then learned about the ROOT, SYSROOT, and PORTAGE_CONFIGROOT |
91 |
>>>> variables. Toghether with sshfs I could easily emerge packages for the |
92 |
>>>> phone on my PC without using something slow like qemu-user, nice! |
93 |
>>>> I emerged a lot of packages like this and noticed that the program |
94 |
>>>> dispatch-conf did not honour the variables. This was easy to fix and I |
95 |
>>>> PR:ed it here https://github.com/gentoo/portage/pull/881. |
96 |
>>>> |
97 |
>>>> I have also created a lot of ebuilds for Mauikit apps, these are cross |
98 |
>>>> platform KDE applications that look great on smaller devices like |
99 |
>>>> phones. https://github.com/gentoo/kde/pull/910/commits. They also work |
100 |
>>>> great on my PC. |
101 |
>>>> |
102 |
>>>> All in all I've spent most my time this week working on the PinePhone, |
103 |
>>>> and the two following weeks I'll do a lot of testing for the KDE |
104 |
>>>> applications. |
105 |
>>>> |