**** BEGIN LOGGING AT Tue Jul 24 03:00:01 2018
Jul 24 06:24:13 <Herrie> Morning!
Jul 24 06:35:19 <Tofe> Morning !
Jul 24 06:36:15 <Tofe> Just unblocking oem didn't remove dm-0 for me; I had to reformat the partition. Unfortunately, when doing that the kernel doesn't find root anymore because we pass root=/dev/dm-0 during boot
Jul 24 07:28:10 <Herrie|Laptop> Tofe: Where we pass "root=/dev/dm-0"? I don't recall putting that anywhere
Jul 24 07:31:10 <Tofe> It's just what I see in dmesg
Jul 24 07:31:22 <Tofe> (from the pstore)
Jul 24 07:32:24 <Herrie|Laptop> Hmmz
Jul 24 07:33:36 <Herrie|Laptop> Might come from Halium somewhere
Jul 24 07:34:13 <Herrie|Laptop> When I grep for dm in meta-smartphone get no relevant hits
Jul 24 07:35:42 <Herrie|Laptop> It could be this one needs updating? https://github.com/shr-distribution/meta-smartphone/blob/pyro/meta-xiaomi/recipes-core/initrdscripts/initramfs-boot-android/tissot/machine.conf
Jul 24 07:35:49 <Herrie|Laptop> I see you did something else for Rosy there
Jul 24 07:37:12 <Tofe> Ah, yes, but it was just that I did put the wrong number
Jul 24 07:37:26 <Tofe> Anyway it's nearly never used in our case
Jul 24 07:37:38 <Tofe> and the kernel panic happens even before the initrd is started
Jul 24 07:40:47 <Tofe> I'm not really sure where this "root=dm-0" comes from - could it be that the recovery install added it?
Jul 24 07:41:37 <Tofe> I'm still looking for a nicer way to work with recovery - it's a bit of a hassle right now
Jul 24 07:44:39 <Herrie|Laptop> Or it could come from some of the Halium scripts, I'm not sure really
Jul 24 07:48:39 <Tofe> We are the ones who build the boot image
Jul 24 07:48:58 <Tofe> Until the initrd script is started, Halium isn't involved
Jul 24 07:56:39 <Herrie|Laptop> Tofe: OK
Jul 24 08:24:01 <Tofe> I now have a tissot build at home, should make things easier
Jul 24 08:28:41 <Herrie|Laptop> :)
Jul 24 11:58:26 <Herrie|Laptop> nizovn: Ping
Jul 24 12:00:36 <nizovn> Herrie|Laptop: pong
Jul 24 12:03:58 <Herrie|Laptop_> I somehow I cannot seem to get your preware feed working
Jul 24 12:04:45 <Herrie|Laptop_> For the new browser
Jul 24 12:04:50 <Herrie|Laptop_> Not sure what I'm doing wrong
Jul 24 12:05:02 <nizovn> you are using TP?
Jul 24 12:06:29 <Herrie|Laptop_> OK I now see my error I guess. Instructions on forum not very clear...
Jul 24 12:06:43 <Herrie|Laptop_> I added "https://gitlab.com/nizovn/preware_feed/"
Jul 24 12:06:51 <Herrie|Laptop_> But now read it should be "Add a feed in Preware using url: https://gitlab.com/nizovn/preware_feed/raw/master/ipkgs/"
Jul 24 12:07:01 <nizovn> ok, i will need to fix that i think
Jul 24 12:08:21 <Herrie|Laptop_> Seems you cannot add https urls in Preware
Jul 24 12:08:39 <nizovn> they works here..
Jul 24 12:22:02 <Herrie|Laptop_> I'll try on TP tonight
Jul 24 12:22:12 <Herrie|Laptop_> Feed needs to be compressed or not?
Jul 24 12:22:23 <nizovn> both should work
Jul 24 16:29:28 <Tofe> I confirm we pass problematic root=.... to the kernel https://bpaste.net/show/c55efc1a341d
Jul 24 16:50:36 <Tofe> where does it come from is still a mystery to me
Jul 24 17:02:51 <Tofe> ok, it looks like additional cmdlilne arguments were added by fastboot, somehow
Jul 24 17:44:30 <Herrie|Laptop> Tofe: No references in device or kernel repo
Jul 24 17:44:41 <Herrie|Laptop> So could be from TWRP somehow?
Jul 24 17:44:51 <Tofe> Herrie|Laptop: no it's the bootloader that adds it
Jul 24 17:45:01 <Herrie|Laptop> Hmmz OK :S
Jul 24 17:45:03 <Herrie|Laptop> Weird
Jul 24 17:45:07 <Herrie|Laptop> You flashed to Android 7?
Jul 24 17:45:32 <Tofe> nope
Jul 24 17:45:42 <Herrie|Laptop> Maybe that's the issue somehow?
Jul 24 17:45:50 <Herrie|Laptop> Or yours came with Android 7?
Jul 24 17:46:15 <Herrie|Laptop> I didn't check my version tbh
Jul 24 17:46:18 <Herrie|Laptop> Just quickly booted it
Jul 24 17:46:21 <Herrie|Laptop> Cna do when at home
Jul 24 17:46:53 <Tofe> no no, it came with 8.0
Jul 24 17:47:14 <Herrie|Laptop> Couldn't that somehow be the issue?
Jul 24 17:47:22 <Herrie|Laptop> Might be good to revert to 7.x just to be sure
Jul 24 17:47:26 <Herrie|Laptop> And avoid funny issues
Jul 24 17:47:34 <Herrie|Laptop> Because 8.0 will have other binary blobs maybe as well
Jul 24 17:47:39 <Herrie|Laptop> Which can cause the kernel panic
Jul 24 17:47:49 <Tofe> maybe yes
Jul 24 17:47:55 <Herrie|Laptop> And other funny side effects from mixing versions
Jul 24 17:48:00 <Tofe> I'll try a revert
Jul 24 17:48:05 <Herrie|Laptop> Not impossible, see our TP
Jul 24 17:48:07 <Herrie|Laptop> But well ;)
Jul 24 18:03:31 <Tofe> Herrie: but anyway the kernel panic is because of the root=... statement, not because of drivers
Jul 24 18:22:02 <Tofe> ok, flashing the whole thing with stock 7.1
Jul 24 19:22:32 <elvispre> I thought I knew that we are always supposed to flash a CM 14.1 image as a first step
Jul 24 19:28:51 <elvispre> I was asking the other night about device tree.
Jul 24 19:30:57 <elvispre> Do we use one? I know there's one in the Halium build but I don't know how it would be picked up by our kernel or if it is even present in our build.
Jul 24 19:36:17 <Herrie> elvispre: In general either CM 14.1 or Android 7.1
Jul 24 19:36:30 <Herrie> It shouldn't really matter (depending if CM modified a lot of stuff or not)
Jul 24 19:39:10 <elvispre> A case of making sure the proprietary blobs are for the right linux device driver, I suppose.
Jul 24 19:39:24 <elvispre> s/driver/drivers
Jul 24 20:08:05 <Tofe> Oddly enough, my boot image doesn't work as well now that I've flashed 7.1...
Jul 24 20:08:24 <Tofe> I can't get any pstore file
Jul 24 20:13:43 <elvispre> Tofe: You're looking for a kernel panic dump file. Is that right?
Jul 24 20:14:42 <Tofe> yup
Jul 24 20:14:50 <Tofe> like I got before
Jul 24 20:15:01 <elvispre> Right.
Jul 24 20:15:23 * elvispre is learning so much new stuff lately.
Jul 24 22:48:48 <elvispre> I now have a tissot build at home too. (Thanks Herrie.)
**** ENDING LOGGING AT Wed Jul 25 03:00:02 2018