Jump to content

curse

Members
  • Posts

    35
  • Joined

  • Last visited

Posts posted by curse

  1. 35 minutes ago, Sigma7 said:

    A new question: would I be able to virtualize the Armbian image from this topic using a PC with a snapdragon 7c processor, install some apps, insert a new default wallpaper, export in IMG and the installation would work normally?

    No. The Snapdragon 7c is different from the RK3318/RK3328. You'd have to find an image for the Snapdragon 7c. 

  2. 4 hours ago, Wester_Minsk said:


    I erased the eMMC, burned the image to SD and deleted the USR and VAR folders from it and inserted it into the board. Then I recorded the same image on an SSD and connected it to USB 3. The system started and works very well and quickly until the first reboot, then u-boot no longer sees the kernel on the SSD:

     

    After overwriting the SD and SSD images, the system starts again.

     

     

    Correct me if I'm wrong. But you want to run the system from a USB3 SSD?

    If so, I think the easiest would be to just have the boot on eMMC or SD-card, and the rest of the system on the SSD, then "almost" everything would be running from the fast SSD.

  3. 10 minutes ago, markst said:

     

    Another day, another Board.  I now have a few of these boards. x88 pro m10 4GB RAM 64GB ROM

     

    1 . Installed to eMMc --- Armbian 21.11 - Debian Bullseye minimal - mainline kernel 5.15.2 Build date: 2021-11-12

    WORKED NO PROBLEM

     

    2. Try to get WIFI working. 

    NOT WORKING

    running  rk3318-config but it indicates  "No WIFI chip has been detected". I go through the menus and try each option rk3318-box-led-conf1  -  rk3318-box-led-conf2  -  rk3318-box-led-conf3 and generic then reboot each time. No luck No WIFI and No leds.

    In file /boot/armbianEnv.txt there is overlays=rk3318-box-wlan-ext

     

    Any ideas?

     

     

    It seems to be an SP6330 wifi chip, if you look at the chip with the most dust on it.

  4. 2 hours ago, chinhhut said:

    @jock

    I have an idea as follow to clone an Armbian box to new one and will try this weekend if reasonable. 

    For instance, we have H96 max with 64GB flash. If making full backup of 64G flash and restore, it takes a lot of time.

     

    Here are major steps:

    Step 1: Install the Armbian according to your guide from page 1 (only take 1 minute to finish) to the box 1.

    Step 2: Boot Armbian from box 1 and using partition tool to divide the eMMC flash into 2 partitions,: partition 1 from beginning to 5GB. Partition 2 is remaining space

    Step 3: Make the backup of partition 1 by rkdeveloptool or similar partition tool to the PC

    Step 4: Install the fresh armbian to the box 2  like Step 1(only take 1 minute to finish)

    Step 5: boot the box 2 and make 2 partitions like Step 2.

    Step 6: using rkdevelopetool or similar to to restore the backup from Step 3 to partition 1 of box 2

     

    I don't have much experience with partition tool on Linux and this is just idea. Please give us your any comments if any.

     

    Thank you.

    Wouldn't it be easier to modify Armbian as you want it before installing it in the first place? I don't know how to do it, but example. Download @jock's Armbian, or compile your own. Modify the files on the .iso. write it to the SD card and install it on box 1 without the need to modify it later. Then do it on box 2, box 3, etc.

  5. Late response. 

    In theory. I think you're on te right track.

    The backup in multitool does a raw copy, sector by sector, of the eMMC, so... theoretically.

    1. Install Armbian to eMMC and configure it to your liking
    2. Take a backup of the eMMC with multitool.
    3. Start the next box with multitool and "restore" the backup from the first box.

    It could work. The problem with TV-boxes though, is that sometimes(or even often), even if they are named the same and look the same, there can be different hardware in them. Probably what was cheapest at the time of production. Other potential issue I see, even if they are 100% identical, would be the hostname. That might be needed to set manually on all boxes. For example "RK3228-Box"(if that was the original hostname) had to be set to "RK3228-Box-1","RK3228-Box-2", etc. Otherwise the network might get confused.

    Then again, if you have hundreds of them. You could experiment a bit. It wouldn't be a total loss if a few of them died during experimentation.

  6. 26 minutes ago, chinhhut said:

    I've tried your way by decompressing the backup.gz file first then the extracted file is very big (the size is 16GB equal to the original eMMC size) and it takes much time to fully restoring.

    So is there a way to reduce the size of extracted image to save the restoring time?

     

    For example, the original size of eMMC is 16GB then the extracted image is also 16GB but the actual data size is only around 2-3GB. My idea is how to keep the data size only in the image and remove the blank data of the backup image. That might help to reduce the backup image even after decompressing.

    I noticed the same when I was trying to restore my backup. It got stuck at around 20-25 percent and I thought it might work better if I uncompress it first.

    Oups, I have a 64GB eMMC, and the SD card I had at the time was only 16 or 32 GB. 

    The backup is a raw disk image of the eMMC, and it will always be the same size as the eMMC until it's compressed, and "removing the blank data" is part of the compression process. 

  7. 15 minutes ago, jock said:

    Update!

     

    New testing minimal and xfce desktop debian images are available on first page!

    • Latest kernel 5.15

    So, it should have the new Paragon additions for NTFS, right? I usually have an external NTFS drive connected to my box, and I'm currently using the NTFS-3G driver. It's said that the new stuff is supposed to be better. 

    Pretty cool, my Arch Linux x86_64 desktop computer still has 5.14.**.

  8. On 10/29/2021 at 9:35 PM, Houjimmy said:

    Why is it messed up? How it should be wrote instead?

    Current:

    APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0gs=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0

     

    Fix after quick look:

    APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0

     

    It seems like you had everything after "APPEND root=LABEL=ROOTFS rootfla" copied and pasted after "net.ifnames=0"

     

    Is this the S905x3 version? I've been looking at one, but still not decided on it. 

  9. And perhaps try with different SD cards. I first used some expensive recommended 64GB SanDisk card and nothing worked then I tried a "no-name" cheap 8GB card and it worked perfectly. I think it's up to luck when it comes to the SD cards. The recommended expensive cards might work more often than the cheap ones, but sometimes it's the other way around. 

  10. 4 hours ago, chinhhut said:

    After booting from eMMC successfully, I try to boot from SD card again to try the multitool but not success. At current, my box still only can boot from eMMC.

    Just one question. How did you "burn" the iso to the SD-card? did you use dd, rufus, etc? Just in case the error is there and not with the box or the iso?

  11. 3 hours ago, chinhhut said:

    Yes I guess your hardware might be different even looks similar.

    My problem is our box is unable from SD card then there is no further step. 

    Did you try multitool? Oh, now when I think of it. Didn't we had to press the "reset button" while plugging in the power, the first time? Toothpick in the headphone jack. Or it might have been my other box.

  12. 1 hour ago, chinhhut said:

    could you share the way to boot Armbian from your H96 max 4/64? I've tried to follow exactly the steps from the guide in this topic but unable to boot from SD card.

    My box look like this photo below:

    59a16b368ac2ad5e1d8b64403b567ae8

     

    I have the plus. However, I was never able to boot Armbian from the SD card, I used Multitool from this thread. Added the Armbian ISO to it, multitool booted fine from the SD card, then took a backup of the stock ROM with multitool and then erased eMMC and installed Jock's Armbian via multitool. 

     

    20211101_173147.jpg

  13. 1 hour ago, byfa said:

    I have since crashed it and recovered to a stock ROM that I had backed up, but it worked.
    Also, I am now reinstalling all of armbian.

    Have fun experimenting. I myself is "hooked" on playing with the TV-boxes. First I had an old Mini M8S II Amlogic S905x 2/8 box that had been in a drawer for years, and I thought it should be possible to use it as a mini server and found Armbian. Then I felt that 8GB was a bit tiny, and started to look around for something slightly bigger though still cheap. I was choosing between Rockship RK3328 and Allwinner H6 since it looked like they both had fairly good support already, and not an Amlogic S905x(2,3,4) since I read here on the forum about some bad practice from Amlogic. After finding out that the H6 only can handle 3GB RAM, I went for the RK3328. In my subjective experience, the Amlogic felt easier to work with and also felt faster... No idea if it is for real. Thinking about getting a box with an Allwinner chip as well, just so I have one each of the three bigger brands, but it will have to wait for some savings to pile up. The RK3566 boxes with 8GB RAM looks fun as well, but I don't think I use anywhere near 4GB at the moment...

  14. Ahh. So it's a HK1 thing...I got a H96 Max+ and at least it seems to have the specified RAM/eMMC size.

     

    Welcome to Armbian 21.11.0-trunk Bullseye with Linux 5.10.68-rockchip64
    
    No end-user support: built from trunk
    
    System load:   55%           	Up time:       2 days 21:36	
    Memory usage:  17% of 3.88G  	IP:	       192.168.0.13 192.168.0.15
    CPU temp:      75°C           	Usage of /:    10% of 57G    	
    storage/:      74% of 1.9T   	storage temp:  31°C         
    curse@H96MaxPlus:~$ df -h
    Filesystem      Size  Used Avail Use% Mounted on
    udev            1.9G     0  1.9G   0% /dev
    tmpfs           398M   44M  355M  11% /run
    /dev/mmcblk2p1   57G  5.4G   51G  10% /
    tmpfs           2.0G     0  2.0G   0% /dev/shm
    tmpfs           5.0M     0  5.0M   0% /run/lock
    tmpfs           2.0G   32K  2.0G   1% /tmp
    /dev/sda1       1.9T  1.4T  490G  74% /home/curse/Media
    /dev/zram1       49M   22M   24M  49% /var/log
    tmpfs           398M     0  398M   0% /run/user/1000
    curse@H96MaxPlus:~$ free -h
                   total        used        free      shared  buff/cache   available
    Mem:           3.9Gi       711Mi       308Mi        43Mi       2.9Gi       3.1Gi
    Swap:          1.9Gi       4.0Mi       1.9Gi
    

     

  15. 16 hours ago, fabiobassa said:

    Hello @Byfa thank you for reporting your experience :beer:

    I doubt it is real 64 giga rom and 4 giga ram... 

    Also corious to know how much it costed and how long you waited to have it

     

    The "HK1 RBOX R1 mini 4G/64G" Seems to be around 45 Euros in various places, Banggood for example.

    Why wouldn't it be real 4GB/64GB? It seems to be more or less standard nowadays. I know the Allwinner H6 only can handle 3GB RAM but usually is sold with a 4GB chip inside, but I've never heard about it with the Rockship RK3318/RK3328. They seem to have cheaper versions with 2/16 and 4/32 though.

     

  16. 6 hours ago, RetroFan90 said:

    i'll check for other monitors with dvi-d.

    hope we can turn this into a full blown computer that supports nearly all hdmi / dvi-d displays

    basic resolutions

    640x480

    720x480 / 720x576

    800x480 / 800x600

    1024x600 / 1024x768

    1152x864

    1280x720 / 1280x768 / 1280x800 / 1280x960 / 1280x1024

    1360x768 / 1366x768

    1440x900

    1600x900 / 1600x1200

    1680x1050

    1920x1080 / 1920x1200

    2048x1536

    and so on

    While I was in Sweden some month ago, I only had access to an old 1024x768 monitor, connected via an HDMI to DVI adapter. It did NOT work. Multitool, yes, everything else, no.

    1 hour ago, MX10.AC2N said:

    I don't understand anything anymore, is it repairable or I have to start over and especially not to forget to do apt update && apt upgrade before doing rk3318-config .. @jock what do you think of all this?

    I would not recommend to do an apt update && apt upgrade before you have gone through "armbian-config" and frozen firmware and kernel updates, or frozen them by other means.

  17. Good Morning. Just a quick question.

    Is it possible that the temperature is shown wrong at login? 

     ____  _  ____________ _  ___    ____            
    |  _ \| |/ /___ /___ // |( _ )  | __ )  _____  __
    | |_) | ' /  |_ \ |_ \| |/ _ \  |  _ \ / _ \ \/ /
    |  _ <| . \ ___) |__) | | (_) | | |_) | (_) >  < 
    |_| \_\_|\_\____/____/|_|\___/  |____/ \___/_/\_\
                                                     
    Welcome to Armbian 21.11.0-trunk Bullseye with Linux 5.10.68-rockchip64
    
    No end-user support: built from trunk
    
    System load:   3%           	Up time:       2 days 21:03	
    Memory usage:  4% of 3.88G  	IP:	       192.168.0.35
    CPU temp:      68°C           	Usage of /:    8% of 57G    	

    It seems to idle at 68 C and when doing stuff goes to 90+. At the same time, "top" sees the CPU going at 270%. While the box feels warm, it doesn't feel hot, which I assume it would be, if it were 90+C a centimeter from my finger.

  18. 10 minutes ago, Gausus said:

    Curse have you opened your box and seen what name is on your wifi chip ?

    No, I'm quite bad at screwing and such because of an injury. Sorry. Oh... I have the H96Max+ RK3328 4GB/64GB Voice Remote version (not that I have tried using voice commands on it). Who knows, the Voice Remote version and the normal remote version might differ.

  19. 44 minutes ago, Gausus said:

    How did you make the WiFi work ?

     

    I replaced the existing /lib/firmware/brcm/brcmfmac4334-sdio.rockchip,rk3318-box.txt with this file. Then it worked in nmcli

    #nmcli device wifi list
    shows available wifi networks
    then 
    #nmcli --ask device wifi connect vodafone5CC8
    and it asked for the password for my wifi named vodafone5CC8, and now it connected, before it didn't.

    My overlays are: overlays=rk3318-box-cpu-hs rk3318-box-emmc-ddr rk3318-box-led-conf1 rk3318-box-wlan-ap6334

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines