Nikolai Asparuhov Posted February 17, 2017 Posted February 17, 2017 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.
gnasch Posted February 17, 2017 Posted February 17, 2017 Hi, you have included no information. Do you look at boot output? try systemd-analyze blame best, gnasch
Nikolai Asparuhov Posted February 17, 2017 Author Posted February 17, 2017 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
gnasch Posted February 17, 2017 Posted February 17, 2017 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
Nikolai Asparuhov Posted February 18, 2017 Author Posted February 18, 2017 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?
Igor Posted February 18, 2017 Posted February 18, 2017 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.
Nikolai Asparuhov Posted February 18, 2017 Author Posted February 18, 2017 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)?
jkajolin Posted February 18, 2017 Posted February 18, 2017 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)?
Nikolai Asparuhov Posted February 18, 2017 Author Posted February 18, 2017 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...
Igor Posted February 18, 2017 Posted February 18, 2017 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
Nikolai Asparuhov Posted February 19, 2017 Author Posted February 19, 2017 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
Recommended Posts