| T42_ | <pachof> Sorry, I have given up on improving the port, if you are really interested I can help you with some things such as fingerprinting, or rpm compilations (re @XAP2P: Oh wow, someone inte...) | 03:45 |
|---|---|---|
| T42_ | <zhainhart> Hi all, could i start porting sailfish OS using AOSP ? Or better to use lineage as a base android OS ? | 08:22 |
| T42_ | <zhainhart> I want to try to porting my android 🙏 | 08:22 |
| T42_ | <ItsNikopol> https://docs.sailfishos.org/Develop/HADK/SailfishOS-HardwareAdaptationDevelopmentKit-4.5.0.19.pdf | 08:52 |
| T42_ | <ItsNikopol> | 08:52 |
| T42_ | <ItsNikopol> Read HADK Guide. It recommends using Lineage/Cyanogen as base (re @zhainhart: Hi all, could i star...) | 08:52 |
| T42_ | <zhainhart> From that page it says AOSP can also used as android base, but ligeage/cyanogen are recommended ? : https://irc.thaodan.de/.imgstore/4ab62e36/file_5873.jpg | 09:23 |
| T42_ | <elros34> you can use aosp too. Official devices from jolla and few ports too are based on AOSP: https://docs.sailfishos.org/Develop/HW_Adaptation/Sailfish_X_Xperia_Android_11_Build_and_Flash/ | 09:38 |
| T42_ | <elros34> @pachof so reverting 2 skip_initramfs commits didn't help? | 09:40 |
| T42_ | <NotKit> or you can use skip on building Android parts altogether as long as the device is Treble and has kernel sources (like Halium ports use prebuilt image) | 09:40 |
| T42_ | <NotKit> or you can use skip on building Android parts altogether as long as the device is Treble and has kernel sources (like Halium ports use prebuilt image of Android container) (edited) | 09:40 |
| T42_ | <zhainhart> Thanks (re @elros34: you can use aosp too...) | 10:03 |
| T42_ | <zhainhart> Btw is there anyone here are doing porting for Nothing Phone 1 ? | 10:04 |
| mal | I haven't heard anyone porting for that yet | 11:24 |
| T42_ | <zhainhart> Thanks mal (re @SailfishFreenodeIRCBridgeBot: <mal>I haven't heard...) | 11:32 |
| T42_ | <pachof> You mean that I reverted 2 commits that are in the kernel, which Xiaomi put in? (re @elros34: @pachof so reverting...) | 14:54 |
| T42_ | <pachof> Sorry I forgot not to reply | 14:55 |
| T42_ | <pachof> How do I find those skip-initramfs commits? | 14:57 |
| T42_ | <pachof> @elros34 | 15:00 |
| T42_ | <elros34> like I said search for skip_initramfs in hadk-hot, it has instruction what to do | 15:18 |
| T42_ | <elros34> if you search in birdzhang's changes then you will also find it: https://github.com/sailfish-on-ginkgo/kernel_xiaomi_ginkgo/commit/da9d26e355ce9bee1cbdb2cbf2d04bb4ed5bc29e | 15:21 |
| T42_ | <pachof> This? https://github.com/MiCode/Xiaomi_Kernel_OpenSource/commit/bb89c2c16c997f60a3c2228a86fbf28a6a656431 | 15:40 |
| T42_ | <elros34> yes but I suggest you to make this one line change instead | 15:42 |
| T42_ | <pachof> I found it https://github.com/MiCode/Xiaomi_Kernel_OpenSource/commits/ginkgo-p-oss/init/initramfs.c | 15:43 |
| T42_ | <CuteDucky> Hi guys | 17:06 |
| T42_ | <CuteDucky> Is there a list of all supported devices officially and unofficially? | 17:06 |
| T42_ | <pachof> I'm having trouble with the kernel, I'll let you know if it works and starts up fine or at least the kernel works and enters telnet mode. | 17:25 |
| T42_ | <pachof> Ready, compile the kernel with the corrections | 19:31 |
| T42_ | <pachof> It does not start and the init.log file is not there | 19:53 |
| deathmist | @pachof *how* does it not start, just instant reboot? what even are your defconfig changes anyway if any, CONFIG_VT=y is known to break older qcom kernels without a few commit reverts at least | 19:56 |
| T42_ | <pachof> It doesn't restart, it stays on the redmi logo | 19:58 |
| deathmist | so what defconfig changes if any | 19:58 |
| T42_ | <pachof> see here : "https://github.com/pachof/ginkgo_Kernel_sailfish_beta/commit/230ed5def71d4d7632f606359162c3424df0f30f" | 20:00 |
| deathmist | I don't even see the usual RNDIS enablement, no wonder you don't get any telnet | 20:00 |
| deathmist | you want at least CONFIG_USB_CONFIGFS_RNDIS=y but on qcom also CONFIG_USB_CONFIGFS_F_GSI=n | 20:01 |
| deathmist | also if you directly edit the config like that put all your changes at the bottom, otherwise if it gets defined again later on in the file it just uses that as value in the created .config... | 20:02 |
| T42_ | <pachof> So should I try the configurations you gave me? | 20:03 |
| T42_ | <elros34> what mess in your kernel, you were supposed to change 1 line | 20:26 |
| T42_ | <pachof> I only reverted the skip-initramfs commits | 20:27 |
| T42_ | <elros34> I see 13 commits. I told you to change only one line like in birdzhang's linked commit because I suspect this will end like that | 20:28 |
| T42_ | <pachof> What file are we referring to? initramfs.c? | 20:30 |
| T42_ | <elros34> check channel history and open link to that commit | 20:31 |
| T42_ | <elros34> and like deathmist said, move all your defconfig changes at the end of file then try again | 20:34 |
| T42_ | <pachof> I just don't know what you mean with a single line, is there an easier way? | 20:34 |
| T42_ | <elros34> https://irclogs.sailfishos.org/logs/%23sailfishos-porters/latest.log.html#t2024-03-16T15:21:28 | 20:36 |
| T42_ | <pachof> but then I reverse what I did? | 20:38 |
| T42_ | <elros34> basically remove all your changes. Then make this ^ one char change and add your defconfig changes at the end of defconfig file | 20:40 |
| T42_ | <elros34> and don't add all these optional file systems like CIFS SUNRPC UDF if build fails | 20:46 |
| T42_ | <b100dian> I remember a while back that I got the advice of disabling a testing repo for a specific version after a build was completed. I don't remember from where (maybe @elros34) but was wondering if that is needed considering the testing repos are pinned for a specific version | 21:36 |
| T42_ | <elros34> depends on repo structure, if you use separate sub repo for each release then you can ignore this kind of advice | 21:38 |
| T42_ | <b100dian> No, not in this case, just bare develop/testing repos as in https://build.sailfishos.org/repositories/nemo:testing:hw:asus:sake | 21:48 |
| T42_ | <elros34> then you should disable that release before adding new one. If you don't do this then you will overwrite older release. Basically both will contains same version of packages (latest one) | 21:56 |
| T42_ | <elros34> example: https://build.sailfishos.org/project/show/nemo:testing:hw:fairphone:fp2-sibon. Building for all older repos are disabled except current one | 21:59 |
| T42_ | <b100dian> So the advice holds, but can one disable _after_ a new release is made (e.g. 4.6.0) or is it already too late? | 22:00 |
| T42_ | <Mister_Magister> yes you disable after | 22:02 |
| T42_ | <Mister_Magister> whenever you want to add new repo and do some changes | 22:02 |
| T42_ | <Mister_Magister> so that the old packages don't get yeeted/changed | 22:02 |
| T42_ | <elros34> the point is to not update for older release/break it | 22:02 |
| T42_ | <Mister_Magister> yep | 22:02 |
| T42_ | <Mister_Magister> as long as you don't touch it nothing is going to change | 22:03 |
| T42_ | <Mister_Magister> if you're going to touch it for new release, lock previous releases | 22:03 |
| T42_ | <b100dian> ok, thanks for clarifying. I was just doing it right after copypac to testing, maybe that was too early | 22:04 |
| T42_ | <Mister_Magister> thats mostly unnecessary | 22:04 |
| T42_ | <Mister_Magister> new sfos release requires new package versions but you don't want to alter what's built for prevoius version because previous version needs its own specific versions, so you lock it | 22:04 |
| T42_ | <elros34> Vlad not sure if I get you right but | 22:06 |
| T42_ | <elros34> if you don't lock old one befor copypac then you mess it up | 22:06 |
| T42_ | <elros34> for now it doesn't matter because you have only one release | 22:06 |
| T42_ | <Mister_Magister> no you mistaken him, he meant copypac from devel when creating the testing | 22:06 |
| T42_ | <Mister_Magister> yep now its whatever | 22:06 |
| T42_ | <b100dian> Yeah, assuming the previous versions were locked, I copypac, and then already lock the new one | 22:07 |
| T42_ | <Mister_Magister> don't need to lock the new one if you aren't making next one | 22:09 |
| T42_ | <b100dian> btw @Mister_Magister pinging on telegram is not possible anymore, while an IRC user can see the handles and do ping.. | 22:12 |
| T42_ | <b100dian> Because of some group member visibility changes | 22:13 |
| T42_ | <b100dian> Is this something intended? that many lurkers spamming here? | 22:13 |
| T42_ | <Mister_Magister> what do you mean you just pinged me | 22:13 |
| T42_ | <b100dian> I can only ping admins | 22:13 |
| T42_ | <elros34> He probably means your decision for disabling list of users or whatever it's called | 22:14 |
| T42_ | <b100dian> you may not see the problem but I can't use @elros for example, it doesn't autocomplete (good thing I know a friendly handle by heart). And newcomers, no way I can guess their handle | 22:14 |
| T42_ | <Mister_Magister> what my decision | 22:15 |
| T42_ | <b100dian> Maybe not yours - one of the admins' | 22:15 |
| T42_ | <elros34> one of admins, I dont remember which one | 22:15 |
| T42_ | <Mister_Magister> the handle u used is wrong its @elros34 | 22:16 |
| T42_ | <elros34> @b100dian yeah it's annoying but for example fernschreiber still remebers old names:) | 22:16 |
| T42_ | <Mister_Magister> imagine not using yottagram smh | 22:16 |
| T42_ | <b100dian> I know, I think telegram desktop also remembers, but really, interacting with new people or new people with you is having a barrier on telegram that doesn't exist on say, IRC | 22:17 |
| T42_ | <Mister_Magister> here, should be fixed | 22:17 |
| T42_ | <elros34> it is, thanks | 22:18 |
| T42_ | <Mister_Magister> no problemo | 22:18 |
| T42_ | <Mister_Magister> also yes i'm pinging myself every time i write on telegram | 22:18 |
| T42_ | <b100dian> pachof how's that new kernel of yours? | 22:18 |
| T42_ | <b100dian> 👍works indeed | 22:18 |
| T42_ | <b100dian> I just lectured a new guy that he doesn't have an username the other day(s) | 22:19 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
