On this page you will a collection of short notes about different pieces of hardware I somewhere had the possibility to try out, on which there was no documentation on the internet, and for which a short explanation is sufficient.
All comments, suggestions etc. are welcome. Please contact me at email@example.com.
Western Digital My Book World Edition II
The first problem was that the windows shares could not be accessed in windows. I couldn't reach the NAS via ssh, so I had to switch it off hard. After switching it back on I still couldn't access the shares and got the following error in the webinterface.
I searched in google and only found descriptions to take out the hard disks, connect them to another computer and try to save the data. I didn't want to accept that fact, as long as I could ssh to the NAS and had a running Linux on the box.
So here is how to solve the problem step by step (at least how it worked for me):
Login as user root (not admin!). The default password is welc0me, this is not changed when you change the password for the webinterface.
You should see the mounted devices
In the root account:
First check the status of the RAID just to make sure that the hard disks and the underlying RAID is OK.
Obviously everything is OK there, so our only problem is that the data partition cannot be mounted.
So we have to stop all services accessing
NB: The integrated mount/umount in busybox always needs 2 parameters, device and mountpoint. Only one parameter results in the Error 'Invalid parameter'.
Then unmount the partition so the system realizes it is actually not mounted
From now on you can mount and remount the Device as often as you want.
Although mounting works let's check and repair the filesystem just in case it
got some damages.
This is the kernel version this NAS is running:
Max! eQ-3 Heizungsthermostat
Das Wochenprogramm lässt sich für ein Zimmer nicht auf die Geräte (in meinem
Fall 2 Heizkörper-Thermostate) in einem Raum laden. Alle anderen Räume
Schritte bei der Fehlersuche
An der Funkverbindung konnte es bei mir nicht liegen, da die Thermostate in
Sichtweite zum Cube installiert sind.
Lösung des Problems
Ich habe den Raum (und damit das Wochenprogramm) gelöscht, die beiden
Thermostate neu angelernt und einem neu angelegten Raum zugewiesen, ein
Wochenprogramm erstellt und erfolgreich an die Thermostate gesendet. Danach
Nokia S60 ' no gateway reply '
You get the error 'No gateway reply' when browsing over wifi / wireless lan?
For me it helped to enter the DNS server (although it should have been configured by DHCP anyways).
Go to Settings - Connectivity - Destinations - Internet - ESSID_OF_YOUR_WIFI - Options - Advanced Settings - IPv4 settings - DNS addresses and enter the IP Address of your DNS server (usually the address of your access point
After that it worked for me, setting the IP address of the phone by hand was not necessary.
Debian lenny - problem with keyboard in X / with xserver
After my dist-upgrade to Debian lenny setting the keyboard layout in
/etc/X11/xorg.conf didn't work (on the console everything was fine). Probably
this is related to the upgrade of the xkb-data package.
Lexmark E210 GDI printer + Netgear PS121 printserver
I wanted to have a small network print server in my LAN so I could switch off
the computer the printer was connected to before.
I bought the printserver, connected it to my LAN and ran the Setup-Program in windows. It found the printserver without problems and I assigned a fixed IP-adress.
Then I added a new (local) printer and chose the printer-share (LAN-Manager Printer Interface) of the printserver as the interface to be used. Then I finished the setup process and printed the test page - and it worked.
The other possibility is to use the IP-address as the interface instead of the
With Linux it is just as simple.
Some interesting links:
Omnibook XE3 GC hotkeys
Finally I upgraded my old laptop to Debian testing/lenny and kernel 2.6. So now I am using the great omnibook kernel module from http://omnibook.sourceforge.net/. Everything is working well, only the hotkeys took me some minutes' search and playing around.
The problem is that compared to the old kernel patches for kernel 2.4 you don't get the keycodes of the hotkeys directly to use them with the hotkeys package, instead you have to use setkeycodes (as root) first to map the scancodes.
The second and more severe problem is that keycodes higher than 240 cannot be used, so you cannot use the same keycodes as with kernel 2.4.
These are the error messages:
When you have loaded the omnibook module without setting any scancode/keycode (at least you see that the module works):
When you are setting scancodes/keycodes and use keycodes higher than 240:
Solution: use for example the following keycodes (check first with getkeycodes
wheter these keycodes are not use yet):
The keycodes used for hotkeys in the .def-file are the following (small blue
one touch keys from left to right):
Some interesting links:
Written 2007-02-07 - last update 2007-11-12
© echo date(Y); ?> by wf