| *** ChanServ sets mode: +v T4 | 02:41 | |
| *** Gizmokid2005 is now known as Mogwai | 04:05 | |
| T4 | <adampigg> Messaging from depecher on latte today! | 07:57 |
|---|---|---|
| T4 | <adampigg> @eugenio_g7 do you get reboots? Mine seems to turn off when not in use...when im using it it seems fine | 08:17 |
| *** ChanServ sets mode: +v T4 | 08:25 | |
| T4 | <eugenio_g7> Yup! I guess I disabled the iTCO watchdog but I haven't tested it yet | 08:26 |
| T4 | <eugenio_g7> s/I guess// | 08:26 |
| T4 | <adampigg> Atleast im not alone! | 08:28 |
| T4 | <adampigg> mal, spiiron, what needs configured in kernel/android side for watchdogs. tablet it rebooting when not in use. on boot, dsme says it cant open watchdog0, i guess it can open /dev/watchdog | 12:06 |
| T4 | <adampigg> yes, lsof says /dev/watchdo is open by dsme, but nothing has watchdog0 | 12:07 |
| T4 | <adampigg> kernel is doing some pinging | 12:20 |
| T4 | <adampigg> 1.626955] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11 … [ 1.627043] iTCO_wdt: Found a Cherry Trail SoC TCO device (Version=3, TCOBASE=0x0460) … [ 1.627287] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=1) … [ 8.435644] iTCO_wdt: iTCO_wdt_ping … [ 8.435777] iTCO_wdt: iTCO_wdt_ping … [ 10.308781] iTCO_wdt: iTCO_wdt_pi | 12:20 |
| T4 | ng | 12:20 |
| T4 | <adampigg> krnlyng: which rule needs changed for.... | 12:40 |
| T4 | <adampigg> i have a /dev/block/platform/by-name/* with invalid links | 12:41 |
| T4 | <adampigg> i … need a /dev/block/by-name/* with valid ones :) | 12:41 |
| r0kk3rz | @adampigg: get your bt to do anything? | 12:42 |
| T4 | <adampigg> r0kk3rz: sort of, it scans and finds stuff, but doesnt pair | 12:43 |
| r0kk3rz | well thats something | 12:43 |
| spiiroin | T4: IIRC so far the "usual situation" has been that (without heavy patching) android kernels tend to have no usable-by-dsme wd device nodes | 12:44 |
| T4 | <adampigg> spiiron, so, the usual fix is? :) | 12:45 |
| T4 | <adampigg> it gets a small mention in the hadk, but not a lot | 12:45 |
| spiiroin | T4: porting the grumpy old driver written for jolla1 kernel / not using wdd | 12:47 |
| spiiroin | T4: the situation has been more like: we'd like to get wd reboots when user side system gets stuck, but the default setup is happy until kernel is whacked too | 12:48 |
| spiiroin | T4: so if you get hit by wd reboots without trying really hard, it would be something novel | 12:48 |
| T4 | <adampigg> spiiroin: what does android do? afaict it has a watchdog service ... will that do? what is the point of dsme-wdd if it doesnt work? | 12:48 |
| T4 | <adampigg> it seems to happen shortly after suspend, if not connected | 12:49 |
| T4 | <adampigg> while in use its fine | 12:49 |
| T4 | <adampigg> if usb is connected it stays up | 12:49 |
| T4 | <adampigg> but, if i unplug and waiti a minute, it will reboot | 12:50 |
| T4 | <adampigg> intel cherry-trail iTCO driver in all intel motherboards i think | 12:50 |
| spiiroin | T4: even without wdd, the dsme-wdd process still participates in system heartbeat and watches over dsme-server process - which in turn handles things like process-watchdog, etc | 12:51 |
| T4 | <adampigg> what would happen if i didnt compile in itco-wdt to the kernel? | 12:52 |
| spiiroin | T4: hmmm.. "intel", "shortly after suspend" ... again IIRC, but I think what we have used have suspend/resume handlers that disable the hw wd on suspend and enable + kick at resume -> user space kicking matter only when device stays out of suspend | 12:56 |
| T4 | <adampigg> Got links to them??? | 13:06 |
| T4 | <adampigg> Spiirion^^ would something similar be on tbj? | 13:46 |
| *** ChanServ sets mode: +v T4 | 14:44 | |
| T4 | <adampigg> May have found a kernel patch to help | 15:14 |
| T4 | <abhishek_0> Mi pad 2 runs on intel atom right? | 15:16 |
| T4 | <adampigg> Yup | 15:17 |
| T4 | <abhishek_0> Can it run mainline ? | 15:18 |
| T4 | <adampigg> Possibly | 15:20 |
| T4 | <adampigg> We have gfx through mesa, not hybris, and sensors should work | 15:20 |
| mal | @adampigg do you see the needed files in sysfs? | 15:21 |
| mal | for sensors | 15:21 |
| T4 | <adampigg> Mal, i havnt messed with sensors yet, touch, bt and suspend are.my current focus | 15:22 |
| T4 | <adampigg> I have the sensor kernel modules | 15:22 |
| T4 | <adampigg> And fojnd some comments in the android init aboit load order | 15:23 |
| r0kk3rz | poor piggz needs his keyboard to work | 15:25 |
| T4 | <adampigg> I do1 | 15:26 |
| r0kk3rz | @adampigg: so why you using old kernel? | 15:27 |
| T4 | <adampigg> Its the los kernel, and i havnt thought about the build sydtem changes to use a new one...but, i can maybe just use upstream android, doesnt have to be kernel.org | 15:29 |
| T4 | <eugenio_g7> I had some trouble with modesetting on newer kernels (not on sailfishos, tried with generic linux distros) | 15:29 |
| r0kk3rz | i should hope cherrytrail support isnt so bad these days | 15:32 |
| T4 | <adampigg> I read 4.11 had imptovements | 15:33 |
| T4 | <adampigg> Mal, you know which rules file needs changed for fixing links? I probably should read about udev rule writing and syntax | 16:08 |
| mal | @adampigg https://github.com/mer-hybris/droid-hal-configs/blob/master/sparse/lib/udev/rules.d/998-droid-system.rules | 16:13 |
| mal | that can be overriden in device sparse | 16:13 |
| T4 | <adampigg> So, telling dsme to not send wd ticks is a.great.way to scew up the user experience, and general joy of using a device | 17:34 |
| r0kk3rz | @adampigg: sounds amazing | 17:53 |
| piggz_ | r0kk3rz: actually, it may have worked.....confirming | 18:18 |
| piggz_ | r0kk3rz: it seems to have | 18:24 |
| piggz_ | @eugenio_g7 maybe fixed reboots | 18:24 |
| piggz | mal: should all /sys mounts be removed on the grounds systemd refuses to mount them anyway? | 18:58 |
| piggz | krnlyng_: mal: this works for me: | 19:13 |
| piggz | ENV{ID_PART_ENTRY_SCHEME}=="gpt", ENV{ID_PART_ENTRY_NAME}=="?*", SYMLINK+="block/by-name/$env{ID_PART_ENTRY_NAME}" | 19:14 |
| mal | piggz: what difference does it have to the existing ones? | 19:36 |
| piggz | mal: it removes the platform folder and platform name folders from the path, which are not expected... | 19:37 |
| piggz | also, one of those variables toesnt expand to anything anyway, and results in broken links | 19:37 |
| piggz | i think it is platform_name | 19:37 |
| piggz | mal: so, should all /sys mounts be removed? | 19:38 |
| mal | piggz: maybe ignore those in droid-hal spec | 19:47 |
| piggz | mal: i have..... | 19:47 |
| mal | so what is the problem? | 19:47 |
| piggz | the reason i say, is that systemd appears to refult them anyway | 19:47 |
| piggz | see.... | 19:47 |
| piggz | Dec 05 19:20:33 Sailfish systemd[1]: sys-firmware-efi-efivars.mount: Cannot create mount unit for API file system /sys/firmware/efi/efivars. Refusing. | 19:48 |
| piggz | Dec 05 19:20:33 Sailfish systemd[1]: sys-fs-pstore.mount: Cannot create mount unit for API file system /sys/fs/pstore. Refusing. | 19:48 |
| piggz | Dec 05 19:20:33 Sailfish systemd[1]: sys-fs-cgroup-bfqio.mount: Cannot create mount unit for API file system /sys/fs/cgroup/bfqio. Refusing. | 19:48 |
| piggz | Dec 05 19:20:33 Sailfish systemd[1]: sys-fs-cgroup-cpuset.mount: Cannot create mount unit for API file system /sys/fs/cgroup/cpuset. Refusing. | 19:48 |
| piggz | seems to be a systemd feature ? | 19:48 |
| mal | piggz: show the spec file | 19:49 |
| piggz | mal: no, this is before the .spec changes, so the build would still create those mount units | 19:49 |
| mal | ? | 19:50 |
| piggz | i am wondering if they should generally always be removed if systemd doesnt support them | 19:50 |
| mal | if some mount fails and nothing really needs it then disable it | 19:50 |
| piggz | yes, i get that ... but im wondering if they should be skipped on creation anyway if systemd refuses to mount them https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems/ | 19:52 |
| mal | ? | 19:53 |
| piggz | the erros message says: | 19:53 |
| piggz | Cannot create mount unit for API file system | 19:53 |
| mal | I don't understand why won't just add those to the spec so the mounts are never created and then forget about the whole thing | 19:53 |
| piggz | mal: i am :) | 19:54 |
| mal | so why are we talking about this? | 19:54 |
| piggz | i am just saying, in general, all 'api' filesystems should be removed | 19:54 |
| mal | obviously if it will fail | 19:55 |
| piggz | mal: for ota/flash support, faq says to match to 'hardware' field from /proc/cpuinfo .... x86 doesnt have that! | 20:28 |
| *** ChanServ sets mode: +v T4 | 20:31 | |
| piggz | looking at the flash_partition script, i guess i can use _any_ string that appears in /proc/cpuinfo!! | 20:34 |
| r0kk3rz | yeah i think its just a protection mechanism | 20:42 |
| piggz | r0kk3rz: a single character would match that rule ;) | 20:51 |
| piggz | r0kk3rz: having a shot at building android-4.14 with existing defconfig | 20:52 |
| r0kk3rz | well i think its to stop BadThingsTM from happening if the config repo ends up on the wrong device | 20:52 |
| mal | r0kk3rz: yes, that is the reason for it | 21:02 |
| piggz | r0kk3rz: it built.... | 21:08 |
| r0kk3rz | dun dun dun | 21:10 |
| eugenio | hello | 21:24 |
| piggz | r0kk3rz: eugenio: so, it seemed to just turn off :( | 21:33 |
| eugenio | the mainline kernel? | 21:35 |
| piggz | not mainline, android-4.14 | 21:35 |
| piggz | i tried that first as an easy way to get a boot img | 21:36 |
| piggz | ideally would like to use a minline next try | 21:36 |
| piggz | eugenio: my repos have fixes for mounting issues, and reboots | 21:37 |
| r0kk3rz | some hacking required no doubt | 21:37 |
| r0kk3rz | check dts | 21:37 |
| eugenio | newer kernels just made the screen turn black for me, unless booting with nomodeset (but that would be pointless) | 21:38 |
| eugenio | piggz, nice, I'll take a look | 21:38 |
| piggz | eugenio: well, screen turned black, but there was no usb activity either | 21:38 |
| piggz | it printed a eufi secure boot disabled message, which it doesnt usually, then went black | 21:38 |
| eugenio | ok | 21:40 |
| eugenio | piggz, on which repository have you pushed the reboot fixes? | 21:43 |
| piggz | eugenio: config ... but you also need the mount fixes from device.... | 21:43 |
| piggz | basically | 21:43 |
| piggz | in the config, i disable the dsme watchdog tick | 21:43 |
| piggz | and with all the mount fixes, the android watchdog daemon is able to run and take care of it | 21:44 |
| eugenio | could you point me at the commit? I see only the android mount points one | 21:45 |
| piggz | eugenio: ah, didnt commit the dsme fix yet, was testing for bit... | 22:02 |
| piggz | eugenio: https://github.com/piggz/droid-config-latte/commit/b90331421c31800512158f7b1b64617be224e093 | 22:10 |
| eugenio | nice, thanks! | 22:11 |
| eugenio | I wonder if we should create a shared org on github | 22:11 |
| piggz | maybe aye | 22:12 |
| piggz | r0kk3rz: suggestions pls https://bpaste.net/show/f166c54b6fc2 | 22:16 |
| piggz | eugenio: hows sensors going? does screen brightness work for you? | 22:20 |
| eugenio | sensors noting yet, brightness works (haven't committed yet)... it only needed adjusting the path in mce | 22:22 |
| eugenio | I'll share soon™, recompiling the kernel now :) | 22:23 |
| eugenio | (stuck in fastboot currently) | 22:23 |
| r0kk3rz | piggz: id disable the service and try and init it manually | 22:30 |
| eugenio | piggz, https://github.com/g7/droid-config-latte/commit/2b4c6e5a82b3907a37ab85a5b013dc4721307e58 | 22:42 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!