Showing posts with label ubuntu. Show all posts
Showing posts with label ubuntu. Show all posts

2013-09-15

Windows 7 insomnia after Ubuntu installation

Recently, I installed Ubuntu 13.04 on my Windows 7 machine. It all went smooth, and was even surprised how everything seemed to work well in Ubuntu without any tweaking. The collateral damage was on the Windows side: it could not go to stand-by any more, even if it was no problem before I installed Ubuntu.

A short search showed an interesting thread from the Ubuntu forum. The various solutions requiring activating a partition were not helpful to me, since the installation was on two separate disks, both active partitions. However, the powercfg command did the trick:

powercfg -h off as administrator restaured instantly my stand-by :)

2012-03-05

Music Player Daemon & Co.

Since installing subsonic is so easy to set up, I looked for another challenge: MPD.

I tried to use Rhythmbox and Banshee as players on my computer dedicated for audio outputs. If the music is located elsewhere on the LAN, both ended up unable to index 100+Gb music, and since I do not like their GUI anyway, I found out another possible solution with MPD.

Installing and setup for Ubuntu 11.10

1. Install

sudo apt-get install mpd mpc gmpc

This will retrieve mpd together with the command line player mpc and the Gnome client gmpc, for those GUI users.

2. Configure

Some guides I found (most of them) explain how to set up mpd on a system using root rights. I preferred to get everything installed for my current user, mainly to be easier to port to another installation later on, and also because I just like simple backup from user home directory. So instead of following guides creating a mpd directory on /var/lib and using a /etc/mpd.conf, I choose to create a mpd directory under the home directory, and use a .mpdconf file.

Following commands are enough to create required directories and starting with a new configuration file.

cd ~
mkdir mpd
mkdir mpd/playlists
gedit .mpdconf

Here is my configuration file (.mpdconf). The music_directory and the playlist directory should exist, according to previous commands.

# Files and directories #######################################################
#
# This setting controls the top directory which MPD will search to discover the
# available audio files and add them to the daemon's online database. This
# setting defaults to the XDG directory, otherwise the music directory will be
# be disabled and audio files will only be accepted over ipc socket (using
# file:// protocol) or streaming files over an accepted protocol.
#
music_directory         "~/Music"
#
# This setting sets the MPD internal playlist directory. The purpose of this
# directory is storage for playlists created by MPD. The server will use
# playlist files not created by the server but only if they are in the MPD
# format. This setting defaults to playlist saving being disabled.
#
playlist_directory              "~/mpd/playlists"
#
# This setting sets the location of the MPD database. This file is used to
# load the database at server start up and store the database while the
# server is not up. This setting defaults to disabled which will allow
# MPD to accept files over ipc socket (using file:// protocol) or streaming
# files over an accepted protocol.
#
db_file                 "~/mpd/mpd_db"
#
# These settings are the locations for the daemon log files for the daemon.
# These logs are great for troubleshooting, depending on your log_level
# settings.
#
# The special value "syslog" makes MPD use the local syslog daemon. This
# setting defaults to logging to syslog, otherwise logging is disabled.
#
log_file                        "~/mpd/mpd.log"
#
# This setting sets the location of the file which stores the process ID
# for use of mpd --kill and some init scripts. This setting is disabled by
# default and the pid file will not be stored.
#
pid_file                        "~/mpd/pid"
#
# This setting sets the location of the file which contains information about
# most variables to get MPD back into the same general shape it was in before
# it was brought down. This setting is disabled by default and the server
# state will be reset on server start up.
#
state_file                      "~/mpd/state"
#
# The location of the sticker database.  This is a database which
# manages dynamic information attached to songs.
#
sticker_file                   "~/mpd/sticker.sql"
#
###############################################################################


