JackOfAll wrote:
I'm clutching at straws, but I've got a sneeky feeling that your
problems might be related to the selinux-policy bug that causes package
scriptlets to fail. 'rpm scriptlets are exiting with status 127'
(https://bugzilla.redhat.com/show_bug.cgi?id=1054350).
Might be worth
bcdaus wrote:
My HiFiBerry DAC arrived today and I wasted no time in connecting it up.
Issue is that I get no audio output. What is the recommended way of
setting it up. I tried scanning for USB devices but it does not show.
What parameters should I pass or will it just auto-magically be
lintweaker wrote:
Ugh, yes indeed! I've been investigating the whole night yesterday :(
Did not think of it could be a selinux thing.
What a screw up...very nasty. Fedora QA control:confused:
Yep, it seems to be a bit of a pickle. I've got selinux disabled on one
machine and set to
Hi,
I get yesterday the CSOS-Wandboard-Quad-F19-R2-20130910-1.img.7z image
and was a little bit unhappy because it doesn't fit at my 8GB card. So I
need to bought a bigger one. So I bought it from the dealer nearby and
start the tests.
I run several FLAC and MP3 and everything runs fine except
Mr. Floppy wrote:
I get yesterday the CSOS-Wandboard-Quad-F19-R2-20130910-1.img.7z image
and was a little bit unhappy because it doesn't fit at my 8GB card. So I
need to bought a bigger one. So I bought it from the dealer nearby and
start the tests.
Not all cards being sold as 8GB cards
I had that same issue with my 8gb cards and had to re-buy 16gb cards to
be sure it'd fit. Is there a reason the partition couldn't be slightly
smaller before imaging in order to increase compatibility with smaller
8gb cards?
I'm a bit nervous of saying anything at all about the the HiFiBerry, as
it could be taken as sour grapes, me working on a similar project and
all. So I'll limit my comments to suggesting that as this DAC chip is
from the same family as the one being used for the CS hardware, that
if the Pi is has
JRatron wrote:
I had that same issue with my 8gb cards and had to re-buy 16gb cards to
be sure it'd fit. Is there a reason the partition couldn't be slightly
smaller before imaging in order to increase compatibility with smaller
8gb cards?
It might help picking the right size, if you could
JackOfAll wrote:
Yep, for 29 EUROS, who cares that it is probably using the on-chip PLL
driven by BCK from Pi. It'll end up being more expensive, but if this
was me, I'd have used the ES9023 in async with a very high quality 50MHz
clock. But John (Swenson) likes the TI chip family. And I
Just a question: since I'm running the Pi+HiFiBerry setup here, I'd like
to try the upsampling you suggest. Can I do that with the provided
Squeezelite build and what should I set the - u parameter to?
CommanderROR's
Reeshar wrote:
Using the same clock as the Pi doesn't guarantee quality especially as a
PLL
I wouldn't want to be using any clock generated by the Pi! ;)
Reeshar wrote:
so what have *you* got planned to beef up the sound quality? :D
John's CS design isn't about using big DAC chips or
Reeshar wrote:
OK, just to be certain, you aren't trying to use the Pi with both the
wireless *and* fixed network connections in place at the same time, are
you? You should only use one or the other, not both. Use sudo poweroff
to shutdown the Pi, disconnect the fixed network connection from
CommanderROR wrote:
Just a question: since I'm running the Pi+HiFiBerry setup here, I'd like
to try the upsampling you suggest. Can I do that with the provided
Squeezelite build and what should I set the - u parameter to?
Not sure, if your Pi squeezelite build is compiled with -DRESAMPLE and
JackOfAll wrote:
It might help picking the right size, if you could give me an exact
byte count from one of these cards that purports to being 8GB but isn't.
;)
EDIT: This a pointless exercise, in as much as the F20 image is sized
much smaller, and on first boot, the last disk partition
JRatron wrote:
Windows says the capacity of the supposed 8gb SD card is 7,813,988,352
bytes and the image file I believe was 7,889,485,824 bytes
Thank you.
OK, 7,800,000,000 bytes would be good for you. Mr. Floppy what about
your 8GB card. How many bytes are available?
Mr. Floppy wrote:
Edit2: squeezelite 1.5 also down sample the flacs. I try at next yum
update to get all packages new. In the piCore thread I read that the
patch the kernel because the original only handle 48KHz. I dont't know
if here ist a similar problem.
Did you try setting the max
JackOfAll wrote:
Not sure, if your Pi squeezelite build is compiled with -DRESAMPLE and
linked to soxr. Must be, if you have a -u option available. Try -u
vL::2 and -u vM::2.
OK, the included build seems to support upsamling. I set it now, right
from the PiCorePlayer menu and used the
JackOfAll wrote:
Thank you.
OK, 7,800,000,000 bytes would be good for you.
that'd be excellent, thanks :)
slightly off at a tangent, but has the Wifi capability been updated in
any of these later builds?
Specifically interested in the inclusion of support for Wireless
networks other than
I'm not sure if this is a software or hardware question but I'll ask it
here in the first instance...
My Wandboard Quad is being delivered on Monday so I'm doing a bit of
prep to get ready for it.
I intend to use a 2GByte HDD attached to Wandboard but all my music
files are currently on a Win7
bobertuk wrote:
Anyway, the question...
Can Fedora read/write Windows formatted NFS or can Windows read/write
Fedora formatted NFS/Ext3/Ext4?
Which would be the best format to go with?
Thanks
Bob
Hi Bob
By 'NFS' I presume you mean NTFS which is the standard for Windows based
JackOfAll wrote:
Did you try setting the max rate, as I said, to 192000? I'm too busy
right now to go back through this thread, but ISTR someone reported 192k
output from HDMI.
I had good results with 192000 over HDMI but that was some time ago and
I've not tried again recently (can't see
slackhead wrote:
By 'NFS' I presume you mean NTFS which is the standard for Windows based
drives these days? [NFS refers to Network File System which is a
protocol for sharing data across a network]
I do indeed mean NTFS :)
Thanks for the reply - I'll go with NTFS.
1 x Touch -
slackhead wrote:
I had good results with 192000 over HDMI but that was some time ago and
I've not tried again recently (can't see any reason for it not to work
now though).
Thank you! Do you remember if you had to use -r max_rate option to
override rate detection maxing out at 48k?
bobertuk wrote:
I do indeed mean NTFS :)
Thanks for the reply - I'll go with NTFS.
(Replying to myself)
Having said that - Ext2fsd apparently doesn't support Ext4.
But Paragon ExtFS does - and it's free. I may check it out and report
back.
Bob
1 x Touch - LMS 7.8.0
1 x Radio
1 x Boom
JackOfAll wrote:
Thank you! Do you remember if you had to use -r max_rate option to
override rate detection maxing out at 48k?
I seem to remember setting the max rate via the Jivelite audio settings
page, but don't recall if that was actually necessary.
I'll give it a go and report back
slackhead wrote:
I'll give it a go and report back shortly.
Thank you! Much appreciated. Better someone who has been around the
block a few times and actually uses the HDMI output confirming that
something works, and here is how you do it, than me telling someone to
go and try this, go and
JackOfAll wrote:
Bob, I'm not trying to discourage you from having a play, have fun! But
if you just want to fit and forget and everything to just work, plug
the drive into windows machine, format it NTFS and copy your music onto
it. Plug it into Wandboard. There is an example of config in
CommanderROR wrote:
OK, the included build seems to support upsamling. I set it now, right
from the PiCorePlayer menu and used the recommended settings -u hL which
seems to work fine.
Now I just need to check if it's actually doing anything. I can't find
the website where the commands for
JackOfAll wrote:
Better someone who has been around the block a few times
I'll take that as a complement :)
To answer the query:
From the Jivelite interface (on my TV) -
I reset squeezelite settings to all default (ie no max rate set) and
output to hdmi.
Played some 44.1k and 48k files
bobertuk wrote:
Ext2fsd apparently doesn't support Ext4.
Ah yes, although EXT3 tends to be fine for most purposes. I'd only use
EXT4 for system or other critical drives.
But Paragon ExtFS does - and it's free. I may check it out and report
back.
Thanks, wasn't aware of the Paragon
JRatron wrote:
slightly off at a tangent, but has the Wifi capability been updated in
any of these later builds?
Specifically interested in the inclusion of support for Wireless
networks other than just basic WPA security. What's the reason for this
limitation?
Specifically, what do
slackhead wrote:
I'll take that as a complement :)
OK, that's how it was meant! ;)
slackhead wrote:
So it does look like Max Sample Rate needs to be explicitly set.
Thought that was going to be the case.
slackhead wrote:
HOWEVER (there had to be a but) ...
There is always a but! ;)
Try setting the max rate to 192000, via the web-gui squeezelite config
page, Save and Conditionally Restart. I don't use HDMI audio out
myself, so anyone else feel free to jump in.
That resolves the problem...:-)
LMS 7.7.2 - r33908 (Vortexbox 2.0)
W2K8R2 DE (AMD 1060T/4GB/1x1TB RAID1 +
bobertuk wrote:
Having said that - Ext2fsd apparently doesn't support Ext4.
It's been years since I've looked at any of the solutions for
accessing ext file systems on Window$. Might not be the case now, but it
was the last time I looked, that the freeware tools to access from
Window$,
sbp wrote:
It is able to survive power failure, but you will need to save you
settings first.
if you use the piCorePlayer menu, then remember to choose the save
backup option, and then you can make a reboot, or pull the plug .
steen
I thought I saw a backup flash up after the setup
Mr. Floppy wrote:
That resolves the problem...:-)
OK, now on the squeezelite config web page, look in the alsa params box.
If you have anything in there, like 40::16:, delete it and put :::0.
Save and Conditionally Restart.
JackOfAll wrote:
Are you running a recent squeezelite, (rpm -q squeezelite), a 1.5
version?
Yes.
Code:
[root@wandboard ~]# rpm -q squeezelite
squeezelite-1.5-2.fc19.armv7hnl
Just notice my squeezelite log is 132 MB !
Will truncate
JackOfAll wrote:
It's been years since I've looked at any of the solutions for
accessing ext file systems on Window$. Might not be the case now, but it
was the last time I looked, that the freeware tools to access from
Window$, READ ONLY. Still the case?
No. I remember that being the case
slackhead wrote:
Yes.
Code:
[root@wandboard ~]# rpm -q squeezelite
squeezelite-1.5-2.fc19.armv7hnl
Just notice my squeezelite log is 132 MB !
Will truncate the useful bit of that and post it here
Yeah, that's on the
slackhead wrote:
No. I remember that being the case too, but there are now a few that do
write too, and appear to work well (certainly EXT2FSD does).
OK, that's me updated. Been a while since I used Window$. ;)
Here's the last few log lines:-
Code:
[08:09:19.689488] alsa_open:330 unable to set hw params: Cannot allocate
memory
[08:09:25.274766] alsa_open:330 unable to set hw params: Cannot allocate
memory
[11:27:42.182263] faad_decode:414 error: 13 Maximum number of
slackhead wrote:
Looking at the time stamps it doesn't look like there is anything
related to the lock up. Think the other errors are from me swapping USB
devices around earlier.
I'm not even going to start thinking about this. I'm in my own
private hell at the moment, having resized
JackOfAll wrote:
OK, that's me updated. Been a while since I used Window$. ;)
Lucky you :)
Unfortunately i'm a little stuck with it (for now).
slackhead's Profile: http://forums.slimdevices.com/member.php?userid=13963
JackOfAll wrote:
I'm not even going to start thinking about this. I'm in my own
private hell at the moment, having resized the ROOT partition of the F19
R3 image. Put it back onto a card. Boot it, make a few tweaks, update a
package. Done! Try and dd it off the card, to 7zip it and
@sbp
It works as far as I can tell, but I have no way to check the results.
I'd need some way to display the current info concerning playback but
don't know how...can you give me some pointers? I have no idea what it's
upsampling too (of it's doing so at all...)
sbp wrote:
Yep, Ralphy compiled a version with up sampling support for piCorePlayer
, and sox is included as well. However, I haven't tried it, so please
report your findings.
Steen
CommanderROR wrote:
@sbp
It works as far as I can tell, but I have no way to check the results.
I'd
@ Pete
Please check your personal message. - we can discuss any problems here,
that is OK.
Steen
piCorePlayer a small player for the Raspberry Pi (25MB in RAM).
Homepage: https://sites.google.com/site/picoreplayer/home and
discussion:
Good luck with the bad sector hell...
JackOfAll wrote:
Specifically, what do you want support for. WPA/WPA2 is kind of where it
is at.
WEP Insecure. Forget it! LOL.
Enterprise encryption
What actually is it, you would like to see supported?
Apologies. Didn't realise WPA2 was
JRatron wrote:
Any ideas?
Yes, ssh into the WB (user: fedora, pass: fedora) and have a look at
logs. Specifically
Code:
sudo less /var/log/wpa_supplicant.log
sudo less /var/log/messages
See anything suspicious there? Should see
Hi, been following this project for a while and decided to buy a
wandboard quad in November. I downloaded and installed F19 without too
much trouble and got it up and working. I have a Audio-gd NFB-2.1 usb
dac and did some initial testing. The spdif output played all
resolutions 44.1, 88.2 and 96
mherger wrote:
Triode - thanks for the scrolling fix!
Here's a suggested diff with minor tweaks to the grid skin. Because size
matters :D.
- Use larger font for track information.
- Use larger font for progress information
- Use alternative set of assets for the progress
was actually present and can see a
version with today's date in the filename:
/var/log/wpa_supplicant.log-20140117 with lots of
Code:
wlan0: Failed to initiate AP scan
wlan0: Failed to initiate AP scan
Does that help?
Maybe a nice F19 R3 image
tobyjug wrote:
Hi, been following this project for a while and decided to buy a
wandboard quad in November. I downloaded and installed F19 without too
much trouble and got it up and working. I have a Audio-gd NFB-2.1 usb
dac and did some initial testing. The spdif output played all
That was rather like the rush, when the doors open at the Harrods sale!
LOL. Links sent out to everyone who asked for them. Please don't post
them publicly for the moment. Any issues, do post back here rather than
PM me.
JRatron wrote:
Code:
Jan 17 20:20:56 wandboard wpa_supplicant[281]: ioctl[SIOCSIWSCAN]:
Resource temporarily unavailable
Don't much like the look of that and can't remember having seen it
before. Have a go with the F19-R3 image. Still a
Seems you may be aware of issues with TE8802 USB under Linux? Did anyone
ever report it working correctly with Touch EDO kernel?
JackOfAll's Profile: http://forums.slimdevices.com/member.php?userid=3069
View this thread:
OK, got something now. Running a 44.1Khz FLAC I get 44100 (so not
upsampled, right?) as value when I enter cat
/proc/asound/card1/pcm0p/sub0/hw_params
CommanderROR's Profile:
57 matches
Mail list logo
