DietPi for Orange Pi PC

Fourdee

Wolfman replied at 2016-2-3 22:58
Hi Fourdee.
Can You tell me will DietPi for Opi PC will work with i2s DAC?
It would be great.

As DietPi is based on the Loboris Jessie image, it looks like i2c is supported:http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=342

Features:

boot0_sdcard.fex, u-boot.fex and kernel (uImage) created from sources
kernel built with many features enabled (btrfs, USB serial adapters, bluetooth, hdmi sound, nfsd ...)
CPU runs at 1.53GHz, termal management adjusted so that all 4 cores are active up to 100 °C
GPIO, i2c (TWI), SPI enabled

No mention on i2s. If you have the i2s device already, give it a whirl. If not, let me know and I'll test my audiophonics soundcard when I can (its in use at the moment).

Wolfman

Fourdee replied at 2016-2-5 22:37
As DietPi is based on the Loboris Jessie image, it looks like i2c is supported:http://www.orangepi ...

Hello.
I don't have any i2s dac yet, but i used oscilloscope and there is no signal on gpio so if You can and have time please check with your soundcard.
Thanks for repaly.

Kit

Fourdee replied at 2016-2-5 22:25
If you ran the firmware update from dietpi-config > advanced, Loboris kernel update script is then ...

Yup, obviously took Pi PC when asked.

Anyway, i just reinstalled and didn't updated the fimware this time.

swordfish6975

hey @Fourdee thanks for your hard work on diet pi, I am running it as a FTP server.

Kit

Hello,

Is there a release for OPi One ?

Fourdee

Kit replied at 2016-2-17 20:13
Hello,

Is there a release for OPi One ?

Unknown at the moment as I do not currently own one. But its the same H3 chip as the OPi PC, so in theroy it "should" work on the current DietPi OPi PC image.

Kit

Will test when I will order one.

Thanks for your excellent work.

Paranoidjack

The latest version of DNScrypt-proxy (1.6.1) fails to bind to any interface using this image - the previous version (1.6.0) works without any problems.

I've compiled the same version on a Raspberry Pi without any problems so I presume it's an issue with the orange Pi PC kernel?

These are all the commits from the 1.6.0 to 1.6.1: https://github.com/jedisct1/dnscrypt-proxy/compare/1.6.0...master

New features which were added in 1.6.1:

Malformed packets could cause the OpenDNS deviceid, OpenDNS set-client-ip, blocking and AAAA blocking plugins to use uninitialized pointers, leading to a denial of service or possibly code execution.

The vulnerable code is present since dnscrypt-proxy 1.1.0.

OpenDNS users and people using dnscrypt-proxy in order to block domain names and IP addresses should upgrade as soon as possible.

I've opened the issue over at DNScrypt-proxy's github: https://github.com/jedisct1/dnscrypt-proxy/issues/368

Fourdee

Paranoidjack replied at 2016-2-18 14:12
The latest version of DNScrypt-proxy (1.6.1) fails to bind to any interface using this image - the p ...

All DietPi images (eg: rpi c1 xu4) and their system configurations are pretty much identical. The only real difference is anything unique to the device, eg: kernel, modules and fstab mounts.

The only thing I can suggest is to disable IPv6. Its a bit of a "hit or miss", but worth a try:

1. echo -e "blacklist ipv6" > /etc/modprobe.d/blacklist-ipv6.conf
   
2. sed -i "/net.ipv6.conf.all.disable_ipv6 /c\net.ipv6.conf.all.disable_ipv6 = 1" /etc/sysctl.conf
   
3. sed -i "/net.ipv6.conf.default.disable_ipv6 /c\net.ipv6.conf.default.disable_ipv6 = 1" /etc/sysctl.conf
   
4. sed -i "/net.ipv6.conf.lo.disable_ipv6 /c\net.ipv6.conf.lo.disable_ipv6 = 1" /etc/sysctl.conf
   
5. reboot
   

Copy code

Paranoidjack

It didn't work so it's likely an issue with the kernel then.