**** BEGIN LOGGING AT Wed Feb 27 02:59:56 2019
Feb 27 09:54:32 <Herrie|Laptop> Morning!
Feb 27 09:55:01 <JaMa> morning
Feb 27 10:29:11 <Tofe> o/
Feb 27 10:45:35 <Herrie|Laptop> Tofe: Tested the reversal of the commit and getting https://bpaste.net/
Feb 27 10:45:48 <Herrie|Laptop> Oops: https://bpaste.net/show/5da76e2b8035
Feb 27 10:46:52 <Herrie|Laptop> So I guess we need to tweak the nyx modules from OSE a bit, so they don't conflict with ours
Feb 27 11:16:51 <saidinesh5> The imge was built but it didn't boot.. just got stuck with a blank screen.. will look into it more later today
Feb 27 11:16:59 <saidinesh5> on the bright side .. the image got built!
Feb 27 11:21:11 <Herrie|Laptop> saidinesh5: That's good. Any logs would be helpful
Feb 27 11:21:19 <Herrie|Laptop> Usually it's small config that needs tweaking still
Feb 27 11:26:38 <saidinesh5> Herrie|Laptop: how do i get logs though?
Feb 27 11:26:49 <saidinesh5> like i was hopign it would print everything to the screen but it wasn't
Feb 27 11:27:10 <saidinesh5> will try activating some usb console or something
Feb 27 11:31:51 <Herrie|Laptop> https://sites.google.com/site/zhuoweisite/blog/newlocationoflastkmsgonandroid60andabovesysfspstoreconsole-ramoops
Feb 27 11:31:57 <Herrie|Laptop> saidinesh5: ^
Feb 27 11:32:05 <Herrie|Laptop> That should work from recovery
Feb 27 11:32:32 <saidinesh5> Ahh this is x86 uefi device
Feb 27 11:32:36 <Herrie|Laptop> Ah wait you don't have android :P
Feb 27 11:32:38 <saidinesh5> no recovery
Feb 27 11:32:41 <saidinesh5> yeah
Feb 27 11:32:44 <Herrie|Laptop> And no recovery
Feb 27 11:32:50 <Herrie|Laptop> Ehm... Yeah then it's a good question
Feb 27 11:33:17 <Herrie|Laptop> Also no ADB then I guess
Feb 27 11:33:21 <saidinesh5> yup
Feb 27 11:33:22 <Herrie|Laptop> ?
Feb 27 11:33:57 <Herrie|Laptop> You know if it bootloops or just doesn't boot?
Feb 27 11:34:15 <saidinesh5> i think kernel is on
Feb 27 11:34:25 <saidinesh5> responds to ctrl alt del
Feb 27 11:34:43 <saidinesh5> justblank screen
Feb 27 11:40:56 <Herrie|Laptop> You might be able to SSH in
Feb 27 11:41:19 <Herrie|Laptop> That's what works on VirtualBox at least
Feb 27 11:41:51 <Herrie|Laptop> localhost on port 5522
Feb 27 11:42:37 <saidinesh5> oh but no ethernet here
Feb 27 11:45:02 <Herrie|Laptop> Ah
Feb 27 11:45:16 <Herrie|Laptop> JaMa: Any ideas?
Feb 27 11:45:38 <saidinesh5>  some kind of usb serial.. or there is a headphone jack
Feb 27 11:45:41 <saidinesh5> so serial via. that
Feb 27 11:45:54 <saidinesh5> orrr some kind of save logs to disk approach
Feb 27 11:46:04 <saidinesh5> usb serial seems like the best option so far  i think
Feb 27 11:46:11 <saidinesh5> although.. not sure if i have the usb cable
Feb 27 11:54:33 <JaMa> ssh should run on 22 (5522 is just port forward to guest 22 in virtualbox)
Feb 27 11:54:54 <JaMa> but maybe systemd didn't start that far to start openssh
Feb 27 11:55:20 <JaMa> serial console would be the best, physical connection depends on the device
Feb 27 12:06:36 <saidinesh5> i can try booting the iso on virtualbox actually
Feb 27 12:06:39 <saidinesh5> that should help right?
Feb 27 12:15:30 <Tofe> saidinesh5: can I see your defconfig ?
Feb 27 12:17:24 <saidinesh5>  how do i find it in yocto meta-intel? https://git.yoctoproject.org/cgit.cgi/meta-intel/tree/recipes-kernel/linux/meta-intel-compat-kernel.inc
Feb 27 12:18:28 <Tofe> mmh... maybe the easiest is to get is from tmp-work
Feb 27 12:18:50 <Tofe> tmp-glibc/work/ I mean
Feb 27 12:20:56 <JaMa> yes, check linux-yocto WORKDIR
Feb 27 12:23:47 <Tofe> saidinesh5: it would also be interesting to see what options are passed to the kernel at boot time (maybe "quiet" ?); because you should be able to see the kernel text, I think...
Feb 27 12:38:46 <saidinesh5> 1 sec
Feb 27 12:38:48 <saidinesh5> looking
Feb 27 12:39:02 <saidinesh5> tried to boot in virtualbox just now
Feb 27 12:39:07 <saidinesh5> but nothing there either
Feb 27 12:46:01 <saidinesh5> Tofe: https://bpaste.net/show/ddc4e02c83e9
Feb 27 12:47:47 <saidinesh5> as for arguments passed .. i am not sure.. but this maybe useful:
Feb 27 12:47:49 <saidinesh5> title boot
Feb 27 12:47:49 <saidinesh5> linux /vmlinuz
Feb 27 12:47:49 <saidinesh5> initrd /initrd
Feb 27 12:47:49 <saidinesh5> options LABEL=boot  rootwait console=ttyS0,115200 console=tty0
Feb 27 12:49:07 <saidinesh5> if i was able to see a grub or something of such sorts, would have been nicer though
Feb 27 12:57:50 <Herrie|Laptop> saidinesh5: You might want to check if you have all required kernel flags in defconfig as well. It's a bit tricky since some are specific for Halium/Mer it seems and might not apply to your UEFI case, but still
Feb 27 12:58:11 <Herrie|Laptop> Most should apply though since they're required for systemd, connman etc: https://github.com/mer-hybris/mer-kernel-check/blob/master/mer_verify_kernel_config
Feb 27 12:58:21 <saidinesh5> Herrie|Laptop: would i need things more than just systemd?
Feb 27 12:58:26 * saidinesh5 checks
Feb 27 12:58:56 <Herrie|Laptop> Well it has a whole bunch of flags that need to be enabled for Mer/SFOS/LuneOS/Halium
Feb 27 12:59:07 <Herrie|Laptop> In general we have same requirements for all distros it seems
Feb 27 13:03:43 <saidinesh5> the script seems to have gone bonkers..: https://bpaste.net/show/2492e5002b0a
Feb 27 13:04:04 <saidinesh5> but i don't think i am getting till kernel at all
Feb 27 13:04:13 <saidinesh5> something maybe up with that syslinux bootlaoder itself it seems
Feb 27 13:05:35 <Herrie|Laptop> Bit funny output indeed
Feb 27 13:05:48 <Herrie|Laptop> But there are values that would need correcting
Feb 27 13:10:26 <saidinesh5> yeah 2 ones
Feb 27 13:10:31 <saidinesh5> one for utf8 filenames
Feb 27 13:10:35 <saidinesh5> andanother config_dummy
Feb 27 13:11:00 <Herrie|Laptop> You should check the unset ones too:
Feb 27 13:11:17 <saidinesh5> unset ones are mostly warnigns
Feb 27 13:11:37 <Herrie|Laptop> WARNING: CONFIG_MEMCG_KMEM is invalid, WARNING: CONFIG_NETFILTER_NETLINK_ACCT is invalid , WARNING: CONFIG_NETFILTER_XT_MATCH_NFACCT is invalid
Feb 27 13:11:47 <Herrie|Laptop> WARNING: CONFIG_LBDAF is invalid
Feb 27 13:11:53 <saidinesh5> yeah the netfilter ones are for accounting
Feb 27 13:12:11 <Herrie|Laptop> I would fix all in general ;)
Feb 27 13:12:44 <saidinesh5> i guess.. although on my older kernels it was better to leave the netfilter warnings because the code was halfway implemented
Feb 27 13:12:47 <saidinesh5> and errored out
Feb 27 13:13:03 <saidinesh5> but before i start another build, i should try booting the .hddimage somehow
Feb 27 13:13:14 <Herrie|Laptop> Which kernel are you building? 4.19 or 4.15?
Feb 27 13:13:19 <saidinesh5> .19 i think
Feb 27 13:13:20 <Herrie|Laptop> Not that it should matter a whole lot
Feb 27 13:13:22 * saidinesh5 checks
Feb 27 13:15:25 <Herrie|Laptop> 4.x is a good kernel :P
Feb 27 13:15:40 <saidinesh5> interesting.. 4.9
Feb 27 13:15:41 <saidinesh5> yeah
Feb 27 13:15:50 <Herrie|Laptop> Well should be new enough too
Feb 27 13:15:57 <saidinesh5> yep
Feb 27 13:16:14 <saidinesh5> how do i boot the .hddimage ?
Feb 27 13:16:21 <saidinesh5> when i fdisk -l
Feb 27 13:16:30 <saidinesh5> it shows partitions of size 100s of gbs
Feb 27 13:17:04 <saidinesh5> the .iso image refuses to boot on virtualbox too
Feb 27 13:30:28 <saidinesh5> https://bpaste.net/show/7268d3c6b7b2
Feb 27 13:37:55 <Tofe> saidinesh5: that's quite a sick partition table
Feb 27 13:42:57 <saidinesh5> yep
Feb 27 13:43:18 <saidinesh5> can't exactly dd that to my 32GB usb stick
Feb 27 13:43:26 <saidinesh5> although the hddimage itself is like 1.5GB or something
Feb 27 15:30:54 <saidinesh5> oh freenode.. why you hate me so much
**** ENDING LOGGING AT Thu Feb 28 02:59:57 2019