# General music daemon options ################################################
#
# This setting specifies the user that MPD will run as. MPD should never run as
# root and you may use this setting to make MPD change its user ID after
# initialization. This setting is disabled by default and MPD is run as the
# current user.
#
#user                           "mpd"
#
# This setting specifies the group that MPD will run as. If not specified
# primary group of user specified with "user" setting will be used (if set).
# This is useful if MPD needs to be a member of group such as "audio" to
# have permission to use sound card.
#
#group                          "nogroup"
#
# This setting sets the address for the daemon to listen on. Careful attention
# should be paid if this is assigned to anything other then the default, any.
# This setting can deny access to control of the daemon. Choose any if you want
# to have mpd listen on every address
#
# For network
bind_to_address         "localhost"
#
# And for Unix Socket
#bind_to_address                "/var/run/mpd/socket"
#
# This setting is the TCP port that is desired for the daemon to get assigned
# to.
#
port                            "6600"
#
# This setting controls the type of information which is logged. Available
# setting arguments are "default", "secure" or "verbose". The "verbose" setting
# argument is recommended for troubleshooting, though can quickly stretch
# available resources on limited hardware storage.
#
#log_level                      "default"
#
# If you have a problem with your MP3s ending abruptly it is recommended that
# you set this argument to "no" to attempt to fix the problem. If this solves
# the problem, it is highly recommended to fix the MP3 files with vbrfix
# (available as vbrfix in the debian archive), at which
# point gapless MP3 playback can be enabled.
#
#gapless_mp3_playback                   "yes"
#
# This setting enables MPD to create playlists in a format usable by other
# music players.
#
save_absolute_paths_in_playlists        "no"
#
# This setting defines a list of tag types that will be extracted during the
# audio file discovery process. Optionally, 'comment' can be added to this
# list.
#
#metadata_to_use        "artist,album,title,track,name,genre,date,composer,performer,disc"
#
# This setting enables automatic update of MPD's database when files in
# music_directory are changed.
#
auto_update    "yes"
#
# Limit the depth of the directories being watched, 0 means only watch
# the music directory itself.  There is no limit by default.
#
#auto_update_depth "3"
#
###############################################################################


# Symbolic link behavior ######################################################
#
# If this setting is set to "yes", MPD will discover audio files by following
# symbolic links outside of the configured music_directory.
#
follow_outside_symlinks "yes"
#
# If this setting is set to "yes", MPD will discover audio files by following
# symbolic links inside of the configured music_directory.
#
follow_inside_symlinks          "yes"
#
###############################################################################


# Zeroconf / Avahi Service Discovery ##########################################
#
# If this setting is set to "yes", service information will be published with
# Zeroconf / Avahi.
#
zeroconf_enabled                "yes"
#
# The argument to this setting will be the Zeroconf / Avahi unique name for
# this MPD server on the network.
#
zeroconf_name                   "Not-o-Matic Music Player"
#
###############################################################################


# Permissions #################################################################
#
# If this setting is set, MPD will require password authorization. The password
# can setting can be specified multiple times for different password profiles.
#
#password                        "password@read,add,control,admin"
#
# This setting specifies the permissions a user has who has not yet logged in.
#
#default_permissions             "read,add,control,admin"
#
###############################################################################


# Input #######################################################################
#

input {
        plugin "curl"
#       proxy "proxy.isp.com:8080"
#       proxy_user "user"
#       proxy_password "password"
}

#
###############################################################################

# Audio Output ################################################################
#
# MPD supports various audio output types, as well as playing through multiple
# audio outputs at the same time, through multiple audio_output settings
# blocks. Setting this block is optional, though the server will only attempt
# autodetection for one sound card.
#
# See  for examples of
# other audio outputs.
#
audio_output {
        type            "alsa"
        name            "MPD ALSA Output"
        device          "hw:0,0"        # optional
        format          "44100:16:2"    # optional
        mixer_type      "software"
        mixer_device    "default"       # optional
        mixer_control   "PCM"           # optional
        #mixer_index    "0"             # optional
}

audio_output {
        type    "pulse"
        name    "MPD PulseAudio Output"
        #server  "localhost"   # optional
        #sink    "alsa_output" # optional
}

audio_output {
        type            "httpd"
        name            "MPD HTTP Stream"
        encoder         "vorbis"                # optional, vorbis or lame
        port            "6680"
#       quality         "5.0"                   # do not define if bitrate is defined
        bitrate         "192"                   # do not define if quality is defined
        format          "44100:16:1"
}

# Character Encoding ##########################################################
#
# If file or directory names do not display correctly for your locale then you
# may need to modify this setting. After modification of this setting mpd
# --create-db must be run to change the database.
#
filesystem_charset              "UTF-8"
#
# This setting controls the encoding that ID3v1 tags should be converted from.
#
id3v1_encoding                  "UTF-8"

Running MPD

Now it is already time to hear some music!
Just enter following in your terminal:

mpd
Yes, this is all!

Running the gnome MDP client

Once the client is running, in the Server-menu, there is an Update entry. This will populate the music database with data found under the ~/Music directory, and music will be shown in the left panel. From here, it is easy to get music played.

Problems?

