CONFIG_TCG_TPM is not enabled in the kernel.shige3106 wrote: Could you let me know the availaility of TCG TPM driver below ?
It was only the zero that didn't boot correctly. It was booted but half the services didn't start. When I tried rpi-update to revert things that process simply hung. So I pulled the card and fixed it on another RPi.MaxK1 wrote:@Dougie - Is this a problem unique to the Zero? How does it manifest itself? I have updated one of my Pi3's and have not noticed anything awry (yet!)
Code: Select all
[ 3.061537] snd-rpi-hifiberry-dacplus soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered
[ 3.061689] snd-rpi-hifiberry-dacplus soc:sound: snd_soc_register_card() failed: -517
[ 3.128564] snd-rpi-hifiberry-dacplus soc:sound: pcm512x-hifi <-> 3f203000.i2s mapping ok
-517 is EPROBE_DEFER. That is normal. Linux will try to probe all modules when booting.Vanfanel wrote:After updating to firmware next (4.9 actually), I am getting:
Code: Select all
[ 3.061537] snd-rpi-hifiberry-dacplus soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered [ 3.061689] snd-rpi-hifiberry-dacplus soc:sound: snd_soc_register_card() failed: -517 [ 3.128564] snd-rpi-hifiberry-dacplus soc:sound: pcm512x-hifi <-> 3f203000.i2s mapping ok
Great, I will ignore it then.. any idea to try to make it go? I love clean boots... thanks!dom wrote:Vanfanel wrote:After updating to firmware next (4.9 actually), I am getting:
Code: Select all
[ 3.061537] snd-rpi-hifiberry-dacplus soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered [ 3.061689] snd-rpi-hifiberry-dacplus soc:sound: snd_soc_register_card() failed: -517 [ 3.128564] snd-rpi-hifiberry-dacplus soc:sound: pcm512x-hifi <-> 3f203000.i2s mapping ok
-517 is EPROBE_DEFER. That is normal. Linux will try to probe all modules when booting.
Some modules are dependent on other module and depending on ordering it may request to be called again later (EPROBE_DEFER). The later call does succeed.
As booting uses multiple cores the actual ordering of the probes can vary, meaning you may or may not see this message. It is harmless.
I believet that TPM is important for secure boot for Iot or security...dom wrote:CONFIG_TCG_TPM is not enabled in the kernel.shige3106 wrote: Could you let me know the availaility of TCG TPM driver below ?
If you want it to be then you'll have to explain how this is generally useful.
There was some discussion of it here but it didn't seem too popular.
Code: Select all
/dts-v1/;
/include/ "bcm2709.dtsi"
/ {
compatible = "brcm,bcm2709";
model = "Raspberry Pi 2 Model B";
};
&gpio {
sdhost_pins: sdhost_pins {
brcm,pins = <48 49 50 51 52 53>;
brcm,function = <4>; /* alt0 */
};
spi0_pins: spi0_pins {
brcm,pins = <7 8 9 10 11>;
brcm,function = <4>; /* alt0 */
};
i2c0_pins: i2c0 {
brcm,pins = <0 1>;
brcm,function = <4>;
};
i2c1_pins: i2c1 {
brcm,pins = <2 3>;
brcm,function = <4>;
};
i2s_pins: i2s {
brcm,pins = <18 19 20 21>;
brcm,function = <4>; /* alt0 */
};
};
&sdhost {
pinctrl-names = "default";
pinctrl-0 = <&sdhost_pins>;
bus-width = <4>;
status = "okay";
};
&fb {
status = "okay";
};
&uart0 {
status = "okay";
};
&spi0 {
pinctrl-names = "default";
pinctrl-0 = <&spi0_pins>;
tcg-tpm-tis-spi@0 {
compatible = "tcg,tpm_tis-spi";
reg = <0>;
#address-cells = <1>;
#size-cells = <0>;
spi-max-frequency = <500000>;
};
};
&i2c0 {
pinctrl-names = "default";
pinctrl-0 = <&i2c0_pins>;
clock-frequency = <100000>;
};
&i2c1 {
pinctrl-names = "default";
pinctrl-0 = <&i2c1_pins>;
clock-frequency = <100000>;
};
&i2c2 {
clock-frequency = <100000>;
};
&i2s {
#sound-dai-cells = <0>;
pinctrl-names = "default";
pinctrl-0 = <&i2s_pins>;
};
&random {
status = "okay";
};
&leds {
act_led: act {
label = "led0";
linux,default-trigger = "mmc0";
gpios = <&gpio 47 0>;
};
pwr_led: pwr {
label = "led1";
linux,default-trigger = "input";
gpios = <&gpio 35 0>;
};
};
/ {
__overrides__ {
uart0 = <&uart0>,"status";
uart0_clkrate = <&clk_uart0>,"clock-frequency:0";
i2s = <&i2s>,"status";
spi = <&spi0>,"status";
i2c0 = <&i2c0>,"status";
i2c1 = <&i2c1>,"status";
i2c2_iknowwhatimdoing = <&i2c2>,"status";
i2c0_baudrate = <&i2c0>,"clock-frequency:0";
i2c1_baudrate = <&i2c1>,"clock-frequency:0";
i2c2_baudrate = <&i2c2>,"clock-frequency:0";
core_freq = <&clk_core>,"clock-frequency:0";
act_led_gpio = <&act_led>,"gpios:4";
act_led_activelow = <&act_led>,"gpios:8";
act_led_trigger = <&act_led>,"linux,default-trigger";
pwr_led_gpio = <&pwr_led>,"gpios:4";
pwr_led_activelow = <&pwr_led>,"gpios:8";
pwr_led_trigger = <&pwr_led>,"linux,default-trigger";
audio = <&audio>,"status";
watchdog = <&watchdog>,"status";
random = <&random>,"status";
sd_overclock = <&sdhost>,"brcm,overclock-50:0";
sd_force_pio = <&sdhost>,"brcm,force-pio?";
sd_pio_limit = <&sdhost>,"brcm,pio-limit:0";
sd_debug = <&sdhost>,"brcm,debug";
};
};
Chromium doesn't support HW video decode on 4.9 yet (we are testing a version which does work but it's not been pushed out yet).cjan wrote:last update to #966, chromium youtube crashed.
ps. did not enable VC4.
These messages are silenced in latest 4.9 kernel.Vanfanel wrote:After updating to firmware next (4.9 actually), I am getting:
I am using the Hifiberry dac, yes. But those weren't there before.Code: Select all
[ 3.061537] snd-rpi-hifiberry-dacplus soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered [ 3.061689] snd-rpi-hifiberry-dacplus soc:sound: snd_soc_register_card() failed: -517 [ 3.128564] snd-rpi-hifiberry-dacplus soc:sound: pcm512x-hifi <-> 3f203000.i2s mapping ok
I went back to 4.4 and I am still getting the same messages...
This is fixed in latest 4.9 kernel.dukla2000 wrote: Did noticein dmesg for each CPU - think its new but can't notice any consequent problems.[/code]Code: Select all
[ 0.000000] arm_arch_timer: WARNING: Invalid trigger for IRQ16, assuming level low [ 0.000000] arm_arch_timer: WARNING: Please fix your firmware [ 0.000000] arm_arch_timer: WARNING: Invalid trigger for IRQ17, assuming level low [ 0.000000] arm_arch_timer: WARNING: Please fix your firmware
Code: Select all
uname -a
Linux thing_three 4.9.9-v7+ #966 SMP Tue Feb 14 13:20:10 GMT 2017 armv7l GNU/Linux
Twelve out of my fourteen raspberries are running 4.9.9+ #966 or 4.9.9-v7+ #966. Two of those machines are running Raspbian Stretch rather than Raspbian Jessie (even though that's not yet a mainstream release).ktb wrote:Agreed. BRANCH=next is running very well (with VC4, DSI, etc.) for me as of today.
ok, Chromium update to 56, but seems against with h264ify, so how to setup properly.dom wrote:Chromium doesn't support HW video decode on 4.9 yet (we are testing a version which does work but it's not been pushed out yet).cjan wrote:last update to #966, chromium youtube crashed.
ps. did not enable VC4.
In my testing Chromium worked correctly with 4.9 but video wasn't HW accelerated.
I'm not really understanding your issue.cjan wrote:ok, Chromium update to 56, but seems against with h264ify, so how to setup properly.
need disable h264ify when enable fkms driver, otherwise youtube wont play.dom wrote:I'm not really understanding your issue.cjan wrote:ok, Chromium update to 56, but seems against with h264ify, so how to setup properly.
I've updated to latest Chromium 56 and 4.9 kernel and Chromium seems fine and videos are HW accelerated.
That is unrelated to the 4.9 kernel. It is probably an experimental graphics driver issue.cjan wrote:need disable h264ify when enable fkms driver, otherwise youtube wont play.
Code: Select all
[ 87.523006] vc4-drm soc:gpu: failed to allocate buffer with size 7372800
[ 87.562753] vc4-drm soc:gpu: failed to allocate buffer with size 10170368
[ 87.562849] vc4-drm soc:gpu: failed to allocate buffer with size 10170368
[ 87.562932] [drm:vc4_bo_create [vc4]] *ERROR* Failed to allocate from CMA:
[ 87.562935] [drm] num bos allocated: 624
[ 87.562937] [drm] size bos allocated: 228032kb
[ 87.562939] [drm] num bos used: 624
[ 87.562941] [drm] size bos used: 228032kb
[ 87.562944] [drm] num bos cached: 0
[ 87.562947] [drm] size bos cached: 0kb
Code: Select all
pi@domoticz:~$ sudo i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- 68 69 6a 6b 6c 6d 6e 6f
70: -- -- -- -- -- -- -- --
Hi,Siewert308SW wrote:Maybe i overlooked something.
But what has been changed to 4.9.11-v7+ armv7l regarding i2c
I run a Pi3 with Jessie 8.0 Lite / 4.4.50-v7+ armv7l with a PIco UPS HV3.0A Stack Plus on top.
After upgrading today to 4.9.11-v7+ i2cdetect -y 1 does detect ports and shows all available tables.
But the UPS daemon fails to detect the UPS and i can't connect to the UPS.Code: Select all
pi@domoticz:~$ sudo i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- 68 69 6a 6b 6c 6d 6e 6f 70: -- -- -- -- -- -- -- --
I mean when trying to do a i2cset no data is set.
When doing a i2cget i don't get any reading anymore only 0xff reading instead of normal byte outputs.
Looked all logs but can't find anything related yet.
For now reverted back to 4.450 and will try to find the cause tomorrow when i have more to to debug.
Meanwhile i hope someone has a more info or a solution.
Try changing i2c-bcm2708 to i2c-bcm28353. Make sure to have the following items in the file and add what is missing
i2c-bcm2708
i2c-dev
rtc-ds1307
That didn't do the trick.ktb wrote:
Try changing i2c-bcm2708 to i2c-bcm2835
If that isn't the problem, then show us your cmdline.txt and config.txt
Code: Select all
dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=c0ac452a-01 rootfstype=ext4 elevator=deadline fsck.repair=yes rootdelay=20 rootwaitCode: Select all
# For more options and information see
# http://www.raspberrypi.org/documentation/configuration/config-txt.md
# Some settings may impact device functionality. See link above for details
# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1
# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
disable_overscan=1
# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16
# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720
# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1
# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1
# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2
# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4
# uncomment for composite PAL
#sdtv_mode=2
#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=1000
# Uncomment some or all of these to enable the optional hardware interfaces
dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on
# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi
# Additional overlays and parameters are documented /boot/overlays/README
# Enable audio (loads snd_bcm2835)
#dtparam=audio=on
max_usb_current=1
gpu_mem=8
#enable_uart=0