Wednesday, 2021-03-03

T42<hacker12455> @elros34 these commits need to be reverted?07:42
T42<hacker12455> so after reverting the commits above08:43
T42<hacker12455> [392080.441410] rndis_host 1-1.2:1.0 usb0: register 'rndis_host' at usb-3f980000.usb-1.2, RNDIS device, 3e:a7:88:97:45:9c08:43
T42<hacker12455> [392112.521672] usb 1-1.2: USB disconnect, device number 608:43
T42<hacker12455> [392112.521961] rndis_host 1-1.2:1.0 usb0: unregister 'rndis_host' usb-3f980000.usb-1.2, RNDIS device08:43
T42<hacker12455> the device is being seen but it's disconnecting08:43
T42<hacker12455> (Document)
malthat means it at least boots to sailfish but something is causes a it to disconnect or reboot10:04
T42<hacker12455> it disconnects10:10
T42<hacker12455> it does not reboot10:10
T42<hacker12455> keep in mind I only reverted that10:37
T42<hacker12455> tty: move tty_port workqueue to be a kthread10:37
T42<hacker12455> tty: add tty_port_set_policy function10:37
T42<hacker12455> msm_serial_hs: make the Bluetooth tty thread RT10:37
T42<elros34> that commit cause issue at very early boot. Now try to get journal10:51
T42<elros34> @hacker12455 You can enable persistent logging according to hadk-faq10:57
T42<hacker12455> (Document)
T42<hacker12455> @elros3412:00
T42the_cave_dweller was added by: the_cave_dweller12:19
T42<the_cave_dweller> Hello, I actually joined because I'm not really sure where to ask this, but I'm using the Vollaphone, and everything seems ok on Sailfish, except I can't get my usb dacs to work, does anyone here know how to configure the system to send the audio signal correctly?, it seems to work normally on android12:26
T42<HengYeDev> is it possible to port Sailfish to android11/lineage18 devices?13:31
piggz@the_cave_dweller I do the volla port.  Cant comment on USB DACs as i dont have one, but does the kernel detect it, and what does pulseaudio do?  You could try pactl lsit cards etc, and you might need some custom routing?13:36
swanuxStill no luck with lipstick, but I found this in logcat: Does it mean anything to you?14:46
T42<edp_17> @swanux : try to search for 'SurfaceFlinger' in TG. You'll get some old posts what may help?15:04
T42<hacker12455> did anyone see that before?15:13
T42<hacker12455> [RMNET:HI] rmnet_config_notify_cb(): Kernel is trying to unregister rndis015:13
swanux@edp_17 Well, I checked the channel history, and as @elros34 mentioned checked logcat for surfaceflinger, here it is:
T42<edp_17> @swanux : "cutils-trace: Error opening trace file: Permission denied (13)" Have you run it as user or root?15:16
T42<edp_17> Try as root.15:17
swanuxI ran it as root15:17
T42<edp_17> Okay.15:17
T42<edp_17> "HWComposer: getSupportedPerFrameMetadata: getSupportedPerFrameMetadata failed for display 0: Unsupported (8)" Maybe this is the issue?!15:18
swanuxIdk, elros recommended it to see if there are any display sizes there, but I don't see them there. As surfaceflinger itself works without any issues, I don't know if any errors from here could be relevant.15:21
T42<edp_17> Maybe this is not relevant but I found this:
T42<hacker12455> @elros34 did you check the journal file?17:07
T42<elros34> Did youtired to look also? A quick glance shows that your partitions are not mounted. Check wheter your fixup-mountpoints are correct and next time paste text log not binary journal file17:13
T42<hacker12455> my fixup-mountpoints is correct, compared to the output of /dev/block/bootdevice/by-name17:21
T42<hacker12455> not sure why it fails to mount system17:21
malcan you show your device repo, the lineage repo17:22
T42<elros34> maybe it's not clear from hadk but you always use fstab  and output of ls command from device to create mapping17:24
malyou see there that those seem to have different paths17:33
T42<hacker12455> well if I run ls -l on that path I get the same partition number17:38
T42<hacker12455> lrwxrwxrwx 1 root root 21 1970-01-02 20:36 system -> /dev/block/mmcblk0p5317:39
T42<hacker12455> from ls -l /dev/block/platform/soc/7824900.sdhci/by-name17:39
malshow your fixup-mountpoint changes17:39
malsystem and vendor lines are wrong17:40
malvendor is missing17:40
T42<hacker12455> how do I figure out what partition number I should use17:43
T42<hacker12455> if vendor is missing from by-name on the device17:43
maland that is 17.1 base?17:48
T42<hacker12455> yes17:48
malanyway system is at least wrong17:48
malyou can verify the issue by checking the system.mount file on device17:49
T42<hacker12455> well I have the journal telling me about it so I don't think it's necessary17:50
T42<hacker12455> should I ignore vendor for now?17:50
mal@hacker12455 I meant that if you check the system.mount you can see that fixup-mountpoints is not correct17:52
T42<hacker12455> so now rebuild hybris-boot?17:52
maldid you fix fixup correctly? show the new version17:52
T42<hacker12455> just changed the system line17:57
malso now make hybris-hal and then repackage droid-hal rpms17:58
malmaybe make hybris-boot could be enough, not sure17:58
T42<hacker12455> let me try hybris-boot firsy17:58
T42<hacker12455> *first17:58
T42<elros34> based on your second fstab, /vendor is your oem18:00
T42<hacker12455> alright18:00
mal@hacker12455 if you really don't want to rebuild first you can just edit teh system.mount file on sfos rootfs18:08
malhybris-boot.img has nothing to do with system mounting18:08
T42<hacker12455> where is it located?18:09
malin /usr/lib/systemd/system/18:11
T42<hacker12455> so here is something weird18:34
T42<hacker12455> (Photo, 1008x585)
T42<hacker12455> it has the platform/soc path18:34
mal@hacker12455 come on, what have been saying to you for a while now? you replace that with the real path18:35
T42<hacker12455> oh18:36
malthe one you have in fixup18:36
malof course full real path18:36
T42<hacker12455> so /dev/block/mmcblk0p5318:37
T42<hacker12455> instead of the by-name path18:38
malwithout the block/18:38
maljust /dev/mmcblk0p5318:38
T42kiam001 was added by: kiam00118:38
T42<hacker12455> we might as well change vendor too18:39
T42<hacker12455> hm should we touch vendor-fsg, vendor-firmware and vendor-dsp?18:44
malthose should be ok, assuming your fixup was otherwise ok before18:44
T42<hacker12455> so now it bootloops18:54
T42<hacker12455> well18:57
T42<hacker12455> [    6.326704,0] android_work: android_work: did not send uevent (1 1 0000000000000000)18:57
T42<hacker12455> [    6.347217,0] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000010018:57
T42<hacker12455> (Document)
T42<kiam001> @hacker12455 dont use here txt files
T42<hacker12455> oops19:08
T42<hacker12455> thanks19:08
rinigusmal: you mentioned two days ago that I have to update ohmd (tama/aosp10/aarch64 port). do you also happen to know which plugins would have to be updated? to get cellular data19:11
T42<elros34> @hacker12455 didn't you forget about usual env variable when building kernel?19:21
T42<hacker12455> let me build hybris-boot again19:22
T42<hacker12455> removing the kernel file before building should be enough to make it apply that variable?19:24
T42<hacker12455> from out/target/cedric19:25
T42<elros34> just make sure hybris-boot.img is really recreated19:30
T42<hacker12455> bootloops too19:39
T42<hacker12455> that's how the vendor and system units look19:43
T42<hacker12455> Fwd from kiam001:
T42<elros34> @hacker12455 create empty file in sfos rootfs /init_enter_debug219:46
malrinigus: libdres-ohm, ohm, ohm-plugins-misc19:46
rinigusmal: thank you very much!19:47
T42<hacker12455> @elros34 that reboots too19:49
T42<elros34> then you mess up something else ,that /data/.stowaways/sailfishos/init_enter_debug2 should stop booting at /init-script19:51
T42<kiam001> this is the log
rinigusmal: have you had a chance to look into the comment regrading ?20:09
malrinigus: not yet20:43
malrinigus: I don't understand the error you mention there, the file should be created in the previous line20:57
T42<hacker12455> so if I get a different person to test the same image and rootfs but without the unit changes it does not bootloop, just stays at the logo21:25
T42<hacker12455> @elros3421:25
maldid the system mount fix help at all?21:27
T42<hacker12455> wait a bit21:34
T42<hacker12455> just want to have a test where only the system mount unit is changes21:35
T42<hacker12455> *changed21:35
T42<hacker12455> [Mount]21:35
T42<hacker12455> What=/dev/mmcblk0p5321:35
T42<hacker12455> Where=/system21:35
T42<hacker12455> that's how it should look?21:35
malwhat other changes did you do?21:35
T42<hacker12455> modified the vendor mount unit too21:35
malwait, you have 17.1? that needs some additional changes21:35
T42<hacker12455> yea21:35
T42<hacker12455> what changes?21:35
T42<hacker12455> specifically aarch64 17.121:36
malfirst thing, you see two symlinks somewhere under /etc/selinux/21:36
malreplace the symlinks with the actual target file21:36
T42<elros34> @hacker12455 that is impossible unless you didn't create that file which stops booting21:37
T42<hacker12455> well when only the system unit was changed it boots21:38
malwhat do you mean boots?21:39
malhow far?21:39
T42<hacker12455> to the same state we had previously21:39
T42<hacker12455> stays on oem logo21:39
T42<hacker12455> usb still disconnects21:39
T42<hacker12455> well21:42
T42<hacker12455> in /etc/selinux we only have one file21:42
T42<hacker12455> Fwd from joelmaxuel: Only a file in selinux, called config. Content:21:43
T42<hacker12455> Fwd from joelmaxuel: SELINUX=disabled21:43
T42<hacker12455> selinux is enabled in the kernel21:44
T42<hacker12455> CONFIG_SECURITY_SELINUX=y21:44
T42<hacker12455> # CONFIG_DEFAULT_SECURITY_DAC is not set21:44
T42<hacker12455> CONFIG_DEFAULT_SECURITY="selinux"21:44
malhmm, ok so you are missing other things also21:45
malI have selinux enabled on my device21:45
malit's a bit too late today already to explain everything that needs to be done21:46
T42campbellsteven was added by: campbellsteven23:16

Generated by 2.17.1 by Marius Gedminas - find it at!