Jump to content

talraash

Members
  • Posts

    101
  • Joined

  • Last visited

Posts posted by talraash

  1. 15 hours ago, scott90420 said:
    • Extract your DTB.img

    You don't need it now. And why you just don't use dd, base busybox utility, and any text editor to change dtb in uEnv.txt/extlinux.conf

    And if you talk about DT from stock adroid, it probably unusable with other kernel(mainline in armbian) without huge editing.

  2. 36 minutes ago, tim-timmy said:

    Hi,

    What steps did you use to have it working on h96max2 ? I burned a lot of different images to SD card, changed to all possible g12 DTBs, but each time I go to the update section and select the aml_update.zip from the card, it reboots, tries to load it, and fails with a broken android robot and just "Error!". It then reboots again on the android.

     

    Mine is flashed with android 9 (from https://mega.nz/#F!enh1kIYD!FdtiQoEO0V4awyrEZRwUew from https://www.h96tvbox.com/content/6-Firmware-upgrade ), could it be the issue ? I read that some were using ddr3 instead of ddr4, how could I check this ?

     

    Just write image, change dtb x96-max-rmii  and run box with reset button in av. 

  3. 27 minutes ago, balbes150 said:

    I understood correctly that when using the latest 5.2.1 kernel image with DTBS that are part of the image, the wired network does not work. But when using the old dtb (for 5.1 kernel) with the latest 5.2 kernel, does the wired network work ?

    No... wired network work with dtb from 5.2.1

    Spoiler

    Нет. dtb из 5.2.1, сеть по проводу работает только с g12a-x96-max-rmii как и в прошлых образах. 

     

  4. 1 hour ago, balbes150 said:

    I am interested in the wired network in the latest version of the image (with kernel 5.2.1) using DTB from the image. You can check it out ?

    ok... in a few hours, then I will edit this post.

    upd Same behavior as before wired network work only with g12a-x96-max-rmii DT.

  5. 1 hour ago, DismissedGuy said:

    I see. Is there anything I can do with the dtb/dts that would allow me to use it with this armbian build?

    Rewrite it. Use armbian as example. Write correct memory/bus addresses etc. You can find specific help in google just type "Device tree"

  6. 1 hour ago, DismissedGuy said:

    Hello,

     

    After trying lots of the provided DTBs, I have found a few files that allow me to successfully boot into the OS. However, I am yet to find one that provides ethernet or even better, wireless connectivity. Therefore I figured it'd be better to just dump the DTB from my box's ROM.

     

    The extracted DTB from /dev/dtb turned out to be around 256KB, much bigger than the ones already provided. After de- and recompiling this DTB using:

     

    dtc -I dtb -O dts -o dts.img dtb.img

    dtc -I dts -O dtb -o newdtb.img dts.img

     

    I ended up with newdtb.img being around ~32KB. Not bad.

    After copying this file to my SD card and specifying it in uEnv.ini, however, armbian refuses to boot.

     

    Why is this? Am I missing something here? Both the decompiling and compiling process spitted out some warnings, which I both ignored since the readable dts output seemed fine to me.

     

    Thanks!

    You can't use dtb from android as is... 

  7. 5 hours ago, balbes150 said:

    If there is no rush, I recommend waiting until the price announcement for VIM3 and Ugos AM6. If not a secret, what tasks are they going to do with this equipment ?

     

     

    info Beelink s922

    https://forum.freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s922x/others-s922x/reviews-tests-cs/772452-beelink-gtking-amlogic-s922x-4-64gb-dual-ac-wifi-mimi-gig-lan-bt4-2

    High performance soc with flat metal heat sink...  what a genius R&D)

  8. 2 hours ago, AndrewDB said:

    Remember that if you brick your TV box, you can always restore it using the SD card method. 😎

     

    Not always. If you break the u-boot being in nand there may be problems. If the u-boot in nand is broken, it was possible to restore the operation of the box only by closing the nand contacts and writing the correct u-boot or full image.

  9. 56 minutes ago, Reddwarf said:

    Mmmmm, maybe download the source and compile it yourself?

     

     

    Is it necessary? Firefox work fine with multimedia, next build of chromium may also be fine.  Chromium is very resource intensive at compile time(one build with compiliting time ~3 hours need 16 threads cpu ~ 32Gb ram and ~100 gb storage on ssd).

  10. 21 minutes ago, Reddwarf said:

    That might be due to poor programming in chromium, how does the test video run for you?

     

    Not sure. Rather, the problem is in different compilation flags. Half a year ago, the situation was reversed, in favor of chromium.  Looks like chromium use hardlocked gpu acceleration options and video decoding use sw opengl.

    I tested versions only from repositories, and it is not known who compilated them and how.  Test video from balbes150 smooth. My own sample h264 720p and 1080p looks ok too.  As before but now it work out of box(no need run video with flags --vo --sws-scaler manually)

  11. 38 minutes ago, Tommy21 said:

    Is it possible to put, in my case hdmi monitor to sleep, without the need for manually turning it off, i know this is maybe silly question that crossed my mind, but i do want to know.

    I know i've read somewhere that power management functions like suspend or hubernate are impossible to implement, but this shouldn't be impossible?

    I didn't try, but dpms may work... https://wiki.archlinux.org/index.php/Display_Power_Management_Signaling

  12. @Reddwarf It's vpu job...  https://dri.freedesktop.org/docs/drm/gpu/meson.html But without properly work v4lm2m, with software decoding we don't have hw scaling, and default scaling algorithm very heavy I mention early that if you play video which does not match with display resolution use --sws-scaler=fast-bilinear it give a huge performance boost

    P.S. Sorry for russian only, but that message was mainly for balbes150

  13. 37 minutes ago, balbes150 said:

    Found a strange behavior of the MPV on the latest builds. If  start playing a video file (720p) on the desktop with a resolution of 1080p, with the option "--vo=x11". The video is shown without brakes in a window with a size of 720 (equal to the resolution of the video). If try to expand to full screen, the video starts to slow down. If  run 1080p video, the windowed video slows down, but if you switch to full screen, it works without brakes. If change the desktop resolution to 720, 720p video works without brakes in windowed and full-screen mode. I don't understand why the 1080 video with the 1080 desktop is slow, but works full screen without brakes. What is the reason for this behavior ?

    Spoiler

    Такое поведение было во всех релизах) ИМХО, связано это в первую очередь со скалингом видео, с софтварным скалингом. С 720p soc еще справляется, в режиме "в окне" с 1080p  - уже проблемно. При проигрывание в фулскрине соответствующего разрешения ничего скалить не нужно, и соответственно проблем нет. P.S. Видел упоминанние про puppyrus, но упорно не получается зарегестрироваться на puppyrus, просто не приходит письмо активации на ящик gmail)

     

  14. 3 hours ago, (Jo)Hannes said:

    I am Running Armbian_5.67_Aml-s9xxx_Ubuntu_bionic_default_4.19.7_desktop_20181218 on an MAGICSEE N4 TV Box (meson-gxl-s905x-p212.dtb)

    The box runs quite fine, i am very impressed. Thanks a lot for your work.

     

    I am struggling to change the resolution of the HDMI out. on my full HD screen it runs fine, but i want tu run it on my 1024x768 screen via an DVI Adapter.

    Can't find the hdmi.sh script mentioned on the first page.

     

    Thanks a lot

          Johannes

    (ver 5.44 =<) For mainline just use regular method via xorg parametrs, or if you use desktop standart xfce4 instrumments in settings.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines