Pinetab 2 screen no longer coming on
#1
I received my Pinetab 2 (ARM version) in early June and the screen worked fine. The screen would go off due to power saving but tapping the screen or keys would bring the screen on again after a bit. However, I was using the Pinetab 2 with the screen working, I left for a few minutes and on return the screen was off. When I tried tapping the screen or keys then the screen didn't come on. Now the screen is always blank/black whatever I try. I've tried the brightness key (Fn+F2) many times, tried rebooting, powering off and then back on again, tried tapping the screen and keys. The keyboard backlight, not the LCD backlight, still works so the keyboard must still be being powered and does work, see later. I've attached the serial dongle and the Pinetab 2 does boot up and systemctl shows the displayer manager, sddm.service - Simple Desktop Display Manager, active. If I type the password on the keyboard and press enter, although there is still nothing on the built-in display, I can see that the user has logged in on the serial console!
Further, I've attached an external monitor via the HDMI port and it displays on external monitor fine.  When I played with removing and then adding back the built-in screen the GUI had lock-ups for a few seconds at a time.
There are error message in `dmesg`:
Code:
[    0.952428] rockchip-drm display-subsystem: bound fe060000.dsi (ops dw_mipi_dsi_rockchip_ops)
[    0.954580] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0
[    0.954939] ------------[ cut here ]------------
[    0.954958] WARNING: CPU: 2 PID: 748 at drivers/gpu/drm/drm_mode_object.c:45 drm_mode_object_add+0x90/0x98
[    0.954990] Modules linked in:
[    0.955007] CPU: 2 PID: 748 Comm: kworker/u8:4 Not tainted 6.3.0-5-danctnix #1
[    0.955021] Hardware name: Pine64 PineTab2 v2.0 (DT)
[    0.955031] Workqueue: events_unbound deferred_probe_work_func
[    0.955050] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[    0.955063] pc : drm_mode_object_add+0x90/0x98
[    0.955075] lr : drm_property_create+0xd0/0x188
[snip]
[    0.955300] Call trace:
[    0.955307]  drm_mode_object_add+0x90/0x98
[    0.955320]  drm_property_create+0xd0/0x188
[    0.955334]  drm_property_create_enum+0x30/0x94
[    0.955348]  drm_connector_set_panel_orientation+0x94/0xb4
[    0.955366]  boe_get_modes+0x70/0xbc
[    0.955386]  drm_panel_get_modes+0x28/0x48
[    0.955399]  panel_bridge_connector_get_modes+0x1c/0x2c
[    0.955418]  drm_helper_probe_single_connector_modes+0x1a4/0x52c
[    0.955433]  drm_client_modeset_probe+0x204/0x1194
[    0.955448]  __drm_fb_helper_initial_config_and_unlock+0x54/0x4b0
[    0.955464]  drm_fb_helper_initial_config+0x4c/0x60
[    0.955480]  drm_fbdev_client_hotplug+0x8c/0xd8
[    0.955495]  drm_fbdev_generic_setup+0x90/0x170
[    0.955509]  rockchip_drm_bind+0x1ec/0x208
[    0.955521]  try_to_bring_up_aggregate_device+0x170/0x1c0
[    0.955536]  __component_add+0xa8/0x174
[    0.955548]  component_add+0x18/0x28
[    0.955560]  dw_mipi_dsi_rockchip_host_attach+0x5c/0x14c
[    0.955577]  dw_mipi_dsi_host_attach+0x98/0xcc
[    0.955593]  mipi_dsi_attach+0x2c/0x44
[    0.955609]  boe_dsi_probe+0xf8/0x1a0
[    0.955623]  mipi_dsi_drv_probe+0x24/0x34
[    0.955639]  really_probe+0x150/0x2b4
[    0.955651]  __driver_probe_device+0x7c/0xe8
[    0.955663  driver_probe_device+0x40/0x164
[    0.955674]  __device_attach_driver+0xc4/0x144
[    0.955687]  bus_for_each_drv+0x88/0xe8
[    0.955702]  __device_attach+0xa0/0x190
[    0.955713]  device_initial_probe+0x18/0x28
[    0.955724]  bus_probe_device+0xb0/0xb4
[    0.955734]  deferred_probe_work_func+0x88/0xc4
[    0.955744]  process_one_work+0x1dc/0x340
[    0.955761]  worker_thread+0x224/0x434
[    0.955773]  kthread+0x10c/0x110
[    0.955785]  ret_from_fork+0x10/0x20
[    0.955800] ---[ end trace 0000000000000000 ]---
[    0.955858] ------------[ cut here ]------------
[    0.955866] WARNING: CPU: 2 PID: 748 at drivers/gpu/drm/drm_mode_object.c:242 drm_object_attach_property+0x6c/0xb8
and later
Code:
[  40.019376] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 282624 bytes), total 32768 (slots), used 0 (slots)
[  40.056213] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 1048576 bytes), total 32768 (slots), used 18 (slots)
[  40.068669] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 1011712 bytes), total 32768 (slots), used 0 (slots)
[  40.251994] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 987136 bytes), total 32768 (slots), used 2326 (slots)
[  40.277979] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 540672 bytes), total 32768 (slots), used 0 (slots)
[  40.358499] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 1667072 bytes), total 32768 (slots), used 92 (slots)
[  40.445645] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 552960 bytes), total 32768 (slots), used 2330 (slots)
[  50.903840] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 831488 bytes), total 32768 (slots), used 430 (slots)
[  50.946254] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 3350528 bytes), total 32768 (slots), used 140 (slots)
[  50.990632] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 5324800 bytes), total 32768 (slots), used 0 (slots)
The touchscreen works because I can do gestures on the screen and they effect the desktop as seen via HDMI.
I've installed the latest updates which included an initramfs rebuild but made no difference.
I've reinstalled the kernel but this has made no difference.
Code:
Linux danctnix 6.3.0-5-danctnix #1 SMP PREEMPT_DYNAMIC Mon Jun 12 06:40:39 UTC 2023 aarch64 GNU/Linux
I'm pretty sure this is a hardware fault.  I've reported the issue to Pine64 support and they have recommended coming here for further diagnosis and will RMA if it is a hardware fault so I appreciate any help on diagnosing this issue.
  Reply
