Raspyfi crashes. I mean every time, without an exception.
My setup:
Raspberry Pi Model B 512MB (no rev 2, ordered march 2013)
SD card: Transcend – TS8GSDHC10 – 8 GB – Class 10 – SDHC, http://elinux.org/RPi_SD_cards says: OK
USB powered DAC schiit modi http://schiit.com/products/modi
Power Supply Adapter DC 5V 1500mA http://thepihut.com/products/e…..spberry-pi
Controlled by webui http://raspyfi/
I have formatted the SD card with SDFormatter V4.0 https://www.sdcard.org/downloads/formatter_4/ on a windows 7 computer
Then the Raspyfi software is copied on the SD card with Win32 Disk Imager http://sourceforge.net/project…..iskimager/
Raspyfi 1.0: http://sourceforge.net/project…..urce=files (NetCologne mirror)
I have also tried other hardware:
another Raspberry pi, also a model B, no rev 2
4GB Sandisk SD Card http://thepihut.com/products/x…..ed-sd-card
Power Supply Adapter for the samsung galaxy s3 (among others)
When done copying I start up and just select webradio JazzGrove.pls and start to listen.
After a while Raspyfi crashes. Sometimes a few minutes sometime a few hours. But it crashes.
After a crash there is no contact possible with the device, not via ssh, not via webui or otherwise.
Why?
Why does Raspyfi crash?
Best regards,
H
Ok, I have created a raspbian mpd server, just to check if that would be just as unstable as Raspyfi 1.0.
If so, and Raspyfi being based on Raspbian, then that would mean it's not to blame Raspyfi for those instability issues.
(not exactly bulletprove evidence, it could still be a hardware problem, even a single hardware problem or some local thingy that only effects my setup)
So I have installed 2013-09-25-wheezy-raspbian on the exact same hardware setup, the same wallsockets and all.
sudo -s
raspi-config #expand over sd
apt-get update
apt-get upgrade
reboot
apt-get install mpd mpc ncmpcpp
apt-get install smbclient
apt-get install mc #filemanager, for your convience: make folders and and file permissions etc
mount -t cifs -o user=yoursmbusername,password=yoursmbpassword //192.168.x.xxx/yourshare /localfolder
nano /etc/rc.local #put that mount line thing in here, just above exit 0
nano /etc/mpd.conf
#change the lines:
music_directory "/change/this/to/where/your/music/will/be"
playlist_directory "/change/this/to/where/your/playlists/will/be"
bind_to_address "any"
dmesg #look for a 'cm109'
lsusb #look for a 'C-Media…'
nano /etc/modprobe.d/alsa-base.conf
#look for the line with: 'options snd-usb-audio' change it in:
options snd-usb-audio index=0 #use usb DAC first
#test if it produces sound:
speaker-test -c2 -D hw:0,0
service mpd restart
# look at http://www.ipodder.org/radio select a radiostation and play, there you see the ip stream listed
mpc add http://199.180.72.2:8015/ #thejazzgroove
or
ncmpcpp #select an audiofile and play
Ok. I'm playing this for over 24 hours nonstop, and there is not one single systemcrash or holt. None.
sources:
http://www.jpstacey.info/blog/…..sic-server
http://raspberrypihelp.net/tut…..spberry-pi
http://learn.adafruit.com/usb-…..structions
Well now, don't get me wrong, I really am fond of Raspyfi.
The concept is really appealing (turn a Raspberry Pi in an audiophile-quality music player), and the webui looks really slick.
But those instability issues are just to much.
Again, please tell me what can I do to try to pinpoint where those problems are originated?
Best regards,
H
21:22
That really seems weird to me… But sure there will be a solution. Please report:
-Do you have an Hard Drive attached?
-Is it connected via Ethernet or Wi-fi?
-Did you try other webradios? Is the behaviour similar?
10:29
I had am simular issue too. After crashing no connection to raspyfi was possible any more.
In my case raspyfi and my router-dns-server work together with fixed ip only. Otherwise pi connects once to the router. After network-drop-out (in my case a powerline issue) pi tries to reconnect to the router (router log tells this) but failes.
So the solution for reconneting was to switch the network settings to fixed ip after the first start.
This was no solution for the network drop-outs but for reconnecting at least.
May be this helps a bit,
thomas
@mikelangeloz
There is no harddrive attached and it is connected via ethernet.
Yes I have tried other webradios and just ordinary mp3s (via samba) as well, but with the same result, the crashes still occur.
I have a more complex setup in mind, but kept getting crashes, so I have reduced it to just installing Raspyfi then play a random webradio (I choose jazzgroove), start playing and see what happens. Only if thats stable then add something else in the mix.
I looked in some log files, but did not see anything deviant. Or did not know where/what to look for.
@thomas
Interesting. I will try your suggestion and see if that makes any difference and report back in about 24h (or earlier when it seems fit)
Now I have set this on Raspyfi =>Network Configuration and on the routerside I have set the mac adress on that static lease.
Thanks, I will report back tomorrow,
Best regards,
H
No.
I have set a static ip number, on the Network Configuration and on the routerside, but the crashes keep coming at the same pace.
Would have been nice if that would have solved it. But no.
So, now I have tried multiple hardware setups (power supplies, SD-cards, network cables), but still crashes with every setup.
Then I have tried a Raspbian install with mpd installed, and this works without any hiccup or crashes. (I know, this test is n=1, but the best I can do for now)
This leads me to believe this is a Raspyfi software problem. Something specific in Raspyfi that causes these crashes.
But what would it be that causes this?
Ok, I have some time on my hands, but where do I have to look?
I don't mind getting my hands dirty, but I have no clue where to start?
Best regards,
H
10:26
I have exactly same problem, I can not enjoy music over 10 minutes (sometimes it goes 30 mins..)
Is this S/W problem or my H/W?
The error message is ;
ERROR :handle_hc_chhltd_intr_dma:2537: handle_hc_chhltd_intr_dma: Channel 2, DMA Mode -- ChHltd set , but reason for halting is unknown, hcint 0x00000002, intsts 0x04600021
10:28
I have exactly same problem, I can not enjoy music over 10 minutes (sometimes it goes 30 mins..)
Is this S/W problem or my H/W?
The error message is ;
ERROR :handle_hc_chhltd_intr_dma:2537: handle_hc_chhltd_intr_dma: Channel 2, DMA Mode -- ChHltd set , but reason for halting is unknown, hcint 0x00000002, intsts 0x04600021
2mvent said
No.
I have set a static ip number, on the Network Configuration and on the routerside, but the crashes keep coming at the same pace.
Would have been nice if that would have solved it. But no.
So, now I have tried multiple hardware setups (power supplies, SD-cards, network cables), but still crashes with every setup.
Then I have tried a Raspbian install with mpd installed, and this works without any hiccup or crashes. (I know, this test is n=1, but the best I can do for now)
This leads me to believe this is a Raspyfi software problem. Something specific in Raspyfi that causes these crashes.
But what would it be that causes this?
Ok, I have some time on my hands, but where do I have to look?
I don't mind getting my hands dirty, but I have no clue where to start?
Best regards,
H
10:31
I have exactly same problem, I can not enjoy music over 10 minutes (sometimes it goes 30 mins..)
Is this S/W problem or my H/W?
The error message is ;
ERROR :handle_hc_chhltd_intr_dma:2537: handle_hc_chhltd_intr_dma: Channel 2, DMA Mode -- ChHltd set , but reason for halting is unknown, hcint 0x00000002, intsts 0x04600021
Hi Jack,
If you have exactly the same problem like mine, then it is a software problem.
Your not describing your exact setup so I can not tell. Do you use a wireless connection?
Where did you locate this error message?
Jack, you put me on to something.
If I connect a display to the Raspberry Pi, then wait till this crash occurs and then for a few minutes there is a error message before the screen goes blank:
[ 1322.125193] ERROR: :handle_hc_chhltd_intr_dma:2537: handle_hc_chhltd_intr_dma: Channel 3, DMA Mode -- ChHltd set , but reason for halting is unknown, hcint 0x00000002, intsts 0x04600021
So, that's similar to yours Jack. (different channel and the blabla at the and is somewhat different)
I got myself a cup of coffee after that.
Finally, there is a error message! For a brief moment that is. I missed that error all those times before.
Ok, a litlle help from big brother google:
http://www.raspberrypi.org/phpBB3/viewtopic.php?uid=10221&f=28&t=49223&start=0
There they mention to revert to a June firmware version:
sudo rpi-update 5ea0f44b673eaa52c578fcd6480495f19cd53d97
It's a sort of irq bladibla problem and so forth I am not interested in.
By the way I have also done a little adjustment of the /etc/modprobe.d/alsa-base.conf, added a single line:
options snd-usb-audio nrpacks=1
to end those bucket-loads of error messages "delay: estimated 0, actual 177" in dmesg
Source: http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=15204
So I leave this playing for 24h and we will see some results hopefully
Best regards,
H
FYI I found a issue that I though originally was a unrecoverable crash until I found it was actually music retained with in the last Playlist (which doesn't clear on reboot) the files it was trying to read were not available either because I updated the file location or changed the music on my USB drive to different songs or I wan't connected to my NAS becuase I took it on the road with me.
Any file it was trying to play/load that no longer existed hung the player.
No MPDroid or Web – interface.
What I did was connected to it via SSH from putty.
and started running a few MPC scripts
mpc help for a list of avail commands.
mpc clear
mpc stop
mpc
I found that it would time out so I ran
sudo /etc/init.d/mpd restart
then tried the scripts again.
Some how I got through and was able to clear the playlist which had the files that were no longer available.
If someone out there has a step by step on adding a mpc clear to the boot up so it is cleared every time I would like to implement that.
Yes!
I am playing music for 17h now and no crash or other malfunction.
The error:
[ 1322.125193] ERROR: :handle_hc_chhltd_intr_dma:2537: handle_hc_chhltd_intr_dma: Channel 3, DMA Mode -- ChHltd set , but reason for halting is unknown, hcint 0x00000002, intsts 0x04600021
Does not occur when:
sudo rpi-update 5ea0f44b673eaa52c578fcd6480495f19cd53d97
Is done. ( it does need two other packages installed, but it conviently mentions that)
Jack, can you confirm?
This whole event does however makes clear that how Raspyfi is setup at this time is somewhat prone to any bugs in Rasbian.
If there is any, it will freeze together with Raspyfi, there is no upgrade possible in Raspyfi 1.0
I would suggest trying to build separate repositories for the adjusted software?
A bit like how Elementary OS has done things. http://elementaryos.org/
But.that would also mean huge workloads for the developers to build this.
Thanks everyone for bearing with me.
Best regards,
H
Dear 2mvent,
First of all, Thank you for your help and effort !!!
I tried the update which you suggest BUT I could not install git-core.
When I tried "sudo apt-get install git-core" But I faced error what it said "no candidate…"
=========================================================================
2013-10-12 08:16:08 (4.16 MB/s) – `/usr/bin/rpi-update.tmp' saved [6782/6782]
*** Relaunching after update
*** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS
!!! This tool requires you have Git installed, please install it first
In Debian, try: sudo apt-get install git-core
In Arch, try: pacman -S git
[email protected]:~$
[email protected]:~$ sudo apt-get install git-core
Reading package lists… Done
Building dependency tree
Reading state information… Done
Package git-core is a virtual package provided by:
git 1:1.7.10.4-1+wheezy1+rpi2 [Not candidate version]
E: Package 'git-core' has no installation candidate
=======================================================================================
What a sad…
Is anybody can help me to install git-core and previous kernel…
Best Regards,
Jack
ps, Dear 2Mvent can you chat with me? (google hangout, [email protected]) OR Can you share your "working" image file ???
Hi, Jack,
First:
sudo apt-get update
(don't upgrade)
After that you can install aditional programs.
Please inform us if you have simular results.
I'm sorry, I am not able to chat.
Best regards,
H
Oh I forgot "sudo apt-get update" before install git-core
Now it working to install, let feedback to you after replace firmware
Thanks !!
Dear 2mvent,
I completed all update, install, replace firmware and now begin to test.
So far everything is fine (no errors) I hope it can work without problem and with stable.
Anyway Many thanks to you and let's wait better raspyfi (next version) This is really great job they did !!
Regards,
Jack
Most Users Ever Online: 200
Currently Online:
5 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Gyp: 82
yoghurtlidlicker: 37
PaulM: 36
icai: 35
Derek: 29
Karsten: 27
tc-fi: 22
Ronaldo: 21
ENSen: 21
chriz: 20
Member Stats:
Guest Posters: 3619
Members: 569
Moderators: 0
Admins: 1
Forum Stats:
Groups: 4
Forums: 10
Topics: 469
Posts: 13163
Newest Members: polo2016, dongdong8, wlpwlp, Sager, ninestab123, lmx66, lmx, jlgg, chenyan, guoyanying
Administrators: admin (401)