• Announcements

    • 1. Check power supply, check SD card and check other people experiences

      Power supply issues are one of the three biggest issues you'll face when starting with Single Board Computers (SBCs). SD card issues, whether fake or faulty, are another and issues resulting from poor board design is the other common issues you can encounter.   Power supply issues can be tricky. You might have a noisy power supply that works with one board because it has extra filtering, but won't work with another. Or you're using that cheap phone charger because your board has a microUSB connector, and it is either erratic, or doesn't start up, or even becomes the cause of some SD card issues.    Some tips to avoid the most common causes of problems reported:   Don't power via micro USB  - unless you have optimised your setup for low power requirements. Micro USB is great for mobile phones because they are simply charging a battery. It's bad for SBCs. Yes, it does work for a lot of people, but it also causes more problems and headaches over time than it is worth, unless you know exactly what you are doing. If you have a barrel jack power connector on your SBC, use it instead! If there is an option for powering via header connections, use that option!
        Don't use mobile phone chargers. They might be convenient and cheap, but this is because they are meant for charging phones, not powering your SBC which has particular power requirements.
        When you are evaluating a power supply, make sure you run some stress tests on your system to ensure that it will not cause issues down the path.   (Micro) SD card issues can be sneaky. They might appear right at the start causing strange boot and login errors, or they might cause problems over time. It is best to run a test on any new SD card you use, to ensure that it really is what it is, and to ensure that isn't faulty. Armbian provides you a simple way to do this   --   armbianmonitor -c /path/to/device/to/test  
    • 2. Make sure to collect and provide all necessary information

      We can only help if you provide quality information for us to work with. All stable images from the download section are tested, most stable upgrades are tested and we have tens of thousands of users. Even with regular and extensive testings, bugs sometimes do slip through. This is a voluntary support service and is unrelated to board makers, and is not obligated to provide you any answers. Repeated asking the same questions because you're not happy with the answers will result in you being ignored.

      Before you post a question, use the forum search as someone else might have already had the same problem and resolved it. And make sure you've read the Armbian documentation. If you still haven't found an answer, make sure you include the following in your post:   1. Logs when you can boot the board: armbianmonitor -u (paste URL to your forum post)   2. If your board does not boot, provide a log from serial console or at least make a picture, where it stops.   3. Describe the problem the best you can and provide all necessary info that we can reproduce the problem. We are not clairvoyant or mind readers. Please describe your setup as best as possible so we know what your operating environment is like.     We will not help in cases you are not using stable official Armbian builds, you have a problem with 3rd party hardware or reported problem would not be able to reproduced.

Orange Pi One 3rd party wireless adapters
1 1

8 posts in this topic

Recommended Posts

I have bought an Orange pi One, and i need to get wireless. I have an rtl8188 and a rtl8192.

 

Tested:

1-Official android: workd slow, no wifi

 

2-Ubuntu lxde 0.9.1: downloaded kernel and cross compiler... error compiling module driver

 

3-Raspbian: no kernel headers-->Error compiling the kernel.

 

4-Armbian: No boot

 

No hdmi signal, red light blinking || keeps rebooting

 

What shall i do?

 

Does this board worth it?

 

Thanks.

Edited by zador.blood.stained
Renamed the thread

Share this post


Link to post
Share on other sites
On 24/1/2017 at 5:41 PM, Igor said:

Start with getting started https://docs.armbian.com and get serial console to debug.

I will not spend money (serial debug) and lots of days to simply boot and test a distribution, i will keep using distributions able to turn on hdmi and show login prompt.

 

All unmodified hardware, all unmodified software, multiple sd card tested. This is not my fault. Armbian needs improvements, i'll try again when this didtribution archieve a single thing: BOOT.

 

See ya.

Share this post


Link to post
Share on other sites
37 minutes ago, garfius said:

This is not my fault.


Now it is.

I asked for serial console output to rule out possible board hardware troubles. We have seen that some boards failed to initialize with a modern u-boot which is used in just about every build. But since you rather waste my time than buying a serial console for 2USD this tells me that it's no use to help you. 

1. This image: https://dl.armbian.com/orangepione/Ubuntu_xenial_default.7z

