Misha

I'm getting logspam from RTL871X running buster on my OrangePi Plus 2e. I'm not using wifi on this so I guess I could just disable/blacklist rtl871x to stop this? But is there a better/cleaner way to stop all these log entries? Or does it indicate something is broken/mis-configured? syslog is showing many many log entries from RTL871X; each minute I get the following sequence: May 23 16:52:06 orangepiplus2e kernel: RTL871X: cfg80211_rtw_scan(wlan0) May 23 16:52:06 orangepiplus2e kernel: RTL871X: _rtw_pwr_wakeup call ips_leave.... May 23 16:52:06 orangepiplus2e kernel: RTL871X: ==>ips_leave cnts:112 May 23 16:52:06 orangepiplus2e kernel: RTL871X: ===> rtw_ips_pwr_up.............. May 23 16:52:06 orangepiplus2e kernel: RTL871X: ===> ips_netdrv_open......... May 23 16:52:06 orangepiplus2e kernel: RTL871X: FW does not exist before power on!! May 23 16:52:06 orangepiplus2e kernel: RTL871X: SetHwReg8188F: hci_sus_state=1 May 23 16:52:06 orangepiplus2e kernel: RTL871X: SetHwReg8188F: bMacPwrCtrlOn=1 May 23 16:52:06 orangepiplus2e kernel: RTL871X: SetHwReg8188F: hci_sus_state=2 May 23 16:52:06 orangepiplus2e kernel: RTL871X: PowerOnCheck: val_mix:0x0000063f, res:0x0000063f May 23 16:52:06 orangepiplus2e kernel: RTL871X: PowerOnCheck: 0x100 the result of cmd52 and cmd53 is the same. May 23 16:52:06 orangepiplus2e kernel: RTL871X: PowerOnCheck: 0x1B8 test Pass. May 23 16:52:06 orangepiplus2e kernel: RTL871X: Power on ok! May 23 16:52:06 orangepiplus2e kernel: RTL871X: rtl8188f_FirmwareDownload(wlan0) tmp_ps=3 May 23 16:52:06 orangepiplus2e kernel: RTL871X: rtl8188f_FirmwareDownload fw: FW_NIC, size: 21020 May 23 16:52:06 orangepiplus2e kernel: RTL871X: rtl8188f_FirmwareDownload: fw_ver=4 fw_subver=0000 sig=0x88f1, Month=08, Date=22, Hour=17, Minute=36 May 23 16:52:06 orangepiplus2e kernel: RTL871X: rtl8188f_FirmwareDownload(): Shift for fw header! May 23 16:52:06 orangepiplus2e kernel: RTL871X: rtl8188f_FirmwareDownload by IO write! May 23 16:52:06 orangepiplus2e kernel: RTL871X: polling_fwdl_chksum: Checksum report OK! (1, 0ms), REG_MCUFWDL:0x00050505 May 23 16:52:06 orangepiplus2e kernel: RTL871X: _8051Reset8188: Finish May 23 16:52:06 orangepiplus2e kernel: RTL871X: _FWFreeToGo: Polling FW ready OK! (237, 16ms), REG_MCUFWDL:0x000505c6 May 23 16:52:06 orangepiplus2e kernel: RTL871X: rtl8188f_FirmwareDownload: DLFW OK ! May 23 16:52:06 orangepiplus2e kernel: RTL871X: rtl8188f_FirmwareDownload success. write_fw:1, 236ms May 23 16:52:06 orangepiplus2e kernel: RTL871X: <=== rtl8188f_FirmwareDownload() May 23 16:52:06 orangepiplus2e kernel: RTL871X: HalDetectPwrDownMode(): PDN=0 May 23 16:52:06 orangepiplus2e kernel: RTL871X: Set RF Chip ID to RF_6052 and RF type to 3. May 23 16:52:06 orangepiplus2e kernel: RTL871X: #### hw_var_set_opmode() -4815 iface_type(0) mode = 2 #### May 23 16:52:06 orangepiplus2e kernel: RTL871X: rtw_rf_get_kfree_tx_gain_offset path:0, ch:6, bb_gain_sel:0, kfree_offset:0 May 23 16:52:06 orangepiplus2e kernel: RTL871X: kfree gain_offset 0x55:0x82060 May 23 16:52:06 orangepiplus2e kernel: RTL871X: after :0x2060 May 23 16:52:06 orangepiplus2e kernel: RTL871X: <=== rtw_ips_pwr_up.............. in 728ms May 23 16:52:06 orangepiplus2e kernel: RTL871X: nolinked power save leave May 23 16:52:06 orangepiplus2e kernel: RTL871X: ==> ips_leave.....LED(0x01028282)... May 23 16:52:08 orangepiplus2e kernel: RTL871X: survey done event(35) band:0 for wlan0 May 23 16:52:08 orangepiplus2e kernel: RTL871X: rtw_indicate_scan_done(wlan0) May 23 16:52:08 orangepiplus2e kernel: RTL871X: ==>rtw_ps_processor .fw_state(8) May 23 16:52:08 orangepiplus2e kernel: RTL871X: ==>ips_enter cnts:113 May 23 16:52:08 orangepiplus2e kernel: RTL871X: nolinked power save enter May 23 16:52:08 orangepiplus2e kernel: RTL871X: ===> rtw_ips_pwr_down................... May 23 16:52:08 orangepiplus2e kernel: RTL871X: ====> rtw_ips_dev_unload... May 23 16:52:08 orangepiplus2e kernel: RTL871X: SetHwReg8188F: bMacPwrCtrlOn=0 May 23 16:52:08 orangepiplus2e kernel: RTL871X: SetHwReg8188F: hci_sus_state=3 May 23 16:52:08 orangepiplus2e kernel: RTL871X: SetHwReg8188F: hci_sus_state=0 May 23 16:52:08 orangepiplus2e kernel: RTL871X: <=== rtw_ips_pwr_down..................... in 8ms