#2
(06-22-2023, 01:12 PM)Fibonacci Wrote: I received my Pinetab 2 (ARM version) in early June and the screen worked fine. The screen would go off due to power saving but tapping the screen or keys would bring the screen on again after a bit. However, I was using the Pinetab 2 with the screen working, I left for a few minutes and on return the screen was off. When I tried tapping the screen or keys then the screen didn't come on. Now the screen is always blank/black whatever I try. I've tried the brightness key (Fn+F2) many times, tried rebooting, powering off and then back on again, tried tapping the screen and keys. The keyboard backlight, not the LCD backlight, still works so the keyboard must still be being powered and does work, see later. I've attached the serial dongle and the Pinetab 2 does boot up and systemctl shows the displayer manager, sddm.service - Simple Desktop Display Manager, active. If I type the password on the keyboard and press enter, although there is still nothing on the built-in display, I can see that the user has logged in on the serial console!
Further, I've attached an external monitor via the HDMI port and it displays on external monitor fine.  When I played with removing and then adding back the built-in screen the GUI had lock-ups for a few seconds at a time.
There are error message in `dmesg`:
Code:
[    0.952428] rockchip-drm display-subsystem: bound fe060000.dsi (ops dw_mipi_dsi_rockchip_ops)
[    0.954580] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0
[    0.954939] ------------[ cut here ]------------
[    0.954958] WARNING: CPU: 2 PID: 748 at drivers/gpu/drm/drm_mode_object.c:45 drm_mode_object_add+0x90/0x98
[    0.954990] Modules linked in:
[    0.955007] CPU: 2 PID: 748 Comm: kworker/u8:4 Not tainted 6.3.0-5-danctnix #1
[    0.955021] Hardware name: Pine64 PineTab2 v2.0 (DT)
[    0.955031] Workqueue: events_unbound deferred_probe_work_func
[    0.955050] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[    0.955063] pc : drm_mode_object_add+0x90/0x98
[    0.955075] lr : drm_property_create+0xd0/0x188
[snip]
[    0.955300] Call trace:
[    0.955307]  drm_mode_object_add+0x90/0x98
[    0.955320]  drm_property_create+0xd0/0x188
[    0.955334]  drm_property_create_enum+0x30/0x94
[    0.955348]  drm_connector_set_panel_orientation+0x94/0xb4
[    0.955366]  boe_get_modes+0x70/0xbc
[    0.955386]  drm_panel_get_modes+0x28/0x48
[    0.955399]  panel_bridge_connector_get_modes+0x1c/0x2c
[    0.955418]  drm_helper_probe_single_connector_modes+0x1a4/0x52c
[    0.955433]  drm_client_modeset_probe+0x204/0x1194
[    0.955448]  __drm_fb_helper_initial_config_and_unlock+0x54/0x4b0
[    0.955464]  drm_fb_helper_initial_config+0x4c/0x60
[    0.955480]  drm_fbdev_client_hotplug+0x8c/0xd8
[    0.955495]  drm_fbdev_generic_setup+0x90/0x170
[    0.955509]  rockchip_drm_bind+0x1ec/0x208
[    0.955521]  try_to_bring_up_aggregate_device+0x170/0x1c0
[    0.955536]  __component_add+0xa8/0x174
[    0.955548]  component_add+0x18/0x28
[    0.955560]  dw_mipi_dsi_rockchip_host_attach+0x5c/0x14c
[    0.955577]  dw_mipi_dsi_host_attach+0x98/0xcc
[    0.955593]  mipi_dsi_attach+0x2c/0x44
[    0.955609]  boe_dsi_probe+0xf8/0x1a0
[    0.955623]  mipi_dsi_drv_probe+0x24/0x34
[    0.955639]  really_probe+0x150/0x2b4
[    0.955651]  __driver_probe_device+0x7c/0xe8
[    0.955663  driver_probe_device+0x40/0x164
[    0.955674]  __device_attach_driver+0xc4/0x144
[    0.955687]  bus_for_each_drv+0x88/0xe8
[    0.955702]  __device_attach+0xa0/0x190
[    0.955713]  device_initial_probe+0x18/0x28
[    0.955724]  bus_probe_device+0xb0/0xb4
[    0.955734]  deferred_probe_work_func+0x88/0xc4
[    0.955744]  process_one_work+0x1dc/0x340
[    0.955761]  worker_thread+0x224/0x434
[    0.955773]  kthread+0x10c/0x110
[    0.955785]  ret_from_fork+0x10/0x20
[    0.955800] ---[ end trace 0000000000000000 ]---
[    0.955858] ------------[ cut here ]------------
[    0.955866] WARNING: CPU: 2 PID: 748 at drivers/gpu/drm/drm_mode_object.c:242 drm_object_attach_property+0x6c/0xb8
and later
Code:
[  40.019376] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 282624 bytes), total 32768 (slots), used 0 (slots)
[  40.056213] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 1048576 bytes), total 32768 (slots), used 18 (slots)
[  40.068669] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 1011712 bytes), total 32768 (slots), used 0 (slots)
[  40.251994] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 987136 bytes), total 32768 (slots), used 2326 (slots)
[  40.277979] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 540672 bytes), total 32768 (slots), used 0 (slots)
[  40.358499] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 1667072 bytes), total 32768 (slots), used 92 (slots)
[  40.445645] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 552960 bytes), total 32768 (slots), used 2330 (slots)
[  50.903840] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 831488 bytes), total 32768 (slots), used 430 (slots)
[  50.946254] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 3350528 bytes), total 32768 (slots), used 140 (slots)
[  50.990632] rockchip-drm display-subsystem: swiotlb buffer is full (sz: 5324800 bytes), total 32768 (slots), used 0 (slots)
The touchscreen works because I can do gestures on the screen and they effect the desktop as seen via HDMI.
I've installed the latest updates which included an initramfs rebuild but made no difference.
I've reinstalled the kernel but this has made no difference.
Code:
Linux danctnix 6.3.0-5-danctnix #1 SMP PREEMPT_DYNAMIC Mon Jun 12 06:40:39 UTC 2023 aarch64 GNU/Linux
I'm pretty sure this is a hardware fault.  I've reported the issue to Pine64 support and they have recommended coming here for further diagnosis and will RMA if it is a hardware fault so I appreciate any help on diagnosing this issue.

It's likely a faulty display unit. To be sure please try to reflash the factory image. If the issue persists then it is relatively safe it was not a bad flash at the factory. For details see https://wiki.pine64.org/wiki/PineTab2#Software.
  Reply
#3
(06-22-2023, 02:23 PM)fxc Wrote: It's likely a faulty display unit. To be sure please try to reflash the factory image. If the issue persists then it is relatively safe it was not a bad flash at the factory. For details see https://wiki.pine64.org/wiki/PineTab2#Software.

I downloaded the factory reset image from https://echo.danctnix.org:7269/danctnix-...527.img.xz, wrote it to a microSD card and verified that the image written to the microSD matched the uncompressed downloaded image.  I then booted from this image using the serial dongle starting with "SD BOOT" to ON and switching it to OFF once the kernel started booting (also tried it lots of other ways!).  The output on the serial console shows a different Linux version being booted, still has the drm crash, shows the eMMC being detected, there's an error about "GPT:Alternate GPT header not at the end of the disk." but I guess that's normal due to the nature of the image, then the log messages stop at "Starting network: OK", a bit later get "[  86.239708] random: crng init done" and then nothing else happens.  I'm not sure what is meant to happen but I'd expect some messages on the console about it flashing the factory image.  Perhaps it is meant to display something on the built-in screen?  I left it for over an hour but when I ejected the microSD, rebooted and it booted into the same unchanged system I'd left on the eMMC; it had not installed a factory version of the image.  I'm guessing that the broken built-in screen is breaking the factory reset install process or maybe options appear on the screen and you have to choose to do the factory install?

