**** BEGIN LOGGING AT Fri Feb 08 02:59:56 2019 Feb 08 06:11:37 elvispre: atop is also quite useful Feb 08 06:23:45 Morning! Feb 08 06:24:17 JaMa: I'll take a look at that later on. Feb 08 07:14:31 Morning Feb 08 07:16:30 Kernel 4.20 "solved" the temperature issue. I now have Tdie added as value which is 27c lower v.s. Tctl. Also tuned the fan speeds a bit in the BIOS so that it's now running on performance mode instead of silent ;) That seems to shave off about 5-10c from full load temperatures. Downside of 4.20 kernel is that RCRAID is playing up with undefined symbols, so I guess I'll try 4.19 later Feb 08 07:21:33 Herrie|Laptop: I guess turning your fans on will resolve your instability issue. Feb 08 07:22:25 elvispre|cloud: Well they were on always, just at low (silent) speed. Since we have a heat pump next to it in the attic the sound from PC is not the worry :P Feb 08 07:22:36 So can up the rpms of the fans :P Feb 08 07:22:45 Still having ICE with QtWebEngine randomly Feb 08 07:22:52 Seems I'm not the only one though who has this Feb 08 07:23:05 Could be specific to this GCC version from what I've Googled Feb 08 07:24:08 But why wouldn't I see it? Intel Vs AMD, maybe? Feb 08 07:29:59 elvispre|cloud: Yeah could be Feb 08 07:30:05 It seems random on QtWebEngine somewhere Feb 08 07:30:13 One time it runs fine, other time not Feb 08 07:30:18 I guess I need to run memtest as well Feb 08 07:30:30 And sort my tmpfs :P Feb 08 12:52:44 Tofe: Trying to do some Halium stuff and getting stuk... Seems that "source build/envsetup.sh" doesn't pull in the device repo. Any idea? Feb 08 13:37:44 Herrie|Laptop: you mean the halium/devices/ script ? Feb 08 13:39:23 Tofe: I do the regular repo sync etc, then followed by the source buid/envsetup.sh which should pull in some device repo, but it doesn't it seems as per "https://docs.halium.org/en/latest/porting/build-sources.html" Feb 08 13:39:43 I would expect "including device/xiaomi/mido/vendorsetup.sh" for example Feb 08 13:40:46 https://docs.halium.org/en/latest/porting/get-sources.html#sync Feb 08 13:41:02 it's one step before Feb 08 13:41:52 Well I've done all the steps, seems OK: https://bpaste.net/show/77880793a60a Feb 08 13:46:49 Herrie|Laptop: so... you just have to start brunch and mka systemimage ? Feb 08 13:49:05 Tofe: I was doing breakfast as per our Jenkins job and that didn't work :S Feb 08 13:49:11 brunch seems to do more, but fail Feb 08 13:49:22 quite strange Feb 08 13:49:51 ooooh could it be it fails on some libcompat stuff ? Feb 08 13:50:09 they were planning to put that one in a separate repo Feb 08 13:50:22 Ah my issue now is that I cloned Halium instead of ours Feb 08 13:50:29 So halium-boot acts up :P Feb 08 13:50:32 Let me retry Feb 08 13:50:37 ah yes, a classic :) Feb 08 13:50:52 we should find a way to fix it a bit Feb 08 13:51:55 Well I should follow the right steps and document them properly :P Feb 08 13:52:43 I.e. Update https://webos-ports.org/wiki/Porting_Guide Feb 08 14:18:27 Yes... we've been talking about that for a while now :p Feb 08 15:18:33 Tofe: yeah I guess I should just start with it LOL ;) Feb 08 15:29:50 well, me too... Feb 08 15:32:00 Herrie|Laptop: I had taken some notes for Rosy port: https://bpaste.net/show/6b4f1522d4f4 Feb 08 15:57:24 Tofe: Ah those are helpful :) Feb 08 15:57:33 Now getting "ninja: error: unknown target 'bacon', did you mean 'chkcon'?" Feb 08 15:57:43 Could be my newer 18.04 box causes issues somehow, not sure Feb 08 16:04:04 Herrie|Laptop: you want tissot, not bacon Feb 08 16:05:44 Tofe: I'm doing: brunch lineage_tissot-userdebug Feb 08 16:06:58 Let me try mido Feb 08 16:33:25 Also no go: https://bpaste.net/show/989b77c61b60 Feb 08 16:34:59 unknown target 'bacon', did you mean 'chkcon'? <- I don't think anyone could confuse 'bacon' with 'chicken' to be honest ;) Feb 08 18:54:21 Herrie: bacon is a oneplus target, in case one of your scripts has some special handing for that. Feb 08 20:19:23 elvispre: I know, but it's really weird Feb 08 20:19:30 I suspect it's a 18.04 issue somehow Feb 08 20:19:40 I get different errors with other targets Feb 08 20:20:05 BTW my rcraid started working again when I moved to 4.19.20 from 4.20.6 kernel Feb 08 20:20:23 There's nothing in 4.20 kernel changelog that indicates it should break my rcraid, but it somehow does Feb 08 20:22:39 Herrie|Laptop: It's a good job you enjoy tinkering, eh? :) Feb 08 20:23:24 elvispre: Well all the main machine linux stuff is new for me ;) Used to Windows so quite a steep learning curve Feb 08 20:23:37 VirtualBox or "simple" machine that's not a daily driver are easier to setup Feb 08 20:24:05 I like Kubuntu UI but there are some KDE particularities like KDEWallet and other things that require tinkering more v.s. plain vanilla Ubuntu Feb 08 20:24:46 In case any of you happen to have a clue: https://github.com/martinkarlweber/rcraid-patches/issues/7 Feb 08 20:24:47 Yes, you don't need to worry about good device drivers for your physical hardware when you're running just VMs. Feb 08 20:25:06 s/VMs/running VMs Feb 08 20:25:24 (Oh, oops) Feb 08 20:25:38 nizovn: BTW for tissot on Halium you shouldn't have libtinyxml errors: https://github.com/Halium/halium-devices/blob/halium-7.1/manifests/xiaomi_tissot.xml#L7 Feb 08 21:27:47 Herrie|Laptop: So you are building and installing that module from source yourself, yes? Feb 08 21:28:03 (rcraid) Feb 08 21:31:20 It looks a little adventurous. I am not surprised that there are some minor issues. **** ENDING LOGGING AT Sat Feb 09 02:59:57 2019