Thanks Igor -- for the benefit of anyone finding this thread in the future: I checked voltage on the PSU and all seemed fine. However, I got a replacement PSU "just in case" (a 5V 3A UK plug wall wart off ebay, instead of the EU plug one that came with the OPi; just had to solder a 4/1.7mm barrel connector onto the cable) and miraculously with the new PSU the board now comes up fine! Lesson learned: PSU quality is make or break with these boards, even when using a decent barrel connector. And the symptoms of dodgy power supply can be pretty random. Thanks again

Retrying Armbian_5.38_Orangepiplus2e_Ubuntu_xenial_default_3.4.113_desktop.img with HDMI connected gives: U-Boot SPL 2017.11-armbian (Jan 25 2018 - 07:57:02) DRAM: 2048 MiB Trying to boot from MMC1 U-Boot 2017.11-armbian (Jan 25 2018 - 07:57:02 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus 2E DRAM: 2 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment with top 60% of HDMI output blank/black and bottom 40% white with multi-coloured pixel snow. Beginning to think the board might be b0rked in some way :-( Same image with no HDMI connected: U-Boot SPL 2017.11-armbian (Jan 25 2018 - 07:57:02) DRAM: 2048 MiB Trying to boot from MMC1 U-Boot 2017.11-armbian (Jan 25 2018 - 07:57:02 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus 2E DRAM: 2 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c30000 starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 USB4: USB EHCI 1.00 USB5: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning bus 4 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3708 bytes read in 198 ms (17.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 154 bytes read in 150 ms (1000 Bytes/s) Again, pressing space to interrupt autoboot again I can get to (more recent) U-Boot prompt: => version U-Boot 2017.11-armbian (Jan 25 2018 - 07:57:02 +0100) Allwinner Technology arm-linux-gnueabihf-gcc (Linaro GCC 7.2-2017.11) 7.2.1 20171011 GNU ld (Linaro_Binutils-2017.11) 2.28.2.20170706 => Can I force it to boot with more logging on or anything?

Evo+ with Raspbian_For_OrangePi_Plus2E_WIFI.img (from http://www.orangepi.org/downloadresources/PiPlus2e/2016-11-12/piplus2e_63e5abfb90c7293d2993b921e14.html): Again, if I hit a key to stop autoboot just before it starts the kernel I can get to a U-Boot prompt: sunxi#version U-Boot 2011.09-rc1-00000-g21ef338-dirty (May 11 2016 - 11:24:04) Allwinner Technology arm-linux-gnueabi-gcc (crosstool-NG linaro-1.13.1-2012.02-20120222 - Linaro GCC 2012.02) 4.6.3 20120201 (prerelease) GNU ld (crosstool-NG linaro-1.13.1-2012.02-20120222 - Linaro GCC 2012.02) 2.22 sunxi#

HDMI attached now but no fb output visible during boot. Where in the bootlog sequence does the resizing occur? With a different sdcard (generic 32GB, h2testw passed just now at 17MBps write 60Mbps read): Armbian_5.52.180715_Orangepiplus2e_Ubuntu_bionic_dev_4.18.0-rc4.img: U-Boot SPL 2018.05-armbian (Jul 15 2018 - 16:10:26 +0000) DRAM: 2048 MiB Trying to boot from MMC1 U-Boot 2018.05-armbian (Jul 15 2018 - 16:10:26 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus 2E DRAM: 2 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** Failed (-5) At this point it appears to stop; the HDMI output shows top ~80% of screen black and bottom ~20% solid white. With the original Evo+ (just retested with h2testw - 21MBps write 76MBps read) and Armbian_5.59.180815_Orangepiplus2e_Ubuntu_bionic_next_4.17.14.img get basically the same: U-Boot SPL 2018.05-armbian (Aug 15 2018 - 15:59:38 +0200) DRAM: 2048 MiB Trying to boot from MMC1 U-Boot 2018.05-armbian (Aug 15 2018 - 15:59:38 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus 2E DRAM: 2 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** Failed (-5) With the generic 32GB and stock ubuntu_server_plus2e.img (from http://www.orangepi.org/downloadresources/PiPlus2e/2017-05-11/piplus2e_f43bac3e68bf784eb78411c4cf4.html): However if I hit a key to stop autoboot I can get to a prompt: sunxi#version U-Boot 2011.09-rc1 (Jun 21 2015 - 19:33:17) Allwinner Technology arm-linux-gnueabi-gcc (crosstool-NG linaro-1.13.1-2012.02-20120222 - Linaro GCC 2012.02) 4.6.3 20120201 (prerelease) GNU ld (crosstool-NG linaro-1.13.1-2012.02-20120222 - Linaro GCC 2012.02) 2.22 Is there anything useful I can accomplish from there?

Thanks for the pointers. Does the fact that it fails to boot from the Android presinstalled image on emmc means that its not (just) an SD card issue? SD card was tested with h2testw. Image was burnt with etcher (on Win10), using a USB3 Transcend SD/MMC/CF adapter. I can try to get hold of another sdcard and try that too. Power is from 3A PSU (bought with the plus2e), which has decently thick cable and barrel connector. Nothing connected to USB or video ports on plus2e. What's the best way to check whether I might have a power issue? I have a (digital) multimeter. edit: 3A not 2A PSU (according to the printing on the case, at least!)

Agreed - this is from the "no SD card installed" bootlog, so is probably the pre-installed Android on the emmc; I only included that because I thought it might provide some useful additional information - apologies for any confusion. I'm not trying to fix the emmc nand-install -- just trying to get it booting with latest armbian from sdcard. Once that is working I may do a nand install, but I need to get it booting first ;-) ! The first bootlog is the one with latest armbian mainline kernel image (Armbian_5.38_Orangepiplus2e_Debian_stretch_next_4.14.14.img), booting from the Evo+, which shows it hanging at the "loading ramdisk" stage. Is there anything there that indicates what might be going wrong?

OrangePi Plus 2e. Used Etcher to write Armbian_5.38_Orangepiplus2e_Debian_stretch_next_4.14.14.img to an Evo+ 32GB. Connected via USB serial (putty). Boot process hangs loading the ramdisk: U-Boot SPL 2017.11-armbian (Jan 25 2018 - 07:57:17) DRAM: 2048 MiB Trying to boot from MMC1 U-Boot 2017.11-armbian (Jan 25 2018 - 07:57:17 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus 2E DRAM: 2 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c30000 starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 USB4: USB EHCI 1.00 USB5: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning bus 4 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3708 bytes read in 210 ms (16.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 152 bytes read in 169 ms (0 Bytes/s) 5070083 bytes read in 518 ms (9.3 MiB/s) 6968976 bytes read in 625 ms (10.6 MiB/s) Found mainline kernel configuration 32985 bytes read in 1082 ms (29.3 KiB/s) 4179 bytes read in 1303 ms (2.9 KiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 44000000 ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5070019 Bytes = 4.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 49b2a000, end 49fffcc3 ... Also tried with a couple of legacy images: Armbian_5.38_Orangepiplus2e_Ubuntu_xenial_default_3.4.113_desktop.img, Armbian_5.30_Orangepiplus2e_Debian_jessie_default_3.4.113. With legacy it also hangs - e.g. with 5.38 xenial 3.4.113 image: U-Boot SPL 2017.11-armbian (Jan 25 2018 - 07:57:02) DRAM: 2048 MiB Trying to boot from MMC1 U-Boot 2017.11-armbian (Jan 25 2018 - 07:57:02 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus 2E DRAM: 2 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c30000 starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 USB4: USB EHCI 1.00 USB5: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning bus 4 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3708 bytes read in 202 ms (17.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 154 bytes read in 154 ms (1000 Bytes/s) 5179171 bytes read in 516 ms (9.6 MiB/s) 4752384 bytes read in 509 ms (8.9 MiB/s) Found legacy kernel configuration 36808 bytes read in 544 ms (65.4 KiB/s) ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5179107 Bytes = 4.9 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Starting kernel ... [sun8i_fixup]: From boot, get meminfo: Start: 0x40000000 Size: 2048MB ion_carveout reserve: 160m@0 256m@0 130m@1 200m@1 ion_reserve_select: ion chipid [0x2c00081! ion_reserve_common: ion reserve: [0xb0000000, 0xc0000000]! With an older 5.30 jessie 3.4.113 image (different uboot version) it also hangs at "io_reserve_common": U-Boot SPL 2017.05-armbian (Jun 13 2017 - 15:36:38) DRAM: 2048 MiB Trying to boot from MMC1 U-Boot 2017.05-armbian (Jun 13 2017 - 15:36:38 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus 2E I2C: ready DRAM: 2 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c30000 Hit any key to stop autoboot: 0 38518 bytes read in 142 ms (264.6 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 192 ms (17.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 115 bytes read in 152 ms (0 Bytes/s) 3795385 bytes read in 448 ms (8.1 MiB/s) 4750952 bytes read in 511 ms (8.9 MiB/s) Found legacy kernel configuration 36808 bytes read in 483 ms (74.2 KiB/s) ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 3795321 Bytes = 3.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Starting kernel ... [sun8i_fixup]: From boot, get meminfo: Start: 0x40000000 Size: 2048MB ion_carveout reserve: 160m@0 256m@0 130m@1 200m@1 ion_reserve_select: ion chipid [0x2c00081! ion_reserve_common: ion reserve: [0xb0000000, 0xc0000000]! I have previously had this plus2e working (on an older legacy kernel image from 2016/7 - can't recall which one). I thought I might have done a nandinstall on that image, but booting with no SD card gives: so I'm guessing either I didn't complete the nand install, or its broken in some way! Any ideas what is wrong and what I can do to diagnose/fix?