HDMI troubles with Pinephone beta edition
#1
HI all, i just recieved my beta edition of the pinephone, and was very excited to try out the HDMI docking features as i have previously been using a UB Ports edition which does not support the feature.

However i am unable to get the phone to recognize that a HDMI cable is connected, i have tried under factory Manjaro Plasma, Manajaro Phosh Beta 8 and Mobian nightly with no luck. I was under the impression that HDMI out was mostly supported as of now? is there some setup that I'm missing? does it only work on certain distros? is it just broken atm?

Any help is very appreciated, overall i am head over heels with this device, it's exactly what i've been missing form my life!
  Reply
#2
When using Mobian, you can check for kernal messages with this command:
sudo dmesg

That might tell you what is the problem when you plug in the device. Also remember that you are using USB-C DisplayPort Alt Mode and it is your USB-C to HDMI cable which is doing the conversion to HDMI, so you are looking for error messages about DisplayPort in dmesg. You might want to verify that your cable is good or try it with a different cable.
  Reply
#3
Log from PostmarketOS

Code:
[ 2397.612464] anx7688 1-0028: plug irq (cd=1)
[ 2397.625867] anx7688 1-0028: cable inserted
[ 2397.674006] anx7688 1-0028: power enabled
[ 2397.746000] anx7688 1-0028: eeprom0 = 0x03
[ 2397.746037] anx7688 1-0028: fw loaded after 40 ms
[ 2397.746231] anx7688 1-0028: OCM firmware loaded (version 0x2312)
[ 2397.747442] anx7688 1-0028: send pd packet cmd=0x00 05 00 32 90 01 26 12
[ 2397.787147] anx7688 1-0028: send pd packet cmd=0x01 05 01 2c 91 01 26 16
[ 2397.787761] anx7688 1-0028: send pd packet cmd=0x02 11 02 00 00 00 ec 00 00 00 00 00 00 00 00 39 00 00 51 77
[ 2397.788615] anx7688 1-0028: send pd packet cmd=0x03 05 03 00 00 01 ff f8
[ 2397.789162] anx7688 1-0028: OCM configuration completed
[ 2397.789935] anx7688 1-0028: status changed to 0x00
[ 2397.789958] anx7688 1-0028: cc_status changed to CC1 = SRC.Open CC2 = SRC.Open
[ 2397.789970] anx7688 1-0028: DP state changed to 0x00
[ 2397.789982] anx7688 1-0028: VCONN role change to SINK
[ 2397.790019] anx7688 1-0028: DATA role change requested to UFP
[ 2398.230593] anx7688 1-0028: cc_status changed to CC1 = SRC.Open CC2 = SNK.Power3.0
[ 2398.337602] anx7688 1-0028: recv ocm message cmd=0x00 05 00 c8 90 01 2e 74
[ 2398.337669] anx7688 1-0028: received SRC_CAP
[ 2398.337677] anx7688 1-0028: SRC_CAP PDO_FIXED (5000mV 2000mA)
[ 2398.337996] anx7688 1-0028: RDO max voltage = 5000mV, max power = 10000mW, PD current limit = 2000mA
[ 2398.341171] anx7688 1-0028: recv ocm message cmd=0xf0 03 f0 16 00 f7
[ 2398.341213] anx7688 1-0028: received response to PWR_OBJ_REQ (SUCCESS)
[ 2398.858373] anx7688 1-0028: updating power mode to PD, current limit 2000mA (0 => BC1.2)
[ 2398.858439] anx7688 1-0028: disabling USB BC 1.2 detection
[ 2398.858554] anx7688 1-0028: setting vbus_in current limit to 2000 mA
[ 2398.858640] anx7688 1-0028: enabling vbus_in power path
[ 2398.964202] anx7688 1-0028: recv ocm message cmd=0x11 01 11 ee
[ 2398.964246] anx7688 1-0028: received DSWAP_REQ
[ 2398.964652] anx7688 1-0028: status changed to 0x20
[ 2398.964783] anx7688 1-0028: DATA role change requested to DFP
[ 2398.981422] anx7688 1-0028: BC 1.2 result: SDP
[ 2399.017500] anx7688 1-0028: recv ocm message cmd=0xf0 03 f0 13 00 fa
[ 2399.017538] anx7688 1-0028: received response to VCONN_SWAP_REQ (SUCCESS)
[ 2399.017993] anx7688 1-0028: status changed to 0x24
[ 2399.018010] anx7688 1-0028: VCONN role change to SOURCE
[ 2399.044220] anx7688 1-0028: recv ocm message cmd=0x02 11 02 39 06 00 6c 00 00 00 00 12 02 20 a0 db 00 00 00 93
[ 2399.044256] anx7688 1-0028: received DP_SNK_IDENTITY
[ 2399.047997] anx7688 1-0028: recv ocm message cmd=0x03 09 03 39 06 01 ff 00 00 00 00 b5
[ 2399.048031] anx7688 1-0028: received SVID
[ 2399.061529] anx7688 1-0028: recv ocm message cmd=0x27 09 27 03 80 01 ff 05 0c 00 00 3c
[ 2399.062526] anx7688 1-0028: received unknown message 0x27
[ 2399.072224] anx7688 1-0028: recv ocm message cmd=0x19 01 19 e6
[ 2399.072720] anx7688 1-0028: received DP_ALT_ENTER
[ 2399.221871] usb 1-1: new high-speed USB device number 40 using ehci-platform
[ 2399.383669] hub 1-1:1.0: USB hub found
[ 2399.384087] hub 1-1:1.0: 4 ports detected
[ 2399.769785] usb 1-1.1: new full-speed USB device number 41 using ehci-platform
[ 2400.161850] usb 1-1.2: new high-speed USB device number 42 using ehci-platform
[ 2400.374422] cdc_ether 1-1.2:2.0 eth0: register 'cdc_ether' at usb-1c1a000.usb-1.2, CDC Ethernet Device, 00:00:00:00:19:87
[ 2402.090197] anx7688 1-0028: DP state changed to 0x03