2. Boot this way:

Spoiler

U-Boot SPL 2017.05-armbian (Jun 13 2017 - 15:34:52)
DRAM: 512 MiB
Trying to boot from MMC1


U-Boot 2017.05-armbian (Jun 13 2017 - 15:34:52 +0200) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi One
DRAM:  512 MiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   phy interface0
eth0: ethernet@1c30000
Hit any key to stop autoboot:  0 
38518 bytes read in 147 ms (255.9 KiB/s)
Unknown command 'bmp' - try 'help'
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3565 bytes read in 195 ms (17.6 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
115 bytes read in 157 ms (0 Bytes/s)
5154669 bytes read in 512 ms (9.6 MiB/s)
4750952 bytes read in 510 ms (8.9 MiB/s)
Found legacy kernel configuration
34880 bytes read in 450 ms (75.2 KiB/s)
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    5154605 Bytes = 4.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

[sun8i_fixup]: From boot, get meminfo:
        Start:  0x40000000
        Size:   512MB
ion_carveout reserve: 160m@0 256m@0 130m@1 200m@1
ion_reserve_select: ion chipid  [0x2c00081!
ion_reserve_common: ion reserve: [0x56000000, 0x60000000]!
Loading, please wait...
starting version 229
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.27.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 
/dev/mmcblk0p1: clean, 48744/90432 files, 288129/361472 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Ubuntu 16.04.2 LTS!

[  OK  ] Reached target Encrypted Volumes.
[  OK  ] Set up automount Arbitrary Executab...ats File System Automount Point.
[  OK  ] Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Reached target Remote File Systems.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on Journal Socket.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Listening on fsck to fsckd communication Socket.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Created slice System Slice.
[  OK  ] Reached target Slices.
         Starting Restore / save the current clock...
         Starting Nameserver information manager...
         Starting Create list of required st... nodes for the current kernel...
[  OK  ] Created slice system-serial\x2dgetty.slice.
         Mounting Debug File System...
         Mounting POSIX Message Queue File System...
         Starting Set console keymap...
[  OK  ] Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Reached target Paths.
[  OK  ] Started Trigger resolvconf update for networkd DNS.
         Starting Remount Root and Kernel File Systems...
[  OK  ] Listening on Syslog Socket.
         Starting Load Kernel Modules...
[  OK  ] Listening on Journal Audit Socket.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Debug File System.
[  OK  ] Started Restore / save the current clock.
[  OK  ] Started Create list of required sta...ce nodes for the current kernel.
[  OK  ] Started Set console keymap.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Started Nameserver information manager.
[  OK  ] Reached target Network (Pre).
         Starting Apply Kernel Variables...
         Mounting FUSE Control File System...
         Activating swap /var/swap...
         Starting udev Coldplug all Devices...
         Starting Load/Save Random Seed...
         Starting Create Static Device Nodes in /dev...
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Activated swap /var/swap.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Started udev Coldplug all Devices.
         Starting udev Kernel Device Manager...
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /tmp...
[  OK  ] Reached target Swap.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Mounted /tmp.
[  OK  ] Started Entropy daemon using the HAVEGE algorithm.
[  OK  ] Reached target Local File Systems.
         Starting Armbian enhanced Log2Ram...
         Starting Raise network interfaces...
         Starting Set console font and keymap...
[  OK  ] Started Armbian enhanced Log2Ram.
[  OK  ] Started Set console font and keymap.
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
[  OK  ] Started ifup for eth0.
[  OK  ] Reached target Sound Card.
[  OK  ] Created slice system-getty.slice.
         Starting Journal Service...
[  OK  ] Started Journal Service.
[  OK  ] Started Raise network interfaces.
         Starting Flush Journal to Persistent Storage...
[  OK  ] Started Flush Journal to Persistent Storage.
         Starting Create Volatile Files and Directories...
[  OK  ] Started Create Volatile Files and Directories.
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Reached target System Initialization.
[  OK  ] Started Daily apt activities.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target Timers.
         Starting Armbian filesystem resize service...
[  OK  ] Started Armbian filesystem resize service.
[  OK  ] Reached target Basic System.
         Starting Login Service...
         Starting Permit User Sessions...
[  OK  ] Started Regular background program processing daemon.
         Starting LSB: Load kernel modules needed to enable cpufreq scaling...
         Starting LSB: Start/stop sysstat's sadc...
         Starting Save/Restore Sound Card State...
         Starting Daily apt activities...
         Starting LSB: Starts LIRC daemon....
         Starting System Logging Service...
         Starting LSB: Armbian gathering hardware information...
[  OK  ] Started D-Bus System Message Bus.
         Starting Network Manager...
[  OK  ] Started System Logging Service.
[  OK  ] Started Permit User Sessions.
[  OK  ] Started Save/Restore Sound Card State.
[  OK  ] Started LSB: Load kernel modules needed to enable cpufreq scaling.
[  OK  ] Started LSB: Armbian gathering hardware information.
[  OK  ] Started LSB: Start/stop sysstat's sadc.
[  OK  ] Started LSB: Starts LIRC daemon..
[  OK  ] Started Network Manager.
[  OK  ] Started Login Service.
         Starting Network Manager Script Dispatcher Service...
         Starting Network Manager Wait Online...
[  OK  ] Reached target Network.
[  OK  ] Started Unattended Upgrades Shutdown.
         Starting OpenBSD Secure Shell server...
         Starting LSB: set CPUFreq kernel parameters...
         Starting Set console scheme...
[  OK  ] Started OpenBSD Secure Shell server.
[  OK  ] Started Set console scheme.
[  OK  ] Started Network Manager Script Dispatcher Service.
         Starting Hostname Service...
[  OK  ] Started LSB: set CPUFreq kernel parameters.
[  OK  ] Started Hostname Service.
         Starting LSB: Set sysfs variables from /etc/sysfs.conf...
         Starting Authenticate and Authorize Users to Run Privileged Tasks...
[  OK  ] Started LSB: Set sysfs variables from /etc/sysfs.conf.
[  OK  ] Started Network Manager Wait Online.
[  OK  ] Started Authenticate and Authorize Users to Run Privileged Tasks.
[  OK  ] Reached target Network is Online.
         Starting LSB: Start NTP daemon...
         Starting /etc/rc.local Compatibility...
         Starting LSB: Advanced IEEE 802.11 management daemon...
         Starting LSB: disk temperature monitoring daemon...
[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Started LSB: Advanced IEEE 802.11 management daemon.
[  OK  ] Started LSB: disk temperature monitoring daemon.
[  OK  ] Started LSB: Start NTP daemon.
[  OK  ] Started Serial Getty on ttyS0.
[  OK  ] Started Getty on tty1.
[  OK  ] Reached target Login Prompts.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.

Ubuntu 16.04.2 LTS orangepione ttyS0

orangepione login:

 

 


Good luck with distributions that works :)

Share this post


Link to post
Share on other sites
1 hour ago, Igor said:


Now it is.

I asked for serial console output to rule out possible board hardware troubles. We have seen that some boards failed to initialize with a modern u-boot which is used in just about every build. But since you rather waste my time than buying a serial console for 2USD this tells me that it's no use to help you. 

1. This image: https://dl.armbian.com/orangepione/Ubuntu_xenial_default.7z

2. Boot this way:

  Reveal hidden contents


U-Boot SPL 2017.05-armbian (Jun 13 2017 - 15:34:52)
DRAM: 512 MiB
Trying to boot from MMC1


U-Boot 2017.05-armbian (Jun 13 2017 - 15:34:52 +0200) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi One
DRAM:  512 MiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   phy interface0
eth0: ethernet@1c30000
Hit any key to stop autoboot:  0 
38518 bytes read in 147 ms (255.9 KiB/s)
Unknown command 'bmp' - try 'help'
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3565 bytes read in 195 ms (17.6 KiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
115 bytes read in 157 ms (0 Bytes/s)
5154669 bytes read in 512 ms (9.6 MiB/s)
4750952 bytes read in 510 ms (8.9 MiB/s)
Found legacy kernel configuration
34880 bytes read in 450 ms (75.2 KiB/s)
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    5154605 Bytes = 4.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

[sun8i_fixup]: From boot, get meminfo:
        Start:  0x40000000
        Size:   512MB
ion_carveout reserve: 160m@0 256m@0 130m@1 200m@1
ion_reserve_select: ion chipid  [0x2c00081!
ion_reserve_common: ion reserve: [0x56000000, 0x60000000]!
Loading, please wait...
starting version 229
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.27.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 
/dev/mmcblk0p1: clean, 48744/90432 files, 288129/361472 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

Welcome to Ubuntu 16.04.2 LTS!

[  OK  ] Reached target Encrypted Volumes.
[  OK  ] Set up automount Arbitrary Executab...ats File System Automount Point.
[  OK  ] Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Reached target Remote File Systems.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on Journal Socket.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Listening on fsck to fsckd communication Socket.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Created slice System Slice.
[  OK  ] Reached target Slices.
         Starting Restore / save the current clock...
         Starting Nameserver information manager...
         Starting Create list of required st... nodes for the current kernel...
[  OK  ] Created slice system-serial\x2dgetty.slice.
         Mounting Debug File System...
         Mounting POSIX Message Queue File System...
         Starting Set console keymap...
[  OK  ] Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Reached target Paths.
[  OK  ] Started Trigger resolvconf update for networkd DNS.
         Starting Remount Root and Kernel File Systems...
[  OK  ] Listening on Syslog Socket.
         Starting Load Kernel Modules...
[  OK  ] Listening on Journal Audit Socket.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Mounted Debug File System.
[  OK  ] Started Restore / save the current clock.
[  OK  ] Started Create list of required sta...ce nodes for the current kernel.
[  OK  ] Started Set console keymap.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Started Load Kernel Modules.
[  OK  ] Started Nameserver information manager.
[  OK  ] Reached target Network (Pre).
         Starting Apply Kernel Variables...
         Mounting FUSE Control File System...
         Activating swap /var/swap...
         Starting udev Coldplug all Devices...
         Starting Load/Save Random Seed...
         Starting Create Static Device Nodes in /dev...
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Activated swap /var/swap.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Started udev Coldplug all Devices.
         Starting udev Kernel Device Manager...
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /tmp...
[  OK  ] Reached target Swap.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Mounted /tmp.
[  OK  ] Started Entropy daemon using the HAVEGE algorithm.
[  OK  ] Reached target Local File Systems.
         Starting Armbian enhanced Log2Ram...
         Starting Raise network interfaces...
         Starting Set console font and keymap...
[  OK  ] Started Armbian enhanced Log2Ram.
[  OK  ] Started Set console font and keymap.
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
[  OK  ] Started ifup for eth0.
[  OK  ] Reached target Sound Card.
[  OK  ] Created slice system-getty.slice.
         Starting Journal Service...
[  OK  ] Started Journal Service.
[  OK  ] Started Raise network interfaces.
         Starting Flush Journal to Persistent Storage...
[  OK  ] Started Flush Journal to Persistent Storage.
         Starting Create Volatile Files and Directories...
[  OK  ] Started Create Volatile Files and Directories.
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Reached target System Initialization.
[  OK  ] Started Daily apt activities.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target Timers.
         Starting Armbian filesystem resize service...
[  OK  ] Started Armbian filesystem resize service.
[  OK  ] Reached target Basic System.
         Starting Login Service...
         Starting Permit User Sessions...
[  OK  ] Started Regular background program processing daemon.
         Starting LSB: Load kernel modules needed to enable cpufreq scaling...
         Starting LSB: Start/stop sysstat's sadc...
         Starting Save/Restore Sound Card State...
         Starting Daily apt activities...
         Starting LSB: Starts LIRC daemon....
         Starting System Logging Service...
         Starting LSB: Armbian gathering hardware information...
[  OK  ] Started D-Bus System Message Bus.
         Starting Network Manager...
[  OK  ] Started System Logging Service.
[  OK  ] Started Permit User Sessions.
[  OK  ] Started Save/Restore Sound Card State.
[  OK  ] Started LSB: Load kernel modules needed to enable cpufreq scaling.
[  OK  ] Started LSB: Armbian gathering hardware information.
[  OK  ] Started LSB: Start/stop sysstat's sadc.
[  OK  ] Started LSB: Starts LIRC daemon..
[  OK  ] Started Network Manager.
[  OK  ] Started Login Service.
         Starting Network Manager Script Dispatcher Service...
         Starting Network Manager Wait Online...
[  OK  ] Reached target Network.
[  OK  ] Started Unattended Upgrades Shutdown.
         Starting OpenBSD Secure Shell server...
         Starting LSB: set CPUFreq kernel parameters...
         Starting Set console scheme...
[  OK  ] Started OpenBSD Secure Shell server.
[  OK  ] Started Set console scheme.
[  OK  ] Started Network Manager Script Dispatcher Service.
         Starting Hostname Service...
[  OK  ] Started LSB: set CPUFreq kernel parameters.
[  OK  ] Started Hostname Service.
         Starting LSB: Set sysfs variables from /etc/sysfs.conf...
         Starting Authenticate and Authorize Users to Run Privileged Tasks...
[  OK  ] Started LSB: Set sysfs variables from /etc/sysfs.conf.
[  OK  ] Started Network Manager Wait Online.
[  OK  ] Started Authenticate and Authorize Users to Run Privileged Tasks.
[  OK  ] Reached target Network is Online.
         Starting LSB: Start NTP daemon...
         Starting /etc/rc.local Compatibility...
         Starting LSB: Advanced IEEE 802.11 management daemon...
         Starting LSB: disk temperature monitoring daemon...
[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Started LSB: Advanced IEEE 802.11 management daemon.
[  OK  ] Started LSB: disk temperature monitoring daemon.
[  OK  ] Started LSB: Start NTP daemon.
[  OK  ] Started Serial Getty on ttyS0.
[  OK  ] Started Getty on tty1.
[  OK  ] Reached target Login Prompts.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Started Update UTMP about System Runlevel Changes.

Ubuntu 16.04.2 LTS orangepione ttyS0

orangepione login:

 

 


Good luck with distributions that works :)

The ONLY thing a distro is supposed to provide is BOOT, the distro must the one to deal with low-level problems. If the low-level problems are not solved this is s DISTRO-DEVELOPER-ONLY distro.

 

You will never be any popular if you do not provide a sure boot, most people does not have time to deal with such incomplete software.

Share this post


Link to post
Share on other sites

So far you haven't proved anything while I provide you a specific evidence that image from download section works on Orange Pi One. Several hundred thousand happy users (don't worry about popularity) are another proof that you are doing something wrong and you refuse to accept. Act upon documentation, react to our bits of advice, ...

 

Except for stock junk (Android, Lubuntu, Raspbian), most 3rd party distribution and compilations are made on the top of our "distro-developers-junk" work. Why?

Share this post


Link to post
Share on other sites
51 minutes ago, garfius said:

The ONLY thing a distro is supposed to provide is BOOT,

 

Thanks for letting us know. We always thought a distro should allow to operate a board reliably which is simply impossible when ignoring a few basic requirements (eg. avoiding crappy SD cards and underpowering issues): https://forum.armbian.com/announcement/1-1-check-power-supply-check-sd-card-and-check-other-people-experiences/

 

53 minutes ago, garfius said:

the distro must the one to deal with low-level problems

 

Yes, the distro should run to the next shop and buy a reliable PSU and a SD card that does not suck. That's the distro's and only the distro's job!

 

54 minutes ago, garfius said:

If the low-level problems are not solved this is s DISTRO-DEVELOPER-ONLY distro

 

Exactly. We (the few developers) are able to use the distro also with crappy SD cards (since we can set the magical 'boot from crap' switch). No one else can do this. Ah, almost forgot. There are also a few thousand users following the recommendations above who you use Armbian on these cheap Chinese boards without any issues. You might think about what's the difference between them and you.

 

And now let's stop. Waste of time. Good luck with another distro :)  

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
1 1

  • Support the project

    We need your help to stay focused on the project.

    Choose the amount and currency you would like to donate in below.