-
Posts
49 -
Joined
-
Last visited
Reputation Activity
-
cvxx got a reaction from klay in [solved] Headless wifi setup - conflict between NetworkManager and /etc/network/interfaces
UPDATE
I have set up a fresh sd card to investigate and collect logs, but this time `ifupdown` worked
Probably it was some typo I made in /etc/network/interfaces during setup
Also, a note for future myself when I visit this thread again, there is a way to create the connection through `armbian_first_run.txt`. I tested and it worked. So, probably, better to switch to this way to have less conflicts between Network Manager and ifupdown
-
cvxx got a reaction from Igor in Cubox-i enable shell on serial console
added:
console=both now I have a shell!
Thanks!
-
cvxx got a reaction from Werner in Cubox-i enable shell on serial console
added:
console=both now I have a shell!
Thanks!
-
cvxx got a reaction from derAfri in [solved] Headless wifi setup - conflict between NetworkManager and /etc/network/interfaces
UPDATE
I have set up a fresh sd card to investigate and collect logs, but this time `ifupdown` worked
Probably it was some typo I made in /etc/network/interfaces during setup
Also, a note for future myself when I visit this thread again, there is a way to create the connection through `armbian_first_run.txt`. I tested and it worked. So, probably, better to switch to this way to have less conflicts between Network Manager and ifupdown
-
cvxx got a reaction from sskrn in [solved] Headless wifi setup - conflict between NetworkManager and /etc/network/interfaces
Thanks for the idea
I found this solution to be more compatible: /etc/NetworkManager/NetworkManager.conf
Source: https://wiki.debian.org/NetworkManager#Wired_Networks_are_Unmanaged
-
cvxx got a reaction from MattCostamagna in [solved] Headless wifi setup - conflict between NetworkManager and /etc/network/interfaces
Thanks for the idea
I found this solution to be more compatible: /etc/NetworkManager/NetworkManager.conf
Source: https://wiki.debian.org/NetworkManager#Wired_Networks_are_Unmanaged
-
cvxx reacted to noxlin in Orange Pi Zero Plus-WiringPi modified version works
I compared two boards (opi zero h3 and opi zero plus h5) and found that cpu pins for 26 gpio are the same .
so I modify the code in wiringPi about cpu detection to force return true value .
and it works.
the step:
1. git clone https://github.com/xpertsavenue/WiringOP-Zero
2. modify the code in WiringOP-Zero/wiringPi/wiringPi.c (or using the attached file to replace)。
3. make && make install
4. run "gpio readall " to test
5. run "gpio write 30 1" (the red-led on, wiringpi pin 30 control red-led status).
wiringPi.c
-
cvxx reacted to Michal8 in DHT11 DHT22 orange pi zero
Hi, I have finally found the solution, the problem is in /etc/default/cpufrequtils where MIN_SPEED was set to 240MHz and it is too low. I set the MIN_SPEED to 600MHz and conservative governor. Now it WORKS as expected. Maybe it helps someone:)
-
cvxx got a reaction from tkaiser in BananaPi kernel 3.4.113, 8192cu: disagrees about version of symbol module_layout
The following wifi dongle does not work with legacy kernel:
Bus 002 Device 002: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
$ uname -a
Linux bananapi 3.4.113-sun7i #40 SMP PREEMPT Thu Feb 2 01:44:33 CET 2017 armv7l armv7l armv7l GNU/Linux
Freshly flashed Armbian_5.25_Bananapi_Ubuntu_xenial_default_3.4.113_desktop