Topics created by CAP 33

@crispyoz I bought another adapter with ASIX AX88179A chip. Reinstalled the following modules: kmod-mii kmod-usb-net kmod-usb-net-asix root@Omega-31F1:~# modprobe asix asix is already loaded root@Omega-31F1:~# modprobe usbnet usbnet is already loaded root@Omega-31F1:~# modprobe mii mii is already loaded Command dmesg | grep usbcore printed following: root@Omega-31F1:/etc/modules.d# dmesg | grep usbcore [ 5.391249] usbcore: registered new interface driver usbfs [ 5.396990] usbcore: registered new interface driver hub [ 5.402486] usbcore: registered new device driver usb [ 5.801747] usbcore: registered new interface driver usb-storage [ 17.632985] usbcore: registered new interface driver btusb [ 17.643265] usbcore: registered new interface driver cdc_acm [ 17.905698] usbcore: registered new interface driver ums-alauda [ 17.914983] usbcore: registered new interface driver ums-cypress [ 17.924496] usbcore: registered new interface driver ums-datafab [ 17.933704] usbcore: registered new interface driver ums-freecom [ 17.943042] usbcore: registered new interface driver ums-isd200 [ 17.955095] usbcore: registered new interface driver ums-jumpshot [ 17.964453] usbcore: registered new interface driver ums-karma [ 17.974610] usbcore: registered new interface driver ums-sddr09 [ 17.984034] usbcore: registered new interface driver ums-sddr55 [ 17.993874] usbcore: registered new interface driver ums-usbat [ 18.007211] usbcore: registered new interface driver usbhid [ 18.026860] usbcore: registered new interface driver usblp [ 18.067654] usbcore: registered new interface driver usbserial [ 18.073744] usbcore: registered new interface driver usbserial_generic [ 18.154428] usbcore: registered new interface driver asix [ 18.162642] usbcore: registered new interface driver ch341 [ 18.177852] usbcore: registered new interface driver cp210x [ 18.193761] usbcore: registered new interface driver ftdi_sio [ 18.222649] usbcore: registered new interface driver pl2303 [ 18.268377] usbcore: registered new interface driver snd-usb-audio [ 18.293507] usbcore: registered new interface driver uvcvideo [ 18.310592] usbcore: registered new interface driver option The problem is still not solved. Omega does not see the interface. Maybe this is due to the fact that the adapter has a USB 3.0 interface?

@CAP-33 Omega2+ is not that hot to burn your fingers. Your top output looks like a standard firmware, but it is possible that loadable modules can impact upon the load. Are you running Onion's latest firmware with no customisation? if not then this would be my first step, then see if this fixes the issue. How are you powering the dock? The best way to troubleshoot this is to bring everything back to standard. Standard firmware, powered from USB port of your computer. If after this it is still very hot, I think it may be a faulty device.

@CAP-33 This is like a DOS crosslink error on the FAT file system. To fix it you need to install the dosfstools. edit /etc/opkg/distfeeds.conf and uncomment line 1 opkg update opkg install dosfstools /usr/sbin/fsck.fat -f -l -a /dev/mmcblk0p1

@CAP-33 uhttpd is installed in the standard Omega firmware build and you can add php7 support. Take a look at this link: https://openwrt.org/docs/guide-user/services/webserver/php I find nginx performs a lot better than uhttpd, you can see the installation details here: https://openwrt.org/docs/guide-user/services/webserver/nginx

Sorry, I have been away for a few days. You did not answer about the input 0.47uF. Do you have it? When you measure the 3.1V output, what is the input from the 3.7V cell? If the drop across the LM3940 is 0.6V then that is out of spec. I have over 10 LM3940s in operation (some SMD, some TO220). None of them behaves like that. I can only guess yours is unstable (long wires or no 0.47uF) or the 3.7V is no longer 3.7V with the Omega2 connected or (very unlikely) the LM3940 is out of spec. I assume you are using a "real" LM3940 (ie reputable brand and not a counterfeit one). However, I doubt it would be a fake one because I cannot imagine there would be any money in making a fake version of such a cheap item. Regds, Dave

@CAP-33 wouldn't the logical conclusion be that your first step would be to upgrade to the latest firmware?

@CAP-33 You are correct this is a "drawback" of python. I find python has a lot of drawbacks That's why I develop my apps using C.

@crispyoz This method works. Thank you!

@György-Farkas Thanks!

@CAP-33 Try date -s YYMMDDhhmm.ss (eg. with date command of BusyBox v1.28.3). date -s 1904071301.00 Sun Apr 7 13:01:00 GMT 2019 If the date command of BusyBox is not enough for you then install the coreutils-date package - it's theoretically a full version of the standard GNU date utility. (As you know well: enable the 5th line of '/etc/opkg/distfeeds.conf', opkg update and opkg install coreutils-date.) date -s '19-04-07' Sun Apr 7 00:00:00 GMT 2019 To change only the date you can use shell command substitution in the date string: date -s "19-04-07 $(date +%H:%M:%S)" it will change the date and keep the time. # Omega2 Pro (light) FW v0.3.2 b218 root@Omega-5BE1:/# date -s '19-04-07 13:01:00' Sun Apr 7 13:01:00 GMT 2019 root@Omega-5BE1:/# date Sun Apr 7 13:01:02 GMT 2019 root@Omega-5BE1:/# date -s '19-04-07' Sun Apr 7 00:00:00 GMT 2019 root@Omega-5BE1:/# date Sun Apr 7 00:00:02 GMT 2019 root@Omega-5BE1:/# date -s '19-04-07 13:01:00' Sun Apr 7 13:01:00 GMT 2019 root@Omega-5BE1:/# date Sun Apr 7 13:01:02 GMT 2019 root@Omega-5BE1:/# date -s "19-04-07 $(date +%H:%M:%S)" Sun Apr 7 13:02:21 GMT 2019 root@Omega-5BE1:/# date Sun Apr 7 13:02:09 GMT 2019