All Activity

This stream auto-updates     

  1. Past hour
  2. This is brand new SoC from Allwinner, this mean Linux support will take a while before it make it under Armbian, unless we find some compatibility with previous H6.
  3. Today
  4. Is there a way to do your workaround without re-flashing eMMC? Like writing FriendlyElec on any other SD and connect it after system boots from eMMC already having system?
  5. Yes that worked, with fdisk /dev/nvme0n1 I created a partition which is now /dev/nvme0n1p1 Thought it was like sata with sda being the first drive etc. Thanks Sent from my moto g(7) power using Tapatalk
  6. Shouldn't you actually be partitioning a /dev/nvme0n1 device as /dev/nvme0 is simply a controller?
  7. @arel I'm afraid without the correct device tree dtb, that is as far as we can get at the moment. Someone might be smart enough to figure it out. Good thing I got mine for cheap
  8. @fabiobassa - good point - i now used the config from the 4.4.189 kernel plus make oldconfig for building 4.4.194 and the resulting kernel now boots and works perfectly fine update: i did not yet find the console connector on this box, but of all the librelec images it only booted the ddr2 one, so i assume it has dd2 memory ... about the rk3228: the funny thing is that it runs nicely with the 1.4ghz clock speed of the rk3229-xt-mx4vr-v01.dtb ... @jock - maybe your 4.4.194 kernel config should be reviewed and potentially adjusted? btw. i can confirm that your above suggested cursor fix for your armsoc xorg server works well ... a lot of thanks and best wishes - hexdump
  9. as said this is still very much work in progress i guess ...
  10. lspci has: 00:00.0 PCI bridge: Fuzhou Rockchip Electronic Co., Ltd RK3399 PCI Express Root Port 01:00.0 Non-Volatile memory controller: Philson Electronics Corporation E12 NVMe Controller (rev 01) lsblock has it as: nvme0n1 259:0 0 931.5G 0 disk /mnt Sent from my moto g(7) power using Tapatalk
  11. Hello, I tried and at least from glxinfo there is a difference with or without the environment variable: marco@aml:~$ glxinfo -display :0|grep version server glx version string: 1.4 client glx version string: 1.4 GLX version: 1.4 Max core profile version: 0.0 Max compat profile version: 2.1 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 2.0 OpenGL version string: 2.1 Mesa 20.1.0-devel (git-2976ae2717) OpenGL shading language version string: 1.20 OpenGL ES profile version string: OpenGL ES 2.0 Mesa 20.1.0-devel (git-2976ae2717) OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16 with gles3 support : marco@aml:~$ PAN_MESA_DEBUG=gles3 glxinfo -display :0|grep version server glx version string: 1.4 client glx version string: 1.4 GLX version: 1.4 Max core profile version: 0.0 Max compat profile version: 2.1 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 OpenGL version string: 2.1 Mesa 20.1.0-devel (git-2976ae2717) OpenGL shading language version string: 1.20 OpenGL ES profile version string: OpenGL ES 3.0 Mesa 20.1.0-devel (git-2976ae2717) OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 so all seems fine but when open something on dolphin-emu (build from source) still saying : in the dolphin gui : GPU: OGL_ERROR: Need OpenGL version 3. GPU: Does your video card support OpenGL 3? in the shell : marco@aml:~$ PAN_MESA_DEBUG=gles3 dolphin-emu Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_MAJOR_VERSION) any idea ?
  12. @hexdump thanks for replayng ; you have a 3228 and not a 3229 , probabily a 3228b 00000000 52 4b 23 82 the numbers 23 82 are 3228 in reverse mode so you must use trust os for 3228, the trust os for 3229 simply will not boot the board but this you already knew regarding the changing in code in kernel I did the following ( but no changes in code, maybe in make config ) : in my long post linux on 3229 I used too the kernel 4.4.189 and it worked fine. I booted in 4.4.189 and take the config.gz and then recompile 4.4.194 with that same .config and it worked with SAME dtb . last info : I am pretty sure you have uart debug. At very early booting ( power on) what ddr it says ? ddr3 or ddr2 ? because ddr2 on 3228 HAVEN'T dmc ( ddr frequency scaling) so they will run at the speed that uboot set , probabily at 333 mhz ( all this infos thanks to @knaerzche that explained in his work on libreelec ). If you have ddr2 you must DISABLE dmc node in dtb boards with 3228b and ddr2..... well.... they are a bit slower than others EDIT: i realized the different behaviour from kernel 4.4.194 to 4.4.189 in @jock config many thing are compiled as modules so then you must insert right modules under /lib/modules in 4.4.189 compilation many things are compiled IN kernel so they work out of box, but yet you should check if have ddr2 or ddr3
  13. Yes, I use the image from FriendlyArm mentioned on their website (in my case, I booted the image that was on the MMC when it got shipped, which is most likely the same one). To capture their first stage bootloader with dd, I analysed the nand-sata-install script to see what needed to be copied. It may be possible to directly fetch the bootloader part from the sdcard image, with a similar dd with if=sdcard.img when you have a linux PC. Since u-boot is opensource, we can probably ask FriendlyArm for their software/configuration changes to the first-stage u-boot in order to get this integrated into the Armbian tree as a patch.
  14. Hi there, I´ve bought the X88 King...but did not read this thread before i bought this fault . The reason i´ve bought it was to run balbes Armbian...the box should be my "Server" for serveral services like "home automation, NAS, TVHEADEND-Server, Docker etc." in other words my Homeserver based on a low power ARM-system. After I´ve tetsted several balbes-images ;-) and dtb´s to start I always get to the point which was mentionend ethernet,no usb.... I´ve bought the X88 at spend 130 Bucks for the ugoos or the Odroid N2 wouldnt be my favourite,. If there is ANY Chance to find a way to find a workaround to get usb OR ethernet up and runnning in armbian would be a dream. So...please go on to investigate on X88 :-)´s a real cheap and powerful platform of s922x. regards arel
  15. Hi Titot, Just to let you know, I have do some reading, and as balbes said, recompiling the kernel with the Mali 400/450 gpu driver will be the solution (well, i am not digging deeper , too much of engineering for me.) ================== I have only the m201 board, mxq black box. I don’t own a Odroid. Links This one saids an open source driver for 400/450 ones, I have not tried yet. Let me know if this enables smoother 720p video playback. (youtube plays a bit better at 360p with hw acceleration off in Chrome settings menu. ) ========================== edit : @Titot if you found the documentations above works for you, please show me your procedures in an easy to understand way.
  16. Hello, That's my problem as well I was writing about it In my case the easiest way is just having empty SD card in slot and it reboots again but I will try Your solution, Dennboy I guess the friendyarm image you mention about is the image from FriendlyARM wiki? Regards
  17. Hi, Please advice about which Armbian + .dtb is needed to boot a T95 Allwinner H616 Mali G31, 4Gig lpddr3 32Gig ROM. Have already tried several distro's but never seen boot splash screen. Zanfi
  18. @jock - i tried reducing the opp tables on mainline to 1.2ghz and to lower the opp and gpu clocks on the rockchip kernel - nothing changed. also with the working 4.4.189 kernel it works with the full opp and gpu clocks without any problem. @fabiobassa - here is the efuse content: root@r39-4k:~# hexdump -C /sys/bus/nvmem/devices/rockchip-efuse0/nvmem 00000000 52 4b 23 82 81 d4 70 55 52 4b 4e 30 39 30 32 35 |RK#...pURKN09025| 00000010 00 00 00 00 01 2c 15 03 00 03 81 00 00 80 00 00 |.....,..........| how to interpret this? update: i also tried to boot the 4.4.194 kernel with the 4.4.189 dtb to rule out potential dtb changes - it does not work the same way the 4.4.194 kernel with its own dtb does not work, so the reason for the problems should be somewhere in code changes between 4.4.189 and 4.4.194 i guess ... a lot of thanks in advance and best wishes - hexdump
  19. Chromium is a larger project than Armbian. If bug is there ... there is little we can do about. You can try to: - compile from sources -
  20. I got an NVME one now, and it is recognized! Did a dd speed test and got 370mb/s on the nvme drive and 13.8mb/s on the SD card. I created an ext4 filesystem on the already existing single partition it had as if I do: sudo fdisk /dev/nvme0 I get the error Illegal seek and it exits. If I try: sudo parted /dev/nvme0 I get Error: The device /dev/nvme0 is so small it cannot possibly store a filesystem or partition table. Perhaps you are using the wrong device. But I can create a filesystem on /dev/nvmen1 mount it and dd a1gb file without errors. Sent from my moto g(7) power using Tapatalk
  21. Took a look here? But I'll guess you have to compile it on your own since the provided binaries are designed for i386 and amd64, not arm.
  22. i have an orangepi plus2e, and i cant find mupen64plus, i can find data and plugins, but i cant find the main package, i tried installing other packages wich might contain it but no luck. are there other repos to add? or do i have to compile it?
  23. I'm pretty sure I found the problem. It's a bad file-system. I think the cause of the bad filesystem was usb 2.0 hub with a long cable. I had the root drive (thumb drive) plugged in at the end of this long cable. I noticed in the documentation it mentions most problems are caused by either a bad file system or a bad power supply.
  24. Probably here (and in case of doubt all other H6 based boards) below the USB3 hint: "H6 may throttle fast on full load. Installing a heatsink is adviced."
  25. So I'm a bit of a dummy. I did not know I could put in the interface name (wlan0) into the device portion of the network manager connections list. When it made the entry for me it had <Mac address>(<ifname>) 00:e0:4c:81:92:5a (wlan0) for instance.. I just removed the Mac address and the parentheses around wlan0 and now network manager is connecting my wifi on boot. I know this not the correct way to do this but this is all I needed. Thanks for giving me a sounding board to reach this conclusion! Cheers
  1. Load more activity