suchende

  • Content Count

    23
  • Joined

Everything posted by suchende

  1. Works like charm. logfile_odroid_2.log
  2. I used the boot.ini from you, but if I want to define the resolution of the hdmi output I need to know which uboot parameters are possible.
  3. The tv is connected via hdmi, it supports full hd. Personally I do not need the desktop, headless would more useful. HDMI is now working, resolution is wrong, the colors are maybe somehow shifted. Are those options possible: https://github.com/armbian/build/blob/master/config/bootscripts/boot-odroid-c1.ini ?
  4. @Igor A little bit improvement could happen with 5.8 kernel. The armbian build seems to boot up. The hdmi output does not work. cQA5:A;SVN:B72;POC:17F;STS:0;BOOT:0;QA5:A;SVN:B72;POC:17F;STS:0;BOOT:0;INIT:10;BOOT:1;INIT:0;READ:0;CHECK:0;PASS:1; ------------------------------------BID : HKC13C0001 S/N : HKC1CC0349CD6833 0x0000009f check SD_boot_type:0x1 card_type:0x1 Loading U-boot...success. U-boot-00000-g3b0181fd0a(odroidc@3b0181fd) (Jul 17 2018 - 18:49:05) DRAM: 1 GiB relocation Offset is: 2ff20000 MMC: SDCARD: 0, eMMC: 1 IR init is done! vpu clk_level = 3 set vpu clk: 1821500
  5. Booting using the fdt blob at 0x11800000 Loading Kernel Image ... OK OK uboot time: 5690452 us. Using machid 0xf81 from environment faild to get aml_reserved_end address the default relocate ramdisk and fdt address-relocate_addr: 0x20000000 Loading Device Tree to 1fff6000, end 1ffff038 ... OK libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND Starting kernel ... [ 0.183645] lima d00c0000.gpu: IRQ ppmmu2 not found [ 0.183687] lima d00c0000.gpu: IRQ ppmmu3 not found [ 0.187786] lima d00c0000.gpu: IRQ ppmmu4 not found [ 0.1926
  6. I tried this one: Armbian_20.05.3_Aml-s812_bullseye_current_5.7.0-rc4_desktop_20200506.img changed the dtb file location. Nothing happend, the uart print is limit to the first stage bootloader: QA5:A;SVN:B72;POC:17F;STS:0;BOOT:0;INIT:10;BOOT:1;INIT:0;READ:41;USB:3;QA5:A;SVN:B72;POC:17F;STS:0;BOOT:0;INIT:10;BOOT:1;INIT:0;READ:41;USB:3;SERIAL:4;STS:0;BOOT:0;INIT:10;BOOT:1;INIT:0;READ:41;USB:3;SERIAL:4; No HDMI output. The same applies to: LibreELEC-ARM-ALL.arm-9.80-devel-20200430145031-569f834-s8xx.img
  7. I have one and I would test it.
  8. @Tido No, I did not buy the wrong SBC, I just want to try this software. 32bit works so far, but not as a docker container. You need to deploy this directly. I address this as a possible workaround for armbian-config.
  9. Not directly, but maybe mayan-edms should be offered only to arm64 or we need a direct deployment.
  10. The same here on an odroid hc1 docker version Client: Version: 18.09.1 API version: 1.39 Go version: go1.11.6 Git commit: 4c52b90 Built: Tue, 03 Sep 2019 19:59:35 +0200 OS/Arch: linux/arm Experimental: false Server: Engine: Version: 18.09.1 API version: 1.39 (minimum version 1.12) Go version: go1.11.6 Git commit: 4c52b90 Built: Tue Sep 3 17:59:35 2019 OS/Arch: linux/arm Experimental: false docker logs mayan-edms standard_init_linux.go:207: exec user pro
  11. thank you, I give it a try. Currently I switched to the HDD, the amount of written data is enormous, like about 200GB for mysql and 150GB in two hours! Luckily the responsiveness raised a lot.
  12. hey, I'm having some trouble with my ssh connection to an armbian based server. It feels like a heavy lag within the filesystem, sometimes it takes up to 20 seconds to open a file with vim or use cd with tab-completion. But it is not always there, it feels more like some heavy write operation occurs spontaneously. I start digging but I have no clue why this happens. But at least I found the most disk I/O processes which are influxdb and mysql. [16:54|root@odroidhc1 ~]# cat /syscat /sys/fs/ext4/mmcblk0p1/session_write_kbytes 118811040 [16:55|root@odroidhc1 ~]# uptime 1
  13. You could use this: https://partclone.org/ Do you have another system to do this offline? Or do you do this under a running armbian on this hc1 board?
  14. Same here, but with a odroid hc1. the bootloader should be the latest (odroidhc1 4.14.150-odroidxu4). The blue led is permanently on, the systems needs a hard power reset
  15. Thank you very much. I fixed it with a different approach in while. Take all necessary files in /boot and /lib/modules and copy them. Save the mbr and partition table with fdisk to a file, then copy straight with the dd if=/dev/mmcblk0 of=/dev/sdc bs=512 count=8192 and restore afterwards the saved fdisk dump. I forget to mentioned it here: the SoC is the odroid HC1.
  16. the dump from fdisk: p device Boot begin end sectors size Kn typ /dev/mmcblk0p1 8192 30396575 30388384 14,5G 83 Linux F beginn end sectors size 2048 8191 6144 3M 30398464 30703615 305152 149M the raw copy with `dd if=/dev/mmcblk0 of=/dev/sdc skip=2048 seek=2048 bs=512 count=6144 conv=notrunc` fails. Did you meant byte #8192 or sector? the kernel modules are still there.
  17. I made a kernel upgrade which was not successful The kernel does not boot up. Unfortunately armbian does not contain a fallback method to load the old kernel. Therefore I need a way to restore the old kernel. I copied a working boot folder from another sdcard which does not work. What did I miss?
  18. So far Kernel 4.14.20 worked for me. (I need however a way to restore it on to the sdcard)
  19. Usually I compile the kernel on my own because I need apparmor. The current 4.14.29 fails with this log. I tried it again with the Debian stretch next nightly. However this leads to the same: Blue and green LEDs get off and that's it. And a little bit offtopic: How do I fix a broken kernel...
  20. I remember this problem with the cubietruck an the armbian 4.9 kernel. With a self compiled 4.10 kernel it works. The same problem occurs with the odroid hc1. The self compiled 4.14 kernel works flawless.
  21. Try the other USB port. It sounds funny, but at my cubietruck it works at least for a 2.5" external drives.
  22. Hey, I compiled and installed the latest kernel (4.7.3 and uboot 2016-09) but something went wrong. The dtb file was missing. while a manually correct the missing dtb from another run a flashed uboot in the wrong way. Instead of using the drive /dev/sdc I used the partition /dev/sdc1. I read this: https://linux-sunxi.org/Bootable_SD_card#SD_Card_Layoutand with these two commands I should have erased the first 1Mb dd if=/dev/zero of=/dev/sdc1 bs=1k count=1023 seek=1 dd if=u-boot-sunxi-with-spl.bin of=/dev/sdc1 bs=1024 seek=8 (Luckily there is no backup at all ) gpart gives me this:
  23. suchende

    AppArmor

    I tried to used AppArmor under the Linux cubietruck 4.4.1-sunxi #10 SMP Wed Feb 17 17:57:20 CET 2016 armv7l GNU/Linux. But I get a kernel panic after i rebooted the system. Some questions: 1. Did you integrate AppArmor into the kernel? 2. Did you use an alternative mandatory access control? 3. Need I an additional kernel argument in the /boot/boot.cmd other than these "apparmor=1 security=apparmor"? 4. Is there a major diffenrece between your kernel and that from danad.de? Unluckily I was not capable of getting a dump from the kernel panic. If you need it, I would take a photo.