Unless that drm crash is normal on boot up then I'd say this proves the screen is broken because it was a different Linux version, nearly certainly the factory image reset installer one.  Let me know if it isn't enough proof and what else I could try.

Serial output:
Code:
Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x412fd050]
[    0.000000] Linux version 6.3.0-danctnix (danct12@melttower) (aarch64-buildroot-linux-musl-gcc.br_real (Buildroot 2023.02-96-g5f9ab2616c) 11.3.0, GNU ld (GNU Binutils) 2.38) #1 SMP PREEMPT_DYNAMIC Thu May 25 14:52:11 +07 2023
[    0.000000] Machine model: Pine64 PineTab2 v2.0h
[snip]
[    0.743084] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0
[    0.744170] ------------[ cut here ]------------
[    0.744610] WARNING: CPU: 2 PID: 764 at drivers/gpu/drm/drm_mode_object.c:45 drm_mode_object_add+0x88/0x90
[    0.745505] Modules linked in:
[    0.745798] CPU: 2 PID: 764 Comm: kworker/u8:4 Not tainted 6.3.0-danctnix #1
[    0.746437] Hardware name: Pine64 PineTab2 v2.0 (DT)
[snip]
[    0.770071] ---[ end trace 0000000000000000 ]---
[    0.770625] ------------[ cut here ]------------
[    0.771056] WARNING: CPU: 2 PID: 764 at drivers/gpu/drm/drm_mode_object.c:242 drm_object_attach_property+0x6c/0xb0
[snip]
[    1.724991] mmc_host mmc0: Bus speed (slot 0) = 375000Hz (slot req 400000Hz, actual 375000HZ div = 0)
[snip]
[    1.833135] mmc1: new HS200 MMC card at address 0001
[    1.841106] mmcblk1: mmc1:0001 SPeMMC 116 GiB
[    1.852720]  mmcblk1: p1 p2
[    1.858667] mmcblk1boot0: mmc1:0001 SPeMMC 4.00 MiB
[    1.867860] mmcblk1boot1: mmc1:0001 SPeMMC 4.00 MiB
[    1.874444] mmcblk1rpmb: mmc1:0001 SPeMMC 4.00 MiB, chardev (245:0)
[    2.004957] mmc_host mmc2: Bus speed (slot 0) = 375000Hz (slot req 400000Hz, actual 375000HZ div = 0)
[    2.023033] mmc_host mmc0: Bus speed (slot 0) = 150000000Hz (slot req 150000000Hz, actual 150000000HZ div = 0)
[    2.024378] Waiting for root device /dev/mmcblk0p4...
[    2.062221] dwmmc_rockchip fe2b0000.mmc: Successfully tuned phase to 190
[    2.072082] mmc0: new ultra high speed SDR104 SDXC card at address aaaa
[    2.079599] mmcblk0: mmc0:REDACTED 59.5 GiB
[    2.097122] GPT:Primary header thinks Alt. header is not at the end of the disk.
[    2.103612] GPT:12951591 != 124735487
[    2.109671] GPT:Alternate GPT header not at the end of the disk.
[    2.115356] GPT:12951591 != 124735487
[    2.120229] GPT: Use GNU Parted to correct GPT errors.
[    2.125349]  mmcblk0: p1 p2 p3 p4
[    2.166240] EXT4-fs (mmcblk0p4): recovery complete
[snip]
Starting syslogd: OK
Starting klogd: OK
Running sysctl: OK
Seeding 256 bits without crediting
Saving 256 bits of non-creditable seed for next boot
Starting network: OK
[   86.239708] random: crng init done
  Reply
#4
(06-24-2023, 09:53 AM)Fibonacci Wrote:
(06-22-2023, 02:23 PM)fxc Wrote: It's likely a faulty display unit. To be sure please try to reflash the factory image. If the issue persists then it is relatively safe it was not a bad flash at the factory. For details see https://wiki.pine64.org/wiki/PineTab2#Software.

I downloaded the factory reset image from https://echo.danctnix.org:7269/danctnix-...527.img.xz, wrote it to a microSD card and verified that the image written to the microSD matched the uncompressed downloaded image.  I then booted from this image using the serial dongle starting with "SD BOOT" to ON and switching it to OFF once the kernel started booting (also tried it lots of other ways!).  The output on the serial console shows a different Linux version being booted, still has the drm crash, shows the eMMC being detected, there's an error about "GPT:Alternate GPT header not at the end of the disk." but I guess that's normal due to the nature of the image, then the log messages stop at "Starting network: OK", a bit later get "[  86.239708] random: crng init done" and then nothing else happens.  I'm not sure what is meant to happen but I'd expect some messages on the console about it flashing the factory image.  Perhaps it is meant to display something on the built-in screen?  I left it for over an hour but when I ejected the microSD, rebooted and it booted into the same unchanged system I'd left on the eMMC; it had not installed a factory version of the image.  I'm guessing that the broken built-in screen is breaking the factory reset install process or maybe options appear on the screen and you have to choose to do the factory install?

Unless that drm crash is normal on boot up then I'd say this proves the screen is broken because it was a different Linux version, nearly certainly the factory image reset installer one.  Let me know if it isn't enough proof and what else I could try.

Serial output:
Code:
Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x412fd050]
[    0.000000] Linux version 6.3.0-danctnix (danct12@melttower) (aarch64-buildroot-linux-musl-gcc.br_real (Buildroot 2023.02-96-g5f9ab2616c) 11.3.0, GNU ld (GNU Binutils) 2.38) #1 SMP PREEMPT_DYNAMIC Thu May 25 14:52:11 +07 2023
[    0.000000] Machine model: Pine64 PineTab2 v2.0h
[snip]
[    0.743084] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0
[    0.744170] ------------[ cut here ]------------
[    0.744610] WARNING: CPU: 2 PID: 764 at drivers/gpu/drm/drm_mode_object.c:45 drm_mode_object_add+0x88/0x90
[    0.745505] Modules linked in:
[    0.745798] CPU: 2 PID: 764 Comm: kworker/u8:4 Not tainted 6.3.0-danctnix #1
[    0.746437] Hardware name: Pine64 PineTab2 v2.0 (DT)
[snip]
[    0.770071] ---[ end trace 0000000000000000 ]---
[    0.770625] ------------[ cut here ]------------
[    0.771056] WARNING: CPU: 2 PID: 764 at drivers/gpu/drm/drm_mode_object.c:242 drm_object_attach_property+0x6c/0xb0
[snip]
[    1.724991] mmc_host mmc0: Bus speed (slot 0) = 375000Hz (slot req 400000Hz, actual 375000HZ div = 0)
[snip]
[    1.833135] mmc1: new HS200 MMC card at address 0001
[    1.841106] mmcblk1: mmc1:0001 SPeMMC 116 GiB
[    1.852720]  mmcblk1: p1 p2
[    1.858667] mmcblk1boot0: mmc1:0001 SPeMMC 4.00 MiB
[    1.867860] mmcblk1boot1: mmc1:0001 SPeMMC 4.00 MiB
[    1.874444] mmcblk1rpmb: mmc1:0001 SPeMMC 4.00 MiB, chardev (245:0)
[    2.004957] mmc_host mmc2: Bus speed (slot 0) = 375000Hz (slot req 400000Hz, actual 375000HZ div = 0)
[    2.023033] mmc_host mmc0: Bus speed (slot 0) = 150000000Hz (slot req 150000000Hz, actual 150000000HZ div = 0)
[    2.024378] Waiting for root device /dev/mmcblk0p4...
[    2.062221] dwmmc_rockchip fe2b0000.mmc: Successfully tuned phase to 190
[    2.072082] mmc0: new ultra high speed SDR104 SDXC card at address aaaa
[    2.079599] mmcblk0: mmc0:REDACTED 59.5 GiB
[    2.097122] GPT:Primary header thinks Alt. header is not at the end of the disk.
[    2.103612] GPT:12951591 != 124735487
[    2.109671] GPT:Alternate GPT header not at the end of the disk.
[    2.115356] GPT:12951591 != 124735487
[    2.120229] GPT: Use GNU Parted to correct GPT errors.
[    2.125349]  mmcblk0: p1 p2 p3 p4
[    2.166240] EXT4-fs (mmcblk0p4): recovery complete
[snip]
Starting syslogd: OK
Starting klogd: OK
Running sysctl: OK
Seeding 256 bits without crediting
Saving 256 bits of non-creditable seed for next boot
Starting network: OK
[   86.239708] random: crng init done

