iamdrq Posted January 11, 2021 Posted January 11, 2021 I tried a lot few days to driver a 3.5" TFT(the display ic is ST7701S,touch ic is FT5316) MIPI DSI color display panel on Orange Pi 4 with kernel 5.10.y . but I unexpected found it worked on linux 4.4 legacy kernel ( but I don't want use legacy kernel ),that below: But on kernel 5.x have some serious error in dmesg: [ 6.135383] rockchip-drm display-subsystem: bound ff940000.hdmi (ops dw_hdmi_rockchip_ops [rockchipdrm]) [ 6.136150] rockchip-drm display-subsystem: bound ff960000.mipi (ops dw_mipi_dsi_rockchip_ops [rockchipdrm]) [ 6.405472] dw-mipi-dsi-rockchip ff960000.mipi: failed to write command FIFO [ 6.427829] dw-mipi-dsi-rockchip ff960000.mipi: failed to write command FIFO [ 6.448508] dw-mipi-dsi-rockchip ff960000.mipi: failed to write command FIFO [ 6.469160] dw-mipi-dsi-rockchip ff960000.mipi: failed to write command FIFO [ 6.490170] dw-mipi-dsi-rockchip ff960000.mipi: failed to write command FIFO ...... what's mean 'dw-mipi-dsi-rockchip ff960000.mipi: failed to write command FIFO' ? I found the code in https://elixir.bootlin.com/linux/v5.10.6/source/drivers/gpu/drm/rockchip/dw-mipi-dsi-rockchip.c : static int dw_mipi_dsi_gen_pkt_hdr_write(struct dw_mipi_dsi *dsi, u32 hdr_val) { int ret; u32 val, mask; ret = readl_poll_timeout(dsi->base + DSI_CMD_PKT_STATUS, val, !(val & GEN_CMD_FULL), 1000, CMD_PKT_STATUS_TIMEOUT_US); if (ret) { dev_err(dsi->dev, "failed to get available command FIFO\n"); return ret; } dsi_write(dsi, DSI_GEN_HDR, hdr_val); mask = GEN_CMD_EMPTY | GEN_PLD_W_EMPTY; ret = readl_poll_timeout(dsi->base + DSI_CMD_PKT_STATUS, val, (val & mask) == mask, 1000, CMD_PKT_STATUS_TIMEOUT_US); if (ret) { dev_err(dsi->dev, "failed to write command FIFO\n"); return ret; } return 0; } Someone has tried to do this ? 1 Quote
iamdrq Posted January 12, 2021 Author Posted January 12, 2021 It works on main line kernel 5.10.6,rk3399 can use that patch(author is not me) driver mipi dsi: https://patchwork.kernel.org/project/dri-devel/patch/95f16906d654057c912f089d286bd51856ee3bdf.1607892237.git.tommyhebb@gmail.com/ 0 Quote
bamkrs Posted March 10, 2021 Posted March 10, 2021 Hey, nice to see MIPI-DSI working in 5.10.y Would you mind sharing your config and devicetree? Im struggeling to get the MIPI-DSI up but the dmesg is completly silent about Mipi. It seems that isn't even loaded even tho the module is compiled and loaded and the devicetree entry is enabled. 0 Quote
bamkrs Posted March 10, 2021 Posted March 10, 2021 10 minutes ago, @lex said: Do you have the touch working? Looking at the pictures, the touch-controller is not connected. But since its an FT5316 its not much of a hassle. I would even assume it will just run with the default FT5x06 mainline module. I'm really interested in how he got the MIPI-DSI DRM running. As soon as I just add &mipi_dsi { status = "okay"; }; the entire rockchip-drm driver stops working. HDMI, eDP nothing comes up anymore. dmesg | grep drm only outputs [ 0.694126] panfrost ff9a0000.gpu: [drm:panfrost_devfreq_init] *ERROR* Couldn't set OPP regulators [ 1.740675] [drm] Initialized panfrost 1.1.0 20180908 for ff9a0000.gpu on minor 0 without mipi_dsi enabled, everything works fine: [ 0.686797] rockchip-drm display-subsystem: bound ff8f0000.vop (ops vop_component_ops) [ 0.687611] [drm] unsupported AFBC format[3231564e] [ 0.689876] rockchip-drm display-subsystem: bound ff900000.vop (ops vop_component_ops) [ 0.695308] panfrost ff9a0000.gpu: [drm:panfrost_devfreq_init] *ERROR* Couldn't set OPP regulators [ 1.748562] rockchip-drm display-subsystem: bound ff8f0000.vop (ops vop_component_ops) [ 1.751190] rockchip-drm display-subsystem: bound ff900000.vop (ops vop_component_ops) [ 1.753993] rockchip-drm display-subsystem: bound ff940000.hdmi (ops dw_hdmi_rockchip_ops) [ 1.755134] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes [ 1.756401] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0 [ 1.764194] [drm] Initialized panfrost 1.1.0 20180908 for ff9a0000.gpu on minor 1 0 Quote
@lex Posted March 10, 2021 Posted March 10, 2021 1 hour ago, bamkrs said: Looking at the pictures, the touch-controller is not connected That's why i asked. How would you wire the touch? I don't have OPI4 but i am curious where it should go to the OPI4. I am thinking to try it out on my NanoPi M4. And it would be interesting to know how to connect all these things, some wires do not show where it goes ... 1 hour ago, bamkrs said: HDMI, eDP nothing comes up anymore Make sure you have: &vopb { status = "okay"; }; &vopb_mmu { status = "okay"; }; &vopl { status = "okay"; }; &vopl_mmu { status = "okay"; }; 0 Quote
iamdrq Posted March 11, 2021 Author Posted March 11, 2021 14 hours ago, @lex said: Do you have the touch working? Yes,after the lcd display ok,I drive the touch by FT5x06 in mainline 0 Quote
iamdrq Posted March 11, 2021 Author Posted March 11, 2021 On 3/10/2021 at 6:11 PM, bamkrs said: Hey, nice to see MIPI-DSI working in 5.10.y Would you mind sharing your config and devicetree? Im struggeling to get the MIPI-DSI up but the dmesg is completly silent about Mipi. It seems that isn't even loaded even tho the module is compiled and loaded and the devicetree entry is enabled. yes,you can got all info by view my blog https://imdrq.cn/blog_detail?id=81523 on pc 0 Quote
bamkrs Posted March 11, 2021 Posted March 11, 2021 1 hour ago, iamdrq said: yes,you can got all info by view my blog https://imdrq.cn on pc Nice! I've already seen your post for the legacy kernel. Do you know when you publish the post about 5.10.y? 0 Quote
iamdrq Posted March 11, 2021 Author Posted March 11, 2021 4 minutes ago, bamkrs said: Nice! I've already seen your post for the legacy kernel. Do you know when you publish the post about 5.10.y? No,I don't care about legacy kernel,I posted it is 5.10.y in my blog,and the title is 'orangepi4 mipi dsi' 0 Quote
bamkrs Posted March 11, 2021 Posted March 11, 2021 5 hours ago, iamdrq said: No,I don't care about legacy kernel,I posted it is 5.10.y in my blog,and the title is 'orangepi4 mipi dsi' So I made some progress, however, something seems of. I get a nullptr kernel panic when the module loads and tries to find the panel devicetree entry (i suppose) [ 1.749834] panel-dsi-simple ff960000.mipi.0: supply power not found, using dummy regulator [ 1.750865] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000290 [ 1.751637] Mem abort info: [ 1.751890] ESR = 0x96000004 [ 1.752166] EC = 0x25: DABT (current EL), IL = 32 bits [ 1.752636] SET = 0, FnV = 0 [ 1.752910] EA = 0, S1PTW = 0 [ 1.753191] Data abort info: [ 1.753449] ISV = 0, ISS = 0x00000004 [ 1.753822] CM = 0, WnR = 0 [ 1.754090] [0000000000000290] user address but active_mm is swapper [ 1.754654] Internal error: Oops: 96000004 [#1] PREEMPT SMP [ 1.755148] Modules linked in: [ 1.755433] CPU: 4 PID: 45 Comm: kworker/4:1 Not tainted 5.10.19-yocto-standard-som-rk3399 #1 [ 1.756181] Hardware name: Gessler GmbH IRISv1 (SOM-RK3399v2, MIPI-DSI) (DT) [ 1.756819] Workqueue: events deferred_probe_work_func [ 1.757282] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO BTYPE=--) [ 1.757818] pc : of_drm_find_panel+0x78/0xc8 [ 1.758200] lr : of_drm_find_panel+0x4c/0xc8 [ 1.758579] sp : ffff800012263a80 [ 1.758876] x29: ffff800012263a80 x28: ffff800011cc7000 [ 1.759356] x27: ffff0000f77a87f0 x26: ffff0000f77a87a0 [ 1.759834] x25: ffff800011e8c540 x24: ffff8000111b47e8 [ 1.760312] x23: 0000000000000000 x22: 0000000000000001 [ 1.760790] x21: ffff800011e8a160 x20: ffff0000f7817330 [ 1.761266] x19: ffff000042fc3c80 x18: 0000000000000000 [ 1.761744] x17: 0000000000000020 x16: 0000000000000019 [ 1.762221] x15: ffffffffffffffff x14: ffffff0000000000 [ 1.762698] x13: ffffffffffffffff x12: 000000000000000c [ 1.763175] x11: 0000000000000003 x10: 0101010101010101 [ 1.763652] x9 : fffffffffffffff9 x8 : 7f7f7f7f7f7f7f7f [ 1.764129] x7 : fefefeff646c606d x6 : 1d150c11f5f38080 [ 1.764605] x5 : 00007375110c151d x4 : 0000000000000000 [ 1.765081] x3 : ffff800011e8a160 x2 : ffff800011e8a180 [ 1.765558] x1 : 0000000000000000 x0 : 0000000000000000 [ 1.766036] Call trace: [ 1.766261] of_drm_find_panel+0x78/0xc8 [ 1.766614] drm_of_find_panel_or_bridge+0x6c/0xe8 [ 1.767043] dw_mipi_dsi_host_attach+0x7c/0x130 [ 1.767449] mipi_dsi_attach+0x28/0x40 [ 1.767785] panel_simple_dsi_probe+0x448/0x548 [ 1.768190] mipi_dsi_drv_probe+0x20/0x30 [ 1.768549] really_probe+0xe8/0x4d0 [ 1.768872] driver_probe_device+0xf4/0x160 [ 1.769246] __device_attach_driver+0x8c/0x118 [ 1.769644] bus_for_each_drv+0x78/0xc8 [ 1.769988] __device_attach+0xf0/0x170 [ 1.770333] device_initial_probe+0x14/0x20 [ 1.770706] bus_probe_device+0x9c/0xa8 [ 1.771051] deferred_probe_work_func+0x88/0xd8 [ 1.771457] process_one_work+0x1c0/0x4a0 [ 1.771817] worker_thread+0x1f8/0x420 [ 1.772154] kthread+0x118/0x150 [ 1.772447] ret_from_fork+0x10/0x34 [ 1.772773] Code: eb02027f d1008273 540001a0 f9400261 (f9414821) [ 1.773314] ---[ end trace 52395e7ef92f2cb0 ]--- Any hints what I might be missing out? 0 Quote
iamdrq Posted March 12, 2021 Author Posted March 12, 2021 13 hours ago, bamkrs said: So I made some progress, however, something seems of. I get a nullptr kernel panic when the module loads and tries to find the panel devicetree entry (i suppose) [ 1.749834] panel-dsi-simple ff960000.mipi.0: supply power not found, using dummy regulator [ 1.750865] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000290 [ 1.751637] Mem abort info: [ 1.751890] ESR = 0x96000004 [ 1.752166] EC = 0x25: DABT (current EL), IL = 32 bits [ 1.752636] SET = 0, FnV = 0 [ 1.752910] EA = 0, S1PTW = 0 [ 1.753191] Data abort info: [ 1.753449] ISV = 0, ISS = 0x00000004 [ 1.753822] CM = 0, WnR = 0 [ 1.754090] [0000000000000290] user address but active_mm is swapper [ 1.754654] Internal error: Oops: 96000004 [#1] PREEMPT SMP [ 1.755148] Modules linked in: [ 1.755433] CPU: 4 PID: 45 Comm: kworker/4:1 Not tainted 5.10.19-yocto-standard-som-rk3399 #1 [ 1.756181] Hardware name: Gessler GmbH IRISv1 (SOM-RK3399v2, MIPI-DSI) (DT) [ 1.756819] Workqueue: events deferred_probe_work_func [ 1.757282] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO BTYPE=--) [ 1.757818] pc : of_drm_find_panel+0x78/0xc8 [ 1.758200] lr : of_drm_find_panel+0x4c/0xc8 [ 1.758579] sp : ffff800012263a80 [ 1.758876] x29: ffff800012263a80 x28: ffff800011cc7000 [ 1.759356] x27: ffff0000f77a87f0 x26: ffff0000f77a87a0 [ 1.759834] x25: ffff800011e8c540 x24: ffff8000111b47e8 [ 1.760312] x23: 0000000000000000 x22: 0000000000000001 [ 1.760790] x21: ffff800011e8a160 x20: ffff0000f7817330 [ 1.761266] x19: ffff000042fc3c80 x18: 0000000000000000 [ 1.761744] x17: 0000000000000020 x16: 0000000000000019 [ 1.762221] x15: ffffffffffffffff x14: ffffff0000000000 [ 1.762698] x13: ffffffffffffffff x12: 000000000000000c [ 1.763175] x11: 0000000000000003 x10: 0101010101010101 [ 1.763652] x9 : fffffffffffffff9 x8 : 7f7f7f7f7f7f7f7f [ 1.764129] x7 : fefefeff646c606d x6 : 1d150c11f5f38080 [ 1.764605] x5 : 00007375110c151d x4 : 0000000000000000 [ 1.765081] x3 : ffff800011e8a160 x2 : ffff800011e8a180 [ 1.765558] x1 : 0000000000000000 x0 : 0000000000000000 [ 1.766036] Call trace: [ 1.766261] of_drm_find_panel+0x78/0xc8 [ 1.766614] drm_of_find_panel_or_bridge+0x6c/0xe8 [ 1.767043] dw_mipi_dsi_host_attach+0x7c/0x130 [ 1.767449] mipi_dsi_attach+0x28/0x40 [ 1.767785] panel_simple_dsi_probe+0x448/0x548 [ 1.768190] mipi_dsi_drv_probe+0x20/0x30 [ 1.768549] really_probe+0xe8/0x4d0 [ 1.768872] driver_probe_device+0xf4/0x160 [ 1.769246] __device_attach_driver+0x8c/0x118 [ 1.769644] bus_for_each_drv+0x78/0xc8 [ 1.769988] __device_attach+0xf0/0x170 [ 1.770333] device_initial_probe+0x14/0x20 [ 1.770706] bus_probe_device+0x9c/0xa8 [ 1.771051] deferred_probe_work_func+0x88/0xd8 [ 1.771457] process_one_work+0x1c0/0x4a0 [ 1.771817] worker_thread+0x1f8/0x420 [ 1.772154] kthread+0x118/0x150 [ 1.772447] ret_from_fork+0x10/0x34 [ 1.772773] Code: eb02027f d1008273 540001a0 f9400261 (f9414821) [ 1.773314] ---[ end trace 52395e7ef92f2cb0 ]--- Any hints what I might be missing out? Could you show your dts ? 0 Quote
cu6apum Posted March 25, 2021 Posted March 25, 2021 Hi there! I'm trying to follow your experience, compiled your patch, but either with or without it, the mipi display does not appear anywhere. The dts is forked from the Firefly howto, and WAS working oob in rockchip 4.4. Now only backlight is on (which is good) and no sound of the panel (which is bad). The howto page is here: http://wiki.t-firefly.com/en/Firefly-RK3399/driver_lcd.html Maybe i forgot something essential in dts? Thank you. 0 Quote
cu6apum Posted March 26, 2021 Posted March 26, 2021 Yes, I did, the "compatible" string was incompatible. Now - worse. The system catches the panel and crashes... Starting kernel ... [ 3.404406] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [ 3.995660] Unable to handle kernel paging request at virtual address 000000000000100a [ 3.996452] Mem abort info: [ 3.996724] ESR = 0x96000044 [ 3.997010] EC = 0x25: DABT (current EL), IL = 32 bits [ 3.997493] SET = 0, FnV = 0 [ 3.997783] EA = 0, S1PTW = 0 [ 3.998077] Data abort info: [ 3.998346] ISV = 0, ISS = 0x00000044 [ 3.998698] CM = 0, WnR = 1 [ 3.998979] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000044ba4000 [ 3.999563] [000000000000100a] pgd=0000000000000000, p4d=0000000000000000 [ 4.000195] Internal error: Oops: 96000044 [#1] PREEMPT SMP [ 4.000702] Modules linked in: stmmac pcs_xpcs pwm_bl adc_keys [ 4.001268] CPU: 1 PID: 44 Comm: kworker/1:1 Not tainted 5.10.21+ #5 [ 4.001843] Hardware name: FriendlyElec NanoPC-T4 (DT) [ 4.002328] Workqueue: events deferred_probe_work_func [ 4.002807] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO BTYPE=--) [ 4.003360] pc : drm_bus_flags_from_videomode+0x0/0x78 [ 4.003831] lr : of_get_drm_display_mode+0x94/0xd0 [ 4.004268] sp : ffff80001259b5e0 [ 4.004576] x29: ffff80001259b5e0 x28: ffff800010f88240 [ 4.005074] x27: ffff000079b2dc88 x26: 0000000000001000 [ 4.005569] x25: 0000000000000034 x24: ffff800011809000 [ 4.006062] x23: ffff00007fbdb628 x22: 000000000000100a [ 4.006555] x21: ffff000044b63500 x20: 0000000000000000 [ 4.007059] x19: ffff800011809000 x18: ffffffffffffffff [ 4.007581] x17: 0000000000000000 x16: 0000000000000000 [ 4.008077] x15: ffff800011809948 x14: ffff000044b63570 [ 4.008573] x13: ffff000044b63558 x12: 0000000000000038 [ 4.009067] x11: 0000000000000004 x10: 0000000005f5e0ff [ 4.009560] x9 : 00000000ffffffd8 x8 : 0000000000000500 [ 4.010054] x7 : 0000000000000000 x6 : ffffffffffffffff [ 4.010547] x5 : 0000000000000000 x4 : ffffffffffffffff [ 4.011039] x3 : ffff0a00ffffff04 x2 : 55b2922229ecb700 [ 4.011532] x1 : 000000000000100a x0 : ffff80001259b628 [ 4.012025] Call trace: [ 4.012265] drm_bus_flags_from_videomode+0x0/0x78 [ 4.012710] panel_simple_get_modes+0x64/0x140 [ 4.013122] drm_panel_get_modes+0x20/0x38 [ 4.013505] panel_bridge_connector_get_modes+0x14/0x20 [ 4.013986] drm_helper_probe_single_connector_modes+0x1d0/0x770 [ 4.014535] drm_client_modeset_probe+0x238/0x1078 [ 4.014978] __drm_fb_helper_initial_config_and_unlock+0x48/0x4c0 [ 4.015535] drm_fb_helper_initial_config+0x40/0x50 [ 4.015987] rockchip_drm_fbdev_init+0x5c/0x100 [ 4.016406] rockchip_drm_bind+0x17c/0x1d0 [ 4.016788] try_to_bring_up_master+0x274/0x2d0 [ 4.017206] __component_add+0xc8/0x190 [ 4.017563] component_add+0x10/0x18 [ 4.017899] dw_mipi_dsi_rockchip_host_attach+0x28/0xd8 [ 4.018379] dw_mipi_dsi_host_attach+0xcc/0x130 [ 4.018797] mipi_dsi_attach+0x24/0x38 [ 4.019146] panel_simple_dsi_probe+0x450/0x548 [ 4.019563] mipi_dsi_drv_probe+0x1c/0x28 [ 4.019936] really_probe+0x20c/0x518 [ 4.020277] driver_probe_device+0xec/0x158 [ 4.020664] __device_attach_driver+0xa4/0x118 [ 4.021077] bus_for_each_drv+0x70/0xc8 [ 4.021432] __device_attach+0xf0/0x178 [ 4.021789] device_initial_probe+0x10/0x18 [ 4.022175] bus_probe_device+0x94/0xa0 [ 4.022531] deferred_probe_work_func+0x80/0xd0 [ 4.022951] process_one_work+0x204/0x4d8 [ 4.023324] worker_thread+0x48/0x458 [ 4.023664] kthread+0x110/0x148 [ 4.023969] ret_from_fork+0x10/0x1c [ 4.024311] Code: b9002822 b9401802 17ffffe1 d503201f (b900003f) [ 4.024869] ---[ end trace 42c12b53ce8568e5 ]--- 0 Quote
cu6apum Posted March 26, 2021 Posted March 26, 2021 Gigantic thanks to @iamdrq for immediate and comprehensive help - I'm finally alive with my display. The things I missed were: a) the patch from Tommy did not lay properly onto the 5.10.21, only 1 of 3 records were hit. I had to edit the file by hand after I realized that; it's pretty easy. b) the "compatible" clause must match the Thierry's code - obvious, hun? That was the easiest part. (The easiest to miss...) c) remove the bus-format = <0x100a> line: after that the kernel stops crashing! d) in my case the lcd-reset pin was stuck in LOW, despite it's declared pull-up in pinctrl. I had to change GPIO_ACTIVE_LOW to _HIGH in reset_gpios - an ambiguous thing left to examine: I was thinking that ACTIVE means "when acting", ie, during reset. Solved. Recommended for usage! 0 Quote
kentAVR Posted July 6, 2021 Posted July 6, 2021 Is anywhere on aliexpress mipi dsi with touch more than 13" ? 0 Quote
iamdrq Posted July 27, 2021 Author Posted July 27, 2021 On 1/12/2021 at 11:35 PM, iamdrq said: It works on main line kernel 5.10.6,rk3399 can use that patch(author is not me) driver mipi dsi: https://patchwork.kernel.org/project/dri-devel/patch/95f16906d654057c912f089d286bd51856ee3bdf.1607892237.git.tommyhebb@gmail.com/ Now, that patch applied since main line kernel 5.12.17,you don't need patch no longer. 0 Quote
suhail Posted April 10, 2022 Posted April 10, 2022 On 3/10/2021 at 11:11 AM, bamkrs said: Hey, nice to see MIPI-DSI working in 5.10.y Would you mind sharing your config and devicetree? Im struggeling to get the MIPI-DSI up but the dmesg is completly silent about Mipi. It seems that isn't even loaded even tho the module is compiled and loaded and the devicetree entry is enabled. Hi, I am having the same behavior, as soon as I enable MIPI block my HDMI also goes down, and there's no message in the dmesg about mipi. I have also enabled the following but it does not help. &vopb { status = "okay"; }; &vopb_mmu { status = "okay"; }; &vopl { status = "okay"; }; &vopl_mmu { status = "okay"; }; 0 Quote
suhail Posted April 12, 2022 Posted April 12, 2022 As soon as I enable the mipi_dsi block the ligtdm fails to load. And now it even does not detect the hdmi. dmesg is silent about mipi, hdmi or drm /display driver. ● lightdm.service - Light Display Manager Loaded: loaded (/lib/systemd/system/lightdm.service; indirect; vendor pres> Active: failed (Result: exit-code) since Tue 2022-04-12 12:42:14 UTC; 7min> Docs: man:lightdm(1) Process: 2915 ExecStartPre=/bin/sh -c [ "$(basename $(cat /etc/X11/default-> Process: 2918 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE) Main PID: 2918 (code=exited, status=1/FAILURE) Apr 12 12:42:14 firefly-rk3399 systemd[1]: lightdm.service: Scheduled restart j> Apr 12 12:42:14 firefly-rk3399 systemd[1]: Stopped Light Display Manager. Apr 12 12:42:14 firefly-rk3399 systemd[1]: lightdm.service: Start request repea> Apr 12 12:42:14 firefly-rk3399 systemd[1]: lightdm.service: Failed with result > Apr 12 12:42:14 firefly-rk3399 systemd[1]: Failed to start Light Display Manage> Running ligtdm in debug mode does not give any helpful logs firefly-rk3399:~$ sudo lightdm --test-mode --debug [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.30.0, UID=0 PID=2945 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/60-lightdm-gtk-greeter.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/90-slick-greeter.conf [+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/10-slick-greeter.conf [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/11-armbian.conf [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: Registered seat module local [+0.00s] DEBUG: Registered seat module xremote [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.03s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? [+0.03s] DEBUG: Monitoring logind for seats [+0.03s] DEBUG: New seat added from logind: seat0 [+0.03s] DEBUG: Seat seat0: Loading properties from config section Seat:* [+0.03s] DEBUG: Seat seat0: Starting [+0.03s] DEBUG: Seat seat0: Creating greeter session [+0.03s] DEBUG: Seat seat0: Creating display server of type x [+0.03s] DEBUG: posix_spawn avoided (fd close requested) [+0.04s] DEBUG: Using VT 7 [+0.04s] DEBUG: Seat seat0: Starting local X display on VT 7 [+0.04s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log [+0.04s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0 [+0.04s] DEBUG: XServer 0: Launching X Server [+0.04s] DEBUG: Launching process 2950: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch [+0.05s] DEBUG: XServer 0: Waiting for ready signal from X server :0 [+0.05s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+0.05s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0 [+0.05s] WARNING: Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files [+0.05s] DEBUG: Loading user config from /etc/lightdm/users.conf [+0.05s] DEBUG: User goberobot added [+0.59s] DEBUG: Process 2950 terminated with signal 6 [+0.59s] DEBUG: XServer 0: X server stopped [+0.59s] DEBUG: Releasing VT 7 [+0.59s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0 [+0.59s] DEBUG: Seat seat0: Display server stopped [+0.59s] DEBUG: Seat seat0: Stopping session [+0.59s] DEBUG: Seat seat0: Session stopped [+0.59s] DEBUG: Seat seat0: Stopping display server, no sessions require it [+0.59s] DEBUG: Seat seat0: Stopping; greeter display server failed to start [+0.59s] DEBUG: Seat seat0: Stopping [+0.59s] DEBUG: Seat seat0: Stopped [+0.59s] DEBUG: Required seat has stopped [+0.59s] DEBUG: Stopping display manager [+0.59s] DEBUG: Display manager stopped [+0.59s] DEBUG: Stopping daemon [+0.59s] DEBUG: Exiting with return value 1 Can anyone help what is wrong here? 0 Quote
iamdrq Posted January 12, 2023 Author Posted January 12, 2023 @suhail dtc /sys/firmware/fdt > now.dts Please execute upper command then upload the now.dts file to there. 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.