blog.ikaika.org

While setting up OpenBSD on my PowerBook, I ran across a problem with GNOME. My mouse would work fine but the moment I tried to type something, key presses would not register and mouse clicks would no longer work. The caps lock lights still worked and I could ssh to the machine so it was not locked up. Restarting X with Ctrl-Alt-Backspace seemed to be the only way out. The problem was the same if GNOME was started from GDM or from startx. FVWM from startx worked fine, so it wasn't a hardware issue.
After much searching I finally stumbled upon a thread from OpenBSD's misc@ email list that matched my problem:
OpenBSD 4.6, powerpc, KDE, Gnome, XFCE play nicely?
The next email in the thread mentioned problems with XDM, and I too was also experiencing problems with GDM.
The third email pointed me to the right location for the solution, "the second parapgraph of /usr/X11R6/README" which states: To use xdm from rc.conf, it is necessary to disable /dev/ttyC0 in /etc/ttys, change t…

Here are some tips on getting a Drobo (tested with a 1st Generation Drobo) working with an Asus RT-N16 running DD-WRT.

DD-WRT's notes on the Asus RT-N16
First off, BACKUP your data on the Drobo. You'll probably need to change the partitions and reformat your Drobo.
It looks like DD-WRT 24 does not support GUID Partition Tables (GPT) which means you need to use a MBR partition table and you LUN size will be limited to 2TB. This was not really a problem in my case since the 1st Generation Drobo is restricted to a 2TB LUN.
I think the standard Drobo tools will use a GPT. To check if your Drobo has a GPT just run fdisk on the drobo
$ sudo fdisk -clu /dev/sdc
WARNING: GPT (GUID Partition Table) detected on '/dev/sdc'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdc: 2199.0 GB, 2199023185920 bytes
87 heads, 57 sectors/track, 866095 cylinders, total 4294967160 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
…