That's fine and I don't think there are any further tests, you can confirm the support that it's a faulty screen.
  Reply
#5
Hello,
I too have the same blank screen issue.

When I first turned on the PineTab2  the screen didn't come on.
I tried many different combinations of power cycles.
Eventually (after a few days) I had left it unattended in a state I thought was off, but noticed the screen didn't appear completely black.
It turned out the PineTab2 was on and I was able to login and use the screen.
However I then turned off the PineTab2 and have not been able to get the screen to work again since.

I have yet to connect via the dongle or the external HDMI. The keyboard backlight responds appropriately, and I have also tried all the screen adjustment options on the keyboard, with no success.

I will investigate further and post again.
  Reply
#6
I have tested my PineTab2 further and have found similar behavior as described in the initial post.

I have submitted a ticket with the Pine64 store and they also directed me to "community channels" for further diagnosis and help, so I will continue positing here.

Currently the PineTab2 display does not come on at all.
I can connect with the external HDMI and see the output on an external monitor as expected.
I connected with the dongle and can log in to a serial terminal as expected.
I reflashed with the factory image from https://echo.danctnix.org:7269/danctnix-...527.img.xz however the screen still does not come on.

The following are error messages in the dmesg output before the reflash.
Code:
[    0.708479] dw-mipi-dsi-rockchip fe060000.dsi: Failed to create device link (0x180) with vcc_3v3
[    0.710908] vcc3v3_sd enforce active low on GPIO handle
[    0.728164] rockchip-drm display-subsystem: bound fe040000.vop (ops vop2_component_ops)
[    0.729433] dwhdmi-rockchip fe0a0000.hdmi: Detected HDMI TX controller v2.11a with HDCP (DWC HDMI 2.0 TX PHY)
[    0.730491] dwhdmi-rockchip fe0a0000.hdmi: registered DesignWare HDMI I2C bus driver
[    0.731188] rockchip-drm display-subsystem: bound fe0a0000.hdmi (ops dw_hdmi_rockchip_ops)
[    0.731889] rockchip-drm display-subsystem: bound fe060000.dsi (ops dw_mipi_dsi_rockchip_ops)
[    0.733241] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0
[    0.733494] ------------[ cut here ]------------
[    0.733510] WARNING: CPU: 0 PID: 772 at drivers/gpu/drm/drm_mode_object.c:45 drm_mode_object_add+0x90/0x98
[    0.733550] Modules linked in:
[    0.733569] CPU: 0 PID: 772 Comm: kworker/u8:5 Not tainted 6.3.0-2-danctnix #1
[    0.733583] Hardware name: Pine64 PineTab2 v2.0 (DT)
[    0.733594] Workqueue: events_unbound deferred_probe_work_func
[    0.733618] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[    0.733631] pc : drm_mode_object_add+0x90/0x98
[    0.733646] lr : drm_property_create+0xd0/0x188
[    0.733660] sp : ffff80000b0835b0
[    0.733667] x29: ffff80000b0835b0 x28: ffff000101c5d400 x27: 0000000000000037
[    0.733691] x26: 0000000000001000 x25: 0000000000001000 x24: ffff000101cf0800
[    0.733713] x23: ffff800008f160c0 x22: 0000000000000004 x21: 00000000b0b0b0b0
[    0.733734] x20: ffff000103ace990 x19: ffff000101cf0800 x18: ffff80000b06d110
[    0.733756] x17: 206d657473797362 x16: 75732d79616c7073 x15: ffff80000b083550
[    0.733777] x14: ffff000103ace4f0 x13: ffff000103ace4d4 x12: 0000000000000000
[    0.733798] x11: 0000000000000000 x10: 0000000000000078 x9 : 0000000000000000
[    0.733817] x8 : ffff000103aced80 x7 : 0000000000000000 x6 : 000000000000003f
[    0.733837] x5 : 0000000000000040 x4 : ffff80000b0835c0 x3 : 0000000000000000
[    0.733858] x2 : 00000000b0b0b0b0 x1 : ffff000103ace990 x0 : 0000000000000001
[    0.733879] Call trace:
[    0.733885]  drm_mode_object_add+0x90/0x98
[    0.733901]  drm_property_create+0xd0/0x188
[    0.733914]  drm_property_create_enum+0x30/0x94
[    0.733926]  drm_connector_set_panel_orientation+0x94/0xb4
[    0.733942]  boe_get_modes+0x70/0xbc
[    0.733957]  drm_panel_get_modes+0x28/0x48
[    0.733972]  panel_bridge_connector_get_modes+0x1c/0x2c
[    0.733988]  drm_helper_probe_single_connector_modes+0x1a4/0x52c
[    0.734000]  drm_client_modeset_probe+0x204/0x1194
[    0.734012]  __drm_fb_helper_initial_config_and_unlock+0x54/0x494
[    0.734026]  drm_fb_helper_initial_config+0x4c/0x60
[    0.734039]  drm_fbdev_client_hotplug+0x8c/0xd8
[    0.734051]  drm_fbdev_generic_setup+0x90/0x170
[    0.734063]  rockchip_drm_bind+0x1ec/0x208
[    0.734080]  try_to_bring_up_aggregate_device+0x170/0x1c0
[    0.734098]  __component_add+0xa8/0x174
[    0.734112]  component_add+0x18/0x28
[    0.734126]  dw_mipi_dsi_rockchip_host_attach+0x5c/0x14c
[    0.734140]  dw_mipi_dsi_host_attach+0x98/0xcc
[    0.734152]  mipi_dsi_attach+0x2c/0x44
[    0.734165]  boe_dsi_probe+0xf8/0x1a0
[    0.734177]  mipi_dsi_drv_probe+0x24/0x34
[    0.734190]  really_probe+0x150/0x2b4
[    0.734204]  __driver_probe_device+0x7c/0xe8
[    0.734219]  driver_probe_device+0x40/0x164
[    0.734232]  __device_attach_driver+0xc4/0x144
[    0.734246]  bus_for_each_drv+0x88/0xe8
[    0.734258]  __device_attach+0xa0/0x190
[    0.734272]  device_initial_probe+0x18/0x28
[    0.734287]  bus_probe_device+0xb0/0xb4
[    0.734300]  deferred_probe_work_func+0x88/0xc4
[    0.734314]  process_one_work+0x1dc/0x340
[    0.734331]  worker_thread+0x224/0x434
[    0.734344]  kthread+0x10c/0x110
[    0.734355]  ret_from_fork+0x10/0x20
[    0.734370] ---[ end trace 0000000000000000 ]---
[    0.734487] ------------[ cut here ]------------
[    0.734500] WARNING: CPU: 0 PID: 772 at drivers/gpu/drm/drm_mode_object.c:242 drm_object_attach_property+0x6c/0xb8
[    0.734529] Modules linked in:
[    0.734544] CPU: 0 PID: 772 Comm: kworker/u8:5 Tainted: G        W          6.3.0-2-danctnix #1
[    0.734559] Hardware name: Pine64 PineTab2 v2.0 (DT)
[    0.734569] Workqueue: events_unbound deferred_probe_work_func
[    0.734588] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[    0.734601] pc : drm_object_attach_property+0x6c/0xb8
[    0.734616] lr : drm_connector_set_panel_orientation+0x68/0xb4
[    0.734630] sp : ffff80000b083650
[    0.734636] x29: ffff80000b083650 x28: ffff000101c5d400 x27: 0000000000000037
[    0.734660] x26: 0000000000001000 x25: 0000000000001000 x24: ffff000101cf0800
[    0.734681] x23: 00000000fffffffd x22: ffff000103fc0e80 x21: ffff000101cf0800
[    0.734702] x20: ffff000101cf0238 x19: ffff000101cf0170 x18: ffff80000b06d0f8
[    0.734723] x17: 206d657473797362 x16: 75732d79616c7073 x15: ffff80000b083550
[    0.734744] x14: ffff000103ace4f0 x13: ffff000103ace4d4 x12: 0000000000000000
[    0.734765] x11: 0000000000000000 x10: 0000000000000078 x9 : 0000000000000000
[    0.734785] x8 : ffff000103ace738 x7 : 00000000c0c0c0c0 x6 : 00000000c0c0c0c0
[    0.734807] x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000006
[    0.734827] x2 : 0000000000000003 x1 : ffff000103ace980 x0 : ffff000101cf01b0
[    0.734848] Call trace:
[    0.734855]  drm_object_attach_property+0x6c/0xb8
[    0.734871]  boe_get_modes+0x70/0xbc
[    0.734886]  drm_panel_get_modes+0x28/0x48
[    0.734902]  panel_bridge_connector_get_modes+0x1c/0x2c
[    0.734916]  drm_helper_probe_single_connector_modes+0x1a4/0x52c
[    0.734929]  drm_client_modeset_probe+0x204/0x1194
[    0.734941]  __drm_fb_helper_initial_config_and_unlock+0x54/0x494
[    0.734955]  drm_fb_helper_initial_config+0x4c/0x60
[    0.734968]  drm_fbdev_client_hotplug+0x8c/0xd8
[    0.734981]  drm_fbdev_generic_setup+0x90/0x170
[    0.734994]  rockchip_drm_bind+0x1ec/0x208
[    0.735011]  try_to_bring_up_aggregate_device+0x170/0x1c0
[    0.735028]  __component_add+0xa8/0x174
[    0.735043]  component_add+0x18/0x28
[    0.735059]  dw_mipi_dsi_rockchip_host_attach+0x5c/0x14c
[    0.735074]  dw_mipi_dsi_host_attach+0x98/0xcc
[    0.735086]  mipi_dsi_attach+0x2c/0x44
[    0.735099]  boe_dsi_probe+0xf8/0x1a0
[    0.735112]  mipi_dsi_drv_probe+0x24/0x34
[    0.735125]  really_probe+0x150/0x2b4
[    0.735139]  __driver_probe_device+0x7c/0xe8
[    0.735153]  driver_probe_device+0x40/0x164
[    0.735167]  __device_attach_driver+0xc4/0x144
[    0.735181]  bus_for_each_drv+0x88/0xe8
[    0.735193]  __device_attach+0xa0/0x190
[    0.735207]  device_initial_probe+0x18/0x28
[    0.735221]  bus_probe_device+0xb0/0xb4
[    0.735233]  deferred_probe_work_func+0x88/0xc4
[    0.735246]  process_one_work+0x1dc/0x340
[    0.735263]  worker_thread+0x224/0x434
[    0.735276]  kthread+0x10c/0x110
[    0.735288]  ret_from_fork+0x10/0x20
[    0.735303] ---[ end trace 0000000000000000 ]---
[    1.455995] Console: switching to colour frame buffer device 160x50
[    1.483389] rockchip-drm display-subsystem: [drm] fb0: rockchipdrmfb frame buffer device


