segv

  • Content Count

    21
  • Joined

  • Last visited

Posts posted by segv

  1. Thank you balbes150, mcb777 and dbsharpe for your help.

     

    Short version:

    My X96 Max is now happily running the 5.9.0 kernel.

     

    Long version:

    I still had the SD card that I used for my initial Armbian tests.

    It had Armbian_20.05.4_Arm-64_bullseye_current_5.7.0-rc5_20200516.img

    I changed the dtb in uEnv.txt from meson-g12a-x96-max-no-cvbs.dtb (which no longer exists) to meson-g12a-x96-max.dtb

    I booted the SD card and did an apt update/upgrade directly from kernel 5.7.0-rc5 to 5.9.0

    It rebooted fine.

    I then did a dd of the BOOT partition from the SD card to my SSD.

    My box then rebooted correctly from the SSD.

     

    Conclusion:

    The main problem was that the dtb in the old example uEnv.txt is no longer included in the new dtb directory.

  2. 10 hours ago, balbes150 said:

    You didn't specify this "little thing", but it fundamentally changes the behavior of the entire startup system.

     

    I just uncommented the line with meson-g12a-x96-max-no-cvbs.dtb in the example uEnv.txt file.

    I chose this because it was already present and it matches my needs: I have an X96 Max and I want HDMI not CVBS.

     

    Unfortunately this dtb is no longer present in the dtb directory which probably explains the failure.

    I changed to meson-g12a-x96-max.dtb and it now at least tries to boot.

    Unfortunately it now says "LABEL=ROOTFS does not exist" :-(

    I don't see why it would have disappeared but I shall try to debug this tomorrow.

     

    Edit: The label does exist.

    I am wondering whether USB is broken in 5.9.0 as I had a similar symptom a long time ago before USB was operational.

    Or maybe there is just a missing module.

  3. 11 hours ago, balbes150 said:

    What settings are set ? What media is used ?

     

    As I wrote 

     

    12 hours ago, segv said:

    I have been running Debian Bullseye on an X96 Max (S905X2) for several months and it has proved very stable.

    It boots from an SSD in an external USB3 enclosure.

    Kernel updates up to 5.7.16 have gone smoothly.

     

    Unfortunately today an "apt upgrade" seems to have attempted to install the 5.9.0 kernel and the box no longer reboots.

    There is nothing on the display and I can no longer ssh into the box.

     

    Concerning the media: to be more complete the SSD is a QMOX 240 GB and the enclosure is a Sabrent EC-UASP and, as I implied, it is running on the USB3 port.

     

    Concerning the settings: nothing concerning the boot process has changed (except for automatic modifications by "apt upgrade") since I installed Armbian Bullseye on the 16th of May with the appropriate DTB for my box.

    It had been running perfectly for five months and I have previously had "apt upgrade" kernel updates without problems.

    I agree with mcb777 that it was the latest linux-image-current-arm-64 package with kernel 5.9.0 which broke it.

    Looking at the contents of the BOOT partition it seems that much has been changed not only by this "apt upgrade" but also by previous ones.

     

    I don't want to reinstall everything so I shall try to fix the BOOT partition and if this fails I shall try overwriting it with the BOOT partition from a recent version.

    However any pointers to the likely cause would be most welcome ;-)

     

    I am convinced that there is a real problem with this deb package which must be corrected :-(

     

  4. On 10/14/2020 at 1:26 PM, balbes150 said:

    Ver 20201014 kernel 5.9

     

    Pay attention. This is the latest version of ArmbianTV images, where there are files for AML. The following images will not contain this data.

     

    First a big thank you to balbes150 for his excellent work.

    I have been running Debian Bullseye on an X96 Max (S905X2) for several months and it has proved very stable.

    It boots from an SSD in an external USB3 enclosure.

    Kernel updates up to 5.7.16 have gone smoothly.

     

    Unfortunately today an "apt upgrade" seems to have attempted to install the 5.9.0 kernel and the box no longer reboots.

    There is nothing on the display and I can no longer ssh into the box.

    However, rather surprisingly to me, the front panel display counts up the minutes.

     

    I haven't tried to debug the problem.

    Does anyone have the same problem or, even better, a solution?

    TIA

  5. On 12/6/2018 at 2:46 PM, Liam Dolman said:

    Ethernet not working although it is showing on "ifconfig -a" with a mac after switching to nightly. anyone have any ideas?

     

    I think you get these symptoms if the Ethernet interface declared in the device tree doesn't match that used on your device (100Mbps vs 1Gbps).

  6. 17 hours ago, martos said:

    Don't put the USB stick in the USB 3 ( blue ) : it 's not work in this position.

    when boot in usb stick:

    enable_dtoverlay eth1 ethernet@ff550000 okay

    after

    ifconfig eth1 up && dhclient

    test with ifconfig , now you see interface eth1 with your dhcp propertie ...

     

    Thank you, this confirms what I wrote in my first post.

    However the solutions I proposed enable eth1 and DHCP automatically and avoid having to issue commands manually at each reboot.

  7. The 0.6.x images will not boot from a micro-SD card.

    If you want to run 0.6.x from a micro-SD card you need to take partitions 1 to 5 from 0.5.15 and only partitions 6 and 7 from 0.6.x.

    However I do not recommend this as I found that the micro-SD card soon gets corrupted and will no longer boot. See my remarks in my first post.

    However it is possible that whatever caused this data corruption has been corrected in later 0.6.x images.

  8. On 7/18/2018 at 11:22 AM, mdel said:

    Anyways, could you elaborate on that "enable_dtoverlay" script you are using, i do see a dtoverlay tool implemented on rpi images but can't find where it was imported through a script, thx.

    i installed armbian (4.4.138) on my z28 pro and would very much like to use that to try and troubleshoot the missing bluetooth device.

     

    I am away on holiday at the moment but I shall post ayufan's enable_dtoverlay script when I return.

    However IIRC it requires a kernel with device tree overlays enabled.

  9. On 14/04/2018 at 6:34 AM, psychedup74 said:

    Just curious if you got your eth1 working. Are you using the DAC board w/ ethernet jack that pine64 sells?

     

    I don't have a real ROCK64, just a Scishion V88 Piano so the ROCK64 DAC board isn't relevant for me.

     

    To enable eth1 during each reboot add the following command to /etc/rc.local

    enable_dtoverlay eth1 ethernet@ff550000 okay

     

    Alternatively you can do this manually each time from a shell with sudo.

     

    In both cases you will first need to install the device-tree-compiler package.

     

    You may also have to configure DHCP on eth1 by executing the following commands in a shell as root (sudo -s):-

    # cd /etc/network/interfaces.d

    # sed s/eth0/eth1/ eth0 > eth1

    # reboot

    (For some unknown reason "service networking restart" wasn't always sufficient for me.)

  10. On 11/04/2018 at 5:33 PM, rob0809 said:

    Thank you Segv for the info.  Are you running the Piano headless?  I'd like to run Kodi on the box and also have it running a NFS and SMB server as well.  Just curious if audio and video are working under Armbian.

     

    I have mainly been running it headless recently.

    (Note that the minimal versions also have a console display on HDMI which I sometimes use.)

     

    I have tried the Mate desktop from time to time but I have generally had some stability problems with it.

     

    Concerning video:  I have only tried YouTube videos which are fluid but with some freezes.

    The freezes were fairly frequent on some versions but I think recent versions may be better.

     

    I have never tried audio: my HDMI monitor doesn't have audio and I haven't tried the S/PDIF.

     

    I am also very interested in running Kodi but I haven't tried it.

    Indeed my ultimate aim is to use it as a general purpose TV box with a Ubuntu desktop including Kodi and Tvheadend for DVB.

     

     

  11. Starting from 0.6.27 ayufan has disabled eth1 in his Rock64 images, so internal Ethernet no longer works on the V88 Piano.

     

    Thanks to Igor and Xalius I found that this command will re-enable it on the running kernel: "sudo enable_dtoverlay eth1 ethernet@ff550000 okay"

    Update:

    I think the best solution is to add "enable_dtoverlay eth1 ethernet@ff550000 okay" to /etc/rc.local

    I also added "enable_dtoverlay eth0 ethernet@ff540000 disabled" to disable the Gigabit interface which is not used on these boxes.

     

    Before upgrading to >= 0.6.27 do a "sudo apt-get install device-tree-compiler" while you still have Ethernet as the enable_dtoverlay script needs it.

  12. Thank you Igor: how stupid of me not to look in the commit messages and find that eth1 had simply been disabled in the DT.

    Thank you also Xalius for the DT overlay tip: it is neat to be able to patch the DT in the running kernel.

     

    For other users the following command re-enables eth1 at run time:

    sudo enable_dtoverlay eth1 ethernet@ff550000 okay

  13. I run these Rock64 images on a Scishion V88 Piano which has eth1 (100 Mbps) but no eth0 (1000 Mbps).

    Unfortunately the 0.6.27 image disables eth1 and therefore I no longer have Ethernet on my box.

    (It worked fine on earlier releases.)

    How do I re-enable eth1 on my box?

    And, less importantly, how do I disable eth0?

     

    Thanks in advance.

  14. On 07/02/2018 at 10:56 PM, segv said:

    Sorry, strictly this post is again OT as it also concerns the Scishion V88 Piano (another RK3328 TV box).

    However there are already many posts concerning this box and others not included in the topic's title.

    While this post is specific to this box, I think much of my previous post is relevant to the Z28 as well.

    Should I start a new topic dedicated to this box?

    Alternatively can the title of this topic be enlarged to cover all RK3328 TV boxes?

     

    Nobody answered these questions :(

    However I felt that I should not continue to hijack this topic so I have started a new one:

     

  15. Ayufan’s Armbian on a V88 Piano or V88 Mini III

     

    These two TV boxes seem to be electrically identical except that the V88 Mini III has 2 GB RAM and 8 GB ROM whereas the V88 Piano has 4 GB RAM and 16 GB ROM.

    They use the same PCB as can be seen from the photos in these FreakTab topics:-
    - http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/681869-scishion-v88-piano-tv-box-rk3328-4gb-ram-16gb-rom-android-7-1-usb-3-0-fast-lan
    - http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/663248-scishion-v88-mini-iii-tv-box-rk3328-2-8gb-2-4-wifi-fast-lan

     

    I do not have a V88 Mini III to test but I believe that my results for the V88 Piano should also be relevant to it.

     

    N.B. many sites claim that the V88 Piano has Gigabit Ethernet (1000 Mbps). It does not: it only has Fast Ethernet (100 Mbps) like the V88 Mini III.

     

    One nice thing about these TV boxes is that, unlike many others, they will boot easily from a micro-SD card.
    Just insert the card and power on :)

     

    My aim was to have Ubuntu running with all version-specific partitions (boot and root) on a USB drive.
    I wanted to keep Android in the internal eMMC so that I could dual-boot by just inserting or removing the micro-SD card.

     

    I wanted to have the root partition on a USB stick for three reasons:
    1) A good USB stick is faster than a micro-SD card.
    2) This avoids the system writing repeatedly to the micro-SD card because, if the root partition is on the micro-SD card, after a while it gets corrupted and will no longer boot. This happened to me with both a cheap Ansonchina card and also with a Kingston card. Maybe the write timings in the micro-SD card driver are incorrect.
    3) Whilst experimenting on Amlogic boxes I have fried two big micro-SD cards. I have read that others have fried cards on Rockchip boxes. Moving the rootfs to a USB stick enables me to use a smaller and cheaper card.
    (I suspect that they were destroyed by over-voltage due to a badly programmed regulator. With a 5 V USB stick and a 5 V PSU there should be no risk as I don’t think the regulators used can step up the voltage.)

     

    I also wanted the boot partition to be on the USB stick so that I could have several GNU/Linux distributions on different USB sticks and boot with the same unmodified micro-SD card containing just the boot loaders.

     

    I have deliberately avoided the necessity to have a Linux (or even Windows) PC.

     

    N.B. the Ubuntu system will not (yet) have working Wi-Fi.

     

    You will need:-
    - a rooted V88 Piano (mine was sold pre-rooted)
    - a micro-SD card: mine was 8 GB but 4 GB should suffice
    - a USB Flash Drive: I have used both 32 GB and 8 GB but 4 GB may suffice for a fairly minimal system
    - a USB keyboard (and mouse if installing a desktop): I used a wireless mini-keyboard/mouse
    - a wired (RJ45) Ethernet connection with DHCP and Internet access

    - an HDMI display

     

    WARNING: before using a /dev/ or /dev/block device verify that you are using the correct one, using dmesg for instance. Otherwise you could overwrite precious data.
    However if you remove all additional USB drives the names below should be correct.

     

    The login is rock64 with password rock64 which is also required for sudo.

     

    First step – install Ayfan’s Ubuntu Xenial Minimal 0.5.15 on a micro-SD card and prepare 0.6.25 on a USB stick.

     

    Boot Android.

     

    I installed and used Google Chrome for the following downloads because, with the stock Lightning browser, I couldn’t see when the download had finished.
    (The busybox wget can't be used because it doesn’t support https.)

     

    Open https://github.com/ayufan-rock64/linux-build/releases/tag/0.5.15 in the browser.
    Download xenial-minimal-rock64-0.5.15-136-arm64.img.xz

     

    If you wish to pass directly to Ubuntu Bionic you could use the Bionic 0.6.25 image instead of Xenial below.
    However this may make it more difficult to update U-Boot later as I think a Xenial environment is expected to compile it.

    Open https://github.com/ayufan-rock64/linux-build/releases/tag/0.6.25 in the browser.
    Download xenial-minimal-rock64-0.6.25-193-arm64.img.xz


    Insert the micro-SD card and the USB stick.

    N.B. all existing files on both will be destroyed.

    You will be asked how to use the USB stick: choose "removable storage" and "cancel" if asked whether to format it.

     

    Execute the following actions and commands (in the text following the $ or #).

     

    Install and start ConnectBot.

     

    Open a local shell.

    Become root.
    $ su

     

    Enter the directory where browsers save downloaded files.
    # cd /sdcard/Download

     

    Decompress the files.
    # busybox xz -d xenial-minimal-rock64-0.5.15-136-arm64.img.xz
    # busybox xz -d xenial-minimal-rock64-0.6.25-193-arm64.img.xz

     

    Write the 0.6.25 image to the USB stick.
    # dd if=xenial-minimal-rock64-0.6.25-193-arm64.img of=/dev/block/sda bs=1048576

     

    Write the 0.5.15 image to the micro-SD card.
    # dd if=xenial-minimal-rock64-0.5.15-136-arm64.img of=/dev/block/mmcblk1 bs=1048576

     

    Ensure everything is written.
    # sync

     

    Power off the box.


    Second step – boot Ayfan’s Ubuntu Xenial Minimal 0.5.15 and prepare the switch to 0.6.25 on the USB stick.

     

    Insert the micro-SD card.
    Boot and login (rock64/rock64).

     

    Become root.
    $ sudo -s

     

    Remove partitions 6 (boot) and 7 (root) from the micro-SD card so that U-Boot and Linux will use the ones on the USB stick next time.
    Luckily this only deletes their entries so Linux can continue to use them until they are unmounted.
    Reply "Yes" and "Ignore" to the warnings.
    # parted /dev/mmcblk1
    rm 6
    rm 7
    q

     

    # poweroff


    Third step - boot Ayfan’s Ubuntu Xenial Minimal 0.6.25 from the boot and root partitions on the USB stick and prepare to update to a recent version.

     

    Insert the USB stick in the middle USB slot and insert the micro-SD card.
    Boot and login.
    $ sudo -s

     

    This DHCP configuration will be necessary for Bionic.
    # cd /etc/network/interfaces.d
    # sed s/eth0/eth1/ eth0 > eth1

     

    At the time of writing there are only pre-release versions of 0.6.x but Ayufan has promised an official release shortly after the official release of Bionic due on 24th April.
    If, in addition to Ubuntu updates,  you want to update to Auyufan's pre-release versions with an added risk of instability then:
    # vi /etc/apt/sources.list.d/ayufan-rock64.list
    Uncomment the last line

     

    # apt update

     

    The following lines are necessary if you update to a more recent Ayufan version which will disable eth1:

    This is needed to re-enable eth1:
    # apt install device-tree-compiler

    Make rc.local enable eth1 which is disabled in recent versions and disable eth0 which is not used on the V88 Piano:

    # vi /etc/rc.local
    Add these two lines just before the last line (exit 0):
    enable_dtoverlay eth1 ethernet@ff550000 okay
    enable_dtoverlay eth0 ethernet@ff540000 disabled

     

    # apt dist-upgrade -y

     

    If you want a Mate desktop you can:
    # install_desktop.sh mate

     

    This gave me an error which I corrected with:
    # apt -f install

     

    If you wish you can also upgrade from Xenial to Bionic with do-release-upgrade.

     

    # reboot

     

    You should now be running an up-to-date version with the boot and root partitions on the USB stick.


    The next step will be to compile and install a more recent U-Boot supporting the USB 3.0 port correctly.

    To be continued...


    The procedure above may seem convoluted so here are some additional explanations.

    0.5.15 is used for its boot loaders as it is the latest version which will boot directly from a micro-SD card. Unfortunately it does not have working Ethernet and its U-Boot will not load correctly from the USB 3.0 slot.
    0.6.25 is used because it has working Ethernet to install device-tree-compiler which is needed to re-enable eth1 on recent versions.

  16. In several places, including this topic, it is claimed that the Scishion V88 Piano has Gigabit Ethernet (1000 Mbps).

    I am pretty sure that mine only has Fast Ethernet (100 Mbps).

    Does anyone have one with confirmed GbE?

    (Maybe there are two versions.)

     

    I have not opened the box but several things indicate that it doesn't have GbE:

    - it connects to my GbE switch at only 100 Mbps

    - photos of the PCB on FreakTab show a TRC1102NL which is a 10/100 Mbps transformer

    - AIUI GbE requires an external chip (e.g. RTL8211F) and I can see no sign of one in the boot logs

    - internal Ethernet doesn't work with DTB's for boards with GbE.

     

    Sorry, strictly this post is again OT as it also concerns the Scishion V88 Piano (another RK3328 TV box).

    However there are already many posts concerning this box and others not included in the topic's title.

    While this post is specific to this box, I think much of my previous post is relevant to the Z28 as well.

    Should I start a new topic dedicated to this box?

    Alternatively can the title of this topic be enlarged to cover all RK3328 TV boxes?

  17. Hi,

     

    I have received my SCISHION V88 Piano and I can confirm that it boots to a Ubuntu Mate desktop from a micro SD-card with the image in the first post of this topic.

    Like rob0809 I did nothing except insert the micro SD-card and power on :)

    Unfortunately after running for a few minutes there were some I/O errors which I must investigate but this is perhaps due to my cheap (Ansonchina) SD-card.

     

    I shall try other images and report back later.

     

    Updates:

    I tried this image:

    https://github.com/ayufan-rock64/linux-build/releases/download/0.5.15/xenial-mate-rock64-0.5.15-136-arm64.img.xz

    and it also booted directly but still with I/O errors.

    I replaced the Ansonchina 8GB SD-card with a Kingston 8GB one and there were no more I/O errors :)

     

    I tried the following images which also booted directly from the Kingston SD-card with no intervention:
    http://dietpi.com/downloads/images/DietPi_Rock64-ARMv8-Stretch.7z

    https://github.com/Raybuntu/LibreELEC.tv/releases/download/rb-leia23/LibreELEC-rock64.arm-rb-leia23.img.gz

    https://github.com/ayufan-rock64/linux-build/releases/download/0.5.15/xenial-i3-rock64-0.5.15-136-arm64.img.xz

     

    Most of these images require an external USB Ethernet adapter (internal Ethernet and WiFi don't seem to be supported).

    They also run much more slowly than I had expected. Unfortunately I don't think that this is just due to a lack of hardware graphics acceleration :( 

    But this is just a start and at least they do run :)

     

    Later update:

    I found an easy hack to greatly speed up simple operations not involving heavy video or graphics.

    (Due to the lack of hardware acceleration, YouTube videos, for example, still play frame by frame.)

    I copied exactly the same disk image to both a micro SD-card and to a USB 3.0 storage device.

    I modified the label on the root partition of the SD-card so that it would use the USB disk as the rootfs instead.

    On most of these images the rootfs is labelled linux-root on partition 7.

    I used gparted to change the SD-card's partition 7 label to linux-rootX so that it would pick up the partition on the USB drive instead.

     

    I also used parted to correct for the size of both the devices and to increase the size of the root partition on the USB drive. However this is not strictly necessary.

    As a stability test and a realistic benchmark, I compiled natively the recent mainline v4.15 Linux kernel: "make defconfig && make -j 4 Image" finished successfully in slightly under 100 minutes.

    This is not too bad for a box costing about $40.

     

    Even later update:

    The best Ubuntu image that I have found is this one:

    https://dl.armbian.com/rock64/Ubuntu_xenial_default_nightly.7z

    This currently redirects to:

    https://dl.armbian.com/rock64/nightly/Armbian_5.34.171121_Rock64_Ubuntu_xenial_default_4.4.77.7z

    There is only one single partition so I had to:

    '- copy the image to a USB storage device

    - resize the partition

    - add the label linux-root

    - copy the appropriate files from the boot directory of this partition to replace the dtb, Image and initrd.img files on the boot partition of the SD-card I used previously

    - ensure that there is no partition labeled linux-root on the SD-card

    - after booting I installed ubuntu-mate-desktop but this is obviously not mandatory

    The advantages of this image are:

    - it will find the linux-root partition even if the USB storage device is on a hub (otherwise the USB drive monopolizes the USB 3.0 port)

    - YouTube video (nearly) works so there must be some hardware acceleration

    Unfortunately the video freezes from time to time. This doesn't seem to be due to a slow Internet connection.

    With this image the compilation time for the same kernel dropped to 72 minutes.

     

    I also tried this image but it did not seem to boot (at least there was only a blank screen on HDMI).

    https://github.com/ayufan-rock64/linux-build/releases/download/0.6.19/bionic-minimal-rock64-0.6.19-181-arm64.img.xz

    Maybe it is headless so I shall try again to ssh into it.

    (Or to login via a serial console but I have not yet needed to open the case.)

     

    Cheers,

    Chris