Werner

  • Posts

    2669
  • Joined

  • Last visited

6 Followers

Profile Information

  • Gender
    Male
  • Location
    Federal republic of Germany

Contact Methods

  • IRC
    werner@irc.libera.chat
  • Website URL
    https://github.com/EvilOlaf
  • Github
    EvilOlaf

Recent Profile Visitors

7956 profile views
  1. You can try official Ubuntu way of upgrading but as mentioned you won't receive support if something goes wrong. Armbian Disco is EOL and therefore does not receive any further updates. If it works you can simply keep it as it is. However do not expose the device or any of its services to any untrusted network (WAN for example) since there are no patches for security issues provided.
  2. Armbian Disco has never been officially supported by Armbian. Also userspace upgrades (like Buster to Bullseye or Bionic to Focal) have never been officially supported by Armbian due to lack of ressources for proper testing. Best would be to start over with a fresh image.
  3. Moved to tv boxes general chat since nobody knows about your unknown tv box.
  4. Correct. Keyservers work independent. I don't know. What I do know however is that httpredir has been deprecated by Debian for years now. deb.debian.org should be used instead. Can be read somewhere in Debian wiki. No idea
  5. ubuntu's keyservers are like any other keyserver around. http://pgp.mit.edu/ for example is a well known keyserver that has been there for ages. However it depends on the key owners to spread their keys on various keyservers.
  6. Okay, then you can create a proper issue report here: armbian.com/bugs
  7. armbian-config was not designed to noticed if somebody messes with the packages by hand. For first clues I suggest to check the source of the script and repeat the steps taken: https://github.com/armbian/config/search?q=desktop
  8. Your issue report is not a valid bug report per the Armbian bug reporting instructions (https://www.armbian.com/bugs). With limited resources the Armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported. Your report is invalid for one or more of the following reasons (non-exhaustive list): it is for an unsupported board or image (CSC/EOS/WIP/edge) it is for software that is not supported (such as userspace modules installed on top of the core operating system) it has been logged in the wrong forum (for example requests for help that are not actual bug reports) it lacks requested data (armbianmonitor output) it could have been easily solved by a quick search and/or reading documentation Please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as Common issues / peer to peer technical support or General chit chat)
  9. Your issue report is not a valid bug report per the Armbian bug reporting instructions (https://www.armbian.com/bugs). With limited resources the Armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported. Your report is invalid for one or more of the following reasons (non-exhaustive list): it is for an unsupported board or image (CSC/EOS/WIP/edge) it is for software that is not supported (such as userspace modules installed on top of the core operating system) it has been logged in the wrong forum (for example requests for help that are not actual bug reports) it lacks requested data (armbianmonitor output) it could have been easily solved by a quick search and/or reading documentation Please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as Common issues / peer to peer technical support or General chit chat)
  10. Last night my Neo3 seems to have died. As I checked it earlier today the heartbeat was gone and the SoC (with glued heat sink on) was hot. After power cycle it refuses to boot again. Wrote the same known to work image I used yesterday to boot it on a fresh sd and got this from serial which was the same as the other sd: DDR version 1.16 20190528 ID:0x805 N In DDR4 333MHz Bus Width=32 Col=10 Bank=4 Bank Group=2 Row=15 CS=1 Die Bus-Width=16 Size=1024MB ddrconfig:14 OUT Boot1 Release Time: May 13 2019 17:34:36, version: 2.50 ChipType = 0x11, 248 mmc2:cmd1,20 emmc reinit mmc2:cmd1,20 emmc reinit mmc2:cmd1,20 SdmmcInit=2 1 mmc0:cmd5,20 That's it. No further output. I assume the board is toast.
  11. Pine64 is a vendor that sells multiple boards.
  12. What did you expect from a system that is neither supported nor maintained?
  13. Your unknown board may or may not be able to boot from eMMC. Some need boot loader stored on sd, others not.