Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Mon 01 Sep 2014, 17:46
All times are UTC - 4
 Forum index » Advanced Topics » Puppy Derivatives
mpdPup - Simplified MPD Music Server/Jukebox - v0.9.3
Moderators: Flash, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 6 of 35 [523 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8, ..., 33, 34, 35 Next
Author Message
jonnyc

Joined: 16 Jan 2012
Posts: 6

PostPosted: Mon 03 Dec 2012, 19:16    Post subject:  Unetbootin and dd  

hi there,

a stucked a little bit with my cuty little pcs. they all hava ide flash drives with 256 mb.

i downloaded mpdpup 0.9.3 and tried to copy it with unetbootin using ubuntu 12.04. after creating a fat32 partition with gparted, i had no chance to install mpdpup on it. there was simply no option within unetbootin. so i tried the same with windows xp on this machine. also no option for this internal drive.
(i was able to mount it, and also windows showed me the drive, but unetbootin wasn't able).

next try was using dd. first i wrecked my partition table on this drive by using:

dd if=/home/user/downloads/mpdpup-0.9.3.iso of=/dev/sdb

after this, the drive couldn't be mounted at all. so i created a new partition table, also with gparted and tried to write directly to the fat32 partition with:

dd if=/home/user/downloads/mpdpup-0.9.3.iso of=/dev/sdb1

this time it worked better. the device is mountable and it also shows its data. but yet i'm not able to boor from this drive.

any further ideas? thank a lot.
Back to top
View user's profile Send private message 
ldolse

Joined: 23 Oct 2009
Posts: 366

PostPosted: Mon 03 Dec 2012, 20:10    Post subject: Re: Unetbootin and dd  

Hi jonnyc, Unetbootin doesn't work with internal drives, it only works with USB drives.

Just install to a USB stick as per the instructions in the first post. Once you've booted off the USB stick you can use the Puppy Linux installers to install to the internal drive. I've written some other posts on how to use the installers, not sure exactly where they are as I write this, either earlier in this thread or in the 0.9.2 thread.
Back to top
View user's profile Send private message 
ldolse

Joined: 23 Oct 2009
Posts: 366

PostPosted: Mon 03 Dec 2012, 21:51    Post subject:  

@jrling, 176/192Khz doesn't work automatically with some sound cards, it's some low level ALSA issue that I haven't gotten to the bottom of. Simplest fix in most cases is to unplug the sound device and re-plug it in - this only needs to be done once each time you boot the system. For whatever reason re-initializing the hardware that way resolves it, at least on my hardware. Other users have reported no problems whatsoever with these higher sample rates.
Back to top
View user's profile Send private message 
luisb

Joined: 30 Sep 2012
Posts: 25

PostPosted: Tue 04 Dec 2012, 07:39    Post subject:  

Hi Idolse and waveio users. In version 92 the unmute file of the previous thread works with my waveio. In version 93 is unmuted at start. Even when i restart mpd, remains that way. Don't know if it's the configuration of waveio i have or something else. I use independent power supply (not the usb supply), cutted the 5 v wire of the cable from pc to waveio pin usb input and non isolated I2S to DAC with all U.fl grounds connected. Firmware not updated. Any thoughts?
Regards
Back to top
View user's profile Send private message 
jrling

Joined: 27 Jun 2012
Posts: 47

PostPosted: Tue 04 Dec 2012, 07:58    Post subject:
Subject description: WaveIO SOX 176/192 Problem
 

Idolese

Thanks for the clarification.

I am using the dreaded WaveIO USB/SPDIF board which has caused you so much heartache with Unmute.

Have any other WaveIO users found the same issue as I have?

I don't keep my system on all the time and so having to do what you suggest every time I boot up would be irritating.I will post up the issue on the DIYAudio WaveIO thread to see if there is any fix.
Back to top
View user's profile Send private message 
bonalux

Joined: 20 Jun 2012
Posts: 22

PostPosted: Tue 04 Dec 2012, 09:51    Post subject:  

Almost all WaveIo users have the same problem as you (included me), but is easily solved with the procedure previously posted by Idolse

Quote:

Type the followingat the command line:

Code:

nano /etc/init.d/unmute


Then paste the following into the editor:

Code:

#!/bin/sh

unmute_audio(){
   CARDS=`aplay -l | grep card | cut -f 1 -d ':' | uniq | cut -f 2 -d ' '`
   for card in $CARDS
   do
      CONTROLS=`amixer -c $card scontrols | cut -f 2 -d "'"`
      for control in $CONTROLS
      do
         amixer -c $card sset $control unmute >/dev/null 2>/dev/null
         amixer -c $card sset $control 100% >/dev/null 2>/dev/null
      done
   done

}

unmute_audio

press ctrl-x to exit, then y to save the script.

Lastly type this command:
Code:

chmod +x /etc/init.d/unmute


Then run "alsamixer", unmute the card, exit and type:

Code:

alsactl -f /etc/asound.state store


before using 'save2flash' or a full reboot.


Reboot to save the config, and give it a good 5-10 minutes or so before yanking any plugs to give it time to do whatever it's trying to do and make sure the changes stick.

After that the cards should be unmuted as part of the boot process no matter what state they decided to boot up in on their own.


Most important part is, as Idolse said, give it at least 10 minutes (better if you go away for at least half an hour to be sure) before restarting again and see if it works. For me it worked and there is no more the mute problem.

As all WaveIo user, another problem with it is that if you restart the system without turning off the WaveIo then it is not recognised, have to unpower the card and power on it again, but it's a card problem not mpdpup one.

Idolse: just that i'm writing, as Jrling say, with the latest release there is a problem with usbnrpacks that is stuck at 8, regardless of the choice in the wizard, checked it now at the cli with the cat command, maybe a bug to be fixed in the next release.
Back to top
View user's profile Send private message 
jonnyc

Joined: 16 Jan 2012
Posts: 6

PostPosted: Tue 04 Dec 2012, 18:19    Post subject:  Installation on a Harddrive / IDE Flash Device  

Hi Idolse, thanks for your reply. I already worked with an USB-drive and Unetbootin. And there was also no problem to get mpdpup working with this very method.

Next goal for me is to install mpdpup to a fake harddrive / IDE Flash device, because there is no rear USB Port on this cute little device and I wanted to have it a little more sexier. And also I have 4 of this IDE Flash Devices, which should work well for this distribution.

Today I tried to install syslinux on the drive and afterwards I copied all files from the loop mounted iso file. It still didn't work.

Next will be an slitaz installation and afterwards I will copy all files from the mounted iso image...
Back to top
View user's profile Send private message 
ldolse

Joined: 23 Oct 2009
Posts: 366

PostPosted: Wed 05 Dec 2012, 01:41    Post subject:  

Hi JohnnyC, what I meant was once you booted off the Unetbootin stick you can then use that live Puppy Linux/mpdPup instance to install to the SSD drive. I added instructions to the second post of this thread. Other users have gotten it working following these basic instructions, but I'm not sure if they're exactly correct. If you go with something like a CF-SATA adapter as you mentioned it would bypass all of these extra steps.

@bonalux, thanks for highglighting that post - in 0.9.3a that script is a included in the iso. I did find there is a bug with it, which is apparently why it doesn't work for some WaveIO users. It needs to be updated to handle spaces in the sound device name. Here is the latest code:
Code:
#!/bin/sh

unmute_audio(){
   SAVEIFS=$IFS
   IFS=$(echo -en "\n\b")
   CARDS=`aplay -l | grep card | cut -f 1 -d ':' | uniq | cut -f 2 -d ' '`
   for card in $CARDS
   do
      CONTROLS=`amixer -c $card scontrols | cut -f 2 -d "'"`
      for control in $CONTROLS
      do
         amixer -c $card sset "$control" unmute &>/dev/null
         amixer -c $card sset "$control" 100% &>/dev/null
      done
   done
   IFS=$SAVEIFS
}

unmute_audio
alsactl -f /etc/asound.state store
exit 0


This will be included in the next iso, which I'm working on getting out soon. The nrpacks problem you noticed will be fixed too - not sure how that one slipped by me.
Back to top
View user's profile Send private message 
jonnyc

Joined: 16 Jan 2012
Posts: 6

PostPosted: Wed 05 Dec 2012, 17:53    Post subject:  thank you  

Hi Idolse and thank you very much for this hint. I just trying to get it on.

I'm so glad, it works! I waited half a year for this solution!!!

Next step is to try this installation procedure with mpdpup 0.9.1.
Since 0.9.2 I have problems with ACPI. After pressing the power button, nothing happens. I hoped that the problem doesn't appear in 0.9.3 anymore, but there is still the same thing... I will try to figure it out.
Back to top
View user's profile Send private message 
ldolse

Joined: 23 Oct 2009
Posts: 366

PostPosted: Wed 05 Dec 2012, 20:38    Post subject: Re: thank you  

jonnyc wrote:
Hi Idolse and thank you very much for this hint. I just trying to get it on.

I'm so glad, it works! I waited half a year for this solution!!!

Next step is to try this installation procedure with mpdpup 0.9.1.
Since 0.9.2 I have problems with ACPI. After pressing the power button, nothing happens. I hoped that the problem doesn't appear in 0.9.3 anymore, but there is still the same thing... I will try to figure it out.
Glad to hear the istructions worked.

Regarding the power button, I wish I knew a good fix there myself - I think the reason 0.9.1 works well in that respect is because it's an old kernel with basically no ACPI support. 0.9.2 and 0.9.3 have proper kernel level support, but that means in order to get the power button to work with a single click you need an extra daemon to watch the power button for clicks. One of my goals is to keep extra processes/daemons to a minimum so I decided to live wtih the long press.

Maybe the trick would be to removing the ACPI kernel modules, will need to give that a try.
Back to top
View user's profile Send private message 
Dynobot

Joined: 05 Dec 2012
Posts: 44

PostPosted: Wed 05 Dec 2012, 20:54    Post subject:  

Just wanted to say great job with this...

Some suggestions you might consider

-cpufreq - change from ondemand to performance
-somehow be able to unbind devices from sharing the same interrupt
-increasing the priority of the audio threads
-if at all possible give MPD a CPU core to itself via affinity
-enable mmap in MPD
Back to top
View user's profile Send private message 
ldolse

Joined: 23 Oct 2009
Posts: 366

PostPosted: Wed 05 Dec 2012, 21:20    Post subject:  

Dynobot wrote:
Just wanted to say great job with this...

Some suggestions you might consider

-cpufreq - change from ondemand to performance
-somehow be able to unbind devices from sharing the same interrupt
-increasing the priority of the audio threads
-if at all possible give MPD a CPU core to itself via affinity
-enable mmap in MPD
Hi Dynobot, I saw you'd done some testing on audioasylum, I was wondering what tweaks you were referring to, so that helps. Was happy to see you had a good experience with it.
  • cpufreq - hadn't heard of that tweak and looks quite simple, will do
  • audio thread priority - my first attempt at this used nice and unfortunately it caused mpd to fail to start on some hardware. I'm looking to do this in the future with chrt, but need to spend some time trying to figure out the best way to build a minimal util-linux package - it's a bit of a clusterf#$!@ to try to build just one piece of it.
  • I'd actually just read about mmap about a week ago, this is on the list to get done soon
  • single core dedicated to MPD is interesting, will explore options there
  • IRQ sharing is the only one that I think will be difficult to tackle, as the behavior varies a lot from platform to platform.
Back to top
View user's profile Send private message 
Dynobot

Joined: 05 Dec 2012
Posts: 44

PostPosted: Wed 05 Dec 2012, 22:24    Post subject:  

ldolse wrote:
Dynobot wrote:
Just wanted to say great job with this...

Some suggestions you might consider

-cpufreq - change from ondemand to performance
-somehow be able to unbind devices from sharing the same interrupt
-increasing the priority of the audio threads
-if at all possible give MPD a CPU core to itself via affinity
-enable mmap in MPD
Hi Dynobot, I saw you'd done some testing on audioasylum, I was wondering what tweaks you were referring to, so that helps. Was happy to see you had a good experience with it.
  • cpufreq - hadn't heard of that tweak and looks quite simple, will do
  • audio thread priority - my first attempt at this used nice and unfortunately it caused mpd to fail to start on some hardware. I'm looking to do this in the future with chrt, but need to spend some time trying to figure out the best way to build a minimal util-linux package - it's a bit of a clusterf#$!@ to try to build just one piece of it.
  • I'd actually just read about mmap about a week ago, this is on the list to get done soon
  • single core dedicated to MPD is interesting, will explore options there
  • IRQ sharing is the only one that I think will be difficult to tackle, as the behavior varies a lot from platform to platform.


Hi

I increased the thread priorites by adding a script in the my-applications/bin directory
#!/bin/bash
renice -10 3
renice -10 9
renice -10 13
renice -10 16

I tried higher values but settled on -10, -19 being the highest.
~~~~~~~~~~~~~~~

In etc/mpd.conf I added this after the alsa_period line to enable memory mapping

mmap_emulation "true"
~~~~~~~~~~~~~~~~~~~

It looks like the start_cpu_freq file located in /etc/init.d directory can be modified to use performance instead of ondemand. I did not try this yet.

~~~~~~~~~~~~~~~~

These are a few things I use for MPD in a normal setup. Unbinding is great but its really task intensive. Pretty much it just frees up the interrupts to handle a single device instead of having one interrupt having multiple devices on it. Normally I would use a tool called tree to find and then unbind USB ports [its kinda over the top] small reward.

I was not able to dedicate a single core to MPD like I normally do...this give pretty good results. Normally I use taskset -c -p 1 $(pidof mpd) but puppy does not recognize taskset.
Back to top
View user's profile Send private message 
Dynobot

Joined: 05 Dec 2012
Posts: 44

PostPosted: Wed 05 Dec 2012, 22:56    Post subject:  

Oh one other thing

Swappiness

swappiness can have a value of between 0 and 100

swappiness=0 tells the kernel to avoid swapping processes out of physical memory for as long as possible
swappiness=100 tells the kernel to aggressively swap processes out of physical memory and move them to swap cache

The default setting in Linux is swappiness=60. Reducing the default value of swappiness will probably improve overall performance for a typical desktop installation. A value of swappiness=10 is recommended, but feel free to experiment.

Copied and pasted from: http://linuxpoison.blogspot.com/2010/05/performance-tuning-linux-kernel-with.html#ixzz2EEjzD9Ht

EDIT: I am not sure swappiness will do any good. But just an idea.
Back to top
View user's profile Send private message 
jonnyc

Joined: 16 Jan 2012
Posts: 6

PostPosted: Thu 06 Dec 2012, 06:29    Post subject: Re: thank you  

ldolse wrote:

Regarding the power button, I wish I knew a good fix there myself - I think the reason 0.9.1 works well in that respect is because it's an old kernel with basically no ACPI support. 0.9.2 and 0.9.3 have proper kernel level support, but that means in order to get the power button to work with a single click you need an extra daemon to watch the power button for clicks. One of my goals is to keep extra processes/daemons to a minimum so I decided to live wtih the long press.


Pressing the power botton for 3 sec. simply forces powerdown. After this, next time mpdpup starts it runs a fsck (it seems so).
Is there no risk to damage the ext2 partition, or is it only held in RAM?

regards
JonnyC

BTW: How about adding mpdpup to distrowatch? Rolling Eyes
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 6 of 35 [523 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7, 8, ..., 33, 34, 35 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Puppy Derivatives
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1146s ][ Queries: 13 (0.0127s) ][ GZIP on ]