Pi3 and DAC+ Pro

Raspberry Pi related support

Re: Pi3 and DAC+ Pro

Postby aleksas » 31 Mar 2016, 14:52

I have contacted HifiBerry support team for assistance, their response was that something is wrong with RuneAudio since no such issue was noticed on Raspbian. I'll try to install Raspbian to confirm that's the case.
aleksas
 
Posts: 4
Joined: 27 Jan 2016, 13:39

Re: Pi3 and DAC+ Pro

Postby hondagx35 » 31 Mar 2016, 16:55

Hi,

their response was that something is wrong with RuneAudio since no such issue was noticed on Raspbian.

I know that, but as we use Arch Linux it is a bit different.

From here i suspect they never tried it on Arch Linux, he always talks about Raspbien.

Sorry, but as already mentioned without the hardware i'm unable to debug.

Frank
User avatar
hondagx35
 
Posts: 3042
Joined: 11 Sep 2014, 22:06
Location: Germany

Re: Pi3 and DAC+ Pro

Postby jimmeuh » 31 Mar 2016, 20:40

I've tried this again with no improvement:
pacman -Sy --force raspberrypi-firmware-bootloader linux-raspberrypi


Frank I understand that you can't test without the same hardware.
Can you maybe set us on track?
What can be the issue? bad kernel modules?
jimmeuh
 
Posts: 28
Joined: 16 Mar 2016, 19:47

Re: Pi3 and DAC+ Pro

Postby hondagx35 » 31 Mar 2016, 21:31

Hi,

What can be the issue? bad kernel modules?

The kernel modules should be the same for both Raspbian and Arch Linux.
The only thing i can think about is that there is an issue with Arch Linux.

I would try this:

- setting up a fresh installation
- mount the DAC+ pro
- attach a monitor and keyboard to the Pi
- connect ethernet
- boot
- switch off "local browser"
- enable DAC+ pro
- reboot
- set up the wifi profile
- reboot without ethernet connected
- see what happens

If wifi doesn't work:
- check logs
Code: Select all
journalctl
dmesg
systemctl status netctl-auto@wlan0


- restart netctl service
Code: Select all
systemctl restart netctl-auto@wlan0

- check logs again

Frank
User avatar
hondagx35
 
Posts: 3042
Joined: 11 Sep 2014, 22:06
Location: Germany

Re: Pi3 and DAC+ Pro

Postby jimmeuh » 01 Apr 2016, 19:58

Thanks Frank for your efforts!

I don't have the chance to connect a monitor at the moment, but noticed this:

When booting the "wlan0 already exists" error is in the dmesg.
Same as when I restart the netctl service:
Code: Select all
Apr 01 20:55:45 runeaudio systemd[1]: Stopping Automatic wireless network connection using netctl profiles...
Apr 01 20:55:45 runeaudio wpa_actiond[259]: Terminating wpa_actiond session for interface 'wlan0'
Apr 01 20:55:47 runeaudio systemd[1]: Stopped Automatic wireless network connection using netctl profiles.
Apr 01 20:55:47 runeaudio systemd[1]: Starting Automatic wireless network connection using netctl profiles...
Apr 01 20:55:47 runeaudio netctl-auto[1353]: Included profile 'waves'
Apr 01 20:55:47 runeaudio kernel: brcmfmac: power management disabled
Apr 01 20:55:47 runeaudio kernel: brcmfmac: brcmf_add_if: ERROR: netdev:wlan0 already exists
Apr 01 20:55:47 runeaudio kernel: brcmfmac: brcmf_add_if: ignore IF event
Apr 01 20:55:47 runeaudio netctl-auto[1353]: Could not read interface p2p-dev-wlan0 flags: No such device
Apr 01 20:55:47 runeaudio wpa_actiond[1380]: Starting wpa_actiond session for interface 'wlan0'
Apr 01 20:55:47 runeaudio systemd[1]: Started Automatic wireless network connection using netctl profiles.


Then I play some tunes. Still no wifi, nothing in the journal.
Then I click the MPD settings page at 21:00 and check the journal:

Code: Select all
Apr 01 21:00:37 runeaudio kernel: cfg80211: Calling CRDA for country: BE
Apr 01 21:00:37 runeaudio wpa_actiond[1380]: Interface 'wlan0' connected to network 'waves'


And wifi is back


When I look further at dmesg I notice that it sets its countrycode to "DE" on boot.
Can this be a problem?

