Nada

Ubuntu, Eclipse, Subclipse

2011-08-29T16:26:00.002+02:00

Subclipse 1.6.18 installed on Eclipse 3.7 on Ubuntu didn't work complaining about:

org.tigris.subversion.javahl.ClientException: svn: REPORT of '$FILENAME_REMOVED': 400 Bad Request ($REPO_URL_REMOVED)

Installing 'libsvn-java' package and changing 'SVN Interface' in Eclipse ('Window -> Preferences -> SVN') to JavaHL (JNI) helps.

2011-05-05T14:23:00.006+02:00

If your Node Manager complains during start-up that it cannot read its state:

java.io.IOException: Invalid state file format. State file contents:
at weblogic.nodemanager.common.StateInfo.load(StateInfo.java:135)
at weblogic.nodemanager.server.ServerMonitor.loadStateInfo(ServerMonitor.java:475)
at weblogic.nodemanager.server.ServerMonitor.isCleanupAfterCrashNeeded(ServerMonitor.java:139)
at weblogic.nodemanager.server.ServerManager.recoverServer(ServerManager.java:255)
at weblogic.nodemanager.server.DomainManager.initialize(DomainManager.java:103)
at weblogic.nodemanager.server.DomainManager.(DomainManager.java:55)
at weblogic.nodemanager.server.NMServer.initDomains(NMServer.java:219)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:199)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:355)
at weblogic.NodeManager.main(NodeManager.java:31)

then you need to remove the following file:

d:\bea\user_projects\domains\$DOMAIN_NAME\servers\C_0-S0\data\nodemanager\C_0-S0.state

So i upgraded ATI drivers

2008-05-23T21:26:00.003+02:00

... and all I got was this lousy, corrupted display in Google Earth. Sigh.

Thankfully, it's usable, ie. it flickers briefly and only becomes very annoying when there are lots of lines (roads, borders) on the screen. But still: sigh.

ATI proprietary drivers on Debian

2008-05-22T21:56:00.004+02:00

1) get binary package from ATI

2) generate packages:


$ ./ati-driver-installer-8-5-x86.x86_64.run --buildpkg Debian/etch

3) install generated packages


$ wajig install fglrx-driver_8.493-1_i386.deb fglrx-amdcccle_8.493-1_i386.deb fglrx-driver-dev_8.493-1_i386.deb fglrx-kernel-src_8.493-1_i386.deb

If you installed fglrx-glx from official Debian repos before (like my experimentally inclined self) you may get an error with clashing diversions (see bug475007):


dpkg-divert: `diversion of /usr/lib/libGL.so.1.2 to /usr/lib/fglrx/diversions/libGL.so.1.2 by fglrx-driver' clashes with `diversion of /usr/lib/libGL.so.1.2 to /usr/lib/fglrx/diversions/libGL.so.1.2 by fglrx-glx'

Remove the offending diversion then:


$ dpkg-divert --remove /usr/lib/libGL.so.1.2
Removing `diversion of /usr/lib/libGL.so.1.2 to /usr/lib/fglrx/diversions/libGL.so.1.2 by fglrx-glx'

4) compile kernel module

After installing fglrx-kernel-src you should have module source tarball under /usr/src:


$ ls -la fgl*
-rw-rw-r-- 1 root root 1228049 2008-05-22 16:04 fglrx.tar.bz2

Make sure this is the right one, module-assistant by default operates on source found under /usr/src. You can change this behavior via MOD_SRCDIR environment variable. Now build it (do not m-a update or m-a auto-install because it would download source from repo):


$ m-a build,install fglrx-kernel-src

5) Hold packages

Put manually generated packages on hold so they won't get auto-updated during your usual update routine


$ wajig  hold fglrx-amdcccle fglrx-kernel-src fglrx-driver fglrx-driver-dev

or, if you don't use wajig:


$ echo "fglrx-amdcccle hold" | dpkg --set-selections
$ echo "fglrx-kernel-src hold" | dpkg --set-selections
$ echo "fglrx-driver hold" | dpkg --set-selections
$ echo "fglrx-driver-dev hold" | dpkg --set-selections

6. update xorg.conf

If you don't have proper entries in your xorg.conf yet, create them using


$ aticonfig --initial

7. reboot

Multiple versions of Java on Debian

2008-05-02T22:04:00.013+02:00

Goal: To install both Java6 and Java7 from Sun and configure a simple way to change which one is used as system default.

Procedure:

I. Install Java6.

After Sun went GPL with Java, Debian started to include it in the repos, but it usually seriously lags behind, so we will install Java from Sun binary packages which can be downloaded from Sun's website. For this we will need two packages: fakeroot and java-package. The whole process is described here and in short looks like:

1) as a non-root user copy *.bin file to the directory where you have write permission
2) still as a non-root:
$ fakeroot make-jpkg $name_of_java_binary_package
3) accept licence, wait a while when .deb builds
4) as a root install .deb created in pt.3

Remember though that there are some packages that depend explicitly on 'sun-jre-1.6' (package provided by java from Debian repositories), while java created with java-package provides more general 'j2re1.6'. There are also packages that depend specifically on GNU Java (scala for example) so installing those will pull whole new Java stacks. Did anyone say 'dependency mess'?

II. Install java7.

Above works like charm for java6, but will fail with java7 because java-package knows nothing about java7 yet. We will have to prepare the configuration ourselves. Basing on info found here that's what we're going to do:

1) use the configuration for java6 as the basis:
$ cp -a /usr/share/java-package/sun-j2sdk1.6 /usr/share/java-package/sun-j2sdk1.7

2) Edit 'install' and 'remove' scripts:
a) update line starting with 'suffix': suffix=j2sdk1.7-sun
b) as of beta26 java7 constains the same list of binaries as java6, so we can leave 'update-alternatives' configuration unchanged

3) update 'sun-j2sdk.sh', add the following to the case statement responsible for handling your architecture:


#jdk-7-ea-bin-b26-linux-i586-24_apr_2008.bin
# WARNING:     change following  when beta numbers > 99
  "jdk-7-ea-bin-b"[0-9][0-9]"-linux-i586"*)
  j2se_version=1.7+beta${archive_name:14:2}${revision}
  j2se_expected_min_size=130
  found=true
  ;;

Now .deb should build without problems, just like with java6. Install it using your package management software of choice (wajig in my case):

banshee:/usr/src/java# wajig install sun-j2sdk1.7_1.7+beta26_i386.deb

At this point, basically everything is configured, you may use update-alternatives to set which java will be used across the system:


banshee:/etc/alternatives# update-alternatives --config java

There are 4 alternatives which provide `java'.
Selection    Alternative
-----------------------------------------------
+        1    /usr/lib/jvm/java-gcj/jre/bin/java
*         2    /usr/lib/j2sdk1.6-sun/bin/java
  3    /usr/lib/j2sdk1.7-sun/bin/java
  4    /usr/bin/gij-4.3

