Jump to content

Search the Community

Showing results for tags 'lime2'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Categories

  • Official giveaways
  • Community giveaways

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP/Jabber


Skype


Github


Discord


Location


Interests

  1. Hi, I'm using a xenial system with Kernel 4.9.11-sunxi on LIME2 (actually it's an Olimex A20-SOM with external RTL8211 PHY) and trying to prevent the ethernet from coming up on boot. When turning the system on, the ethernet interface will assign a random MAC address; later on my script sets a proper MAC from an assigned range. Until then the eth0 interface must stay down to prevent the network from being spammed with bogous messages. This is because the ethernet interface chooses a random MAC address when the system boots up; later on a script sets the proper MAC address from an assigned range (along with IP and route configuration); The link must stay down until this has happened. I've tried to replace the eth0 entries in /etc/network/interfaces with auto eth0 inet manual Which has the effect that the interface no longer gets a DHCP address, but I'm still seeing this in my dmesg log: [ 15.972814] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 16.990692] sun7i-dwmac 1c50000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 16.990760] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
  2. Hello , I have a fresh install of armbian Legacy 3.4.113 desktop Xenial on olimex lime2 I try since many hours to install lighttpd but I have a problem On a new fresh install I do apt-get update && apt-get upgrade after a restart i install lighttpd apt-get install lighttpd after this , without restart if I test lighttpd it's ok but after a restart lighttpd won't start A strange thing is after install I have "/var/log/lighttpd/error.log" but after the restart it disappears and lighttpd don't re-create it if i do /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf I have I do not understand why this folder is erased on reboot can you help me please ?
  3. Hello, I received a few weeks ago some new Lime2 boards. Using compiled Armbian kernel leads to a network problem: no IP is set and network does not work I have messages when connecting Ethernet cable: sun7i-dwmac 1c50000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx Link is Up - 100/Full The ip a command gives: 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 02:02:02:cc:cc:cc brd ff:ff:ff:ff:ff:ff inet6 fefe::fe:xxx:xxx:9307/64 scope link valid_lft forever preferred_lft forever I think the problem is related to the new revision of the board as described here : Ethernet PHY is changed to RTL8211E replacing the obsolete RTL8211CL no need for kernel patches But searching through the kernel options did not give me any clue, and nothing works. What is to be done to make network up again ? Is there something to reconfigure on an existing armbian installation ? Are there some files to modify ?
  4. Hi, Does armbiam fully support SATA port on Olimex Lime2? greetings, Marcin
  5. Hello, I have the LIME2 board from Olimex (A20 SoC). I tried writing the image Armbian_5.20_Lime2_Debian_jessie_4.7.3_desktop to an SD card with dd. However, nothing happens when I plug in power (except that a red light near the barrel jack connector turns on). I tried pressing some of the switches (reset, power) but they didn't do anything either. This is the second LIME2 board I have received that just won't turn on. I have also tried with the images recommended by Olimex, to no avail. Is there something special that needs to be done that I'm missing?
  6. On an Olimex Lime2 NAND 4GB I installed Armbian legacy debian jessie server on an sd-card. "lime2 3.4.112-sun7i #10 SMP PREEMPT Sun Oct 23 15:49:51 CEST 2016 armv7l" I followed: https://docs.armbian.com/User-Guide_Getting-Started/#how-to-install-to-emmc-nand-sata-usb and after reboot without card, it did not boot: (from serial console) [...] [ 0.366] flash init finish [ 0.367] mbr magic is not correct [...] Anyhow I didnt understand as prerequisits in description: "pre-installed system on NAND (stock Android or other Linux)" I erased the nand before, since I used it otherwise: dd if=/dev/zero of=/dev/nand bs=512 count=16 Question: Is my NAND broken or must I install some mbr before in the nand ? Any advice ? mfg winfried Appendix: complete boot output: HELLO! BOOT0 is starting! boot0 version : 2.0.0� read dram para. dram driver version: 1.15 dram size =1024MB 0x00018608 super_standby_flag = 0 Succeed in opening nand flash. block from 2 to 6 deal block 2 Succeed in reading Boot1 file head. The size of Boot1 is 0x00068000. The file stored in 0x00000000 of block 2 is perfect. Check is correct. Ready to disable icache. Succeed in loading Boot1. Jump to Boot1. [ 0.159] boot1 version : 2.0.0 [ 0.159] script installed early ok [ 0.160] pmu type = 3 [ 0.265] bat vol = 942 mv [ 0.278] axi:ahb:apb=4:2:2 [ 0.278] set dcdc2=1400mv, clock=912M successed [ 0.281] key [ 0.293] no key found [ 0.293] flash init start [ 0.293] NB1 : enter NFB_Init [ 0.296] NB1 : enter phy init [ 0.299] [NAND] nand driver(A20) version: 0x0x00000002, 0x0x00000012, data: 0x426fff64 1111692733 [ 0.308] set retry default value: [ 0.311] 0x00000020[ 0.314] 0x00000020[ 0.316] 0x00000073[ 0.318] 0x000000c1[ 0.321] [ 0.322] get the good blk ratio from hwscan : 870 [ 0.327] NB1 : nand phy init ok [ 0.366] NB1 : init ok [ 0.366] flash init finish [ 0.367] mbr magic is not correct [ 0.370] fs init fail [ 0.372] fs init fail, jump to fel [ 0.376] set retry default value: [ 0.380] 0x00000020[ 0.382] 0x00000020[ 0.384] 0x00000073[ 0.386] 0x000000c1[ 0.389] [ 0.390] [NAND]dumy read,chip 0x00000000
  7. I have a problem similar to post http://forum.armbian.com/index.php/topic/182-freezing-problems-with-bpi-r1/:my board is blocked for the second time. But my configuration is quite different from that post: Kernel: linux-image-next-sunxi 4.3 (version 4.2.0-sunxi) UBoot: linux-image-next-sunxi 4.3 (2015.07) RootFS: on sda1 powered by the board (WDC WD10JFCX-68N) UpTime: about 10 days before my last restart. When the board is blocked I can't interact with the debug console on the serial port. I cant't find anything interesting in /var/log, but I'm not really an expert.
  8. Hi, we bought several Lime2 and tested them. Unfortunatelly, the GBit-Lan did not seem to work reliyable. Later ping tests revealed a packet loss on many boards of 1% to 20%. (eg. "ping -s 9000 -i 0.0001 -c 5000 fritz.box"). Some boards dont have any problems, other more. On heavy access with SSD it's increasing a little. It's happens also without SSD. Other boards worked fine at the same power and network cable. Its possible thant this strange TX_DELAY isn't set correctly? Are there other problems known? I used the wheezy image with kernel 3.4.105-lime2 and 3.4.107 from you latest wheezy image. The image with Kernal 4.0.4 stopped after "restarting sshd", so I couldnt test them. Any thoughts? Can I adjust the TX-Delay timing without recompiling? Thanks, Jan
  9. Hi, I have compiled the FFmpeg version in "https://github.com/stulluk/FFmpeg-Cedrus" (great job !!) to get h264 hardware encoding on Olinuxino-LIME2-4G A20 board. My goal is to encode in realtime h264 with a low cpu load and to stream video with crtmpserver. The crtmpserver service runs fine, while FFmpeg exits with the following error: [cedrus264 @ 0x28cf680] VE Open error. I entered the following command line: root@lime2:/etc/campipe# ffmpeg -f v4l2 -s 640x480 -pix_fmt nv12 -i /dev/video0 -pix_fmt nv12 -qp 23 -c:v cedrus264 -threads 0 -b:v 1200k -bufsize 2400k -r 25 -vewait 3600 -an -f matroska - | ffmpeg -i - -c:v copy -f flv -metadata streamName=livestream tcp://0.0.0.0:6666 ffmpeg version git-2015-01-22-f86a076 Copyright (c) 2000-2014 the FFmpeg developers built on Oct 22 2016 20:38:02 with gcc 4.9.2 (Debian 4.9.2-10) configuration: --prefix=/usr --enable-nonfree --enable-gpl --enable-version3 --enable-vdpau --enable-libx264 --enable-libmp3lame --enable-libpulse --enable-libv4l2 --enable-libtheora --enable-libvorbis --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable-libfaac ffmpeg version git-2015-01-22-f86a076 Copyright (c) 2000-2014 the FFmpeg developers built on Oct 22 2016 20:38:02 with gcc 4.9.2 (Debian 4.9.2-10) configuration: --prefix=/usr --enable-nonfree --enable-gpl --enable-version3 --enable-vdpau --enable-libx264 --enable-libmp3lame --enable-libpulse --enable-libv4l2 --enable-libtheora --enable-libvorbis --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libvo-amrwbenc --enable-libfaac libavutil 54. 6.100 / 54. 6.100 libavcodec 56. 0.101 / 56. 0.101 libavformat 56. 2.100 / 56. 2.100 libavdevice 56. 0.100 / 56. 0.100 libavfilter 5. 0.102 / 5. 0.102 libswscale 3. 0.100 / 3. 0.100 libswresample 1. 1.100 / 1. 1.100 libpostproc 53. 0.100 / 53. 0.100 libavutil 54. 6.100 / 54. 6.100 libavcodec 56. 0.101 / 56. 0.101 libavformat 56. 2.100 / 56. 2.100 libavdevice 56. 0.100 / 56. 0.100 libavfilter 5. 0.102 / 5. 0.102 libswscale 3. 0.100 / 3. 0.100 libswresample 1. 1.100 / 1. 1.100 libpostproc 53. 0.100 / 53. 0.100 Input #0, video4linux2,v4l2, from '/dev/video0': Duration: N/A, start: 1710.222761, bitrate: 73728 kb/s Stream #0:0: Video: rawvideo (YUY2 / 0x32595559), yuyv422, 640x480, 73728 kb/s, 15 fps, 15 tbr, 1000k tbn, 1000k tbc [cedrus264 @ 0x1b97680] VE Open error. Output #0, matroska, to 'pipe:': Stream #0:0: Video: h264, q=2-31, 128 kb/s, 25 fps Metadata: encoder : Lavc56.0.101 cedrus264 Stream mapping: Stream #0:0 -> #0:0 (rawvideo (native) -> h264 (cedrus264)) Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height pipe:: Invalid data found when processing input Any idea why this is? Thanks for any infos... Tommaso
  10. Hi there Have purchased a Lime 2 device, as it offered GigE-which my Pi's dont :-) Loaded up both the vanilla and the normal distro's but both have this annoying habit of the device just goes to sleep-sometimes after a few hours. When I say sleep, I can still see the Ethernet LED's blinking away-but it wont respond to PING's, and it wont respond to SSH. Plugging in a monitor and keyboard doesn't bring it back to life either. If I power recycle it (2.5A unit being used-have tried the OTG and the 5vdc but no difference), up she comes. Fully updated in terms of packages. I have even set up a continuous ping to my home router from the Lime 2 (its on my internal LAN) to see of this would keep it up, but no luck. I've searched up on this, but nothing I find seems to make any difference. Before I send it back (UK reseller), anyone have any ideas on what I could try? Desperate for the thing to work, but as it would be in a remote location, no way can I use it if it decides to give up the ghost on a random basis! :-) cheers cabs
  11. Hello, I attached Micron M500 SSD with gpt table, also Seagate 3GB hard disk with gpt to sata data connection and powered disks with external power adapter(it supplies 5V and 12V and comes with usb-sata adapter). U-Boot shows message: SCSI: AHCI PHY power up failed. dmesg: SATA AHCI Phy Power Failed! SATA AHCI Phy Calibration Failed! sw_ahci sw_ahci.0: controller can't to PMP, turning off CAP_PMP sw_ahci sw_ahci.0: forcing PORTS_IMPL to 0x1 sw_ahci sw_ahci.0: AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl platform mode sw_ahci sw_ahci.0: flags: ncq sntf pm led clo only pio slum part ccc scsi0 : sw_ahci_platform ata1: SATA max UDMA/133 mmio [mem 0x01c18000-0x01c18fff] port 0x100 irq 88 . . . ata1: SATA link down (SStatus 0 SControl 300) The raw "Legacy Jessie Server" image was download today. Under U-Boot neither of scsi scan and other commands showed that it recognize disk. If disks were connected through usb-sata adapter, linux recognizes disks. The same U-Boot message is displayed if using opensuse image. Funtoo does not find SSD either. lime2 is "C" revision. 2 sata cables were tried, and these cables were working earlier ok. Is this U-Boot message is vital, and linux relies on U-Boot while discovering SATA? Is it necessary to use lime2 power source in order for linux to discover sata disk? If yes, how to power sata hard disk? Gintaras
  12. Hi all, some days ago I successfully built the image mentioned above (Build environment is Ubuntu 14.04/64 bit). The only remarkable issue was the ever-repeating "firstrun" script, which was easily solved with the method mentioned here: http://forum.armbian.com/index.php/topic/1100-post-install-scripts-on-every-reboot/#entry8509 (may be ALL of the scripts should be changed this way?) But today, after checking out the actual "master", I see a lot of failed copy and sed commands until the debootstrap-ng script finally fails at Mali-libdri2. The 1st occurrence of an error was during installation of "ramlog". I've inserted a breakpoint and looked into the image. "dpkg.log" reads 2016-05-13 07:45:53 startup archives install 2016-05-13 07:45:53 install ramlog:all <none> 2.0.0 2016-05-13 07:45:53 status half-installed ramlog:all 2.0.0 2016-05-13 07:45:53 status unpacked ramlog:all 2.0.0 2016-05-13 07:45:53 status unpacked ramlog:all 2.0.0 I manually issued the dpkg -i with the following result: dpkg -i /tmp/ramlog_2.0.0_all.deb Selecting previously unselected package ramlog. (Reading database ... 9890 files and directories currently installed.) Unpacking ramlog (from /tmp/ramlog_2.0.0_all.deb) ... dpkg: dependency problems prevent configuration of ramlog: ramlog depends on lsof; however: Package lsof is not installed. ramlog depends on rsync; however: Package rsync is not installed. dpkg: error processing ramlog (--install): dependency problems - leaving unconfigured Errors were encountered while processing: ramlog I have tried to deactivate the apt-cache by inserting the somewhat hidden command "NO_APT_CACHER=yes" in my compile.sh but this didn't help. (There are more errors following this one, e.g. /etc/default/console-setup is missing as well as /etc/lirc/hardware.conf, /etc/lirc/lircd.conf, /etc/wicd/manager-settings.conf, /etc/default/nodm, /etc/X11/xorg.conf) Some strange messages in-between, which I think I also saw earlier but as i haven't faced an issue with the image I ignored them: [ o.k. ] Installing desktop [ XFCE ] /bin/tar: A lone zero block at 70 /bin/tar: A lone zero block at 70 /bin/bash: unzip: command not found At the very end: [ o.k. ] Adding support for Mali - acceleration [ sunxi ] E: Unable to locate package mesa-utils-extra E: Unable to locate package libdri2-1 E: Unable to locate package libdri2-dev dpkg: dependency problems prevent configuration of libdri2-1: libdri2-1 depends on libdrm2 (>= 2.3.1); however: Package libdrm2 is not installed. libdri2-1 depends on libx11-6 (>= 2:1.4.99.1); however: Package libx11-6 is not installed. libdri2-1 depends on libxext6; however: Package libxext6 is not installed. dpkg: error processing libdri2-1 (--install): dependency problems - leaving unconfigured Errors were encountered while processing: libdri2-1 [ error ] Installation failed [ Mali - libdri2-1 ] What should I do now?
  13. Hello Everybody I'm using olimex olinuxino lime2. I'm to expiriment on real time linux. I could build the kernel with the real time patch by disabling newer kernel patches, .108 and on, but I would really like to have a ticking system. There are not options for this in the kernel menu configuration. Just tickless system. That may cause some extra delays on realtime processes. Is there a way to configure tick frequency at 1khz? Thank you for your time
  14. have there been more changes for Desktop recently except the repos? Yesterday I have updated and tried to compile, noticed that the function "fetch_from_github" was gone (replaced by "fetch_from_repo"?). After I changed my script accordingly I was able to compile, but the desktop doesn't come up any more. It looks like "fbturbo" module is completely missing? I don't see any reference to this in the logs; where should it be so I can try to debug?
  15. Hi to All, I decided to start this new tread for searching of the best solution for unification of the boot process from any available media. Main target is Armbian next and development branches and mainline Kernel and U-Boot. Boot device can be eMMC, SD/MMC, USB Flash/HDD and SATA HDD/SSD probed in given order. In case of booting from eMMC, SD/MMC and USB Flash Read-Only Root FS can be used optionally. In case of booting from SD/MMC or USB Flash eMMC and / or SATA devices can be updated automatically. Some effort in this direction was done by me and described in Armbian Customization thread. The tests was done on Olimex' A20-Olimexino-Lime2-eMMC (HW rev. E) board with following additional staff: 60GB SATA SSD with SATA-CABLE-SET MOD-WIFI-R5370 mounted on the rear panel - only antenna outside USB-ETHERNET-AX88772B - optional BATTERY-LIPO6600mAh ALUMINIUM-HEATSINK-20x20x6MM later changed with special high efficient cooling system A10-OLinuXino-LIME-BOX later changed to water and dust resistant solution based on Aluminum box FTDI FT4232H based USB Hi-Speed Serial/Hub Module AC/DC 5V/4A wall adapter Dual LED Red + Blue Display Digital Voltmeter Ammeter DC 3.5-28V 3A Additional User Push Button and 3 LEDs are connected via Lime2 GPIO-1 connector 1-Wire GPIO based Master and additional Device Boot control is implemented via Lime2 GPIO-1 connector Reset, Power On/Off buttons and Charge LED are wired to front panel doubles Console, DC-IN, USB and Ethernet connectors are wired to rear panel doubles The current status is: U-Boot is patched to:recognize eMMC; search a boot-able device on SATA, USB, SD/MMC, eMMC etc.; boot from the boot-able device with the highest priority; send to the kernel via the command line right root=PARTUUID=${uuid}; Kernel is patched to recognize eMMC; firstrun script is modified to resize right MMC device (mmcblk0 or mmcblk1); eMMC and SATA device experimental update scripts are implemented and tested; it is investigated the classical and overlayfs way to run Debian on RO Root FS; Described staff is working fine on latest Armbian (5.17), Kernel (4.6.3) and U-Boot (2016.05). Not solved issues are: to mount root accordingly without explicit setting in /etc/fstab; to resize root partition from firstrun script in case of USB and / or SATA devices; to prepare and use Read-Only Root FS on eMMC, SD/MMC and USB Flash optionally; to start eMMC and /or SATA device update procedure from firstrun script if boot from SD/MMC or USB Flash. The main use case will include following steps: If the system will be setup for the first time SD/MMC has to be used for been able to install U-Boot on empty eMMC; In case of next FW update USB Flash will be used to boot from by installed on eMMC U-Boot; Booting from SD/MMC will be forced by pushing of user button or renaming of /boot/boot.scr file on the devices with higher priority; Booting from USB Flash will be done always when present because of highest priority; firstrun script will be executed always if booting from image cloned device and the system will reboot if necessary; At the end of firstrun script eMMC and / or SATA device update scripts will be executed to update them from image or SD/MMC or USB Flash itself. The following staff was used to customize Armbian: Mainline U-Boot patch to enable eMMC: Mainline U-Boot patch to change boot order: Mainline U-Boot boot script: Mainline Kernel patch to enable eMMC: Change in do_expand_rootfs() function of firstrun script to recognize right MMC device to resize: # DEVICE="/dev/"$(lsblk -idn -o NAME | grep -w mmcblk0) DEVICE=$(mount|grep ' / '|cut -d' ' -f 1 | cut -dp -f1) Reboot script and service looking for user button push: Experimental script to update eMMC from image: Experimental script to update SATA SSD from image: Whole customization process with more details and test results can be found on Armbian Customization thread. Latest prototype insides and test results can be found in the attached files. Any ideas, comments and references are welcome. Best regards Chris Lime2-rev-C-E-comp-06-p8.pdf Lime2-rev-C-E-comp-06-7p.pdf
  16. Hello, I try use UART interface on Lime2, but have problems with data transmission. Input echo 12345 > /dev/ttyS2 Output â–’;375 UART settings stty -F /dev/ttyS2 9600 -parity cs8 -cstopb How to detect the problem? Thanks
  17. Hi, I generated SD images for A20-OLinuXino-Lime2-eMMC boards. Kernel is 4.6.2, Debian wheezy, u-boot 2016.05 On my last two images (generated with slight differences in u-boot configuration), the first time I booted, everything worked fine. After that, I installed a booting system on the eMMC of the card. After few boots, (on the same board) the first SD card hanged (several minutes) just after displaying: random: nonblocking pool is initialized The other card continued to work (booting did not hang). A few hours later, I copied several files into a /data directory (.deb files). Trying to boot that second card, it ran in the same blocked status: "random: nonblocking pool is initialized". The first card: same thing. I already waited for an hour once without success. Booting from eMMC does does not hang Any clue on what could avoid this problem ? And what causes it ?
  18. Hello, I tried several times to install debian in eMMC on Lime2, using nand-sata-install, without success, getting with the message : "There are no targets. Please check your drives." Note that on the same board, the official debian image provided by Olimex is working and can be installed in eMMC Checking with "dmesg | grep mmc", I don't find mmcblk1 (only mmcblk0). I tried with 3.4.112 image from armbian (also with 4.5.2). I installed a lot of images on Lime2 in NAND, so I'm not so unexperienced, but I don't understand where I'm wrong (or what I don't know) Thanks for any help ! Regards,
  19. Hello, im new to linux and armbian systems, but im really interested in the topic, recently im working with an a20-Olinuxino-Lime2 , and my goal was to put another OS, for that i followed some tutorials to install a Linux Mate system on the sd card, i configured it to access the internet thought my router but after a point that i changed the kernel , i lost connection to the internet, all my "interfaces" files are the same and i can ping to my router, but i cant ping from my computer to it booting up it gives some errors opening lib modules: systemd-udev(439) could not open builtin file : "/lib/modules/3.4.109-sunxi/modules.builtin.bin" modprob : ERROR: ../libkmod/libkmod.c:514 lookup_builtin_file() could not open builtin file : "/lib/modules/3.4.109-sunxi/modules.builtin.bin" modprob : FATAL : module a20_tp not found in directory lib/modules/3.4.109-sunxi i tried to solve this but im taking too much time to find out.. Thanks
  20. Hello, Me, again !! I used pwm on Lime2 with 3.4.109 and works fine (generating sounds with 2-3 Khz) But, with 3.4.112, I have sound up to 363 Hz. Beginning with 364 Hz ... no sound !! I verified with an oscilloscope and I don't have rectangular waves over 364 Hz . Did anybody experienced such a strange thing ? What can be this 364 limit ? Thanks, Regards,
  21. For some days now I have the board mentioned in the subject, the goal is to have a webserver, git server, and maybe lateron something like a mini-personal-cloud for my family. Yesterday me and my brother finally decided which OS to use - and dd-ed the SD card with the Armbian/Debian Vanilla Jessie Server image (Armbian_5.10_Lime2_Debian_jessie_4.5.2). Some hours later after installing apache2 and trying things out I thought it would be a good idea to do an apt-get upgrade for security reasons before exposing the server to "the world". Unfortunately it was not: The device is not booting any longer after the upgrade. This is the log output of /var/log/apt/term.log (I mounted the SD card at the Linux system on my notebook): It seems the upgrade routine tried to create a new initrd image, but failed: When I look into the /boot/ directory on the SD card, there really is no file "initrd.img-4.5.5-sunxi" (and from my (admittedly not very deep) linux knowledge there *should* be such a file ^^) and also not the old version 4.5.2. Now 2 questions: 1. If my diagnosis is correct - does anyone know how to (re)create the file, when the board itself is not longer booting? Can I compile it on the Linux Mint system currently running on my NB? If yes, how? And is that the only thing to fix, or do I have to do more work to... well, get the system back to work? 2. I thought Debian Jessie has reached state 'stable'. So was this incident bad luck? Or is this supposed to happen more often? Since I guess this will not be the last upgrade I run on the server, I *really* don't want to rush to my families house (where the server will be located) every few weeks, only because an update script has blown up the boot files for the server and have to manually recreate them. Or is there maybe another way to keep the system up-to-date *except* the sensitive kernel/initrd stuff, something like "apt-get safe-upgrade-that-will-not-be-likely-to-touch-the-kernel-and-ruin-my-systems-bootability"? I would be glad if someone could help me with this issue.
  22. I keep my Lime2 updated with apt-get update/apt-get upgrade, but it does not upgrade the u-boot, that is still an old version: U-Boot SPL 2015.07-armbian-sun7i (Oct 11 2015 - 17:17:10) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Because the network speed is not that fast, I suspect this could be solved with a more recent u-boot. How do I update the Lime2 bootloader to a recent u-boot without re-downloading an image and re-installing all my software and data? It looks like there is already a recent u-boot.bin file on the system... # ls -l /usr/lib/nand-sata-install/a20/bootloader/linux/ -rwxr-xr-x 1 root root 152 May 23 22:35 linux.ini -rw-r--r-- 1 root root 309228 May 23 22:35 u-boot.bin ...but what steps are needed to make the Lime 2 use the new bootloader?
  23. are the 1-wire modules built into legacy kernel ( 3.4.xx ) with debian jesse on an Olimex A20 LIME2 ( also the -SOM-4GB ) ? To use 1-Wire for DS18b20 temperature sensors on GPIO5 (from my fex file : gpio_pin_5 = port:PG04<0><default><default><default>) I added [w1_para] w1_used = 1 gpio = 5 to the aw_som_a20.fex file but I don't see any 1-wire modules or drivers loaded. I then used fex2bin ( in windows) to get the .bin file, copied it over and replaced the symlink from script.bin that was pointing to lime2.bin to point to my SSM_som.bin ( I changed the name of the edited one to my board name : SSM_som) Would I need to recompile the kernel to add these modules or can I add them to the current installation ? where are the bin2fex and fex2bin files stored on these images ( i used FTP to get them off, edit, put them back on ) -dd SSM_som_fex.txt
  24. Hello, I'm testing the latest (kernel 4.5) jessie server vanilla on a Olimex Lime2. If a battery is connected to the board and the power plugged in, the board start by itself ! I would like to change this behavior, is there any file to tweak ? Thanks
  25. Hi Igor and all, after running armbian on my A20 lime2 for a long time, I decided to switch to armbian on my A10 lime, too (from jessie with a eewiki-based self-compiled kernel). So far it works as perfect as the A20, but there are two small and funny things with the Armbian_5.00_Lime-a10_Debian_jessie_3.4.110.zip image I used: After login the nice armbian banner stated that my A10 lime is a cubieboard . I have a cubieboard, too. So I double checked... The problem is located in /etc/init.d/armhwinfo, There all "sun4i" boards are simply "Cubieboard". I had to adapt the LED check which is used to detect Lime and Lime2 a bit and added the Lime A10. I checked the LEDs path on my cubian based cubieboard 1 and it was different, so hopefully the LED check correctly detects the Lime A10. During test (restarting service armhwinfo) I saw that the detected ID is appended to /var/run/machine.id. I had a funny banner with Cubieboard and 2 times Lime A10 . Here is what I changed finally: --- armhwinfo.org 2016-02-11 23:58:47.000000000 +0100 +++ armhwinfo 2016-04-07 12:17:16.848138250 +0200 @@ -17,6 +17,8 @@ HARDWARE=$(cat /proc/cpuinfo | grep Hardware | awk '{print $3}') GMAC=$(dmesg | grep "sun6i_gmac") LEDS=$(dmesg |grep "green:ph02:led1") +# a10 lime +LEDS2=$(dmesg |grep "green:ph2:led1") TERMINUS=$(lsusb | grep "1a40:0101") SWITCH=$(dmesg | grep "BCM53125") INTERUPT=$(cat /proc/interrupts | grep "eth0") @@ -55,8 +57,12 @@ ID="Orange H3" fi if [ $HARDWARE = "sun4i" ] || [ $HARDWARE = "Allwinner" ]; then + if [ "$LEDS2" != "" ]; then + ID="Lime A10" + else ID="Cubieboard" fi + fi if [ $HARDWARE = "sun7i" ] || [ $HARDWARE = "Allwinner" ]; then # redistribute irq to dedicated core if [ "$INTERUPT" != "" ] && [ "$CORES" -gt 1 ]; then @@ -115,7 +121,7 @@ if [[ $MACHINE == *M2* ]]; then ID="Banana M2"; fi echo -e "[\e[0;32m ok \x1B[0m] Starting ARM hardware info: $ID" -echo $ID >> /var/run/machine.id +echo $ID > /var/run/machine.id ;; stop|reload|restart|force-reload|status) echo -e "[\e[0;32m ok \x1B[0m] Stopping ARM hardware info ..." The second issue was an (compared to the A20) incredibly high temperature: 72,2. I checked /etc/update-motd.d/30-sysinfo and found out that although it is commented as "only on A20", the a20-tp-hwmon reading is available at the A10 lime, too. Whatever this value is, the correct temperature seems to be at i2c. I got a 37,8 there. So I commented out the A20 temp reading, but this is surely just a quick hack... --- 30-sysinfo.org 2016-02-11 23:58:47.000000000 +0100 +++ 30-sysinfo 2016-04-06 23:06:55.713259579 +0200 @@ -106,9 +106,9 @@ fi # if we are reading from A20 -if [ -d "/sys/devices/platform/a20-tp-hwmon/" ]; then - board_temp=$(cat /sys/devices/platform/a20-tp-hwmon/temp1_input | awk '{printf("%d",$1/1000)}') -fi +#if [ -d "/sys/devices/platform/a20-tp-hwmon/" ]; then +# board_temp=$(cat /sys/devices/platform/a20-tp-hwmon/temp1_input | awk '{printf("%d",$1/1000)}') +#fi # where it should be if [ -d "/sys/devices/virtual/thermal/thermal_zone0/" ]; then Finally I want to send you a big thank you for providing armbian! Bye, wahlm
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines