**** BEGIN LOGGING AT Sun Jan 14 03:00:04 2018 Jan 14 09:53:13 I'm having trouble building the systemimage: … it says the recovery image is too large Jan 14 09:53:44 https://paste.kde.org/pijrpxna5 Jan 14 10:06:36 @Ellenjott, you can tune the recovery size in the device BoardConfig or so Jan 14 10:06:46 But then dont ever try to flash that one ^^ Jan 14 10:07:04 Ok :) Jan 14 10:07:11 I'll try that Jan 14 10:07:19 We dont use the android recovery normally Jan 14 10:08:11 @Walid, Hmm I think your script has an infinite loop for me Jan 14 10:10:14 maybe you have pb inn your wncss driver Jan 14 10:10:34 I was online with WiFi in Halium rootfs, so somehow it worked already Jan 14 10:10:48 But I dont remember what I did, tried a few things ;) Jan 14 10:11:13 Also in my /etc is already init.qcom.bt.sh which should enable bluetooth the same like you do Jan 14 10:11:20 @Flohack, There is only a BOARD_USERDATAIMAGE_PARTITION_SIZE var ... Jan 14 10:11:21 shall I disable this maybe later Jan 14 10:12:20 its called service hciattach Jan 14 10:12:52 @Ellenjott, Wait I take a look. Basically if you run the build with make -n it will show you where the warning comes from Jan 14 10:13:41 ah forget you must disable any other wcnss / wifi service in init.qcom.rc Jan 14 10:13:43 yes for me the size is in BoardConfig hmmm Jan 14 10:13:49 @Walid, :D Jan 14 10:14:23 @Flohack, make? not mka? Jan 14 10:14:47 @Ellenjott, same probably. Dunno if mka has options ^^ Jan 14 10:15:04 with mka -n, makes no difference Jan 14 10:15:20 and make has no targets Jan 14 10:15:33 make works only in croot from top ^^ Jan 14 10:16:00 upss .. I was in the wrong dir ... Jan 14 10:16:03 @Walid, this one too? … service wcnss-service /system/bin/wcnss_service … class late_start … user root … group system wifi … oneshot Jan 14 10:16:48 Ahhh! class main Jan 14 10:16:55 Its late_start here lol Jan 14 10:17:47 @Flohack, Still no difference in the output ... Jan 14 10:21:37 @Ellenjott, hmm Jan 14 10:21:59 there is a size check at the end of this make run. The constants are either hardcoded or derived. grep for mkbootimg Jan 14 10:22:05 somewhere it must be ^^ Jan 14 10:26:58 what rootfs did you use? Jan 14 10:37:55 @Walid, you mean mine? Jan 14 10:42:27 @doniks, Here now Jan 14 10:42:40 hallo Jan 14 10:43:20 Hello there Jan 14 10:43:39 Is there a reason to try to change kernel or device tree? Jan 14 10:44:17 if one doesn't work and the other looks more promising Jan 14 10:44:24 maybe I misunderstood the question Jan 14 10:45:31 Well I was thinking maybe my trees have a problem or something Jan 14 10:48:26 at what state is it now? did bhushansha's tips help? Jan 14 10:50:03 @doniks, Trying now Jan 14 10:50:43 which kernel and device tree are you using? Jan 14 10:51:29 Want link on git? Jan 14 10:55:20 prajjwallaad was added by: prajjwallaad Jan 14 10:57:45 @Flohack, yes Jan 14 10:58:01 @KuranKaname, yes Jan 14 10:58:57 @doniks, device: https://github.com/slim-x2/android_device_leeco_x2-old … kernel: https://github.com/celtare21/android_kernel_leeco_msm8996/tree/blue_bsi_test Jan 14 10:59:13 Also removed the sepolicy folder from device tree Jan 14 11:03:06 Александр Якубенко was added by: Александр Якубенко Jan 14 11:03:18 @Александр Якубенко, welcome Александр Jan 14 11:04:04 <Александр Якубенко> @vanyasem, Hello 😊 Jan 14 11:04:38 @doniks, dmesg still has recovery stuff? Jan 14 11:06:40 the github names look a bit random. how did you pick them? are there no lineageos repositories? Jan 14 11:07:08 @KuranKaname, Actually sepolicy is required without it, it would show error Jan 14 11:07:46 @doniks, Kernel is mine Jan 14 11:07:49 @Walid, started with 16.-04 but now back on 15.04 - problem is booting stops, but no reboot. Also nothing in last_kmsg. Somehow though it loads android init.rc bc I get a small error msg about it Jan 14 11:07:52 Device tree is from slim roms Jan 14 11:07:57 Mine is based on that too Jan 14 11:08:11 @doniks, Lineage os ones are old and out of date Jan 14 11:09:08 ok Jan 14 11:09:35 For a fact I know they work on a normal rom Jan 14 11:09:44 you can always keep it as a last resort to try other trees, but doesn't sound like its the next step Jan 14 11:09:49 that's good Jan 14 11:09:55 then I'd keep them for now Jan 14 11:10:02 Oke Jan 14 11:10:22 did you say YOUR last_kmsg is still showing you recovery logs Jan 14 11:10:30 or did you ASK ME about MINE? Jan 14 11:10:39 @doniks, dmesg still has recovery stuff? Jan 14 11:10:53 Mine Jan 14 11:11:15 [ 0.000000] Linux version 3.18.20-lineage (root@instance-1) (gcc version 4.9 20150123 (prerelease) (GCC) ) #1 SMP PREEMPT Sat Jan 13 23:18:14 UTC 2018 Jan 14 11:11:43 @KuranKaname check if your kernel configs have this … CONFIG_ANDROID_RAM_CONSOLE=y … CONFIG_ANDROID_RAM_CONSOLE_ENABLE_VERBOSE=y Jan 14 11:11:50 Yes I do Jan 14 11:11:56 mhm Jan 14 11:12:15 but Jan 14 11:12:24 Sat Jan 13 23:18:14 UTC 2018 Jan 14 11:12:29 it was build yesterday Jan 14 11:12:44 I think that IS your kernel Jan 14 11:12:51 Yeah yesterday it's from last night Jan 14 11:13:06 so, then it's not recovery stuff right? Jan 14 11:13:11 @doniks, Can't be. My kernel is 3.18.86 and built with uber 6 Jan 14 11:13:43 @KuranKaname, But the build date... Jan 14 11:13:51 I first tried a 3.18.20 kernel and it wouldn't build Jan 14 11:13:57 display-caf was failing Jan 14 11:14:03 After kernel change it works Jan 14 11:14:11 And my kernel doesn't compile if it doesn't have uber Jan 14 11:14:19 what is uber? Jan 14 11:14:26 uber gcc toolchain Jan 14 11:15:40 Also, [ 99% 2035/2038] Making initramfs : /root/halium2/out/target/product/x2/obj/ROOT/hybris-boot_intermediates/boot-initramfs.gz … 2990 blocks … It says 2990 blocks. I have it synced 2 times, first time it wouldn't compile but it was saying 3110 blocks Jan 14 11:16:03 why ANDROID_PARANOID_NETWORK=n doesn't work? Jan 14 11:16:11 New android kernel limit? Jan 14 11:16:36 @doniks, https://forum.xda-developers.com/android/software/toolchain-uber-toolchains-t3527997 Jan 14 11:17:48 lets do this differently Jan 14 11:18:14 set your CONFIG_LOCALVERSION="-bladiblub" Jan 14 11:18:18 rebuild Jan 14 11:18:20 flash Jan 14 11:18:23 boot into telnet Jan 14 11:18:28 and check with dmesg Jan 14 11:18:44 that you are actually running that kernel now Jan 14 11:18:55 @doniks, CONFIG_LOCALVERSION="-BlueScreen" Jan 14 11:18:59 Already had that changed Jan 14 11:19:00 sure Jan 14 11:19:12 I mean, it was like that already Jan 14 11:19:33 ok, but it is like that now? Jan 14 11:19:45 Yes it is and always been Jan 14 11:19:50 It was never -lineage Jan 14 11:19:52 ok boot into telnet Jan 14 11:20:04 Ok lemme flash Jan 14 11:20:25 then post the dmesg Jan 14 11:39:25 @Walid, Reverting now apparmor patches to see if this helps :) Jan 14 11:40:07 yaserpathan was added by: yaserpathan Jan 14 11:42:14 Doesn't boot anymore Jan 14 11:42:21 @doniks, After adding that param Jan 14 11:42:48 which one? Jan 14 11:43:58 @doniks, CONFIG_DEVPTS_MULTIPLE_INSTANCES=y Jan 14 11:44:40 ok, then lets see whether we can establish reliable last_kmsg debugging Jan 14 11:45:02 so far it still seemed unclear to me which log file were looking at Jan 14 11:45:16 cd .. Jan 14 11:45:21 meh Jan 14 11:45:28 so remove the config, back to telnet, confirm that log and kernel match Jan 14 11:47:58 why does the rootfs get corrupted when restarted? Jan 14 11:54:13 @ErnyTech, the lxc rootfs? Jan 14 11:54:41 I think pre-start isn't built to run multiple times Jan 14 11:55:17 but maybe even if it where the android stuff inside wouldn't behave sane if restarted?! Jan 14 12:02:44 @doniks, Ok it doesn't boot no matter what Jan 14 12:04:29 Why now mount system.img read only?? Jan 14 12:08:07 @KuranKaname, well, I guess you have to backtrack until you get it back to telnet Jan 14 12:08:28 Not sure how much you kept track of all changes you made Jan 14 12:08:37 Maybe starting over is easiest Jan 14 12:19:47 @Flohack, you can disable apparmor add apparmor=0 in cmdline Jan 14 12:20:44 @Walid, I disabled already in kernel. So now situation is: … - boot and telnet to 192.168.2.15 is possible with debug appended … - normal boot: no ssh anymore, eventually sometimes get a black screen and also a kernel panic. Smth is wrong with ubports-boot I think Jan 14 12:21:01 ah wait now I got smth Jan 14 12:21:34 I got RNDIS up but no sshd Jan 14 12:21:37 damn Jan 14 12:21:50 how can this be? Jan 14 12:22:43 ah look: Jan 14 12:22:45 Starting Nmap 7.01 ( https://nmap.org ) at 2018-01-14 13:22 CET … Nmap scan report for 10.15.19.82 … Host is up (0.0096s latency). … Not shown: 999 closed ports … PORT STATE SERVICE … 22/tcp open ssh Jan 14 12:23:00 its just not using my credentials or what Jan 14 12:23:12 ssh -v Jan 14 12:23:12 use @UniversalSuperBox script to install it make ssh work fine Jan 14 12:23:17 or -vv Jan 14 12:23:19 @Walid, I used Jan 14 12:23:42 debug2: fd 3 setting O_NONBLOCK … debug1: Authenticating to 10.15.19.82:22 as 'phablet' … debug1: SSH2_MSG_KEXINIT sent … Connection reset by 10.15.19.82 port 22 Jan 14 12:23:53 did you change ip address Jan 14 12:23:58 its definitely not configured correctly Jan 14 12:24:15 no otherwise I would not get to this point Jan 14 12:24:19 10.15.19.100 Jan 14 12:24:28 not sure how the ubports rootfs likes their ssh connections Jan 14 12:24:35 password Jan 14 12:24:36 key Jan 14 12:24:37 PING 10.15.19.82 (10.15.19.82) 56(84) bytes of data. … 64 bytes from 10.15.19.82: icmp_seq=1 ttl=64 time=0.377 ms Jan 14 12:24:40 root Jan 14 12:24:42 phablet Jan 14 12:25:01 no its user phablet, and the rootstock-ng script injects all settings Jan 14 12:25:07 I check manually.... Jan 14 12:25:47 with -vv there should be way more output can you post it? Jan 14 12:26:29 @doniks, Yes but its not interesting. It shows the banner of the server, so its up ^^ Jan 14 12:26:36 I need to manually inject my PW Jan 14 12:31:06 I can't remount!! Jan 14 12:31:30 @ErnyTech, what, where Jan 14 12:39:19 I'm trying to get ubports-boot to work Jan 14 12:39:36 but I'm stuck at "I hit a nail" Jan 14 12:39:39 then telnet Jan 14 12:39:48 I think I tracked it down to https://github.com/ubports/ubports-boot/blob/master/initramfs/scripts/touch#L377 Jan 14 12:40:03 this line failing with status 255 Jan 14 12:40:12 here is my dmesg https://paste.ubuntu.com/26384482/ Jan 14 12:40:39 with some extra logging I put in prefixed with UT.init Jan 14 12:40:49 anybody has a clue? Jan 14 12:47:57 @Walid, can it be that ssh works only in xenial rootfs? Jan 14 12:48:07 I tried now vivid, and I get no RNDIS Jan 14 12:49:37 I also destroyed my kernel log again, I get only warnings from some drivers. Its impossible with this kernel config to find out when it logs correctly and when not. Its heavily customized it seems Jan 14 12:51:17 @Flohack, Vivid probably doesn't have hybris-usb, but ADB could work there Jan 14 12:51:36 @flohack, maybe you can already look at all other kinds of logs in /var/log/syslog Jan 14 12:51:58 if the rootfs boots and ssh starts there should be normal logging Jan 14 12:53:17 @doniks, Seems empty Jan 14 12:53:26 maybe its not mounted r/w? Jan 14 12:53:33 that would also explain crash of sshd Jan 14 12:53:47 but sshd is talking to you? Jan 14 12:54:16 no this time its not started Jan 14 12:54:37 disable lxc? Jan 14 12:54:43 i definitely wiped /data before to be sure its fresh Jan 14 12:55:05 hmm Jan 14 12:55:15 how was this on upstart Jan 14 12:55:26 oh upstart Jan 14 12:55:30 dunno Jan 14 12:56:10 rename the android folder :) Jan 14 12:56:46 hmm can it be just dead slow? Jan 14 12:56:48 look at this: Jan 14 12:57:14 Until I killed it by buttons: https://pastebin.com/A1kLUnkV Jan 14 12:57:36 second 11: its in android init.rc Jan 14 12:58:20 systemd-logind[1204]: Failed to start user service, ignoring: Unknown unit: user@32011.service Jan 14 12:58:23 yep its slow Jan 14 12:58:28 135 seconds after boot Jan 14 12:58:40 doesn't ubports porting guide say you need to disable all kind of "radio" stuff Jan 14 12:59:45 @doniks, hmm dunno. Did not see it now Jan 14 13:00:04 lets disable lxc Jan 14 13:00:57 https://docs.ubports.com/en/latest/porting/building-ubports-boot.html#edit-init-rc Jan 14 13:01:17 yes I think disabling lxc is a good next step Jan 14 13:01:58 damn where is this script again - those things have gone bad since upstart & system became real Jan 14 13:02:41 upstart uses initctl or something righ? Jan 14 13:02:52 oh but I'm not sure it works in chroot Jan 14 13:03:58 btw, I started a list :) Jan 14 13:04:00 https://gist.github.com/doniks/2ac14a1bb6750165bf782f62139c8aab Jan 14 13:05:59 Ok now got a bootloop finally ^^ Jan 14 13:12:14 Hmm can I somehow create the udev rules offline? Jan 14 13:13:01 @Flohack, define offline Jan 14 13:13:05 bootloop with lxc disabled? Jan 14 13:13:10 in adb. there are some files in / Jan 14 13:13:19 no bootloop but also no ssh ^^ Jan 14 13:14:13 you are in adb? Jan 14 13:14:18 yep Jan 14 13:14:19 how is / mounted? Jan 14 13:14:22 rw/ro? Jan 14 13:14:45 rw Jan 14 13:14:54 oh and to be clear you are in adb in the ubports rootfs? Jan 14 13:15:13 no currently in the adb rootfs ^^ what you want me to do? Jan 14 13:15:45 https://paste.ubuntu.com/26384691/ Jan 14 13:15:51 @SALPHA8506, any solution? Jan 14 13:16:27 @flohack, I have a hard time following. so lxc is disabled? Jan 14 13:16:46 @doniks, I made an lxc.override file with manual inside, yes Jan 14 13:17:05 ok and if you boot into the ubports rootfs what does it look like? Jan 14 13:17:11 sshd talking to you? Jan 14 13:18:05 @doniks, He talsk but hangs up. Its running but it cant give me entry. I dunno why, thats all the same with @UniversalSuperBox special script that enabled ssh. I checked the config, its password auth and a passowrwd has been set. I would love to see the error output of sshd Jan 14 13:18:41 can you try with ssh key? Jan 14 13:18:43 is password set Jan 14 13:18:59 yes Jan 14 13:19:00 i was the one that wrote the part of the script regarding setting the password Jan 14 13:19:05 it might not work correctly Jan 14 13:19:13 Ok I try again manually with chroot Jan 14 13:21:19 i think yes ssh work only in xenial, for vivid you need hack adbd binary file to start adb shell, and remove any init.usb*.rc import Jan 14 13:21:38 there is also no syslog in /var/log/ so I still doubt that it is r/o mounted Jan 14 13:22:32 for vivid some rootfs can't create syslog, strange i have this issue before Jan 14 13:23:13 or maybe it goes into some tmpfs? Jan 14 13:24:24 im on xenial now again Jan 14 13:24:49 which vivid rootfs are you using anyway> Jan 14 13:24:53 ? Jan 14 13:25:00 latest from ci.ubports Jan 14 13:25:12 i thougth ubportsonly works with xenial on halium Jan 14 13:27:14 https://github.com/ubports/docs.ubports.com/pull/67/files#diff-53e04d5e6e3e8482d46bc84fb6e51cf2R24 Jan 14 13:27:26 Right now, we only have one available. Simply download ``ubports-touch.rootfs-xenial-armhf.tar.gz`` from `our CI Jan 14 13:30:03 Ok I have to give up for the moment. Going to the airport soon, off for some days. Jan 14 13:30:25 Its a pity - I was already booting into graphical UI and now after changing a few small things its totally broken again ;) Jan 14 13:30:43 graphical in vivid? Jan 14 13:30:47 @Flohack, don't forget that porting is a strange sadism Jan 14 13:30:54 I know Jan 14 13:31:10 that's your quote Jan 14 13:31:14 to be exact Jan 14 13:32:52 I know ;) Jan 14 13:35:03 Hmm does anyone know if the fstab needs to be patched for ubports-boot? I stated my /dev/mmc... there instead of the android link, since @UniversalSuperBox had this in his docs somewhere ;) Jan 14 13:36:19 @Flohack, example wicht work for me … /dev/mmcblk0p38 /data ext4 rw,discard,nodev,noatime,nodiratime,noauto_da_alloc,nobarrier wait,check,encryptable=footer Jan 14 13:37:42 you put there rw? Jan 14 13:38:30 y Jan 14 13:39:51 hmm intersting I try. last try ^^ Jan 14 13:50:44 why radio services such as rild have to be disabled? aren't they needed to provide radio functionality or Ubuntu 16.04 starts them on its own? Jan 14 13:52:39 Some Android services conflict with ofono in 16.04 and will cause your device to reboot without warning, about 30-60 seconds after it boots. We will need to disable these services until the issue is resolved. Jan 14 13:52:45 sounds like a temp workaround Jan 14 13:52:54 don't know the issue number Jan 14 14:35:42 @mariogrip ubuntu_overlay folder is needed only for xenial ? Jan 14 14:53:17 Ugh, I keep "hitting nails" in ubports-boot does anybody know that code? Jan 14 15:10:18 * UniversalSuperBox looks at the 300 line PR I'm making Jan 14 15:10:21 Noooooo... Jan 14 15:23:54 seems I have no /root/sbin/init Jan 14 15:27:39 Do you have a `/root`? Jan 14 15:28:23 jup Jan 14 15:28:28 _log_msg "t\n" Jan 14 15:28:33 Is anything in there? Jan 14 15:28:47 (sorry wayland clipboard is killing me) Jan 14 15:28:55 /dev/loop0 on /root type ext4 (rw,relatime) Jan 14 15:29:07 ls /root/ Jan 14 15:29:09 run userdata vendor media etc boot addon.d Jan 14 15:29:11 android xbin usr lib build.prop bin lost+found Jan 14 15:29:33 /dev/loop0: 0 /tmpmnt/system.img Jan 14 15:29:58 I think it just mounted Android as its rootfs Jan 14 15:30:04 How did you install? Jan 14 15:30:29 ahh indeed looks like Jan 14 15:30:35 rootstock thingy Jan 14 15:30:46 Which one? Jan 14 15:30:48 I guess Jan 14 15:30:54 Other thing to try is `cat /proc/cmdline` Jan 14 15:31:18 cat /proc/cmdline Jan 14 15:31:20 androidboot.hardware=flo user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 vmalloc=340M cgroup_disable=memory adc datapart=/dev/mmcblk0p30 pqr break=init androidboot.emmc=true androidboot.serialno=00ffc806 bootreason=Reboot fuse_info=Y ddr_vendor=hynix androidboot.baseband=mdm asustek.hw_rev=rev_e androidboot.bootloader=FLO-04.08 Jan 14 15:31:43 I gave up today @UniversalSuperBox with ubports-boot, smth is fishy. Ssh server closed the connection just so. Now in China, lets see end of week. Everything worked already Jan 14 15:31:47 Okay, it's because system.img is the Android image Jan 14 15:32:00 Wipe the phone's data partition and install again. Jan 14 15:32:18 I've changed the code since so that it mounts ubuntu.img, completely gets around that. Jan 14 15:32:25 But that's not merged Jan 14 15:32:30 Needs lots of testing Jan 14 15:32:36 ok Jan 14 15:33:58 is this the right rootstock to use? Jan 14 15:34:01 https://docs.ubports.com/en/latest/porting/installing-16-04.html#install-system-img-and-rootfs Jan 14 15:34:40 Yep Jan 14 15:52:25 ah, ok, I think now I am at the point where @Flohack was Jan 14 15:52:35 ubports rootfs seems to be running Jan 14 15:52:37 in some way Jan 14 15:52:49 I can ping Jan 14 15:52:59 but nmap doesn't give me an ssh port Jan 14 15:54:15 @doniks, This or you connect but you get kicked again Jan 14 15:54:58 true Jan 14 15:55:11 So, SSH isn't starting Jan 14 15:55:29 Are `/data/user-data` and `/data/system-data` created? Jan 14 15:55:53 yes Jan 14 15:56:06 Anything in system-data/var/log? Jan 14 15:57:35 yes Jan 14 15:58:58 upstart/ssh.log ? Jan 14 16:00:00 no Jan 14 16:00:02 https://paste.ubuntu.com/26385579/ Jan 14 16:00:08 but adb Jan 14 16:00:14 didn't try to connect with that Jan 14 16:00:21 Does it say that it started? Jan 14 16:00:25 but then ... nmap didn't see anything Jan 14 16:00:37 adbd-emergency-shell stop/pre-start, process 1226 Jan 14 16:00:46 only line in adb log Jan 14 16:00:56 Can you mount ubuntu.img and check it out? Jan 14 16:01:05 Look in etc/init/ for ssh.override Jan 14 16:01:25 (can't see anything interesting in syslog either https://paste.ubuntu.com/26385589/ ) Jan 14 16:01:28 ok Jan 14 16:02:41 cat ssh.override Jan 14 16:02:44 manual Jan 14 16:02:47 Does halium can buildable with prebuild Kernel thanks Jan 14 16:02:48 exec /usr/sbin/sshd -D -o PasswordAuthentication=no Jan 14 16:03:00 Oh, well absolutely nothing got done there. Jan 14 16:03:19 what did you expect? Jan 14 16:03:38 Edit it, make it this: https://paste.ubuntu.com/26385598/ Jan 14 16:03:44 Did you get a passwd prompt? Jan 14 16:04:17 @kutlay1653, I wouldn't recommend it, modifications need to be made to enable features. See docs.halium.org Jan 14 16:04:25 no, I don't think so, and after a few attempts I got nothing Jan 14 16:04:47 as in: nmap said all ports are closed Jan 14 16:04:47 We dont have Kernel source code Jan 14 16:04:54 Device is etab5 Jan 14 16:05:03 Okay then. Edit the ssh conf then chroot into the image. Run `passwd phablet`. Jan 14 16:05:09 @kutlay1653, You can't port Halium to the device. Jan 14 16:05:20 hmm Thanks Jan 14 16:05:49 ohhh "start on startup" now I see, yeah on it Jan 14 16:06:54 And PasswordAuthentication=yes Jan 14 16:07:11 yea Jan 14 16:07:25 That should all be done by xenial-actuallyfixit rootstock Jan 14 16:07:32 Did the script error out? Jan 14 16:08:32 @kutlay1653, If Linux is running on the device (or android), GPL code is included which the manufaturere HAS to release. You could write them a e-mail, and if they don't give you the source, that will be a violation Jan 14 16:09:27 @UniversalSuperBox don't know anymore whether there was any erro with rootstock, I'm quite sure I am running that branch, but maybe my git expertise failed me Jan 14 16:12:28 no, sshd doesn't like me Jan 14 16:12:30 https://paste.ubuntu.com/26385652/ Jan 14 16:13:19 how do I disable lxc container in ubports? Jan 14 16:16:29 @doniks, Thats my error, too Jan 14 16:16:45 So its nothing device specific Jan 14 16:16:58 good, so it's easily reproducible. Jan 14 16:17:00 indeed! Jan 14 16:17:19 @doniks, Make an override file like ssh, for lxc-....conf Jan 14 16:17:23 `echo 'manual' > /etc/init/lxc-android-config.override` Jan 14 16:17:39 cool. willdo Jan 14 16:17:46 But disable did not help Jan 14 16:17:59 oh ok Jan 14 16:18:12 Is there no log in /system-data? Jan 14 16:18:18 I dont think its related to the container Jan 14 16:18:29 @doniks, ı will try Jan 14 16:19:53 I was getting connection reset when the read-write portion of the disk wasn't getting mounted. Jan 14 16:20:00 The overlay mounts Jan 14 16:20:18 @UniversalSuperBox, Yes thats the issue Jan 14 16:20:29 No Jan 14 16:20:34 Because user-data and system-data exist Jan 14 16:20:58 I have stuff in /data/system-data and in /data/system-data/var/log Jan 14 16:20:58 I also dont see any logs int /var/log - is that normal? Jan 14 16:21:22 @Flohack, No, it sounds like the phone is stopping very early in boot Jan 14 16:21:53 now that i think about it, I also did not get an ssh key mismatch Jan 14 16:21:55 So even `start on startup` isn't getting run. Jan 14 16:21:56 Hmm its logging in dmesg and last_kmsg Jan 14 16:22:14 Yeah, you can always do that Jan 14 16:22:23 @doniks, Thats too early when you get dusconnected Jan 14 16:22:24 That's held in the SOC's ram Jan 14 16:22:37 The key does not even come Jan 14 16:22:52 So you aren't even getting to Upstarts `startup` event. Jan 14 16:23:21 Got your `last_kmsg` handy? Jan 14 16:28:51 today for no reason, when you start halium in normal mode it corrupts the rootfs Jan 14 16:28:58 https://pastebin.com/3YEzr790 Jan 14 16:29:02 I5t happens from time to time Jan 14 16:29:29 it seems I can setup rndis network and ping the device and at the moment when I try to ssh in, the pings also stop going through Jan 14 16:29:48 Then you get connection reset? Jan 14 16:30:13 networkmanager likes to be "helpful", I've found, and resets the network when it doesn't get an IP Jan 14 16:30:14 Connection reset by 10.15.19.82 port 22 Jan 14 16:30:46 Okay, ssh isn't running again. Jan 14 16:31:29 ok, not completely repeatable, now I got the connection reset from ssh, but the pings keep going Jan 14 16:32:38 na I think sshd IS running Jan 14 16:33:31 Can you get to this control panel on your desktop? Jan 14 16:33:32 (Photo, 600x202) https://irc.ubports.com/mvMaKBy7/file_3780.jpg Jan 14 16:33:36 https://paste.ubuntu.com/26385788/ Jan 14 16:33:47 line 1 is the openssh version on my laptop Jan 14 16:34:03 line 26 is, I think, the server version on the device Jan 14 16:35:01 I'd be willing to bet that ssh would log that somewhere Jan 14 16:35:14 Possibly auth.log, possibly syslog, possibly the kernel messages Jan 14 16:36:06 I would not be willing to bet against that :) Jan 14 16:37:18 As soon as it tries to do the key exchange, it dies Jan 14 16:37:26 So I'm thinking SSH can't read or write what it wants to Jan 14 16:37:37 ah udev? Jan 14 16:37:48 Probably not Jan 14 16:39:24 hm Jan 14 16:39:28 I have stuff in both Jan 14 16:39:38 ls -l /data/system-data/var/log/ Jan 14 16:39:46 ls -l /data/mnt/var/log/ Jan 14 16:39:54 actually it looks the same Jan 14 16:40:42 You said you were booting with ubports-boot right? Jan 14 16:40:50 yes Jan 14 16:41:18 ALMOST the same Jan 14 16:41:20 https://paste.ubuntu.com/26385836/ Jan 14 16:41:50 Jan 9 01:12:31 ubuntu-phablet sshd[1038]: error: Could not load host key: /etc/ssh/ssh_host_rsa_key Jan 14 16:42:10 @UniversalSuperBox, Yes it dies prematurely, maybe wants to log, do smth in /tmp or the like Jan 14 16:42:11 There it is Jan 14 16:42:13 in /data/system-data/var/log/auth.log Jan 14 16:42:21 repeated a lot with similar errors Jan 14 16:42:38 And that, friends, is why ssh isn't working Jan 14 16:43:06 juhuu, let's go for a beer :) Jan 14 16:43:17 So I'm guessing that you don't have system-data/etc/ssh? Jan 14 16:44:29 I have something there Jan 14 16:44:31 https://paste.ubuntu.com/ Jan 14 16:44:40 uh Jan 14 16:44:54 So it's blank? Jan 14 16:45:15 pfff, I'm blank Jan 14 16:45:17 Lol broken link Jan 14 16:45:17 hang on Jan 14 16:45:36 https://paste.ubuntu.com/26385870/ Jan 14 16:45:40 but it wants more Jan 14 16:46:05 https://paste.ubuntu.com/26385872/ Jan 14 16:46:06 It's generating a dsa key Jan 14 16:46:14 Then getting upset because it doesn't have an rsa key Jan 14 16:46:22 are those other keys supposed to be created when sshd runs first? Jan 14 16:46:29 Yep Jan 14 16:50:17 It should be run by /etc/init/ssh-keygen.conf, which is set to `start on ssh` Jan 14 16:50:39 No, `start on starting ssh` Jan 14 16:51:10 https://paste.ubuntu.com/26385911/ Jan 14 16:51:19 how do those two directories interact Jan 14 16:51:25 one overlays the other? Jan 14 16:52:00 Oh, those are synced? Jan 14 16:52:03 The hell... Jan 14 16:52:18 `rm -r /data/system-data` and reboot. Jan 14 16:52:21 Let's torch it. Jan 14 16:53:16 ha, so .... sometimes .... some stuff ... gets copied over?! Jan 14 16:54:25 Always Jan 14 16:54:29 It's how the overlay mounts work Jan 14 16:54:42 For select directories, `/etc/init` being one of them apparently Jan 14 16:55:05 The configuration for that is in `/etc/system-image/writable-paths` Jan 14 16:55:25 Ahhhhhhh Jan 14 16:55:28 WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! Jan 14 16:55:30 ha Jan 14 16:55:46 `ssh.override` and `whoopsie.override` are both persistent files in the overlay Jan 14 16:56:03 So that you can edit them without changing the system image Jan 14 16:56:12 and I'm in! Jan 14 16:57:00 That's really smart, actually Jan 14 16:57:49 So you can change the startup type in system-data, then write your ssh public key into user-data... Jan 14 16:57:51 so what's inside ubuntu.img is kinda like the default, copied upon first boot Jan 14 16:58:05 then later if you change it in /system-data then that version wins Jan 14 16:58:28 Only for 'persistent\ttransition` paths in writable-paths Jan 14 16:58:38 right Jan 14 16:58:52 oh and that's normal for UT anyway that sshd is not run by default Jan 14 16:59:00 which makes sense on consumer devices Jan 14 16:59:18 Right, so we need to change how we're instaling the auth Jan 14 17:00:05 we're actually telling people that they need to Jan 14 17:00:07 https://docs.ubports.com/en/latest/userguide/advanceduse/ssh.html#configure-your-device Jan 14 17:00:27 but that procedure relies on a working device Jan 14 17:00:33 porters need a backdoor Jan 14 17:01:42 No, rootstock does it for them Jan 14 17:02:00 right Jan 14 17:02:16 but right now it doesn't do it right i guess Jan 14 17:02:26 But now I know a more reliable way to do that, just relies on the user's public key. I'll put that on my to-do list for the week. Jan 14 17:02:55 so for the moment I tink it was Jan 14 17:03:24 https://paste.ubuntu.com/26385598/ Jan 14 17:03:29 and Jan 14 17:03:39 rm -r /data/system-data Jan 14 17:07:29 If the file is edited inside the image with rootstock before system-data is created, that becomes the file Jan 14 17:07:49 If the file exists in system-data, it is used Jan 14 17:10:02 In other words... I get what happened there. Jan 14 17:25:18 hello … If the command while : ; do lsusb -v 2>/dev/null | grep -Ee 'iSerial +[0-9]+ +[^ ]' ; done | uniq … don't return anything … where do I have to begin debugging/what can be the problem? … I have no telnet or ssh … I only have a enp0s20f0u2 interface which doesn't provide a a connection... … my device is a oneplus2 Jan 14 17:26:16 You need to assign it a ip adress manually Jan 14 17:26:53 This for telnet: … ```sudo ip address add 192.168.2.1 dev enp0s20f0u2 … sudo ip route add 192.168.2.15 dev enp0s20f0u2``` Jan 14 17:27:13 Then you can connect using `telnet 192.168.2.15` Jan 14 17:35:02 telnet: Unable to connect to remote host: Network is unreachable :/ … as I said, I don't connect to enp0s20f0u2 ... … connecting... then disconnected … 10s later connecting.... then disconnected Jan 14 17:36:26 which rootfs? Jan 14 17:37:05 halium-rootfs-20170630-151006.tar.gz … given by the halium docs Jan 14 17:37:28 Sounds like it's in ssh, not telnet Jan 14 17:37:37 Rather, the rootfs has booted Jan 14 17:38:18 @UniversalSuperBox I'm now ssh'd into the ubports rootfs, but no GUI, seems lxc is not running https://paste.ubuntu.com/26386361/ Jan 14 17:38:24 any idea how to proceed? Jan 14 17:38:39 `sudo lxc-start -nandroid -F` Jan 14 17:38:57 No, starting the container manually will not rek your entire rootfs. Jan 14 17:39:02 On Ubuntu Touch Jan 14 17:39:05 same Jan 14 17:39:12 :) Jan 14 17:39:14 too late Jan 14 17:39:29 but I think it's not actually starting, so it's also not wrecking Jan 14 17:39:40 It won't anyway Jan 14 17:39:54 sudo -i Jan 14 17:40:03 `ls /var/lib/lxc/android/rootfs` Jan 14 17:40:42 @vince1171, if you run ping 10.15.19.82 , do you get a stable connection? Jan 14 17:41:20 @UniversalSuperBox, ha, it's empty! Jan 14 17:41:52 Can I get your `dmesg`? Jan 14 17:41:55 nope … no pong response... Jan 14 17:43:06 @doniks, nope … no pong response... Jan 14 17:43:44 @UniversalSuperBox https://paste.ubuntu.com/26386393/ Jan 14 17:44:08 @vince1171 did you set it up for the 10.... ip ? Jan 14 17:45:10 @UniversalSuperBox, oh it's the syslog, two boots in there Jan 14 17:45:15 `ls /android/system`? Jan 14 17:45:29 empty as well Jan 14 17:45:46 Aha, then `device is "unknown"` Jan 14 17:45:54 I think your system.img isn't in your ubuntu.img Jan 14 17:45:59 I've seen that somewhere Jan 14 17:46:20 I really don't think rootstock is completing correctly Jan 14 17:46:51 do I need to do something wrt device unknown in some build.prop or something? Jan 14 17:46:57 @doniks, how to? ^^' … via sudo ip address add 192.168.2.1 dev enp0s20f0u2 … sudo ip route add 192.168.2.15 dev enp0s20f0u2? Jan 14 17:47:09 No, the system.img is not pushed to the system correctly Jan 14 17:50:33 @vince1171 https://github.com/Halium/docs/pull/52/files Jan 14 17:51:32 If that works for you, say here. I'll merge it as soon as Travis finishes. Jan 14 17:53:18 root@localhost:~# test_hwcomposer "/system/vendor/lib/libsdmextension.so" is 64-bit instead of 32-bit "/system/vendor/lib/libsdmextension.so" is 64-bit instead of 32-bit Jan 14 17:53:21 @UniversalSuperBox, ah, I wanted to say: I'll redo the rootstock, but now the battery is empty. time for a break :) Jan 14 17:53:32 No problem Jan 14 17:55:43 @doniks, vince@vince-Ubuntu:~$ sudo ip link set enp0s20f0u2 address 02:01:02:03:04:08 … [sudo] password for vince: … RTNETLINK answers: Device or resource busy Jan 14 17:56:08 uhhh yeah Jan 14 17:56:15 unplug /replug the device? Jan 14 17:57:59 vince@vince-Ubuntu:~$ sudo ip link set enp0s20f0u2 address 02:01:02:03:04:08 … RTNETLINK answers: Device or resource busy … ... Jan 14 17:59:27 I don't think that my problem is here... … my connecction with my device try to connect and then disconnects all the time … without beeing connected even 1 second... Jan 14 18:00:16 (Photo, 1280x720) https://irc.ubports.com/W2XyTn5k/file_3782.jpg see... Jan 14 18:01:25 10 second later... Jan 14 18:01:33 (Photo, 1280x720) https://irc.ubports.com/EVVppAcx/file_3784.jpg Jan 14 18:01:40 so, when you say, "try to connect and then disconnects" are you referring to some command you enter on the commandline or some graphical notification icon? Jan 14 18:01:54 No, networkmanager is stupid Jan 14 18:02:01 When it doesn't get an IP configuration it resets the device Jan 14 18:02:06 some graphical notification icon Jan 14 18:02:14 Go to "Edit Connections", then delete "Wired Connection 2", vince. Jan 14 18:02:22 Then run the commands again Jan 14 18:04:27 this command? … sudo ip link set enp0s20f0u2 address 02:01:02:03:04:08 … with that random IP? or with the IP given by ifconfig for enp0s20f0u2? Jan 14 18:04:35 That's not an IP Jan 14 18:04:39 That's a MAC address Jan 14 18:04:49 *faceplam... Jan 14 18:04:53 You're setting the MAC address of that device Jan 14 18:05:20 vince@vince-Ubuntu:~$ sudo ip link set enp0s20f0u2 address 16:01:42:c2:40:4c … RTNETLINK answers: Device or resource busy Jan 14 18:05:28 Try the rest Jan 14 18:07:49 yahoo … vince@vince-Ubuntu:~$ ping -c 2 10.15.19.82 … PING 10.15.19.82 (10.15.19.82) 56(84) bytes of data. … 64 bytes from 10.15.19.82: icmp_seq=1 ttl=64 time=1.93 ms … 64 bytes from 10.15.19.82: icmp_seq=2 ttl=64 time=0.447 ms … —- 10.15.19.82 ping statistics —- … 2 packets transmitted, 2 received, 0% packet loss, time 1001ms … rtt min/avg/max/mdev = 0.447/1.190/1.933/0.743 ms Jan 14 18:08:06 huge thanks guys Jan 14 18:08:12 now ssh Jan 14 18:08:54 ssh working :D Jan 14 18:09:15 😄 Jan 14 18:09:16 remove that line from the PR, doniks? Jan 14 18:09:27 Also, there has to be a way to tell nm not to manage a device Jan 14 18:09:28 the one for mac setting? Jan 14 18:09:33 from the commandline Jan 14 18:09:34 yes Jan 14 18:09:57 but then I guess there are other people where the mac needs to be set? not sure tbh Jan 14 18:10:07 Nor am I Jan 14 18:10:08 but for some reason we have it in the telnet guide Jan 14 18:10:12 thanks verry much guys … be back very soon Jan 14 18:10:13 I just copied it from there Jan 14 18:10:38 I didn't want to be as verbose as in the telnet part Jan 14 18:10:44 people kept asking here Jan 14 18:11:03 but yeah, I guess the lesson learned just now is - this PR is also not the right solution :( Jan 14 20:19:26 @mariogrip for xenial, Graphic work, RIL work, wifi, bluetooth, camera, … sound not work, filemanager show nothing crash, and big problem for me is "VIRTUAL KEYBOARD" its not showing when i'm trying to put password or enter url... Jan 14 20:31:27 euuuh guys … root@localhost:~# reboot … -bash: reboot: command not found … any idea/fix/explanation? Jan 14 20:34:21 nothing said Jan 14 20:34:32 just reboot Jan 14 20:34:35 Wait longer, sometimes it takes 30 seconds until something happens Jan 14 20:34:52 yep Jan 14 20:42:15 @UniversalSuperBox for xenial, i changed libhybris-common.so.1.0.0 in /usr/lib/arm-linux-gnueabihf/ with vivid rootfs file, got sound work Jan 14 20:43:37 Huh. Jan 14 20:44:02 also keyboard work haha Jan 14 20:44:03 That'll work in your case, but not in others. Wonder if there's a good tracker for Halium-only bugs... Jan 14 20:44:08 Yeah, maliit depends on pulse Jan 14 20:46:33 Maybe Pulseaudio just needs to be rebuilt against the newer libhybris build in Xenial Jan 14 20:50:27 (Photo, 720x1280) https://irc.ubports.com/FJUj0DHv/file_3788.jpg Xenial Jan 14 21:39:00 In a handy twist, it turns out ubports-boot will commonly find the data partition without being told where it is. Jan 14 21:45:22 can't make call, there is any thing to do ? Jan 14 21:46:08 What happens Jan 14 21:52:51 don't know, i will try install last devel rootfs using channel for titan and change system;img file and add missing libhybris, and test again, i can receive call but when i try make call , nothing happen and call finish Jan 14 21:58:33 https://github.com/boulzordev/android_device_motorola_potter/commit/283260b377ab9c5239315baa6b1c0e8199b332c3 … I don't know why, but this feels like it's going to ruin everything Jan 14 21:59:06 Oh, he switched the default branch on me Jan 14 22:12:18 oh noooooo... he switched to 64-bit Jan 14 22:41:45 petya230 was added by: petya230 Jan 14 22:42:30 Hi! … i need help... >< … i made these: … systemimage … hybris-boot Jan 14 22:42:32 soo Jan 14 22:42:41 how can i make ubuntu? Jan 14 22:42:59 i dont got it.. … https://github.com/Halium/rootfs-builder/blob/ubuntu/build.sh … http://docs.halium.org/en/latest/Distribution.html#startup-sequence Jan 14 23:29:26 (Photo, 720x1280) https://irc.ubports.com/qgZ6O0mE/file_3793.jpg Jan 14 23:37:17 ESKEREEEE **** ENDING LOGGING AT Mon Jan 15 03:00:01 2018