[Another TV out questions.]

For the change in red, Yes !

I've all my OPi as headless, so, I can't answer for the HDMI2DVI questions.

 

[second SPI interface on Orange PI - problem]

You're lucky ...

SPI is designed only for few inches of wire. So, in you case, it is really out of specs.

 

[second SPI interface on Orange PI - problem]

What do you mean ?

Do you mean "how long SPI wiring can be" ? Shortest as possible !

SPI isn't design to work on long distance, especially with high speed.

Although reducing speed could help, it is not designed to support more than few inch of wires.

You are better having two OPiZero is the MFC are meters away from each other ...

 

[Another TV out questions.]

It is already installed on any images ...

 

[Orange Pi PC unable to connect through SSH from Macbook]

@tkaiser, that what I did when adding it as user-patches, but it is partially failed with (as mentioned above) :

 

chfn: PAM: Authentication token is no longer valid; new one requiredM
adduser: `/usr/bin/chfn -f Avahi mDNS daemon avahi' returned error code 1. Exiting.M

 

[Additional FAT partition]

In such case, since Windows is so stupid, you won't have much choice to have a separate sdcard mounted in a USB reader, having a single FAT partition on this one.

Another solution is to have a Window's folder shared and having your SoC board mounting that CIFS network share.

 

 

[Another TV out questions.]

euuhhh ?

libusb-1.0-0-dev as nothing to do with your issue...

why sunxi-fexc ? the tools I've mentioned are "bin2fex" and "fex2bin", but of course, sunxi-fexc can work too.

Of course, it is better to keep manual backups before overwriting any files.

Check this page : http://linux-sunxi.org/Fex_Guide

 

[kernel 4.11-rc7]

It is not the patching tool that is broken, it is the content of the patch that doesn't match code changes in 4.11.

You probably need to find out those change by comparing 4.10 and 4.11 together, and check which parts of the patch are broken.

 

[BPi-M2+ Problem to pair bluetooth speaker in command line]

Unfortunately, this grid is soo incomplete that you can't rely on it for any purchase decision.

(No OPiPC, no OPiPC+, no OPiPlus2E, no OPiPC2, etc)

[Orange Pi PC unable to connect through SSH from Macbook]

@tkaiser, has it been added recently to builds (and how ?) ? in my recent builds I had to install it manually ...

 

Also, when I configure user-patches to install them during build process, it is installing them but failed to run their post-install scripts :

 

Setting up libavahi-common-data:arm64 (0.6.31-5) ...M
Setting up libavahi-common3:arm64 (0.6.31-5) ...M
Setting up libavahi-client3:arm64 (0.6.31-5) ...M
Setting up libavahi-core7:arm64 (0.6.31-5) ...M
Setting up libdaemon0:arm64 (0.14-6) ...M
Setting up avahi-daemon (0.6.31-5) ...M
You are required to change your password immediately (root enforced)M
chfn: PAM: Authentication token is no longer valid; new one requiredM
adduser: `/usr/bin/chfn -f Avahi mDNS daemon avahi' returned error code 1. Exiting.M
dpkg: error processing package avahi-daemon (--configure):M
 subprocess installed post-installation script returned error exit status 1M
dpkg: dependency problems prevent configuration of libnss-mdns:arm64:M
 libnss-mdns:arm64 depends on avahi-daemon (>= 0.6.16-1); however:M
  Package avahi-daemon is not configured yet.M
M
dpkg: error processing package libnss-mdns:arm64 (--configure):M
 dependency problems - leaving unconfiguredM
Setting up libtalloc2:arm64 (2.1.2-0+deb8u1) ...M
Setting up libwbclient0:arm64 (2:4.2.14+dfsg-0+deb8u5) ...M
Setting up samba-common (2:4.2.14+dfsg-0+deb8u5) ...M
M

 

[Additional FAT partition]

Don't move this first/main partition, simply shrink it at the end, and add new FAT partition at the end of the SDCard.

 

[Orange Pi PC unable to connect through SSH from Macbook]

@tkaiser, 'ping orangepipc.local' won't work on virgin image since avahi-daemon isn't installed by default.

 

[Another TV out questions.]