Press enter to keep the default[*], or type selection number: 3
Using '/usr/lib/j2sdk1.7-sun/bin/java' to provide 'java'.

III. A bit more fun with update-alternatives

To avoid having to manually switch all binaries that come with Java (like javac, javap etc) you can write two simple scripts which will automate the process:


banshee:/etc/alternatives# cat /usr/bin/switch_to_java6
#! /bin/sh
for i in $(ls /usr/lib/j2sdk1.6-sun/bin/); do
  update-alternatives --set $i /usr/lib/j2sdk1.6-sun/bin/$i;
done;

banshee:/etc/alternatives# cat /usr/bin/switch_to_java7
#! /bin/sh
for i in $(ls /usr/lib/j2sdk1.7-sun/bin/); do
  update-alternatives --set $i /usr/lib/j2sdk1.7-sun/bin/$i;
done;

You will see some warnings like:


Using '/usr/lib/j2sdk1.7-sun/bin/jconsole' to provide 'jconsole'.
update-alternatives: Cannot find alternative `/usr/lib/j2sdk1.7-sun/bin/jcontrol'.

That's because not everything contained in jdk's bin/ directory is provided as an alternative. Those warnings are harmless.

javac -XD-printflat

2007-10-16T21:35:00.000+02:00

As a self-remainder, extremely useful 'hidden' javac option I found here:

$ javac -XD-printflat

Copying EXIF tags

2007-06-04T19:28:00.000+02:00

Somewhere along my image processing worklow (RAW -> ufraw -> tiff -> GIMP -> jpg -> flickr) I lost EXIF data. Probably it'd been stripped during conversion to tiff using ufraw. Hmm, how to automagically copy EXIF meta-data from CR2 RAW files to post-processed jpgs? Exiftool to rescue!

/home/banshee# wajig install libimage-exiftool-perl
/home/banshee# cd $ImagesDir
$ImagesDir# exiftool -tagsfromfile %d%f.CR2 -r -ext jpg .

From exiftool manpage: exiftool -tagsfromfile %d%f.CRW -r -ext JPG dir
*Recursively* rewrite all "JPG" images in "dir" with information copied from the corresponding "CRW" images in the same directories.

2007-02-08T15:30:00.000+01:00

As a sidenote to future self, next time before you spend an hour on debugging a completely unrelated issue, please check if you enabled auto-generating primary keys on this 'one-time debug' copy of the database... FFS.

Mounting external ntfs partitions using ntfs-3g

2007-01-27T14:33:00.000+01:00

When you use removable media you probably want to mount it always to the same mount point regardless of its physical dev node location which can can change depending on the order you connect the devices or the slot you connect them to. This is where LABEL/UUID fstab options come in handy.

So, instead of a fstab entry like this:

/dev/sda5 /mnt/FOTO_BCKP ntfs defaults 0 0

you make an entry like this:

LABEL=FOTO_BCKP /mnt/FOTO_BCKP ntfs defaults 0 0

But if, instead of a default ntfs driver, you want to use a new ntfs-3g driver, there's a small problem: ntfs-3g, at the time of writing this, doesn't support LABEL or UUID options. A nice workaround, which I found here is to use /dev/disk/by-label/:

/dev/disk/by-label/FOTO_BCKP /mnt/FOTO_BCKP ntfs-3g defaults,user 0 0

To check labels or uuids, connect your media and simply list /dev/disk subdirectories:

ls -l /dev/disk/by-label/
ls -l /dev/disk/by-uuid/

To set the ntfs partition's label use `ntfslabel` from ntfsprogs package.

How to make BCM4318 on Acer5024 work on Debian Etch

2007-01-10T12:11:00.001+01:00

WARNING: for kernels >= 2.6.24 this note is deprecated. Use b43 driver + acer-wmi instead. I'll try to write about it in a while.

== original blognote follows ==

BCM4318 is a wireless chipset from Broadcom Corporation. Full name, as given by lspci is: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller.

Broadcom released only Windows driver for this chipset, so to make this card work under Linux you have two choices:

- native, open source driver included in the kernel since 2.6.17-rc2. Because Broadcom refused to provide any kind of specification for this chipset, development on this driver is based on reverse-engineering.
- Windows binary-only driver and ndiswrapper

There's an ongoing flamew^Wdiscussion whether using binary drivers as a fast way to support more hardware under Linux is a good or a bad thing. It's actually pretty interesting, if you feel like reading some more you can start by pointing your browser at Linux Kernel Mailing List Archive.
Even if you don't care much for security or ethical reasons, in the long term native driver would be a better choice because it is possible that at some point in the future kernel will ban binary modules. So, one of these choices has a future, and one of them does not, Mr. Anderson.
But reality bites and as of january 2007 native driver is said to be still in an experimental state, there's no WPA support, connection is not stable, speed is limited to 11 Mbps/sec and there are some power issues with BCM4318 in particular. Tough luck. The choice is yours :-)

For now I decided to use ndiswrapper. This is a step-by-step description how I made this little Broadcom's beast work on my Acer Aspire 5024 laptop under Debian Etch using ndiswrapper:

You will need:

BCM4318 driver for Windows, I got mine from Acer ftp.

acer_acpi

ndiswrapper

kernel headers for your kernel's version, this is a prerequisite for compiling acer_acpi and ndiswrapper modules

Also it's really helpful to have an extra console window running `tail -f /var/log/messages` open during the process, just to see what's going on, make sure you're on the right track or diagnose problems if you are not :-)

Installing acer_acpi:

0. Download tarball from the location given above, unpack it to /usr/src/ or /usr/local/src and cd to acer_acpi directory.

1. Read 'INSTALL' file :-)

2. As advised in 'INSTALL' file:
make acer_acpi.ko

3. Copy acer_acpi.ko to lib/modules/$kernelversion/kernel/drivers/char/

4. depmod -a

5. modprobe acer_acpi

Installing ndiswrapper:

0. You can get ndiswrapper from Debian repositories, so simply:
apt-get install ndiswrapper-utils-1.9
apt-get install ndiswrapper-source

1. Unpack ndiswrapper-source to /usr/src or /usr/local/src and cd to its directory.

2. Install ndiswrapper module:
make install
Alternatively you could use module-assistant to get, build and install ndiswrapper kernel module:
m-a a-i ndiswrapper

3. Download windows driver, unpack it to any directory (AFAIR you only need bcmw5.inf and bcmw5.sys files) and cd there.

4. Install driver
ndiswrapper -i bcm5.inf
Check if driver installed succesfully:
ndiswrapper -l

5. Unload native bcm43xx driver
modprobe -r bcm43xx
and put it on a blacklist so it doesn't load automatically by adding entry in /etc/modprobe.d/blacklist file:
blacklist bcm43xx

6. Load ndiswrapper module
modprobe ndiswrapper

You can read here a bit more about managing modules on Debian.

Configuring wireless card:

acer_acpi module creates entries under /proc/acpi/acer. Now you can enable the hardware. Linux equivalent of pushing the wi-fi button on Windows is:

echo "enabled : 1" > /proc/acpi/acer/wireless

Show that to your girlfriend for that extra 'You're weirdo...' look :-)

Of course typing this manually every time you want to turn your wireless on/off is out of question, so put that in your network interface configuration. On Debian you do that in /etc/networking/interfaces. Read man interfaces and man wireless for more info on commands and syntax. Here's how my wireless entry looks like:

# wireless
auto eth0
iface eth0 inet dhcp
pre-up modprobe ndiswrapper
pre-up modprobe acer_acpi
pre-up echo "enabled : 1" > /proc/acpi/acer/wireless; sleep 1;
post-down echo "enabled : 0" > /proc/acpi/acer/wireless
wireless-ESSID yourESSID
wireless-key yourKey
wireless-mode auto

So ifup at first loads ndiswrapper, then acer_acpi module, then enables the hardware and finally configures interface with wireless-<> commands. These are the same parameters you would give to iwconfig.
Note that sleeping after enabling wireless is crucial (at least on my machine...), otherwise ifup tries to configure the card too early, while it's not really enabled yet (just a guess but it behaved like that).

Now, if everything went okay, `ifup eth0` should give you working wireless connection. Hopefully :-)