tkaiser Posted January 26, 2017 Posted January 26, 2017 Preliminary Armbian images with mainline kernel are available (nightly builds that means untested and without any end user support): https://dl.armbian.com/orangepipc2/ This is neither an announcement of Armbian support for this device nor anything a typical end user should play with. If you want to watch video go buy an Android TV box, if you want to help improving Linux support and are able and willing to accept that this is just a test image to get stability reports for DVFS then please read through: https://github.com/igorpecovnik/lib/commit/9838cc30f47c47a86da1fa0d6ce22ed1098c5706 https://github.com/igorpecovnik/lib/issues/298 https://github.com/longsleep/build-pine64-image/pull/3 It would be great if we get a lot of feedback on @ErwinH's new dvfs table that means playing around with different workloads, cramp the board in tiny enclosures (read as: eg. cardboard boxes) to let throttling start early, changing max cpufreq by adjusting /etc/defaults/cpufreq-utils and test through different clockspeeds since we need results from a lot of boards to get an idea whether the safety headroom regarding DVFS operating points is ok or needs to be extended. BTW: This is also not a call for stupid requests ('When will Armbian be ready...'). Those will be either deleted or moved to a special thread 'The user requests that prevent any dev doing any more work'. 1 Quote
zador.blood.stained Posted January 26, 2017 Posted January 26, 2017 Note for the nightly images: Docker support will be added in the next nightly - after 170127 Note for the desktop nightly images: No sound - only USB sound cards are supported; video playback in MPV may work with software decoding (read as - with proper cooling and no other processes eating the CPU), at least short 720p videos should play fine Edit: Also I deleted the previous broken nightly image 0 Quote
ErwinH Posted January 26, 2017 Posted January 26, 2017 Great work! I'm curious what's the experience with my DVFS table. Hope it runs stable on all the boards! 0 Quote
hojnikb Posted January 26, 2017 Posted January 26, 2017 Can resolution be changed from 720p ? Btw, thanks for all the hard work guys. 0 Quote
zador.blood.stained Posted January 26, 2017 Posted January 26, 2017 Can resolution be changed from 720p ? The situation is the same as with H3 mainline images - video mode is selected in u-boot using EDID (and it should default to the monitor's native resolution) and it can't be changed right now. 0 Quote
Christos Posted January 26, 2017 Author Posted January 26, 2017 (edited) Is the build repository able to build PC2 images? Tried a PC2 build (Debian jessie desktop) a few hours ago (up to commit a0a3bbe) and got this problem, repeated reboots U-Boot SPL 2017.01-rc1-g5df570f-dirty (Jan 26 2017 - 13:01:22) DRAM: 1024 MiB Trying to boot from MMC1NOTICE: BL3-1: Running on H5 (1718) in SRAM A2 (@0x44000) NOTICE: Configuring SPC Controller NOTICE: BL3-1: v1.0(debug):cd7fa48 NOTICE: BL3-1: Built : 13:00:57, Jan 26 2017 NOTICE: PLL_CPUX: 90001410 INFO: BL3-1: Initializing runtime services INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9 U-Boot 2017.01-rc1-g5df570f-dirty (Jan 26 2017 - 13:03:29 +0200) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: OrangePi PC 2 DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment HDMI connected: Setting up a 1920x1080 hdmi console (overscan 0x0) hdmi enabled In: serial Out: vga Err: vga Net: phy interface7 eth0: ethernet@1c30000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 1768 bytes read in 199 ms (7.8 KiB/s) ## Executing script at 4fc00000 Boot script loaded from mmc 91 bytes read in 169 ms (0 Bytes/s) 23888 bytes read in 268 ms (86.9 KiB/s) 3304777 bytes read in 423 ms (7.5 MiB/s) 11401224 bytes read in 675 ms (16.1 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 3304713 Bytes = 3.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 49cd9000, end 49fffd09 ... OK Loading Device Tree to 0000000049cd0000, end 0000000049cd8d4f ... OK Starting kernel ... Loading, please wait... Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/disk/by-uuid/c5a436c3-dfd4-4279-849f-a5f4bf567115 does not exist. Dropping to a shell! Rebooting automatically due to panic= boot argument [ 42.535340] reboot: Restarting system INFO: PSCI Affinity Map: INFO: AffInst: Level 0, MPID 0x0, State ON INFO: AffInst: Level 0, MPID 0x1, State ON INFO: AffInst: Level 0, MPID 0x2, State ON INFO: AffInst: Level 0, MPID 0x3, State ON U-Boot SPL 2017.01-rc1-g5df570f-dirty (Jan 26 2017 - 13:01:22) DRAM: 1024 MiB Trying to boot from MMC1NOTICE: BL3-1: Running on H5 (1718) in SRAM A2 (@0x44000) NOTICE: Configuring SPC Controller NOTICE: BL3-1: v1.0(debug):cd7fa48 NOTICE: BL3-1: Built : 13:00:57, Jan 26 2017 NOTICE: PLL_CPUX: 90001410 INFO: BL3-1: Initializing runtime services INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9 U-Boot 2017.01-rc1-g5df570f-dirty (Jan 26 2017 - 13:03:29 +0200) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: OrangePi PC 2 DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment HDMI connected: Setting up a 1920x1080 hdmi console (overscan 0x0) hdmi enabled In: serial Out: vga Err: vga Net: phy interface7 eth0: ethernet@1c30000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 1768 bytes read in 199 ms (7.8 KiB/s) ## Executing script at 4fc00000 Boot script loaded from mmc 91 bytes read in 169 ms (0 Bytes/s) 23888 bytes read in 267 ms (86.9 KiB/s) 3304777 bytes read in 423 ms (7.5 MiB/s) 11401224 bytes read in 675 ms (16.1 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 3304713 Bytes = 3.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 49cd9000, end 49fffd09 ... OK Loading Device Tree to 0000000049cd0000, end 0000000049cd8d4f ... OK Starting kernel ... Loading, please wait... Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. <Removed power at this stage as it was rebooting repeatedly> Edited January 26, 2017 by zador.blood.stained Added spoiler tags 0 Quote
zador.blood.stained Posted January 26, 2017 Posted January 26, 2017 @Christos @martinayotte has the same problem with his board, while for other people (including me) these images work fine. I have no idea if this is a HW issue or it can be solved on software level. Edit: It is possible to boot from USB, but it is tricky if you don't have u-boot in SPI flash since having the same image on USB storage and SD card will cause a UUID collision, and I'm not sure if this u-boot can be loaded in FEL. 0 Quote
ErwinH Posted January 26, 2017 Posted January 26, 2017 I used this u-boot with FEL, but you have to get the files by hand: You need the sunxi-spl.bin from the 32 bit version of the u-boot and the u-boot-dtb.bin from the 64 bit. sunxi-spl.bin is in the u-boot-sun50i/master/ folder if it isn't cleaned. This is my script to boot through FEL: #!/bin/sh UBOOT=u-boot-dtb.bin DTB=sun50i-h5-orangepi-pc2.dtb UIMAGE=Image DTBADDR=0x4FA00000 KERNELADDR=0x40080000 BOOTSCRADDR=0x43100000 BOOTSCR=boot.scr sunxi-fel -v -p spl sunxi-spl.bin \ write 0x44000 bl31.bin \ write 0x4a000000 $UBOOT \ write $DTBADDR $DTB \ write $KERNELADDR $UIMAGE \ write $BOOTSCRADDR $BOOTSCR \ reset64 0x44000 \ 0 Quote
zador.blood.stained Posted January 26, 2017 Posted January 26, 2017 Hm. I stil wonder if this is the same MMC pins pull-up issue that affects 4.10-rc kernels. In this case it can be easily fixed... 0 Quote
Christos Posted January 26, 2017 Author Posted January 26, 2017 @zador.blood.stained Thanks. That was the final blow on this board. I gave up on it quite some time ago due to the fact that its expansion pinheader is not compatible to any audio add-on (really bad design from orangepi..) but just made a compilation since I happened to have the board. Should left it in the drawer, its a waste. It looks orangepi has put all of us into a really big mess with the PC2. For what is worth it though, you guys are the best, regardless of my opinion on the specific board, your work is exceptional. 0 Quote
zador.blood.stained Posted January 26, 2017 Posted January 26, 2017 @Christos Please wait for the new nightly. I've found the original discussion about this problem and I now think it's a software problem that can be fixed. 0 Quote
Christos Posted January 26, 2017 Author Posted January 26, 2017 @zador.blood.stained Although this board is of no use to me, it might be to others so as soon as I see aditional commits on it I'll give it another try, just to give you some feedback. p.s. Added some board photos just in case you need some resistor inspection 0 Quote
hojnikb Posted January 26, 2017 Posted January 26, 2017 The situation is the same as with H3 mainline images - video mode is selected in u-boot using EDID (and it should default to the monitor's native resolution) and it can't be changed right now. Great stuff.. It pretty annoying having fixed 720p resolution on a 1080p display. Will give it a go tonight. 0 Quote
zador.blood.stained Posted January 26, 2017 Posted January 26, 2017 @Christos I uploaded a new test image, please try it out https://dl.armbian.com/orangepipc2/mmc_issue_test/ 0 Quote
hojnikb Posted January 26, 2017 Posted January 26, 2017 Question... Is there any kind of 2D accelaration for desktop or is just a pure framebuffer done by cpu ? 0 Quote
zador.blood.stained Posted January 26, 2017 Posted January 26, 2017 Question... Is there any kind of 2D accelaration for desktop or is just a pure framebuffer done by cpu ? Pure FB. No DRM display driver, no Mali, no HW video decoding. Still it can play 720p video in mpv, but you'll need a USB sound card to get any kind of audio output from it. 0 Quote
hojnikb Posted January 26, 2017 Posted January 26, 2017 Pure FB. No DRM display driver, no Mali, no HW video decoding. Still it can play 720p video in mpv, but you'll need a USB sound card to get any kind of audio output from it. Makes sense. I guess mali is a hard nut to crack with mainline kernels. As for video accelaration; Cedrus doesn't work with H5 ? Audio is bust for hdmi and analog out ? 0 Quote
Christos Posted January 26, 2017 Author Posted January 26, 2017 (edited) Ok, it boots now. U-Boot SPL 2017.01-rc1-g5df570f-dirty (Jan 26 2017 - 16:48:51) DRAM: 1024 MiB Trying to boot from MMC1NOTICE: BL3-1: Running on H5 (1718) in SRAM A2 (@0x44000) NOTICE: Configuring SPC Controller NOTICE: BL3-1: v1.0(debug):cd7fa48 NOTICE: BL3-1: Built : 16:48:47, Jan 26 2017 NOTICE: PLL_CPUX: 90001410 INFO: BL3-1: Initializing runtime services INFO: BL3-1: Preparing for EL3 exit to normal world INFO: BL3-1: Next image address: 0x4a000000, SPSR: 0x3c9 U-Boot 2017.01-rc1-g5df570f-dirty (Jan 26 2017 - 16:49:01 +0300) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: OrangePi PC 2 DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c30000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 1768 bytes read in 194 ms (8.8 KiB/s) ## Executing script at 4fc00000 Boot script loaded from mmc 91 bytes read in 165 ms (0 Bytes/s) 23888 bytes read in 267 ms (86.9 KiB/s) 4221761 bytes read in 456 ms (8.8 MiB/s) 11401224 bytes read in 674 ms (16.1 MiB/s) ## Loading init Ramdisk from Legacy Image at 4fe00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 4221697 Bytes = 4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Loading Ramdisk to 49bf9000, end 49fffb01 ... OK Loading Device Tree to 0000000049bf0000, end 0000000049bf8d4f ... OK Starting kernel ... Loading, please wait... starting version 229 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.27.1 [/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 /dev/mmcblk0p1: clean, 51929/87120 files, 245921/348160 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. Welcome to Ubuntu 16.04.1 LTS! [ OK ] Listening on Journal Audit Socket. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Reached target Remote File Systems (Pre). [ OK ] Reached target Remote File Systems. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Listening on Syslog Socket. [ OK ] Reached target Encrypted Volumes. [ OK ] Listening on udev Kernel Socket. [ OK ] Listening on Journal Socket. [ OK ] Started Forward Password Requests to Wall Directory Watch. [ OK ] Listening on fsck to fsckd communication Socket. [ OK ] Set up automount Arbitrary Executab...ats File System Automount Point. [ OK ] Created slice User and Session Slice. [ OK ] Created slice System Slice. Starting Set console keymap... Starting Nameserver information manager... Mounting POSIX Message Queue File System... Starting Create list of required st... nodes for the current kernel... Starting Load Kernel Modules... Starting Restore / save the current clock... Starting Remount Root and Kernel File Systems... [ OK ] Created slice system-serial\x2dgetty.slice. Mounting Debug File System... Mounting Huge Pages File System... [ OK ] Started Dispatch Password Requests to Console Directory Watch. [ OK ] Reached target Swap. [ OK ] Listening on udev Control Socket. [ OK ] Reached target Slices. [ OK ] Mounted Huge Pages File System. [ OK ] Mounted Debug File System. [ OK ] Mounted POSIX Message Queue File System. [ OK ] Started Set console keymap. [ OK ] Started Create list of required sta...ce nodes for the current kernel. [ OK ] Started Load Kernel Modules. [ OK ] Started Restore / save the current clock. [ OK ] Started Remount Root and Kernel File Systems. [ OK ] Started Nameserver information manager. Starting udev Coldplug all Devices... Starting Load/Save Random Seed... Mounting FUSE Control File System... Mounting Configuration File System... Starting Apply Kernel Variables... Starting Create Static Device Nodes in /dev... [ OK ] Mounted Configuration File System. [ OK ] Mounted FUSE Control File System. [ OK ] Started Load/Save Random Seed. [ OK ] Started Apply Kernel Variables. [ OK ] Started Create Static Device Nodes in /dev. [ OK ] Started udev Coldplug all Devices. [ OK ] Reached target Local File Systems (Pre). Mounting /tmp... Starting udev Kernel Device Manager... [ OK ] Mounted /tmp. [ OK ] Started Entropy daemon using the HAVEGE algorithm. [ OK ] Reached target Local File Systems. Starting Set console font and keymap... Starting Raise network interfaces... Starting Armbian enhanced Log2Ram... [ OK ] Started udev Kernel Device Manager. [ OK ] Found device /dev/ttyS0. [ OK ] Started Armbian enhanced Log2Ram. Starting Journal Service... [ OK ] Started ifup for eth0. [ OK ] Started Journal Service. [ OK ] Found device /sys/subsystem/net/devices/eth0. Starting Flush Journal to Persistent Storage... [ OK ] Started Flush Journal to Persistent Storage. Starting Create Volatile Files and Directories... [ OK ] Started Create Volatile Files and Directories. Starting Update UTMP about System Boot/Shutdown... [ OK ] Reached target System Time Synchronized. [ OK ] Started Update UTMP about System Boot/Shutdown. [ OK ] Started Raise network interfaces. [ OK ] Reached target System Initialization. [ OK ] Started Daily apt activities. [ OK ] Reached target Paths. [ OK ] Listening on D-Bus System Message Bus Socket. [ OK ] Reached target Sockets. Starting Armbian filesystem resize service... [ OK ] Started Daily Cleanup of Temporary Directories. [ OK ] Reached target Timers. [ OK ] Started Armbian filesystem resize service. [ OK ] Reached target Basic System. Starting LSB: Load kernel modules needed to enable cpufreq scaling... Starting LSB: Starts LIRC daemon.... Starting System Logging Service... [ OK ] Started D-Bus System Message Bus. Starting Network Manager... [ OK ] Started Regular background program processing daemon. Starting Permit User Sessions... [ OK ] Started Armbian first run tasks. Starting LSB: Start/stop sysstat's sadc... Starting Login Service... Starting LSB: Armbian gathering hardware information... [ OK ] Started System Logging Service. [FAILED] Failed to start Set console font and keymap. See 'systemctl status console-setup.service' for details. [ OK ] Started Permit User Sessions. [ OK ] Started LSB: Start/stop sysstat's sadc. [ OK ] Started Login Service. [ OK ] Started LSB: Load kernel modules needed to enable cpufreq scaling. [ OK ] Started LSB: Starts LIRC daemon.. Starting LSB: set CPUFreq kernel parameters... Starting Set console scheme... [ OK ] Created slice system-getty.slice. [ OK ] Started Set console scheme. [ OK ] Started LSB: set CPUFreq kernel parameters. Starting LSB: Set sysfs variables from /etc/sysfs.conf... [ OK ] Started LSB: Set sysfs variables from /etc/sysfs.conf. [ OK ] Started LSB: Armbian gathering hardware information. [ OK ] Started Network Manager. [ OK ] Reached target Network. Starting OpenBSD Secure Shell server... Starting Network Manager Wait Online... Starting Network Manager Script Dispatcher Service... [ OK ] Started Network Manager Script Dispatcher Service. Starting Hostname Service... [ OK ] Started Hostname Service. [ OK ] Started OpenBSD Secure Shell server. Starting Authenticate and Authorize Users to Run Privileged Tasks... [ OK ] Started Network Manager Wait Online. [ OK ] Reached target Network is Online. Starting LSB: Advanced IEEE 802.11 management daemon... Starting /etc/rc.local Compatibility... Starting LSB: disk temperature monitoring daemon... Starting LSB: Start NTP daemon... [ OK ] Started LSB: Advanced IEEE 802.11 management daemon. [ OK ] Started /etc/rc.local Compatibility. [ OK ] Started Authenticate and Authorize Users to Run Privileged Tasks. [ OK ] Started LSB: disk temperature monitoring daemon. [ OK ] Started Serial Getty on ttyS0. [ OK ] Started Getty on tty1. [ OK ] Reached target Login Prompts. [ OK ] Started LSB: Start NTP daemon. [ OK ] Reached target Multi-User System. [ OK ] Reached target Graphical Interface. Starting Update UTMP about System Runlevel Changes... [ OK ] Started Update UTMP about System Runlevel Changes. Ubuntu 16.04.1 LTS orangepipc2 ttyS0 Edited January 26, 2017 by zador.blood.stained Add spoiler tags 1 Quote
zador.blood.stained Posted January 26, 2017 Posted January 26, 2017 Makes sense. I guess mali is a hard nut to crack with mainline kernels. Framebuffer Mali can be added, it's not that hard (but it's mostly useless). For a X11 Mali you would need a DRM display driver first (if I understand things correctly), and current H3 one is too limited and experimental ATM. As for video accelaration; Cedrus doesn't work with H5 ? H3 cedrus may work if you are talking about mainline one (well, a fork of this one that supports H3), but again - it's early WIP that depends on another WIP feature (Requests API), so I wouldn't expect it to be fully ready and operational this year. Audio is bust for hdmi and analog out ? Analog audio will be present in 4.10 if anyone finds time and motivation to rebase this branch on top of 4.10. I also saw SPDIF patches for H3, so they may appear in 4.11-4.12 too. For the HDMI audio - I don't think any sunxi board has it supported in Linux kernel, and I don't think anybody is working on it. 0 Quote
ErwinH Posted January 26, 2017 Posted January 26, 2017 if anyone finds time and motivation to rebase this branch on top of 4.10 I can rebase these commits on top of 4.10 if you like. 0 Quote
zador.blood.stained Posted January 26, 2017 Posted January 26, 2017 I can rebase these commits on top of 4.10 if you like. Let's wait at least for the official 4.10.0 release, no need to rush only for the analog audio yet. Also please note that we changed and fixed some of yours and apritzel's commits and patches in order to support Pine64 and booting from SPI. 0 Quote
tkaiser Posted January 26, 2017 Posted January 26, 2017 no need to rush only for the analog audio yet. Yep, let's focus on basic things first: Stress testing to get stability reports from a much larger sample size than currently. I still fear that it ends with this H5 mainline image like with dev vanilla images for H3 boards. Zero useful feedback from any user but them starting to use 4.x images productive and flooding the forum with complaints about stuff that is known to not work (ATM). 0 Quote
hojnikb Posted January 26, 2017 Posted January 26, 2017 Any chance for a script that would simplify stress and temperature testing for noobs ? Maybe even include one in the image and let it run on the first boot, then submit results to armbian server. 0 Quote
zador.blood.stained Posted January 26, 2017 Posted January 26, 2017 I still fear that it ends with this H5 mainline image like with dev vanilla images for H3 boards. Zero useful feedback from any user but them starting to use 4.x images productive and flooding the forum with complaints about stuff that is known to not work (ATM). Exactly why I didn't want to announce it yet. Link to the images and to this thread already appeared in some other PC2 discussions (hi 4pda.ru forum ), but other people may run into the same MMC pull-up issue with current nightlies. Edit: as expected. 0 Quote
hojnikb Posted January 26, 2017 Posted January 26, 2017 Can you explain mmc pull-ip issues for noobs ? 0 Quote
zador.blood.stained Posted January 26, 2017 Posted January 26, 2017 For noobs - some Device Tree definitions were wrong, it will be fixed in the tomorrows nightly (or there is a test CLI image linked above that has this issue fixed). Not for noobs - most SD cards require external (relative to the card) pull-ups on its data lines. Previously kernel relied on pull-ups enabled by u-boot, but after the pinctrl rework same definition (SUN4I_PINCTRL_NO_PULL) caused kernel to actively disable pull-ups instead of not touching previous value. 0 Quote
tkaiser Posted January 26, 2017 Posted January 26, 2017 Any chance for a script that would simplify stress and temperature testing for noobs ? Maybe even include one in the image and let it run on the first boot, then submit results to armbian server. Nope, fire and forget doesn't work (based on experiences already made wasting hours for automated testing images and receiving not that much feedback), it requires some time and at least the will to get some knowledge. There's a reason why I referenced 3 github issues/threads above. Exactly why I didn't want to announce it yet. Hmm... please feel free to pro-actively prevent me then from leaking such stuff the next time (already when I asked the first time regarding your commit from the day before yesterday) 0 Quote
jernej Posted January 26, 2017 Posted January 26, 2017 Great stuff.. It pretty annoying having fixed 720p resolution on a 1080p display. If I understand you correctly, you didn't try it yet? Because the driver should select native screen resolution, in this case 1080p. If it is not, then it is bug. Question... Is there any kind of 2D accelaration for desktop or is just a pure framebuffer done by cpu ? H5 doesn't have any HW 2D acceleration, only 3D through mali. For the HDMI audio - I don't think any sunxi board has it supported in Linux kernel, and I don't think anybody is working on it. For this you need DRM driver. Maybe something can be done with H3 experimental one, but let's focus on basics first. 1 Quote
martinayotte Posted January 26, 2017 Posted January 26, 2017 @martinayotte has the same problem with his board, while for other people (including me) these images work fine. I have no idea if this is a HW issue or it can be solved on software level. I had this issue with my own build done before your official commit, so, maybe I missed something, since when rebuilded with your changes, the problem disappeared. Hm. I stil wonder if this is the same MMC pins pull-up issue that affects 4.10-rc kernels. In this case it can be easily fixed... I though that too, and was thinking that you've included that fix. Since you didn't, the problem was maybe elsewhere. 0 Quote
tomter Posted January 26, 2017 Posted January 26, 2017 Good work team, congratulations. I have already tried it, installed on hdd with nand-sata-install, but I am thinking if it's possible to remove sd card, and have boot files on SPI flash. Is that possible? 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.