Re: [SlimDevices: Unix] BETA: piCorePlayer6.0.0 - PI4 support
davis wrote: > To be honest I think I'll give up with the rPi0w and Bluetooth/WiFi > onboard. I've already got a DAC on the way, so I'm happy to wait for > that to arrive. Wires are pretty hard to argue with, and I can tuck it > all behind the speaker. > > Thanks for the support and advice thus far; this really is a great > project, and I suspect it's filled more than a few homes with music! Yep. DAC just arrived this morning, soldered the headers in place and just plugged it in. It all just works, and it replaces my dead SB3. Hurrah! davis's Profile: http://forums.slimdevices.com/member.php?userid=8771 View this thread: http://forums.slimdevices.com/showthread.php?t=110727 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] BETA: piCorePlayer6.0.0 - PI4 support
paul- wrote: > Davis, > > You need to add load the net usb kernel modules. > > Add a file named netusb. On your boot partition. Did you mean to address this to TWART016 rather than me? davis's Profile: http://forums.slimdevices.com/member.php?userid=8771 View this thread: http://forums.slimdevices.com/showthread.php?t=110727 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] BETA: piCorePlayer6.0.0 - PI4 support
paul- wrote: > Bluetooth is completely separate from the squeezelite page. Please send > your bluetooth logs. > > I think you are going to be disappointed in this setup, as the rpi > wireless chip does not play that nicely with WiFi and Bluetooth. > Using a usb WiFi stick getting it away from the rpi will work. Or use > one of the newer Rpi board that support 5G WiFi. To be honest I think I'll give up with the rPi0w and Bluetooth/WiFi onboard. I've already got a DAC on the way, so I'm happy to wait for that to arrive. Wires are pretty hard to argue with, and I can tuck it all behind the speaker. Thanks for the support and advice thus far; this really is a great project, and I suspect it's filled more than a few homes with music! davis's Profile: http://forums.slimdevices.com/member.php?userid=8771 View this thread: http://forums.slimdevices.com/showthread.php?t=110727 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] BETA: piCorePlayer6.0.0 - PI4 support
Paul Webster wrote: > Try taking the quotes out Ah, if I remove the quotes from the wpa_supplicant.conf file (which kinda contradicts the sample) to get the following line: country=GB then the kernel panic goes away, thanks. However the problem of "no sound" apparently continues, and I'm still not sure if I should see Bluetooth as a Squeezelite Output Device. davis's Profile: http://forums.slimdevices.com/member.php?userid=8771 View this thread: http://forums.slimdevices.com/showthread.php?t=110727 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] BETA: piCorePlayer6.0.0 - PI4 support
I have v6.0.0-b7 on an rPi0w. I'm trying to use both WiFi and Bluetooth
to create a totally wireless "Squeezebox".
I have enabled WiFi, and it joins my SSID ok, and I've paired with a
speaker successfully. However, I can't seem to actually get any sound
out (I've tried playing with volume, but I'm not ruling that out as a
cause). I suspect this is because the "Bluetooth" option isn't available
in the "Squeezelite settings" - the list goes "Analog Audio" straight to
"HDMI Audio" and "USB Audio". Has it been renamed?
I've also seen this kernel panic in my diagnostics page. Paul said this
was because I haven't set the WiFi country, but I did that when I
flashed the card (snippet below from webpage) - I used "GB" as per the
ISO code:
[ 27.282721] [ cut here ]
[ 27.283664] WARNING: CPU: 0 PID: 10 at net/wireless/reg.c:418
restore_regulatory_settings+0xb8/0x478 [cfg80211]
[ 27.283677] Unexpected user alpha2: "G
[ 27.283682] Modules linked in: rfcomm bnep spidev hci_uart serdev
btbcm bluetooth ecdh_generic brcmfmac brcmutil sha256_generic cfg80211
rfkill snd_soc_bcm2835_i2s regmap_mmio snd_soc_core snd_compress
snd_pcm_dmaengine snd_bcm2835(C) snd_pcm spi_bcm2835 snd_timer snd fixed
squashfs sch_fq_codel lz4 lz4_compress zram zsmalloc raspberrypi_hwmon
hwmon i2c_bcm2835
[ 27.283805] CPU: 0 PID: 10 Comm: kworker/0:1 Tainted: G C
4.19.80-pcpCore #1
[ 27.283810] Hardware name: BCM2835
[ 27.284650] Workqueue: events_power_efficient crda_timeout_work
[cfg80211]
[ 27.284703] [] (unwind_backtrace) from []
(show_stack+0x20/0x24)
[ 27.284734] [] (show_stack) from []
(dump_stack+0x20/0x28)
[ 27.284759] [] (dump_stack) from []
(__warn+0xe0/0x108)
[ 27.284774] [] (__warn) from []
(warn_slowpath_fmt+0x54/0x74)
[ 27.285623] [] (warn_slowpath_fmt) from []
(restore_regulatory_settings+0xb8/0x478 [cfg80211])
[ 27.287247] [] (restore_regulatory_settings [cfg80211])
from [] (crda_timeout_work+0x30/0x3c [cfg80211])
[ 27.288084] [] (crda_timeout_work [cfg80211]) from
[] (process_one_work+0x1f8/0x45c)
[ 27.288110] [] (process_one_work) from []
(worker_thread+0x3c/0x5a4)
[ 27.288126] [] (worker_thread) from []
(kthread+0x14c/0x164)
[ 27.288141] [] (kthread) from []
(ret_from_fork+0x14/0x28)
[ 27.288149] Exception stack(0xdd559fb0 to 0xdd559ff8)
[ 27.288159] 9fa0:
[ 27.288170] 9fc0:
[ 27.288180] 9fe0: 0013
[ 27.288187] ---[ end trace ef01fcab2e76a868 ]---
wpa_supplicant.conf:
country="GB"
update_config=1
# This is the details about your Wireless network. Configure as needed.
# Most will just need to change the ssid and psk.
network={
ssid="secret"
psk="password"
key_mgmt=WPA-PSK
auth_alg=OPEN
}
davis's Profile: http://forums.slimdevices.com/member.php?userid=8771
View this thread: http://forums.slimdevices.com/showthread.php?t=110727
___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: piCorePlayer 3.5.0
paul- wrote: > There must be a dependancy issue in 5.0.0. I'll have to check. I would > recommend using the 6.0.0-b7 for bluetooth. In my experience it works > much better. Hmm. That seems significantly better, in that the bluetooth page allows me to discover and pair with a speaker, but the "Bluetooth" option has now disappeared from the audio output options and now Squeezelite seems to fail to run. I'm still looking for the debug logs on that, but if I had to guess I think it's something to do with the fact that the pairing connection is lost after rebooting PCP. I'll continue poking about because it seems so close to being perfect! davis's Profile: http://forums.slimdevices.com/member.php?userid=8771 View this thread: http://forums.slimdevices.com/showthread.php?t=108852 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] Announce: piCorePlayer 3.5.0
Hi, I've just installed piCorePlayer v5.0.0 on an rpi0w, and I thought I'd try out a Bluetooth connection while I wait for the DAC to arrive. I know it's experimental, and beta, and that's completely understood. However, when I try to scan for devices, it simply shows the line "[ INFO ] Scanning for Bluetooth Devices, make sure device is in pair mode..." and doesn't actually show any scan results. The "pair" dropdown-list remains empty too. I took a look, and I /think/ this is because the WebUI relies on the utility "bluetoothctl" (called from /usr/local/bin/pcp-bt-functions), which in turn relies on libreadline.so.8. I don't think this is installed, or similar, because when I try to run "bluetoothctl" manually from an ssh session I get: "bluetoothctl: error while loading shared libraries: libreadline.so.8: cannot open shared object file: No such file or directory". I did try installing the readline package from the repo (which took some reading about TCB's packaging!) but it says it was already installed. I know the bluetooth hardware is working, because I can use "hcitool scan" and see the speakers I'm trying to pair with. Does this make any kind of sense? Can I add the device manually, bypassing bluetoothctl? (great project anyway; sadly a couple of my squeezeboxes died so I'm building their replacements) davis's Profile: http://forums.slimdevices.com/member.php?userid=8771 View this thread: http://forums.slimdevices.com/showthread.php?t=108852 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
Re: [SlimDevices: Unix] ffmpeg on fedora 9, t5720 and SC 7.2
Well, you need to find out if it's only files on the net-mounted filesystem, or if it's every file you try to play. It's difficult to make suggestions when there is more than one cause of the problem you're experiencing. Also, I don't really understand what you mean by music on my slimp3 Fedora 9 on a USB stick, on an HP T5720 with music on a mounted net drive -- davis davis's Profile: http://forums.slimdevices.com/member.php?userid=8771 View this thread: http://forums.slimdevices.com/showthread.php?t=54275 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/unix
Re: [SlimDevices: Unix] ffmpeg on fedora 9, t5720 and SC 7.2
Ok, to paraphrase, I believe you're saying you have a problem when SqueezeCenter is serving files sourced from a NAS (or similar) drive. SqueezeCenter is running on an HP T5720 thin client machine running Fedora 9 Live from a USB stick. Is my understanding correct? If so, I'd suggest getting SqueezeCenter to serve a file from a more local source (perhaps copy one to the USB stick). This will allow you to see if it's related to network activity. If it's related to network activity, I'd be inclined to look at network card driver versions on the Fedora live distribution (assuming you've checked network card speed and duplex). It appears from Googling that the T5720 is an AMD-based machine; it's only empirical (and quite likely to attract flames) but I've found AMD-based machines tend to have chipsets which have worse Linux driver support than Intel-based machines (that's just my experience -- yours may work wonderfully!). Do you know what network card the T5720 has? You could also try playing a lower bitrate version of the file to see if that helps, and, if it does, I'd look at trying a different distribution with a more recent driver (perhaps Fedora 10 beta). -- davis davis's Profile: http://forums.slimdevices.com/member.php?userid=8771 View this thread: http://forums.slimdevices.com/showthread.php?t=54275 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/unix
Re: [SlimDevices: Unix] Squeezecenter scan not finding any music
cjbrooker;288945 Wrote: Could someone read through it to check it makes sense and is correct? Looks good to me; nice work. -- davis davis's Profile: http://forums.slimdevices.com/member.php?userid=8771 View this thread: http://forums.slimdevices.com/showthread.php?t=45901 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/unix
Re: [SlimDevices: Unix] Squeezecenter scan not finding any music
Have you ever had SqueezeCenter finding your music? What directory have you told SqueezeCenter to search? Does the user squeezecenter have permission to view your music? Here's what I've just tried (as root): chsh -s /bin/bash squeezecenter # Set sc's shell to bash to allow login su - squeezecenter # change to sc user ls -al /home/public/music/06_the_sunshine_underground.flac #list file info ###Output omitted, but successful metaflac --list /home/public/music/06_the_sunshine_underground.flac ###Output omitted, but successful exit# exit sc user shell chsh -s /sbin/nologin squeezecenter # set shell back as it was If you're using e.g. Oggs or MP3s you'll have to change the metaflac --list to ogginfo or mp3info or whatever. Basically you're just checking that the user squeezecenter can view stuff inside the path you've given to SqueezeCenter (check, and double-check the paths). cheers -- davis davis's Profile: http://forums.slimdevices.com/member.php?userid=8771 View this thread: http://forums.slimdevices.com/showthread.php?t=45901 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/unix
Re: [SlimDevices: Unix] Squeezecenter scan not finding any music
cjbrooker;288603 Wrote:
I have the following permissions for directories: drwxr--r--
and the following for files:-rw-r--r--
What are the recommended permissions for music files and directories in
*nix environments in order for squeezecenter to access them? I thought
squeezecenter would only need read access.
That's the problem (probably). In Unix-style systems, the relevant user
(squeezecenter) *must* have Execute x access on *all* *parent*
directories.
I.e. if, for example, your music is in
/home/public/music/foo/track.ogg, you want world-executable and
world-readable (mode 755) on /home, /home/public/,
/home/public/music, and /home/public/music/foo/.
The following commands will probably sort it out for you
===
cd /home/public/music #or wherever your music is
chmod -R a+r *# add read permission recursively to everything
find . -type d -exec chmod go+rx {} \; # Add read+exec perms to
directories
===
The punctuation at the end of the find command is important: it reads
open-braces, close-braces, space, backslash, semi-colon.
cheers
--
davis
davis's Profile: http://forums.slimdevices.com/member.php?userid=8771
View this thread: http://forums.slimdevices.com/showthread.php?t=45901
___
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/lists/listinfo/unix
Re: [SlimDevices: Unix] squeezebox on eth1 using a crossover cable?
snarlydwarf;182548 Wrote: As for gateway, you don't want to set a gateway on eth1 on the linux box and you want to tell the SB to use the Linux box as the gateway. Routing should be enabled on the Linux box. Eh? You wouldn't need routing at all. The SB is on the same IP subnet as the linux box. Setting the SB's default route to be the IP address of the linux box's eth1 interface wouldn't hurt however, it just wouldn't get used as the SB would have no reason to go outside the 192.168.1.0 subnet. snarlydwarf;182548 Wrote: A $20 switch will do this much easier, tho. A switch wouldn't make any difference -- the problems are at the IP level, not the ethernet level. -- davis davis's Profile: http://forums.slimdevices.com/member.php?userid=8771 View this thread: http://forums.slimdevices.com/showthread.php?t=32991 ___ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/unix
