Pinetab 2 screen no longer coming on
#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


Messages In This Thread
RE: Pinetab 2 screen no longer coming on - by fxc - 06-22-2023, 02:23 PM
RE: Pinetab 2 screen no longer coming on - by fxc - 06-24-2023, 02:29 PM
RE: Pinetab 2 screen no longer coming on - by Purple_Illusion - 06-30-2023, 08:26 AM

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

Forum Jump:


Users browsing this thread: 1 Guest(s)