| *** ChanServ sets mode: +v T4 | 02:09 | |
| *** ChanServ sets mode: +v T4 | 08:34 | |
| piggz | mal: on mido, udevadm infor -e works as exptected, so need to figure out whats wrong with that rule | 10:47 |
|---|---|---|
| T4 | <adampigg> mal: i wonder if it becuase i dont have a /dev/block | 11:33 |
| mal | @adampigg so the device never has /dev/block ? even in android? | 11:40 |
| T4 | <adampigg> mal: i dont know for sure, but i would assume it does have it in android becuase thats what is used in the fstab file | 13:09 |
| T4 | <adampigg> mal: https://github.com/piggz/android_device_xiaomi_latte/blob/cm-13.0/ramdisk/fstab | 13:11 |
| *** ChanServ sets mode: +v T4 | 14:02 | |
| piggz | mal: would android init be responsible for creating /dev/block? https://github.com/piggz/android_device_xiaomi_latte/blob/cm-13.0/ramdisk/init.latte.rc#L545 | 14:51 |
| mal | piggz: no, it's done in systemd, init shouldn't do it in sailfish | 14:51 |
| piggz | ok | 14:52 |
| mal | piggz: or actually in udev | 14:52 |
| piggz | yes, but i think my udev isnt working | 14:52 |
| piggz | it has no devices :D | 14:52 |
| mal | piggz: maybe something wrong with the default udev rules | 14:53 |
| piggz | mal: well, there is the rule it complains about, but i dont understand why | 14:53 |
| piggz | mal: this.... | 15:03 |
| piggz | DEVLINKS=="* platform/pci0000:00/80860F14:00/by-name/android_persistent *|platform/pci0000:00/80860F14:00/by-name/android_persistent *|* platform/pci0000:00/80860F14:00/by-name/android_persistent|platform/pci0000:00/80860F14:00/by-name/android_persistent" | 15:03 |
| piggz | my /sys doesnt contain any by_name | 15:03 |
| piggz | but, i dont really know what im looking for atm | 15:04 |
| piggz | mal: i commented out that line .. now there are no errors reported by udev, but still my udev DB is empty | 15:08 |
| piggz | mal: should uevent files in /sys be mode rw, or w ? | 15:42 |
| mal | piggz: those are 644 on my device | 15:44 |
| piggz | mal: doing a strace on udeavedmin trigger shows loats of failures opening them fro read | 15:46 |
| mal | piggz: maybe you should get some logs from udev behavior | 15:48 |
| piggz | mal: https://bpaste.net/show/089b0ccfad21 | 15:51 |
| piggz | mal: so, i have a bunch of files that are 644, and others which are 2 ... so maybe it is correct | 15:57 |
| piggz | mal: is this correct... | 15:59 |
| piggz | sh-3.2# file ./sbin/ueventd | 15:59 |
| piggz | ./sbin/ueventd: symbolic link to `./droid-hal-init' | 15:59 |
| piggz | i guerss it is | 16:01 |
| piggz | krnlyng: hi, any thoughts about why udev database on my device might be emtpy, or wht may cause it? | 18:04 |
| piggz | or just places to look | 18:04 |
| krnlyng | hmm | 18:04 |
| krnlyng | are there any warnings during the generation? | 18:05 |
| krnlyng | or errors | 18:05 |
| krnlyng | which db are you refering too? the generated rules files? | 18:05 |
| piggz | krnlyng: there is one error in a rule, and with that one rule commented out, it is still mepty.... | 18:05 |
| piggz | krnlyng: udevedm info -e | 18:06 |
| piggz | lists all devices | 18:06 |
| piggz | on mido, lists lots, on latte, nothing | 18:06 |
| piggz | systemd is unable to do any mounting until udev says devices are there | 18:06 |
| krnlyng | hm ok | 18:09 |
| krnlyng | any errors from udev in systemd? | 18:09 |
| piggz | nope.... | 18:09 |
| piggz | https://bpaste.net/show/579f7d30eb08 | 18:10 |
| krnlyng | piggz, hmm maybe it is somehow stuck? | 18:15 |
| krnlyng | piggz, can you run /sbin/ueventd and see what happens? | 18:16 |
| krnlyng | not sure if that shows us anything.. | 18:16 |
| piggz | krnlyng: well, that may be rleated....that is a symlink to droid-hal-init isnt it? | 18:16 |
| piggz | and it aborts | 18:16 |
| krnlyng | it should be a symlink to droid-hal-init yes | 18:18 |
| piggz | https://bpaste.net/show/7c25d8b91658 | 18:18 |
| krnlyng | piggz, are there devices in /dev before running it, and after? | 18:19 |
| krnlyng | hm ok | 18:19 |
| piggz | krnlyng: yes, i have devices in /dev, but nothing like /dev/block | 18:19 |
| krnlyng | can you rm /dev/.coldboot_done | 18:20 |
| krnlyng | and run it agian? | 18:20 |
| krnlyng | with strace | 18:20 |
| * krnlyng is just guessing and hoping something reveals something | 18:20 | |
| piggz | https://bpaste.net/show/cbadffbe3a79 | 18:21 |
| mal | piggz: stack corruption error is visible in that | 18:22 |
| mal | so maybe ueventd crashes | 18:23 |
| krnlyng | piggz, maybe the block rules are broken | 18:24 |
| piggz | it does, as does droid-hal-init | 18:24 |
| krnlyng | again... | 18:24 |
| piggz | krnlyng: one moment.... | 18:24 |
| krnlyng | piggz, which android version? | 18:24 |
| piggz | krnlyng: 6.0.1, LOS 13 | 18:24 |
| krnlyng | i see | 18:26 |
| krnlyng | could be tls breakage again | 18:26 |
| mal | krnlyng: but that is i486 | 18:26 |
| krnlyng | the dhi crash* | 18:26 |
| krnlyng | i486 device? | 18:27 |
| piggz | krnlyng: yes | 18:27 |
| krnlyng | then it almost certainly is tls breakage? | 18:27 |
| krnlyng | not sure if we applied the patch to 6 | 18:27 |
| piggz | krnlyng: new territory ;) | 18:27 |
| piggz | krnlyng: udev doesnt like this rul | 18:27 |
| piggz | SUBSYSTEM=="block", DEVLINKS=="* platform/pci0000:00/80860F14:00/by-name/android_persistent *|platform/pci0000:00/80860F14:00/by-name/android_persistent *|* platform/pci0000:00/80860F14:00/by-name/android_persistent|platform/pci0000:00/80860F14:00/by-name/android_persistent", MODE="0660", GROUP="system", OWNER="system" | 18:27 |
| piggz | Dec 02 18:27:39 Sailfish systemd-udevd[1058]: unknown key 'DEVLINKS' in /lib/udev/rules.d/999-android-system.rules:268 | 18:28 |
| piggz | Dec 02 18:27:39 Sailfish systemd-udevd[1058]: invalid rule '/lib/udev/rules.d/999-android-system.rules:268' | 18:28 |
| krnlyng | piggz, yeah i am aware of that one | 18:30 |
| krnlyng | but it shouldn't cause this | 18:30 |
| piggz | ok | 18:30 |
| krnlyng | but the other rules for the block devices | 18:30 |
| piggz | is there a dhi patch i need? | 18:32 |
| krnlyng | bionic | 18:33 |
| mal | at least hybris-13.0 and 14.1 have different patches in bionic | 18:33 |
| krnlyng | piggz, https://github.com/mer-hybris/android_bionic/commit/f3b400cfd529d72745b35b41d667cc292bd69f71 | 18:33 |
| krnlyng | something like this one | 18:33 |
| TheKit | <piggz> krnlyng: hi, any thoughts about why udev database on my device might be emtpy, or wht may cause it? | 18:55 |
| TheKit | it is not resolved yet? | 18:55 |
| piggz | not yet... | 18:55 |
| piggz | ideas? | 18:55 |
| TheKit | on mine, there was a change in kernel by Intel that sysfs symlinks | 18:56 |
| piggz | TheKit: and the fix was? | 19:01 |
| TheKit | piggz, [PATCH 269/429] Skip creating subsystem/ in sysfs nodes | 19:03 |
| TheKit | took me a while to find, but check if it is applied: https://bpaste.net/show/77eed0c85a9a - if yes, unapply | 19:03 |
| piggz | TheKit: yup, unapplied | 19:11 |
| piggz | TheKit: thanks, i have a udev database now! mal, krnlyng^^ | 19:14 |
| piggz | and system is mounted | 19:15 |
| piggz | and /vendor | 19:15 |
| piggz | so,that is something new to me anyway, silly kernel patches breaking udev! | 19:17 |
| mal | piggz: nice, now you can continue debugging other issues | 19:26 |
| piggz | yup | 19:26 |
| mal | piggz: do you see the crashes still? | 19:27 |
| piggz | mal: dhi works now with the bionic patch | 19:29 |
| piggz | tho, logcat not working | 19:30 |
| piggz | sh-3.2# /usr/libexec/droid-hybris/system/bin/logcat | 19:30 |
| piggz | logcat read failuresh-3.2# | 19:30 |
| piggz | mal: and after some time, i loose my usb net connection, not sure if its usb_moded or DHI | 19:32 |
| mal | piggz: check that usb stuff is disabled in init rc files | 19:32 |
| piggz | mal: yes, just need to be connect long enought | 19:33 |
| steeeve | Guess whos back | 20:17 |
| piggz | mal: even comnent lines like https://github.com/piggz/android_device_xiaomi_latte/blob/cm-13.0/ramdisk/init.latte.rc#L420 | 20:35 |
| piggz | all the way to 499 | 20:36 |
| *** ChanServ sets mode: +v T4 | 20:38 | |
| T4 | <adampigg> @eugenio_g7 looking at init.latte.rc, the wifi mac address seems to be loaded from /config (which i havnt got mounted yet) | 20:48 |
| piggz | mal: yes, commenting htose seems to have helped | 20:58 |
| piggz | mal: this is how droid-hal-init looks now https://bpaste.net/show/0da59ca7cb06 | 20:59 |
| piggz | and now got logcat | 21:01 |
| T4 | <morfeokmg> how can start to install sailfish to one tablet itab 4 | 21:03 |
| Mister_Magister | this english is beautiful (i wasn't better tho) | 21:04 |
| mal | piggz: does that mean dhi exists? | 21:29 |
| mal | *exits | 21:29 |
| piggz | mal: i think so, i have a second-stage dhi | 21:30 |
| piggz | mal: https://bpaste.net/show/490dcbefae02 | 21:34 |
| piggz | mal: surfaceflinger worked, hwcomposer not yet | 21:37 |
| TheKit | piggz, you mean you have graphics on surfaceflinger? | 21:37 |
| piggz | TheKit: yes, i got the LOS logo | 21:38 |
| TheKit | I thought Mer one | 21:38 |
| TheKit | (with qmlscene) | 21:38 |
| piggz | no, just tested the surfaceflinger executable | 21:38 |
| eugenio | hello | 21:38 |
| eugenio | joining the fun :) | 21:39 |
| piggz | eugenio: so, small kernel fix needed to fix udev | 21:39 |
| piggz | and comment out all the usb stuff, which i assume youve done | 21:39 |
| piggz | wondering now if i shoould install all your packages | 21:39 |
| piggz | eugenio: oh, and small bionic fix also needed | 21:40 |
| eugenio | yup I do have the bionic fixes, but still no dice on libhybris (on cm12.1 though) | 21:40 |
| eugenio | going to (un)apply the kernel fix | 21:42 |
| piggz | eugenio: is your extremely slow to interact with over telnet/usb ? | 21:50 |
| eugenio | after starting systemd? Try masking usb-moded | 21:50 |
| piggz | eugenio: no, all the time | 21:51 |
| piggz | its fsking painful! | 21:51 |
| eugenio | works smoothly here... | 21:54 |
| eugenio | do you use NetworkManager in your host computer? | 21:54 |
| piggz | yes | 21:57 |
| piggz | it doesnt even refresh the text properly, have to hit enter to arrow keys to refresh output | 21:57 |
| eugenio | try disabling NM and bringing up the rndis interface manually | 21:58 |
| eugenio | huh, finally got the sensor modules to load | 23:48 |
| eugenio | I guess I should now recompile sensorfwd with the iio adaptor | 23:48 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!