Thanks for the reply Smile

Here is my dmesg output after connecting the dock, (let me know if a full log would be more useful). Nothing immediately obvious jumps out at me, except maybe the part about "received unknown message 0x27".

As for the Dock/HDMI cable, both are working with my android phone and my razer laptop, so presumably the hardware is ok.

Edit: tried again with mobian and got some different output
Code:
[  725.595511] anx7688 1-0028: cable inserted
[  725.635524] anx7688 1-0028: power enabled
[  725.699708] anx7688 1-0028: eeprom0 = 0x03
[  725.699726] anx7688 1-0028: fw loaded after 40 ms
[  725.707683] anx7688 1-0028: OCM firmware loaded (version 0x2410)
[  725.718560] anx7688 1-0028: send pd packet cmd=0 05 00 32 90 01 26 12
[  725.748675] anx7688 1-0028: send pd packet cmd=1 05 01 2c 91 01 26 16
[  725.749208] anx7688 1-0028: send pd packet cmd=2 11 02 00 00 00 ec 00 00 00 00 00 00 00 00 39 00 00 51 77
[  725.750013] anx7688 1-0028: send pd packet cmd=3 05 03 00 00 01 ff f8
[  725.750507] anx7688 1-0028: OCM configuration completed
[  725.751230] anx7688 1-0028: status changed to 0x00
[  725.751243] anx7688 1-0028: cc_status changed to CC1 = SRC.Open CC2 = SRC.Open
[  725.751248] anx7688 1-0028: dp state changed to 0x00
[  725.751267] anx7688 1-0028: data role change requested to ufp
[  726.191198] anx7688 1-0028: status irq
[  726.191702] anx7688 1-0028:   soft = 0x38
[  726.192074] anx7688 1-0028: cc_status changed to CC1 = SRC.Open CC2 = SNK.Power3.0
[  726.270154] anx7688 1-0028: status irq
[  726.270655] anx7688 1-0028:   soft = 0x01
[  726.271783] anx7688 1-0028: recv ocm message cmd=0 05 00 c8 90 01 2e 74
[  726.272074] anx7688 1-0028: status irq
[  726.272571] anx7688 1-0028:   soft = 0x01
[  726.273649] anx7688 1-0028: recv ocm message cmd=240 03 f0 16 00 f7
[  726.302826] anx7688 1-0028: status irq
[  726.303353] anx7688 1-0028:   soft = 0x40
[  726.894596] anx7688 1-0028: status irq
[  726.895130] anx7688 1-0028:   soft = 0x21
[  726.896219] anx7688 1-0028: recv ocm message cmd=17 01 11 ee
[  726.896609] anx7688 1-0028: status changed to 0x20
[  726.896749] anx7688 1-0028: data role change requested to dfp
[  726.896821] phy id_det change to host
[  726.947409] anx7688 1-0028: status irq
[  726.947927] anx7688 1-0028:   soft = 0x05
[  726.948945] anx7688 1-0028: recv ocm message cmd=240 03 f0 13 00 fa
[  726.949325] anx7688 1-0028: status changed to 0x24
[  726.971835] anx7688 1-0028: status irq
[  726.972465] anx7688 1-0028:   soft = 0x01
[  726.977811] anx7688 1-0028: recv ocm message cmd=2 11 02 39 06 00 6c 00 00 00 00 12 02 20 a0 db 00 00 00 93
[  726.978037] anx7688 1-0028: status irq
[  726.978497] anx7688 1-0028:   soft = 0x01
[  726.979548] anx7688 1-0028: recv ocm message cmd=3 09 03 39 06 01 ff 00 00 00 00 b5
[  726.980968] anx7688 1-0028: status irq
[  726.981481] anx7688 1-0028:   soft = 0x01
[  726.982516] anx7688 1-0028: recv ocm message cmd=39 09 27 03 80 01 ff 05 0c 00 00 3c
[  726.990441] anx7688 1-0028: status irq
[  726.990989] anx7688 1-0028:   soft = 0x01
[  726.992134] anx7688 1-0028: recv ocm message cmd=25 01 19 e6
[  727.143458] usb 1-1: new high-speed USB device number 8 using ehci-platform
[  727.316097] usb 1-1: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.00
[  727.324440] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[  727.333185] usb 1-1: Product: USB2.0 HUB
[  727.342852] hub 1-1:1.0: USB hub found
[  727.346887] hub 1-1:1.0: 4 ports detected
[  727.753302] usb 1-1.1: new full-speed USB device number 9 using ehci-platform
[  727.974101] usb 1-1.1: New USB device found, idVendor=0639, idProduct=7210, bcdDevice=68.4d
[  727.982517] usb 1-1.1: New USB device strings: Mfr=1, Product=4, SerialNumber=2
[  727.989876] usb 1-1.1: Product: Billboard
[  727.993921] usb 1-1.1: Manufacturer: Chrontel
[  727.998292] usb 1-1.1: SerialNumber: CH7210
[  728.199355] usb 1-1.2: new high-speed USB device number 10 using ehci-platform
  Reply
