nokirunner

  • Content Count

    69
  • Joined

  • Last visited

Everything posted by nokirunner

  1. good job guys, I felt that it would only be a matter of time for you to screw these drivers. I'm going to test them right now.
  2. honestly, I did some mix cocktails, I put kernels and libraries of the latest release of the legacy kernel in the sdcard that worked for me ... so theoretically I'm with the latest release ... however, the fact is that now I have a good 2d acceleration ... but anyway there is something that engulfs the download and the upload of the browser navigation, I tried midori and it works a little better ... As for the multi boot project I saw that there is grub for arm u boot but I am still too immature for these steps https://forum.odroid.com/viewtopic.php?t=26894 https://packages.debian.org/si
  3. @fabiobassa hehehe for now I'm having fun when I have some free time ... @jock hey I can use firefox from the tv box, and the scrolling of the pages is superfast!, I managed to activate the 2d acceleration, the only thing is that it takes a long time to load the pages, how could I get around this problem? ... however this is the configuration I'm using on the xorg config file Section "Device" Identifier "Rockchip Graphics" Driver "modesetting" Option "DRI2" "True" Option "AccelMethod" "glamor" ### "glamor" to enable 3D acceleration, "n
  4. hey @jock how are you? yes, I'm using an old installation, it's working on my sdcard and I'm fiddling with that. unfortunately on my board, I still can't install on emmc, I checked and I understood that I don't have a nand, my board is strange, if I try to make a firmware flash I fuck the bootloader, and I'm forced to do a maskrom recovery. however I'm studying, my goal is to keep both android in one partition from a couple of gigabytes and Armbian on a second partition. I have already managed to make one of my armbian sdcard on the second partition in the emmc and I have been able to b
  5. Well guys I don't know if you have already done it, but I realized that there was no 3D acceleration on my desk (after installing the video drivers) so I modified the x11 config file and I restarted ... and now i have the tv box which can be used almost like a desktop ... so Make a backup of the file "/etc/X11/xorg.conf.d/01-armbian-defaults.conf", and replace its content with the following: Section "Device" Identifier "Rockchip Graphics" Driver "modesetting" Option "AccelMethod" "glamor" ### "glamor" to enable 3D acceleration, "none" to disable O
  6. I believe it will be possible only if some acute wizard manages to take the source code and update and fix it. there are some sources of the drivers of these wifi chips on github, here is same example: https://github.com/khadas/android_hardware_wifi_icomm_drivers_ssv6xxx https://github.com/trustfarm/orangepi-zero-tfarm/tree/0a9ce3984366d54d4fdefb9abbdcf9b899d924e6/OrangePi-Kernel/linux-3.4/drivers/net/wireless/ssv6xxx
  7. @jock no recently having had little time, I just took a peek at the last comments .. this is great news, as soon as i can i try to give it a peek. HURRA!
  8. Ciao @jock are there any news in this new update from the point of view of 3D &video acceleration?
  9. we hope that we will have more luck with the opensource gpu drivers in the near future ... everything will have to go through a mesa-opengl acceleration, including video ... va-api or samething
  10. I'm arming myself to try the new method just for this
  11. @jock sorry I did not have time in these days to devote to the tvbox .. here is the result of your request $ sudo mmc extcsd read /dev/mmcblk2 [sudo] password for neonoki: Sorry, try again. [sudo] password for neonoki: ============================================= Extended CSD rev 1.6 (MMC 4.5) ============================================= Card Supported Command sets [S_CMD_SET: 0x01] HPI Features [HPI_FEATURE: 0x01]: implementation based on CMD13 Background operations support [BKOPS_SUPPORT: 0x01] Max Packet Read Cmd [MAX_PACKED_READS: 0x3f] Max Packet Write Cmd [MAX_PACKED_WRITES:
  12. @jock obviously I did this too (and in this case, the device gose in mask rom directly directly as soon as I power up) but despite the formatting those other "3 partitions" remain however, formatting mmclk2p1 the sdcard patched with libreELEC starts, while the sdcard with the original rom created by you continues not to start .. So I assume I can't boot by installing on nand for some reason which is the same as that which does not start the sdcard ... anyway, what is particular about the patching with libreElEC that manages to start the sdcard, while the original rom created by you doe
  13. @fabiobassa ok I understood, it was for the excitement of being able to do something that had a meaning .. I reflash the loader at 300mhz. I continue to have the problem that I can not put the system on nand ... deleting it completely I ca in mask mode and therefore I do not start from sdcard with the systems that created @jock so I wonder I noticed that there are two other "partitions" but they are not, because if I try to manage them with fdisk it won't let me access ... so it's as if they were 3 other micro memories apart ... mmcblk2boot0 mmcblk2boot1 mmcblk2rpmb .. could
  14. @fabiobassa I did it! and everything works perfectly, both with android and with armbian before I tried to flash the loader by @jock, but it did not work well, I could not enter usb mode to flash other things, also I did not start android, only armbian from sdcard ... so I entered mask mode rom and I flashed the original firmware ... then I loaded the custom loader at 300mhzRK322A_loader_v1.10.256.bin and I saw that everything worked perfectly .. but I was tempted to flash the 400mhz RK322A_loader_v1.09.256.bin version to see what was happening ... at most if it di
  15. @fabiobassadei poveri .... ok I go back to 300 mhz .. ... e se ci piallassi qualcosa a raffreddamento a liquido funzionerebbe a 400mnz?
  16. @jock it worked! for some reason ul wasn't working ... i had to use from here http://opensource.rock-chips.com/wiki_Rkdeveloptool rkdeveloptool wl 0x40 loader.bin
  17. @jock probably indendevi with the addition of ul, otherwise it tells me that illegal operation ... however I tried and I get the same result ... sudo ./rkdeveloptool ul rk322x_loader.bin The device does not support this operation! meanwhile, I had also gone to create the custom loader, having investigated the type of chip and ram taken from the official firmware and from the network by reading the datasheet on the type of ram mounted on the pcb ... but I always get stuck at the usual point ... am I wrong wrong connection mode with the usb ?? do I have to enter mask
  18. @fabiobassa thanks for the link, now the situation is a little more understandable, however I have this problem, that when I run these commands, I don't get the idbloaders from the eemmc -rom loaded .. or maybe I'm doing something wrong and I have to get the idbloader from somewhere else ??
  19. @jock @fabiobassa i can't understand some issues .. I tried to do some experiments on the nand .. first I deleted directly to see if I can start armbian from sdcard, and it did not boot .. so I investigated why, and I found that the device went directly to mask rom mode as soon as I gave it power so I tried flashing armbian directly with the command ./rkdeveloptool wl 0x0 <armbian-image.img> I can flash but the device does not boot. also I can't in any way flash the bootloader nor do it the bakup with /rkdeveloptool db (or ul) what am i doing wrong? the only pos
  20. guys, you have not commented on this, can these driver sources be useful?
  21. @jock don't tell me ... are you italian too? Well there is to say that I experienced that the system had become very fluid, but today when I turned the TV box back on it no longer booted from sdcard ... I have to investigate why, I put the sdcard in the pc, so I have access to the files, but I don't know what to manage ...
  22. guys, can someone explain something to me? as soon as i installed the full firmware package from armbian comfig, the system became noticeably more responsive, almost reaching the capabilities of a real desktop, can anyone explain this to me? have you checked ?? the reason why i installed the full signing package was because the usb wifi that i am using had no firmware installed ... P.S. I am very happy that I managed to install the octoprint server without difficulty
  23. @fabiobassa non si era capito? I'm having fun, so I'll see if I can sift the net like a good truffle mole .. also because the usb wifi that i currently have available armbian tells me that the firmware are not loaded ... by the way, if i take the firmware from linux for x86 and insert it in the armbian do I have any chance that it works? this source ... what do you say they could be? https://github.com/khadas/android_hardware_wifi_icomm_drivers_ssv6xxx https://github.com/khadas/android_hardware_wifi_icomm_drivers_ssv6xxx/tree/khadas-vim3-pie/ssv6x5x
  24. I believe that they have unified it and have put the x x as a reference which is a general driver for all this variants of wifi chip, it seems to me the most logical thing.