asterisk-user

Hi All, I've just got the new Orange Pi R1 and as expected it's working just well with the Orange Pi Zero armbian image. The only thing I'm struggeling with is the Wifi driver. The driver compiles succesfully but it seems that the kernel needs patching as well: ... CC [M] /usr/src/rtk8189es-2015-12-15-90ed86d42d/rtl8189ES//hal/OUTSRC/rtl8188e/phydm_RTL8188E.o CC [M] /usr/src/rtk8189es-2015-12-15-90ed86d42d/rtl8189ES//platform/platform_ops.o CC [M] /usr/src/rtk8189es-2015-12-15-90ed86d42d/rtl8189ES//platform/platform_ARM_SUNnI_sdio.o CC [M] /usr/src/rtk8189es-2015-12-15-90ed86d42d/rtl8189ES//core/rtw_mp.o CC [M] /usr/src/rtk8189es-2015-12-15-90ed86d42d/rtl8189ES//core/rtw_mp_ioctl.o LD [M] /usr/src/rtk8189es-2015-12-15-90ed86d42d/rtl8189ES//8189es.o Building modules, stage 2. MODPOST 1 modules WARNING: "wifi_teardown_dt" [/usr/src/rtk8189es-2015-12-15-90ed86d42d/rtl8189ES//8189es.ko] undefined! WARNING: "wifi_setup_dt" [/usr/src/rtk8189es-2015-12-15-90ed86d42d/rtl8189ES//8189es.ko] undefined! WARNING: "wifi_pm_get_mod_type" [/usr/src/rtk8189es-2015-12-15-90ed86d42d/rtl8189ES//8189es.ko] undefined! CC /usr/src/rtk8189es-2015-12-15-90ed86d42d/rtl8189ES//8189es.mod.o LD [M] /usr/src/rtk8189es-2015-12-15-90ed86d42d/rtl8189ES//8189es.ko This has been discussed in an older topic: I just wanted to know if there are any plans to intigrate the driver into the armbian zero image? Thanks! Viktor

Hi zador.blook.stained, thanks for the quick reply. I had a read through the other post and I'm not completely sure that I've understood this issue. Just to summarise the issue: Since armbian moved form FAT as the boot partition the u-boot process is broken even for the official armbian image. From now on the u-boot files have to be manually copied over to eMMC via UART. Is that correct? The u-boot partition can't be updated on an external PC because the files have to be some sort of signed in order to get booted properly? Thanks, Viktor

Hi All! I was wondering if there is a proper way to deploy a freshly built armbian for Odroid XU4 on an eMMC? Unfortunately, the SD-Card version doesn't seem to work with the eMMC. After searching for this topic I couldn't find anythin in particular related to Odroid. Thanks, Viktor

Hi All, it took me a while, but I found the solution: crontab (root): @reboot /bin/echo 0 > /proc/sys/kernel/printk_ratelimit solved the problem for me. It seems that the kernel is automatically filtering the apparmor messages (spam). Thanks, Viktor

Hi All, I might need your help with one issue I've encountered. I'm running debian with the 4.9.20 kernel on an Odroid XU4 board. I've compiled the kernel with the options for AppArmor enabled. The installed AppArmor version is the 2.10.95 (auditd is also installed in version 1:2.4-1+b1). ## Kernel Options ## CONFIG_SECURITY=y CONFIG_SECURITYFS=y CONFIG_SECURITY_APPARMOR=y CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1 CONFIG_DEFAULT_SECURITY_APPARMOR=y CONFIG_DEFAULT_SECURITY="apparmor" CONFIG_SECCOMP=y CONFIG_SECCOMP_FILTER=y CONFIG_AUDIT=y ## ## AppArmor itself is working without any issues. If I set a profile to enforce, then any not allowed action is blocked and logged accordingly. The problem I'm facing now is that AppArmor is not logging anything in complain mode, which makes it very difficult to create a new profile for applications. The strange thing is, that all actions get logged in enforce mode perfectly... (e.g. Apr 17 14:21:56 localhost kernel: [ 2913.082774] audit: type=1400 audit(1492435316.208:54): apparmor="DENIED" operation="open" profile="/usr/sbin/nginx" name="/etc/nginx/nginx.conf" pid=4260 comm="nginx" requested_mask="r" denied_mask="r" fsuid=0 ouid=0) Does anyone have a cloue what's wrong? I'd be greateful for any hints. Kind regards, Viktor

Hi glaucioklipel, I kind of stuck at the same point now. Could you possibly discribe your workaround more detailed? At the moment I'm running armbian from emmc and getting the exact same behaviour whilste upgrading the system. PS: Worked well running from SD-Card Thank you in advance!