script.bin is located in /boot. you need to decompile it into script.fex using bin2fex, edit it, and then recompile it into script.bin with fex2bin.

 

[Boot OPi over network]

What do you mean exactly ? How to flash SPI-NOR or How to make LCD work on RaspberryPi ? this is completely 2 different subjects.

For the SPI-NOR, as Zador said, it is not enabled by default. I personally suggest to use Mainline kernel anyway, it is much more easy to enable the overlay.

[Orange Pi PC unable to connect through SSH from Macbook]

The IP address 169.254.134.132 is or is not the IP of your MAC ?

How did you figured out that this IP could be the one from OrangePiPC ?

If your router doesn't help to figure out the real IP of the OPi, your will need to connect using Serial USB-TTL and do "ifconfig" on the board itself.

"orangepipc.local" doesn't work until "avahi-daemon" is installed on the OPi, when you will get access to it, simply go "apt-get install avahi-daemon".

 

[wifi direct Orange pi plus Linux 4.9]

8189ES isn't not the same as 8189FS.

But, anyway, the 8189fs is already part of Armbian build for some boards such OPiPC+.

Which board do you have ?

And why do you need it under 4.9 ? Armbian is on 4.10 since months ...

 

[Orange Pi Zero WiFi issues when disconnect Ethernet cable]

That is pretty normal if both wlan0 and eth0 are on the same subnet.

the default gateway route is pointing by default to eth0, so when disconnecting eth0, it has no gateway.

Simply boot your OPiZero without eth0 plugged in, the gateway will then point to wlan0.

 

[What does mean ~$]

~$ is effectively a command prompt shel, where the ~ means home directory.

For Desktop, did you use a Desktop image for your SDCard ?

Because Server image are headless by default, no Desktop installed ...

 

[Boot OPi over network]

Check the back of your OPiZero to make sure you have a SPI_NOR already soldered.

If your PCB has blank SOIC8 pads, you will need to purchase a flash chip and solder it there.

 

[Orange Pi Plus 2E Won't boot Armbian]

Not having a USB-TTL to do debugging is like a carpenter not having any hammer ...

[Orange Pi Win]

@Igor, can you confirm with Steven that PL9 is really on pin 16 of the header ? It doesn't work and since the PDF is named ORANGEPI-Winplus-V1_3.pdf and not ORANGEPI-Win-V1_x.pdf, i suspect some discrepancies ...

Same thing with ORANGEPI-Prime_V1_0.pdf, the STATUS-LED doesn't light up when bring PA15 to HIGH.

And if I remember this is the same issue with ORANGE_PI-PC2-V1_2_schematic.pdf, the STATUS-LED doesn't light up when bring PA15 to HIGH !

Steven should make sure that his schematics are reflecting the reality !!!

 

EDIT : Ok ! I found the discrepancies. In top area of the schematic, it says PA15 = STATUS-LED, but on the CPU pins , it is PA20. Same thing for PC2.

[kernel 4.11-rc7]

The errors with "scripts/dtc/livetree.c" is related to the fact that "scripts-dtc-Update-to-version-with-overlay.patch" failed.

 

[Orange Pi Win]

@Igor, thanks for confirmation !

I will continue digging ...

 

[OPi Win with A64]

Don't expect such feature like LCD interface to be in working state.

A week ago, none of the contributors had any OPiWin to work with.

The current build is booting, eth0 is working, but no WiFi yet.

 

[Orange Pi Win]

On another subject, since this is a new build target only since few days, my recent works as to get R_PIO working on OPiWin to allows getting the WiFi AP6212 working soon.

Unfortunately, I didn't get expected success yet.

R_PIO seems to be properly initialized, but neither wifi_en_pin@0 (PL8) or manual sysfs PL9 on header doesn't work.

 

The sad thin is that the sames R_PIO patches works well on Pine64 where I've been able to blink PL7 LED.

 

That make me think that the schematic we got ORANGEPI-Winplus-V1_3.pdf maybe not matching the real hardware, the "plus" maybe means "another" board, not yet available.

@Igor  could you confirm  with Steven ? There many other schematics that never been published yet, that should be updated ...