#4
I have same problem.

I received my PinePhone Beta Edition with convergence package a few days ago. I saw other people using display output on Phosh, so I tried Mobian stable (20210324) and Mobian unstable, but could not get display output working. I also tried postmarketOS-edge with Sxmo so that I can see the output from xrandr, but the phone did not recognized any external display.

I have tested the dock bar on my tablet with Debian-Phosh, and everything worked. So the dock bar is fine. Then I tried flashing ANX7688 firmware on PinePhone, but nothing has changed.

At this point, I have no idea how to investigate the problem any further. Any help would be much appreciated.

Here is my dmesg on Mobian stable.

Code:
[  236.430531] usb 1-1: new high-speed USB device number 2 using ehci-platform
[  236.561923] anx7688 1-0028: status irq
[  236.562534] anx7688 1-0028:   soft = 0x01
[  236.563631] anx7688 1-0028: recv ocm message cmd=22 05 16 32 c8 00 12 d9
[  236.595348] usb 1-1: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.00
[  236.603612] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[  236.618530] usb 1-1: Product: USB2.0 HUB
[  236.624725] hub 1-1:1.0: USB hub found
[  236.630884] hub 1-1:1.0: 4 ports detected
[  236.692061] anx7688 1-0028: status irq
[  236.692594] anx7688 1-0028:   soft = 0x01
[  236.693721] anx7688 1-0028: recv ocm message cmd=1 05 01 2c 91 01 05 37
[  236.714554] anx7688 1-0028: status irq
[  236.715155] anx7688 1-0028:   soft = 0x01
[  236.716246] anx7688 1-0028: recv ocm message cmd=2 11 02 39 06 00 6c 00 00 00 00 12 02 20 a0 db 00 00 00 93
[  236.718463] anx7688 1-0028: status irq
[  236.719010] anx7688 1-0028:   soft = 0x01
[  236.720160] anx7688 1-0028: recv ocm message cmd=3 09 03 39 06 01 ff 00 00 00 00 b5
[  236.722061] anx7688 1-0028: status irq
[  236.722626] anx7688 1-0028:   soft = 0x01
[  236.723714] anx7688 1-0028: recv ocm message cmd=39 09 27 03 80 01 ff 05 0c 00 00 3c
[  236.733424] anx7688 1-0028: status irq
[  236.733937] anx7688 1-0028:   soft = 0x01
[  236.735052] anx7688 1-0028: recv ocm message cmd=25 01 19 e6
[  237.030564] usb 1-1.1: new full-speed USB device number 3 using ehci-platform
[  237.250008] usb 1-1.1: New USB device found, idVendor=0639, idProduct=7210, bcdDevice=68.4d
[  237.258577] usb 1-1.1: New USB device strings: Mfr=1, Product=4, SerialNumber=2
[  237.267671] usb 1-1.1: Product: Billboard
[  237.276547] usb 1-1.1: Manufacturer: Chrontel
[  237.285498] usb 1-1.1: SerialNumber: CH7210
[  237.474437] usb 1-1.2: new high-speed USB device number 4 using ehci-platform
[  237.697216] usb 1-1.2: New USB device found, idVendor=0fe6, idProduct=9900, bcdDevice=20.00
[  237.706299] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  237.713699] usb 1-1.2: Product: 10/100M LAN
[  237.719449] usb 1-1.2: Manufacturer: CoreChips
[  237.724018] usb 1-1.2: SerialNumber: 00000000008A
[  237.800937] cdc_ether 1-1.2:2.0 eth0: register 'cdc_ether' at usb-1c1a000.usb-1.2, CDC Ethernet Device, 00:00:00:00:00:8a
[  237.813176] usbcore: registered new interface driver cdc_ether
[  237.861985] cdc_ether 1-1.2:2.0 enx00000000008a: renamed from eth0
[  237.914479] usb 1-1.3: new low-speed USB device number 5 using ehci-platform
[  238.137466] usb 1-1.3: New USB device found, idVendor=1a81, idProduct=2010, bcdDevice= 1.00
[  238.145941] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  238.153305] usb 1-1.3: Product: USB KEYBOARD
[  238.157641] usb 1-1.3: Manufacturer: SINO WEALTH
[  238.170594] input: SINO WEALTH USB KEYBOARD as /devices/platform/soc/1c1a000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:1A81:2010.0001/input/input6
[  238.244431] hid-generic 0003:1A81:2010.0001: input,hidraw0: USB HID v1.10 Keyboard [SINO WEALTH USB KEYBOARD] on usb-1c1a000.usb-1.3/input0
[  238.266125] input: SINO WEALTH USB KEYBOARD System Control as /devices/platform/soc/1c1a000.usb/usb1/1-1/1-1.3/1-1.3:1.1/0003:1A81:2010.0002/input/input7
[  238.339707] input: SINO WEALTH USB KEYBOARD Consumer Control as /devices/platform/soc/1c1a000.usb/usb1/1-1/1-1.3/1-1.3:1.1/0003:1A81:2010.0002/input/input8
[  238.356125] hid-generic 0003:1A81:2010.0002: input,hiddev1,hidraw1: USB HID v1.10 Device [SINO WEALTH USB KEYBOARD] on usb-1c1a000.usb-1.3/input1
[  238.550595] usb 1-1.4: new full-speed USB device number 6 using ehci-platform
[  238.785994] usb 1-1.4: New USB device found, idVendor=056e, idProduct=00e3, bcdDevice= 2.10
[  238.796567] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  238.806800] usb 1-1.4: Product: ELECOM BlueLED Mouse
[  238.813604] usb 1-1.4: Manufacturer: ELECOM
[  238.839445] input: ELECOM ELECOM BlueLED Mouse as /devices/platform/soc/1c1a000.usb/usb1/1-1/1-1.4/1-1.4:1.0/0003:056E:00E3.0003/input/input9
[  238.867577] hid-generic 0003:056E:00E3.0003: input,hidraw2: USB HID v1.11 Mouse [ELECOM ELECOM BlueLED Mouse] on usb-1c1a000.usb-1.4/input0
[  239.551346] anx7688 1-0028: dp state changed to 0x03
[  244.303011]  mmcblk2: p1 p2
[  266.174888] anx7688 1-0028: dp state changed to 0x00
[
  Reply
#5
Today I saw this tracking issue on postmarketOS.

https://gitlab.com/postmarketOS/pmaports/-/issues/1009

A few people there reported that lower DRAM frequency may fix the problem.
I tried Manjaro phosh nightly with 492MHz u-boot image, but this did not work for me.
  Reply
#6
(04-23-2021, 08:38 PM)caveman250 Wrote: HI all, i just recieved my beta edition of the pinephone, and was very excited to try out the HDMI docking features as i have previously been using a UB Ports edition which does not support the feature.

However i am unable to get the phone to recognize that a HDMI cable is connected, i have tried under factory Manjaro Plasma, Manajaro Phosh Beta 8 and Mobian nightly with no luck. I was under the impression that HDMI out was mostly supported as of now? is there some setup that I'm missing? does it only work on certain distros? is it just broken atm?

Any help is very appreciated, overall i am head over heels with this device, it's exactly what i've been missing form my life!
Hello there, I'm in the same predicament as you, 
When my phone arrived, I first tested it with the pre-installed Plasma Mobile, and the HDMI output actually worked. After I flashed Majanro/Phosh it stopped working. I tried reinstalling Plasma Mobile, with no luck making it work again, I've also tried Arch/Phosh with no luck neither. I've confirmed my issue doesn't come from the adapter itself. I've been trying to figure it out all afternoon and I have found myself defeated for today. I'll try poking around it tomorrow, but as far as I can see, I don't know what else to try. 'dmesg' doesn't return anything about DP, except for
'
anx7688 1-0028: DP state changed to 0x00'
and
'
anx7688 1-0028: DP state changed to 0x03'
Hope this can help, cheers!
  Reply
#7
I just tried the Beta Edition with the docking bar from the convergence package together with Phosh on Mobian stable 20210314 and it worked, but only after several software restarts of the device and inserting/pulling the cable into the phone. Then, without restarting the device it worked each time just by pulling and inserting the cable. It was quite slow to initialize (needed several seconds) and while waiting I did poke at the "undocked" icon from the top menu, but I'm not sure if that helped.

I hope this helps and good luck!
  Reply
#8
(05-13-2021, 11:11 AM)bosi564 Wrote: I just tried the Beta Edition with the docking bar from the convergence package together with Phosh on Mobian stable 20210314 and it worked, but only after several software restarts of the device and inserting/pulling the cable into the phone. Then, without restarting the device it worked each time just by pulling and inserting the cable. It was quite slow to initialize (needed several seconds) and while waiting I did poke at the "undocked" icon from the top menu, but I'm not sure if that helped.

I hope this helps and good luck!

Thank you for your help!

I tried Mobian stable 20210314 again. At first boot, it did not work. After reboot, display output worked! Then I rebooted into Mobian unstable installed on eMMC, and now display output also working here!

I don't know why, but it somehow resolved the problem for me.
  Reply
#9
Is the reboot fix related to the last shipped Pinephones? I'm curious
  Reply
#10
Quote:There are still some HDMI issues some people keep reporting, that manifest themselves by anx7688 firmware not getting past „DP status = 0×03“ (it should go from 0 all the way to 6 normally). When this happens it's caused by HDMI controller inside the SoC using incorrect clock frequency, and anx7688 fails to acquire the HDMI signal from the SoC. It should be easy to fix, but I have trouble reproducing it with my kernel and userspace, so I can't identify the root of the problem, yet.

megi mentioned this problem in the latest dev log entry.

I appreciated the note about what the dmesg entry is supposed to report since mine is showing the 0x03 behavior. Now I have a better idea of what to look for as I'm testing.
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  UPDATED (June 2021): 17-distro multi-boot image for Pinephone (incl. 3GiB variant) megous 151 94,755 Yesterday, 01:37 PM
Last Post: calinb
  Pinephone 3/32GB , convergence, beta edition for sale -- Europe(Czech republice) pom3ranc 3 225 06-16-2021, 02:46 PM
Last Post: piner67
  My PinePhone shuts down when the screen turns off rvbarreto 0 76 06-13-2021, 05:11 PM
Last Post: rvbarreto
  Are you using the Pinephone as your daily driver? jro 28 3,659 06-11-2021, 04:31 PM
Last Post: OhneZ
  Manjaro Phosh Beta 10...how to get button labels on Angelfish? INSTRUCTIONS WITHIN patrio 4 254 06-11-2021, 07:10 AM
Last Post: patrio
  Buiding apps for pinephone katesfb 6 547 06-10-2021, 10:52 PM
Last Post: katesfb
  The Best Feature of the PinePhone is... Dog House Dave 8 443 06-08-2021, 06:22 PM
Last Post: ryo
Heart What native PinePhone application would you like to see in the near future? kern707 61 9,221 06-05-2021, 04:13 PM
Last Post: AwHereWeGoAgain
  List of Pinephone browsers Gamey 15 3,119 06-04-2021, 11:22 AM
Last Post: ryo
  PinePhone Game Thread PixelPaintbrush 15 6,953 06-02-2021, 05:07 AM
Last Post: biketool

Forum Jump:


Users browsing this thread: 1 Guest(s)