24d5f0a4150f09a37884240f8926d2 (ba43047bec)
See GitHub Issue:
https://github.com/Hexxeh/rpi-firmware/issues/67
ba43047bec - With Bump to 3.12.35 My Pi will not boot
with HiFiBerry installed. I updated based on a document
they have suggesting that this be done prior to
installation. It was initializing fine prior to this
update, now the system freezes with a multicolored
screen (red on upper left, yellow upper right, blue
lower left and green lower right). If I remove the
HiFiBerry, it boots fine. I had a similar problem using
the HiFiberry with raspbian.
By poking around without the DAC+ installed I was able to
finally get the version with the rpi-update to boot with
the DAC+ attached. Honwestly I am not sure which thing
that I did allowed the R-Pi to boot, but anyway it is now
running with the DAC+ attached and the rpi-update installed.
Is there a way to roll back the rpi-update to a previous
version?
Thanks in advance for any help that You may have
to offer.
......>
In the mean time I have set up my modules file as
follows:
######################################################
#
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules
# that should be loaded at boot time, one per line.
# Lines beginning with "#" are ignored.
#
# Parameters can be specified after the module name
#
## HiFiBerry DAC,DAC+,Digi and Digi+
#
snd_soc_bcm2708
bcm2708_dmaengine
snd_soc_pcm5102a
snd_soc_hifiberry_dac
snd_soc_hifiberry_dacplus
snd_soc_hifiberry_digi
#
#
####################################################
#-eof-
I notice when it starts up, dacplus and digi registrations are
failing. I assume this tells uds that the kernal; I have from
rpi-udpate does not contain support for these?
aplay -l returns:
card 0: sndrpihifiberry [snd_rpi_hifiberry_dac], device 0: HifiBerry DAC HiFi pcm5102a-hifi-0 []
Subdevices: 1/1
Subdevice #0: subdevice #0
So the kernal is registering that device.
uname -a yeilds:
Linux RedLightning 3.12.28+ #709 PREEMPT Mon Sep 8 15:28:00 BST 2014 armv6l GNU/Linux
I am trying to get a version of mpd (with a UpNp front end)
to work with the HiFiberry. I run a Wifi connected radio music
station for my appartment building that uses an analog stereo
intput. I want to replace a handful of ipod "Shuffles" with
a wWiFi connection to a music server on my Raspberry Pi.
I would simply set mpd to play from a music directory on the
SD card (or an attached seagate backup USB drive using
downloadable playlists, either consuming the Downloladed music
(SD solution) or the playlists (the ultimate 1TB backup usb
drive contains the entire music library)
With my application in mind, I am a little concerned. I would
very much like to use a fairly vanilla version of raspian and
firmware so that I could continue to use more or less off the
shelf/stable releases (is there such a thing?).
Anyway, The only sound I have been able to get out of the
Dac+ so far is from your test software. Please help me to
configure a working system.
Regards,
73
-Grace
NNNN
z
Date
Votes
40 comments
-
Grace Thomson Note to simplify my problem:
I am trying to get Raspbian with mpd to use the Dac+
Is This possible?
If so, How?
Thanks/Regards!
73
-Grace
NNNN
z -
HiFiBerry team Hi Grace,
The HiFiBerry boards work well with plain Raspbian. We haven't tested the latest kernel version yet, but I would not expect that this one has a problem.
First you need to load only the DAC+ module, not the Digi and DAC, if you're using the DAC+. Remove the other modules firs.
Second: Have you disabled blacklisting of the I2C modules?
Do you have any hardware connected to the Raspberry Pi except the DAC+?
Best regards
Daniel -
Grace Thomson Okay,
I Downloaded the latest Raspbian image from www.raspberrypi.org
(2014-12-24-wheezy-raspbian.img). I did my setup as follows:
using raspi-config I set:
memory for system 64
overclock to medium
enable ssh
hostname
timezone
I logged in and set up WIFI
I did rpi-update
I edited the blacklist and the modules file
in the blacklist file there were a few lines that
I needed to edit out, now the blacklist file is empty.
the modules file:
######################################################
#
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules
# that should be loaded at boot time, one per line.
# Lines beginning with "#" are ignored.
#
# Parameters can be specified after the module name
#
### HiFiBerry DAC,DAC+,Digi and Digi+ ###
#
snd_soc_bcm2708
bcm2708_dmaengine
snd_soc_hifiberry_dacplus
#
#
######################################################
Here is the result of uname -a:
Linux RedLightning 3.12.35+ #730 PREEMPT Fri Dec 19 18:31:24 GMT 2014 armv6l GNU /Linux
In this configuration the R-Pi will not boot with the DAC+ attached.
I noticed that during boot, the following lines are displayed:
(without the DAC+ attached)
[info] loading kernal module snd_soc_bcm2708
FATAL: Module sbd_soc_bcm2708 not found.
[info] loading kernal module bcm2708_dmaengine.
[ 13.746892] snd-rpi-hifiberry-dacplus snd-rpi-hifiberry-dacplus.0: ASoC: CODEC pcm512x.1-004d not registered
[ 13.765770] snd-rpi-hifiberry-dacplus snd-rpi-hifiberry-dacplus.0: snd_soc_register_card() failed: -517
[ 13.701402] platform snd-rpi-hifiberry-dacplus.0: Driver snd-rpi-hifiberry-dacplus requests probe deferral
[ok] Activating and nd swap...done.
Can you tell me what to check to see why the R-Pi will not boot
with the DAC+ attached?
Thanks Again!
73
-Grace
NNNN -
Grace Thomson Incidently aplay -l returns:
aplay: device_list:252: no soundcards found...
--gbt -
Grace Thomson Here is some information from the booot log (without DAC+
attached):
[ 5.752935] bcm2708_i2c_init_pinmode(1,2)
[ 5.889164] bcm2708_i2c_init_pinmode(1,3)
[ 6.053030] bcm2708_i2c bcm2708_i2c.1: BSC1 Controller at 0x20804000 (irq 79) (baudrate 100000)
[ 6.320232] bcm2708_spi bcm2708_spi.0: master is unqueued, this is deprecated
[ 6.448095] bcm2708_spi bcm2708_spi.0: SPI Controller at 0x20204000 (irq 80)
[ 9.034844] pcm512x 1-004d: Failed to reset device: -5
[ 9.114988] pcm512x: probe of 1-004d failed with error -5
[ 9.162623] pcm512x 1-004c: Failed to reset device: -5
[ 9.185504] pcm512x: probe of 1-004c failed with error -5
[ 9.207854] usbcore: registered new interface driver rtl8192cu
[ 12.238060] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 12.860084] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 13.734725] snd-rpi-hifiberry-dacplus snd-rpi-hifiberry-dacplus.0: ASoC: CODEC pcm512x.1-004d not registered
[ 13.750718] snd-rpi-hifiberry-dacplus snd-rpi-hifiberry-dacplus.0: snd_soc_register_card() failed: -517
[ 13.766064] platform snd-rpi-hifiberry-dacplus.0: Driver snd-rpi-hifiberry-dacplus requests probe deferral
[ 24.177234] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 27.775160] bcm2835-cpufreq: switching to governor ondemand
[ 27.775196] bcm2835-cpufreq: switching to governor ondemand
[ 31.691134] Adding 102396k swap on /var/swap. Priority:-1 extents:2 across:2134012k SSFS
Regards,
-gbt -
HiFiBerry team Hi,
if you used the latest Raspbian the kernel update should not be necessary as it is already using kernel 3.12.35.
However even with the updated kernel system should boot.
I just noticed that dependencies are still not fully correct in the 3.12.x kernel. Therefore you need to load also the PCM512x module:
snd_soc_bcm2708
bcm2708_dmaengine
snd_soc_pcm512x
snd_soc_hifiberry_dacplus
I guess the kernel upgrade messed up some things. I would recommend installing Raspbian again. I just did this and the system boots without problem. Do not use Noobs to install Raspbian as we've seen several problems there.
If the problem still occurs, I recommend to check the power supply. Unstable power supplies might cause problems.
Best regards
Daniel -
Grace Thomson Thank You Daniel.
Well, I took a nightly image and with the exception of the rpi-update I
followed the instructions posted Here:
http://www.hifiberry.com/guides/hifiberry-software-configuration/
I added the snd_soc_pcm512x as you suggested.
after rebooting I attached the DAC+ and when I poewer it up I just get
the multicolored screen that I am growing so accustomed to.
Can I send You my .img file to see if it works on Your P-Pi in Your lab?
If so, how can I post it to You?
Thanks Again!
Regards
73
-Grace
NNNN
z -
Grace Thomson Or could You send me Your working image?
-gbt -
Grace Thomson The uname -a returns:
Linux RedLightning 3.12.35+ #730 PREEMPT Fri Dec 19 18:31:24 GMT 2014 armv6l GNU/Linux
Thanks!
-gbt -
Grace Thomson P.P. Your Question "Do you have any hardware connected to the Raspberry Pi except the DAC+?"
answer is I have the following:
1) EDIMAX Wireless 802.11b/g/n nano USB Adapter
2) Insignia Keyboard USB transciever
3) USB Wireless Logitech Mouse dongle
Thanks Again.
-gbt -
Grace Thomson The Power supply is:
Kootek 5V 2A Universal Micro USB Charger Adapter Power Supply for Raspberry Pi
Raspberry Pi is a Model B+ 512MB.
-gbt -
HiFiBerry team Hi Grace,
i use the standard image from the Raspberry Pi web site. Nothing special.
http://www.raspberrypi.org/downloads/
Did you use this? If yes, you do not need to upgrade the kernel. It comes already with kernel 3.12.35
Best regards
Daniel -
Grace Thomson Thanks Daniel.
Yes, I just tried it again. I used the image that You recommended
just to be sure, but again I get the Rainbow Screen of death when
I attach the DAC+. aplay -l returns:
aplay: device_list:252: no soundcards found...
I am really getting very frustrated here. I must be missing something
that You are doing, but I have followed the instructions carefully.
I have had the DAC+ attached without any problem until I refer to
dacplus in the modules file, then I get the problem. If you want,
I can attach lgo files or look at something else for You. Please
tell me what steps I need to take to determine the cause of this
problem.
Exactly what settings are you using when you first configure Your
R-Pi with raspi-config? I am turning on I2c for example. Is there
any setting that I must enable, or any that could cause the
failure that I am seeing?
Is there any other prerequisite or contraindication that might I
might be missing?
Thanks again.
Regards,
73
-Grace
NNNN
z -
Grace Thomson lgo=log
--gbt -
HiFiBerry team Do I understand this correctly: The Raspberry Pi boots with the DAC+ attached. If you edit /etc/modules and add the modules for the DAC+ it stops booting. Right?
I've never seen something like this before.
Did you try our test image from here?
http://www.hifiberry.com/guides/sd-card-images/
Does this boot?
Best regards
Daniel -
Grace Thomson Yes, the test works fine. I tried to used that Raspbian, but as I said
in my first post, I could not get WIFI and other things to work as
it seemed to be a rather stripped down version. I was able to play
with it for a while, and it seemed fine, just could not get the network
to WIFI connect to my router, so I could not apt-get etc... so I
gave up on that image.
Raspbian boots fine without the card installed. If I don't configure
it for the DAC+ it boots just fine with the DAC+ installed.
That's what I have been trying to get to work, apparently the kernel
crashes during initialization of the card, but its hard to debug since
I can't log into the R-Pi once the problem has occurred.
I just get the "Rainbow screen of death" then the only thing I can
do is turn off the power and remove the DAC+. I have not figured out
how to see if there was any log of the boot attempt as that might
tell us what it was doing when it "fell over".
I'm fairly certain it is not a power problem unless the DAC+ is virtually
shorting out when it wakes up. I did notice though, with your test
image, I saw the rainbow momentarily as it loaded up. As I understand it
what you are seeing when the rainbow appears happens even in a normal boot
for a split second but it is too quick for the video interface to display
it but if the kernel stops during initialization, it just never gets cleared
so you see it on the screen. Actually it is a pixel displayed as a
whole screen. see:
http://elinux.org/R-Pi_Troubleshooting
Is there a way to get a log file of the previous reboot? After my last
reply, I tried diddling several things. I turned back the overclocking and
set a boot delay in the /boot/config.txt by adding "boot_delay=1". I
thought I might try changing the display mode to start desktop on boot
(I have not tried that yet).
I could set up Teamviewer so that you could access my R-Pi via Windows SSH
and you could have a look around if that appeals to You. Otherwise, I
would be happy to look at anything that You think might give us a clue.
I am afraid of what the problem is. I will probably be embarrassed because
it is something so simple.
By the way, I found out something that You and your users may find very
interesting. It is *SO-EASY!* to set up emacs/emms along with mplayer or mpd
alt-get install emacs <--- installs GNU emacs
then
alt-get innstall emms <--- installs emacs Multimedia system
That's so easy!!!
emms is powerful!
Apparently you can interface with many players including mplayer, mpd,
etc. It also has modes for streaming from various sources lastfm,
internet radio, Pandora, .. also allows editing and maintenance of
playlists and music libraries. I don't know how much of the other
multimedia modes might work.....
Anyway, I can't wait to get my HiFiberry working! I want to play with
it!!! I'm going crazy here....
Okay, I will try anything You can think of.
Thanks again
73
-Grace
NNNN
z
-
Grace Thomson innstall=install
-gbt -
HiFiBerry team Hi Grace,
the interesting thing is that initialisation of the drivers for the card is done very late at boot stage. Therefore even with a defective driver the Raspberry Pi should boot first. I start to suppose that the SD card has a problem. Do you have another SD card that you can test?
Best regards
Daniel -
Grace Thomson Hi Daniel,
No, but I have used this one for everything, openelec, rasbmc, etc all of my images seem to work fine.
let me know how I can send You my image file, maybe you can load it up and see how it works op
Your R-Pi?
There is no other way that I can think of to isolate the problem with raspbian except to let you
test it there. Perhaps with your experience You will immediately see the problem with my configuration,
or if it works, then we know it is a problem with my R-Pi or the DAC+
I would have to wait until next week when I get paid to buy another card, and from my experiences
with this one, I don't think that is the problem.
If there is some known working configuration I could load it to further test the DAC+ that way, but
I really want it to work with raspbian.
Regards.
73
-grace
NNNN
z -
Grace Thomson For example, I could upload my image to my google drive, and give you access to that.
-gbt -
Grace Thomson The SD card that I have is a SanDisk Extreme 16gb MicroSDHC.
-gbt -
Grace Thomson Just noticed that the image is 14.8 GB, I don't have tha much space online at google, but I may be able
to put it up on another server if you are willing to download it, I think I can get You FTP access to
it. I need to check to see if I can arrange that much space. I will let you know if You are interested.
-gbt -
Grace Thomson Yes, I can arrange to make it available via ftp from my account at eskimo.com,
but I can't get that done until the PM local time here (about 12 hours from now).
Would that be helpful?
-gbt -
Grace Thomson Could the partition expansion in raspi-config cause some kind of problem. I have been doing that.
I wonder if I could make a smaller image file for you by skipping this step in my setup?
-gbt -
HiFiBerry team Hi,
I haven't seen problems from resizing, but it could be. Try it without resizing the partition. You can do the resizing later.
Best regards
Daniel -
Grace Thomson Okay, with this version of raspbian, I can't get it to boot with the DAC+ attached. Not on the first boot before
raspi-config. I am removing the DAC+ and I will try to add the card after an initial setup....
Okay, with minimal setup, the DAC+ causes the reboot to freeze with the screen of death. So, I need to find an earlier
version of the kernel that will allow me to boot up with the DAC+ attached. This one will not.
You say that yours will boot with the DAC+ attached running this kernel, so maybe it is a power issue after all.
I will see if I have a PC power supply that I can use to test, or power it from my PC USB power..
Back to the drawing board. I really thought I had a good supply though.
Have a nice New Years Eve / Day.
Talk to you after.
Regards
73
-Grace
NNNN
z -
Grace Thomson Daniel,
I hope You had a great New Years Eve!
I went out today and bought a Power Rechargeable Bank Battery Pack intended to recharge cell-phones.
It will supply 5 volts at 2.1 Amps. It has a charge capacity of 37 Wh (10.4 Ah). I charged it fully
for 6.5 hours. When I hooked it up with the DAC+ attached, there was no difference that I could
discern between that and the power supply. In other word, with the DAC+ attached, the vanilla
12-24 Wheezy crashes at start-up and displays the rainbow screen.
So, I am thinking that when I did the rpi-update, the firmware changes that were made then caused
the problem. So how do I get a firmware upgrade or rollback to a working version? What firmware
version is installed in your lab R-Pi? I suspect that if I could duplicate that firmware, and load
the same software that You have been successful with, then I would be able to make this work.
If not, the we are likely looking at a hardware problem. with either the DAC+ or my R-Pi.
I also bought a second microSD. The First card (the one i'm using now is the SanDisk Extreme 16gb.
Sandisk claims that this is the fastest SD card available at 250mb/s. The new card is the SanDisk
Ultra Plus. It was about 1/2 the price, so I checked the specs and the difference seems to be
the claimed speed; the Ultra Plus about 65mb/s from one source I found. Anyway, I wiill try using
the slower SD (the new one) and see if there is any difference.
Anyway, if I still have a problem, one option would be for me to post my image on an SD to You in
the mail for You to look at.
I have been working on this for about 30 hours and I'm getting a bit punchy, so I need to go
horizontal for a few hours so I can get out to the party here at the Space Needle tonight
They have a great show with the music and fireworks here every year and I live only 5 blocks
from there. The weather is nice for it (it should be a clear night, but very cold for
Seattle (-2C).
Regards,
73
-Grace
NNNN
z -
Grace Thomson Daniel, please execute the following command on an R-Pi that is working well for you running raspbian:
sudo /opt/vc/bin/vcgencmd version
it should give You an output like this:
pi@RedLightning ~ $ sudo /opt/vc/bin/vcgencmd version
Dec 19 2014 18:35:53
Copyright (c) 2012 Broadcom
version 5abd572e2ed1811283443387af09377b95501c50 (clean) (release)
I need this information so that I can load a workin firmware version. I suspect that the firmware version
shown above was the upgrade where my R-Pi stop booting with the DAC+ attached. I just downgraded mine to
an earlier version, I will try several versions and see if I can get one that will allow me to attach
the DAC+.
Regards,
73
-Grace
NNNN
z -
Grace Thomson Daniel,
I Did the following:
1) I went retro on my rpi-upgrade as follows:
pi@RedLightning ~ $ sudo /opt/vc/bin/vcgencmd version
Dec 19 2014 18:35:53
Copyright (c) 2012 Broadcom
version 5abd572e2ed1811283443387af09377b95501c50 (clean) (release)
2) I installed An old version of NOOBS to reset everything back I used
NOOBS_v1_3_10.
3) After getting this working I attached the DAC+ and it was successful
(no rainbow of death screen)
4) I installed an older version of Raspbian (raspbian-2014-09-12/) from:
http://downloads.raspberrypi.org/raspbian/images/
This is because the 2014-12-24-wheezy-raspbian causes the RSOD
(rainbow screen of death) to occur.
5) I followed the instructions found here:
http://www.hifiberry.com/guides/hifiberry-software-configuration/
6) I installed emacs and emms (along with mplayer. I will be installing
mpd as well so I will probably need to re-partition my SD card with
raspi-config so I will save the image file from what I have so far first
in case something goes wrong.
Bye for now...
Regards,
73
-Grace
NNNN
z -
Grace Thomson Daniel,
It finally works! I just tested it with:
mpg123 "01 Paint It Black.mp3"
And it is playing well through a pair of iPod shuffle headphones
that I happened to have kicking around.
Also, this is the first time that I noticed the green LED on top of
the DAC+. It was on prior to playing, after finishing the track it
turned off then it turned on again while I was playing it again.
What does the LED indicate exactly?
Anyway the DAC+ seems to be working just fine now. Thank You for
Your patience. Please keep us to date on software versions that
work. It was just trial and error on My part trying to get this
to work.
I would be happy to try newer configurations that You have tested.
Thanks again!
73
-Grace
NNNN
z
Please sign in to leave a comment.