Alrighty... After a few days of hacking, I've learned a few things that might be useful. I'll be posting a few other bits and pieces shortly.
* Running X Windows *
I fiddled with the DNARD sources for a good bit. It's a mess. It's written for ARM32. If anyone gets it working, POST IT!
In the meantime, use the framebuffer device. Luckily, the WS has vesa bios extensions built in, so this is relatively easy.
The exact steps:
* Compile a new kernel with the fb enabled.
From 'make menuconfig', go to Console Drivers, and add:
- Support for frame buffer devices
- VESA VGA graphics console
- Advanced low level driver options
- 8 bpp packed pixels support
- 16 bpp packed pixels support
- 24 bpp packed pixels support
- 32 bpp packed pixels support
- Select compiled-in fonts
- VGA 8x8 font
- VGA 8x16 font
Note: the fonts are supposed to be optional
* Setup lilo.conf
Setup lilo.conf with "vga=ask" or the exact mode number you want. See Documentation/fb/vesafb.txt for mode numbers.
Note that the WS can do:
640x480 at 8-bit, 16-bit, 24-bit
800x600 at 8-bit, 16-bit
1024x786 at 8-bit
Run lilo (more likely plilo ;)
* Reboot to see the fb work
Note: vga=ask will NOT list the fun modes, for 800x600 at 16bit, use 0314
* Install XF86_FBDev and Configure X Windows
Install XF86_FBDev if it isn't installed. Make sure the /etc/X11/X is a symlink to XF86_FBDev
Exerpts from my /etc/X11/XF86Config:
Section "Device"
Identifier "Primary Card"
VendorName "Unknown"
BoardName "Unknown"
EndSection
Section "Screen"
Driver "FBDev"
Device "Primary Card"
Monitor "Generic Multisync"
Subsection "Display"
Depth 16
Modes "default"
ViewPort 0 0
EndSubsection
EndSection
Note: apparently you HAVE to tell it the color depth and it MUST match the mode you selected from lilo or boot. If anyone has a good idea for a work around to this, do tell.
* Run X Windows
Cross your fingers and 'startx'
Enjoy,
Gern