Note that if all sounds easy, it is also easy to miss a small part of these steps, and no music will be played. There is some things to check, in order to find out possible problems.

  • Check that sound is working, using Rhythmbox for example, and playing a local music file.
  • Check that all pathes are correct. A wrong path to the music will be problematic for mpd to find any music. A non existing path for the database file will also be problematic to populate the database with content.
  • Still no music? Using Ubuntu Unity, I could play without problem the music, but not under XFCE. This was because of muted sound on the login screen!

Bonus: Client175

Now, once MPD is running smoothly on the audio box, perhaps (probably) one would like to control the music from other devices.
There is a huge list of clients for MPD here: http://mpd.wikia.com/wiki/Clients.
However, some of them are old/abandoned/unfinished projects. This requires a bit of searching to get the one(s) you like.

A simple web access can be achieved using Client175. The setup does not require anything to run correctly (based on my .mpdconf). I just created a folder for the client175 files under my mpd directory, and started it with python server.py. Then accessing from another box with your prefered browser is enough to enjoy it (default port is 8080, not to forget when trying to connect ;) ).

2012-01-17

Mint trial

After lots of playing around with my Ubuntu box, I eventually managed to get some strange effects I could not solve with my poor knowledge of the system. Since I've heard it is not difficult to reinstall the system and keep my settings, I decided to give it a try.

It's almost enough to keep one's home directory as backup, all settings for various applications are safe this way and do not need to be reconfigured after the reinstallation is done.

But since I got quite some problems at first with Unity, then could use it but was not pleased with it, I decided to try something different. Linux Mint seemed to be quite popular too. This is what I choose to replace my standard Ubuntu (using XFCE instead of Unity).

After two weeks of Mint, I am ready to remove it and go back to plain Ubuntu (well, still avoiding Unity, of course). The reason? even if the desktop looks nice, this is not much more than a front and not much behind other than an Ubuntu with less accessible configuration over the GUI.
Also, using this box also as a jukebox, it makes no sense when Banshee and Rhythmbox were both instable, and sometime the system seemed to have slow down to the point I had to reboot.

So, next install? next try with Linux? I'll try again Ubuntu, this time with XBMC, let see what happens :)

2011-11-14

What hardware is in there?

You are helping out friends with a linux installation? You just forgot what hardware you used to build your server out of spare parts?
I found the lshw command to be a quick help: sudo lshw -html > ~/hw.html
Now, opening the created file to be located in your home directory will show all kind of hardware details, like how much memory was installed, what disks, what processor and motherboard... So no need to get the screwdriver.

2011-09-02

Loud fans...again

Configuring fan speed using pwmconfig and fancontrol is not a big deal, normally. However, some problem can arise (see: "Loud fans...WHAT?"). Now it was running smoothly on my machine, but was not always working after a reboot.

Running sudo fancontrol brings up no noise reduction, but following message:

Not starting fancontrol, outdated configuration file; please re-run pwmconfig.
Running and restarting fancontrol helps, but it will eventually fail later, after some reboot.
A closer look to the /etc/fancontrol config file shows following (on my system):
INTERVAL=10
DEVPATH=hwmon0=devices/platform/w83627ehf.656
DEVNAME=hwmon0=w83627dhg
FCTEMPS=hwmon0/device/pwm2=hwmon0/device/temp2_input
FCFANS=hwmon0/device/pwm2=hwmon0/device/fan2_input
MINTEMP=hwmon0/device/pwm2=35
MAXTEMP=hwmon0/device/pwm2=65
MINSTART=hwmon0/device/pwm2=135
MINSTOP=hwmon0/device/pwm2=90
MINPWM=hwmon0/device/pwm2=90
MAXPWM=hwmon0/device/pwm2=255
When I run again pwmconfig, what I missed first was the number behind hwmon. This number changed, being sometime 0, sometime 1 after rebooting. Searching for this kind of problem brought up this interesting page with the solution.
This seems to happen quite often in relation with the k8temp module. Anyway, removing this module from /etc/modules and black-listing it in the file /etc/modprobe.d/blacklist.conf adding blacklist k8temp did the trick, and I can listen to music without vacuum cleaner noise in background.

2011-04-03

Non-root subsonic installation

I choose already for some time subsonic as music streaming and jukebox system. This was working well with the basic installation information provided from the website:

sudo apt-get install openjdk-6-jre
sudo dpkg -i subsonic-x.x.deb
sudo apt-get install lame flac faad vorbis-tools ffmpeg

First problem: no sound in jukebox mode. The solution is to install the java from sun, and use this one instead of the openjdk provided by default.

sudo apt-get install sun-java6-jre sun-java6-plugin

Installing is only half of the job. Selecting what java to use is done with following command:

update-java-alternatives -s java-6-sun

Second problem: subsonic is now running as root. This is not a big deal when the server is intended to be use behind your firewall, but becomes a bit scary when allowing access from internet. The solution is described in the official subsonic forum. I preferred the second post of the thread explaining how to do the changes to run as a specific user still using the simple package based installation. The first post requires to configure your own web-server, a bit more complex for similar result.

I used slightly different commands:
sudo su
service subsonic stop
adduser --system --no-create-home subsonic
adduser subsonic audio
chown -R subsonic:nogroup /tmp/subsonic 
chown -R subsonic:nogroup /var/subsonic 
chown -R root:root /var/subsonic/transcode 
chown -R root:root /var/subsonic/jetty/*/webapp

Now we need to edit /usr/share/subsonic/subsonic.sh to use sudo -u subsonic before the call to java. The line looks like that with the change applied:

sudo -u subsonic ${JAVA} -Xmx${SUBSONIC_MAX_MEMORY}m \

Now subsonic can be started, and we can verify it uses the correct assigned user instead of root. Start subsonic: service subsonic start.

ps -Af | grep subsonic shows what user runs subsonic.

To finish, enjoy some music :)

2011-02-03

Loud fans... WHAT?


Before becoming deaf, I thought it would be a nice idea to check what can be done to slow down the fans. The good keywords are 'fancontrol' and 'pwmconfig'. With these, plenty of setup descriptions can be found.


To resume quickly:
  1. check what sensors you can use: sudo sensors-detect
  2. copy the drivers like indicated. A manual copy is better to avoid duplicate entries in your /etc/modules
  3. (optional) Some sudo modprobe work can be necessary if the drivers are not loaded
  4. now, a call to sudo pwmconfig will configure the fan speeds. Follow the proposed steps, it is well explained
  5. now the /etc/fancontrol file was created
  6. running sudo fancontrol & activates the fan speed regulation based on the settings made with pwmconfig

Unfortunately, executing the command sudo fancontrol & got me an error in /usr/sbin/fancontrol at line 402... Looking there, I was middle in a UpdateFanSpeed function, and one the the variables got invalid value. Since this section looks like it reads the settings made in the /etc/fancontrol file, I looked there. The problem could be solved easily using information from pwmconfig about what temperature sensor name to use, since this was missing.

The fan control worked once I corrected the /etc/fancontrol from
FCTEMPS= hwmon0/device/pwm2=
to
FCTEMPS= hwmon0/device/pwm2=hwmon0/device/temp1_input

Note that hwmon0/device/temp1_input was my preferred sensor, chosen based on the measured temperatures shown during pwnconfig set-up. This is probably only valid for my box.

2011-02-02

remote desktop and the 'd' key

Accessing my ubuntu box from windows over remote desktop connection worked without problem. However, after some update (again?), I figured out the 'd' key was not doing what expected: it would reduce all the windows of the gnome desktop instead of just inserting a simple 'd'... not really friendly when you want to play with 'sudo' command.

After some searching, the solution is quite simple: going to 'system > preferences > shortcuts' and looking for assigned shortcuts, 'd' was one of them, responsible for reducing all windows. Removing the shortcut (or replacing it with something useful) is enough to get 'd' back alive.

2011-02-01

ubuntu killer update

Some ubuntu 10.10 update broke it! I'm still having some problems, but I already learned about groups and the importance of the first created user.

This first user belongs (normally) to the admin group, and is allowed to use the 'sudo' command. It seems my '/etc/group' file got corrupted at some point, leaving my first user with almost no rights. Specially, I was not even allowed to use 'sudo' to get it fixed.

Thanks to this page, I got at least the required access rights back, editing the '/etc/group' file in recovery mode, adding my first user to the admin group. 'nano' is already configured to be used as alternative to 'vidudo' (often recommanded to edit '/etc/sudoers'), and much simpler to use for normal people. Also worth reading about 'sudo', in order to understand what it is all about: this ubuntu help page.

After I got my user back into the admin group, I had to edit again the '/etc/group' file to add my user also to various other groups, since every settings were gone.

Here is the list of groups I used (found on serverfault.com): 
  • adm
  • dialout
  • cdrom
  • floppy
  • fuse
  • audio
  • dip
  • video
  • plugdev
  • sambashare
  • lpadmin
  • admin

Note: having a backup is always the best solution. If you are lazy and lucky, you can find a valid 'group' file at one of these locations:
  • /etc/group_backup
  • /var/backups/group.bak