And errors in dmesg output after the reflash.
Code:
[    0.678911] dw-mipi-dsi-rockchip fe060000.dsi: Failed to create device link (0x180) with vcc_3v3
[    0.681125] vcc3v3_sd enforce active low on GPIO handle
[    0.697632] rockchip-drm display-subsystem: bound fe040000.vop (ops vop2_component_ops)
[    0.698949] dwhdmi-rockchip fe0a0000.hdmi: Detected HDMI TX controller v2.11a with HDCP (DWC HDMI 2.0 TX PHY)
[    0.699915] dwhdmi-rockchip fe0a0000.hdmi: registered DesignWare HDMI I2C bus driver
[    0.700536] rockchip-drm display-subsystem: bound fe0a0000.hdmi (ops dw_hdmi_rockchip_ops)
[    0.701202] rockchip-drm display-subsystem: bound fe060000.dsi (ops dw_mipi_dsi_rockchip_ops)
[    0.702663] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0
[    0.813327] ------------[ cut here ]------------
[    0.813351] WARNING: CPU: 3 PID: 723 at drivers/gpu/drm/drm_mode_object.c:45 drm_mode_object_add+0x90/0x98
[    0.813386] Modules linked in:
[    0.813402] CPU: 3 PID: 723 Comm: kworker/u8:4 Not tainted 6.3.0-2-danctnix #1
[    0.813416] Hardware name: Pine64 PineTab2 v2.0 (DT)
[    0.813426] Workqueue: events_unbound deferred_probe_work_func
[    0.813449] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[    0.813463] pc : drm_mode_object_add+0x90/0x98
[    0.813479] lr : drm_property_create+0xd0/0x188
[    0.813493] sp : ffff80000af6b5b0
[    0.813500] x29: ffff80000af6b5b0 x28: ffff000105471880 x27: 0000000000000037
[    0.813523] x26: 0000000000001000 x25: 0000000000001000 x24: ffff00010487d800
[    0.813545] x23: ffff800008f160c0 x22: 0000000000000004 x21: 00000000b0b0b0b0
[    0.813566] x20: ffff0001055b7390 x19: ffff00010487d800 x18: ffff80000af6d110
[    0.813587] x17: 2c58402d38711880 x16: 3a02010101010101 x15: ffff80000af6b550
[    0.813608] x14: ffff0001055b7470 x13: ffff0001055b7454 x12: 00000000000001ef
[    0.813629] x11: 000000000000020d x10: 0000000000000078 x9 : 0000000000000000
[    0.813649] x8 : ffff0001055b7300 x7 : 0000000000000000 x6 : 000000000000003f
[    0.813670] x5 : 0000000000000040 x4 : ffff80000af6b5c0 x3 : 0000000000000000
[    0.813689] x2 : 00000000b0b0b0b0 x1 : ffff0001055b7390 x0 : 0000000000000001
[    0.813710] Call trace:
[    0.813718]  drm_mode_object_add+0x90/0x98
[    0.813734]  drm_property_create+0xd0/0x188
[    0.813746]  drm_property_create_enum+0x30/0x94
[    0.813758]  drm_connector_set_panel_orientation+0x94/0xb4
[    0.813773]  boe_get_modes+0x70/0xbc
[    0.813788]  drm_panel_get_modes+0x28/0x48
[    0.813802]  panel_bridge_connector_get_modes+0x1c/0x2c
[    0.813817]  drm_helper_probe_single_connector_modes+0x1a4/0x52c
[    0.813829]  drm_client_modeset_probe+0x204/0x1194
[    0.813842]  __drm_fb_helper_initial_config_and_unlock+0x54/0x494
[    0.813857]  drm_fb_helper_initial_config+0x4c/0x60
[    0.813869]  drm_fbdev_client_hotplug+0x8c/0xd8
[    0.813882]  drm_fbdev_generic_setup+0x90/0x170
[    0.813894]  rockchip_drm_bind+0x1ec/0x208
[    0.813911]  try_to_bring_up_aggregate_device+0x170/0x1c0
[    0.813929]  __component_add+0xa8/0x174
[    0.813942]  component_add+0x18/0x28
[    0.813956]  dw_mipi_dsi_rockchip_host_attach+0x5c/0x14c
[    0.813970]  dw_mipi_dsi_host_attach+0x98/0xcc
[    0.813983]  mipi_dsi_attach+0x2c/0x44
[    0.813996]  boe_dsi_probe+0xf8/0x1a0
[    0.814009]  mipi_dsi_drv_probe+0x24/0x34
[    0.814023]  really_probe+0x150/0x2b4
[    0.814036]  __driver_probe_device+0x7c/0xe8
[    0.814050]  driver_probe_device+0x40/0x164
[    0.814063]  __device_attach_driver+0xc4/0x144
[    0.814077]  bus_for_each_drv+0x88/0xe8
[    0.814090]  __device_attach+0xa0/0x190
[    0.814103]  device_initial_probe+0x18/0x28
[    0.814116]  bus_probe_device+0xb0/0xb4
[    0.814129]  deferred_probe_work_func+0x88/0xc4
[    0.814142]  process_one_work+0x1dc/0x340
[    0.814158]  worker_thread+0x224/0x434
[    0.814171]  kthread+0x10c/0x110
[    0.814183]  ret_from_fork+0x10/0x20
[    0.814199] ---[ end trace 0000000000000000 ]---
[    0.814256] ------------[ cut here ]------------
[    0.814264] WARNING: CPU: 3 PID: 723 at drivers/gpu/drm/drm_mode_object.c:242 drm_object_attach_property+0x6c/0xb8
[    0.814288] Modules linked in:
[    0.814300] CPU: 3 PID: 723 Comm: kworker/u8:4 Tainted: G        W          6.3.0-2-danctnix #1
[    0.814314] Hardware name: Pine64 PineTab2 v2.0 (DT)
[    0.814322] Workqueue: events_unbound deferred_probe_work_func
[    0.814341] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[    0.814353] pc : drm_object_attach_property+0x6c/0xb8
[    0.814368] lr : drm_connector_set_panel_orientation+0x68/0xb4
[    0.814380] sp : ffff80000af6b650
[    0.814386] x29: ffff80000af6b650 x28: ffff000105471880 x27: 0000000000000037
[    0.814409] x26: 0000000000001000 x25: 0000000000001000 x24: ffff00010487d800
[    0.814431] x23: 00000000fffffffd x22: ffff00010545f180 x21: ffff00010487d800
[    0.814453] x20: ffff00010487d238 x19: ffff00010487d170 x18: ffff80000af6d0f8
[    0.814474] x17: 2c58402d38711880 x16: 3a02010101010101 x15: ffff80000af6b550
[    0.814494] x14: ffff0001055b7470 x13: ffff0001055b7454 x12: 00000000000001ef
[    0.814515] x11: 000000000000020d x10: 0000000000000078 x9 : 0000000000000000
[    0.814535] x8 : ffff0001055b7238 x7 : 00000000c0c0c0c0 x6 : 00000000c0c0c0c0
[    0.814555] x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000006
[    0.814575] x2 : 0000000000000003 x1 : ffff0001055b7380 x0 : ffff00010487d1b0
[    0.814596] Call trace:
[    0.814602]  drm_object_attach_property+0x6c/0xb8
[    0.814618]  boe_get_modes+0x70/0xbc
[    0.814632]  drm_panel_get_modes+0x28/0x48
[    0.814647]  panel_bridge_connector_get_modes+0x1c/0x2c
[    0.814661]  drm_helper_probe_single_connector_modes+0x1a4/0x52c
[    0.814673]  drm_client_modeset_probe+0x204/0x1194
[    0.814685]  __drm_fb_helper_initial_config_and_unlock+0x54/0x494
[    0.814699]  drm_fb_helper_initial_config+0x4c/0x60
[    0.814712]  drm_fbdev_client_hotplug+0x8c/0xd8
[    0.814724]  drm_fbdev_generic_setup+0x90/0x170
[    0.814736]  rockchip_drm_bind+0x1ec/0x208
[    0.814751]  try_to_bring_up_aggregate_device+0x170/0x1c0
[    0.814768]  __component_add+0xa8/0x174
[    0.814781]  component_add+0x18/0x28
[    0.814795]  dw_mipi_dsi_rockchip_host_attach+0x5c/0x14c
[    0.814808]  dw_mipi_dsi_host_attach+0x98/0xcc
[    0.814820]  mipi_dsi_attach+0x2c/0x44
[    0.814834]  boe_dsi_probe+0xf8/0x1a0
[    0.814846]  mipi_dsi_drv_probe+0x24/0x34
[    0.814859]  really_probe+0x150/0x2b4
[    0.814872]  __driver_probe_device+0x7c/0xe8
[    0.814886]  driver_probe_device+0x40/0x164
[    0.814898]  __device_attach_driver+0xc4/0x144
[    0.814912]  bus_for_each_drv+0x88/0xe8
[    0.814924]  __device_attach+0xa0/0x190
[    0.814937]  device_initial_probe+0x18/0x28
[    0.814950]  bus_probe_device+0xb0/0xb4
[    0.814963]  deferred_probe_work_func+0x88/0xc4
[    0.814975]  process_one_work+0x1dc/0x340
[    0.814989]  worker_thread+0x224/0x434
[    0.815001]  kthread+0x10c/0x110
[    0.815012]  ret_from_fork+0x10/0x20
[    0.815025] ---[ end trace 0000000000000000 ]---
[    1.578740] Console: switching to colour frame buffer device 100x67
[    1.603449] rockchip-drm display-subsystem: [drm] fb0: rockchipdrmfb frame buffer device