Code: Select all
[    6.956879] cfg80211: Calling CRDA to update world regulatory domain
[    6.983382] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Dec 15 2015 18:10:45 version 7.45.41.23 (r606571) FWID 01-cc4eda9c
[    6.998466] cfg80211: Updating information on frequency 2412 MHz with regulatory rule:
[    6.998477] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[    6.998482] cfg80211: Updating information on frequency 2417 MHz with regulatory rule:
[    6.998487] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[    6.998492] cfg80211: Updating information on frequency 2422 MHz with regulatory rule:
[    6.998497] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[    6.998501] cfg80211: Updating information on frequency 2427 MHz with regulatory rule:
[    6.998506] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[    6.998511] cfg80211: Updating information on frequency 2432 MHz with regulatory rule:
[    6.998516] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[    6.998520] cfg80211: Updating information on frequency 2437 MHz with regulatory rule:
[    6.998525] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[    6.998529] cfg80211: Updating information on frequency 2442 MHz with regulatory rule:
[    6.998534] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[    6.998538] cfg80211: Updating information on frequency 2447 MHz with regulatory rule:
[    6.998543] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[    6.998548] cfg80211: Updating information on frequency 2452 MHz with regulatory rule:
[    6.998552] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[    6.998557] cfg80211: Updating information on frequency 2457 MHz with regulatory rule:
[    6.998562] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[    6.998566] cfg80211: Updating information on frequency 2462 MHz with regulatory rule:
[    6.998571] cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[    6.998675] cfg80211: Ignoring regulatory request set by core since the driver uses its own custom regulatory domain
[    6.998682] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
[    7.021678] cfg80211: Ignoring regulatory request set by core since the driver uses its own custom regulatory domain
[    7.021693] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
[    7.021699] cfg80211: World regulatory domain updated:
[    7.021703] cfg80211:  DFS Master region: unset
[    7.021707] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[    7.021714] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[    7.021719] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[    7.021725] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[    7.021731] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[    7.021737] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[    7.021743] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[    7.021748] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[    7.021753] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[    7.022290] cfg80211: Calling CRDA for country: DE
[    7.038428] cfg80211: Updating information on frequency 2412 MHz with regulatory rule:
[    7.038439] cfg80211: 2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[    7.038444] cfg80211: Updating information on frequency 2417 MHz with regulatory rule:
[    7.038449] cfg80211: 2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[    7.038453] cfg80211: Updating information on frequency 2422 MHz with regulatory rule:
[    7.038458] cfg80211: 2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[    7.038463] cfg80211: Updating information on frequency 2427 MHz with regulatory rule:
[    7.038467] cfg80211: 2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[    7.038472] cfg80211: Updating information on frequency 2432 MHz with regulatory rule:
[    7.038477] cfg80211: 2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[    7.038481] cfg80211: Updating information on frequency 2437 MHz with regulatory rule:
[    7.038486] cfg80211: 2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[    7.038490] cfg80211: Updating information on frequency 2442 MHz with regulatory rule:
[    7.038495] cfg80211: 2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[    7.038499] cfg80211: Updating information on frequency 2447 MHz with regulatory rule:
[    7.038504] cfg80211: 2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[    7.038508] cfg80211: Updating information on frequency 2452 MHz with regulatory rule:
[    7.038513] cfg80211: 2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[    7.038517] cfg80211: Updating information on frequency 2457 MHz with regulatory rule:
[    7.038522] cfg80211: 2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[    7.038526] cfg80211: Updating information on frequency 2462 MHz with regulatory rule:
[    7.038531] cfg80211: 2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
[    7.079026] cfg80211: Regulatory domain changed to country: DE
[    7.079037] cfg80211:  DFS Master region: ETSI
[    7.079041] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[    7.079047] cfg80211:   (2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[    7.079054] cfg80211:   (5150000 KHz - 5250000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[    7.079060] cfg80211:   (5250000 KHz - 5350000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[    7.079066] cfg80211:   (5470000 KHz - 5725000 KHz @ 160000 KHz), (N/A, 2698 mBm), (0 s)
[    7.079071] cfg80211:   (57000000 KHz - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
[    7.276893] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[    7.530078] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[    8.023085] brcmfmac: brcmf_add_if: ERROR: netdev:wlan0 already exists
[    8.023096] brcmfmac: brcmf_add_if: ignore IF event
[    8.026837] brcmfmac: power management disabled
jimmeuh
 
Posts: 28
Joined: 16 Mar 2016, 19:47

Re: Pi3 and DAC+ Pro

Postby hondagx35 » 01 Apr 2016, 20:35

Hi,

you can set the regdom with
Code: Select all
iw reg set XX

XX = countrycode
DE = germany
US = united states

For all country codes see /etc/conf.d/wireless-regdom

Frank
User avatar
hondagx35
 
Posts: 3042
Joined: 11 Sep 2014, 22:06
Location: Germany

Re: Pi3 and DAC+ Pro

Postby jimmeuh » 01 Apr 2016, 20:54

Changed the code, rebooted -> dmesg still shows DE

Changed the code -> journalctl:

Code: Select all
Apr 01 21:54:32 runeaudio kernel: cfg80211: Calling CRDA for country: BE
Apr 01 21:54:32 runeaudio kernel: cfg80211: Updating information on frequency 2412 MHz with regulatory rule:
Apr 01 21:54:32 runeaudio kernel: cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Apr 01 21:54:32 runeaudio kernel: cfg80211: Updating information on frequency 2417 MHz with regulatory rule:
Apr 01 21:54:32 runeaudio kernel: cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Apr 01 21:54:32 runeaudio kernel: cfg80211: Updating information on frequency 2422 MHz with regulatory rule:
Apr 01 21:54:32 runeaudio kernel: cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Apr 01 21:54:32 runeaudio kernel: cfg80211: Updating information on frequency 2427 MHz with regulatory rule:
Apr 01 21:54:32 runeaudio kernel: cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Apr 01 21:54:32 runeaudio kernel: cfg80211: Updating information on frequency 2432 MHz with regulatory rule:
Apr 01 21:54:32 runeaudio kernel: cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Apr 01 21:54:32 runeaudio kernel: cfg80211: Updating information on frequency 2437 MHz with regulatory rule:
Apr 01 21:54:32 runeaudio kernel: cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Apr 01 21:54:32 runeaudio kernel: cfg80211: Updating information on frequency 2442 MHz with regulatory rule:
Apr 01 21:54:32 runeaudio kernel: cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Apr 01 21:54:32 runeaudio kernel: cfg80211: Updating information on frequency 2447 MHz with regulatory rule:
Apr 01 21:54:32 runeaudio kernel: cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Apr 01 21:54:32 runeaudio kernel: cfg80211: Updating information on frequency 2452 MHz with regulatory rule:
Apr 01 21:54:32 runeaudio kernel: cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Apr 01 21:54:32 runeaudio kernel: cfg80211: Updating information on frequency 2457 MHz with regulatory rule:
Apr 01 21:54:32 runeaudio kernel: cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Apr 01 21:54:32 runeaudio kernel: cfg80211: Updating information on frequency 2462 MHz with regulatory rule:
Apr 01 21:54:32 runeaudio kernel: cfg80211: 2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A mBi, 2000 mBm)
Apr 01 21:54:32 runeaudio kernel: cfg80211: Regulatory domain changed to country: BE
Apr 01 21:54:32 runeaudio kernel: cfg80211:  DFS Master region: ETSI
Apr 01 21:54:32 runeaudio kernel: cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Apr 01 21:54:32 runeaudio kernel: cfg80211:   (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
Apr 01 21:54:32 runeaudio kernel: cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
Apr 01 21:54:32 runeaudio kernel: cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
Apr 01 21:54:32 runeaudio kernel: cfg80211:   (5490000 KHz - 5710000 KHz @ 160000 KHz), (N/A, 2700 mBm), (0 s)
Apr 01 21:54:32 runeaudio kernel: cfg80211:   (57000000 KHz - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)


No wifi yet

Start playing songs and switch to MPD tab 10 seconds later wifi is back and I see this:

Code: Select all
Apr 01 21:57:33 runeaudio kernel: cfg80211: Verifying active interfaces after reg change
jimmeuh
 
Posts: 28
Joined: 16 Mar 2016, 19:47

Re: Pi3 and DAC+ Pro

Postby hondagx35 » 01 Apr 2016, 21:04

Hi jimmeuh,

check which channel your WiFi access point is on.
In my experience channels 12 and 13 do not work on RP3, even if the internationalisation is set correctly.

Frank
User avatar
hondagx35
 
Posts: 3042
Joined: 11 Sep 2014, 22:06
Location: Germany

Re: Pi3 and DAC+ Pro

Postby jimmeuh » 01 Apr 2016, 21:10

channel 11
jimmeuh
 
Posts: 28
Joined: 16 Mar 2016, 19:47

Re: Pi3 and DAC+ Pro

Postby hondagx35 » 02 Apr 2016, 23:48

Hi jimmeuh,

any news on this?

Frank
User avatar
hondagx35
 
Posts: 3042
Joined: 11 Sep 2014, 22:06
Location: Germany

support RuneAudio Donate with PayPal

PreviousNext

Return to Raspberry Pi

Who is online

Users browsing this forum: No registered users and 4 guests
cron