• Before reporting problems with your board running Armbian, check the following:

    • 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.

Boot Time
0

11 posts in this topic

Hello, greetings from Bulgaria and thanks for the OS. We use Orange Pi Lite and something may be is problem. Full boot time is around 1 min and 15 sec, how can we degree this time because it's so slow? When we was with 5.23 distro it was around 45 sec with same SD card and power supply.

Share this post


Link to post
Share on other sites

Hi,

you have included no information.

Do you look at boot output?

 

try

systemd-analyze blame

best, gnasch

Share this post


Link to post
Share on other sites
 systemd-analyze blame output:

 

 

          5.171s networking.service

          5.171s networking.service

          5.171s networking.service

          5.171s networking.service

          2.736s armhwinfo.service

          2.422s isc-dhcp-server.service

          1.782s systemd-logind.service

          1.482s alsa-restore.service

          1.193s rsyslog.service

          1.159s systemd-user-sessions.service

          1.156s rc-local.service

          1.046s systemd-journal-flush.service

           899ms loadcpufreq.service

           809ms keyboard-setup.service

           769ms motion.service

           749ms systemd-udev-trigger.service

           739ms fake-hwclock.service

           709ms kmod-static-nodes.service

           706ms ntp.service

           689ms systemd-setup-dgram-qlen.service

           602ms lirc.service

           579ms systemd-modules-load.service

           559ms sysstat.service

           529ms hddtemp.service

           505ms hostapd.service

           429ms console-setup.service

           394ms dev-mqueue.mount

           379ms netfilter-persistent.service

           359ms systemd-tmpfiles-setup.service

           343ms sys-kernel-debug.mount

           339ms keymap.service

           309ms cpufrequtils.service

           279ms kbd.service

           279ms systemd-sysctl.service

           249ms systemd-tmpfiles-setup-dev.service

           249ms systemd-rfkill@rfkill0.service

           239ms udev-finish.service

           159ms hdparm.service

           149ms sys-fs-fuse-connections.mount

           146ms user@0.service

           129ms systemd-random-seed.service

           128ms var-swap.swap

            99ms systemd-update-utmp.service

            89ms systemd-remount-fs.service

            79ms sysfsutils.service

            72ms tmp.mount

            18ms systemd-update-utmp-runlevel.service

            15ms systemd-udevd.service

Share this post


Link to post
Share on other sites

here is mine on opi pc:

 systemd-analyze blame 
          6.009s shorewall.service                                                                                                                                                  
          4.820s armhwinfo.service                                                                                                                                                  
          2.048s rpimonitor.service                                                                                                                                                 
          2.016s alsa-restore.service                                                                                                                                               
          1.988s sec.service                                                                                                                                                        
          1.729s networking.service
          1.727s ifplugd.service
          1.521s rc-local.service
          1.279s hostapd.service
          1.269s hddtemp.service
          1.260s lirc.service
          1.208s gpm.service
          1.149s systemd-udev-trigger.service
          1.147s rpimonitor-helper.service
          1.129s loadcpufreq.service
          1.048s ntp.service
          1.019s systemd-setup-dgram-qlen.service
          1.004s systemd-journal-flush.service
           939ms fake-hwclock.service
           879ms keyboard-setup.service
           720ms dev-mqueue.mount
           647ms rsyslog.service
           639ms kmod-static-nodes.service
           623ms sys-kernel-debug.mount
           619ms blacklists.service
           619ms systemd-modules-load.service
           609ms keymap.service
           549ms systemd-user-sessions.service
           509ms console-setup.service
           499ms systemd-sysctl.service
           410ms kbd.service
           359ms cpufrequtils.service
           359ms systemd-tmpfiles-setup-dev.service
           319ms systemd-tmpfiles-setup.service
           214ms sys-fs-fuse-connections.mount
           209ms hdparm.service
           199ms systemd-random-seed.service
           191ms var-swap.swap
           189ms udev-finish.service
           169ms shorewall6.service
           159ms systemd-update-utmp.service
           115ms user@0.service
           114ms systemd-logind.service
           113ms systemd-udevd.service
            89ms sysfsutils.service
            79ms systemd-remount-fs.service
            43ms systemd-update-utmp-runlevel.service
            42ms systemd-tmpfiles-clean.service
            11ms tmp.mount

is there a problem with network or name resolution?

dns timeouts?

 

gnasch

Share this post


Link to post
Share on other sites

I have dongle rtl8192cu it is so big garbage, until now i have some drivers for it but it crushes some times and have unstable connection. Try these drivers from git hub: 

 

https://github.com/pvaret/rtl8192cu-fixes

 

and no improvement. Any suggestions?

 

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.

Share this post


Link to post
Share on other sites

