Installation manual

16 4. Configuration of the Custom Kernel
Kernel configuration for VESA framebuffer:
—— Console Drivers ——
yes VGA text console
yes Video mode selection support
—— Frame−buffer support ——
yes Support for frame buffer devices
yes VESA VGA graphics console
VESA Video Modes:
Mode: LILO: Graphics: Text:
0x318 vga=792 1024x 768 128x48
0x31b vga=795 1280x1024 160x64
0x374 vga=884 1600x1200 200x74
Video mode confguration in /etc/lilo.conf:
image=/boot/vmlinuz
label=linux
read−only
vga=884
image=/boot/vmlinuz.old
label=backup
read−only
vga=normal
optional
4. 3. Radeon Framebuffer
Our graphic chip is an ATIMobility FireGL 7800,which seems to be quite similar to the ATIMobility M6 type
of chips. The card reports itself in /proc/pci as device 1002:4c58 (ATI Technologies Inc) (rev0).
Unfortunately,the ATIFireGL 7800 is not (yet) supported by the Linux Radeon Framebuffer.But with a little bit
of hacking, we can makeitso. In /usr/src/kernel-source-2.4.18/drivers/video/radeon.h we redefine the
RADEON_LWtype to our ID number and then reconfigure the kernel.
Kernel configuration for Radeon framebuffer support:
—— Console Drivers ——
yes VGA text console
yes Video mode selection support
—— Frame−buffer support ——
yes Support for frame buffer devices
yes ATI Radeon display support
Kernel hack in /usr/src/kernel-source-2.4.18/drivers/video/radeon.h:
#define PCI_DEVICE_ID_RADEON_LW 0x4c57 /* original */
#undef PCI_DEVICE_ID_RADEON_LW
#define PCI_DEVICE_ID_RADEON_LW 0x4c58 /* dirty hack */
4. 4. DRI (Direct Rendering Infrastructure)
Frankly we don’tknowwhether the fbdev or the patched radeon XFree86 servers really makeuse of the Direct
Rendering Infrastructure (DRI). Support for it does not hurt us, though.
Kernel Configuration:
—— Character Devices ——
yes /dev/agpgart (AGP Support)
yes Intel 440LX/BX/GX and i815/i830M/i840/i850 support
yes Direct Rendering Manager (XFree86 DRI support)