Pete's Personal Homepage

Hacking Conky in Ubuntu

The important infos that have effect on conky:

Original system:

• Linux: Ubuntu - Feisty Fawn
• Processor: Sinlge core AMD64
• Graphics: Nvidia 6800 Ultra
• Desktop: Beryl

New system:

• Linux: Ubuntu - Gutsy Gibbon
• Processor: Quad-core Intel
• Graphics: Nvidia 8800 GTS
• Desktop: Compiz (w/ tweaks to make it like Beryl)

As with anything you'll need the right software installed, 'lm-sensors', 'hddtemp', 'nvidia-settings', etc. I won't bother explaining in detail. You'll want to check out the Conky homepage, Conky how-to for Ubuntu, Ubuntu Forum's conkyrc file thread, and Brian Carper's Conky blog posts.

${color slate grey}UP: ${color}$uptime
${color slate grey}CPU: ${color}${freq_dyn}Mhz $cpu% ${i2c 9191-0290 temp 2}C
${color slate grey}GPU: ${color}${execi 60 nvidia-settings -query GPUCoreTemp | perl -ne 'print $1 if /GPUCoreTemp.*?: (\d+)./;'}C
${color slate grey}MOBO: ${color}${i2c 9191-0290 temp 1}C
${color slate grey}C/S: ${color}${i2c 9191-0290 temp 3}C
${color slate grey}ROOT: ${color}${fs_free /} ${color}${exec nc localhost 7634 | perl -ne 'print $1 if /\/sda\|.*?\|(\d+)\|C/;'}C

For getting cpu, mother board, and bridge temps, using ${i2c (dev) type n} requires the dev part to work, the value to which is in /sys/bus/i2c/devices. For GPU temp we simply call nvidia-settings -query GPUCoreTemp and parse the output with perl - note the use of execi with a timer - thats because the nvidia-settings program seemed to cause crasues if queried to frequently over a period of time. Lastly hard drive temp needs to query hddtemp via localhost so we use nc localhost 7634. Again parsing the output with perl (god I love perl).

As I mentioned at the start of this - your PC's configuration will dictate what you want to put into your conkyrc file. Even between my original system and my new system I had to change the CPU parts obviously, but also the motherboard tempature settings.

How to Test Your Gnome Display Manager (GDM) Themes

A GDM Theme is a login screen for Gnome Desktop Envorment. There is only one good tutorial I've found so far on the net reguarding how to make a GDM from scratch. They suggested first making a small shell script:

chvt 7 ; sleep 5 ; XAUTHORITY=/var/gdm/:0.Xauth DISPLAY=:0.0 import -window root /tmp/gdm-shot.png

You'll have to point your XAUTHORITY to the right location (/var/lib/gdm on Ubuntu), and set the right xserver number, etc. After that you logout (to the GDM screen) and press CTRL+ALT+F1 to reach the root shell. Login as root, you will then run the script which if all works right will result in the png file being made. For me the problem was that the image was always empty even though everything appeared to be working correctly.

An alternitive is that you can use a program called Xnest which can be used by GDM to create a new X Server inside of a window. There are a number of different ways to launch Xnest and get GDM attached to it but the simplest way I've found is the GDM command gdmflexiserver -n. Hopefully it works perfectly and you have something that looks like:

This may also have a couple of issues, such as the window/desktop created may be distorted ratio wise. The best way to solve this is to modify /etc/gdm/gdm.conf which provides the arguements that GDM will pass to Xnest when it is launched. I modified mine to look like this:

Xnest=/usr/bin/Xnest -geometry 1280x1024 -br -br -audit 0 -name Xnest

Hopefully thats enough details on this.

Fin.

Samsung SyncMaster 204B Blackouts and Snow Problems Work Around for Windows and Linux

Problem description:

When using the Samsung SyncMaster 204B in DVI mode at 1600x1200 can sometimes result in blackouts, or a sort of pixel snow on some parts of the picture. This happens for me on some nVidia graphics boards, I don't know if it happens on any other kinds of graphics cards. Some report that the blackouts get more frequent, while others only experence the pixel snow. One solution is to use the display in its vga analog mode, but if you don't like that don't worry - there are work arounds.

This can be a very mysterious problem which many people report not getting much help from Samsung with except to return/exchange the LCD. Some report that it is only a problem with models made in China as well. Skip over that stuff, and onto the fix!

Windows Solution:

For either Linux or Windows, the goal is to switch the timing standard a little down from 60Hz to 59.92Hz. In windows this can be done by turing on "CVT Reduced Blank" which lives in nVidia Control Panel -> Display -> Manage Custom Timings -> Create or Edit -> Advanced.

Linux Solution:

This will require adding the following mode line to the /etc/X11/xorg.conf file in the Monitor section.

ModeLine "1600x1200_59.92_rb" 130.25 1600 1648 1680 1760 1200 1203 1207 1235 +hsync -vsync

And to the Device section this line:

Option "ExactModeTimingsDVI" "yes"

Then in the Display section add "1600x1200_59.92_rb" to the front of the mode list as you would "1600x1200", or any other desired resolutions. Like so:

Modes "1600x1200_59.92_rb" "1600x1200" "1024x768"

Lastly, if you're running dual displays in TwinView you will also need to modify the MetaModes option.

Option "MetaModes" "1600x1200_59.92_rb,1600x1200_59.92_rb;1600x1200,1600x1200;1024x768,1024x768"

I give credits to the smart asses on nvnews for most of this solution.