Search the Community

Showing results for tags 'Important'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements & first aid
    • Announcements
    • Board doesn't start
  • Community forums
    • Common issues
    • Peer to peer technical support
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner H5 & A64
    • Allwinner H6
    • Armada A388, A3700
    • Amlogic S905(x)
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Other supported boards
  • Development
    • Rockchip 3399
    • Development

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 66 results

  1. Release Candidate Code Freeze Date: 2020-07-18 Release Date: 2020-08-XX Release Candidate Branch Link: TBD Release Changelog: TBD Release Coordinator: @lanefu Testing Tracking Sheet: TBD (google sheets) The goal of this thread is to discuss testing, bugfixes, and the overall quality of the release. Once the release is complete, this thread should be locked and unpinned. --- Our next release date is coming and perhaps its time to discuss what to push into 20.08, what not, resolve open questions and distract from most used keyword for past few weeks. @Myy @TonyMac32 @balbes150 @piter75 @sfx2000 @ebin-dev @count-doku @chwe @ning @lanefu @gprovost @aprayoga @5kft @JMCC @Werner @karabek @martinayotte @tkaiser @selfbg @Siraj @jock @going ... I am preparing a meeting on IRC in Saturday, July 4th, at 2 pm GMT - this is reasonable good timing for US / EU folks. Agenda: check meeting attendees (if nick is not self explanatory, add your forum/Github handle. Just say hi or something) present tasks, bugs or project you are working on (open discussion if there will not be much people, otherwise meeting officer call people out). Jira should be open in not already. cycle Jira backlog: discuss task / bug (one at a time) assign to person / release / tag re-prioritise cycle open issues and PR on build engine board status update on download pages and build engine (wip, supported, eol) choosing upcoming release officer (so far it was me and Lane) misc / open discussion Tips: when you got a voice, be concise (1-2 min) and make it clear when you stop. ("No more, I'm done") channel is recorded so a summary and adjustments to Jira can made afterwards, ideally along with the meeting Meeting location is IRC channel #armbian on Freenode. (previous session as an example) Ideally it would be that prior to this meeting we all update tasks/project statuses in Jira - who still does not have access shall PM to @lanefu or @Igor - reviewing, prioritising and releasing goes faster this way.
  2. We all know there are several shortcomings which causes mess in the config files and prevent simple implementing of more complex scripting. In order to make build system future proof and to cleanup the exception mess, which is virtually everywhere, I decided to start working on a part of the build system. Now the concept works and it is not that far to be mad if idea is bad packages/extras was moved into this, then board support package and (for now) Cubietruck and Tinkerboard hacks from config/sources/ All others have to be implement into packages and their scripts. It's one time job and it will be much easier in the future, with new boards or functions. New board support packages are now broken into unlimited number of packages. Currently there are three main groups and already present logical packages. Most of present are tested and are fully operational. Mostly its copy/past with bug fixed here and there. Perhaps some bugs were made in this process, but in essence system works - for those two boards. Upgrade path is not determined yet - I only focused on packaging and installing. All those packages can be installed from freshly build ones or from the repository. Each package can have their own number and package is rebuild only if number upstream doesn't exists. This RFC includes preliminary merge of @balbes150 TV boxes fork so it's ATM a bit messy. Cubietruck and Tinkerboard images were tested (Bluetooth briefly, audio need to check again), the rest is not prepared and it requires some manual work. I hope someone else, not just the usual suspects, will help doing this. I will slowly move forward and keep it mergeable/synced with upstream. This approach is more or less only a working proposal for changes. IMHO it's better than what we have now but not perfect. (WIP) Readme with some more details You can try this by adding LIB_TAG="tvboxes" Edit: Skeleton is done, images can be build from this branch ... Most but not all of our current families and board specialities has been moved under this packaging system. I tested Cubietruck, RockPro, Tinkerboard. At least they works fine - checked for Bluetooth (TB/CB3) and video acceleration on Cubietruck. TBD: adjust changes in armbian-config regarding desktop (nodm is gone, lightdm only with possible autologin) and kernel switching. @JMCC Welcome to try adding perhaps Tinkerboard MM script as a new multimedia/something package. What shall be its name? If some 3rd party packages needs to be placed to the repository, put them here: @gprovost mvebu family is not there yet, but if you got time it should be clear what to do? If not, I wrote lousy docs or scripting is more complicated as before @selfbg Added Olimex SOM204. Check when possible. @zador.blood.stained Are packages relations alright? I hope they are future proof. Upgrade is planned from armbian-config and is actually optional. Older packages, except boot and kernel are no more. @tkaiser cpufreq is not overwriting anymore, serial consoles are board property SERIALCON="ttyS0,ttyGS0", board config is reloaded right before packages building. Shell we move to per board script? Changes should not affect OMV. @Staars Z28Pro merged but untested @lanefu @5kft @TonyMac32 .... check. @balbes150 have a lot of work to move his scripting into the build engine. Helping him, testing, fixing, ... @all Check and join if you can. can be switched to this new world order ASAP. Expected merge due: 2/2019 ? Happy 19! Edit by lanefu 7/2019: A project #1 has been created on github. There are several tasks, which will be tracked as issues on the board.
  3. Hi, UPDATE 26 of May 2018: minor text for better reading, Document section added tools, repository idea SITUATION: In our "day to day" exchange on Armbian we are probably to close to look at it the way it looks for a firsttime visitor. Many members of the community have seen that as well and wrote about it in the Forum - but they didn't come up with a solution. Now, neither do I have a solution nor do I have nice document, but I think we need to set some standard pillars of FOSS projects in order to overcome some of our well known problems. For the ones who joined armbian a while ago (me for example May 2015) have read about missing developers, rare drive-by contributions. Which is sad because as a FOSS (Free and Open Source Software) project there is no sustainability without contributors. We (armbian members) cannot explain that ourselves, tens of thousand of people have SBCs and use armbian, we are friendly - why so little participation? IDEA: I will not call a the 'holy grail', but certainly a clear idea and a process attracts more people than "We do this when we feel like" == no information about how we treat and like contributions. In the documentation we have a is this enough, is this the right place? The development happens on GitHub so I think this is also the place where information belongs and we can link from the documentation to this place, to write it down just once. DOCUMENT: Contributing Guidelines Oftentimes open source projects place a CONTRIBUTING file in the root directory. It explains how a participant should do things like format code, test fixes, and submit patches. an example: Contributing When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change. Our tools to control and setup armbian armhwinfo armbiansetuphw armbianzram armbian-config armbianmonitor scripts configuration Repository structure - The "wip" (work in progress) branch or a branch per SoC/big change - dev-rockchip | dev-sunxi (Allwinner) | dev-meson64 (AMLogic) - Incremental kernel patches can be applied to "master" (also known as Stable) after testing (eg. a little .deb for testers) since they should only ever break one family, and should be fairly consistent across all members. Pull Request Process Update the or Documentation with details of changes to the interface, this includes new environment variables, exposed ports, useful file locations and other parameters. Increase the version numbers in any examples files and the to the new version that this Pull Request would represent. The versioning scheme we use is SemVer. You may merge the Pull Request in once you have the sign-off of two other developers, or if you do not have permission to do that, you may request the second reviewer to merge it for you. License This project is under GNU GENERAL PUBLIC LICENSE Version 2, June 1991 - Copyright (C) 1989, 1991 Free Software Foundation, Inc., <> What does belong into the - please just leave a comment of what is important to you - so I can collect and put it together for us That's all I have for now, I will update this OP as anything important changes/comes up.
  4. I have managed to build FFmpeg with Cedrus on Armbian and it seems working. It would be nice to see some benchs and how would be the best use for this AW Encoder. I have not much experience with FFmpeg. You can test it: To grab video stream from the CMOS camera: sudo ./ffmpeg -f v4l2 -channel 0 -video_size 640x480 -i /dev/video0 -pix_fmt nv12 -r 30 -b:v 64k -c:v cedrus264 test.mp4
  5. We try to set up lirc on opi pc, but only receive works fine, any idea how to set it up to work in both modes - transmit and receive?
  6. Hi, On the main site: it says only 60 days to go for the next release :-) Well, to have a good user experience and squash bugs I think we should do a feature-freeze from about day 50 onwards - what is your take on that ? To do so, I was thinking about how you could handle this period on Github. Will “pull request’s” after feature-freeze be tagged for later integration? Everybody is welcome in squashing bugs (only the ones in code) eg. updating or adding configuration file for armbianmonitor ? eg. updating or adding information to the documentation ? Last but not least, if you can help with some ‘stubborn’ code or improvement here or here ? If you support this upcoming release just a little - it will become a great release for you too Did you already pick one from the above or do you know a dark corner in armbian you always wanted to do some clean up? Now is the time to do that. Post your idea here, write on github or simply fork the project on github and submit your pull request Tido
  7. I received the BPI M2 Ultra a couple of days ago (thanks to Nora Lee for the board) and worked a while on the BSP to learn and apply some of our changes on the ov5640 driver to be able to use Auto Focus and see if i could get Guvcview working on it. Here are some of my findings: * Working with the BSP is very similar to what we were used to on the Cubieboard A10/A20 era, those who worked with BSP at that time will feel very comfortable. * As usual, the BSP used arm-linux-gnueabi to compile the u-boot and kernel, i think is the Android way, and parses FEX to build a DTB. (Thanks to my old dual-core PC running Lubuntu). * It is hard to know where to change in the BSP to get your changes applied to DTB, it is a trial and error but once you learn and know how to bypass the bugs you can get it working your way. * working with BSP is not trivial I am not as expert as @tkaiser to squeeze the board and do some benchmarks the right way or brush the bits, i just wanted to get the Camera working and compare to what we have so far, one nice thing about the board is it runs way cooler than H3 at 1200Mhz. What i did so far: * compiled u-boot and kernel with armhf (don't ask me about mali driver and 3D things, it compiled but i did not tested) * applied some changes on ov5640 for AF and to work with MPJPG-streamer * compiled Guvcview as the usual way Issues: * For some unknown reason ION memory manager fails most of the times, need a way to extend the contiguous memory, anyone have any idea how to? * Guvcview have trouble and core dumps most of the times, need to investigate it. * MJPG-Streamer works better, thanks to FriendlyArm work. * AF works, perhaps a bit slower or just because we can not change AF zone as we can in Android with the Touch. But i think it works nice with good light condition if you want close up. Here are some samples you can have a look and see AF working and the state of Cedrus. 1920x1080 MP4 (cedrus264) 800x600 MP4 (cedrus264) What next? * Apply these changes on OV5640 (Armbian) * Improve the OV5640, i realized Enhanced OV5640 runs a bit hot (may be too hot) with AF. Guvcview with AF in action: And finally Let's test Guvcview with FA A64 soon....
  9. Hello, I experimented with various OS-es for my new Odroid-XU4. From what I have learned I like armbian the best because it's the closest to the original debian. A clean, small, tuned up system with the possibility to switch back to sysvinit from system(d). What I would run on it is not a desktop environment but exactly Kodi. The XU4 comes with Ubuntu 16 LTS preloaded to sdcard and I can say this is the OS which maxes out the potential of this hardware. With this after an update & upgrade everything works out of the box: kodi, networking, hdmi-cec, hdmi-audio. With using the unofficial debian jessie for odroid: It is possible to put a working odroid-kodi environment together on jessie using these packages but not on armbian. Using these 3 sources: wget # package list for ODROID XU3 devices and all Distributions (Kernel and Headers) wget # package list for all ODROID devices / Debian Jessie (not for Debian Wheezy, or Ubuntu 12.04) wget # package list for all ODROID devices / Debian Jessie (backports of newer or missing packages) The kodi packages install but then kodi will break with libgl error. So my question is will kodi be officially supported on armbian in the future? Armbian_5.14 ============ Linux odroidxu4 3.10.102-odroidxu4 #2 SMP PREEMPT Tue Jun 21 18:55:10 CEST 2016 armv7l GNU/Linux Module Size Used by fuse 74906 1 bonding 101352 0 cdc_ether 5022 0 usbnet 23026 1 cdc_ether r8152 60184 0 spidev 5907 0 spi_s3c64xx 14774 0 s3c2410_wdt 7601 0 init(1)-+-cron(1568) |-dbus-daemon(1697) |-dhclient(1624) |-getty(1890) |-getty(1891) |-getty(1892) |-getty(1893) |-getty(1894) |-getty(1895) |-haveged(1515) |-nmbd(1729) |-ntpd(1585) |-rsyslogd(1396)-+-{in:imklog}(1400) | |-{in:imuxsock}(1399) | `-{rs:main Q:Reg}(1401) |-smbd(1864)---smbd(1889) |-sshd(1816)---sshd(1907)---bash(1994)---pstree(2004) `-udevd(246) Ubuntu 16 LTS ============= Linux odroid 3.10.96-117 #1 SMP PREEMPT Thu Jul 28 18:28:12 UTC 2016 armv7l armv7l armv7l GNU/Linux Module Size Used by cdc_ether 4675 0 usbnet 22817 1 cdc_ether r8152 53542 0 ina231_sensor 9048 0 i2c_s3c2410 9423 0 Section "Device" Identifier "Mali-Fbdev" Driver "armsoc" Option "fbdev" "/dev/fb0" Option "Debug" "false" Option "DPMS" "false" EndSection Section "Screen" Identifier "Default Screen" Device "Mali-Fbdev" DefaultDepth 24 EndSection Section "ServerLayout" Identifier "Default Layout" Option "BlankTime" "0" Option "StandbyTime" "0" Option "SuspendTime" "0" Option "OffTime" "0" EndSection Section "DRI" Mode 0666 EndSection systemd(1)─┬─ModemManager(2781)─┬─{gdbus}(2818) │ └─{gmain}(2815) ├─NetworkManager(2788)─┬─dhclient(4790) │ ├─dnsmasq(2965) │ ├─{gdbus}(2840) │ └─{gmain}(2838) ├─accounts-daemon(2780)─┬─{gdbus}(2811) │ └─{gmain}(2808) ├─agetty(3156) ├─agetty(3157) ├─avahi-daemon(2810)───avahi-daemon(2858) ├─avahi-dnsconfd(2798) ├─cron(2793) ├─cups-browsed(2879)─┬─{gdbus}(2919) │ └─{gmain}(2918) ├─cupsd(6892) ├─dbus-daemon(2776) ├─dbus-daemon(3006) ├─dbus-launch(3005) ├─nmbd(3232) ├─ntpd(3159) ├─polkitd(2834)─┬─{gdbus}(2855) │ └─{gmain}(2850) ├─rsyslogd(2782)─┬─{in:imklog}(2813) │ ├─{in:imuxsock}(2812) │ └─{rs:main Q:Reg}(2814) ├─rtkit-daemon(3017)─┬─{rtkit-daemon}(3027) │ └─{rtkit-daemon}(3028) ├─smbd(3246)─┬─smbd(3247) │ └─smbd(3255) ├─snapd(2819)─┬─{snapd}(2857) │ ├─{snapd}(2859) │ ├─{snapd}(2864) │ ├─{snapd}(2866) │ ├─{snapd}(2923) │ ├─{snapd}(2925) │ └─{snapd}(2924) ├─sshd(4660)───sshd(5214)───bash(5277)───pstree(6904) ├─systemd(5221)───(sd-pam)(5226) ├─systemd-journal(1241) ├─systemd-logind(2774) ├─systemd-udevd(1304) ├─upowerd(3170)─┬─{gdbus}(3172) │ └─{gmain}(3171) ├─whoopsie(2775)─┬─{gdbus}(2874) │ └─{gmain}(2870) ├─xinit(2876)─┬─Xorg(2892)─┬─{llvmpipe-0}(2948) │ │ ├─{llvmpipe-1}(2949) │ │ ├─{llvmpipe-2}(2950) │ │ ├─{llvmpipe-3}(2951) │ │ ├─{llvmpipe-4}(2952) │ │ ├─{llvmpipe-5}(2953) │ │ ├─{llvmpipe-6}(2954) │ │ └─{llvmpipe-7}(2955) │ └─kodi-standalone(3002)───kodi(3114)───kodi.bin(3116)─┬─{AESink}(3209) │ ├─{ActiveAE}(3208) │ ├─{CECAdapter}(3260) │ ├─{CECAdapter}(3262) │ ├─{CECAdapter}(3263) │ ├─{CECAdapter}(3264) │ ├─{CECAdapter}(3265) │ ├─{EventServer}(3280) │ ├─{PeripBusCEC}(3261) │ ├─{PeripBusUSBUdev}(3266) │ ├─{TCPServer}(3281) │ ├─{Timer}(3296) │ ├─{kodi.bin}(3243) │ ├─{kodi.bin}(3259) │ ├─{kodi.bin}(3273) │ ├─{kodi.bin}(3276) │ ├─{kodi.bin}(3277) │ ├─{kodi.bin}(3278) │ ├─{kodi.bin}(3279) │ ├─{kodi.bin}(3286) │ ├─{kodi.bin}(6879) │ ├─{mali-event-hnd}(3216) │ ├─{mali-hist-dump}(3226) │ ├─{mali-mem-purge}(3215) │ ├─{mali-renderer}(3225) │ ├─{mali-utility-wo}(3217) │ ├─{mali-utility-wo}(3218) │ ├─{mali-utility-wo}(3219) │ ├─{mali-utility-wo}(3220) │ ├─{mali-utility-wo}(3221) │ ├─{mali-utility-wo}(3222) │ ├─{mali-utility-wo}(3223) │ └─{mali-utility-wo}(3224) └─zabbix_agentd(2929)─┬─zabbix_agentd(2930) ├─zabbix_agentd(2931) ├─zabbix_agentd(2932) ├─zabbix_agentd(2933) └─zabbix_agentd(2934) Udev KERNEL=="mali",SUBSYSTEM=="misc",MODE="0777" KERNEL=="mali0",SUBSYSTEM=="misc",MODE="0777" KERNEL=="ump",SUBSYSTEM=="ump",MODE="0777" KERNEL=="ttySAC0", SYMLINK+="ttyACM99" KERNEL=="event*", SUBSYSTEM=="input", MODE="0777" KERNEL=="CEC", MODE="0777" KERNEL=="amvideo", MODE="0666" KERNEL=="amstream*", MODE="0666" ii kodi 16.1+hk3-exynosmfc5422 armhf Open Source Home Theatre (executable binaries) ii kodi-bin:armhf 16.1+hk3-exynosmfc5422 armhf Open Source Home Theatre (architecture-dependent files) ii kodi-data 16.1+hk3-exynosmfc5422 all Open Source Home Theatre (arch-independent data package) Using meveric repos: ii kodi-odroid 16.1-1+deb8 armhf Kodi - award-winning free and open source (GPL) software media player and entertainment hub (ODROID build) ii linux-dtb-odroidxu4 5.16 armhf Linux DTB, version 3.10.102-odroidxu4 ii linux-headers-odroidxu4 5.16 armhf Linux kernel headers for 3.10.102-odroidxu4 on armhf ii linux-image-odroidxu4 5.16 armhf Linux kernel, version 3.10.102-odroidxu4 ii linux-jessie-root-odroidxu4 5.16 armhf Armbian tweaks for jessie on odroidxu4 (default branch) ii linux-u-boot-odroidxu4-default 5.16 armhf Uboot loader 2012.07 Debian Jessie 8.5 ================= Linux odroid-jessie 3.10.92+ #1 SMP PREEMPT Tue Nov 17 11:14:11 CET 2015 armv7l GNU/Linux Module Size Used by cdc_ether 4507 0 usbnet 22193 1 cdc_ether r8152 49758 0 spi_s3c64xx 13713 0 ina231_sensor 8388 0 s3c2410_wdt 7016 0 dpkg --list |grep -i kodi ii kodi-odroid 16.1-1+deb8 armhf Kodi - award-winning free and open source (GPL) software media player and entertainment hub (ODROID build) root@odroid-jessie:~# dpkg --list |grep -i systemd ii libsystemd0:armhf 215-17+deb8u4 armhf systemd utility library # X.Org X server configuration file for xfree86-video-mali Section "Device" Identifier "Mali-Fbdev" Driver "armsoc" Option "fbdev" "/dev/fb0" Option "Debug" "false" Option "DPMS" "false" Option "Fimg2DExa" "true" Option "DRI2" "true" Option "DRI2_PAGE_FLIP" "false" # Option "Fimg2DExaSolid" "false" # Option "Fimg2DExaCopy" "false" Option "Fimg2DExaComposite" "true" Option "SWcursorLCD" "false" EndSection Section "Screen" Identifier "Default Screen" Device "Mali-Fbdev" DefaultDepth 24 EndSection Section "DRI" Mode 0666 EndSection init(1)─┬─avahi-daemon(1498)───avahi-daemon(1504) ├─console-kit-dae(1628)─┬─{console-kit-dae}(1629) │ ├─{console-kit-dae}(1630) │ ├─{console-kit-dae}(1631) │ ├─{console-kit-dae}(1632) │ ├─{console-kit-dae}(1633) │ ├─{console-kit-dae}(1634) │ ├─{console-kit-dae}(1635) │ ├─{console-kit-dae}(1637) │ ├─{console-kit-dae}(1638) │ ├─{console-kit-dae}(1639) │ ├─{console-kit-dae}(1640) │ ├─{console-kit-dae}(1641) │ ├─{console-kit-dae}(1642) │ ├─{console-kit-dae}(1643) │ ├─{console-kit-dae}(1644) │ ├─{console-kit-dae}(1645) │ ├─{console-kit-dae}(1646) │ ├─{console-kit-dae}(1647) │ ├─{console-kit-dae}(1648) │ ├─{console-kit-dae}(1649) │ ├─{console-kit-dae}(1650) │ ├─{console-kit-dae}(1651) │ ├─{console-kit-dae}(1652) │ ├─{console-kit-dae}(1653) │ ├─{console-kit-dae}(1654) │ ├─{console-kit-dae}(1655) │ ├─{console-kit-dae}(1656) │ ├─{console-kit-dae}(1657) │ ├─{console-kit-dae}(1658) │ ├─{console-kit-dae}(1659) │ ├─{console-kit-dae}(1660) │ ├─{console-kit-dae}(1661) │ ├─{console-kit-dae}(1662) │ ├─{console-kit-dae}(1663) │ ├─{console-kit-dae}(1664) │ ├─{console-kit-dae}(1665) │ ├─{console-kit-dae}(1666) │ ├─{console-kit-dae}(1667) │ ├─{console-kit-dae}(1668) │ ├─{console-kit-dae}(1669) │ ├─{console-kit-dae}(1670) │ ├─{console-kit-dae}(1671) │ ├─{console-kit-dae}(1672) │ ├─{console-kit-dae}(1673) │ ├─{console-kit-dae}(1674) │ ├─{console-kit-dae}(1675) │ ├─{console-kit-dae}(1676) │ ├─{console-kit-dae}(1677) │ ├─{console-kit-dae}(1678) │ ├─{console-kit-dae}(1679) │ ├─{console-kit-dae}(1680) │ ├─{console-kit-dae}(1681) │ ├─{console-kit-dae}(1682) │ ├─{console-kit-dae}(1683) │ ├─{console-kit-dae}(1684) │ ├─{console-kit-dae}(1685) │ ├─{console-kit-dae}(1686) │ ├─{console-kit-dae}(1687) │ ├─{console-kit-dae}(1688) │ ├─{console-kit-dae}(1689) │ ├─{console-kit-dae}(1690) │ ├─{console-kit-dae}(3494) │ ├─{gdbus}(1693) │ └─{gmain}(1692) ├─cron(1328) ├─dbus-daemon(1365) ├─dhclient(1810) ├─getty(1597) ├─getty(1598) ├─getty(1599) ├─getty(1600) ├─getty(1601) ├─getty(1602) ├─nmbd(1395) ├─ntpd(1809) ├─rsyslogd(1240)─┬─{in:imklog}(1242) │ ├─{in:imuxsock}(1241) │ └─{rs:main Q:Reg}(1244) ├─rtkit-daemon(3434)─┬─{rtkit-daemon}(3435) │ └─{rtkit-daemon}(3436) ├─smbd(1566)───smbd(1607) ├─sshd(1864)─┬─sshd(1876)───bash(1884)───apt-get(3587)───dpkg(3620)───dpkg-deb(3753)─┬─dpkg-deb(3754) │ │ └─dpkg-deb(3755) │ └─sshd(3690)───bash(3698)───pstree(3790) └─udevd(345)
  10. Armbian Cubietruck Desktop does not start the graphical environment for Nand. I downloaded the Armbian Legacy 5:10 Cubietruck Debian jessie 3.4.112 Desktop ( , I recorded the image on an SD card using a software called Rufus ( ) Insert the card into Cubietruck and Armbian starts and works perfectly ! run the script to perform the copy of the card to nand , the same copy without any error and asks at the end off the Cubietruck and disconnect the SD card . After disconnecting the SD card the Armbian does not start. However I rode the Nand and it meets all of the recorded files. I wonder how to start the Cubietruck by nand perfectly? Here the configuration of FSTAB file written in NAND my Cubietruck. copy was performed using the script Do not start by NAND /dev/nand2 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaults,rw,nosuid 0 0 /var/swap none swap sw 0 0 /dev/nand1 /boot vfat defaults 0 0 Sorry I do not speak English , I'm using Google Translate ! But I thank the collaboration of all of the community !
  11. I'm trying the Orange Pi PC for a smal project but while installing th OpiPC corrupts its SD Card. Typical error occurence: - Install Debian Jessy server on 16GB SD Card (ScanDisk Ultra class 10). - run first bootup. - update und upgrade software, install nfs-common and rrdtool. - setup keyboard, console-setup, tzdata, locales, static ip. - edit /etc/fstab, mount nfs-volume. - copy project software (mostly bash scripts, reading cpu temp and switching GPIO-Pin). - seting up a cron job. on one of the next shutdown/reboot the console shows mmc errors while reading and writing (see log file). - the Sd card can not be started any more, all attempts fail with mmc read and write erros. - reinstalling the image on the same SD card allows me to start over again. On first Boot no errors are shown. tested variations: - after the crash the SD card can be tested with badblocks on a different system; no errors shown - 3 other SD cards (32GB class10) show the same results - Using an industrie standard power supply with 3 different voltages (4,5V, 5V, 5,5V) show the same errors - using Orange Pi Plus, no errors are shown (not within the firs 3 days and many reboots). - using other linux builds from or laboris do not show this efect. Is there any thing in /boot/scrip.bin that sets mmc timing ? Any other idear ? Greetings Eddy kern_log.txt
  12. Hi I want to build armbian for nanopi neo with a different mainline. What I have done is 1. added lib.config file in userpatches with statement ARMBIAN_MAINLINE_KERNEL_VERSION='4.9' that didn't work, I still get a 4.10.1 kernel build 2. then changed ARMBIAN_MAINLINE_KERNEL_VERSION='4.9' that didn't work either, I got 4.10.1 kernel build Any other tricks? -jerry
  13. Hi, I updated the gc2035 driver, kernel 3.4.x. The driver can be loaded with parameter, so you can choose to have different window size and/or image quality on the fly (well, kind of). Parameter: hres=[0,1,2] hres=0 (default without parameter) 640x480, 15 fps, good quality (fps with good light condition) 1280x720, 13 fps, poor quality (fps with good light condition) 1600x1200, 10 fps, poor quality (fps with good light condition) hres=1 800x600, 12 fps, good quality (fps with good light condition) 1600x1200, 8 fps, medium quality (fps with good light condition) hres=2 320x240, 20 fps, poor quality (fps with good light condition) 640x480, 18 fps, medium quality (fps with good light condition) 800x600, 18 fps, medium quality (fps with good light condition) Loading the driver (manually): modprobe gc2035 hres=1 modprobe vfe_v4l2 or add it to /etc/modules Unloading the driver: modprobe -r -v vfe_v4l2 modprobe -r -v gc2035 and loading with other window size and performance: modprobe gc2035 hres=2 modprobe vfe_v4l2 PS: Light condition does affect fps performance! github: Cheers, @lex
  14. Hello , I have a Adafruit TFP401 HDMI/DVI converter module. On my orange pi pc plus with Armbian kernel 3.4.113, i changed resolution to 800x480 on script.bin file and screen doesn't fit, it has margin from left. anyone help me ? Module Screenshot
  15. Hello, I'm using armbian 5.25 on OPI Lite and wifi dongle 8192cu, after instaling these drivers: I saw that the interface drop half of the packages.... Can someone provide better drivers or tell me how to fix that? wlan1 Link encap:Ethernet HWaddr 00:13:ef:6b:24:e2 inet addr: Bcast: Mask: inet6 addr: fe80::213:efff:fe6b:24e2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 -------->>>>>> RX packets:22255 errors:0 dropped:20602 overruns:0 frame:0 TX packets:22 errors:0 dropped:2 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3853233 (3.6 MiB) TX bytes:2734 (2.6 KiB) And not everytime it takes IP ?!?! Also whatever dongle i use it won't go up automatically and it's necessary to do ifconfig wlan1 down and after that ifconfig wlan1 up
  16. Hello I have a little problem with the usb devices, i use usb camera and if u plug the power supply to the OPI Lite board (5.25) it recognize the camera but it doesn't work well (stream with like 8-10 fps), after a software reboot, the device go to other Bus and the camera work fine with 15-30 fps stream. Before reboot, exact on first power of the board: Bus 006 Device 002: ID 058f:3822 Alcor Micro Corp. Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter After reboot: Bus 003 Device 002: ID 058f:3822 Alcor Micro Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter I try to remove and after that load again uvcvideo driver, but nothing happened, i tried some scripts to restart the usb ports but the result was 0, only if i unplug and plug the camera again or reboot solve the problem. Also i tried with different power supplies and nothing changed. Currently we use chargers from the Orange Pi manufacture so this is the best power supply i guess. Any ideas how can i configure the camera to be on Bus 3 and tha wifi dongle to be on Bus 2 or some other solution to the problem?
  17. Hello, I'm using OPI Lite with 5.25 armbian and there is a little problem with the permissions: root@orangepilite:~/Raws/libjpeg/jpeg-8c# ./configure -bash: ./configure: Permission denied root@orangepilite:~/Raws/libjpeg/jpeg-8c# sudo ./configure sudo: ./configure: command not found root@orangepilite:~/Raws/libjpeg/jpeg-8c# ls | grep configure configure That appeared to me twice, first time i compile and install nodejs and npm was not recognized like a command (ask for permissions after use sudo just said command not found), this is my second hit to that problem, trying to compile libjpeg. I try to gi to root owners for that folder, same results, I try to cp the files and then compile it, same results and so on and so on. Can someone explain me from where these problems are coming?
  18. With Debian LTS, updates at least every week. Signatures don't work Stupid, childish pictures for idiots,called captchas are not shown security (!) checks can't be used. No administors can be reached because of github. Never. neve again answer this, I can't be reached in this forum. I can be reached by being much more secure than all zhe securitythingies in this forum. Well, I do have a question armbianspecific: When will gnuit be made working for armbian? Oh and another one: Sinfo doesn't show the frequency of the CPU - to be made working. Why can't emails be sent to operators to be inserted in forum? Bye.
  19. Armbian_5.20_Bananapipro_Debian_jessie_4.7.3 Armbian_5.20_Bananapipro_Debian_jessie_4.7.3_desktop both images are not working on my bananapro. Actually when I tried the first time they worked properly but after that time when i tested other images from lemaker links. After from that time no armbian images are working. keyboard and mouse are not able to power up. Also it showing swap on /var/swap. Priority:-1 extents 1 across 131068k SSFS and keep waiting there only. Please help me i was successfully able to build can4linux on armbian Debian desktop 4.7 which is not at all possible on other images.
  20. We would like to thanks all of those who participated in our small contest. Great submission! It was really hard to make a cherry pick, while the winner will be chosen by the vote. Since we only need one default wallpaper and that one must be as generic and clean as possible, this choice is as follows. Few others, which might come into action, had either too small text size, strange colors or were simply too busy. We might will add more than those five wallpapers to our desktop or use them as a boot splash. Vote will be online until 16.12. 1. Dre0x-Minum-dark 2. chzbacon-Micro-SD 3. chzbacon-Linen---Dark 4. 1430-very-dark 5. username-dark
  21. Hi Friends, on Banian I was using "xset dmps force off" and "xset dpms force on" to switch display off and on as I need it. Tryed to use this commands in terminal with armbian but nothing happens. I'm using LeMakers 5" LCD RGB Display with PCAP Touch. Armbian is 5.24 jessi with desktop and 4.8.12 Kernel. Has anyone an Idea, how to turn off and on display form terminal? Yours, Martin
  22. Hi specialists, I'm trying to understand how the axp209 on Banana Pi works with the A20. In the Banana Pi schematics I see, that they are connected with only four lines. Two lines are used for I²C (TWSI), one is from axp209 PWROK to RESET# of A20 and another one is connected from axp209 IRQ and GPIO2 to NMI# of A20. When system is off and I press my Power Button (K1) on the Pi, the system is booting. System is running and I long press the Power Button, System shuts down. But can anyone say whats happening? What does axp209 do with IRQ, GPIO2 and PWROK pins? Wich way does the A20 recognize, that it has to shutdown? Yours Martin
  23. I just got the Guvcview working on the Pine64+ with a 5MP camera. Have a look here: Some consideration: 640x480 -> 30 FPS 1280x720 -> 18 FPS
  24. Hi I've just set up the Roseapple Pi with Armbian (legacy server Debian). As I often find (over a range of monitors) there's an overscan so bad I can't see the "login" instructions at the bottom of the screen... on all sides the text is off the edge of the screen. For the life of me I can't see WHERE to adjust the overscan - can anyone help. Pete.
  25. Hi, I updated my cubietruck jessie to 5.23. update successful but no boot on kernel . I boot on sd card and mount nand . no uImage but an zImage. I use mkimage in order to generate uImage and it work. kernel packaging must be corrected.