What does the "i2c should be 0x03 on cable detect" PCoIP Zero Client event log error indicate?
Answer:
Faulty cables interfere with the mechanisms in which PCoIP detects displays and can present a variety of errors. The i2c should be 0x03 on cable detect PCoIP Zero Client log errors are usually indicative of faulty cables and occasionally of faulty hardware. Issues that may be present when using faulty cables in a deployment are:
- Monitors show no display
- EDID errors appear
- Monitors are not being recognized
- Replacing the PCoIP Zero Client with another PCoIP Zero Client appears to fix the issue
- Event log errors such as:
0d,05:06:58> LVL:1 RC:-500 DDC :(tera_ddc_is_duallink_cable_present): (0xbb006a40:0x00000000): i2c should be 0x03 on cable detect
0d,05:07:00> LVL:1 RC:-500 DDC :(tera_ddc_is_duallink_cable_present): (0xbb006a40:0x00000000): i2c should be 0x03 on cable detect
0d,05:07:03> LVL:1 RC:-500 DDC :(tera_ddc_is_duallink_cable_present): (0xbb006a40:0x00000000): i2c should be 0x03 on cable detect
0d,05:07:05> LVL:1 RC:-500 DDC :(tera_ddc_is_duallink_cable_present): (0xbb006a40:0x00000000): i2c should be 0x03 on cable detect
If these event log errors are seen, replace the cable with a known working cable and test your configuration again.
Pertains to:
- PCoIP Zero Client 4.0.2
- PCoIP Zero Client 4.0.3
- PCoIP Zero Client 4.1.0
- PCoIP Zero Client 4.1.1
- PCoIP Zero Client 4.1.2
- PCoIP Zero Client 4.2.0
- PCoIP Zero Client 4.5.0
- PCoIP Zero Client 4.5.1
- PCoIP Zero Client 4.6.0
- PCoIP Zero Client 4.7.0
- PCoIP Zero Client 4.7.1
- PCoIP Zero Client 4.8.0
- PCoIP Zero Client 4.8.1
- PCoIP Zero Client 4.8.2
- PCoIP Zero Client 5.0.0
- PCoIP Zero Client 5.0.2
- PCoIP Zero Client 5.1.0
- PCoIP Zero Client 5.1.1
- PCoIP Zero Client 5.2.0
- PCoIP Zero Client 5.2.1
- PCoIP Zero Client 5.2.2
- PCoIP Zero Client 5.3.0
- PCoIP Zero Client 5.4.0
- PCoIP Zero Client 5.4.1
- PCoIP Zero Client 5.5.0
- PCoIP Zero Client 5.5.1
- PCoIP Zero Client 6.0.0