**** BEGIN LOGGING AT Wed Aug 08 03:00:02 2018 Aug 08 12:24:20 Hi guys! Seems that exynos7880 SoC has qualcomm wifi module (at least kmsg(https://pastebin.com/AsyrqC2H) says it uses qca-cld-2.0 driver). Should this driver be open-source? I heard, that qualcomm give this driver to linux foundation, but Samsung doesn't provide source code for it Aug 08 12:37:04 [Edit] Hi guys! Seems that exynos7880 SoC has qualcomm wifi module (at least kmsg(https://pastebin.com/AsyrqC2H(see wifiloader section)) says it uses qca-cld-2.0 driver). Should this driver be open-source? I heard, that qualcomm give this driver to linux foundation, but Samsung doesn't provide source code for it Aug 08 12:37:17 [Edit] Hi guys! Seems that exynos7880 SoC has qualcomm wifi module (at least kmsg(https://pastebin.com/AsyrqC2H (see wifiloader section)) says it uses qca-cld-2.0 driver). Should this driver be open-source? I heard, that qualcomm give this driver to linux foundation, but Samsung doesn't provide source code for it Aug 08 13:52:50 ~ # mount /data/rootfs.img a … mount: mounting /dev/block/loop0 on a failed: Invalid argument Aug 08 13:53:21 @ankaos, Use /a and not just a Aug 08 13:53:35 ~ # mount /data/rootfs.img /a … mount: mounting /dev/block/loop0 on /a failed: Invalid argument Aug 08 13:54:06 I tried it in two ways. Aug 08 13:55:15 Is rootfs flashed correctly? Aug 08 14:02:06 it seems like no problem. Aug 08 14:03:27 Please run, "adb shell file /data/rootfs.img" from recovery Aug 08 14:03:43 And provide output Aug 08 14:37:43 file command not found Aug 08 14:39:48 What recovery you are using? Aug 08 14:43:31 twrp Aug 08 14:46:09 https://paste.ubuntu.com/p/vkv8Kr245x/ Aug 08 14:46:40 (Photo, 1024x768) https://irc.ubports.com/87JHrsym.png Aug 08 14:52:30 Stupid question: do you have write access in your home folder? Aug 08 14:56:33 stat ~/ Aug 08 15:09:37 @ankaos, read the mount manpage.. mounting iso needs minimal the parameter -o (mount -o loop /rootfs.img /a Aug 08 15:11:10 and if its an iso with more than one Partition its more tricky but possible.. Aug 08 15:15:53 With offsets an wo on .. Aug 08 15:19:32 @samyy samyyy, Have you ever worked with halium? Aug 08 15:19:54 Not to sound rude, but your comment doesn't apply to what he is doing. At all Aug 08 15:20:24 Rootfs.img is a single parition ext4 image. And you don't need to specify -o loop, mount does that for you Aug 08 15:20:57 Well `-o loop` might be required if the recovery is particularly old Aug 08 15:21:32 But since his device was making the loop device, it would seem it figured out what to do Aug 08 15:22:17 @UniversalSuperBox, Yep :P i don't really know why that person is trying to mount rootfs.img at such a weird location called `a` though Aug 08 15:22:31 It's the de facto place to mount a rootfs Aug 08 15:22:40 @UniversalSuperBox, It was just `a` at the beginning:P Aug 08 15:22:45 Yeah Aug 08 15:26:33 source:https://docs.halium.org/en/latest/porting/debug-build/logging-in.html#logging-in Aug 08 15:27:41 Try to mount again then type `dmesg`. Aug 08 15:27:56 There'll be some lines describing the failure to mount Aug 08 15:28:51 @samyy samyyy, it was :D Aug 08 15:52:39 then I do not know what to do. Aug 08 19:52:22 hey Aug 08 19:52:31 i forgot, is libcompat patch required on non-3.18 kernels? Aug 08 19:57:45 evandro_santana11 was added by: evandro_santana11 Aug 08 19:57:54 @evandro_santana11, welcome Aug 08 19:58:13 Thanks Aug 08 21:50:36 @vanyasem, is libcompat patch required on 3.18 kernels? I don't remeber this from docs.... Aug 08 21:50:50 it's not in the docs, i'm about to merge the PR to add that note Aug 08 21:51:04 which is why i'm wondering if it's required on other kernels as well Aug 08 21:51:58 👍 Aug 08 22:45:54 artP2 was added by: artP2 **** ENDING LOGGING AT Thu Aug 09 02:59:59 2018