belfastraven Posted November 23, 2018 Posted November 23, 2018 Re Pine64 WiFi. Using a USB Wifi adapter, WiFi is fine. The Wifi/bluetooth module told by Piine64 is not working. I can load the driver, but the SDIO device is not being enumerated. Still looking into the issue...
martinayotte Posted November 23, 2018 Posted November 23, 2018 25 minutes ago, belfastraven said: but the SDIO device is not being enumerated. It is probably something missing in the Main DT.
belfastraven Posted November 23, 2018 Posted November 23, 2018 Yes--and there isn't an overlay for it either. I'm looking around to see if I can find a dt somewhere which has a node for it... I'm very new to dt's :-)
vlad59 Posted November 23, 2018 Posted November 23, 2018 23 minutes ago, martinayotte said: It is probably something missing in the Main DT. Strange wifi is working on my Pine64 but I have an old SDIO adaptor : root@pine64:~# dmesg | grep 8723 [ 5.240274] r8723bs: module is from the staging directory, the quality is unknown, you have been warned. [ 5.287430] RTL8723BS: module init start [ 5.287439] RTL8723BS: rtl8723bs v4.3.5.5_12290.20140916_BTCOEX20140507-4E40 [ 5.287441] RTL8723BS: rtl8723bs BT-Coex version = BTCOEX20140507-4E40 [ 5.397757] RTL8723BS: rtw_ndev_init(wlan0) [ 5.406514] RTL8723BS: module init ret =0 [ 16.270611] rtl8723bs: acquire FW from file:rtlwifi/rtl8723bs_nic.bin
martinayotte Posted November 23, 2018 Posted November 23, 2018 29 minutes ago, vlad59 said: Strange wifi is working on my Pine64 but I have an old SDIO adaptor Using which kernel ? I don't see any SDIO node in Mainline 4.19.y DT for Pine64 ...
vlad59 Posted November 23, 2018 Posted November 23, 2018 2 hours ago, martinayotte said: Using which kernel ? I don't see any SDIO node in Mainline 4.19.y DT for Pine64 ... Latest build from Armbian dev 4.19.2
belfastraven Posted November 23, 2018 Posted November 23, 2018 Yes, I just tried another pine64 sdio adapter and device is now working. I don't know how I managed to kill the first one.. 5.433718] r8723bs: module is from the staging directory, the quality is unknown, you have been warned. [ 5.481983] RTL8723BS: module init start [ 5.481994] RTL8723BS: rtl8723bs v4.3.5.5_12290.20140916_BTCOEX20140507-4E40 [ 5.481997] RTL8723BS: rtl8723bs BT-Coex version = BTCOEX20140507-4E40 [ 5.522202] RTL8723BS: rtw_ndev_init(wlan0) [ 5.524817] RTL8723BS: module init ret =0 [ 10.488627] rtl8723bs: acquire FW from file:rtlwifi/rtl8723bs_nic.bin [ 14.397509] RTL8723BS: rtw_set_802_11_connect(wlan0) fw_state = 0x00000008 [ 14.535050] RTL8723BS: start auth [ 14.537783] RTL8723BS: auth success, start assoc [ 14.548427] RTL8723BS: rtw_cfg80211_indicate_connect(wlan0) BSS not found !! [ 14.548446] RTL8723BS: assoc success [ 14.558911] RTL8723BS: send eapol packet [ 14.580272] RTL8723BS: send eapol packet [ 14.618036] RTL8723BS: set pairwise key camid:4, addr:92:3b:ad:ad:a7:34, kid:0, type:AES [ 14.618588] RTL8723BS: set group key camid:5, addr:92:3b:ad:ad:a7:34, kid:1, type:AES I haven't checked bluetooth yet. It isn't defined in the megous linux DTS, but from Anarsouls-- Defined here in Anarsouls DTS /* On Wifi/BT connector, with RTS/CTS */ &uart1 { pinctrl-names = "default"; pinctrl-0 = <&uart1_pins>, <&uart1_rts_cts_pins>; status = "okay"; bluetooth { compatible = "realtek,rtl8723bs-bt"; reset-gpios = <&r_pio 0 4 GPIO_ACTIVE_LOW>; /* PL4 */ device-wake-gpios = <&r_pio 0 5 GPIO_ACTIVE_HIGH>; /* PL5 */ host-wake-gpios = <&r_pio 0 6 GPIO_ACTIVE_HIGH>; /* PL6 */ firmware-postfix = "pine64"; }; };
vlad59 Posted November 23, 2018 Posted November 23, 2018 @belfastraven It's great you also got it working. I bought 3 pine64 + 3 SDIO Wifi / BT addons and I got a faulty one, fortunately I tested all 3 three and I got another one for free ;). About bluetooth I also saw Anarsoul kernel, In case you didn't saw you may have to tweak the firmware blobs : * https://forum.manjaro.org/t/bluetooth-not-working-with-rtl8723bs-bt/51906/10 * https://github.com/lwfinger/rtl8723bs_bt/issues/28#issuecomment-432806835 If nobody beats me to it, I'll probably try to fix bluetooth next week.
lomady Posted November 23, 2018 Posted November 23, 2018 On 11/18/2018 at 9:54 PM, Igor said: Mine hanged with current stock settings already at first boot ... then I tried orangepipc2 DT and ... it looks fine. I notice DT is missing regulator bits and after adding them ... at least that problem is gone. I did several reboots and cold starts. At one cold start it hanged ... Not sure if everything is fine yet. @IgorShould this update be available via apt-get update && apt-get upgrade? Look like daily builds stopped on Nov 18th
martinayotte Posted November 23, 2018 Posted November 23, 2018 2 hours ago, vlad59 said: 4 hours ago, martinayotte said: Using which kernel ? I don't see any SDIO node in Mainline 4.19.y DT for Pine64 ... Latest build from Armbian dev 4.19.2 Still strange ... Are you using pinebook image on a pine64 board ? Because the SDIO node doesn't exist on Pine64 DT, but it is there for Pinebook ...
belfastraven Posted November 24, 2018 Posted November 24, 2018 FWIW, with my working hardware module, this is where the device enumerates. /sys/bus/sdio/devices/mmc1:0001:1 wlan0 show up in that directory tree. and there is this entry in the device tree: &mmc1 { pinctrl-names = "default"; pinctrl-0 = <&mmc1_pins>; vmmc-supply = <®_dldo4>; vqmmc-supply = <®_eldo1>; mmc-pwrseq = <&wifi_pwrseq>; non-removable; bus-width = <4>; status = "okay"; }; I just compiled a dtb with the bluetooth node, and will see what else it takes to make bluetooth work. vlad59 gave a lot of helpful information in his last post, also. I know that the wifi driver and firmware were loaded automatically at boot, once the hardware module was recognized. I notice that Bluetooth enabling can be done in armbian-config, but am not sure what has to be in place for that to work.
Igor Posted November 24, 2018 Author Posted November 24, 2018 11 hours ago, lomady said: Look like daily builds stopped on Nov 18th ATF for building H6 boards is broken and building stops. Somebody needs to fix. 1
Perier Posted November 24, 2018 Posted November 24, 2018 Orange Pi Zero Plus (H5) http://ix.io/1ujE I can not understand what kind of error or what is it connected with? (present since version 4.14.y) [ 6.888226] 29 [ 6.888237] 81 [ 6.888239] 03 [ 6.888241] CC [ 6.888243] 00 [ 6.888245] 00 [ 6.888247] 50 [ 6.888249] 00 [ 6.888251] 00 [ 6.888253] 00 [ 6.888255] 04 [ 6.888257] CC [ 6.888259] 0A [ 6.888262] 0C [ 6.888264] 00 [ 6.888266] 00 [ 6.888268] FF and other errors: Spoiler [ 2.170832] usb_phy_generic usb_phy_generic.0.auto: usb_phy_generic.0.auto supply vcc not found, using dummy regular [ 4.042684] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 4.682287] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 4.682298] cpu cpu0: _opp_add: OPP not supported by regulators (1056000000) [ 4.682395] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 4.682402] cpu cpu0: _opp_add: OPP not supported by regulators (1104000000) [ 4.682482] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 4.682488] cpu cpu0: _opp_add: OPP not supported by regulators (1152000000) [ 4.682592] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator [ 4.682602] cpu cpu0: _opp_add: OPP not supported by regulators (1200000000) [ 4.682671] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator [ 4.682679] cpu cpu0: _opp_add: OPP not supported by regulators (1224000000) [ 4.682785] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator [ 4.682793] cpu cpu0: _opp_add: OPP not supported by regulators (1248000000) [ 4.682862] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator [ 4.682868] cpu cpu0: _opp_add: OPP not supported by regulators (1296000000) [ 4.682975] core: _opp_supported_by_regulators: OPP minuV: 1400000 maxuV: 1400000, not supported by regulator [ 4.682981] cpu cpu0: _opp_add: OPP not supported by regulators (1344000000) [ 4.683058] core: _opp_supported_by_regulators: OPP minuV: 1400000 maxuV: 1400000, not supported by regulator [ 4.683065] cpu cpu0: _opp_add: OPP not supported by regulators (1368000000) [ 4.683579] thermal thermal_zone1: binding zone cpu-thermal with cdev thermal-cpufreq-0 failed:-22 [ 4.797299] thermal thermal_zone0: failed to read out thermal zone (-110) [ 4.797358] OF: /thermal-zones/cpu-thermal: arguments longer than property [ 4.797373] thermal thermal_zone2: failed to read out thermal zone (-110) [ 9.069655] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW platform regulatory.0 (error) - appeared in the dev branch, there is none in the mainline branch CPU temp, without heatsink: Spoiler root@orangepizeroplus:~# armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 17:54:07: 480MHz 0.00 2% 0% 1% 0% 0% 0% 65.9°C 3/6 17:54:13: 480MHz 0.00 0% 0% 0% 0% 0% 0% 63.9°C 0/6 17:54:18: 480MHz 0.00 0% 0% 0% 0% 0% 0% 57.2°C 0/6 17:54:23: 480MHz 0.00 0% 0% 0% 0% 0% 0% 60.7°C 0/6 17:54:28: 480MHz 0.00 0% 0% 0% 0% 0% 0% 63.0°C 0/6 17:54:33: 480MHz 0.00 0% 0% 0% 0% 0% 0% 63.5°C 0/6 17:54:38: 480MHz 0.00 0% 0% 0% 0% 0% 0% 62.2°C 0/6 17:54:43: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.0°C 0/6 17:54:48: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.1°C 0/6 17:54:54: 480MHz 0.07 0% 0% 0% 0% 0% 0% 63.8°C 0/6 17:54:59: 480MHz 0.07 0% 0% 0% 0% 0% 0% 62.5°C 0/6 17:55:04: 480MHz 0.06 0% 0% 0% 0% 0% 0% 62.7°C 0/6 17:55:09: 480MHz 0.06 0% 0% 0% 0% 0% 0% 64.7°C 0/6 17:55:14: 480MHz 0.05 0% 0% 0% 0% 0% 0% 63.2°C 0/6 Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 17:55:19: 480MHz 0.05 0% 0% 0% 0% 0% 0% 63.1°C 0/6 17:55:24: 480MHz 0.04 0% 0% 0% 0% 0% 0% 64.3°C 0/6 17:55:29: 480MHz 0.04 0% 0% 0% 0% 0% 0% 64.1°C 0/6 17:55:34: 480MHz 0.04 0% 0% 0% 0% 0% 0% 62.1°C 0/6 17:55:40: 480MHz 0.03 0% 0% 0% 0% 0% 0% 65.0°C 0/6 17:55:45: 480MHz 0.03 0% 0% 0% 0% 0% 0% 63.4°C 0/6 17:55:50: 480MHz 0.03 0% 0% 0% 0% 0% 0% 63.7°C 0/6 17:55:55: 480MHz 0.02 0% 0% 0% 0% 0% 0% 64.7°C 0/6 17:56:00: 480MHz 0.02 0% 0% 0% 0% 0% 0% 64.5°C 0/6 17:56:05: 480MHz 0.02 0% 0% 0% 0% 0% 0% 63.7°C 0/6 17:56:10: 480MHz 0.02 0% 0% 0% 0% 0% 0% 64.1°C 0/6 17:56:15: 480MHz 0.02 0% 0% 0% 0% 0% 0% 64.5°C 0/6 17:56:21: 480MHz 0.02 0% 0% 0% 0% 0% 0% 63.0°C 0/6 17:56:26: 480MHz 0.01 0% 0% 0% 0% 0% 0% 63.1°C 0/6 17:56:31: 480MHz 0.01 0% 0% 0% 0% 0% 0% 65.1°C 3/6 Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 17:56:36: 480MHz 0.01 0% 0% 0% 0% 0% 0% 63.2°C 0/6 17:56:41: 480MHz 0.01 0% 0% 0% 0% 0% 0% 63.0°C 0/6 17:56:46: 480MHz 0.01 0% 0% 0% 0% 0% 0% 64.6°C 0/6 17:56:51: 480MHz 0.01 0% 0% 0% 0% 0% 0% 66.0°C 3/6 17:56:56: 480MHz 0.01 0% 0% 0% 0% 0% 0% 64.4°C 0/6 17:57:01: 480MHz 0.01 0% 0% 0% 0% 0% 0% 64.3°C 0/6 17:57:07: 480MHz 0.01 0% 0% 0% 0% 0% 0% 63.8°C 0/6 17:57:12: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.1°C 3/6 17:57:17: 480MHz 0.00 0% 0% 0% 0% 0% 0% 63.9°C 0/6 17:57:22: 480MHz 0.00 0% 0% 0% 0% 0% 0% 66.0°C 3/6 17:57:27: 480MHz 0.00 0% 0% 0% 0% 0% 0% 63.3°C 0/6 17:57:32: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.7°C 3/6 17:57:37: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.6°C 0/6 17:57:42: 480MHz 0.00 0% 0% 0% 0% 0% 0% 63.8°C 0/6 17:57:48: 480MHz 0.00 1% 0% 0% 0% 0% 0% 64.7°C 0/6 Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 17:57:53: 480MHz 0.00 0% 0% 0% 0% 0% 0% 66.5°C 3/6 17:57:58: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.5°C 3/6 17:58:03: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.4°C 0/6 17:58:08: 480MHz 0.00 0% 0% 0% 0% 0% 0% 66.0°C 3/6 17:58:13: 480MHz 0.00 0% 0% 0% 0% 0% 0% 63.8°C 0/6 17:58:18: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.7°C 0/6 17:58:23: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.7°C 0/6 17:58:28: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.7°C 0/6 17:58:34: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.7°C 3/6 17:58:39: 480MHz 0.07 0% 0% 0% 0% 0% 0% 66.3°C 0/6 17:58:44: 480MHz 0.07 0% 0% 0% 0% 0% 0% 66.2°C 0/6 17:58:49: 480MHz 0.06 0% 0% 0% 0% 0% 0% 64.3°C 0/6 17:58:54: 480MHz 0.06 0% 0% 0% 0% 0% 0% 64.0°C 0/6 17:58:59: 480MHz 0.05 0% 0% 0% 0% 0% 0% 64.3°C 0/6 17:59:04: 480MHz 0.05 0% 0% 0% 0% 0% 0% 64.5°C 0/6 Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 17:59:09: 480MHz 0.04 0% 0% 0% 0% 0% 0% 64.4°C 0/6 17:59:15: 480MHz 0.04 0% 0% 0% 0% 0% 0% 64.1°C 0/6 17:59:20: 480MHz 0.04 0% 0% 0% 0% 0% 0% 66.4°C 3/6 17:59:25: 480MHz 0.03 0% 0% 0% 0% 0% 0% 65.3°C 3/6 17:59:30: 480MHz 0.03 0% 0% 0% 0% 0% 0% 65.2°C 3/6 17:59:35: 480MHz 0.03 0% 0% 0% 0% 0% 0% 64.9°C 0/6 17:59:40: 480MHz 0.02 0% 0% 0% 0% 0% 0% 65.7°C 3/6 17:59:45: 480MHz 0.02 0% 0% 0% 0% 0% 0% 66.4°C 3/6 17:59:50: 480MHz 0.02 0% 0% 0% 0% 0% 0% 64.9°C 0/6 17:59:55: 480MHz 0.02 0% 0% 0% 0% 0% 0% 62.5°C 0/6 18:00:01: 480MHz 0.02 0% 0% 0% 0% 0% 0% 64.9°C 0/6 18:00:06: 480MHz 0.02 1% 0% 0% 0% 0% 0% 65.6°C 3/6 18:00:11: 480MHz 0.01 0% 0% 0% 0% 0% 0% 66.4°C 3/6 18:00:16: 480MHz 0.01 0% 0% 0% 0% 0% 0% 66.4°C 3/6 18:00:21: 480MHz 0.01 0% 0% 0% 0% 0% 0% 65.7°C 3/6 Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 18:00:26: 480MHz 0.01 0% 0% 0% 0% 0% 0% 65.7°C 3/6 18:00:31: 480MHz 0.01 0% 0% 0% 0% 0% 0% 64.7°C 0/6 18:00:36: 480MHz 0.01 0% 0% 0% 0% 0% 0% 64.4°C 0/6 18:00:41: 480MHz 0.01 0% 0% 0% 0% 0% 0% 63.4°C 0/6 18:00:47: 480MHz 0.01 0% 0% 0% 0% 0% 0% 65.6°C 3/6 18:00:52: 480MHz 0.01 0% 0% 0% 0% 0% 0% 65.0°C 0/6 18:00:57: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.1°C 3/6 18:01:02: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.3°C 3/6 18:01:07: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.7°C 3/6 18:01:12: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.8°C 3/6 18:01:17: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.4°C 0/6 18:01:22: 480MHz 0.00 0% 0% 0% 0% 0% 0% 63.7°C 0/6 18:01:28: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.5°C 3/6 18:01:33: 480MHz 0.00 0% 0% 0% 0% 0% 0% 66.2°C 0/6 18:01:38: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.3°C 0/6 Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 18:01:43: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.1°C 3/6 18:01:48: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.5°C 3/6 18:01:53: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.0°C 0/6 18:01:58: 480MHz 0.00 0% 0% 0% 0% 0% 0% 62.5°C 0/6 18:02:03: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.6°C 0/6 18:02:08: 480MHz 0.00 0% 0% 0% 0% 0% 0% 65.8°C 3/6 18:02:14: 480MHz 0.00 0% 0% 0% 0% 0% 0% 66.3°C 3/6 18:02:19: 480MHz 0.00 0% 0% 0% 0% 0% 0% 64.6°C 0/6 18:02:24: 480MHz 0.08 0% 0% 0% 0% 0% 0% 65.3°C 3/6 18:02:29: 480MHz 0.07 0% 0% 0% 0% 0% 0% 63.8°C 0/6 18:02:34: 480MHz 0.06 0% 0% 0% 0% 0% 0% 66.5°C 3/6 18:02:39: 480MHz 0.06 0% 0% 0% 0% 0% 0% 63.7°C 0/6 18:02:44: 480MHz 0.05 0% 0% 0% 0% 0% 0% 64.6°C 0/6 18:02:49: 480MHz 0.05 0% 0% 0% 0% 0% 0% 63.5°C 0/6 18:02:55: 480MHz 0.04 0% 0% 0% 0% 0% 0% 63.9°C 0/6 Time CPU load %cpu %sys %usr %nice %io %irq CPU C.St. 18:03:00: 480MHz 0.04 0% 0% 0% 0% 0% 0% 64.3°C 0/6 18:03:05: 480MHz 0.04 0% 0% 0% 0% 0% 0% 63.7°C 0/6 18:03:10: 480MHz 0.03 0% 0% 0% 0% 0% 0% 64.4°C 0/6 18:03:15: 480MHz 0.03 0% 0% 0% 0% 0% 0% 63.0°C 0/6 18:03:20: 480MHz 0.03 0% 0% 0% 0% 0% 0% 63.8°C 0/6 18:03:25: 480MHz 0.02 0% 0% 0% 0% 0% 0% 65.1°C 3/6 18:03:30: 480MHz 0.02 0% 0% 0% 0% 0% 0% 64.3°C 0/6 18:03:35: 480MHz 0.02 0% 0% 0% 0% 0% 0% 62.4°C 0/6 18:03:41: 480MHz 0.02 0% 0% 0% 0% 0% 0% 65.5°C 3/6 18:03:46: 480MHz 0.02 0% 0% 0% 0% 0% 0% 64.7°C 0/6 18:03:51: 480MHz 0.02 0% 0% 0% 0% 0% 0% 64.5°C 0/6 18:03:56: 480MHz 0.01 0% 0% 0% 0% 0% 0% 64.4°C 0/6 18:04:01: 480MHz 0.01 0% 0% 0% 0% 0% 0% 65.0°C 0/6^C
TonyMac32 Posted November 25, 2018 Posted November 25, 2018 @Evgeny would you be able to put the code blocks into the Spoiler containers so they don't hog an entire page? As to the question, I assume the Opi zero plus has a "dumb" regulator setup with no voltage switching? (OK, found it, it will do 1.1 and 1.3V). Basically you have no voltage to support those higher operating points, the processor will theoretically fall on it's face if you tried. As for the temp and random hex showing up, I do not know.
Perier Posted November 25, 2018 Posted November 25, 2018 1 hour ago, TonyMac32 said: @Evgeny would you be able to put the code blocks into the Spoiler containers so they don't hog an entire page? As to the question, I assume the Opi zero plus has a "dumb" regulator setup with no voltage switching? (OK, found it, it will do 1.1 and 1.3V). Basically you have no voltage to support those higher operating points, the processor will theoretically fall on it's face if you tried. As for the temp and random hex showing up, I do not know. Thank you for a hint about a spoiler (corrected) HEX-error migrated from the mainline 4.14.y
Igor Posted November 25, 2018 Author Posted November 25, 2018 1 hour ago, TonyMac32 said: As for the temp and random hex showing up, I do not know. It's related to wireless drivers, probably showing firmware loading progress. In any case safe to ignore.
Perier Posted November 25, 2018 Posted November 25, 2018 9 minutes ago, Igor said: It's related to wireless drivers, probably showing firmware loading progress. In any case safe to ignore. But how did you determine that the problem in loading wireless drivers? (for own development)
Werner Posted November 25, 2018 Posted November 25, 2018 On 11/24/2018 at 9:22 AM, Igor said: ATF for building H6 boards is broken and building stops. Somebody needs to fix. Fixed...maybe. Just give it a shot. @lomady
guidol Posted November 26, 2018 Posted November 26, 2018 Yesterday I did compile 2 variants: Armbian_5.67_Orangepizeroplus_Debian_stretch_dev_4.19.4 and Armbian_5.67_Orangepizeroplus2-h5_Debian_stretch_dev_4.19.4 The OPi Zero Plus (a H5) does boot and I did create a report. The OPi Zero Plus2 H5 doesnt seem to boot (right) I got no serial TTL-Port connected, because I do use the original black Cube-Case, but I can see the green Power LED and a few seconds a red Heartbeat while powering up. But after the 1.-2 seconds the Heartbeat will go out and no HDMI, Ethernet (USB activity - which normally works as eth0 DHCP) So from me no report for the OPi Zero Plus2 H5 at this timePS: I have to check the flashing of the card, because etcher version did jump from 1.4.5 to 1.4.8 Named now BalenaEtcher with a new Icon and Adverts
Igor Posted November 26, 2018 Author Posted November 26, 2018 2 hours ago, guidol said: The OPi Zero Plus2 H5 doesnt seem to boot (right) Yes, there is something wrong ... with/around powering wireless. I haven't resolved yet. 2 hours ago, guidol said: Named now BalenaEtcher with a new Icon and Adverts Is there any libretcher?
guidol Posted November 26, 2018 Posted November 26, 2018 24 minutes ago, Igor said: Is there any libretcher? Nope 1.4.7 renamed etcher to balena-etcher and 1.4.8 does include now the "featured project" advert etcher changelog: Spoiler Change Log All notable changes to this project will be documented in this file. This project adheres to Semantic Versioning. v1.4.8 - 2018-11-23 Features Added featured-project while flashing Fixes Moved back the write cancel button Reject drives with null size (fixes pretty-bytes error) v1.4.7 - 2018-11-12 Fixes Fix typo in contributing guidelines Modify versionist.conf.js to match new internal commit guidelines Misc Rename etcher to balena-etcher Convert Select Image button to Rendition v1.4.6 - 2018-10-28 Fixes Provide a Buffer to xxhash.Stream Fix 64 bit detection on arm Fix incorrect file constraint path Fix flash cancel button interaction Misc Add new balena.io logos Use Resin CI scripts to build Etcher Enable React lint rules Convert Progress Button to Rendition v1.4.5 - 2018-10-11 Features Center content independent to window resolution. Add electron-native file-picker component. Hide unsafe mode option toggle with an env var. Use new design background color and drive step size ordering. Add a convenience Storage class on top of localStorage. Introduce env var to toggle autoselection of all drives. Add font-awesome. Add support for configuration files Use GTK-3 darkTheme mode. Add environment variable to toggle fullscreen. Allow blacklisting of drives through and environment variable ETCHER_BLACKLISTED_DRIVES. Show selected drives below drive selection step. Add a button to cancel the flash process. Download usbboot drivers installer when clicking a driverless usbboot device on Windows. Allow disabling links and hiding help link with an env var. Fixes Add "make webpack" to travis-ci build script Makefile: Don't use tilde in rpm versions Change Spectron port so not to overlap with other builds Fix multi-writes analytics by reusing existing logic in multi-write events. Load usbboot adapter on start on GNU/Linux if running as root. Misc Update drivelist to v6.4.2 Add instructions for installing and uninstalling on Solus.
guidol Posted November 26, 2018 Posted November 26, 2018 On 11/16/2018 at 8:48 AM, TonyMac32 said: I see NanoPi K1+ is done already, so my work here is done. :-) I did create a report for NanoPi K1 Plus-dev, but using the HDMI-console image (not Desktop). I'll use Desktop on SBCs when I got one with 4Gb of Ram - 2GB is not much enough for GUI and Web-Browser in my opinion
TonyMac32 Posted November 26, 2018 Posted November 26, 2018 For 64-bit you are probably correct. On the other side, the Tinker board web browses quite well with it's 2GB of RAM. Sent from my Pixel using Tapatalk
lomady Posted November 27, 2018 Posted November 27, 2018 (edited) On 11/18/2018 at 9:54 PM, Igor said: Mine hanged with current stock settings already at first boot ... then I tried orangepipc2 DT and ... it looks fine. I notice DT is missing regulator bits and after adding them ... at least that problem is gone. I did several reboots and cold starts. At one cold start it hanged ... Not sure if everything is fine yet. Did another fresh install and switch to daily dev 27 Nov. Cold boot hangs at various stages with HDMI image distortions: Spoiler I am sure that my Orange PC Prime is not defective because I have stress tested it with official Arch linux image (kernel 3.10) Since I got two of these boards - I tried another one. It boots but with kernel oops'es at random: Spoiler Can I suggest that it is something with DDR settings? Edited November 27, 2018 by lomady Tried second board
vlad59 Posted November 27, 2018 Posted November 27, 2018 In case that's useful, I reinstalled my Orange Pi +2E with latest DEV image. Everything seems to work (I can send a report if needed but the current one is quite recent). This morning I checked `dmesg` output for something else and I saw these three red lines (full armbianmonitor output is http://ix.io/1uAk) [ 6.087868] sun4i-codec 1c22c00.codec: ASoC: codec-analog@1f015c0 not registered [ 6.087882] sun4i-codec 1c22c00.codec: Failed to register our card [ 6.140691] sun8i_ths 1c25000.thermal-sensor: no memory resources defined I have no way to check if audio is working for now (I'm at work). But I checked DVFS / Thermal protection and it's works perfectly fine.
hojnikb Posted November 27, 2018 Posted November 27, 2018 Any easy way to modify DVFS tables ? Or perhaps set a set frequency for testing purposes. I'd like to test out each frequency point (and do some undervolting) to see how power consumption responds. This used to be doable with a single command, not sure if it's possible now on newer kernel. Thanks
Igor Posted November 27, 2018 Author Posted November 27, 2018 31 minutes ago, hojnikb said: Any easy way to modify DVFS tables ? Or perhaps set a set frequency for testing purposes. I'd like to test out each frequency point (and do some undervolting) to see how power consumption responds. This used to be doable with a single command, not sure if it's possible now on newer kernel. Thanks For H6?https://github.com/armbian/build/blob/master/patch/kernel/sunxi-dev/board-h6-clock-higher.patch arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi You can decompile DTB, edit and compile back. No need to recompile kernel.
hojnikb Posted November 28, 2018 Posted November 28, 2018 11 hours ago, Igor said: For H6?https://github.com/armbian/build/blob/master/patch/kernel/sunxi-dev/board-h6-clock-higher.patch arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi You can decompile DTB, edit and compile back. No need to recompile kernel. Sorry, i meant for H5. I assume it's the same procedure ?
Igor Posted November 28, 2018 Author Posted November 28, 2018 50 minutes ago, hojnikb said: Sorry, i meant for H5. I assume it's the same procedure ? Yes. just location is elsewhere if you look from kernel sources perspective. IIRC its inside common sunxi-h3-h5 include file which is under arch/arm/boot/dts not arm64 ... which is a bit confusing.
targa Posted November 28, 2018 Posted November 28, 2018 Worth trying this on a R40 board (Banana Berry) ? /T
Recommended Posts