Jump to content

Igor

Administrators
  • Posts

    13589
  • Joined

  • Last visited

Everything posted by Igor

  1. Updated. It should be populated with data from all forums now.
  2. You have wrong u-boot / boot script combination and you are most likely using not supported developing kernel ? ... it's not possible to activate cpu's from user space.
  3. MiQi added to Armbian. What I did: - added kernel 4.4.50 ... took from https://github.com/mqmaker/linux-rockchip(4.4.16) ... and patch all the way up to 4.4.50. - added stock MiQi uboot. I tried too merge it with mainline but figured out soon that it's not going to be easy and abandoned that - added boot scripts with environment file - packaged kernel, u-boot, ... - updated kernel config to meet Docker requirements - added proper serial console - tested CLI and desktop build. Both runs smoothly. Known bugs: random MAC, eMMC install script and boot script need some adjustments Unknown: mali, video accleration librarires, ... etc. most likely those should go: https://github.com/mqmaker/rk-rootfs-build From tomorrow morning, betas will be available here: https://dl.armbian.com/miqi/nightly/ armbianmonitor -u http://sprunge.us/TWMF Console log:
  4. AFAIK on one revision of this board WiFi part is broken ... to (me) unknown degree.
  5. This page is more like a table with all kernels that we build. You don't need to install anything since images comes with all those packages ... but in case you do some damage or in your case, you can fix the system by installing a proper one. Next, some boards have more kernels and you can switch between them. So this table has naming and if you go for "DEV" ... you need usually to change to DEV u-boot to ... so it's better to change all packages if you want to do so. In any case, all this is recommended for experienced users who know how to fix things if something goes wrong.
  6. It's O.K. now ... you could further uninstall those packages, linux-image-sunxi linux-image-3.4.107-cubietruck linux-jessie-root-next-cubietruck but it's also harmless if you just leave as is.
  7. Than proceed to plan B, which is less user friendly but it must work. http://git.denx.de/?p=u-boot.git;a=blob;f=configs/Cubietruck_defconfig;h=4ac128533826f66ad7cd92d9edf9574aad263489;hb=HEAD Comment out # CONFIG_VIDEO_VGA=y and recompile.
  8. And you think this problem will be solved by switching to Debian version?
  9. There is no official support from Openwrt folks for this board, that's why. It looks like they only support old Allwinner chips like A10 and A20.
  10. You are upgrading from very old image and we change some package names in between. You will need to uninstall some and install new one. Check this page for relevant info: https://www.armbian.com/kernel/
  11. No, but you can build it on your own from sources. That's why provide and support build tools - for those who need something else than our prebuilds.
  12. Set some fixed resolution, monitor to hdmi, disabled hdp, disabled edid ... save that into u-boot environment, otherwise it wont work. Plan B: recompile u-boot with disabled VGA support and it should also be fine.
  13. Yes, I just checked. It's set to VGA if nothing come up on HDMI. This is the console output: U-Boot 2017.01-armbian (Feb 02 2017 - 02:21:14 +0100) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Cubietech Cubietruck I2C: ready DRAM: 2 GiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment Setting up a 1024x768 vga console (overscan 0x0) In: serial Out: vga Err: vga SCSI: SATA link 0 timeout. AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part ccc apst Net: eth0: ethernet@01c50000 Hit any key to stop autoboot: 0 6944 bytes read in 156 ms (43 KiB/s) switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1...
  14. I should already work out of the box - I think you get 1024x768 if EDID detection failed. Are you perhaps using self configured desktop?
  15. Check: /etc/default/log2ram # configuration values for the log2ram service ENABLED=true SIZE=50M USE_RSYNC=false
  16. We need to find out what the problem might be ... Just disable ramlog service and you are back to normal / slower logging.
  17. We are using ram logging to gain performance and save SD media and which might have some issues ... Temporally workaround is to create this file along with directory.
  18. Yes, all images were rebuilt (5.2.) since they were built without video acceleration libraries. By mistake / with wrong parameter.
  19. Try via some powered USB hub. Bad powering looks exactly like this ... some random problems, first on areas where 5V is needed ... Wrote on mobile phone
  20. Those drivers should be fine / the best what's out there ... strange. Well, those dongles are shit in first place ... Alternative is (testing) mainline kernel. We provide automated nightly builds ... but you are on your own.
  21. https://www.armbian.com/orange-pi-pc-> Nightly releases It works, but this is automated build since its still under development, which means sometimes could be broken.
  22. Perhaps you have older Cubox which is based on Marvell chip set and not imx6 ? Are there any marks on the box? Can you open and check the chip?
  23. With USB camera and Bluetooth headset, mouse and keyboard.
  24. Last time I was installing it to Debian Jessie - few months ago, it was working normally. In case of troubles - check logs and read documentations. There are no quick solutions: Note that ISPconfig is a complex and powerful tool. I also need to read manual if things broke: http://www.ispconfig.org/get-support/ If you need just a web server wih php and perhaps sql, check those tutorials: https://www.digitalocean.com/community/tutorials
  25. Patch should go here (sun8i-dev): https://github.com/igorpecovnik/lib/tree/master/patch/kernel/sun8i-dev
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines