Friday, 2021-11-12

T42<hacker12455> so currently trying to figure out why it does not boot09:36
T42<hacker12455> it just stays on the logo09:36
T42<TheVancedGamer> how did this get through (re @Lani .E. Armstrong: 𝖨'𝗏𝖾 𝖻𝖾𝖾𝗇 π—‚π—‡π—π–Ύπ—Œπ—π—‚π—‡π—€ ...)09:37
T42<hacker12455> any way to grab logs if even the hybris-recovery image stays on the OEM logo?11:30
T42<hacker12455> selinux is set to 1 on the kerbel command line11:31
T42<hacker12455> selinux is set to 1 on the kernel command line (edited)11:31
poetasteranyone here know the redmi note 5 (Vince) port? desperate user on the forum.13:27
T42<birdzhang> poetaster: i'm the porter13:45
poetasterah, user reports NO audio MPEG-1 Layer3 (mp3) not supported13:47
poetasteralso says no ringtones and Video.13:47
T42<birdzhang> i see on the forum13:47
poetasterah, you've seen it.13:47
T42<birdzhang> will try to contact him on vince tg group13:49
T42<Itzxdatl> How to update Platform Sdk?I'm on version (Verla)14:10
mal@Itzxdatl you mean all part, there are 3 parts, sdk itself, tooling and target14:46
T42<Itzxdatl> yes, I tried with sdk-assistant update &lt;target&gt;, but it gives me error14:49
malwhen I want to update everything I usually do: "sdk-foreach-su -l ssu some_version" , then "sdk-foreach-su -ly zypper ref" and finally "sdk-foreach-su -ly zypper dup"14:54
malreplace some_version with new version14:54
piggzmal: do you know what this is, dont remember adding it
malno idea15:01
poetasterpiggz, mal: that was like a 1950s sitcom scetch for hypergeeks.15:11
poetasterWell, the kind of guy who actually looks at the file geek.15:11
T42<hacker12455> btw, do I have to touch the audit settings in the kernel/cmdline if I use hybris-17.1?18:39
T42<elros34> I think you should add audit=0 to suppress audit messages, it will makes your logs easier to read18:52
T42<hacker12455> well for now I want to get any logs out18:53
T42<hacker12455> checked if the initramfs is in the boot image18:54
T42<hacker12455> but I get no output in dmesg18:54
T42<hacker12455> or in pstore18:54
T42<hacker12455> it just sits on the logo18:54
T42<hacker12455> does not reboot18:54
T42<elros34> what about host dmesg?18:54
T42<hacker12455> no usb devices there (re @elros34: what about host dmes...)18:54
T42<elros34> check again at first boot right after flashing18:55
T42<elros34> I assume you did follow advice about reverting skip_initramfs support18:55
T42<hacker12455> where? (re @elros34: I assume you did fol...)19:05
T42<hacker12455> didn't do that19:10
T42<hacker12455> just swap this to 0?19:12
T42<elros34> I think should be enough19:19
T42<hacker12455> that didn't seem to work20:49
T42<hacker12455> still returns nothing20:49
T42<elros34> what steps did you make after changing kernel?20:54
T42<hacker12455> ran breakfast and rebuilt hybris-boot21:21
T42<elros34> so after flashing hybris-boot.img there is still nothing at all in dmesg and device do not reaboot?21:22
T42<hacker12455> yes21:31
T42<elros34> hm can you show output of abootimg-i hybris-boot.img and your kernel/device repos?21:32
T42<elros34> I meant with your changes, see "cmdline = selinux=1" looks strange and most likely it should't be like that21:53
T42<hacker12455> I set that in (re @elros34: I meant with your ch...)21:54
T42<hacker12455> pretty much the only thing changed there would be the kernel config21:54
T42<elros34> your board config have a lot of cmdline arguments but your hybris-boot.img only one wrong:
T42<hacker12455> for whatever reason the BOARD_KERNEL_CMDLINE part didn't even exist in my BoardConfig21:55
T42<elros34> what do you mean I just show you the link with BOARD_KERNEL_CMDLINE (re @hacker12455: for whatever reason ...)21:56
T42<hacker12455> I mean the one I have in hadk (re @elros34: what do you mean I j...)21:56
T42<elros34> definitely you have the one I linked21:56
T42<hacker12455> ah I see21:57
T42<hacker12455> that's in common21:57
T42<elros34> so probably you overwrite BOARD_KERNEL_CMDLINE21:57
T42<hacker12455> so add the selinux=1 to common?21:57
T42<elros34> forget about selinux=1, I do not even know why you would add it. Maybe this one but I am not sure: androidboot.selinux=permissive21:58
T42<hacker12455> like that?21:59
T42<elros34> looks sane, make sure hybris-boot.img also have all these arguments22:00
T42<hacker12455> don't see the permissive part22:01
T42<hacker12455> but the rest is there22:01
T42<hacker12455> did not seem to change the situation...22:11
T42<elros34> do you flash hybris-boot.img or recovery? Do you see all cmdline in hybris-boot.img?22:12
T42<hacker12455> as for the cmdline part22:13
T42<elros34> so selinux part is still missing so who know if you even rebuild kernel with skip_initramfs changes22:14
T42<hacker12455> is there a way to ensure it gets rebuilt22:15
T42<hacker12455> maybe disable ccache?22:15
T42<hacker12455> oof22:15
T42<hacker12455> just realized why that selinux change wasn't there...22:15
T42<hacker12455> forgot to save the file22:15
T42<hacker12455> that initramfs.c change in the file is still there22:16
T42<hacker12455> is there some way to clean out the kernel ccache22:21
T42<elros34> I do not think you need to clean anything kernel related, abootimg should be always rebuild22:22
T42<elros34> oh I see you have breaking commit "tty: move tty_port workqueue to be a kthread" on 17 branch, newer see it on >16 base. Not sure if it's still broken but worth to check. Disable config_vt for test in kernel, if that helps then you need to revert that commit22:24
T42<hacker12455> yep, that actually returns stuff in dmesg22:43
T42<hacker12455> after disabling config_vt22:44
T42<hacker12455> reverted the commit22:48
T42<hacker12455> the hell22:55
T42<hacker12455> I reverted it and I get kernel build error22:55
T42<hacker12455> I reverted it and I get kernel build errors (edited)22:55
T42<hacker12455> well, warnings22:55
T42<elros34> there at least 2 more commits to revert which use tty_port_set_policy22:58
T42<hacker12455> so this one22:59
T42<hacker12455> anything else?23:00
T42<elros34> you have 4 commits after breaking one, it should be easy to check all of them whether they use changes introduced previously23:01
T42<Itzxdatl> can someone please help me? I don't know exactly what to do :
T42<Itzxdatl> I don't see any similar configurations to base it on.23:07
T42<elros34> you do not need anything similar, in fixup-mountpoints: left side is what you have in fstab, right side is block device (sda/sdb//mmcblk0)23:09
T42<hacker12455> now I get Product: Failed to boot init in real rootfs23:16
T42<elros34> progress!23:17
T42<hacker12455> indeed23:18
T42<Itzxdatl> that's how I stay, I hope it works hehe :
T42<elros34> no it will not23:21
T42<Itzxdatl> sad23:22
T42<elros34> have you checked how by-name path looks in your fstab?23:22
T42<Itzxdatl> How do I see that?23:23
T42<elros34> open your device fstab in text editor, compare it to other devices defined in  fixup-mountpoints and you will get it23:24
T42<Itzxdatl> ok, well then let me look for the fstab of my device23:25
T42<Itzxdatl> I found this, but lines 9, 10 and 11 don't match the others :
T42<elros34> what about fstab in your device repo?23:40
T42<elros34> and by device repo I mean github android_device_$VENDOR_$DEVICE23:41
T42<hacker12455> the problem now is that I can't telnet into the device23:43

Generated by 2.17.1 by Marius Gedminas - find it at!