Jump to content

Igor

Administrators
  • Posts

    13867
  • Joined

  • Last visited

Everything posted by Igor

  1. Not possible. Stretch need a more recent kernel and on this recent kernel, there is no NAND support. If you want (much) worse support, yes. I recommend you to wait for release - few days ahead - or do some testing with nightlies too see what you can expect: https://dl.armbian.com/cubietruck/Debian_stretch_next_desktop_nightly.7z https://dl.armbian.com/cubietruck/Debian_stretch_next_nightly.7z In any case, use some modern SD card.
  2. You don't need to mount anything. The best is to remove the partition on target completely and the installer will invoke partition manager. In any case, we need to look more closely. There is one thing you can try and what might help - switch to beta nightly builds, update and then try again.
  3. I would compare kernel configuration first. Perhaps something is missing in ours. When you find missing options, send a PR. In less than 24h you have a kernel in a beta repository with enabled options ... in case you don't have a build engine around.
  4. HDMI sound works for me on a legacy desktop version with Orangepi PC. Whenever reporting some malfunction, provide as much useful data as possible. We operate too many boards.
  5. Two most common but rear problems: broken SD card or not paying attention. You log in with root, the password is 1234. Then it asks you for root password again, then you need to type the new password twice. In case of bad SD card/fs corruption, it usually does not allow you to change the password because fs is mounted read-only.
  6. Building yes, working untested. Working now on a cleanly installed host. http://sprunge.us/DQJV It looks like mine is corrupted somehow. Will rebuild.
  7. No proper quick hack solution yet. https://github.com/armbian/build/commit/d95d45f20947661c17d3d1ee3b1ba964de677cb4
  8. I try to install the latest beta and it worked out of the box. I used ext4 and it worked fine ... when using BTRFS ... I found a bug: "/sbin/init: error while loading shared libraries: /lib/aarch64-linux-gnu/libuuid.so.1: cannot read file data: Input/output error"
  9. Are you sure you have Orangepi Zero? Does it look the same? Mine works without a problem: http://sprunge.us/EjgT
  10. "Rear" could be understood both ways Router rear are usually RJ45 sockets. In any case logical connections matters - both are 100M only and can be used in any WAN/LAN combination. Current armbian-config have a wizard for setting AP while for extended interfaces manipulating, creating bridges, firewall, ... is not yet done. Network config is anyway on your own/upon your needs and my goal is to provide some simple router functionality. If you need some serious stuff it's better to use (containerized) OpenWRT or similar.
  11. @doru you need to update boot loader ... download this https://beta.armbian.com/pool/main/l/linux-u-boot-nanopineo2-next/linux-u-boot-next-nanopineo2_5.34.171121_arm64.deb and install with: dpkg -i xxxxxxxxxxxxxxxx.deb ... reboot and report armbianmonitor -u again to see if its fixed. Than run nand-sata-install
  12. What is your power supply? If it's on the edge / not good enough, USB ports will remain dead.
  13. If you look from rear, left is usb right internal. eth0 is the internal by naming. Wrote on mobile
  14. Networks work normally for me while I noticed that leds on USB based eth stays on but since this is a cosmetic issue I didn't even try to find out how to turn that down.
  15. Those are early experimental builds and we didn't get any further. Last week I tried to attach C2 to 4.14 but the board constantly crashed during boot, USB is sometimes up sometimes not ... there are many troubles to solve first before dealing with MALI. I gave up for now.
  16. I see you are using self-made image ... how about our nightly images? https://dl.armbian.com/orangepizero/Ubuntu_xenial_next_nightly.7z Do they work for you o.k. ?
  17. Update: https://www.armbian.com/orange-pi-r1/ Debian Jessie and Ubuntu Xenial with 3.4.113 (stable) Debian Stretch with 4.13.14 (nightly testing) Bootlogs: http://sprunge.us/TZIQ Running AP: wlan0 IEEE 802.11bgn ESSID:"ARMBIAN" Nickname:"<WIFI@REALTEK>" Mode:Master Frequency:2.432 GHz Access Point: 08:EA:40:7C:02:B1 Bit Rate:150 Mb/s Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0
  18. It's a small bug. Fixed. Tomorrow there will be a new server test image as well: https://github.com/armbian/build/commit/f586584df4cb7b9e208a2d8c112685d09fca6aba
  19. I forced compiler re-download, cleared sources again. It builds o.k. but the result is the same
  20. Any quick fix for this? This? will proceed with the investigation in the evening.
  21. Besides this, what about MALI? Currently, its also broken for legacy builds? Still something wrong with Clearfog:
  22. http://sprunge.us/eiFf There are no problems with Armbian. Bananapi M1 + USB hub + AC Wireless access point. Connected at boot time or later, in any case, it works perfectly fine. Armbian is not responsible for hardware design failures. Either use powered USB hub or some other board.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines