jeanrhum

I'm currently using a GT1 ultimate with 5.75 release of Balbes150 and vim2 dtb. I don't use it as a desktop but with another s912 box used as a desktop, I use also vim2 dtb successfully.

You're right, but znoxx may already have an USB-sata bridge since he mentioned this option. If price is not so important, rk3399 is clearly a better choice with other possibilities.

I never tried, but I suppose that this package is better than the generic one.

If you want a cheaper solution, maybe a supported board based on rk3328 like rock64 could be a good option since it has usb3 and gigabit ethernet.

Mali is for the GPU, i.e. 2D/3D rendering and not for video playing, this is the job of the VPU.

Is your wifi chipset detected ? Run armbian-config and look in the network section if a wireless device is listed. If not, the best way is to use a cheap usb dongle based on mainline supported chip.

Hi, After 2 tests with recent images (5.77) with debian stretch for s912 (balbes ilmages) and dev image for pineh64, I get the same issue when configuring locales. I selected fr_FR.UTF-8 in armbian-config and I also ran manually dpkg-reconfigure locales and locale-gen, but I ended each time to default locales settings (ANSI_X3.4-1968). Only the LANG variable is set to fr_FR.UTF-8 and all LC_XXX variables are set to C. To solve this issue, I have modified manually the /etc/environment to set LC_ALL=fr_FR.UTF-8. Does anybody else have this issue and is it specific to debian? With a 5.75 stretch image the locale configuration worked well.

Thanks to report report your experience. Maybe next kernels will have a better support, even if I didn't really see improvement in mainline support in the recent release.

You have to run "sudo apt upgrade" and not only update. If no kernel upgrade is proposed, you may have to download the deb file from Oleg's yandex repository: https://yadi.sk/d/pHxaRAs-tZiei/5.77/deb But be careful, you may have to check that the new kernel support is as good as your current one. You can try just to burn latest image and if everything works as you expect, you can then come back to your current version and install the deb files.

Look at armbian-config command line tool, I think in the software section you'll find the kernel headers.

Thanks, I will try this. It is sometime difficult to find the posts where the information is given. The topic becomes long and even if search utility helps, it sometimes difficult to find the relevant post. Can I also use the install.sh from my usb key to install uboot 2015?

You are right, I just wanted to report back that in fact old uboot (so uEnv.ini config file) may have been used when I started from usb, since now the cpu temp is not reported well when I look at htop. I will update the extlinux.conf file to use the vim2 dtb. Moreover I tried to use USBburning tool to check if I can restore an android image and the box is not visible. I also tried to boot again from my usb stick, but it doesn't work anymore, since I'm always booting to emmc.

Tested last 5.77 aml-s912 on an Excelvan EX-T2 using q201 dtb: ~$ uname -a Linux aml 5.0.2-aml-s912 #5.77 SMP PREEMPT Mon Mar 18 14:19:43 MSK 2019 aarch64 GNU/Linux armbianmonitor -u output: http://ix.io/1E8H There is no sd slot on this tv box, so I use an usb stick. Integrated wifi is working well. The desktop bit laggy, but it is expected since there is no HW acceleration. Edit: Install-2018.sh works well too.

Nice to heard that! I hope that such mini computer can be used easily with linux in a near future and that mainline kernel can be used with most features actives. Maybe a manufacturer can have more weights to obtain drivers for mainline kernel and all the info to define full-featured dtb files.

I can't get access to SPI pompt, only to u-boot: U-Boot 2015.07-g428cfe7-dirty (Jul 28 2017 - 10:10:26 +0800) aarch64-linux-xgcc (Realtek ASDK64-4.9.3 Build 2180) 4.9.3 20150413 (prerelease) GNU ld (Realtek ASDK64-4.9.3 Build 2180) 2.24.0.20141017

Hi, I think your have to upgrade your bootlader first to be able to boot from sd or usb, but I don't know if such a version exists for rk3229. The rootfs of current image is based on armv7 so no problem about that compared to rk3328 images you ask for in another thread, but the kernel itself may not be able to boot your board since the soc is different from rk3288 (at least the gpu).

Nice to hear such news. I haven't time to do anything about that last week. In my case I didn't solder UART, but just use some basic wires used previous with a breadboard and it enters the holes of the UART ports.

It's nice to see that you progress regarding kernel 4.19. Don't hesitate if you want me to test something and if I can help on some other tasks.

Ethernet is working. I deactivated wifi using armbian-config and then ran: sudo dhclient eth0 There were these messages, but I got an IP and was able to access to internet: smbd.service is not active, cannot reload. invoke-rc.d: initscript smbd, action "reload" failed. /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /etc/resolvconf/run/resolv.conf

With fdisk, the disk appear labelled as sataa: Disk /dev/sataa: 465,8 GiB, 500107862016 bytes, 976773168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 1807A3EC-C61F-48C2-B54B-A06A8856E92C Device Start End Sectors Size Type /dev/sataa1 40 409639 409600 200M EFI System /dev/sataa2 409640 391034639 390625000 186,3G Apple HFS/HFS+ /dev/sataa3 391296784 783007583 391710800 186,8G Apple HFS/HFS+ /dev/sataa4 783269888 974675967 191406080 91,3G Linux filesystem /dev/sataa5 974675968 976773119 2097152 1G Linux filesystem In dmesg it is also detected correctly: [ 3.543051] phy-rtk-sata 9803ff60.sata_phy: init phy0 OK [ 6.894037] ahci_rtk 9803f000.sata: masking port_map 0x3 -> 0x1 [ 6.894079] ahci_rtk 9803f000.sata: AHCI 0001.0301 32 slots 2 ports 6 Gbps 0x1 impl platform mode [ 6.894086] ahci_rtk 9803f000.sata: flags: ncq sntf pm led clo only pmp fbs pio slum part ccc sadm sds apst [ 6.894099] ahci_rtk 9803f000.sata: port 0 is not capable of FBS [ 7.102013] phy-rtk-sata 9803ff60.sata_phy: power on phy0 [ 10.554421] sd 0:0:0:0: [sataa] 976773168 512-byte logical blocks: (500 GB/466 GiB) [ 10.562394] sd 0:0:0:0: [sataa] 4096-byte physical blocks [ 10.568046] sd 0:0:0:0: [sataa] Write Protect is off [ 10.573921] sd 0:0:0:0: [sataa] Mode Sense: 00 3a 00 00 [ 10.573972] sd 0:0:0:0: [sataa] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 10.635891] sataa: sataa1 sataa2 sataa3 sataa4 sataa5 [ 10.642417] sd 0:0:0:0: [sataa] Attached SCSI disk

No problem if you don't get any result soon. I wanted to do something, but I don't really know where to start. I will try fdisk this evening when I'll be back home.

Thanks for your quick answer. In fact I looked at the boot folder on my sd card and there only a few files. I think that the write_uboot_platform function is not working correctly since it is written with absolute path for dtb and uboot from your fork. I don't search for a specific feature, I was just curious how to do that since I have mainly a "user" experience of armbian and this device seems interesting to me (however realtek is not the best open source friendly...). I saw that rtd1295 started to be introduced since kernel 4.13 so I hope the recent kernel can be built and run on this soc. For my second question, I'm not searching to boot from sata, but boot from sd and use a sata drive for a nas use case since this soc seems to be used in several nas commercial product.

Hi, Current kernel is 4.9.y, is it possible to get a more recent kernel (4.19.y LTS or 5.0.y mainline)? I tried to build a 4.19 by modifying the board config to have target next and dev as well as the source config. After running compile.sh with target next, I obtain a new image, but when trying to start it I got an error about bad gzipped data early after the second uboot start. I tried to modify the script writting uboot, but without any luck. Otherwise, I also tried to put a sata disk, but it appears as /dev/sataa and not /dev/sda and it is not recognized as a usable disk (nothing in /dev/disk) and OMV does not show it. It is the first time I see /dev/sataX dev and I don't know how to change that.

I'm currently accessing it through ssh and using a wireless connection. It works well, here is iwconfig result: wlxa02c36cad0d2 IEEE 802.11 ESSID:"XXXXXXXX" Mode:Managed Frequency:2.412 GHz Access Point: XX:XX:XX:XX:XX:XX Bit Rate=72.2 Mb/s Tx-Power=18 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=61/70 Signal level=-49 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 EDIT: I used armbian-config to set up the wifi.

Hi, I received my box yesterday and was able to build and follow your instructions to get the following system: _ _ _ | | __ _| | _____ / | | | / _` | |/ / _ \ | | | |__| (_| | < __/ | | |_____\__,_|_|\_\___| |_| Welcome to ARMBIAN 5.76 user-built Debian GNU/Linux 9 (stretch) 4.9.157-rtd1295 System load: 1.31 0.91 0.41 Up time: 5 min Memory usage: 3 % of 1636MB IP: CPU temp: 52°C Usage of /: 2% of 58G Great work!