Jump to content

Khadas

Members
  • Posts

    51
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @Vito Dgb I'm sorry but I returned that TV box to the seller for free because it was counterfeit. You could put the Multitool for TV boxes with RK322x Soc that you find in this forum on a USB drive. if the multitool boots you have confirmation that it is a sox 322x I recommend an old kernel to start with, like 5. Good luck
  2. @WayneGibbous I'm glad you solved it, I actually reported the counterfeit TV boxes with different CPUs and inferior performances with the photos
  3. That kernel is based on the warpme minimyth2 h616 patches
  4. I had never seen the PCB in version 4.0 thanks for sharing the photo. From that working image if you do the updates will you have an equally fresh and updated system or do you have problems after the updates? You should open an issue on the miniarch project's github and understand if the author has this specific hardware but I don't think otherwise you would have found it in the list of images, I see four different ones for h96q. Ihave PCB version 1.3
  5. Great news!!! thanks. If I can I want to try a new image with kernel 6.6 on another micro SD and see what happens. Perhaps it was a bug in the first kernel after the official release and the transition to the CSC releases. Over the years it has already happened to me twice to find the board blocked and the plastic of the case melted and this time I didn't want to do further tests but I left the latest kernel 6.1 of the official release.
  6. @Magd Almuntaser unfortunately this forum does not offer support for armbian forks for various technical issues. what I can tell you is that ipbs9505 dtb is correct if you boot the fork image from micro sd when you do the installation on emmc you will have to use that precise dtb as if you had the Wojia-TV-IPBS9505 (s905L2) tv box. I also bricked the board some time ago trying to install the official armbian on emmc. my problem was trying to overwrite an installation of a fork distro previously done on the emmc rather than starting from an emmc with the factory android image. I am currently using the fork image with this kernel Distribution: Armbian 24.2.1 jammy Kernel version: Linux 5.15.145-ophub aarch64 and I must say that it is stable for my experimental server needs. I have no interest in putting modern kernels because I noticed that using them on micro sd they were not very stable and I chose an older kernel.
  7. This is a post to search for the firmware of the Tanix TX3 Mini TX box with S905L2-B soc (yet another fake TV box). I advise you to write a new post, after searching the forum for the information you are asking for. This low-end TV box will not allow you to use it as a replacement for a desktop PC. Internet browsing for example will be very slow.... These TV Boxes can be used as small Linux servers like for example an old Raspberry, with the difficulty that you don't have the same support as the Raspberry community and this means that you won't have updated images that work immediately. You will have to waste time to understand why it doesn't start immediately or how to copy to the Linux emmc and fear bricking the board with the hope of recovering it if its firmware from the specific manufacturer exists. Bye and good luck.
  8. I'm using the latest kernel from the official armbian release: Kernel version: Linux 6.1.53-current-sunxi armv7l I must say that stability and temperatures are now normal.I disabled kernel updates from armbian config Honestly, I don't want to experiment with the current release kernel, i.e. CSC 6.6.x, again. I don't want to find random crashes and loose plastic cases due to the CPU having temperatures out of control. For now the 6.1 kernel lets me run everything and is still modern.
  9. Since last week the official image for Tanix TX1 has been available but the installation procedure is complex as I had already anticipated. I remember that the Miniarch project is not linked to the armbian project and with this post I would like to close this thread so as not to go off topic. It is possible to open issues on github of our friend Piotr who develops the project alone.
  10. Since last week the official image for x96q 1.3 (and also for pcb 5.1) has been available. Unfortunately, the hardware of the x96q TV box suffers from the classic problems of Chinese TV boxes, that is, there are many fakes around, i.e. PCBs with other hardware (even a different processor) and continuous revisions of the board based on what the manufacturer finds cheapest. I remember that the Miniarch project is not linked to the armbian project and with this post I would like to close this thread so as not to go off topic. It is possible to open issues on github of our friend Piotr who develops the project alone.
  11. I can say that a way has been found on a board to be able to run a minimal arch Linux distro. Unfortunately it is not easy and we are still in an initial testing phase. 1) Open the case and press the button located behind the audio jack during power on. At this point, use the USB male cable to load the modified image with Linux PC and Sunxi-fel utility to boot from USB. 2) Boot with a USB stick and USB keyboard hub and check that the Linux kernel starts. 3) Upload Linux image to eMMC. I am not at risk of carrying out point 2 and I will have to solder the cables for the serial port to understand where the problem is in my case. If there are any updates I'll let you know. If it is possible to create an image ready to be directly on emmc this could be within everyone's reach.
  12. Hi @compent you're right, I'll try to write what I did to solve the problem. After these commands run sudo armbian-install - option 7 to flash mtdblock0 (bootloader install) - option 4 (to install system and boot from mtdblock0) choose nvme0n1p2 partition to install system After checking that when I rebooted it didn't start from nvme I did this I deleted the nvme ssd partitions with fdisk I copied the armbian image with SCP from another PC into a currently working installation folder on Microsd Finally with the DD command I copied the image to nvme Rebooted without micro sd and started from nvme with the fresh armbian image. At this point for future installations on nvme with the new armbian images I will only delete with fdisk and copy with the dd command using an image on microsd. I hope I was helpful. I'm sorry to say but the installation part of armbian-config is very confusing to me
  13. I solved it but I don't understand why the armbian install command didn't copy anything on the nvme. I had to delete the partitions on nvme, then copy the fresh image file onto the micro sd with a working image with scp and then load the image with dd. By doing this I was able to fix it and it booted straight away.
  14. Before writing I searched the forum a bit but couldn't find any recent posts about it. I have an OPI5 board and on NVME I would like to install armbian. I downloaded the image to micro sd and it boots fine. At this point I don't know what to do because I had to waste a lot of time on it some time ago and I don't remember the steps. With the armbian-config utility is it possible to clone the armbian release I am using on the micro sd? I remember that this wasn't possible some time ago. I would like to know specifically the steps to take and whether it is advisable to delete any old partitions on nvme. Thank you
  15. Hi @SteeMan, is official support back for orange pi zero? Not long ago the releases page clearly indicated CSC support but now I read standard support. The kernel I had problems with was 6.6.16 and now I see 6.6.20 available, who knows if they have solved the temperature problem with the new kernel.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines