**** BEGIN LOGGING AT Wed Apr 25 03:00:06 2018 Apr 25 11:11:49 @mayltonfnds lets switch back to the group chat here Apr 25 11:12:09 So I understand there are two problems: Apr 25 11:12:40 1 with lxc disabled you get ssh connection refused Apr 25 11:12:55 2 with container enabled it bootloops Apr 25 11:13:06 1 - not sure right now Apr 25 11:13:16 2 - check last kmsg Apr 25 11:14:45 In order to check last_kmsg I have to boot in a bootable system after trying to boot halium, is it correct? Apr 25 11:55:48 Jup. TWRP for example Apr 25 11:57:58 Do you know how can I reboot my phone from ssh screen without holding power off? Apr 25 12:02:03 Won't it reboot my laptop? Apr 25 12:08:17 ~ # cat /proc/last_kmsg > ~/last_kmsg … cat: can't open '/proc/last_kmsg': No such file or directory Apr 25 12:09:00 I do have the lines below enabled in my kernel settings … CONFIG_ANDROID_RAM_CONSOLE=y … CONFIG_ANDROID_RAM_CONSOLE_ENABLE_VERBOSE=y Apr 25 12:11:09 What I did was the following: Apr 25 12:11:40 Login telnet 192.168.2.15 Apr 25 12:11:49 rebooted phone into recovery Apr 25 12:11:57 entered adb shell Apr 25 12:12:07 and ran cat /proc/last_kmsg > ~/last_kmsg Apr 25 12:12:15 am I wrong? Apr 25 12:25:41 I was checking some settings in my kernel and found that many are missing Apr 25 12:25:42 https://paste.ubuntu.com/p/NQWhnsQ5RZ/ Apr 25 12:26:41 Do you think my problem is related to it? Apr 25 14:45:54 Try /sys/fs/pstore/* Apr 25 14:50:22 @mayltonfnds, That /dev/pts thing looks familiar... I'd try and enable that, if possible Apr 25 15:04:30 Now I have the following files Apr 25 15:04:30 dmesg-ramoops-0.enc.z dmesg-ramoops-1.enc.z Apr 25 15:08:44 How can I read the log? Apr 25 15:09:11 .enc? Is it encrypted? Apr 25 15:09:36 My phone? no, it's not Apr 25 15:09:43 or shouldn't be Apr 25 15:09:51 No, the file Apr 25 15:10:05 What kind of file is it? `file dmesg-ramoops-0.enc.z` Apr 25 15:10:06 No idea Apr 25 15:11:22 That's weird. Look: Apr 25 15:15:42 Oh, duh. Apr 25 15:15:43 Let's see Apr 25 15:16:15 Can you use `adb pull` to get that file off your phone then work on it from your computer? Apr 25 15:16:39 let me try Apr 25 15:17:47 @gouster4, Linux Deploy should help with that Apr 25 15:18:28 (Document) https://irc.ubports.com/fgRXk6Vw.null Apr 25 15:18:30 (late to answer, but just in case) Apr 25 15:19:38 `dmesg-ramoops-0.enc.z: data` Apr 25 15:19:41 that was helpful Apr 25 15:19:58 Apr 25 15:20:24 So it's a binary ramoops Apr 25 15:20:30 what the heck Apr 25 15:20:40 Does systemd do that? Apr 25 15:22:22 I'm using hybris-recovery btw Apr 25 15:22:40 Do you think I should try with hybris-boot? Apr 25 15:23:02 (Photo, 1115x759) https://irc.ubports.com/iNOtKtGR.png yyyyep, that didn't help either Apr 25 15:23:04 I don't know how to read your log Apr 25 15:23:35 I don't know what I expected Apr 25 15:24:11 It's not a systemd journal file Apr 25 15:26:18 and with hybris-boot I cant make it reboots Apr 25 15:26:24 only forced Apr 25 15:26:39 [Edit] and with hybris-boot I cant make it reboot Apr 25 15:26:53 [Edit] only if I force it Apr 25 15:27:08 which would not help Apr 25 16:03:22 Is there a way to force a kernel panic? So the ramoops gets filled? Apr 25 16:03:51 Maybe with some delayed systemd "service" Apr 25 16:15:19 @mayltonfnds can you get into hybris-recovery & telnet and paste the output of dmesg and mount Apr 25 16:15:50 sure Apr 25 16:15:55 give me a minute Apr 25 16:16:03 I have made some changes in kernel Apr 25 16:22:06 @dohniks https://paste.ubuntu.com/p/J6Qm4tGJfZ/ Apr 25 16:23:03 ls / /target Apr 25 16:23:46 https://paste.ubuntu.com/p/Z3QJCMfFf2/ Apr 25 16:25:47 losetup -a Apr 25 16:27:03 # losetup -a … /dev/block/loop0: 0 /data/rootfs.img Apr 25 16:29:06 (confused) Apr 25 16:29:26 (Photo, 720x1280) https://irc.ubports.com/PFotOlVy.png Apr 25 16:29:35 😂😂 Apr 25 16:29:43 you mount /data/rootfs.img as loop0 - OK Apr 25 16:29:52 it's mounted at /target - OK Apr 25 16:30:15 the contents of /target look like an android system ... not a linux rootfs ?!?! Apr 25 16:30:39 ls -il /data Apr 25 16:30:44 And I did format my data Apr 25 16:31:28 https://paste.ubuntu.com/p/qxHNrxBCBC/ Apr 25 16:33:34 how did you install onto the device? Apr 25 16:41:46 I think your rootfs.img is wrong Apr 25 16:42:11 format data again in twrp and reinstall Apr 25 16:42:13 How to get ..for OPO Apr 25 16:42:39 Is that stable enough? Apr 25 16:45:24 @dohniks, Using someone's install Apr 25 16:45:36 I don't remember whom Apr 25 16:47:08 Can you mount the rootfs.img manually when the phone is booted into recovery mode, or is there some error message? Apr 25 16:48:20 @mayltonfnds, I think it mounts ok, just the content is surprising Apr 25 16:49:41 shouldnt it just be Apr 25 16:49:45 usr bin sbin lib Apr 25 16:49:46 ... Apr 25 16:51:07 That looks like a system.img Apr 25 16:51:22 I think the install went wrong Apr 25 16:51:46 Something interesting is that halium-install system image partition is 160mb by default, but my system.img is 523mb Apr 25 16:51:56 so I have to change it to 560mb Apr 25 16:52:56 @dohniks, But even if the installation did go wrong, why should the system.img get used as rootfs...? Apr 25 16:53:39 no, I think he DOES mount the file called "rootfs.img", but it CONTAINS the android stuff Apr 25 16:53:58 When I use default installer, i got the following error Apr 25 16:54:00 unpacking rootfs tarball to system-image ... error: device not found Apr 25 16:55:15 @lambdaperl[m], The only script that works for me is this one Apr 25 16:56:15 Maybe this script simply contains a huge bug and uses the wrong image Apr 25 16:56:45 Did you already try https://github.com/JBBgameich/halium-install? Apr 25 16:57:06 So what am I suppose to do? Default script does not give any clue about the problem Apr 25 16:58:24 uhhh I might have seen that before :) the loop mounts on twrp are a bit funky Apr 25 16:58:49 Your adb installation seems to be set up wrong (Or your device is not connected or the adb server doesn't run). That device not found error is from adb not from halium-install. Apr 25 16:59:30 I think: mount a.img /mnt ; umount /mnt ; mount b.img /mnt ; cd /mnt ; tar xf /file.tar Apr 25 16:59:39 can end up writing into *a.img* Apr 25 17:00:04 because somehow even though you umount the loopdevice still points at that other file Apr 25 17:01:52 delete those two lines Apr 25 17:01:57 umount $TMPMOUNT … rmdir $TMPMOUNT Apr 25 17:02:05 then install again Apr 25 17:02:11 format in twrp first Apr 25 17:02:49 @mayltonfnds, you mean delete from this? Apr 25 17:02:55 jup Apr 25 17:03:43 the hypothesis is that by NOT umounting ANOTHER loop device is used to setup the rootfs Apr 25 17:04:08 [Edit] the hypothesis is that by NOT umounting ANOTHER loop device is used to fill the android system.img Apr 25 17:04:20 and consequently it doesn't overwrite the contents of your rootfs.img Apr 25 17:04:43 totally based on that OTHER hypothesis that the loopdevices actually DO behave as crazy as I said Apr 25 17:05:17 The Right way would of course be to get the regular install script to work for you, but hey, screw Right Apr 25 17:11:23 I removed this Apr 25 17:11:24 cleanup() … { … echo … echo "cleaning up" … mount | grep -q $TMPMOUNT 2>/dev/null && umount $TMPMOUNT … cleanup_device … rm -rf $WORKDIR … echo … } Apr 25 17:11:58 Please respect the IRC friends and don't paste more than 4 lines on Telegram. ;) Apr 25 17:12:06 uh no Apr 25 17:12:09 Oh, sorry Apr 25 17:12:16 I meant the two lines inside convert_android_img Apr 25 17:16:23 Oh, I got it Apr 25 17:16:42 I was confused, but I figured out i had already removed that lines Apr 25 17:17:08 because the original script has it and my local one doesn't Apr 25 17:17:29 oh really?! Apr 25 17:18:25 you lost me now. did you use that script or something else? Apr 25 17:18:30 https://paste.ubuntu.com/p/dpmC3JsvJR/ Apr 25 17:22:31 My steps: … 1. Flash hybris-recovery.img (hybris-boot.img doesn't work and it's not recognized) … 2. Got into TWRP and install rootfs.img and system.img by using halium-install-hostbuild … 3. Login telnet and disable lxc … 4. Configure ssh and login … Error: connection refused Apr 25 17:24:07 ugh, I thought we were working on the bootloop Apr 25 17:24:30 Wait Apr 25 17:26:01 @dohniks, I was actually looking at halium default installer. My apologies Apr 25 17:26:19 I'm confused with so many files and information Apr 25 17:26:30 😅 Apr 25 17:28:46 may I suggest again that you start over and you note down the exact steps and the exact results Apr 25 17:29:07 otherwise it is also quite confusing for everyone that wants to advise Apr 25 17:32:12 But I already now all the steps I followed. That was just a misreading Apr 25 17:33:23 I know I'm too depend and do not know even the basic Apr 25 17:33:59 [Edit] I know I'm too dependent and do not know even the basic Apr 25 17:34:00 we all started like that Apr 25 17:34:44 Now I did exactly what you told me to Apr 25 17:34:48 if you know all the steps can you write them up in one place, so it becomes clear also to others Apr 25 17:35:14 pfff, haha, I'm also saying a lot :) don't ask ME to keep track of that Apr 25 18:29:16 https://forums.ubports.com/topic/1169/porting-halium-to-leeco-le-max2-aka-x2-x820 Apr 25 19:03:48 @dohniks, of course there is :) https://github.com/doniks/crashandburn any brave soul that wants to take it for a spin? Apr 25 20:58:13 @UniversalSuperBox in theory, hallium-boot can be built outside of Android system? Apr 25 20:58:30 Sure, I guess Apr 25 20:58:50 Using the right incantation of `mkbootimg`, anything is possible Apr 25 21:00:18 I was talking to some developers of my device and three of them tried porting Halium before me Apr 25 21:00:53 One of them told me he stopped at the same point of me Apr 25 21:01:58 would be interesting to properly package Android kernel on Gemini PDA Apr 25 21:03:15 What do you mean? Apr 25 21:03:49 Building a proper debiab package probably Apr 25 21:03:57 [Edit] Building a proper debiabn package probably Apr 25 21:04:15 [Edit] Building a proper debian package probably Apr 25 21:04:36 @mayltonfnds, I wonder, if you mount the system image are there things in the directory `/etc/ssh/`? Apr 25 21:04:45 @mayltonfnds, [Edit] I wonder, if you mount the rootfs image are there things in the directory `/etc/ssh/`? Apr 25 21:05:48 @JBBgameich, For easy testing you can use make deb-pkg in the kernel directory. Abootimg should be able to produce and update the bootimg if you create a bootimg.cfg for the device. Apr 25 21:06:34 @UniversalSuperBox, Can I try this in the computer without installing it on the phone? Apr 25 21:08:00 @mayltonfnds, No, I'm trying to see if it's creating the keys Apr 25 21:08:20 I see Apr 25 21:08:41 I'll try that Apr 25 21:08:51 Let me backup everything again Apr 25 21:29:01 @UniversalSuperBox, to do this I should adb shell and look what is inside this, right? Apr 25 21:29:23 You'll need to boot the device first Apr 25 21:29:35 And then after you reboot check the rootfs image for that Apr 25 21:37:01 Seems that theres no ssh inside etc Apr 25 21:37:20 only this: Apr 25 21:37:31 You need to mount the rootfs image Apr 25 21:38:33 like mount /data/rootfs.img /mnt ? Apr 25 21:38:43 I would put it somewhere else, but yes Apr 25 21:39:15 I will follow the steps in halium documentation for creating password Apr 25 21:41:53 Do you want full output Apr 25 21:41:55 ? Apr 25 21:42:20 I'd like to know what's in the ssh folder, really Apr 25 21:42:32 Nothing Apr 25 21:42:48 there is no such folder Apr 25 21:43:32 No `/etc/ssh`? Apr 25 21:43:57 as long as I can see, no 😅 Apr 25 21:44:11 `sshd`? Apr 25 21:44:52 I'm afraid no Apr 25 21:44:58 I can't find it Apr 25 21:45:09 Now why's it gone and done that... Apr 25 21:45:31 That's after you've allowed it to boot the rootfs from hybris-recovery, huh? Apr 25 21:45:38 I mounted /data/rootfs.img inside /a Apr 25 21:45:47 navigate into /etc Apr 25 21:45:54 and looked there Apr 25 21:45:56 no ssh Apr 25 21:46:11 Right, and the phone has tried to boot the rootfs once now? Apr 25 21:50:09 Yes Apr 25 21:50:20 I tried echo continue > /init-ctl/stdin Apr 25 21:55:15 Just for you to know, I'm using halium-rootfs-20170630-151006 Apr 25 22:52:03 @NotKit, I was using linux deploy, but now im trying to not use it, so im searching for solution. Apr 25 23:27:49 hmm it appears i have run into an issue Apr 25 23:27:52 https://paste.ubuntu.com/p/MC7GG8y9WS/ Apr 25 23:28:14 i got this when compiling hybris-boot Apr 25 23:29:42 for nexus 6p Apr 25 23:42:48 other people have had this problem but i cant find a solution Apr 25 23:45:47 https://github.com/usb-bullhead-ubuntu-touch/kernel_msm/commit/fe4569e75e083bd7608c7dadc4a44d663a57818a Apr 25 23:45:55 I think I fixed it this way, but I have no idea how I happened on that Apr 25 23:50:05 ah pure try out found a solution hope this works Apr 25 23:50:21 Yeah, I'm guessing my way broke things Apr 26 01:29:32 my kernel booted Apr 26 01:29:46 (im pretty sure) Apr 26 01:31:16 there was no rootfs in /data Apr 26 01:31:24 so ive got to fix my fstab Apr 26 01:31:25 anyway goodnight Apr 26 01:33:37 @UniversalSuperBox, No idea, dude? Apr 26 01:34:02 No, not really... and your board gives kernel logs that we can't seem to read Apr 26 01:34:37 That's really strange Apr 26 01:35:11 I tried changing some settings in kernel thinking that'd make logs correctly, but no luck Apr 26 01:35:30 Dead end I think **** ENDING LOGGING AT Thu Apr 26 03:00:03 2018