Jump to content

lev2k

Members
  • Posts

    8
  • Joined

  • Last visited

Posts posted by lev2k

  1. 4 hours ago, AndrewDB said:

    I think, and since there are another 14~15GB of eMMC remaining, they don't matter that much.

     

    I don't care about the space, I was just curious for what such a large "empty partition" is needed...;)

    Found this somewhere else from balbes150 (what is a "service part"?):

    Quote

    Primary 700Mb is the service part when using the regular u-boot-2015. If you use u-boot-2018, it will be possible to exploit the full capacity of eMMC for the system (minus the 4MB service in the beginning to u-boot-2018)

     

  2. 37 minutes ago, balbes150 said:

    Do not confuse writing an image to external media (which is usually done on a PC) and creating and restoring a backup. These are completely different tasks.

     

    I'm not confused about that.. ;-)

    I'm talking about to write back/restore an emmc backup, formerly created with "DD".

    I personally, had never issues with "dd" restoring a backup, even if I backup only a part of /dev/mmcblk1. (I usually don't include "unallocated space" in my backup).

     

    Another question: why is there 700MB unallocated space at the beginning of /dev/mmcblk1.

    Is that somehow necessary?

    1372426221_Screenshotgparted.thumb.PNG.49a5073d6cac4c36260e632e84f69d03.PNG

     

  3. 15 minutes ago, balbes150 said:

    Do not use the DD utility to write the image. This often creates problems with the image (there have been many messages from different users about this problem). You need to use special programs to record the image.

     

    What software do you suggest instead of "dd", to write an image back to emmc?

  4. 9 hours ago, Peyton said:

    I'm actually running armbian since 1 hour on usb key (i read since 4.20 emmc isn't supported anymore and don't want to brick it..).

     

    I have the same device and I'm running Armbian (Armbian_5.74_Aml-s905_Ubuntu_bionic_default_4.20.5_desktop_20190304.img) from emmc without any issues.

  5. Quote

     

      On 8/9/2018 at 11:32 AM, lev2k said:

    eventually received my UART Adapter to determine the reason of the non-booting "3.10.108" Kernels

    The "3.10.99" and also the "4.17.0-rc3" Kernels are booting fine.

    The "3.10.108" is always stopping at the same place, independent which dtb.img is used:

     

    Quote

    The answer is similar to the previous one, you need to build another kernel.

     

    Yes I know and thats no big deal, since I`ve already set up the cross-compile environment on my Ubuntu PC, (or even compile the kernel directly on the box which takes only 15-20 minutes).

    I've compared the .108 and .99 .configs from your images, but they are completely different, so no idea where to start...

    I also compiled the mainline Kernel (4.18.rc8) from here https://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git/?h=v4.19/integ

    Boots and works fine so far, but like all mainline Kernel, no HDMI-Out with the S812, thus only useful for server OS.

     

     

     

  6. Hi,

    eventually received my UART Adapter to determine the reason of the non-booting "3.10.108" Kernels

    The "3.10.99" and also the "4.17.0-rc3" Kernels are booting fine.

    The "3.10.108" is always stopping at the same place, independent which dtb.img is used:

    Spoiler

    [    2.996420@0] eth%d: PHY ID 001cc916 at 0 IRQ 0 (stmmac-0:00) active

    [    3.000628@0] eth%d: PHY ID 001cc916 at 1 IRQ POLL (stmmac-0:01) active

    [    3.007473@0] PPP generic driver version 2.4.2

    [    3.011668@0] PPP BSD Compression module registered

    [    3.016422@0] PPP Deflate Compression module registered

    [    3.021597@0] PPP MPPE Compression module registered

    [    3.026513@0] NET: Registered protocol family 24

    [    3.031108@0] usbcore: registered new interface driver asix

    [    3.036643@0] usbcore: registered new interface driver ax88179_178a

    [    3.042828@0] usbcore: registered new interface driver cdc_ether

    [    3.048789@0] usbcore: registered new interface driver dm9601

    [    3.054480@0] usbcore: registered new interface driver net1080

    [    3.060244@0] usbcore: registered new interface driver cdc_subset

    [    3.066293@0] usbcore: registered new interface driver zaurus

    [    3.071991@0] usbcore: registered new interface driver cdc_ncm

    [    3.077765@0] usbcore: registered new interface driver qf9700

    [    3.083457@0] usbcore: registered new interface driver sr9600

    [    3.089227@0] usbcore: registered new interface driver usb-storage

    [    3.095402@0] mousedev: PS/2 mouse device common for all mice

    [    3.101100@0] usbcore: registered new interface driver xpad

    [    3.106495@0] usbcore: registered new interface driver usb_acecad

    [    3.112513@0] usbcore: registered new interface driver aiptek

    [    3.118216@0] usbcore: registered new interface driver gtco

    [    3.123744@0] usbcore: registered new interface driver hanwang

    [    3.129505@0] usbcore: registered new interface driver kbtab

    [    3.135121@0] usbcore: registered new interface driver wacom

    [    3.140755@0] i2c /dev entries driver

    [    3.144681@0] device-mapper: uevent: version 1.0.3

    [    3.149223@0] device-mapper: ioctl: 4.24.0-ioctl (2013-01-15) initialised: dm-devel@redhat.com

    [    3.157957@0] hidraw: raw HID

     

    Here is the full log from the UART Adapter:

    https://pastebin.com/4vjB4HBD

     

    I'm willing to help, if I can.

    I have access to an Ubuntu 16.04 PC, so I'm able to modify the dtb/dts files as well as the uInitrd (if needed).

    If absolutely necessary, I could setup a build-environment and try to build a custom kernel...

     

  7. Hi folks,

    I'm currently running @150Balbes "Armbian_5.27_S812_Ubuntu_xenial_3.10.99" on a S812, but with some minor issues.

    • Ethernet only 100Mbits (Realtek 8211F).
    • Kernels newer than 3.10.99 won't boot (but will try to determine why, when I get my UART Adpter.)

    So after all, I'm thinking to replace this box, with a more current one.

    Purpose of this box: running an "Emby-Server" with external HDDs and probably "Pi-Hole".

    Which box is recommendable for these purposes?

    thanks in advance

     

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines