Section 5 (almost there!): Install Compiz-Fusion/Emerald If it does then we’re nearly there! If not, then check your Xorg log files for anything which looks broken, and google the problem. It should come back with “direct rendering: Yes”. Now restart your X-server (ctrl-alt-backspace), open up a console, and type the following: You’ll have to add in the following two sections to the end of the file… Option "LCDPort" "DFP_HIGHLOW" # This line is necessary to avoid the 'black screen' problem I always switch to runlevel 3 (text mode) before messing with my nf, as it makes it a lot easier to fix it if you screw up.ĭevice (modify the Driver line, don’t add a new one): This bit was the most time consuming for me, as there were an unholy number of problems I experienced trying to get the configuration right… Insert the following lines under the section named (if they’re not already there). Now… (as root)Ĭhmod +x config_x11r7 configure autogen.sh Now reboot, select NewKernel from the boot loader, and cross your fingers! Step 3: Compile the VIA xf86 driverįirst up, in a console, navigate to the folder in which you’ve got the driver tarball. Lilo -v # I always use the -c flag as well to speed up booting, but I can't guarantee it'll work for you. To install lilio use the following command (as root): Root = /dev/sda1 # Replace sda1 with your main HDD device nodeĪlso, it is essential that you have your current kernel as an entry in there as well… If anything goes wrong and you haven’t, you’ll be in for a world of hurt, er, fun… Yes, fun. In lilo, add these lines to your /etc/nf… Now set up your bootloader to boot from this kernel. Also, I have seen reports of the modules having the wrong read-permissions. On Slackware, this file needs to be in /usr/lib/modules/dri, and in Ubuntu (I have subsequently learned) in /usr/lib/dri. requires via_chrome9_dri.so to be installed, so if you can’t find it, just rip the file from the “”, downloadable from here. I had to find where it was installed and move it to /usr/lib/modules/dri. Something to note is that the kernel installed the via_chrome9_dri to the wrong location for Slackware for some reason. ext3, reiserfs) into your kernel, you don’t really need one though. As long as you’ve compiled support for your main filesystem (e.g. If you need an initrd you should create it now. When this finishes (it’ll take a good hour and a half), install the kernel with these commands (as root):Ĭp arch/x86/boot/bzImage /boot/vmlinuz-custom-2.6.24.7Ĭp System.map /boot/System.map-custom-2.6.24.7 Device Drivers –> Graphics Support –> Direct Rendering Manager –> Via unichrome9 video cards.Patch -p0 Graphics Support –> /dev/agpgart (AGP Support) –> VIA Chipset support Copy these files to the linux source folder and run the following commands: Now unpack the chrome9 patch tarball (GUI is easiest with this one, as the folder and file names are a pain to deal with in the console). On a console in the folder you’ve downloaded the kernel source to: A basic knowledge of how to compile and install a customised kernel.The xf86 VIA vga driver source from here.In this case I used 2.6.24.7 from I tried it with 2.6.26, but wasn’t able to get the via_chrome9 kernel module to compile, although it’s probably possible. This guide will outline the basics for compilation on Slackware 12.0, but it shouldn’t be too hard to port it to any other distro. With Via’s release a short while ago of OSS drivers for chrome9 cards, it’s now possible to have chrome9-powered Compiz-fusion on whichever distro you like! Officially they only support Ubuntu 8.04, but the source is readily available, so as long as you’re not scared of the command prompt (would you be using linux if you were? :P) you can compile your way to compiz-enabled beauty. Hey peeps, long time no see, and yes, you did read that right…
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |