**** BEGIN LOGGING AT Mon Jan 15 03:00:01 2018 Jan 15 05:28:05 Anybody? XD Jan 15 07:47:50 @petya230, First try the Halium reference rootfs (or the pm rootfs), get ssh connection, try to get the lxc working and some tests and then you can try to port to ubuntu touch. Jan 15 07:48:50 @petya230, http://docs.halium.org/en/latest/porting/install-build/reference-rootfs.html Jan 15 07:49:59 @Ellenjott, hm, okay! thanks Jan 15 07:50:27 question Jan 15 07:50:42 yeah? Jan 15 07:51:36 stock halium have any gui? Jan 15 07:51:50 No, not really Jan 15 07:52:21 It's the reference rootfs, it's not meant for production Jan 15 07:52:33 hm Jan 15 07:52:46 and how can i connect to the internet? xD Jan 15 07:52:49 to have ssh? Jan 15 07:53:00 It uses network over usb Jan 15 07:53:12 default? :o Jan 15 07:53:44 Yeah, otherwise you couldn't do anything, if it doesn't work Jan 15 07:53:56 m Jan 15 07:53:57 hm Jan 15 07:53:59 thanks! :D Jan 15 07:54:31 It's also all in the documentation Jan 15 07:54:53 http://docs.halium.org/en/latest/porting/debug-build/early-init.html Jan 15 07:56:26 this halium is new for me .-: Jan 15 07:56:28 ._. Jan 15 07:56:34 But i love it :o Jan 15 07:57:02 😀 Jan 15 08:04:19 for halium-7.1 there is any recommended rootfs sudoku maybe ? Jan 15 08:04:35 I've got a problem in telnet: … diagnosis.log says: … No /proc/config.gz. Enable CONFIG_IKCONFIG and CONFIG_IKCONFIG_PROC … But both configs are enable, there is just no /proc/config.gz ... Jan 15 08:04:56 @Walid, the halium reference rootfs or a plasma mobile rootfs Jan 15 08:05:20 at least for porting and getting basics working Jan 15 08:15:58 Somehow ... (I can't understand why), in telnet it booted my systems kernel (lineageos), instead of the one I've built, so no wonder why CONFIG_IKCONFIG isn't present ... 😐 Jan 15 08:17:01 what? Jan 15 08:17:08 u added it toconfig? Jan 15 08:17:15 anssdfnds I DONT DDDD: … fuck me Jan 15 08:18:27 You probably can't help me here, so don't mind Jan 15 09:59:36 In telnet: … The /target/ folder only contains a data folder, is this correct? Jan 15 12:06:51 @Ellenjott, must contain the rootfs Jan 15 12:07:38 @ErnyTech, ... seems so fixup mountpoints isn't working ... (the device is there, but nothing is mounted) Jan 15 12:07:51 I have to mount it manually Jan 15 12:10:03 Is the userdata partition mounted? Jan 15 12:48:40 nirajnikant was added by: nirajnikant Jan 15 16:14:48 hey … I got this … root@localhost:~# lxc-start -nandroid -F … rm: cannot remove '/var/lib/lxc/android/rootfs/bt_firmware/image/btfw32.tlv': Read-only file system … rm: cannot remove '/var/lib/lxc/android/rootfs/bt_firmware/image/btnv32.bin': Read-only file system … rm: cannot remove '/var/lib/lxc/android/rootfs/bt_firmware/image/btfw30.tlv': Read-only file system … rm: cannot remove '/var/lib/lxc/android/rootfs/bt_firmware/image/btnv30 Jan 15 16:14:49 system … and 100+ more line like this... … which file system is in RO? … how to fix? … I think it's system.img which is mounted in ro … but how to remount in rw mode? Jan 15 16:18:48 Do not start the container manually ... It will delete files on /data ... Jan 15 16:19:39 If it isn't started automatically, there is something to fix anyway, starting it manually doesn't help Jan 15 16:24:54 ok … and for the read only? Jan 15 16:25:05 any idea? Jan 15 16:29:34 ah yes... no more internal storage😓 Jan 15 16:44:57 when it happened to me it was caused by in problem with the systemimage Jan 15 16:50:46 yes I have to use the replace-android-image script to get a system.mount working … but it doesn't fix my non-working lxc unfortunatly :/ Jan 15 16:52:47 systemctl … => 4 failed services … apparmor.service … isc-dhcp-server.service … lxc@android.service … ureadahead.service Jan 15 16:53:05 systemctl status lxc@android Jan 15 16:54:24 https://paste.ubuntu.com/26392661/ Jan 15 17:02:24 @ErnyTech, what was your problem? Jan 15 17:03:57 @vince1171, it was the same as yours, I solved by recreating the systemimage Jan 15 17:04:39 just mka systemimage? ^^ Jan 15 17:05:15 no lol, your tree has some problems Jan 15 17:07:56 any advice where I have to look for problems/bugs? Jan 15 17:09:43 fstab and vendor Jan 15 17:09:49 I do not know much about helping you because the problem occurred as a result of changes made yesterday, and I have not yet discovered the faults Jan 15 17:10:36 okay thx anyway :) Jan 15 17:56:49 Rafa was added by: Rafa Jan 15 18:10:54 (Photo, 822x438) https://irc.ubports.com/33JapcxR/file_3801.jpg Jan 15 18:10:55 ._. Jan 15 18:11:58 @petya230, ask @JBBgameich he has script that resolve this error Jan 15 18:12:18 @petya230, @JBBgameich >< Jan 15 18:12:31 See https://github.com/JBBgameich/halium-install/blob/master/halium-install Jan 15 18:13:09 @Ellenjott, thanks Jan 15 18:13:15 That script alone won't work though, use the standalone release: https://github.com/JBBgameich/halium-install/releases/download/continuous/halium-install-standalone.sh Jan 15 18:14:37 Noticed that we have 333 members on telegram, the exact half of 666, this can't be a coincidence Jan 15 18:16:45 @Ellenjott, Also an exact opposite, in a way :) Jan 15 18:18:38 @JBBgameich, passwd error ._. Jan 15 18:18:57 but the script run ._. Jan 15 18:19:12 Can you send the log please? Jan 15 18:19:23 Which rootfs are you using btw? Jan 15 18:21:03 @JBBgameich, i use hungarian language xDD Jan 15 18:21:09 @JBBgameich, ubports-touch.rootfs-xenial-armhf.tar.gz … ubuntutouch Jan 15 18:21:23 @petya230, oh.. i need to test it with halium -.- Jan 15 18:21:43 Yeah. The ubports-rootfs might work, but I have never tested it with my script Jan 15 18:21:55 hm Jan 15 18:21:56 I: Pushing rootfs and android image to /data via ADB … 7804 KB/s (325787648 bytes in 40.764s) Jan 15 18:22:02 now its pushing xD Jan 15 18:22:07 ok, with the Ubports rootfs, the passwd error is normal I think Jan 15 18:22:13 and no real problem Jan 15 18:22:15 kk :D Jan 15 18:22:22 we will see it. Jan 15 18:22:31 its boot or not. Jan 15 18:24:52 question.. why /data? Jan 15 18:28:30 @petya230, Where else? Jan 15 18:29:05 idk xDD Jan 15 18:29:10 i got it. Jan 15 18:29:13 :D Jan 15 18:29:26 😁 Jan 15 18:29:27 Debug: Chosen rootfs is halium-rootfs-20170630-151006.tar.gz … Debug: Chosen android image is ../rootstock-ng/system.img … Debug: Chosen release is none … I: Writing rootfs into mountable image … I: Writing android image into mountable image … I: Setting up passwd for root user … Enter new UNIX password: … Retype new UNIX password: … passwd: password updated successfully … I: Running post installation tasks … I: Unmounting ima Jan 15 18:29:35 okay, with halium its good Jan 15 18:29:39 Please read the pin Jan 15 18:30:12 Fwd from bhushanshah: Please please don't paste more then 4 lines on telegram directly Jan 15 18:31:10 Btw, I think I've got a solution to get rid of the fixup mountpoints script Jan 15 18:31:31 👍 Jan 15 18:31:46 This can create the by-name mountpoints without udev … https://gist.github.com/LNJ2/848e8456e9473c157144c113a89b6139 Jan 15 18:32:13 @UniversalSuperBox, kkkk, sorry Jan 15 18:39:42 twrp says: No OS installed Jan 15 18:39:47 ._. Jan 15 18:40:02 What? Why should twrp even say anything about that Jan 15 18:40:03 but i run this script Jan 15 18:40:04 There's no OS on `/system`, just boot. Jan 15 18:40:11 Ignore it. Jan 15 18:40:15 not booting. :c Jan 15 18:40:17 xDD Jan 15 18:40:18 The system is stored on /data/rootfs.img, not /system Jan 15 18:40:42 @petya230, First, you should get a telnet connection Jan 15 18:40:47 Like described in the docs Jan 15 18:40:52 okay Jan 15 18:41:01 but device dont do anything Jan 15 18:41:10 just look in your host's demsg, maybe the device posts something there Jan 15 18:41:38 adb shell dmesg … error: device not found Jan 15 18:41:41 i have a p9 lite Jan 15 18:41:46 host's dmesg Jan 15 18:41:56 without adb shell, just your pc's shell Jan 15 18:42:11 oh, kk Jan 15 18:42:46 can i copy it? Jan 15 18:42:53 9 line :l Jan 15 18:42:54 xD Jan 15 18:43:15 (Photo, 822x438) https://irc.ubports.com/HjzSZJmi/file_3803.jpg Jan 15 18:44:42 @petya230, use a pastebin service in the future (paste.debian.net, paste.ubuntu.com, paste.kde.org) Jan 15 18:45:00 okay Jan 15 18:45:01 Ok, the device really gives no sign of life .... Jan 15 18:45:07 is /data encrypted maybe? Jan 15 18:45:14 hm Jan 15 18:45:35 nope, coz i format it Jan 15 18:45:57 f2fs Jan 15 18:45:58 its problem? :l Jan 15 18:46:23 nvm, i try with ext4 Jan 15 18:46:24 xD Jan 15 18:47:35 wowow Jan 15 18:47:41 now its make ssh Jan 15 18:47:58 last time its not do this Jan 15 18:48:25 oh, ssh already, nice! So it's already booted into the rootfs, not only initrd Jan 15 18:48:30 nononon Jan 15 18:48:37 in the halium script Jan 15 18:49:02 (Photo, 822x438) https://irc.ubports.com/o0qYMKXS/file_3805.jpg Jan 15 18:49:35 ok, the script can regenerate the ssh key of the device, so not all devices use the same key. That works only if you tell the script which sort of rootfs you are using (by adding halium or pm at the end of the command line) Jan 15 18:50:07 @JBBgameich, oh, i see :o … i dont tell the script to make " halium" 😂 Jan 15 18:50:34 pushing Jan 15 18:56:19 okay, its not boot.. Jan 15 18:56:24 maybe its kernel problem? Jan 15 18:56:45 kernel or boot image offsets are the most likely problems Jan 15 18:56:53 kernel? Jan 15 18:56:54 hm Jan 15 18:56:57 wait Jan 15 18:57:02 kernel = bootimg Jan 15 18:57:15 ? Jan 15 19:06:30 mountfix can be wrong? Jan 15 19:06:45 maybe this is the problem ._. Jan 15 19:10:34 @petya230, fixup mountpoints isn't used at all for installing the image Jan 15 19:12:46 hm Jan 15 20:21:25 @petya, when you say it doesn't boot, what EXACTLY are you observing Jan 15 20:23:36 maybe its booting anyway, just doesn't show anything visibly Jan 15 20:23:44 try getting last_kmsg Jan 15 20:24:12 (Document) https://irc.ubports.com/OQQl50ea/file_3806.JPG Jan 15 20:24:17 nope, nothing! … its not how anything. … no adb Jan 15 20:24:36 Halium doesn't support adb anyway Jan 15 20:24:41 You have to use ssh Jan 15 20:24:46 @JBBgameich, ssh* Jan 15 20:24:49 sry Jan 15 20:24:55 no usb tether Jan 15 20:25:20 output of `ip a`? … and `lsusb`? Jan 15 20:25:47 @Ellenjott, nothing Jan 15 20:25:54 and its rebooting always Jan 15 20:26:01 ah ok Jan 15 20:26:13 then you have to check the last_kmsg from your recovery Jan 15 20:26:24 @Ellenjott, hmm. in terminal? Jan 15 20:26:42 its in the guide Jan 15 20:26:46 boot into recovery and then use adb shell Jan 15 20:27:35 It's a great advantage if you read the guide completely Jan 15 20:29:05 @Ellenjott, i reading >< Jan 15 20:29:32 👍 Jan 15 20:30:53 adb shell cat /proc/last_kmsg > ~/last_kmsg Jan 15 20:30:55 :D Jan 15 20:30:58 u see? :P Jan 15 20:41:50 could you get it? Jan 15 20:44:50 adb pull /proc/last_kmsg Jan 15 20:55:27 @doniks, not yet, i needed to rebuild the kernel + systemimage Jan 15 21:06:00 cat: can't open '/proc/last_kmsg': No such file or directory Jan 15 21:06:01 xDD Jan 15 21:06:59 soo Jan 15 21:07:02 what is this? Jan 15 21:08:24 there are some configs needed do you have them? Jan 15 21:08:36 @doniks, mean? which configs? Jan 15 21:08:39 in the kernel? Jan 15 21:08:42 yes, i have all Jan 15 21:08:48 "all" Jan 15 21:08:54 hu Jan 15 21:09:12 i cant add 2 conf Jan 15 21:09:13 wait Jan 15 21:09:37 CONFIG_FHANDLE=y Jan 15 21:09:38 CONFIG_SCHED_DEBUG=y Jan 15 21:09:43 this two Jan 15 21:10:29 i think they dont matter here Jan 15 21:10:45 @doniks, i think it too xD Jan 15 21:10:55 is the usb iserial saying anything? Jan 15 21:11:21 in dmesg? Jan 15 21:11:37 no Jan 15 21:12:03 there is a while .... iserial ... Jan 15 21:12:13 command in the guide Jan 15 21:12:13 while : ; do lsusb -v 2>/dev/null | grep -Ee 'iSerial +[0-9]+ +[^ ]' ; done | uniq Jan 15 21:12:18 kkk Jan 15 21:12:19 yes Jan 15 21:12:57 iSerial 1 0000:00:1d.0 … iSerial 1 0000:00:1a.0 … iSerial 1 0000:00:14.0 Jan 15 21:13:06 these repeat theyself Jan 15 21:13:20