Jump to content

Igor

Administrators
  • Posts

    13862
  • Joined

  • Last visited

Everything posted by Igor

  1. Not really. Microsoft fatal: unable to access 'https://github.com/armbian/build/': Failed to connect to github.com port 443: Connection timed out I guess I am not alone?
  2. No need for that. This EXPERT switch just opens you a possibility to build more than what's recommended for end users. We do Bionic builds, but we don't want to remove label "testing" until it's working as expected. If you find a bug in Bionic, you are more than welcome to submit a fix. Only together we can hunt em down successfully
  3. You need to add a switch EXPERT="yes" ... and you are on your own if something doesn't work. Bionic works, but there are tiny bugs ... from the upstream, which we have no capacity nor wish to fix. If you don't want trouble, stick to Debian Stretch.
  4. You are referring to a document from early 2016. We have added many resolutions since. Not just we, but people who had their specific needs. Download image and type h3disp and you will see which one are available.
  5. Look once again. My test setup is exactly the same, except monitor is some Philips. No, except you are the one who will do that. That feature of switching screen resolution works only on some boards with modern kernels. In case you have some odd screen size, this is the way to add it: https://github.com/armbian/build/blob/master/patch/kernel/sun8i-default/z-0003-add-additional-video-modes.patch
  6. And updated images with many bugfixes.
  7. I am switching beta building to sunxi-4.18 branch where Allwinner NEXT (sunxi and sunxi64) is getting an upgrade directly to 4.17.y ... I made a few tests: Cubietruck: wlan fails http://ix.io/1fYS USB OK, HDMI yes Bananapi R40: http://ix.io/1fZm USB OK, HDMI yes Lime A64: USB no, HDMI no, wireless buggy, eMMC yes Orangepi prime H5: OK http://ix.io/1fZJ DVFS no Orangepi2e: DVFS OK, HDMI OK, net OK, wifi OK, eMMC ok, http://ix.io/1fZT Please report your findings ... after you boot into the new kernel ... currently building.
  8. This board is not supported anymore and it is not receiving BSP updates. That's why you got that error. It's safe to ignore.
  9. Not sure if we are there yet. This still shows up and sometimes it just hangs there: domain-0 init dvfs: 4 scpi_regression_hangs_the_board_possible_fix.patch doesn't have any effect. I don't recall if we had this problem before ... rebooting (sometimes) takes a lot of time. Boot log: http://ix.io/1fY9
  10. Yes A80 was prior to this, but support was also never mainlined. It is probably getting support with this batch ... A80 is even bigger exotics and there are just little boards out there.
  11. Each platform/kernel has/can have its unique way of setting screen resolution. What I have seen here, only a few screen resolutions are prepared in the kernel video driver so you are limited to those. Using a kernel parameter to enable them can't help since they don't exist. I am not aware of this particular board/kernel, but for Allwinner legacy kernels we had to do it this way https://github.com/armbian/build/blob/master/patch/kernel/sun8i-default/z-0003-add-additional-video-modes.patch RPi has a huge community and things as such were done a long time ago.
  12. That those few who had bad luck buying this board can perhaps use it? Well, I am not planning to provide any support for it. I saw patches ... A83T is a first big/little with a mainline support. I just needed to see how it works.
  13. Update: http://ix.io/1fUK Broken: wired, wireless network, Bluetooth, ... Works: serial console, 8 cores, DVFS, USB, SATA, HDMI, DRM video driver, ... https://dl.armbian.com/bananapim3
  14. Yes, it will. We needed that someone with 1G board proves it's a fix. Thanks for your help as well.
  15. It is applied. Perhaps in some rare cases, even this adjustment might not be enough? And powering with microUSB ?
  16. Random crashes are usually related to DRAM clocked too high. Your DRAM configuration might be below average quality and ... the second option is DVFS, which is also not done properly yet. Setting to fixed CPU speed might help. For first you need to recompile u-boot with lower DRAM speed, second, you need to adjust /etc/default/cpufrequtils
  17. Try this image: https://dl.armbian.com/rock64/nightly/Armbian_5.51.180704_Rock64_Debian_stretch_default_4.4.138.7z
  18. http://linux-sunxi.org/Hardware_Reliability_Tests
  19. It works for me http://ix.io/1fQ8 sometimes. As you can see there are many cpufreq: __target_index: Failed to change cpu frequency: -5 in the logs. One possible solution is to disable dvfs for now?
  20. USB section in a modern kernel is sensitive, hotplugging doesn't work ... you need to boot with the attached USB device. Then it (usually) work ... a small price for running a modern kernel. This is also noted on the download page.
  21. One quick solution is to use a nightly kernel which has those modules built-in. Edit /etc/apt/sources.list.d/armbian.list, change apt to beta, apt update & apt upgrade, reboot
  22. Correct: verbosity=4 console=bothoverlay_prefix=rk3328 rootdev=UUID=29b52589-9141-438e-961d-c475411d19bf rootfstype=ext4 load_addr=0x39000000 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u Sorry, I wasn't precise enough before.
  23. You need to ask FriendlyArm/WaveShare if they have any. We can merge drivers to the kernel if you come up with a working patch. That's all we can officially do on this subject. Armbian is ready to build out of the kernel tree drivers ... if you have sources and support from Waveshare. For SPI based displays ... it could work.
  24. You can. They have been recently reduced down to https://github.com/armbian/build/blob/master/packages/bsp/common/etc/apt/apt.conf.d/02-armbian-periodic#L4-L10 so you might just wait for update.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines