**** BEGIN LOGGING AT Sat Jun 23 03:00:01 2018 Jun 23 05:00:30 Morning! Jun 23 05:58:06 What does the android init think 'machine name' is, I wonder? qcom, perhaps. Jun 23 06:45:25 Morning Jun 23 06:49:51 Ah no. Our kernel command line has android.boothardware=qcom. Our android has no init.'machine name'.rc. Jun 23 07:26:41 I think other targets also only have qcom.rc Jun 23 07:26:46 Or init.qcom.rc Jun 23 07:26:48 I think mido has too Jun 23 07:28:23 Herrie: As you may guess, I am trying to follow the android boot process through my onyx boot log Jun 23 07:29:01 It all looks pretty good actually. I am actually trying to identify the next problem to solve. Jun 23 07:29:52 "Unable to open '/dev/cpuset/foreground/cpus': Permission denied" is the current candidate. Jun 23 07:41:46 Are you getting UI? Jun 23 07:42:12 I have tons of errors in my log but those are "normal" Jun 23 07:43:30 Herrie: No. Lots of processes running, lots of repetition in the system log. I'm not sure how to tell what *is* working. Jun 23 07:44:07 I notice that my mako *does* have a init.mako.rc file. Jun 23 07:45:42 Then again, it *deosn't* have init.qcom.rc, so I guess those correspond. Jun 23 07:50:41 I must say it is interesting to have my mako for comparison. Jun 23 07:51:43 Its init.rc (and friends) is very different to the onyx one. Jun 23 07:59:50 A difference between Halium 5.1 and 7.1, I suppose. Jun 23 08:55:26 Yes and Onyx & mido are CAF Jun 23 08:55:33 Mako is AOSP Jun 23 09:12:23 Mako is non-caf Jun 23 09:12:37 CAF = Code Aurora Forum which is the open source effort for Qualcomm socs Jun 23 09:13:03 Herrie:Yes, I read a bit about that a few weeks ago. Jun 23 09:13:17 You have UI on your mido, I think? Jun 23 09:14:29 elvispre: Yes Jun 23 09:14:39 It could be that you need to fix a few permissions in your init.rc Jun 23 09:14:47 Might be interesting to compare your bootlog to mine. Jun 23 09:14:52 I get lines like Jun 23 09:15:05 write_file: Unable to open '/dev/cpuset/foreground/cpus': Permission denied Jun 23 09:15:06 then Jun 23 09:15:11 See soem things I did like: https://github.com/Herrie82/android_device_xiaomi_mido/commits/pgz-14.1 Jun 23 09:15:36 init: couldn't write 5 to /dev/cpuset/system-background/tasks: No space left on device Jun 23 09:15:41 Also check the ones from piggz Jun 23 09:15:47 Ta Jun 23 09:15:54 elvispre: I have the no space left ones as well Jun 23 09:16:02 That's "normal" somehow Jun 23 09:16:08 At least according to bshah Jun 23 09:16:16 Like I said, it's hard to tell which are the important errors. Jun 23 09:16:21 Compters, eh? Jun 23 09:16:26 Computers Jun 23 09:16:27 Yeah Jun 23 09:16:32 Well post a full log Jun 23 09:16:36 We can help Jun 23 09:16:42 Either me, Tofe or bshah Jun 23 09:16:51 We have seen some before probably Jun 23 09:21:24 Herrie: An excerpt https://pastebin.com/BaH5An3m Jun 23 09:46:44 luna-next: eglplatform_fbdev.cpp:35: void fbdevws_init_module(ws_egl_interface*): Assertion `0' failed. <-- could you check your /etc/luna-next/environment.conf file ? It seems you aren't using hwcompositor Jun 23 09:49:28 Tofe: See https://pastebin.com/X5rCSi4a Jun 23 09:55:55 Hmm. All the supported devices have a meta-webos-ports/meta-luneui/recipes-luneui/luna-next/luna-next-conf device folder Jun 23 09:56:22 That'll be why I just have the default environment.conf Jun 23 09:56:59 (Incidentally, the mido one seems corrupt at the end in my dev machine.) Jun 23 09:57:46 (Actually, it just has no newline at the end.) Jun 23 10:10:36 elvispre: try to use the one of mido for instance; push it with adb Jun 23 10:10:45 elvispre: Yes that should help already Jun 23 10:10:45 as you said there may be a mistake with the recipe Jun 23 10:10:48 Flashing it right now :) Jun 23 10:11:15 Seems we just didn't put an Onyx one yet: https://github.com/webOS-ports/meta-webos-ports/tree/pyro/meta-luneui/recipes-luneui/luna-next/luna-next-conf Jun 23 10:11:28 And Athene, Angler, Tissot for that matter Jun 23 10:12:43 elvispre: and if touch doesn't work, the place to fix it is : " -plugin evdevtouch:/dev/input/event1 ", where /dev/input/eventX should correspond to your touchscreen Jun 23 10:14:24 OMG! Jun 23 10:14:29 success ? Jun 23 10:14:32 I have a logo Jun 23 10:14:57 great :) Jun 23 10:15:17 and sound. But touch doesn't work. I'll try what you said :-) Jun 23 10:15:58 elvispre: to determine which eventX to choose, just use "cat /dev/input/event0" and tap the screen to see if characters appear Jun 23 10:16:33 there might be smarter ways, but this always works :p Jun 23 10:17:03 It's 3! Jun 23 10:36:02 elvispre: :) so, what's left? Jun 23 10:36:26 Tofe: I have UI, touchscreen and sound. Jun 23 10:36:36 no wifi, no bluetooth? Jun 23 10:36:49 I can control the volume with the hardware button too. Jun 23 10:36:52 No wifi Jun 23 10:36:58 No phone network Jun 23 10:37:23 but you've put a sim card ? Jun 23 10:38:09 sim card works with Oxygen OS and LineageOS, yes. Jun 23 10:38:21 No bluetooth Jun 23 10:38:37 ok Jun 23 10:38:41 But I am inclined to look at the positives right now :-) Jun 23 11:08:37 elvispre: Well the wifi and bt are usually not that hard to fix Jun 23 11:08:52 You need to make sure the defconfig compiles wifi as a module Jun 23 11:09:03 And to update meta-smartpone systemd scripts Jun 23 11:10:21 Might be useful to check mer-hybris to see what they did for onyx there: https://github.com/mer-hybris/droid-config-onyx/tree/master/sparse Jun 23 11:10:45 You'd need to update https://github.com/shr-distribution/meta-smartphone/tree/pyro/meta-oneplus/recipes-core/systemd/systemd-machine-units/onyx probably Jun 23 11:11:01 I.e. you might have a different wlan module: https://github.com/shr-distribution/meta-smartphone/blob/pyro/meta-oneplus/recipes-core/systemd/systemd-machine-units/onyx/wifi-module-load.service Jun 23 11:11:33 For SIM i.e. oFono you need https://github.com/mer-hybris/droid-config-onyx/blob/master/sparse/etc/ofono/ril_subscription.conf Jun 23 11:12:00 Need to add it here similar to https://github.com/webOS-ports/meta-webos-ports/tree/pyro/meta-luneos/recipes-connectivity/ofono/ofono-conf Jun 23 11:17:42 The PostmarketOS guys also have a port: https://github.com/postmarketOS/pmbootstrap/pull/856/files Jun 23 11:17:54 Might have some useful info in there too Jun 23 15:58:27 hi Jun 23 15:59:45 can anybody tell me what i'm doing wrong to boot the webos-ose and luneos on the raspberrypi3? Everytime i only have the console without the GUI Jun 23 16:00:31 And for LuneOS i see only a blinking cursor for some seconds and then nothing anymore Jun 23 16:01:14 i'm trying to use the current stable averytime, but for the testing is it the same issue Jun 23 16:02:22 hoshy: Our LuneOS RPi3 image is broken Jun 23 16:02:31 It builds and boots but GUI issues Jun 23 16:02:35 Not sure how to solve it Jun 23 16:02:45 I don't have a RPi3 myself so cannot work on it really Jun 23 16:03:45 :( Jun 23 16:04:01 for all versions? Jun 23 16:35:22 hoshy: I have just tried the latest webOS OSE image from http://build.webos-ports.org/webosose/raspberrypi3/ Jun 23 16:35:34 It boots into the GUI just fine for me. Jun 23 16:45:20 uuuh, thank you, i will try it Jun 23 16:46:09 hoshy: You are aware that it must be the model B and not the model B+, are you? Jun 23 16:46:25 That caught me out first time round. Jun 23 16:51:16 elvispre: i have a raspberry pi 3 model b Jun 23 16:51:44 v1.2 Jun 23 16:53:23 You should be OK then Jun 23 17:34:00 elvispre how long does it take to get your pri3 booted into the GUI? Jun 23 17:34:37 i only have a black screen since minutes :D Jun 23 17:35:16 and the green activity LED is blinking randomly Jun 23 17:40:17 hoshy: Less than one minute to boot from scratch into the GUI here. Jun 23 17:40:37 You don't even get the console login prompt at first? Jun 23 17:40:58 not on the DSi display Jun 23 17:41:15 let me check what's on HDMI Jun 23 17:41:53 I have only USB keyboard and mouse plus HDMI attached here. Jun 23 17:45:25 yes, i have a console :D Jun 23 17:46:29 i've unplugged the DSI display now for testing it Jun 23 17:47:03 currently i'm trying this image here: Jun 23 17:47:04 http://build.webos-ports.org/webosose/raspberrypi3/webos-image-raspberrypi3-master-20180615150841.rpi-sdimg.zip Jun 23 17:47:09 is that right? Jun 23 17:47:39 Yes. That is the one I tested myself earlier. Jun 23 17:48:42 mmh, i only have a console Jun 23 17:48:55 only keyboard and hdmi display connected Jun 23 17:49:27 Curious. Possibly you need a mouse as well, but I really don't think so. Jun 23 17:50:00 I would ask a question here - http://forum.webosose.org/ - if I were you. Jun 23 17:50:37 You can maybe log on to the console. Jun 23 17:51:06 i can login via root Jun 23 17:51:09 this is working Jun 23 17:51:22 but i don't know how i can boot the GUI Jun 23 17:51:22 That's something, I suppose. Jun 23 17:52:41 Use journalctl to see if there's anything useful in the logs? Jun 23 17:56:32 Stopped webos - "surface-manager.service" Jun 23 17:57:11 Couldn't create new file /var/lib/dropbear/dropbear_rsa_host_key: File exists Jun 23 17:58:13 Core dump to /usr/sbin/save-core-dump.sh surface-manafer 866 pipe failed Jun 23 17:58:59 yes... something with the surface-manager.service doesn't seems to work Jun 23 18:02:28 https://www.dropbox.com/s/4pb5370ljoa06ux/20180623_195942.jpg?dl=0 Jun 23 18:02:34 https://www.dropbox.com/s/g3dvrxddb938jtk/20180623_200012.jpg?dl=0 Jun 23 18:02:42 https://www.dropbox.com/s/3qdh62yiqlnxh43/20180623_200025.jpg?dl=0 Jun 23 18:02:52 maybe you see something more Jun 23 18:04:13 hoshy: What display? HDMI? Jun 23 18:04:50 yes **** ENDING LOGGING AT Sun Jun 24 03:00:00 2018