Comment 41 for bug 1467542

Revision history for this message
Thierry FAUCK (thierry-j) wrote :

On VIVID, I get the following messages in /var/log/syslog - need to check why

Sep 15 09:37:55 abanb systemd[1]: Starting OPAL PRD daemon...
Sep 15 09:37:55 abanb opal-prd: I2C: Found Chip: 80000001 engine 0 port 0
Sep 15 09:37:55 abanb opal-prd: I2C: Found Chip: 80000001 engine 0 port 1
Sep 15 09:37:55 abanb opal-prd: I2C: Found Chip: 00000000 engine 0 port 0
Sep 15 09:37:55 abanb opal-prd: I2C: Found Chip: 00000000 engine 0 port 1
Sep 15 09:37:55 abanb opal-prd: I2C: Found Chip: 00000000 engine 1 port 2
Sep 15 09:37:55 abanb opal-prd: I2C: Found Chip: 80000004 engine 0 port 0
Sep 15 09:37:55 abanb opal-prd: I2C: Found Chip: 80000004 engine 0 port 1
Sep 15 09:37:55 abanb opal-prd: I2C: Found Chip: 80000000 engine 0 port 0
Sep 15 09:37:55 abanb opal-prd: I2C: Found Chip: 80000000 engine 0 port 1
Sep 15 09:37:55 abanb opal-prd: I2C: Found Chip: 80000005 engine 0 port 0
Sep 15 09:37:55 abanb opal-prd: I2C: Found Chip: 80000005 engine 0 port 1
Sep 15 09:37:55 abanb opal-prd: CTRL: Listening on control socket /run/opal-prd-control
Sep 15 09:37:55 abanb opal-prd: FW: Can't open PRD device /dev/opal-prd: No such file or directory
Sep 15 09:37:55 abanb opal-prd: FW: Error initialising PRD channel
Sep 15 09:37:55 abanb systemd[1]: opal-prd.service: main process exited, code=exited, status=1/FAILURE
Sep 15 09:37:55 abanb systemd[1]: Unit opal-prd.service entered failed state.
Sep 15 09:37:55 abanb systemd[1]: opal-prd.service failed.