The second problem is the usb camera. It require reboot to be ok, if i disconnect the power supply and plug it in, it doesn't recognize the usb camera properly (almost in 70-80% of the test cases)

 

dmesg output:

[    1.230073] usb 3-1: new high-speed USB device number 2 using sunxi-ehci
[    5.198897] usbcore: registered new interface driver rtl8192cu
[    5.211860] usbcore: registered new interface driver uvcvideo
 
 
lsusb output:
Bus 003 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
Bus 006 Device 002: ID 058f:3822 Alcor Micro Corp.
 
 
lsmod output:
uvcvideo               58868  1
ir_lirc_codec           3650  0
lirc_dev                7834  1 ir_lirc_codec
ir_mce_kbd_decoder      2885  0
ir_sanyo_decoder        1480  0
ir_sony_decoder         1422  0
8192cu                520861  0
 
 
But when i start mjpeg streamer:
 MJPG Streamer Version: svn rev: 3:172
 i: Using V4L2 device.: /dev/video0
 i: Desired Resolution: 1280 x 720
 i: Frames Per Second.: 15
 i: Format............: MJPEG
i: The format asked unavailable, so the width 640 height 480
 o: www-folder-path...: /usr/local/www/
 o: HTTP TCP port.....: 8080
 o: username:password.: disabled
 o: commands..........: disabled
 
 
and V4L output:
v4l2-ctl --list-formats-ext
ioctl: VIDIOC_ENUM_FMT
        Index       : 0
        Type        : Video Capture
        Pixel Format: 'MJPG' (compressed)
        Name        : MJPEG
                Size: Discrete 640x480
                        Interval: Discrete 0.033s (30.000 fps)
                Size: Discrete 160x120
                        Interval: Discrete 0.033s (30.000 fps)
 
 
 
So after a reboot wifi dongle may be work good may be not, the camera always is good after reboot.
 
v4l output after a reboot:
ioctl: VIDIOC_ENUM_FMT
        Index       : 0
        Type        : Video Capture
        Pixel Format: 'MJPG' (compressed)
        Name        : MJPEG
                Size: Discrete 1280x720
                        Interval: Discrete 0.033s (30.000 fps)
                Size: Discrete 800x600
                        Interval: Discrete 0.033s (30.000 fps)
                Size: Discrete 640x480
                        Interval: Discrete 0.033s (30.000 fps)
                Size: Discrete 640x360
                        Interval: Discrete 0.033s (30.000 fps)
                Size: Discrete 320x240
                        Interval: Discrete 0.033s (30.000 fps)
                Size: Discrete 160x120
                        Interval: Discrete 0.033s (30.000 fps)
 
        Index       : 1
        Type        : Video Capture
        Pixel Format: 'YUYV'
        Name        : YUV 4:2:2 (YUYV)
                Size: Discrete 1280x720
                        Interval: Discrete 0.100s (10.000 fps)
                Size: Discrete 800x600
                        Interval: Discrete 0.100s (10.000 fps)
                Size: Discrete 640x480
                        Interval: Discrete 0.033s (30.000 fps)
                Size: Discrete 640x360
                        Interval: Discrete 0.033s (30.000 fps)
                Size: Discrete 320x240
                        Interval: Discrete 0.033s (30.000 fps)
                Size: Discrete 160x120
                        Interval: Discrete 0.033s (30.000 fps)
 
 
So what is going on here, wifi dongle is shit ok, can u provide me a link to 5.20 distro for OPI Lite so i can check it if the drivers will be fine for the dongle and the camera and why the boot time is so high, because of the network services that starts ( we have ap on wlan0 and dongle on wlan1 who is connect to the internet)? 

Share this post


Link to post
Share on other sites

Most likely the device does not get enough power check used cable and charger.

 

 

The second problem is the usb camera. It require reboot to be ok, if i disconnect the power supply and plug it in, it doesn't recognize the usb camera properly (almost in 70-80% of the test cases)

 

So what is going on here, wifi dongle is shit ok, can u provide me a link to 5.20 distro for OPI Lite so i can check it if the drivers will be fine for the dongle and the camera and why the boot time is so high, because of the network services that starts ( we have ap on wlan0 and dongle on wlan1 who is connect to the internet)? 

 

Share this post


Link to post
Share on other sites

2000mA standard power supply, if it was the problem why after the reboot make changes. And the interesting here is on first use the camera is on bus 006 and the dongle is no 002 after the reboot camera goes to bus 002 and the dongle go to 003...

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

Hmmm i guess ill need other type of charger because this one is from Orange Pi factory and its without removable cable.... But some other news are on 5.25 clean distro with  8192cu-fixed driver from git hub the dongle work fine, may be the problem was during the upgrade from 5.23 to 5.25. But the problem with the camera is the same. Boot time is low because of hostap services (around 25 sec to load them all) and the camera just don't wanna 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
0

  • 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.