dony71
-
Posts
128 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by dony71
-
-
2 hours ago, Igor said:
I did and also did't saw AP. Than I try the same on Friendly ARM M1+ which uses the same wireless chip and it's working. Than I used nanopim1plus.bin on Banana M2+ and it's working there too ... which means stock board configuration is messed up.Manage to get nanopim2plus fex at https://github.com/igorpecovnik/lib/blob/master/config/fex/nanopim1plus.fex
I compare and found differences only in bluetooth gpio pin assignment below
It should not affect any function on wifi, but you mentioned using nanopim1plus.bin on bpim2+ then AP shows up? strange .....
[bt_para]
bt_used = 1 bt_uart_id = 3 bt_uart_baud = 115200 bt_rst_n = port:PG13<1><default><default><0> bt_wake = port:PA08<1><default><default><0> bt_host_wake = port:PA07<0><default><default><0> bt_host_wake_invert = 0 -
On 4/6/2017 at 0:39 AM, Igor said:
I am running out of ideas. Try changing channel, change SSID ... When you got this at running hostapd:
wlan1: AP-ENABLEDYou should see your AP even your network settings are wrong. Those must be correct only when you are trying to connect.
change channel and SSID, but still same problem, SSID is not shown
what is this message below referring to?
nl80211: Could not re-add multicast membership for vendor events: -2 (No such file or directory) -
2 minutes ago, Igor said:
I guess there is bcmdhd modile in /etc/modules ... and it loads automatically - remove it and reboot if you want to "modprobe bcmdhd op_mode=2" ... It looks that you properly enabled AP mode since you won't get this in first place:
nl80211: Could not re-add multicast membership for vendor events: -2 (No such file or directory) Using interface wlan1 with hwaddr 94:a1:a2:ca:17:d8 and ssid "BPi-M2P" wlan1: interface state UNINITIALIZED->ENABLED wlan1: AP-ENABLEDAccording to this log, AP mode is working, while the network part, when removing op_mode=2 from interfaces file, should also be fine. Not two things: this driver is shit and you will get some errors and driver might crash on unloading, so you need to reboot each time you need to load it with different settings.
BTW. The kernel is not ours while I assume nothing vital has been changed.
yes, this is retrorangpie kernel which based on armbian 5.23 (http://www.retrorangepi.org/)
i don't get it what you mean ... so how to fix this since i don't see AP SSID
-
-
8 minutes ago, Igor said:
op_mode=2 does not go to the interfaces but elsewhere. The rest is o.k. and you need to reboot after those changes.
i put in /etc/modules-load.d/module.conf
bcmdhd op_mode=2but still same failure
then i do "modprobe bcmdhd op_mode=2"
root@RetrOrangePi:/etc/modules-load.d# modprobe bcmdhd op_mode=2
modprobe: FATAL: Module bcmdhd not found.but wifi is working fine in client mode, so bcmdhd should be already loaded
-
3 minutes ago, Igor said:
If you have more or less default /etc/networkl/interfaces, you need to alter your network configuration, from this to this and reboot.
Those days I am working on some configuration and all this will be possible to enable with a wizard.just attach my interfaces file
seems already follow your recommendation -
Anybody can guide me how to enable wifi in AP mode?
I already follow https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-set-wireless-access-point
Also add op_mode=2 in /etc/network/interfaces (see attached file)
However when I run "hostapd /etc/hostapd.conf", it shows message below and AP not running
Anything I'm missing?------------------------------------------------------------------------------------------------------------------------------
root@RetrOrangePi:/etc# hostapd /etc/hostapd.conf
Configuration file: /etc/hostapd.conf
nl80211: Could not re-add multicast membership for vendor events: -2 (No such file or directory)
Using interface wlan1 with hwaddr 94:a1:a2:ca:17:d8 and ssid "BPi-M2P"
wlan1: interface state UNINITIALIZED->ENABLED
wlan1: AP-ENABLED
-
-
I want to upgrade from legacy kernel to mainline kernel to enable uasp driver
Does the script work also for allwinner H3 device such as Banana Pi M2+ ?
-
I just purchased JM567 USB-SATA adapter and using Armbian 5.23 Jessie Desktop.
However "dmesg | grep uas" doesn't show anything.
It seems that usb uasp is not enable by default.
Can anybody tell me how to enable uasp ?
root@RetrOrangePi:~# modprobe uas
modprobe: FATAL: Module uas not found.
strange ... I though armbian 5.23 which has already kernel compiled with CONFIG_USB_UAS=y ???
-
I just purchased JM567 USB-SATA adapter and using Armbian 5.23 Jessie Desktop.
However "dmesg | grep uas" doesn't show anything.
It seems that usb uasp is not enable by default.
Can anybody tell me how to enable uasp ?
-
I think the developer (E.Jurgensen) might be willing to help. So I would suggest to ask him directly in this thread:
https://www.raspberrypi.org/forums/viewtopic.php?t=49928
I know this is a Raspberry-Pi Forum, but regarding sound-card configuration there should be no difference. Maybe he has an idea, or another user has a similar setup to yours. If you can solve your problem it would be nice to post the solution here as well.
Best wishes, Bernie_O
Thanks
Will post the solution here
-
I have no idea too. Please try to experiment, maybe comment out this line, use something like "default" or "dmix".
try mixer = "dmix" or mixer = "default", not working
forked-daapd has very poor documentation regarding sound output setting
now to find correct setting, it's like trying to find needle in the desert
-
So you need to change the mixer line too in the config
i have no idea change to what?
-
Please try
card = "default"
in forked-daapd
/var/log/forked-daapd.log
----------------------------------------
[2017-01-16 12:28:51] [ LOG] laudio: Failed to open configured mixer element 'I2s Or Pcm Audio Mode Select format'[2017-01-16 12:28:51] [ LOG] laudio: Could not open mixer[2017-01-16 12:28:51] [ LOG] player: Could not start ALSA device 'BPi-M2P'[2017-01-16 12:28:51] [ LOG] player: Could not activate ALSA device 'BPi-M2P'FYI, sound output is OK by testing "aplay -f cd -D default test.wav" -
You need to create ctl.!default block in asoundrc too, since the log tells that it fails to open the mixer controls.
Also I may be wrong about referencing the card in forked-daapd, you should check its manuals too.
I read below link under software mixing
https://www.alsa-project.org/main/index.php/Asoundrc#dmix
I follow .asoundrc overthere and aplay running with default device
unfortunately forked-daapd has very limited reference for the card
-
change card = "plug:default"
/var/log/forked-daapd.log
-------------------------------
[2017-01-16 02:29:33] [ LOG] laudio: Invalid CTL plug:default[2017-01-16 02:29:33] [ LOG] laudio: Failed to attach mixer: No such file or directory[2017-01-16 02:29:33] [ LOG] laudio: Could not open mixer[2017-01-16 02:29:33] [ LOG] player: Could not start ALSA device 'BPi-M2P'[2017-01-16 02:29:33] [ LOG] player: Could not activate ALSA device 'BPi-M2P' -
But you are still telling your applications to use "hw:1" directly and thus bypassing the dmix. If your default configuration is correct, you should be able to use something like "plug:default" in applications too.
/var/log/forked-daapd.log
-------------------------------
[2017-01-16 02:27:51] [ LOG] laudio: Invalid CTL plug:dmix[2017-01-16 02:27:51] [ LOG] laudio: Failed to attach mixer: No such file or directory[2017-01-16 02:27:51] [ LOG] laudio: Could not open mixer[2017-01-16 02:27:51] [ LOG] player: Could not start ALSA device 'BPi-M2P'[2017-01-16 02:27:51] [ LOG] player: Could not activate ALSA device 'BPi-M2P' -
Yes, you need to set it as a default ALSA input or you need to tell your applications to use dmix explicitly (instead of "hw:1" it should be something like "plug:dmix" if I remember correctly.
I change .asoundrc to this below, but still not working
-----------------------------------------------------------------------
pcm.!default {
type plug
slave.pcm "dmixer"
}
pcm.dmixer {
type dmix
ipc_key 1024
slave {
pcm "hw:1,0"
period_time 0
period_size 1024
buffer_size 4096
rate 44100
}
bindings {
0 0
1 1
}
}
ctl.dmixer {
type hw
card 1
}
-
dmix if we are talking about ALSA, otherwise pulseaudio can do this too.
I do have already enable dmixer in .asoundrc
Am I missing something?
.asoundrc
-----------------------------------------------------------
pcm.snd_card {type hwcard 1device 0}ctl.snd_card {type hwcard 1device 0}pcm.dmixer {type dmixipc_key 1024ipc_perm 0666slave.pcm snd_cardslave {period_time 0period_size 1024buffer_size 4096rate 44100format S32_LEchannels 2}bindings {0 01 1}} -
This looks like forked-daapd is trying to access the correct device, but there is another service/application running which accesses and thus blocks the audio device - or another application was running which used the audio device and didn't free the access again after using that audio-device.
Do you have an idea what that could be? Try to disable it (or maybe reboot) and then try again with forked-daapd.
I think we found the correct card and mixer. But with the "device or resource busy" problem I can't help any further. This you need to figure out yourself. Good luck :-)
shairport-sync is using this audio device
however i didn't hard lock the device, instead i'm using .asoundrc in /home/shairport-sync
my understanding by doing this, hw:1,0 can be switched, activated upon usage selection, but seems it's not the case
do you know anyway to share same device by multiple application?
-
This doesn't work?
card = "hw:1" mixer = "I2s Or Pcm Audio Mode Select format"
/var/log/forked-daapd.log
---------------------------------
[2017-01-15 00:05:54] [ LOG] laudio: open '/dev/snd/pcmC1D0p' failed (-16)[2017-01-15 00:05:54] [ LOG] laudio: Could not open playback device: Device or resource busy[2017-01-15 00:05:54] [ LOG] player: Could not start ALSA device 'BPi-M2P'[2017-01-15 00:05:54] [ LOG] player: Could not activate ALSA device 'BPi-M2P' -
amixer --card 1-----------------------------------------------------------------------------------Simple mixer control 'I2s Or Pcm Audio Mode Select format',0Capabilities: pswitch pswitch-joinedPlayback channels: MonoMono: Playback [on]Change in /etc/forked-daapd.conf.....mixer = "I2s Or Pcm Audio Mode Select format"
/var/log/forked-daapd.log
-----------------------------------
[2017-01-14 22:31:03] [ LOG] laudio: Failed to open configured mixer element 'I2s Or Pcm Audio Mode Select format'[2017-01-14 22:31:03] [ LOG] laudio: Could not open mixer[2017-01-14 22:31:03] [ LOG] player: Could not start ALSA device 'BPi-M2P'[2017-01-14 22:31:03] [ LOG] player: Could not activate ALSA device 'BPi-M2P' -
I have Banana Pi M2+ and use PCM5102 DAC via I2S
So far I know PCM5102 doesn't have digital mixer to control volume
"amixer" output below, no mixer for PCM ??
==================================================
Simple mixer control 'Lineout volume control',0
Capabilities: volume volume-joinedPlayback channels: MonoCapture channels: MonoLimits: 0 - 31Mono: 31 [100%]Simple mixer control 'ADC input gain ctrl',0Capabilities: volume volume-joinedPlayback channels: MonoCapture channels: MonoLimits: 0 - 7Mono: 3 [43%]Simple mixer control 'Audio adda drc',0Capabilities: pswitch pswitch-joinedPlayback channels: MonoMono: Playback [off]Simple mixer control 'Audio adda loop',0Capabilities: pswitch pswitch-joinedPlayback channels: MonoMono: Playback [off]Simple mixer control 'Audio linein in',0Capabilities: pswitch pswitch-joinedPlayback channels: MonoMono: Playback [off]Simple mixer control 'Audio lineout',0Capabilities: pswitch pswitch-joinedPlayback channels: MonoMono: Playback [on]Simple mixer control 'LINEIN_G boost stage output mixer control',0Capabilities: volume volume-joinedPlayback channels: MonoCapture channels: MonoLimits: 0 - 7Mono: 3 [43%]Simple mixer control 'MIC1 boost AMP gain control',0Capabilities: volume volume-joinedPlayback channels: MonoCapture channels: MonoLimits: 0 - 7Mono: 4 [57%]Simple mixer control 'MIC1_G boost stage output mixer control',0Capabilities: volume volume-joinedPlayback channels: MonoCapture channels: MonoLimits: 0 - 7Mono: 3 [43%]Simple mixer control 'MIC2 boost AMP gain control',0Capabilities: volume volume-joinedPlayback channels: MonoCapture channels: MonoLimits: 0 - 7Mono: 4 [57%]Simple mixer control 'MIC2_G boost stage output mixer control',0Capabilities: volume volume-joinedPlayback channels: MonoCapture channels: MonoLimits: 0 - 7Mono: 3 [43%]Simple mixer control 'audio capture mode',0Capabilities: enumItems: 'main mic' 'mic1_2' 'linein'Item0: 'main mic'
Banana Pi M2plus & inboard wifi [solved]
in Allwinner sunxi
Posted
This is it !!!
Thank you for your support