Posts Tagged ‘Ubuntu’

Useful Bash Scripts

Tuesday, April 7th, 2009
Bash
Image via Wikipedia

Here’s a couple of bash scripts I’ve written recently that might be of use to someone.They work well under Ubuntu, and should work under any GNU/Linux or Unix system with the suitable software installed.

Improved “svn diff” command (ignores whitespace, colour highlights output, requires colordiff) – I put it in /usr/local/bin/svndiff:

#!/bin/bash svn diff -x -w $@ | colordiff

Improved recursive grep command (greps recursively, ignores files in the .svn folders, ignores temporary files, highlights output in colour) – I put it in /usr/local/bin/grepr:

#!/bin/sh SEARCHTERM=$1; shift; find . -type f -a -not -iname "*~" -a -not -iwholename "*/.svn/*" -exec grep -H --color=auto $@ "$SEARCHTERM" "{}" \;

You might also be interested in my previous “whoops I deleted files without telling svn” post here.

Reblog this post [with Zemanta]
Bookmark and Share

Working: HDMI Audio on ATI Graphics Card

Friday, October 24th, 2008
List of video connectors

Image via Wikipedia

Under Ubuntu Intrepid Ibex (should also work for Hardy Herron) with pulseaudio.

(Gfx card: ATI HD 4850)

It is a simple fix that took me ages to work out. Basically, PulseAudio does not recognize the graphics card’s sound card. To fix, we simply force it to recognize it, and remove detection  of alternatives to make it default. There is almost definitely a better way than removing the alternatives,  but *meh* it works for me.

First, work out which device is your correct HDMI device (in this case, 1,3 as it is card 1, output 3):

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC883 Analog [ALC883 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: ALC883 Digital [ALC883 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 3: ATI HDMI [ATI HDMI]
Subdevices: 0/1
Subdevice #0: subdevice #0

Open up /etc/pulse/default.pa in your favourite text editor

Add this line just before all the #load_module lines (around line 32), replacing 1,3 with whatever you found above):

add-autoload-sink output module-alsa-sink device=plughw:1,3 rate=48000 sink_name=output

Comment out the module-hal-detect section (around lines 40-47):

#### Automatically load driver modules depending on the hardware available
#.ifexists module-hal-detect.so
#load-module module-hal-detect
#.else
#### Alternatively use the static hardware detection module (for systems that
#### lack HAL support)
#load-module module-detect
#.endif

Uncomment this line at the bottom of the file:

set-default-sink output

Save and close the file, then log out and back in again (or kilall pulseaudio && pulseaudio) and, hopefully, your sound should work!

Reblog this post [with Zemanta]
Bookmark and Share

Ubuntu NFS Home Directory Issues

Saturday, May 24th, 2008
Horny Humpback

Image by Blyzz via Flickr

If you choose to mount over NFS just one of your user’s home directories (e.g. /home/jem) under Ubuntu, then you may come accross issues such as failure to log in, the screen freezing (but mouse still moving), loss of configuration data (e.g. icons in your panels), being told that your login session lasted under 10 seconds, and just general instability.

The reason for this is, in Ubuntu’s rush to get you to the Desktop quickly, it loads up GDM (and possibly auto-logs you in) *before* your home directory is mounted over NFS. This is a simple issue of priorities. However, if you log in before the home directory has been mounted, then gconfd-2 and other similar apps will load (or save) settings to your (supposedly empty) /home/jem on your hard drive. When you give up and log out (e.g. Control-Alt-Backspace, or a proper logout), and log back in again, these programs will still be accessing the wrong settings, because they continue to run in the background.

The solution is to abort Ubuntu’s Windows-like behaviour of allowing you to log in before everything has started running at boot time – change GDMs priority from 14 to 80 (or some other number). I chose to do this the lazy way, using “bum“. BUM, the Boot Up Manager, is a simple way to change all things related to booting. It is easy to use, though it does take quite a while (a few minutes!) to start the first time you run it. It must be run in a graphical environment. Simply tick the advanced box, go to the third tab, find gdm, and change its priority up to 80. Save, exit and reboot, and all is well again in the world… though you may have to restore your settings from a backup, or go through the long process of re-configuring your desktop the way you like it.

Good luck!

Bookmark and Share

Synce-gnomevfs Install on Ubuntu

Sunday, April 6th, 2008
Ubuntu (Linux distribution)Image from Wikipedia

Windows MobileImage from Wikipedia

Yesterday I tried to install the latest version of synce in order to get Jem’s Dad’s Windows Mobile 6 phone to share files with Linux (Ubuntu Gutsy Gibbon in this case). After managing to get the software installed, I have been very impressed with it, however actually installing it was a bit of a challenge, though the solution is quite simple and I share it with you now.

  1. Uninstall everything synce related before starting.
  2. Follow the Synce with Ubuntu instructions.
  3. pls should work at this time.
  4. Follow the SynceVfs instructions.
    Use ./configure –prefix=/usr
    make; sudo make install
  5. Heres the important bit:
    cp /usr/etc/gnome-vfs-2.0/modules/synce-module.conf /etc/gnome-vfs-2.0/modules/
  6. killall gnome-vfs-daemon

I think that you can do step 5 alternatively by adding –sysconfdir=/etc to your ./configure command in step 4, however I have not tested this.

Once this is done you should be able to just plug your phone (or other Windows Mobile device) in to the USB, and type synce:/// into Nautilus’ address bar. Simple!

Bookmark and Share