sinovoip
November 15, 2017, 5:04am
1
2017-11-13-ubuntu-16.04-mate-desktop-beta2-bpi-m2u-sd-emmc.img.zip
based on ubuntu 16.04.3 LTS Mate Desktop
support BPI-M2 Ultra & BPI-M2 Berry kernel 3.10.108 & uInitrd
username & password: pi/bananapi , root/bananapi
support LCD 7" with GT touch
support LCD 5"
support HDMI 1080P & 480P & 720P (default)
support GMAC
support WIFI
support BT (with bluetoothctl can setup)
support SATA
support UART (default set 2 pin mode for /dev/ttyS2)
support I2C (test with bpi_test_lcd1602)
support SPI (test with bpi_test_hello & bpi_test_52pi)
support eMMC (support boot from eMMC)
support Battery (BPI-M2 Ultra only)
support IR (getevent can test, BPI-M2 Ultra only)
support touch screen (can control desktop or getevent to test)
support power key (getevent can test)
support OTG (BPI-M2 Ultra only)
support CAMERA ov5640 (guvcview / cap / ffmpeg-3.1.4 support video H.264 hw encode)
support uEnv.txt to fatload uImage
support bpi-bootsel to set LCD7" / LCD5" / HDMI (720P & 1080P & 480P)
support bpi-copy to write SD/eMMC with img.zip file
support video play 1080p with vdpau (mpv , vlc, smplayer)
support xrdp
support chromium 62.0.3202.75
support wiringpi 2.44 (https://github.com/BPI-SINOVOIP/BPI-WiringPi2 , thanks to http://wiringpi.com/ & https://github.com/WiringPi/WiringPi
support rpi.gpio 0.6.3 for python (https://github.com/BPI-SINOVOIP/RPi.GPIO , thanks to https://sourceforge.net/projects/raspberry-gpio-python/ )
Thanks for linux-sunxi community (http://linux-sunxi.org/ )
Special thanks for Daniel Andersen with BPI-M2U-bsp ( https://github.com/dan-and )
Special thanks for Alex support with camera functions ( https://github.com/avafinger )
ref. https://github.com/BPI-SINOVOIP/BPI-M2U-bsp
ref. https://bananapi.gitbooks.io/bpi-m2-ultra-open-source-single-board-computer/content/
Google Drive:
https://drive.google.com/file/d/19PI9yuL9iFa4bU6dh7ym3tcCHhjAh-cM/view?usp=sharing
baidu cloud:
http://pan.baidu.com/s/1nvccOlz
MD5: 4655b896a3c4e1958a15bb8ca45ac4fe
FILESIZE: 1780632239 (~1698MB)
UNPACK: 7296MB (eMMC size)
Customer
November 15, 2017, 1:15pm
2
What has changed since your previous release? Why should someone use this release over another?
Was something fixed? How about a ChangeLog!!!?!?!
1 Like
Has anyone tested this build?
I’ve been using the Ubuntu mate image . It’s been OK, but SATA performance is seriously lacking. My M2U decided to crash and go into a boot loop. After turning off for 30 mins it was fine. Have this problem whenever I change to a different ROM, need to wait 30 mins before m2u will stop boot looping. Maybe the voltage issue mentioned here.
Will be looking at moving away from BPI once there is a good alternative with faster SATA performance, stable ROM, and better performance.
bureau
January 30, 2018, 9:59pm
4
After manual PowerOff my board doesn’t want to start normally. On the terminal I see this log:
[ 7.033536] android_usb gadget: Number of LUNs=3
[ 7.044257] lun0: LUN: removable file: (no medium)
[ 7.061390] lun1: LUN: removable file: (no medium)
[ 7.078359] lun2: LUN: removable file: (no medium)
[ 7.097324] android_usb gadget: android_usb ready
[ 7.114358] sunxi-rtc rtc: setting system clock to 2010-01-01 00:00:10 UTC (1262304010)
[ 7.144089] ALSA device list:
[ 7.159256] #0: audiocodec
[ 7.174289] #1: sndhdmi
[ 7.190749] Freeing unused kernel memory: 296K
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 ... done.
Begin: Will now check root file system ... fsck from util-linux 2.27.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p2] fsck.ext4 -a -C0 /dev/mmcblk0p2
BPI-ROOT contains a file system with errors, check forced.
<1>BPI-ROOT: |=
| 1.3% <\r><1>BPI-ROOT: |= / 2.5% <\r><1>BPI-ROOT:
|== - 3.8% <\r><2><1>BPI-ROOT:
|=== \ 5.1% <\r><2><1>BPI-ROOT:
|==== | 6.4% <\r><1>BPI-ROOT:
|==== / 7.6% <\r><1>BPI-ROOT:
|===== - 8.9% <\r><2><1>BPI-ROOT:
|====== \ 10.2% <\r><2><1>BPI-ROOT:
|====== | 11.5% <\r><2><1>BPI-ROOT:
|============ / 21.6% <\r><1>BPI-ROOT:
|============= - 22.9% <\r><2><1>BPI-ROOT:
|============== \ 24.2% <\r><2><1>BPI-ROOT:
|============== | 25.5% <\r><1>BPI-ROOT:
|=============== / 26.7% <\r><2><1>BPI-ROOT:
|================ - 28.0% <\r><2><1>BPI-ROOT:
|================ \ 29.3% <\r><1>BPI-ROOT:
|================== | 31.8% <\r><2><1>BPI-ROOT:
|=================== / 33.1% <\r><2><1>BPI-ROOT:
|======================== - 42.0% <\r><1>BPI-ROOT:
|========================= \ 44.5% <\r><2><1>BPI-ROOT:
|========================== | 45.8% <\r><2><1>BPI-ROOT:
|========================== / 47.1% <\r><2><1>BPI-ROOT:
|=================================== - 62.4% <\r><1>BPI-ROOT:
|==================================== \ 63.6% <\r><2><1>BPI-ROOT:
|===================================== | 66.2% <\r><2><1>BPI-ROOT:
|======================================= / 70.5% <\r><2><1>BPI-ROOT:
|======================================== - 71.7% <\r><2><1>BPI-ROOT:
|========================================= \ 72.5% <\r><2><1>BPI-ROOT:
========================================= | 73.8% <\r><2><1>BPI-ROOT:
|========================================== / 74.7% <\r><2><1>BPI-ROOT:
|========================================== - 75.9% <\r><2><1>BPI-ROOT:
|=========================================== \ 77.1% <\r><1>BPI-ROOT:
|============================================ | 78.1% <\r><2><1>BPI-ROOT:
|============================================ / 79.1% <\r><1>BPI-ROOT:
|============================================= - 79.9% <\r><1>BPI-ROOT:
|============================================= \ 81.2% <\r><1>BPI-ROOT:
|============================================== | 82.3% <\r><2><1>BPI-ROOT:
|=============================================== / 83.6% <\r><2>BPI-ROOT: <1>
<\r><2>
Directory inode 299070, block #0, offset 0: directory corrupted
BPI-ROOT: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
<9>(i.e., without -a or -p options)
fsck exited with status code 4
done.
Failure: File system check of the root filesystem failed
The root filesystem on /dev/mmcblk0p2 requires a manual fsck
Rebooting automatically due to panic= boot argument
[ 24.093636] CPU1: shutdown
[ 24.111707] CPU2: shutdown
[ 24.129621] CPU3: shutdown
[ 24.146284] drivers/cpufreq/cpufreq.c:reboot_notifier_call: stop none boot cpus done
[ 24.167574] drivers/devfreq/sunxi_dramfreq.c:sunxi_dramfreq_reboot: stop dramfreq done
[ 24.197196] [alarmtimer] have no shutdown alarm! alarmtimer_shutdown 330
[ 24.220177] sunxi-mmc sdc2: try to disable cache
[ 24.238038] sunxi-mmc sdc2: sdc set ios: clk 50000000Hz bm PP pm ON vdd 7 width 8 timing LEGACY(SDR12) dt B
[ 24.262045] sunxi-mmc sdc2: sdc set ios: clk 50000000Hz bm PP pm ON vdd 7 width 1 timing LEGACY(SDR12) dt B
[ 24.285533] sunxi-mmc sdc2: sdc set ios: clk 400000Hz bm PP pm ON vdd 7 width 1 timing LEGACY(SDR12) dt B
[ 24.309007] sunxi-mmc sdc2: sdc set ios: clk 400000Hz bm PP pm ON vdd 7 width 1 timing LEGACY(SDR12) dt B
[ 24.334715] sunxi-mmc sdc2: sdc set ios: clk 400000Hz bm PP pm ON vdd 7 width 1 timing LEGACY(SDR12) dt B
[ 24.370400] sunxi-mmc sdc2: sunxi_mmc_do_shutdown_com: mmc shutdown exit..ok
[ 24.390722] [ohci2-controller]: ohci shutdown start
[ 24.408566] [ohci2-controller]: ohci shutdown end
[ 24.426102] [ehci2-controller]: ehci shutdown start
[ 24.443731] [ehci2-controller]: ehci shutdown end
[ 24.460978] [ohci1-controller]: ohci shutdown start
[ 24.478278] [ohci1-controller]: ohci shutdown end
[ 24.495160] [ehci1-controller]: ehci shutdown start
[ 24.512061] [ehci1-controller]: ehci shutdown end
[ 24.528427] sunxi_ohci_hcd_shutdown, ohci0-controller is disable, need not shutdown
[ 24.548156] sunxi_ehci_hcd_shutdown, ehci0-controller is disable, need not shutdown
[ 24.567726] Restarting system.
[ 24.581882]
[ 24.591861] Restarting Linux version 3.10.108-BPI-M2U-Kernel (root@bpi-iot-ros-ai) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) #1 SMP Sat Nov 11 19:20:49 CST 2017
[ 24.591861]
[ 0.33]HELLO! BOOT0 is starting!
there is the answer for your question in the log you have posted :
bureau
February 12, 2018, 4:16pm
6
Yes, I did. My post was just for information (for developers) for the future
