01-16-2019, 03:18 PM
I think I found** the permanent fix for this particular error message.
After digging around a LOT of forums in regards to the filename (dptx.bin), I found not only the original commit in 2016 for this file in a chromiumOS forum (see this post) and where it belongs (see this post), but I also traced it down to what the file's purpose is (listed below). I was also able to find the actual dptx.bin file necessary to make the problem go away. This was done in both Debian and Ubuntu images from Ayufan.
(**I don't assume I'm the 1st one to find this, but I didn't find the answer in my searches. They're as flawed as I am, I admit.)
Original Commit, from Chromium OS checkins, dated 7/21/16
https://i.imgur.com/fGAD5RB.png
After scouring (and trial-and-error), I found the appropriate file in the following repo location:
https://github.com/wkennington/linux-fir...p/dptx.bin
I'm even going to attach it, in case the repo goes bye-bye. But basic instructions are as below.
1. Using a simple wget, from root's home directory:
2. Now, copy it over to the requisite directory where it's expected to be (works in both Ubuntu and Debian):
Now, on reboot, the error messages go away. I'm so surprised that it worked, I swear I did something wrong.
Critiquing is welcome. Thanks for reading.
(Yes, I run as root. My network's secure, and nobody in my network cares. The closest they get to Linus is saying he walks around with a blanket.)
After digging around a LOT of forums in regards to the filename (dptx.bin), I found not only the original commit in 2016 for this file in a chromiumOS forum (see this post) and where it belongs (see this post), but I also traced it down to what the file's purpose is (listed below). I was also able to find the actual dptx.bin file necessary to make the problem go away. This was done in both Debian and Ubuntu images from Ayufan.
(**I don't assume I'm the 1st one to find this, but I didn't find the answer in my searches. They're as flawed as I am, I admit.)
Original Commit, from Chromium OS checkins, dated 7/21/16
https://i.imgur.com/fGAD5RB.png
Quote:This series patch is for rockchip Type-C DisplayPort controller driver.
The USB Type-C PHY is designed to support the USB3 and DP applications.
The PHY basically has two main components: USB3 and DisplayPort. USB3
operates in SuperSpeed mode and the DP can operate at RBR, HBR and HBR2
data rates. The Type-C cable orientation detection and Power Delivery
(PD) is accomplished using a PD PHY or an external PD chip.
The DP controller is compliant with DisplayPort Specification,
Version 1.3, This IP is compatible with the rockchip type-c PHY IP.
There is a uCPU in DP controller, it need a firmware to work, please
put the firmware file[0] rockchip/dptx.bin to
/lib/firmware/rockchip/dptx.bin. The uCPU in charge of aux communication
and link training, the host use mailbox to communicate with the ucpu.
After scouring (and trial-and-error), I found the appropriate file in the following repo location:
https://github.com/wkennington/linux-fir...p/dptx.bin
I'm even going to attach it, in case the repo goes bye-bye. But basic instructions are as below.
1. Using a simple wget, from root's home directory:
Code:
root@rockpro64:/home/rock64# wget https://raw.githubusercontent.com/wkennington/linux-firmware/master/rockchip/dptx.bin2. Now, copy it over to the requisite directory where it's expected to be (works in both Ubuntu and Debian):
Code:
cp /home/rock64/dptx.bin /lib/firmware/rockchip/dptx.binNow, on reboot, the error messages go away. I'm so surprised that it worked, I swear I did something wrong.
Critiquing is welcome. Thanks for reading.
(Yes, I run as root. My network's secure, and nobody in my network cares. The closest they get to Linus is saying he walks around with a blanket.)
