thc013

  • Posts

    38
  • Joined

  • Last visited

Recent Profile Visitors

1346 profile views

thc013's Achievements

  1. a 3A power supply is enough you can check L2101 inductor the opi 4 is little bad with noisy power and active cooling is needed for working under heavy load on a rk3399 i compile gentoo on a opi4 wit all usb populated and a mini pcie wifi (yeah rust,gcc,clang spidermpnkey is no fun ) idle 30c /full load 60 c 5.10 is the most stable
  2. yeah the admin of that forum and you got 423 channels and tvheadend is fun there is a wiki a manual and a lot of info how it works the wizard is just to get it working , and then you have to tune it to your desires map the services to channels has the option check mux changes to be enabled or not etc,etc and epg is not that fast and works when you have it setup . just check what the mux is to start to scan to get a mux list , is the provider id right ,is there a encryption involved , etc etc
  3. it is not a bootsplash problem at boot the kernel searches for device and activates them and if a device takes time to get seen by the kernel the kernel get a amount of time to wait so when a device for example my usb3 got called before the bootsplash there is no bootsplash because kernel is waiting for the usb before he wants to put something on screen. you can see that effect if you boot through a console then you see the kernel spit out messages sometimes fast sometimes slower and it happens even more when you reboot but that is more less nowdays because the drivers are getting better
  4. ow iam not a little it is just a very old law they call it the law of ohm if i got 3 amp at 4.8v or i get 3amp at 5v makes a difference off 0.2v what should the R do ? "voltage drop since I'm going thru a voltage meter" realy ? https://www.dummies.com/programming/electronics/how-to-measure-voltage-on-an-electronic-circuit/ and to inform you 4.8v indicates that you power-supply can't supply 5.0v under load and it is not that panfrost or the codecs are a mess they are just come clear every day even that i know can get a little grip on it . and if you read the posts of EndlessEden you see he is missing the connection between kernel and ffmpeg. and he can remove from dts rockchip,defaultmode = <16>; /* CEA 1920x1080@60Hz */ and this hdmi { /delete-node/ hdmi-i2c-xfer; }; it is useless it will become a lot more clear for him if he compiles ffmpeg with the libreelec patches on his armbian build from source instead of the armbian normal ffmpeg otherwise you get ffmpeg calling the wrong codec paths and also integrate some of the libreelec patches to the armbian kernel otherwise ffmpeg cant let the kernel know to switch to other vpu state kodi doesnt matter much as long as the drmprime patches are included and these didnt change lateley and if he does that he can come to same kernel level as librele or armbian normal 5.10.34 or are we 35 already above 5.10 to 5.11 and 5.12 take a look at minimyth2 sources not realy much different with patches it has a other layout how he comes to the same result . or even my sensei has a libre for alwinner on 5.12 and me i just on 5.12 gentoo system with armbian-librelelec-minimyth2 mixed together and instead of 40 mousepointers when i move the mouse or green screen or v4l2 errors in gbm i now have only no picture on hdr ,sound works and kodi says it is using the correct codec didnt check with v4l utils yet can watch tv again and play most of my series and movies. and in 5.10 everything works. and why overclock even the codec core get underclocked to be smoother
  5. such a useless discussion was the 3.06 at 4.87 or 4.82 and where is the 5v how is you chain to the power grid . and by the looks of it it is powered through a usb hub with powered devices throuh selfmade pcb,s what is the losses of that . and great start of the chain of power you think ? u=ixr i=u/r what is the cos what is the foam layer of the beer from the board ? https://www.dc.systems/dcwiki/power-quality-a-typical-ac-problem https://www.youtube.com/watch?v=pKXPqApOYfk https://www.youtube.com/watch?v=wopmEyZKnYo how is your power supply build you see you got multiple choices to get a 5v on all the opi runs and the opi is delivering power to the ssd,oled,tft, pcie wifi , fan and still hapily compiling gentoo with distcc no pump overclocking isnt just stable power. where was your chiplet on the wafer ? how is the power chain on the board for example the power of the ram on the opi is shared with the rest of the 1.8v rail while other boards have a seperate regulator for that . and does the cpu run from the 5v source directly so you can undervolt it for example . and how is your cooling ? https://github.com/warpme/minimyth2 and even mythtv is still alive and it is another way to run your board as mediabox . how is mainline going almost everything is out of staging or will be soon ?
  6. https://github.com/armbian/build/blob/master/patch/kernel/archive/rockchip64-5.11/rk3399-add-sclk-i2sout-src-clock.patch so i dont know wich distro he is using but he just could copy the patches from armbian ony thig he had to do is choose a dtb or adjust it nothing more
  7. ah you downgraded your kernel with the cp command lucky you still got the modules installed of that kernel. so now your back at 5.9.14 and linux-headers isnt the problem. boot from sd do a blkid write it down or copy it , mount the rootdev look wich kernelmodules are installed in /lib/modules/<kernelname> or copy your modules from sd to rootdev edit armbianenv.txt change the uuid to wich rootdev it should boot.
  8. well you got a mac adress so hardware is seen did you do a apt update /apt upgrade seems more a systemd fault
  9. yeah that is rubbish armbianio and if wiringpi or wiringnp doesnt work or you edit the script of it or just calculate the gpio pin and use the normal linux commands to use a gpio pin like this https://wiki.radxa.com/Rockpi4/hardware/gpio https://www.programmersought.com/article/92031588023/ and ofcourse use the pinout of your board shematic
  10. it is WiringNP for GPIO . and gpio just works only you hve to calculate the pin but you are talking connecting a i2c device for lcd some you can add to dts and compile a kernel module . or through a script wich calls the i2c bus only just watch the bus number and device id . ow and watch the voltage of the i2c bus
  11. Yeah it is a m2 slot and just 2 lanes and there are nvme ssd with a m2 key they are called m2 ssd they copied the m2 slot of the rk3399 board to a pcie/m2 slot with a flex cable so more as 2x pcie is not gonna happen i get today that pcie board , just in time i fixed yesterday the typc boot option in uboot the pinebook and the helios gave the solution rk3399 is not that good in bringing up all rails in 1 time and they do it in the board c file instead with the dts file
  12. they are back in stock now from what i see , i just ordered one last week https://www.aliexpress.com/item/4000575054675.html?spm=2114.12010612.8148356.1.30b67fddNzcI4W
  13. Thnx Werner little cryptic message Yah already updated topic titel i made some fixes HDMI Uboot support works it was a dts change in the kernel dts , &cdn_dp and hantro are not good friends with hdmi yet so from SD SD (duh) ,USB3, USB-C works so pi 4b users can have some more options as the sd and mmc ,emmc and nvme not tested yet. From SPI SD ,USB3 , somehow fusb302 keeps his f up to still be fuzzy so no USB-C yet Uboot gives it no power and mmc and nvme not tested yet . HavE Fun Ps you can now change pi to his own elif [[ $BOARD == orangepi4 ]]; then BOOT_USE_BLOBS=yes BOOT_SUPPORT_SPI=yes BOOT_SOC=rk3399 DDR_BLOB='rk33/rk3399_ddr_933MHz_v1.24.bin' # Orange Pi 4 does it has 4gb standard and is cheaper and b has also a ai MINILOADER_BLOB='rk33/rk3399_miniloader_v1.19.bin' BL31_BLOB='rk33/rk3399_bl31_v1.30.elf' or elif [[ $BOARD == orangepi4 ]]; then BOOT_USE_MAINLINE_ATF=yes BOOT_SUPPORT_SPI=yes BOOT_SOC=rk3399 ATFPATCHDIR='atf-rk3399' if you apply the changes kernel-rockchip64-dev.patch linux-dtb-dev-rockchip64_21.02.0-trunk_arm64.deb linux-u-boot-dev-orangepi4_21.02.0-trunk_arm64.deb orangepi-4-rk3399_defconfig rk3399-orangepi-4-kernel.dts rk3399-orangepi-4-u-boot.dtsi rk3399-orangepi-4-uboot.dts sd-usbc-dmesg.txt spi-uboot-atf-log.txt u-boot-rockchip64-dev.patch