mdrmdr

Seems to work 😀
 
/dev/spidev0.0 is created. The SPI device CC1101 and therefore the Homegear gateway initializes fine.
What else information do you need? dmesg output? Logfiles?
 
Small change in your instructions: cd deb must be cd deb/nanopineo

Seems to work 😀
 
/dev/spidev0.0 is created. The SPI device CC1101 and therefore the Homegear gateway initializes fine.
What else information do you need? dmesg output? Logfiles?
 
Small change in your instructions: cd deb must be cd deb/nanopineo

Doing what is explained in this post make it to work but spidev isn't anymore controlled through /boot/armbianEnv.conf file but the DT.
 
I used the "quick and dirty" fix for now by using "rohm,dh2228fv" which is already in the spidev_dt_ids[] list and avoid me creating a new build with a patch to modify drivers/spi/spidev.c
 
So basically, I used armian-config to edit the Device Tree (System => Dtc),
Browse the DT over soc => spi@1c68000
And I added these lines :
spi@1c68000 { ... spidev@0x00 { compatible = "rohm,dh2228fv"; spi-max-frequency = <100000000>; reg = <0x00>; }; }  
And the same for the second SPI controller :
 
spi@1c69000 { ... spidev@0x00 { compatible = "rohm,dh2228fv"; spi-max-frequency = <100000000>; reg = <0x00>; }; }  
I also had to remove the spidev stuff from /boot/armbianEnv.conf (No spi-spidev overlay)

This way, I get two SPI devices and the SBC is working again with 5.15 kernel :
 
# ls /dev/ | grep spi spidev0.0 spidev1.0  

workaround:
 
download file from https://imola.armbian.com/beta/pool/main/l/
install with
 
sudo dpkg -i FILE.deb  
 
and DTB package. Headers are optional - if you need to build modules.

Hi all,
 
I'm new here at the Armbian board. I operate a self made house automation based on a Raspberry using a self written PHP server and Homegear.
To have a better wireless connection to a differential temperature sensor, I built a Homegear Gateway based on a Nano Pi Neo with Armbian OS and a 868 MHz CC1101 module.
For the network connection I use a Realtek USB WLAN NIC (Realtek RTL8188EUS-Chipset). Most of the time the gateway works.
But around 2-3 times per week the gateway hangs and I cannot log on anymore. A hard restart by unplugging power is required.
 
The only indications I find are 2 dumps of the RTL8188EU driver in kern.log. Check the 2 dumps at the far end of the armbianmonitor output starting at 24.009211.
 
I already built & installed the 8188EU(S) driver from here and here by myself. But unfortunateley without success.
 
Anybody any idea whats going on with my gateway?
 
Thanks a lot for help.
 
Update: Just had another crash. Maybe someone sees the reason here.
 
Update: 19.09: Since I cannot create a new answer (what's the reason behind "You have reached the maximum number of posts you can make per day"?), I add it here.
I just ordered a new NIC with a Ralink 5370 Chipset . Should arrive on monday. I operate the gateway with LAN until then. I'll report how it works with the new NIC.