Jump to content

amirul

Members
  • Posts

    394
  • Joined

  • Last visited

Posts posted by amirul

  1. 1 hour ago, balbes150 said:

    This setting applies only to u-boot-2018.

    After installing u-boot-2018 in eMMC, there are no other options to run other than using "extlinux.conf " or build a special script "boot.scr" .

    I see, thanks for clearing that up. There is only s905x and s912 uboot.img files. What about s905?

  2. 19 hours ago, balbes150 said:

    Good news. I tried installing the latest version of Armbian on VIM with the new u-boot-2018 in eMMC. Everything works. If write a last option Armbian (20180925) to the USB drive, the system starts from USB stick. That is, now you can have a new u-boot-2018 in eMMC and run any test system from USB media (Armbian Libreelec OpenSYSE etc ). Pay attention. The steps to configure the system to run from external media using u-boot-2018 have changed. Now you do NOT NEED to manually copy the dtb. You need to make changes to the text file “/extlinux/extlinux.conf”  . You must change the string with the name of the dtb you are using. The list of available files (name) can be seen in the "/dtb" directory. By default, the settings specify dtb for VIM1 (S905X). To use the new images with VIM2 (S912), you must correct the file name dtb for VIM2.

    To install in the eMMC the latest version Armbian changed steps. Now you need to run only one installation script. To install with the old version of u-boot-2015, you need to run the script “/root/install.sh”. To install in the eMMC with uboot-2018, you need to first rename one of the existing files on the media "Sxxx-uboot.img" to “uboot.img” (select the option for your model). After renaming the file “uboot.img”, to install Armbian in eMMC, you need to run the script “/root/install-2018.sh”.

     

     

    Pay attention. All tests of the new u-boot-2018 are performed on Khadas VIM and VIM2. I don't know how it will work on other models. Therefore installation in eMMC with replacement of regular u-boot on u-boot-2018, you do your own risk. I take no responsibility for your choices.

    Burned the bionic verison to usbdrive. The extlinux.conf way didn't boot but the good old dtb.img way worked. I'm using the boxes as cheap X terminals and so far they're working great. At under $100 per seat, what's not to like, keeps getting better and better with each new image.

     

    BTW love the videos that come with the images :-)

  3. Hi everyone,

    First of all thanks for the awesome builds. Had success with the S805 and S905 images with framebuffer display. Now trying the hardware accelerated builds.

    So far..

    Armbian_5.59_Aml-s9xxx_Ubuntu_bionic_default_4.18.0_desktop_20180829.img

    Hardware: Mini MX

    dtb.img from meson-gxbb-p200.dtb did not finish booting (LABEL=ROOTFS does not exist)error -110 whilst initialising SD card . In previous images gxbb-p200.dtb used to work

    Boot screen was very garbled. I can provide images if anyone is interested.

    Got to desktop using meson-gxbb-nexbox-a95x.dtb, although screen was garbled

     

    Keep up the great work! Really appreciate it

     

    UPDATE: got rid of the garbled screen :-) added video=1280x720 to the end of uEnv.ini, then boot messages became readable.

    lightdm login screen still garbled. Still able to log into desktop, then did xrandr -s 1280x720 everything cleared up. Sweet!

     

    Now to see why wifi & ethernet is not working...

     

    UPDATE: able to boot to desktop with meson-gxbb-p200.dtb - only with usb & side usb port. Boot process takes a bit longer though. Wifi & ethernet still not working.

     

    TX3 Mini (meson-gxl-s905w-tx3-mini.dtb, using sdcard or usb) boots to desktop (although slow to get login screen).

    eth0 working, wifi not (kern.log message: Direct firmware load for brcm/brcmfmac4330-sdio.clm_blob failed with error -2).

    Cannot switch vt out from X

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines