• Content Count

  • Joined

  • Last visited

 Content Type 


Member Map






Everything posted by Igor

  1. You can do it this way: First do a copy to larger image, than execute those commands manually to expand to whole space: fdisk /dev/mmcblk0 d ENTER # delete 1 ENTER # partition 1 which is the only one n ENTER # create new p ENTER # primary ENTER # default number is 1 ENTER # default start ENTER # default end w ENTER # write to disk reboot # when system gets back resize2fs /dev/mmcblk0p1
  2. I have similar (Realtek 8812AU chipset) but haven't got far yet. Most promising driver, not sure that AP is operational and stable @5Ghz. https://github.com/gnab/rtl8812au more info https://wikidevi.com/wiki/ALFA_Network_AWUS036AC
  3. I would need some logs to be sure what's going on. I am out of office for some days so I can't check this particular build to make sure / check if there is anything wrong with it.
  4. There is a different wireless driver in kernel 4.x+ (actually 3.16+) brcmfmac but unfortunately it's a litle buggy at the moment. Looking and waiting for a solution.
  5. I know now what's the essential problem and it will be fixed. NAND/SATA/USB install part is as is. If you follow the install it works, It fails in custom situations - It's not designed for that yet. I am glad everything went o.k. and thanks, testing is always helpful and saves a lot of time. Mine and all users if we discover and fix thigns propmtly.
  6. http://www.cubieforums.com/index.php/topic,2211.msg16734.html#msg16734
  7. For default kernel 3.14.x https://github.com/igorpecovnik/lib/blob/next/config/boot-cubox.cmd Others: https://github.com/igorpecovnik/lib/tree/next/config boot*.cmd For rotation try this: Rotation You can rotate the framebuffer by supplying fbcon=rotate:<n> kernel parameter, where n can be one of the following. 0 - normal orientation (0 degree) 1 - clockwise orientation (90 degrees) 2 - upside down orientation (180 degrees) 3 - counterclockwise orientation (270 degrees) This is how it's done on Allwinner. I haven't try this with HB but it might work.
  8. yes they are. Boards are now stable after 2-3 weeks of burn in test.
  9. Check FAQ, section kernel update. The only note here is that you also need to update u-boot since most likely there is a problem. Download my kernel TAR pack, uncompress and install with: dpkg -i FILENAME Soon this part will be solvable via apt-get update / upgrade. I am working on it.
  10. One option is to boot SD image with 3.4.108 ...copy /lib/modules/*********-3-4-108 to nand2 and sda1, convert /boot/zImage to uImage with previously mentioned method and copy to NAND1 ... check uEnv.txt @NAND that it's pointing to proper root. So do step by step. First boot from NAND and rootfs=/dev/nand2 ... than copy modules to HDD and switch rootfs there.
  11. Any recommendations? http://wiki.lamobo.org/index.php/Lamobo_R1S New version is coming out but with Mediatek wifi which is as crappy as Realtek. I think we'll get more cheap (but with a little better hw) router boards soon.
  12. What I can see from log is that you are booting kernel 3.4.107 which makes me think that you haven't used the proper kernel as source. Somehow the conversion from zImage to uImage was not made properly. This is necessary since we use the preinstalled NAND u-boot. I'll recreate the exact scenario in next days to make sure this scenario works.
  13. You need to load alternative driver. It's located in /usr/local/bin insmod rt8192.cu or similar But don't expect too much. Get image with kernel 3.4.108 ... wifi is working better.
  14. Certain things can not be read at kernel 4.x yet or needed manual adjustments. For ambient temperature, illuminance, human detection ... you need external sensors. So, disable it. CPU temperature start to work properly in latest, i think 4.1.2
  15. The chipset is cheap & crap as well the drivers. There are few alternative drivers around but I am not aware if they are any better. I think the driver on 3.4.x works better. BTW: One alternative is located in /usr/local/bin ... blacklist kernel driver and load that one.
  16. I am working on Ubuntu 14.04 with it's defaults. gcc version 4.8.4 / gcc version 4.7.3 Recommended to avoid problems. Perhaps this is related.
  17. Kernel install only kernel (and modules), dtb only dtb, uboot only uboot, headers only header, ... They are not linked together by purpose.
  18. Yes, ignore. Kernel post install script creates a symbolic link to installed kernel. This is not possible on FAT file-system which is on the first NAND partition /boot. I'll fix once that it won't show the error and that that this command will be executed automatically. I am using NAND u-boot as is. All other debs are more or less optional.
  19. Where do you build it? There are troubles on some systems and compilers.
  20. Kernel installation is not yet ready for such scenario. I need to fix it. The only thing you need to do is to convert zImage to uImage (inside /boot) and reboot: mkimage -A arm -O linux -T kernel -C none -a "0x40008000" -e "0x40008000" -n "Linux kernel" -d vmlinuz-3.4.108-cubietruck uImage
  21. I recompile the kernel and image. Lime A10 image with kernel 3.4.108 and HW accelerated MATE desktop Same link: http://mirror.igorpecovnik.com/Lime-a10_Debian_1.0_wheezy_3.4.108.zip
  22. Thanks. 1. I don't need logs. You are right ... I'll fix asap. 2. No ideas at this point. I guess it's not a proper FEX script. I use the one from here. Access to hardware would be nice to conduct more tests. It would be glad to have this working ... some day
  23. Kernel tar pack has it all except rootfs deb package which is anyway not needed in this case. http://mirror.igorpecovnik.com/kernel/3.4.108-cubietruck-default.tar