| uvos | Wizzup: yes | 00:28 |
|---|---|---|
| uvos | Wizzup: and yes | 00:28 |
| uvos | you might want to build the kernel by running make localmodconfig and changing every =m to =y | 00:35 |
| uvos | thats how the bionic bootloader kernel is built | 00:36 |
| uvos | and allows you to see whats going on if, for instance, the kernel fails to find the rootfs becuase the d3's sdcard slot is connected to a different mmc port or whatever | 00:37 |
| uvos | make localmodconfig run on some other mapphone ofc | 00:37 |
| Wizzup | ok | 00:51 |
| Wizzup | uvos: so the mkbootimage output is what I give to safestrap? | 11:04 |
| uvos | if safestrap where a normal android bootloader yes | 11:04 |
| uvos | but there was some detail i am forgetting | 11:05 |
| uvos | i think you need something on /system as well | 11:05 |
| uvos | maby look at a old maemo image | 11:05 |
| uvos | they used to use safestrap | 11:05 |
| Wizzup | I think we used to use safestrap for the d4 on leste, we could maybe dig that up | 11:05 |
| uvos | yeah | 11:05 |
| uvos | or unpack a los image | 11:06 |
| uvos | and look at what it dose | 11:06 |
| uvos | or just skip safe strap and kexec from android | 11:06 |
| uvos | by unpacking safestrap and using the kexec.ko and uart.ko and its kexec binary directly | 11:07 |
| uvos | and use it via adb shell | 11:07 |
| uvos | that should also work | 11:07 |
| Wizzup | oh, kexec from adb shell in safestrap you mean? | 11:07 |
| uvos | that might also work | 11:07 |
| uvos | but i ment from normal android | 11:07 |
| Wizzup | oh, ok | 11:07 |
| uvos | just adb shell into normal android and load the .ko and then kexec your image | 11:08 |
| uvos | this works on los d4 | 11:08 |
| uvos | (but pvr ends up broken) | 11:08 |
| uvos | if you do it form safestrap pvr might even work | 11:09 |
| uvos | idk at what stage the boot process is at that point | 11:09 |
| uvos | android calling psvrinit breaks it | 11:09 |
| uvos | safestrap starts itself by hijaking the andoid userspace boot pretty early | 11:10 |
| Wizzup | parazyd: ping | 11:14 |
| Wizzup | uvos: btw you said this: | 11:15 |
| Wizzup | 21:11 < uvos> you can just lift the modules from the safestrap apk | 11:15 |
| Wizzup | 21:11 < uvos> they are in there | 11:15 |
| Wizzup | 21:11 < uvos> and its just a zip | 11:15 |
| uvos | yes | 11:15 |
| Wizzup | but I don't see them I think | 11:15 |
| Wizzup | oh they are in another zip.. | 11:16 |
| Wizzup | ok | 11:16 |
| uvos | install-files.zip yeah | 11:16 |
| uvos | i think we can just use those for clown boot too, i dont remember why i build the bionic ones myself maybe to activate some debugging | 11:17 |
| uvos | then you dont have to build ainchent gcc | 11:17 |
| Wizzup | (or just install ancient debian :p ) | 11:17 |
| uvos | yeah | 11:17 |
| Wizzup | ok, let me grab my bionic sd card, I think I build a dtb as well | 11:18 |
| Wizzup | https://dpaste.com/D5HBUV2JW | 11:19 |
| Wizzup | hang on | 11:19 |
| Wizzup | https://dpaste.com/9FCAPVKLG this is what I meant to paste | 11:19 |
| uvos | you will want to keep the bionic compatible for now | 11:20 |
| uvos | there is a check in the cpcap driver that activates a path for older cpcap regulator setup | 11:20 |
| Wizzup | good to know | 11:20 |
| Wizzup | https://dpaste.com/CYHWPLTD9 ? | 11:21 |
| uvos | looks sane | 11:21 |
| uvos | Wizzup: you need to add solana/d3 to the if at line 248 in arch/arm/mach-omap2/pmic-cpcap.c | 11:26 |
| Wizzup | ah, ok, then I'll need to build a new kernel as well | 11:28 |
| Wizzup | I was planning to re-use the bionic one | 11:28 |
| uvos | or just use the bionic compatible | 11:28 |
| uvos | to test | 11:28 |
| Wizzup | ok, yeah, I reverted to that | 11:28 |
| Wizzup | ok, I misunderstood | 11:28 |
| Wizzup | yeah the latest paste I shared is what I want to try first | 11:28 |
| Wizzup | upgrading the bionic first | 11:29 |
| Wizzup | (the sd card) | 11:29 |
| Wizzup | uvos: maybe logwrapper was the thing? | 11:47 |
| uvos | what thing? | 11:47 |
| uvos | thats the script it hijacs | 11:48 |
| Wizzup | that you tried to remember or something | 11:48 |
| Wizzup | oh, ok | 11:48 |
| uvos | safestraps injects itself there | 11:48 |
| uvos | so dose clownboot | 11:48 |
| Wizzup | uvos: hm... | 12:00 |
| Wizzup | ~ # insmod /sdcard/bootattempt/uart.ko | 12:00 |
| Wizzup | insmod: can't insert '/sdcard/bootattempt/uart.ko': invalid module format | 12:00 |
| uvos | hmmm | 12:01 |
| uvos | strange | 12:01 |
| Wizzup | <3>[ 310.889282] board_mapphone_emu_uart: version magic '2.6.35.7 SMP preempt mod_unload ARMv7 ' should be '3.0.31+ SMP preempt mod_unload modversions ARMv7 ' | 12:02 |
| Wizzup | yeah ok so safestrap has a newer kernel | 12:02 |
| uvos | thats the wron safestrap then | 12:02 |
| uvos | thats for android 4 | 12:02 |
| uvos | you need a older one | 12:02 |
| Wizzup | I mean, the safestrap works just fine | 12:02 |
| Wizzup | so you're saying I need 2.x, not 3.x ? | 12:03 |
| uvos | no | 12:03 |
| uvos | it shows the menu just fine | 12:03 |
| uvos | if you try and kexec from it it wont work either | 12:03 |
| uvos | only the stock slot will work | 12:03 |
| uvos | because thats pivot_root | 12:03 |
| Wizzup | why do they recommend this on all the docs then | 12:03 |
| uvos | no idea | 12:03 |
| Wizzup | I don't think it would make sense if it was pivot_root, since this is kernel 3.x | 12:03 |
| Wizzup | android is 2..6.35 | 12:03 |
| Wizzup | how would that even work | 12:03 |
| uvos | hmm? | 12:03 |
| Wizzup | 12:03 < uvos> only the stock slot will work | 12:04 |
| Wizzup | 12:03 < uvos> because thats pivot_root | 12:04 |
| uvos | safestrap (the menu) just runs under whatever kernel is installed in boot | 12:04 |
| uvos | and it also runs the stock slot with this kernel | 12:04 |
| Wizzup | ok, I see, I think | 12:04 |
| uvos | so that works | 12:04 |
| uvos | but if you try and boot los now | 12:04 |
| uvos | it will fail | 12:04 |
| Wizzup | ok, so what's next, I can downgrade safestrap (ugh) or go for clown boot | 12:04 |
| uvos | because that will try an kexec 3.0 | 12:04 |
| Wizzup | I kinda wanted to see it boot at least one | 12:04 |
| Wizzup | maube I'll try to do the kexec from android first | 12:04 |
| uvos | Wizzup: just unpack older safestrap | 12:05 |
| uvos | and kexec from android with it | 12:05 |
| uvos | would be what i would do next | 12:05 |
| Wizzup | ok | 12:05 |
| Wizzup | uvos: why do I need to unpack older safestrap? | 12:06 |
| Wizzup | I think the kexec stuff from safestrap 3.x (the one I have now) should be ok | 12:06 |
| Wizzup | since it manages to kexec to 3.x | 12:06 |
| Wizzup | (kernel 3.x) | 12:06 |
| uvos | oh | 12:06 |
| uvos | i thought it dident | 12:06 |
| uvos | <3>[ 310.889282] board_mapphone_emu_uart: version magic '2.6.35.7 SMP preempt mod_unload ARMv7 ' should be '3.0.31+ SMP preempt mod_unload modversions ARMv7 | 12:06 |
| Wizzup | no, so what happens is I booted to safestrap | 12:06 |
| Wizzup | which made it kexec from android to its menu | 12:07 |
| uvos | oh ok | 12:07 |
| Wizzup | and then from the menu I tried to do kexec with the android-kexec modules | 12:07 |
| Wizzup | iirc | 12:07 |
| Wizzup | which didn't work | 12:07 |
| uvos | those are the wrong modules :P | 12:07 |
| uvos | also in the menu the modules are loaded allready irc | 12:07 |
| Wizzup | no, since it kexecs to linux 3.0 with no modules | 12:07 |
| uvos | ok | 12:07 |
| Wizzup | oh, you mean it has kexec as built in | 12:08 |
| Wizzup | possible but I don't think so, because I got this when I tried kexec: | 12:08 |
| uvos | i gues this might be special on the d3 since it dosent run 3.0 natively | 12:08 |
| Wizzup | kexec_load failed: Function not implemented | 12:08 |
| uvos | so they kexec to it first | 12:08 |
| uvos | for safestrap | 12:08 |
| uvos | there must be modules for kernel 3.0 somewhere then | 12:08 |
| uvos | inside ramdisk-recovery.img | 12:10 |
| uvos | so i would suspect they are in the filesystem mounted at / while in safestrap menu | 12:10 |
| mighty17[m] | uvos: https://github.com/IMbackK/mesa/tree/mesa-pvr-meamo this branch for mesa right? or the master? | 12:11 |
| Wizzup | heh, I did insmod uart.ko from android and it kicked me out of adb shell (over usb) | 12:11 |
| Wizzup | ... obviously | 12:11 |
| uvos | yeah | 12:11 |
| uvos | you need to write a script that dose everything in one go | 12:11 |
| mighty17[m] | im trying to hack it into pmos, ie only this mesa instead of the one that pmos has | 12:11 |
| uvos | (and dosent get killed when the shell dies) | 12:11 |
| mighty17[m] | uvos: i may be wrong but if i just build it in pmos (and use jonathan bakker's other stuff ie ddk1.17) it should work right? plus i'd be doing it on a live device :P | 12:13 |
| uvos | mighty17[m]: right but pmos has this thing int its repos this is just jonathan bakkers mesa packaged for maemo leste | 12:13 |
| Wizzup | uvos: what do you mean, doesn't get killed when the shell dies? | 12:14 |
| uvos | Wizzup: if you have a script running and adb disconnects the shell dies and the script exits | 12:14 |
| uvos | you need to deamonize it is what i was saying | 12:14 |
| mighty17[m] | exactly, pmos has his mesa in the repos, but i will remove that mesa and use yours instead | 12:14 |
| Wizzup | uvos: so 'nohup' | 12:14 |
| uvos | Wizzup: right | 12:14 |
| uvos | mighty17[m]: jonathan bakkers mesa is what pmos uses by default | 12:15 |
| uvos | there is no reason for you to use that repo | 12:15 |
| uvos | you might want to use the pvr+pvr setup if chomeos/jonathan bakker mesa pvr setup is giveing you trouble | 12:16 |
| uvos | or is to slow | 12:16 |
| Wizzup | uvos: maybe this is not fatal? https://dpaste.com/DGP26BR7R | 12:16 |
| uvos | also pvr+pvr setup is hard/impossible on pmos | 12:16 |
| Wizzup | (just trying to see if that function not implemented is hthe problem or not) | 12:16 |
| uvos | as it dosent use glibc | 12:16 |
| mighty17[m] | yes it is too slow :( | 12:16 |
| uvos | well pmos uses musl so the blobs dont help you that mutch | 12:17 |
| mighty17[m] | but what im thinking is to replace his/chromium mesa with yours | 12:17 |
| uvos | mine is just chromium mesa packaged for leste | 12:17 |
| uvos | there is no code difference | 12:17 |
| mighty17[m] | oh okay | 12:17 |
| Wizzup | uvos: yeah ok looks like it doesn't work: # ./kexec -e | 12:18 |
| Wizzup | kexec failed: Invalid argument | 12:18 |
| uvos | yeah | 12:18 |
| uvos | Wizzup: thats reacting like kexec.ko is no loaded | 12:18 |
| uvos | *not | 12:18 |
| Wizzup | yeah | 12:18 |
| uvos | are you using the right binary | 12:18 |
| uvos | ? | 12:18 |
| Wizzup | so, this is me booting to safestrap 3.x menu again, with kernel 3.x | 12:18 |
| Wizzup | Linux localhost 3.0.31+ #1 SMP PREEMPT Mon Oct 15 16:58:30 PDT 2012 armv7l GNU/Linux | 12:18 |
| Wizzup | so see if what you said, that there might be .ko's for kexec somewhere in safestrap, would be true | 12:19 |
| uvos | they (hashcode) had some hacky kexec binary | 12:19 |
| Wizzup | or if it was loaded at all | 12:19 |
| uvos | that did.. something to make it work we just use that | 12:19 |
| Wizzup | I am using the safestrap kexec binary | 12:19 |
| Wizzup | that is: ./assets/install-files/etc/safestrap/kexec/kexec | 12:19 |
| uvos | there might be one version for kernel 2 and one for kernel 3 | 12:19 |
| uvos | in safestrap | 12:19 |
| uvos | thats the one for kernel 2 | 12:19 |
| Wizzup | not in the .apk at least | 12:19 |
| uvos | Wizzup: its in the ramdisk | 12:19 |
| uvos | Wizzup: i would suspect | 12:19 |
| Wizzup | find / | grep kexec didn't yield much | 12:20 |
| uvos | since they only need inside of safestrap | 12:20 |
| uvos | ok | 12:20 |
| uvos | no idea then | 12:20 |
| Wizzup | I could try to install the older safestrap if you think it makes sense (2.x) | 12:20 |
| Wizzup | I had trouble doing the kexec from android since it's so weird and locked down | 12:20 |
| uvos | ok | 12:21 |
| Wizzup | most places you cannot make files executable | 12:21 |
| Wizzup | others are not writable | 12:21 |
| Wizzup | it's a bit awkward | 12:21 |
| uvos | no not really | 12:21 |
| uvos | older safestrap | 12:21 |
| Wizzup | 'no not really' was at what? | 12:21 |
| uvos | "I could try to install the older safestrap if you think it makes sense (2.x)" | 12:21 |
| Wizzup | ok | 12:21 |
| uvos | can you post a tree of the files in the ramdisk? | 12:22 |
| Wizzup | uvos: all of the files? | 12:24 |
| Wizzup | ok | 12:24 |
| Wizzup | uvos: https://wizzup.org/out.txt | 12:26 |
| uvos | this is in safestrap? | 12:27 |
| Wizzup | uvos: yes | 12:30 |
| uvos | wierd | 12:33 |
| uvos | i have no idea how safestrap works then on d3 | 12:33 |
| uvos | https://github.com/IMbackK/bionic-clown-boot/blob/master/scripts/kexebootstart.sh | 12:33 |
| uvos | maybe try what this script dose | 12:33 |
| uvos | from android | 12:33 |
| uvos | with the modules you have for kern 2.x | 12:33 |
| uvos | the reason why i copy everything into / (a ramdisk on andorid) | 12:34 |
| uvos | is to avoid the permissions problems | 12:34 |
| uvos | ah maybe you where just missing arm_kexec.ko? | 12:36 |
| Wizzup | hm? | 12:37 |
| uvos | $BBX insmod /arm_kexec.ko <- | 12:37 |
| Wizzup | well neither of those load remember | 12:37 |
| Wizzup | in 3.x | 12:37 |
| uvos | oh right | 12:37 |
| Wizzup | ok so the options are | 12:37 |
| Wizzup | 1. try from android (but pvr won't work) | 12:38 |
| Wizzup | 2. try older safestrap and hope the modules just load or are loaded | 12:38 |
| Wizzup | 3. try clownboot straight away | 12:38 |
| uvos | Wizzup: well if it boots from android with no pvr | 12:38 |
| uvos | Wizzup: then clownboot will work | 12:38 |
| Wizzup | yeah, but just as an initial attempt | 12:38 |
| uvos | 3. clownboot right away is a bad idea, as installing it breaks android leaving you with no way to recover except | 12:39 |
| uvos | to reinstal everything | 12:39 |
| uvos | so i would do 1 | 12:39 |
| uvos | and if that works you can be very sure clownboot will work on the first go | 12:39 |
| Wizzup | ok | 12:40 |
| uvos | also option 4 | 12:41 |
| uvos | try los first and see how the safestrap setup works exactly | 12:41 |
| Wizzup | would rather skip that, but yeah | 12:42 |
| uvos | also option 5 since safestrap on d3 kexecs kern 3.0 | 12:43 |
| uvos | it sounds likely that this is the same kernel tree as is stock on bionic | 12:43 |
| uvos | so the bionic modules might load | 12:43 |
| uvos | https://github.com/IMbackK/bionic-clown-boot/tree/master/kexecboot | 12:43 |
| Wizzup | /dev/mmc* doesn't exist in android, did they give it all different names? | 12:47 |
| Wizzup | oh, it's /dev/block | 12:47 |
| bencoh | :) | 12:49 |
| Wizzup | uvos: so 'chmod -x foo' doesn't work on android, is that some messed up chmod as well? | 12:49 |
| Wizzup | it says 'Bad mode' | 12:50 |
| Wizzup | I guess I can do 755 or something | 12:50 |
| uvos | no idea, every sane person just instalas busybox on android :P | 12:50 |
| Wizzup | yeah ok | 12:50 |
| Wizzup | root@cdma_solana:/# /system/xbin/busybox sh | 12:50 |
| bencoh | oh, I think I didn't :] | 12:50 |
| bencoh | but that sounds like a decent idea, yeah | 12:51 |
| Wizzup | uvos: ok, trying to load the kexec modules on android gives me this: | 12:53 |
| Wizzup | first of all insmod sas 'No such file or directory', which is not true | 12:53 |
| Wizzup | and then dmesg says: | 12:53 |
| Wizzup | <4>[ 646.709564] kexec: Unknown symbol machine_shutdown (err 0) | 12:53 |
| Wizzup | <4>[ 646.710540] kexec: Unknown symbol printascii (err 0) | 12:53 |
| Wizzup | <4>[ 646.711578] kexec: Unknown symbol machine_kexec_prepare (err 0) | 12:53 |
| Wizzup | <4>[ 646.714630] kexec: Unknown symbol machine_kexec (err 0) | 12:53 |
| Wizzup | <4>[ 646.715637] kexec: Unknown symbol machine_kexec_cleanup (err 0) | 12:53 |
| uvos | trying what where exactly | 12:53 |
| Wizzup | in android, with the files copied to an sdcard, I am trying to load the kexec kernel modules | 12:54 |
| Wizzup | /mnt/sdcard-ext/bootattempt # uname -a | 12:54 |
| Wizzup | Linux localhost 2.6.35.7-g5fa4155 #1 SMP PREEMPT Fri Feb 24 22:09:47 CST 2012 armv7l GNU/Linux | 12:54 |
| Wizzup | so basically (1) as above | 12:54 |
| Wizzup | I didn't load uart.ko yet, but truly that can't be the problem | 12:55 |
| uvos | you have to load them in the order proscribed by kexebootstart.sh | 12:55 |
| Wizzup | do you mean as logwrapper has them? | 12:55 |
| uvos | same thing yeah | 12:55 |
| uvos | its finiky i would do exactly this by hand https://github.com/IMbackK/bionic-clown-boot/blob/master/scripts/kexebootstart.sh | 12:56 |
| uvos | or rather by script | 12:56 |
| Wizzup | well I managed to make it do something, not sure if it paniced or tried to load but failed | 12:58 |
| uvos | ok thats good | 12:58 |
| Wizzup | a script like that cannot work since / is read only | 12:59 |
| uvos | mount -o remount,rw rootfs | 12:59 |
| uvos | should make it rw | 12:59 |
| Wizzup | I think I tried that and it didn't work | 12:59 |
| Wizzup | let me try it again I guess | 12:59 |
| uvos | ok | 12:59 |
| uvos | i guess android 2.3 might be different | 12:59 |
| Wizzup | could just be not being busybox mount | 12:59 |
| uvos | its not here either | 12:59 |
| uvos | its android mount | 12:59 |
| Wizzup | root@cdma_solana:/# mount -o remount,rw rootfs | 13:00 |
| Wizzup | Usage: mount [-r] [-w] [-o options] [-t type] device directory | 13:00 |
| bencoh | yeah, remount doesn't work iirc | 13:00 |
| Wizzup | it does not | 13:00 |
| bencoh | but I think you can just mount -o rw rootfs / | 13:00 |
| uvos | i mean it works on bionic | 13:01 |
| bencoh | or something similar | 13:01 |
| Wizzup | uvos: what is that init=/preinit.sh | 13:01 |
| uvos | in logwrapper? | 13:01 |
| Wizzup | in your script | 13:01 |
| uvos | oh in the cmdline | 13:01 |
| uvos | thats just kexecboot | 13:01 |
| Wizzup | k | 13:02 |
| uvos | its a script that determines some stuff about the device and then starts kexecboot proper? | 13:02 |
| uvos | s/?/. | 13:02 |
| Wizzup | well at least on serial I can 'see' that safestrap manages to kexec to 3.x ok | 13:09 |
| Wizzup | it's such a weird feeling to have a device where you can't just tell it what to boot, and that you have to jump through all these hoops | 13:10 |
| uvos | the sad reality of most consumer devices.... | 13:10 |
| uvos | yeah locked bootloaders suck | 13:10 |
| Wizzup | going to take a break from this stuff again for a bit | 13:17 |
| uvos | Motorola 1:0 Wizzup | 13:38 |
| Wizzup | :-p | 13:42 |
| Wizzup | it helps for me to take a break every few hours to think about what makes sense otherwise I just keep trying things that don't work | 13:42 |
| bencoh | :) | 13:45 |
| alex1216 | Hello everyone. Have obtained a N900 with a hope of putting Leste/pmOS onto it and using it with usual (up-to-date) apps (don't care about surfing the modern Web full of HTML5 etc.). But, of course, felt more comfortable with Fremantle+CSSU as it has all the h/w support while I was able to barely boot modern distributions (I can guess why, but for now it's an another question because now I haven't a | 21:02 |
| alex1216 | spare μSD to just DD over it). TBH, from the very begining my plan was to bring Fremantle drivers to Leste (and stick with "power user kernel" for Fremantle), to somehow update userspace of Fremantle further than CSSU using Leste's resources or to run Leste/pmOS userland in an chroot. Are these ideas are "new", or there are already some developments in this way which I can learn about? | 21:02 |
| uvos | alex1216: not impossible but you will run into loooots of issues | 21:04 |
| uvos | alex1216: like for starters modern glibc dosent even support kernels that old | 21:04 |
| Wizzup | alex1216: there is little reason to use old fremantle kernel | 21:04 |
| Wizzup | n900 kernel is in really good shape, the userspace is what needs more work | 21:05 |
| uvos | needing 3.2 at least | 21:05 |
| Wizzup | but yeah, running old userspace in chroot wont work since kernel interfaces are different | 21:05 |
| alex1216 | I'd meant running new userspace in a Fremantle's chroot. | 21:05 |
| Wizzup | bbiab | 21:06 |
| uvos | alex1216: right as i said almost impossible due to modern software requirent more modern kernels | 21:06 |
| alex1216 | Actually, my main "bottleneck" for now is lack of TLS1.2, so even a proxy-only chroot would be enough. | 21:06 |
| alex1216 | ...So, what are other major issues? | 21:12 |
| alex1216 | And what can be done about h/w support without downgrading the kernel? | 21:13 |
| uvos | all hardware, except the cameras (and even those can be patched to work), are supported by recent (ish) kernels on n900 | 21:13 |
| uvos | the kernel is not the problem | 21:14 |
| uvos | idk what issues more major than "all these apps use kernel interfaces that dont exist on 2.6.x" you are expecting | 21:15 |
| uvos | its pretty damning | 21:15 |
| uvos | i mean you could get some stuff runing by using musl chroot and selecting applications judicially | 21:16 |
| alex1216 | Simply speaking, I'm trying to combine full hardware support and up-to-date applications... :) | 21:16 |
| uvos | you allso run into the issue that n900 really dosent have any resources to spare for sutch an endeavour... | 21:17 |
| uvos | alex1216: well if "full hardware support" means fremantle to you then prepare to be disapointed or at least reduce your expectaions to the occasional app running in chroot | 21:18 |
| alex1216 | Well, I take many photos every day (including, for example, college timetable patches) and get to the college by the subway, so to use N900 as a daily driver, I need both camera support and a modern browser which can barely handle TLS1.2 and modern JS to sign in to subway's hotspot)... | 21:20 |
| uvos | really if you want to run linux apps on a phone that otherwise works and is usable as a daly driver | 21:20 |
| uvos | a chroot on a mondern android phone is a much better idea | 21:20 |
| alex1216 | uvos: It is an option too. Is it a good idea to port Leste userland to some Android container agregator (like Linux Deploy)? | 21:21 |
| uvos | someone has done that | 21:21 |
| alex1216 | oh, really? | 21:21 |
| uvos | yeah | 21:22 |
| uvos | i forget his name | 21:22 |
| uvos | its not something we support | 21:22 |
| uvos | but its possible | 21:22 |
| uvos | but really the only good long term soultion is helping us | 21:22 |
| uvos | finish leste | 21:22 |
| uvos | so its usable as a daly driver | 21:22 |
| uvos | the droid 4 is pretty close | 21:22 |
| alex1216 | Yeah, I noticed it, but it appeared that N900 is easier to find at Russian aftermarket, and I also thought that the N900 is more hackable as it had made GNU/Linux in-mind. :) | 21:25 |
| uvos | at this point the n900 is just old(er) | 21:25 |
| alex1216 | Of course, the Droid 4 was also more attractable as it appeared to be more powerful, but not hack-friendly. | 21:26 |
| uvos | not sure what hack-frendly means in this context they both run mainline linux (pinephone too) aprox equally well, with the d4 being maybe in slightly better shape. | 21:28 |
| uvos | anyhow the pont is moot you have a n900. | 21:28 |
| sicelo | alex1216: "need both camera support and a modern browser which can barely handle TLS1.2 and modern JS to sign in to subway's hotspot" ---> Fremantle easy debian chroot, using the last/latest Jessie image, and install Midori | 21:28 |
| uvos | idk if a javascript browser running on jessie is a good idea | 21:29 |
| uvos | thats asking for it on public wifi | 21:29 |
| uvos | id would try compiling something more modern against musl | 21:30 |
| uvos | just a minimal buildroot | 21:30 |
| uvos | and midory or browser of choice on that | 21:30 |
| alex1216 | sicelo: 1) Can it run Fennec too? 2) Are there still images somewhere on the Net? | 21:30 |
| sicelo | fennec has the TLS1.2 issues you want to get around | 21:31 |
| uvos | no way in hell the n900 ever gona run modern fennec | 21:31 |
| uvos | sicelo: i assume he means current fennec in chroot | 21:31 |
| alex1216 | Of course, I mean the last Fennec from Fremantle repos. :) | 21:32 |
| uvos | then what sicelo says applies | 21:32 |
| alex1216 | Okay, lemme check something. | 21:33 |
| sicelo | alex1216: maybe discuss Fremantle issues in #maemo, not here :) | 21:34 |
| alex1216 | sicelo: joining now | 21:35 |
| alex1216 | Thanks everyone. It's very good that there are developments going on to make mobile GNU/Linux great again. Because GNU/Linux is more lightweight than Android, and GNU/Linux feels really good at the desktop... | 21:57 |
| alex1216 | uvos: ...But the truth is that GNU/Linux feels good at mobiles too, but as devices like N900 or pinephone are harder to obtain and either difficult to bring up all the h/w, IMHO it would be a good idea to finish the userland to be able to run it in an Android'chroot at least. :) | 22:00 |
| uvos | alex1216: sure we could use your help with that | 22:00 |
| uvos | but no chroot in android is not a real solution imo | 22:01 |
| sicelo | --> halium :'( | 22:01 |
| uvos | http://wiki.postmarketos.org/wiki/Devices has lots of devices | 22:01 |
| uvos | proting real linux to android devices is imo the way forward long term | 22:02 |
| uvos | at least until/ if we get some traction | 22:02 |
| uvos | i would recommend any of the "main" or "Community" pmos devices or a droid4/ droid bionic if you want to mess around. | 22:03 |
| alex1216 | uvos: Hope the answer is yes. Despite I'm definitely going to work on this, I'm also going to graduate next year, so it can be uneasy, and then things can get either hard because it's Russia. | 22:04 |
| uvos | alex1216: if you want and can help us im sure Wizzup would be happy to give you a device | 22:05 |
| alex1216 | uvos: I certainly do, but also I want to get a good job and need to work on some medical documentation in order not to run into mandatory military service. :) | 22:06 |
| uvos | ok | 22:07 |
| uvos | thats life :| | 22:07 |
| alex1216 | And now I'm unsure a bit as participating in WSR this year has made me barely finish the course paper and reach end of the term with a line of As... | 22:10 |
| alex1216 | Nevermind, hope for the best. Good night (it's 1am herre). | 22:11 |
| alex1216 | here* | 22:11 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!