Hi everyone!!
Any chance to know the estimated schedule for having Gb ethernet working in mainline kernel 4.x for this board?
Greetings!!
↧
OrangePi+2 Gb ethernet kernel 4.x
↧
Summary of boards for a NAS
Since I was looking up which boards would make a proper NAS and home automation hub, I figured I might as well summarize the options in a post.
Requirements for a proper NAS:
- Gigabit Ethernet
- SATA that is not a crappy USB->SATA chip
- Armbian-supported
That last one is because otherwise the options are much more numerous and scattered, and the previous requirements become vague (e.g., you could even just take out a netbook's motherboard and run it standalone).
Also, you could use an A80 board (USB 3.0) but I believe none are supported by Armbian, same goes for R40 (has SATA), so this leaves us with these A20 boards that also have GbE:
_____________________________________________________
Banana Pi
_____________________________________________________
Banana Pi+
_____________________________________________________
Cubietruck
_____________________________________________________
Lamobo R1
_____________________________________________________
Olimex Lime 2
_____________________________________________________
Olimex Lime 2 eMMC
_____________________________________________________
Orange Pi
_____________________________________________________
Orange Pi mini
_____________________________________________________
pcDuino3 nano
_____________________________________________________
Clearfog Base
_____________________________________________________
Clearfog Pro
_____________________________________________________
CuBox-i
_____________________________________________________
HummingBoard (Pro & Edge)
_____________________________________________________
Udoo Quad
_____________________________________________________
The prices and availability for these boards is as follows:
Lamobo R1 (out of stock / discontinued)
Orange Pi (renamed? / out of stock / discontinued)
Orange Pi mini (renamed? / out of stock / discontinued)
According solely to the above, and disregarding other board differences/features, for a simple LAN-connected NAS hard drive that occasionally pulls a few GPIO pins high or low for automation, the Banana Pi looks like a good option.
Maybe I'm overlooking things, and maybe any of those prices are wrong; since this is a forum anyone is free to correct me and I'll try to update this OP in case the thread grows (and I remember to check back down the road).
Edit: a great read is this wiki article, some considerations: clock speed and CPU governor matters a lot more than in x86 (doing other stuff during transfers might be a no-no) and Gigabit Ethernet might mean "USB 2.0 speeds, but in a RJ45".
Side note: it would be nice to have a list of boards somewhere with feature matrices and prices/links, not sure if such a thing exists.
Edit: added Clearfog Base/Pro, CuBox-i, HummingBoard Pro/Edge and Udoo Quad as per suggestion)
↧
↧
Compiled external module, Exec format error
I tried to compile wireguard from source in armbian xenial with kernel 4.9.7. on a Banana Pro.
After compiling and installing the resulting kernelmodule, modprobe fails:
sudo modprobe wireguard
modprobe: ERROR: could not insert 'wireguard': Exec format error
dmesg shows:
[ 5563.012529] wireguard: loading out-of-tree module taints kernel.
[ 5563.013912] wireguard: unknown relocation: 102
On the wireguard list, one pointed out this might be related to old toolchain, so i checked:
the installed gcc is:
gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4)
and the mentiond gcc Version in dmesg is
(gcc version 6.2.1 20161016 (Linaro GCC 6.2-2016.11) )
So do i need to crosscompile the module? I set up a crosscompile enviroment as described in the documentation, but its lacking hints about compiling external kernelmodules.
Regards, Alexander Morlang
↧
Armbian 5.25 on NanoPi NEO: new MAC address on each boot
I realize there have been a few topics on this, but it seems to me that this was considered fixed.
When using 5.23 with a 4.8 kernel, the MAC address was stable.
After upgrading to 5.25, the MAC address was still the same as before. However after an outage, the two boards running 5.25 came up with a new MAC address (two boards still running 5.23 came up with the same MAC address). Then the MAC address seems to change every boot.
The problem is that the FiOS router (an ActionTec) I have remembers both the machine name and the MAC address (it nicely creates a DNS entry). If the same name appears with a different MAC address, it ignores the name from DHCP and create a new entry with a made-up name. The router does not let you delete an entry, only rename it. (It is obviously a case of a router trying to be too smart for its own good: why does not it trust the DHCP name to begin with?)
So now I have unpredictable IP addresses and names.
Searching through google, I found an advice to add "hwaddress ether xx:xx:xx:xx:xx" to /etc/networks/interfaces. However after setting the MAC address this way (to the original MAC address), the network does not start properly and no new machine is even listed by the router. If I remove the statement, the network starts again.
Any advice, or pointer to the right topic, will be appreciated.
Thanks.
↧
Permission denied when activate cpu in beelink X2
Hello everyone,
First of all, I'm sorry for my English. I'll do my best.
Currently armbian is installed in the mmc (although I tried the same test with a sd memory).
Now, with lscpu I can see that only cpu0 is enabled; 1-3 are off.
When I try: sudo echo '1' | Sudo tee / sys / devices / system / cpu / cpu1 / online to activate cpu1, shell replies with: online: Permission denied
I'm looking for options on root permissions or sysfs mount options; For now, I can not find a solution.
Thanks in advance for your help.
↧
↧
Issue with Armbian_5.25_Nanopineo_Debian_jessie_default_3.4.113
Hi all,
I'm trying to get some sensors working with latest Armbian on a NanoPi Neo ...
1st thing is that there are a bunch of modules loaded where I have no hardware for, f.e. pcf8591 and bmp085:
root@nanopineo:~# uname -a Linux nanopineo 3.4.113-sun8i #28 SMP PREEMPT Thu Feb 2 02:01:28 CET 2017 armv7l GNU/Linux root@nanopineo:~# lsmod Module Size Used by ir_lirc_codec 3650 0 lirc_dev 7834 1 ir_lirc_codec ir_mce_kbd_decoder 2885 0 ir_sanyo_decoder 1480 0 ir_sony_decoder 1422 0 ir_jvc_decoder 1452 0 ir_rc6_decoder 1941 0 ir_rc5_decoder 1412 0 ir_nec_decoder 1556 0 sunxi_cir 1601 0 rc_core 12727 10 ir_lirc_codec,ir_rc5_decoder,ir_nec_decoder,ir_sony_decoder,sunxi_cir,ir_mce_kbd_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_sanyo_decoder bmp085 3487 0 pcf8591 3363 0 g_serial 27617 0 btrfs 712409 0 root@nanopineo:~# cat /etc/modules #w1-sunxi #w1-gpio #w1-therm #sunxi-cir g_serial root@nanopineo:~# dmesg | grep plat [ 0.115079] plat: add bmp085 device [ 0.115079] plat: add pcf8591 device
except for g_serial which seems loaded from /etc/modules I cant find from where the rest gets loaded ...?
Then when trying to delete the instance of pcf8591 (I need address 0x48 for a lm75a ) I get:
root@nanopineo:~# ll /sys/bus/i2c/devices/i2c-0/ total 0 drwxr-xr-x 4 root root 0 Jan 1 1970 0-0048 drwxr-xr-x 3 root root 0 Feb 19 19:18 0-004f drwxr-xr-x 3 root root 0 Jan 1 1970 0-0077 --w------- 1 root root 4096 Feb 21 11:02 delete_device lrwxrwxrwx 1 root root 0 Feb 19 19:17 device -> ../../twi.0 drwxr-xr-x 3 root root 0 Jan 1 1970 i2c-dev -r--r--r-- 1 root root 4096 Feb 19 19:17 name --w------- 1 root root 4096 Feb 19 19:18 new_device drwxr-xr-x 2 root root 0 Feb 19 19:11 power lrwxrwxrwx 1 root root 0 Feb 19 19:11 subsystem -> ../../../../bus/i2c -rw-r--r-- 1 root root 4096 Jan 1 1970 uevent root@nanopineo:~# echo 0x48 > /sys/bus/i2c/devices/i2c-0/delete_device -bash: echo: write error: Invalid argument root@nanopineo:~# echo 0x4f > /sys/bus/i2c/devices/i2c-0/delete_device -bash: echo: write error: Invalid argument root@nanopineo:~# echo 0x77 > /sys/bus/i2c/devices/i2c-0/delete_device -bash: echo: write error: Invalid argument
here the device at 0x4f is another lm75a which I have self instantiated and which works fine - though even that I cant remove ...
so my questions are:
1) from where get all those modules (pcf8591, bmp085, ir* and related) loaded and why?
2) why does deleting of devices not work?
I've have an older version of Armbian running on a BPI and there I can delete instantiated devices just fine ...
Excuse me if this has already been asked/answered in another thread but I have heavily searched but wasnt successful :-(
↧
NanoPi Neo PWM pin
With a little shell script I can switch gpio6 on/off:
#!/bin/sh
# PWM1 / GPIOA6
P=6
G="/sys/class/gpio/gpio${P}"
if [ ! -d "${G}" ]; then
echo "Exporting GPIO${P}"
echo ${P} > /sys/class/gpio/export
echo out > ${G}/direction
fi
i=100
while [ "$i" -gt 0 ]; do
i=`expr $i - 1`
sleep .2
echo 1 > ${G}/value
sleep .1
echo 0 > ${G}/value
done
if [ -d "${G}" ]; then
echo "Unexporting GPIO${P}"
echo ${P} > /sys/class/gpio/unexport
fi
but I dont see anything which could enable PWM on this pin:
root@nanopineo:~# ll /sys/class/gpio/gpio6/ total 0 -rw-r--r-- 1 root root 4096 Feb 21 11:38 active_low lrwxrwxrwx 1 root root 0 Feb 21 11:38 device -> ../../../sunxi-pinctrl -rw-r--r-- 1 root root 4096 Feb 21 11:37 direction -rw-r--r-- 1 root root 4096 Feb 21 11:38 edge drwxr-xr-x 2 root root 0 Feb 21 11:38 power lrwxrwxrwx 1 root root 0 Feb 21 11:38 subsystem -> ../../../../../class/gpio -rw-r--r-- 1 root root 4096 Feb 21 11:37 uevent -rw-r--r-- 1 root root 4096 Feb 21 11:38 value
Is it possibe to enable PWM on the NanoPi Neo via sysfs?
↧
RSS feed for new forum posts
I know there exists https://forum.armbian.com/index.php/rss/forums/1-armbian-news/ but this feed does not seem to carry all new Armbian forum posts. I'm looking for something like http://forum.odroid.com/feed.php which makes it easier to track all feeds in on place like feedly.com does.
Thanks
Uli
↧
Armbian 5.25 on OrangePI PC: The gc2035 video camera doesn't work
After update from armbian5.23 to armbian5.25 driver for gc2035 not work. The device isn't defined.
=========== Armbian 5.25 ==============
root@orangepipc:~# ls /dev/video*
/dev/video0 /dev/video1
Where: /dev/video0 and /dev/video1 - v4l2loopback
root@orangepipc:~# cat /etc/modules
#8189es
#rfcomm
#w1-sunxi
#w1-gpio
#w1-therm
gc2035
vfe_v4l2
#sunxi-cir
v4l2loopback
root@orangepipc:~# modinfo vfe_v4l2
filename: /lib/modules/3.4.113-sun8i/kernel/drivers/media/video/sunxi-vfe/vfe_v4l2.ko
description: Video front end driver for sunxi
license: Dual BSD/GPL
author: raymonxiu
depends: videobuf-core,vfe_os,vfe_subdev,videobuf-dma-contig,cci
intree: Y
vermagic: 3.4.113-sun8i SMP preempt mod_unload modversions ARMv7 p2v8
parm: ccm:string
parm: i2c_addr:uint
parm: act_name:string
parm: act_slave:uint
parm: define_sensor_list:uint
parm: vfe_i2c_dbg:uint
parm: isp_log:uint
parm: vips:uint
root@orangepipc:~# modinfo gc2035
filename: /lib/modules/3.4.113-sun8i/kernel/drivers/media/video/sunxi-vfe/device/gc2035.ko
license: GPL
description: A low-level driver for GalaxyCore gc2035 sensors
author: @lex
author: leonardo lontra
author: raymonxiu
alias: i2c:gc2035
depends: cci,vfe_subdev
intree: Y
vermagic: 3.4.113-sun8i SMP preempt mod_unload modversions ARMv7 p2v8
parm: hres:hres=0 (640x480|1280x720|1600x1200 - 15 FPS), hres=1 (800x600|1600x1200 - 10 FPS), hres=2 (320x240|640x480|800x600 - 20 FPS), hres=3 (320x240|352x288|640x480 - 15 FPS) (default=0) (uint)
parm: mclk:mclk override (default=0) (uint)
parm: frate:frate override (default=0) (uint)
root@orangepipc:~# dmesg | grep GC2035
[ 5.938267] [CSI_ERR][GC2035]sensor_read err at sensor_detect!
[ 5.938289] [CSI_ERR][GC2035]chip found is not an target chip.
root@orangepipc:~# uname -a
Linux orangepipc 3.4.113-sun8i #28 SMP PREEMPT Thu Feb 2 02:01:28 CET 2017 armv7l armv7l armv7l GNU/Linux
root@orangepipc:~# cat /etc/armbian-release
# PLEASE DO NOT EDIT THIS FILE
BOARD=orangepipc
BOARD_NAME="Orange Pi PC"
VERSION=5.25
LINUXFAMILY=sun8i
BRANCH=default
ARCH=arm
IMAGE_TYPE=stable
root@orangepipc:~#
================================
Under armbian5.23 the gc2035 driver works. The device is defined.
=========== Armbian 5.23 ==============
root@orangepipc:~# ls /dev/video*
/dev/video0 /dev/video1 /dev/video2
Where: /dev/video0 and /dev/video1 - v4l2loopback, /dev/video2 - gc2035
root@orangepipc:~# cat /etc/modules
#8189es
#gpio_sunxi
#w1-sunxi
#w1-gpio
#w1-therm
gc2035
vfe_v4l2
#sunxi-cir
v4l2loopback
root@orangepipc:~# modinfo vfe_v4l2
filename: /lib/modules/3.4.112-sun8i/kernel/drivers/media/video/sunxi-vfe/vfe_v4l2.ko
description: Video front end driver for sunxi
license: Dual BSD/GPL
author: raymonxiu
depends: videobuf-core,vfe_os,vfe_subdev,videobuf-dma-contig,cci
intree: Y
vermagic: 3.4.112-sun8i SMP preempt mod_unload modversions ARMv7 p2v8
parm: ccm:string
parm: i2c_addr:uint
parm: act_name:string
parm: act_slave:uint
parm: define_sensor_list:uint
parm: vfe_i2c_dbg:uint
parm: isp_log:uint
parm: vips:uint
root@orangepipc:~# modinfo gc2035
filename: /lib/modules/3.4.112-sun8i/kernel/drivers/media/video/sunxi-vfe/device/gc2035.ko
license: GPL
description: A low-level driver for GalaxyCore gc2035 sensors
author: @lex
author: leonardo lontra
author: raymonxiu
alias: i2c:gc2035
depends: cci,vfe_subdev
intree: Y
vermagic: 3.4.112-sun8i SMP preempt mod_unload modversions ARMv7 p2v8
parm: hres:hres=0 (640x480|1280x720|1600x1200 - 15 FPS), hres=1 (800x600|1600x1200 - 10 FPS), hres=2 (320x240|640x480|800x600 - 20 FPS), hres=3 (320x240|352x288|640x480 - 15 FPS) (default=0) (uint)
parm: mclk:mclk override (default=0) (uint)
parm: frate:frate override (default=0) (uint)
root@orangepipc:~# dmesg | grep GC2035
[ 5.353480] [CSI][GC2035]V4L2_IDENT_SENSOR=2035
[ 5.780057] [CSI][GC2035]disalbe oe!
root@orangepipc:~# uname -a
Linux orangepipc 3.4.112-sun8i #10 SMP PREEMPT Sun Oct 23 16:06:55 CEST 2016 armv7l GNU/Linux
root@orangepipc:~# cat /etc/armbian-release
# PLEASE DO NOT EDIT THIS FILE
BOARD=orangepipc
BOARD_NAME="Orange Pi PC"
VERSION=5.23
LINUXFAMILY=sun8i
BRANCH=default
ARCH=arm
root@orangepipc:~#
================================
P.S.: Settings of parameters in section [csi0] are identical in both versions of the orangepipc.fex file
↧
↧
Using GPIO on BananaPro and Mainline
Hello together,
I'm trying to connect an LVDS panel to my BananPro and would like to switching power on/of and backlight on/off throw a GPIO pin.
So, first of all, I've added some lines to my DTS file (in &pio section).
This is for backlight driver (PH12 is connected to CON2 pin 7):
bl_en_pins_a: bl_en@0 {
allwinner,pins = "PH12";
allwinner,function = "gpio_out";
allwinner,drive = <SUN4I_PINCTRL_10_MA>;
allwinner,pull = <SUN4I_PINCTRL_PULL_DOWN>;
};
And this is for enable pin of voltage regulator (PH7 is connected to CON2 pin 6):
lcd_power_pins_a: lcd_power@0 {
allwinner,pins = "PH7";
allwinner,function = "gpio_out";
allwinner,drive = <SUN4I_PINCTRL_10_MA>;
allwinner,pull = <SUN4I_PINCTRL_PULL_DOWN>;
};
So, my question: How can I access those pins in linux (i.e. switch on or off and so one)?
I'm using mainline kernel 4.4.11 and BananaPRO.
Many thanks & kind regards,
Heinrich
↧
Orange Pi H3 - Can not start wireless static IP on boot
Hi!
I think all fine in my configuration, but not connect on boot, I need to killall -q wpa_supplicant and run /etc/init.d/networking restart to connect.
# /etc/network/interfaces
iface wlan0 inet static
address 192.168.1.200
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
pre-up wpa_supplicant -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf -wB -D <forgot the name>
post-down killall -q wpa_supplicant
↧
PWM with Vanilla Kernel on Lime2?
I'm using an Olimex LIME2 board with an A20 processor (actually it's a Olimex A20-SOM, but that shouldn't matter) and trying to use PWM.
I have an older image (jessie with Kernel 3.4) where the PWM hardware can be accessed through /sys/class/pwm-sunxi/pwm*/{duty, duty_percent, period, pin, polarity, pulse, run}.
Now I'm building a newer image (xenial with Vanilla kernel). It has /sys/class/pwm, but the directory is empty. Any ideas?
The fex file is the same for both boards; the relevant section is:
[pwm0_para] pwm_used = 1 pwm_period = 10000 pwm_duty_percent = 50 [pwm1_para] pwm_used = 1 pwm_period = 10000 pwm_duty_percent = 50
↧
Prevent eth0 link from coming up on boot
Hi,
I'm using a xenial system with Kernel 4.9.11-sunxi on LIME2 (actually it's an Olimex A20-SOM with external RTL8211 PHY) and trying to prevent the ethernet from coming up on boot.
When turning the system on, the ethernet interface will assign a random MAC address; later on my script sets a proper MAC from an assigned range. Until then the eth0 interface must stay down to prevent the network from being spammed with bogous messages.
This is because the ethernet interface chooses a random MAC address when the system boots up; later on a script sets the proper MAC address from an assigned range (along with IP and route configuration); The link must stay down until this has happened.
I've tried to replace the eth0 entries in /etc/network/interfaces with
auto eth0 inet manual
Which has the effect that the interface no longer gets a DHCP address, but I'm still seeing this in my dmesg log:
[ 15.972814] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 16.990692] sun7i-dwmac 1c50000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 16.990760] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
↧
↧
Unable to re-enable WiFi module
Hi there,
I am new to OrangePi and Linux as well and that's probably why I have faced my first problem I could not find an answer on web. I use OP Lite with the latest debian jessie.
And there is the problem (or just a bug):
after some time of using WiFi (and wwan) I wanted to disable it in order to reduce "excessive" power consumption. So firstly I had disabled it via "nmcli" and after a while I found out about "h3consumption" command. But recently I wanted to install (and download) but none of the above commands were able to re-enable them.
Any ideas how to re-enable (besides loading new OS image) ?
In addition, I noted that changind "h3consumption" is not able to change dram clockspeed.
↧
8189fs driver setting MTU on Kernel 4.10.0
Hi All,
I seem to be encountering an issue with setting the MTU for the 8189fs driver on the 4.10.0-sun8i kernel
I am trying to set the MTU for wlan0 to 1532. Note this works on the 3.4.113-sun8i kernel without issue.
#uname -a
Linux orangepipcplus-02c0008115dff7be 4.10.0-sun8i #10 SMP Sun Feb 12 16:51:59 AEST 2017 armv7l armv7l armv7l GNU/Linux
/etc/network/interfaces
----------------------------------------------------------------------------------------------------------------------------------
auto wlan0
iface wlan0 inet6 manual
wireless-channel 1
wireless-essid batnet6
wireless-mode ad-hoc
wireless-ap 02:13:13:13:13:13
mtu 1532
----------------------------------------------------------------------------------------------------------------------------------
# ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:e0:4c:67:db:86
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:12285 errors:0 dropped:3 overruns:0 frame:0
TX packets:673 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1693434 (1.6 MB) TX bytes:63171 (63.1 KB)
# ifconfig wlan0 mtu 1532
SIOCSIFMTU: Invalid argument
# /bin/ip link set mtu 1532 dev wlan0
RTNETLINK answers: Invalid argument
# ifup wlan0
sysctl: setting key "net.ipv6.conf.wlan0.mtu": Invalid argument
I did a bit of searching and found http://www.microhowto.info/howto/change_the_mtu_of_a_network_interface.html#idp42736
SIOCSIFMTU: Invalid argument
indicates that the requested MTU was rejected by the kernel. Typically this would be due to it exceeding the maximum value supported by the interface hardware. In that case you must either reduce the MTU to a value that is supported or obtain more capable hardware.
If this was a hardware restriction It wouldn't work on the 3.4.113-sun8i kernel, so this leads me to think its the driver on the 4.10.0-sun8i kernel.
Is anyone here familiar with the code of this driver and able to confirm for me if this is a known issue?
Thanks,
Dave.
↧
TC358743 drivers
Hello.
I've tried to find the TC358743 toshiba chip drivers in the kernel, but I can't. As far as I know they are included from 4.1 version, but in the menuconfig option I didn't found them. Is driver avaliable on this kernel or I should use another kernel?
↧
BananaPi Pro crash at shutdown/reboot with ARMBIAN 5.25 stable Ubuntu 16.04.2 LTS 3.4.113-sun7i
I tested the actual Xenial on my BPP but got a crashdump each time I reboot or shutdown the system.
I found, that armhwinfo was causing this crash by removing the module a20_tp.
Disabling the line
/sbin/modprobe -r $(cut -f1 -d' ' </proc/modules)
in /etc/init.d/armhwinfo avoid this problem.
This line is part of a patch Thomas Kaiser introduced in October last year.
I don't know, if this problem occurs only in my configuration (nothing special, but a connected Lemaker 5" LCD may be the difference), or it is related to the Kernel 3.4.113 only, but it goes reproducably wrong, if this line is active. It cause the oposite of the intention of this patch, because after the crash, the next module (sunxi_ir) is ending in a loop. So no sync is executed and the power stays on.
Without this line, all works well.
I think, the patch has to be patched again - don't touch a20_tp.
BR
Guido
↧
↧
NanoPI NEO (H3) Audio (kernel 4+)
Hi there,
I was wondering how to get the audio running on the NanoPI NEO.
It has line-out PINs and I read the H3 has SPDIF which should be the correct output.
So I found this post: https://forum.armbian.com/index.php/topic/1891-spdif-output-on-nanopi-m1/and changed my fex .
Anyway, that seems to be for the older kernel. What exactly do I need for version 4+?
I am using Gentoo and the sources from https://github.com/megous/linux .
The modules seem to be different and that's what I got right now:
sun4i_i2s 6408 0 sun4i_codec 12657 0 sun4i_spdif 5087 0 snd_soc_core 132869 3 sun4i_codec,sun4i_i2s,sun4i_spdif snd_pcm_dmaengine 4522 1 snd_soc_core snd_pcm 84734 3 sun4i_i2s,snd_pcm_dmaengine,snd_soc_core snd_timer 21349 1 snd_pcm snd 53569 3 snd_timer,snd_soc_core,snd_pcm soundcore 1112 1 snd
However, I got no devices listed in /proc/asound .
Thanks a lot for your efforts.
↧
PcDuino3 Nano - on board ethernet fails to load, mainline 4.9.7
Hello,
I just updated my pcduino3 nano with armbian mainline 4.9.7 download on SD card and now the onboard ethernet port fials.
I am using a USB to ethernet for now with no problems.
Below are the messages I get during boot
Feb 22 14:35:23 localhost kernel: [ 2435.162554] sun7i-dwmac 1c50000.ethernet: Failed to reset the dma
Feb 22 14:35:23 localhost kernel: [ 2435.168668] stmmac_hw_setup: DMA engine initialization failed
Feb 22 14:35:23 localhost kernel: [ 2435.174517] stmmac_open: Hw setup failed
I have tried several times to reset via cli and NetworkManager with the same results.
ip a & ip link show as down
seen in ifconfig but not able to change state
I am guessing the fix wil need to be during boot.
Anyone run into this?
Thanks for any help here!
Dave
↧
[OrangePi Plus 2] Question with external DD in usb more than 2to
Hello,
I want to branch a disque that have 3to or 4to to do my personnal backup of data.
Can I do this ? Can I branch it in the usb and do this ?
I format in ext4 ? or ntfs ? (with gpt mode).
Thanks
↧