Virverus

Members
  • Content Count

    11
  • Joined

  • Last visited

  1. uartparameternewrk3188.txt Hi , no luck , result is the same , including the creation of two log files . Something else , in my search for images ,answers and clues I stumbled on a small conversation you had in a Radxa forum . They tried your image on a rockpro with the same result as I. You also mentioned you had difficulties accessing Radxa resources , So for sake of completeness : their first rk3188 models where simply called "rock" and had the exact same hdmi chip as mine , the it66121fn and these images boot from sd om my stick , I downloaded yesterday thier latest Lubuntu image and it worked. I'm connected to a fullhd hdmi monitor. In 2014 they launched two more models "rock pro" and "rock lite" both of them use the rk618 for hdmi output , their images do not work anymore on my stick , i tried their latest sd ubuntu_fullhd image , it only partly booted . So they tested your image on a device with a different hdmi interface than mine .
  2. I'm not the developer of these images ,that's balbes150 , I'm just the consumer and I did not even boot succesfully into a desktop (!), so why ask me?
  3. @balbes150 Hi. To rule things out I reformatted my sd card as recommended in Getting Started on the Armbian website and burned a fresh bulseye test image . It made no difference . I also dd'd as you explained the sd with boot-z-ut2.img and boot-z-cs968.img and boot-z-rock.img ,the uart output stayed more or less the same but I also tried an usb-stick and sd and usb combined , although the results stayed the same I sometimes noticed disk activity (burning led) on my usb stick , which means the device was not completely locked up ,although there was no serial output , it probed the usb stick . So I searched for log files and found 2 new files in /var/log : armbian-hardware-monitor.log and armbian-ramlog.log . These files where only created when I booted your unaltered image or with the boot-z-rock.img ,with the other 2 dtb's cs968 and z-ut2 these files where not created.I tested this several times.Also sometimes after a while on uart showed a long string of hooked zero's like this: [00][00][00][00]........etc..This also happens with serial output text when you choose the wrong baudrate , then all your output shows as hooked zeros.So it seems the rock dtb image does boot in armbian but somehow the uart and hdmi interfaces are corrupted . armbian-hardware-monitor.log : ### Activated 1 lzo zram swap devices with 1000 MB each ### Activated Armbian ramlog partition with zstd compression ### Activated lzo compressed /tmp armbian-ramlog.log : Mounting /dev/zram0 as /var/log/ Mon Jun 29 17:40:11 UTC 2020: Loading logs from storage sending incremental file list alternatives.log armbian-hardware-monitor.log bootstrap.log btmp dpkg.log faillog fontconfig.log lastlog wtmp apt/ apt/history.log apt/term.log chrony/ cups/ journal/ openvpn/ runit/ runit/ssh/ speech-dispatcher/ sysstat/ unattended-upgrades/ sent 969,578 bytes received 273 bytes 1,939,702.00 bytes/sec total size is 968,132 speedup is 1.00 These are the files created on the first run with a fresh unaltered image. Perhaps it's possible to get in armbian through ssh , but I have never worked with ssh so that's complete new territory for me .
  4. @balbes150 Hi , I managed to solder a uart interface to my android stick and reflashed your bulseye rk3188 test image to my sd card this is the serial output: DR Version 1.04 20130517 In 3 3 DDR3 222MHz Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=8 Size=2048MB Memory OK OUT BUILD=====3 SdmmcInit=0 0 FwPartOffset=2000 , 0 run on sd0 OK! 15747 unsigned! SecureBootEn = 0 0 Boot ver: 0000-00-00#0.00 start_linux=====28658 4419477 Starting kernel...@0x60408000 Yes ,that's all , a bit disappointing I have to admit
  5. Thank you for your answer ,this clarifies a lot , I'll wait for a rk3188 version then .
  6. Hi Balbes150 , I downloaded and burned both images focal and bulseye to SD ( armbian-focal-rk3188_20200629.img and armbian-bulsey-rk3188_20200629_5.6.6.img )and tried them on my MK802IV but they didn't boot to desktop . I did change the uEnv.txt file in the Boot directory to use the radxarock dtb file ,you did not mention that , but it made no difference. I also noted some boot-z img files in the yandex archive ( boot-z-rock.img ) , are they needed in some way? radxarock images usually boot on the mk802IV also. Some elementary booting did happen ,because android from Nand didn't start ,but my HDMI monitor stayed black , there was no signal.
  7. Hello balbes150 , I do have a rkm802IV ( the 'old' model )stick , I can boot the old linuxium linux image from sd , (from this post http://www.linuxium.com.au/how-tos/tastytreats ) . Because it's almost 10 years ago my memory of what I read and did has become a bit rusty so I downloaded this image again and burned it to sd using balenaEtcher on Debian and indeed it booted immediately. I tried a few of your 32 images the same way ,burned them to sd but they won't boot . ( Armbian_20.05.6_Arm-32_focal_current_5.4.43_desktop_20200604.img and Armbian_20.05.6_Arm-32_focal_current_5.7.2_desktop_20200613.img ) ,the system boots to android nand .Then I tried to flash the bootloader from your link using rkAndroidtool under windows 10 ,but that was refused by the program .(check chip not ok) , well .it's a rk3188 so it refuses a rk3288 loader . In the past I read a lot of linuxium's posts and he had many solutions for booting . Not all these posts exist anymore , google+ has dissappeared so it's a bit tricky finding everything back .The next few days I'll try to refresh my knowledge .(I don't know what happened here but i've gone Italic !!)
  8. for wifi I found this https://github.com/wonview/wifi_driver. It might work.I've not tested this myself,in fact it's been a long time since a compiled kernels or modules,before the DTS era actually.