Before and after the reflash the version info at the start of dmesg was the same.
Code:
[    0.000000] Linux version 6.3.0-2-danctnix (builduser@alarm) (aarch64-unknown-linux-gnu-gcc (GCC) 12.1.0, GNU ld (GNU Binutils) 2.38) #1 SMP PREEMPT_DYNAMIC Fri May 26 07:05:36 UTC 2023

In the dmesg output there is the message " Failed to create device link (0x180) with vcc_3v3" just before the errors, occur.

Can anyone with a working screen check if this message is in their dmesg output?

Not sure what else to log. Hope someone has some extra insight.
  Reply
#7
Hi,
I don't have any information, but I am also experiencing this (black screen, even when trying to boot from factory image, keyboard backlights are only sign of life).

I'll try to get my hands on a usb data cable and/or a hdmi -> micro hdmi cable and see what I can find.
  Reply
#8
Following the directions from the wiki page to connect to the UART adapter, I run into trouble as I don't see a /dev/ttyUSB0 on my system.

But that's mostly fine, as I was able to connect to an external display with the HDMI.
I flashed the factory image (no trouble booting from the SD card) and powered it off.
Restarting and disconnecting the external display... there is still nothing on the Pinetab's screen.

Ah well. At least I can see some things now, I can look for logs.
  Reply
#9
I have exactly the same issue (blank screen, error in drm_mode_object_add):/ the UART log is at https://pastebin.com/4rv7gbYE .

Quote:Following the directions from the wiki page to connect to the UART adapter, I run into trouble as I don't see a /dev/ttyUSB0 on my system.


I first plugged the cable into the other USB port, it has to be in the one labeled DEBUG. Perhaps run "dmesg -w" and you should see something like this after you plug it in (it does not have to be in the PineTab, as it takes power from your computer):


Code:
[94825.741027] usb 1-2.4.1: new full-speed USB device number 19 using xhci_hcd
[94825.850246] usb 1-2.4.1: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.33
[94825.850257] usb 1-2.4.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[94825.850261] usb 1-2.4.1: Product: USB Serial
[94825.902691] ch341 1-2.4.1:1.0: ch341-uart converter detected
[94825.909575] usb 1-2.4.1: ch341-uart converter now attached to ttyUSB0
  Reply
#10
(06-30-2023, 12:10 AM)eudoxos Wrote: I have exactly the same issue (blank screen, error in drm_mode_object_add):/ the UART log is at https://pastebin.com/4rv7gbYE .

Quote:Following the directions from the wiki page to connect to the UART adapter, I run into trouble as I don't see a /dev/ttyUSB0 on my system.


I first plugged the cable into the other USB port, it has to be in the one labeled DEBUG. Perhaps run "dmesg -w" and you should see something like this after you plug it in (it does not have to be in the PineTab, as it takes power from your computer):


Code:
[94825.741027] usb 1-2.4.1: new full-speed USB device number 19 using xhci_hcd
[94825.850246] usb 1-2.4.1: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice=81.33
[94825.850257] usb 1-2.4.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[94825.850261] usb 1-2.4.1: Product: USB Serial
[94825.902691] ch341 1-2.4.1:1.0: ch341-uart converter detected
[94825.909575] usb 1-2.4.1: ch341-uart converter now attached to ttyUSB0

Thanks!

Watching dmesg -w on my desktop when I plug in the adapter, I see messages like that, but then immediately afterwards it gets detached from ttyUSB0.
Only once out of the ~5 times I tried plugging it in did it remain attached to ttyUSB0. Odd. But it seems to work better with other devices.

---

And yeah, I also found warnings in dmesg around drm_mode_object_add.

Code:
[    0.826751] ------------[ cut here ]------------
[    0.826773] WARNING: CPU: 2 PID: 50 at drivers/gpu/drm/drm_mode_object.c:45 drm_mode_object_add+0x90/0x98
[    0.826811] Modules linked in:
[    0.826829] CPU: 2 PID: 50 Comm: kworker/u8:1 Not tainted 6.3.0-2-danctnix #1
[    0.826842] Hardware name: Pine64 PineTab2 v2.0 (DT)
[    0.826853] Workqueue: events_unbound deferred_probe_work_func
[    0.826876] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[    0.826889] pc : drm_mode_object_add+0x90/0x98
[    0.826904] lr : drm_property_create+0xd0/0x188
[    0.826917] sp : ffff8000098735b0
[    0.826925] x29: ffff8000098735b0 x28: ffff0001f17b3480 x27: 0000000000000037
[    0.826948] x26: 0000000000001000 x25: 0000000000001000 x24: ffff0001f1705800
[    0.826970] x23: ffff800008f160c0 x22: 0000000000000004 x21: 00000000b0b0b0b0
[    0.826991] x20: ffff0001f21db590 x19: ffff0001f1705800 x18: ffff80000985d110
[    0.827012] x17: 286e201ed0517200 x16: 1d01010101010101 x15: ffff800009873550
[    0.827033] x14: ffff0001f21db170 x13: ffff0001f21db154 x12: 00000000000001ef
[    0.827054] x11: 000000000000020d x10: 0000000000000078 x9 : 0000000000000000
[    0.827074] x8 : ffff0001f21db580 x7 : 0000000000000000 x6 : 000000000000003f
[    0.827095] x5 : 0000000000000040 x4 : ffff8000098735c0 x3 : 0000000000000000
[    0.827115] x2 : 00000000b0b0b0b0 x1 : ffff0001f21db590 x0 : 0000000000000001
[    0.827136] Call trace:
[    0.827143]  drm_mode_object_add+0x90/0x98
[    0.827159]  drm_property_create+0xd0/0x188
[    0.827172]  drm_property_create_enum+0x30/0x94
[    0.827184]  drm_connector_set_panel_orientation+0x94/0xb4
[    0.827200]  boe_get_modes+0x70/0xbc
[    0.827214]  drm_panel_get_modes+0x28/0x48
[    0.827229]  panel_bridge_connector_get_modes+0x1c/0x2c
[    0.827246]  drm_helper_probe_single_connector_modes+0x1a4/0x52c
[    0.827258]  drm_client_modeset_probe+0x204/0x1194
[    0.827271]  __drm_fb_helper_initial_config_and_unlock+0x54/0x494
[    0.827285]  drm_fb_helper_initial_config+0x4c/0x60
[    0.827298]  drm_fbdev_client_hotplug+0x8c/0xd8
[    0.827310]  drm_fbdev_generic_setup+0x90/0x170
[    0.827324]  rockchip_drm_bind+0x1ec/0x208
[    0.827341]  try_to_bring_up_aggregate_device+0x170/0x1c0
[    0.827359]  __component_add+0xa8/0x174
[    0.827373]  component_add+0x18/0x28
[    0.827389]  dw_mipi_dsi_rockchip_host_attach+0x5c/0x14c
[    0.827403]  dw_mipi_dsi_host_attach+0x98/0xcc
[    0.827415]  mipi_dsi_attach+0x2c/0x44
[    0.827429]  boe_dsi_probe+0xf8/0x1a0
[    0.827443]  mipi_dsi_drv_probe+0x24/0x34
[    0.827457]  really_probe+0x150/0x2b4
[    0.827471]  __driver_probe_device+0x7c/0xe8
[    0.827485]  driver_probe_device+0x40/0x164
[    0.827498]  __device_attach_driver+0xc4/0x144
[    0.827513]  bus_for_each_drv+0x88/0xe8
[    0.827526]  __device_attach+0xa0/0x190
[    0.827539]  device_initial_probe+0x18/0x28
[    0.827554]  bus_probe_device+0xb0/0xb4
[    0.827568]  deferred_probe_work_func+0x88/0xc4
[    0.827583]  process_one_work+0x1dc/0x340
[    0.827600]  worker_thread+0x224/0x434
[    0.827614]  kthread+0x10c/0x110
[    0.827626]  ret_from_fork+0x10/0x20
[    0.827644] ---[ end trace 0000000000000000 ]---
[    0.827699] ------------[ cut here ]------------
[    0.827707] WARNING: CPU: 2 PID: 50 at drivers/gpu/drm/drm_mode_object.c:242 drm_object_attach_property+0x6c/0xb8
[    0.827733] Modules linked in:
[    0.827746] CPU: 2 PID: 50 Comm: kworker/u8:1 Tainted: G        W          6.3.0-2-danctnix #1
[    0.827759] Hardware name: Pine64 PineTab2 v2.0 (DT)
[    0.827768] Workqueue: events_unbound deferred_probe_work_func
[    0.827787] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[    0.827800] pc : drm_object_attach_property+0x6c/0xb8
[    0.827814] lr : drm_connector_set_panel_orientation+0x68/0xb4
[    0.827828] sp : ffff800009873650
[    0.827835] x29: ffff800009873650 x28: ffff0001f17b3480 x27: 0000000000000037
[    0.827858] x26: 0000000000001000 x25: 0000000000001000 x24: ffff0001f1705800
[    0.827880] x23: 00000000fffffffd x22: ffff0001f0234380 x21: ffff0001f1705800
[    0.827902] x20: ffff0001f1705238 x19: ffff0001f1705170 x18: ffff80000985d0f8
[    0.827923] x17: 286e201ed0517200 x16: 1d01010101010101 x15: ffff800009873550
[    0.827944] x14: ffff0001f21db170 x13: ffff0001f21db154 x12: 00000000000001ef
[    0.827964] x11: 000000000000020d x10: 0000000000000078 x9 : 0000000000000000
[    0.827985] x8 : ffff0001f21db638 x7 : 00000000c0c0c0c0 x6 : 00000000c0c0c0c0
[    0.828006] x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000006
[    0.828025] x2 : 0000000000000003 x1 : ffff0001f21db580 x0 : ffff0001f17051b0
[    0.828046] Call trace:
[    0.828052]  drm_object_attach_property+0x6c/0xb8
[    0.828067]  boe_get_modes+0x70/0xbc
[    0.828081]  drm_panel_get_modes+0x28/0x48
[    0.828097]  panel_bridge_connector_get_modes+0x1c/0x2c
[    0.828111]  drm_helper_probe_single_connector_modes+0x1a4/0x52c
[    0.828123]  drm_client_modeset_probe+0x204/0x1194
[    0.828138]  __drm_fb_helper_initial_config_and_unlock+0x54/0x494
[    0.828153]  drm_fb_helper_initial_config+0x4c/0x60
[    0.828166]  drm_fbdev_client_hotplug+0x8c/0xd8
[    0.828178]  drm_fbdev_generic_setup+0x90/0x170
[    0.828189]  rockchip_drm_bind+0x1ec/0x208
[    0.828205]  try_to_bring_up_aggregate_device+0x170/0x1c0
[    0.828224]  __component_add+0xa8/0x174
[    0.828238]  component_add+0x18/0x28
[    0.828252]  dw_mipi_dsi_rockchip_host_attach+0x5c/0x14c
[    0.828266]  dw_mipi_dsi_host_attach+0x98/0xcc
[    0.828279]  mipi_dsi_attach+0x2c/0x44
[    0.828293]  boe_dsi_probe+0xf8/0x1a0
[    0.828305]  mipi_dsi_drv_probe+0x24/0x34
[    0.828318]  really_probe+0x150/0x2b4
[    0.828332]  __driver_probe_device+0x7c/0xe8
[    0.828345]  driver_probe_device+0x40/0x164
[    0.828358]  __device_attach_driver+0xc4/0x144
[    0.828371]  bus_for_each_drv+0x88/0xe8
[    0.828384]  __device_attach+0xa0/0x190
[    0.828397]  device_initial_probe+0x18/0x28
[    0.828412]  bus_probe_device+0xb0/0xb4
[    0.828425]  deferred_probe_work_func+0x88/0xc4
[    0.828439]  process_one_work+0x1dc/0x340
[    0.828454]  worker_thread+0x224/0x434
[    0.828468]  kthread+0x10c/0x110
[    0.828479]  ret_from_fork+0x10/0x20
[    0.828494] ---[ end trace 0000000000000000 ]---
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Pinetab2 screen removal Corconegre 5 1,117 01-10-2024, 08:08 AM
Last Post: stozi
  Not able to power on PineTab anymore zkajdan 3 320 12-26-2023, 04:38 PM
Last Post: FortunateFowl
Question Will Pinetab 2 spare parts be available? vatin 6 1,312 12-09-2023, 01:31 AM
Last Post: tllim
  ?brighter screen replacement for pinetab (>1600 nits) dynobang 0 464 09-28-2023, 01:06 PM
Last Post: dynobang
  [Tutorial] How to overclock Pinetab 2 Darth-Apple 0 700 09-25-2023, 08:45 AM
Last Post: Darth-Apple
  External Reset button on PineTab V? michaelengel 0 461 09-18-2023, 06:31 AM
Last Post: michaelengel
  PineTab2 screen won't turn back on until reboot KelsonV 3 886 08-23-2023, 09:08 AM
Last Post: diederik
  Pinetab completely bricked Saksmito 8 2,296 06-10-2023, 04:23 PM
Last Post: fxc
  What RISC-V chip will the PineTab-V use? msm 2 1,536 04-05-2023, 06:58 PM
Last Post: msm
Big Grin Howto: Pinetab Screen Replacements (+ Pictures) RTP 5 6,093 02-10-2022, 08:31 PM
Last Post: barray

Forum Jump:


Users browsing this thread: 1 Guest(s)