Christian

Members
  • Content Count

    11
  • Joined

  • Last visited

About Christian

  • Rank
    Member

Recent Profile Visitors

557 profile views
  1. How to update to nightly versions/kernels with mainline? I have the latest Armbian (5.25) installed with mainline kernel (4.9.4). uname says: Linux orangepipc 4.9.4-sun8i #14 SMP Thu Feb 2 02:03:26 CET 2017 armv7l armv7l armv7l GNU/Linux There are nightlys with 4.10 kernel. How do I upgrade to them? If I try to install the kernel manually, root@orangepipc:~# apt-get -s install linux-image-dev-sun8i Reading package lists... Done Building dependency tree Reading state information... Done linux-image-dev-sun8i is already the newest version (5.25). 0 upgraded, 0 newly installed, 0 to remove and 26 not upgraded. it says I have the newest one. With apt-get -s upgrade I get: The following packages will be upgraded: base-files bind9-host console-setup console-setup-linux dnsutils keyboard-configuration klibc-utils libbind9-140 libdns-export162 libdns162 libgssapi-krb5-2 libhogweed4 libisc-export160 libisc160 libisccc140 libisccfg140 libk5crypto3 libklibc libkrb5-3 libkrb5support0 liblwres141 libnettle6 libssh2-1 linux-firmware linux-libc-dev sudo Would be the new kernel in "linux-firmware"? The script mentioned earlier wget -q -O - http://upgrade.armbian.com | bash has no option for orangepipc Thanks in advance!
  2. Thanks! So "x.y." means "future" -- now I know for the future I wish you guys success and wait for the week, it's not that urgent.
  3. On http://docs.armbian.com/Release_Changelog/I see am Armbian 5.25 with many improvements But on https://dl.armbian.com/orangepipc/the files seem to be 5.24 and older, even the nightly versions. I am interested in the sunxi mainline version with kernel 4.9. Thanks in advance! Christian
  4. As without serial console, I tried to integrate load mmc ... into the Armbian boot script. Didn't work also with ext4load or putting it in separate lines but ... with the information of your posting how to access partitions I just copied the contents of the Openelec boot script into the Armbian one: setenv bootm_boot_mode sec setenv bootargs console=ttyS0,115200 boot=/dev/mmcblk0p3 disk=/dev/mmcblk0p2 consoleblank=0 fatload mmc 0:3 0x43000000 script.bin fatload mmc 0:3 0x42000000 KERNEL bootm 0x42000000 And this did work :-) :-) :-) Thanks for providing the "hint"! I had this nearly before, but with those two files on the Armbian partition and it didn't work. I'll write a how-to, as I guess others are interested in this "dual boot" also.
  5. I use the u-boot of "your" Openelec. I created a new ext4 partition, copied Armbian there and the boot files additionally to the root folder of the FAT partion. Before I tried to add Openelec to Armbian by creating a new partition for /storage and modified 'boot.scr' as described in http://forum.armbian.com/index.php/topic/2042-boot-armbian-vanilla-kernel-472-from-fat-boot-partition/#entry15642 In that case I use the Armbian u-boot, but then Armbian started, but Openelec did not. Maybe it's because "your" 'boot.scr' contains absolute addresses, which are not compatible with Armbian's u-boot? Would ext4load mmc 0 ${fdt_addr_r} /boot/script.bin ext4load mmc 0 ${kernel_addr_r} /boot/KERNEL bootz ${kernel_addr_r} work and have SYSTEM in both the /boot and the root folder of the ext4 partition. Update: I tried it and it didn't work :-( So I assume Openelec needs to start from a FAT partition. Which MBR records do I have to copy (and then replace) to get the Armbian u-boot? I hope boot.scr of Openelec works with this new u-boot. Thanks for your great work and support!
  6. I tried to add the the Openelec files to the ext4 partition, but this didn't work either. I had the following 'boot.scr': gpio set PL10 gpio set PG11 setenv machid 1029 setenv bootm_boot_mode nonsec if ext4load mmc 0 0x00000000 /boot/.verbose then setenv verbosity 7 else setenv verbosity 1 fi if ext4load mmc 0 0x00000000 /boot/.next then # sunxi mainline kernel #------------------------------------------------------------------------------------------ setenv bootargs "console=tty1 root=/dev/mmcblk0p1 rootwait rootfstype=ext4 cgroup_enable=memory swapaccount=1 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 panic=10 consoleblank=0 enforcing=0 loglevel=${verbosity}" ext4load mmc 0 ${fdt_addr_r} /boot/dtb/${fdtfile} || fatload mmc 0 ${fdt_addr_r} /dtb/${fdtfile} || ext4load mmc 0 ${fdt_addr_r} /dtb/${fdtfile} ext4load mmc 0 ${ramdisk_addr_r} /boot/uInitrd || fatload mmc 0 ${ramdisk_addr_r} uInitrd || ext4load mmc 0 ${ramdisk_addr_r} uInitrd || setenv ramdisk_addr_r "-" ext4load mmc 0 ${kernel_addr_r} /boot/zImage || fatload mmc 0 ${kernel_addr_r} zImage || ext4load mmc 0 ${kernel_addr_r} zImage bootz ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r} #------------------------------------------------------------------------------------------ else # openelec #------------------------------------------------------------------------------------------ setenv bootargs console=ttyS0,115200 boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2 consoleblank=0 ext4load mmc 0 0x43000000 /boot/script.bin ext4load mmc 0 0x42000000 KERNEL bootm 0x42000000 I copied the command in the second part from the Openelec 'boot.scr'
  7. Well, I don't have a serial console and HDMI doesn't work :-D But booting get's very far, so I assume it's not a bootloader problem except that maybe I have to change another parameter. I have attached all relevant logs -- I have deleted all but the last boot. The times are "jumping", but I guess I tell you nothing new here. Maybe it's just a strange ssh problem. Is it possible to enable telnet? armbian-booted-from-fat.zip
  8. I want to have a "dual boot" system with Openelec for video and Armbian for the rest :-) The boot files are named different except 'boot.scr'. So the idea is to rename it, so the right one is used and then do a reboot. Not the PC dual boot with a menu, but good enough for me :-D So I copied the files from the /boot folder to an existing FAT partition and copied the rest to a newly created ext4 partition (mmcblk0p3). I modified 'boot.scr' to this: gpio set PL10 gpio set PG11 setenv machid 1029 setenv bootm_boot_mode nonsec if fatload mmc 0 0x00000000 /boot/.verbose then setenv verbosity 7 else setenv verbosity 1 fi setenv bootargs "console=tty1 root=/dev/mmcblk0p3 rootwait rootfstype=ext4 cgroup_enable=memory swapaccount=1 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_no_mali_mem_reserve sunxi_fb_mem_reserve=16 panic=10 consoleblank=0 enforcing=0 loglevel=${verbosity}" fatload mmc 0 ${fdt_addr_r} /dtb/${fdtfile} || ext4load mmc 0 ${fdt_addr_r} /boot/dtb/${fdtfile} fatload mmc 0 ${ramdisk_addr_r} uInitrd || ext4load mmc 0 ${ramdisk_addr_r} /boot/uInitrd || setenv ramdisk_addr_r "-" fatload mmc 0 ${kernel_addr_r} zImage || ext4load mmc 0 ${kernel_addr_r} /boot/zImage bootz ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r} It's removing/replacing 'ext4load' from the original at some places and changing the partition where root resides. It doesn't boot. What do I do wrong? Or does the boot files have to be on a ext4 partition. How else could I create a "dual boot" withe Openelec? Thanks! Christian
  9. This URL also failed for me, but someone else posted a link to an image that works perfect for me on my Opi PC : http://forum.armbian.com/index.php/topic/1914-system-with-vanilla-kernel-available-for-opi-pc-but-not-pc/#entry15085
  10. Exaclty the same hardware and use case Only that I want to use tvheadend 4.2 (for the moment the beta versions of it). Thanks for sharing! I downloaded it. How do I install it? With dd or similar programs? I renamed it to .img and could see with 7zip that it is only one partition including /boot on it. Normally there are 2 partitions in the image files: a boot partition with FAT and a system partition with ext4.
  11. According to http://www.armbian.com/orange-pi-pc-plus/ If I understand correctly, the only difference is that PC+ has additional eMMC and WiFi. So a system with vanilla kernel for Opi PC+ should also work on the PC. Or are there other hardware differences? The page states: "serial console only, no HDMI." Does this vanilla system support Ethernet yet, so one can login via ssh after installation? My targeted use would be a tvheadend server (without local video for the moment).