Quake on Linux

I always wanted to play Quake(2,3) on Linux. I like that game. I even bought a windows version of that game when I used to use windows earlier.

On, Yoper, DRI is working, so next obivious thing for me was to install quake(2, or 3). As I do not have that Windows quake2 game cd with me, I decided to install demo version of the game.

I downloaded quake2 demo, installed it and it complained about "default.cfg".

I thought when I just have to install a demo, why not try quake3 demo.

As I am totally new in Linux gaming. I started with a quake3 RPM package. Some rpm did not install because of unmet dependencies, while others were installed but gave some error starting. I think same "default.cfg" error. I was because I did not have pk0.pk3 file.

Then I searched some more and downloaded "linuxq3ademo-1.11-6.x86.gz.sh" which is 40+MB installation file for quake3 demo. After downloading the file, when I tried to run it, "Checksum Error".
UPDATE: check this post. He has something interesting to say aboout "checksum error"

I downloaded again(and again) from different servers (http://www.3dgamers.com/games/quake3arena/, http://www.bluesnews.com/files/idstuff/quake3/linux/linuxq3ademo.shtml etc.) using several download methods (ftp, http, wget, Kget ....), but all the files gave same error. I still wonder if all the linux demo available on the net for quake3 are corrupted files!!!

When I was just about to give up.
I thought of downloading windows version and running it with wine and guess what it worked :-)
Finding windows version of quake3 on the net was very easy. The command I used were as follows
#apt-get update
#apt-get install wine
#wine q3ademo.exe

wow Q3 installation started!!!!
After installation, to run quake3

#wine quake3

It works fine, without a flicker. Happy gaming.


Thank you
Alex (agd5f_NOSPAM@SPAMFREE_yahoo (d.o.t.) com)
Michaƫl (mgourlain_NOSPAM@SPAMFREE_carillion (d.o.t.) cica.fr)

for helping me out of libGL linking trap of glxinfo and glxgears...

# glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes

# glxgears
1522 frames in 5.0 seconds = 304.400 FPS
1877 frames in 5.0 seconds = 375.400 FPS
1878 frames in 5.0 seconds = 375.600 FPS
1875 frames in 5.0 seconds = 375.000 FPS
1848 frames in 5.0 seconds = 369.600 FPS
1845 frames in 5.0 seconds = 369.000 FPS

its so nice to see things working.

gotta go. have to play some games ;)

Setting up ACPI (with Custom DSDT) on Yoper

As I mentioned earlier, the default Yoper desktop is good enough but I had to setup ACPI because I need to compile custom DSDT specific to my laptop (custom DSDT creation method is described in detail at www.azeemarif.co.nr).

I could install kernel source from Yoper web-site, but I had saved the kernel source from my debian box. It is because, on debian box kernel source I had already applied
1) acpi patch (http://acpi.sourceforge.net/download.html)
This patch provides proper acpi support in kernel
2) acpi custom patch (http://www.behnel.de/acpi/acpi-custom-DSDT.patch)
This patch enables you to provide your custom DSDT table (see www.azeemarif.co.nr)

Also had already copied the DSDT hex file prepared by me for my laptop (Sens S830).

After copying that kernel source to /usr/src, I started compilation (make bzImage, make modules, make modules_install).

I installed the kernel manually because I am using Grub as boot loader which is not supported properly under Yoper (Yoper's default boot loader is LILO, yet).

Also I installed acpid (apt-get install acpid) from Yoper repositories. But there is no acpi client script on Yoper servers, so I downloaded an i686 RPM for acpi client script using www.rpmfinder.net.

After rebooting with new kernel, everything, yes almost everything stopped working. My network card, sound card, nothing was working.

The reason. Well, it was because I compiled all these things as loadable modules in my kernel while Yoper default kernel comes with everything compiled into kernel. So, there was no entry in /etc/modprobe.conf for loadable modules.

I used generate-modprobe.conf script that comes with new module init tools, to auto-generate modprobe.conf file.
generate-modprobe.conf /etc/modprobe.conf

Rebooted again and things started working fine :-)

Happy ending....

A word about "Yoper"

Yoper!! as claimed by the creator of Yoper, is I suppose, the fastest Linux distro out of the box.
Ok, I have not tried all the distros in the world, so I can not say "The Fastest", but It would not stop me from saying that it is the fastest out of the box among all the distros I have seen.

I have already described very briefly Yoper installation. After installation, you are presented with a fast, real fast, KDE desktop with a custom theme.

First thing you must do is
apt-get update
apt-get upgrade

Gnome does not come pre-installed. If you want to install Gnome, type
apt-get install Ygnome

The kernel I got with Yoper was For me, Network (e100 driver) and Sound (ESS maestro3 driver) was already setup.

Sax2 was automatically launched after installation for configuring X. So X was running fine.

So over all, its a very good desktop for a new Linux user. I think a new user will find most of her daily use utilities just some clicks away (and even those clicks are fast :-).

As for me, I wanted to make some changes to suit my laptop, highest priority being enabling ACPI support correctly. Though Yoper has ACPI enabled, my laptop's DSDT is broken. I have correct DSDT (as described at www.azeemarif.co.nr) but to incorporate this corrected DSDT in the system I have to compile the kernel again.

DRI installation file in Yoper does not work

in install.sh file set

DRV_NAME = savage
DRV_MODULE = savage
DRV_ARCH = i686

You need not change install script if you uncompress

first common tarball
second savage tarball

because savage tarball overwites common tarball and is already perfect.

Yoper Installation

Yoper installer is still very immature. it is text based and above this if you forget to give some option correctly, you have no way to come back and correct the mistake.

I read that Yoper does not support Grub in V2 installer. When it asked me to chose the partition to install boot loader, I just skipped.

Later, when I came to know that Yoper team has added Grub as boot loader (still default is LILO but you have an option to choose Grub as well), I could not come back and select the boot partition.

But what I liked at this moment of installation that Yoper team is very fast in fixing things. The review I read was about Yoper V2, and in Version 2.1 they had already fixed the problems mentioned about the installer in the review (Ok, not all the problems but at least the most visible one).

I realised that installer is not the strongest point of Yoper. Afterall, when you have as nice a Distro as Yoper, who cares what little problem you faced at installation time :-)

Go Yoper.

Swiped debian

I was more or less happy with debian (which was libranet in the beginning). As I upgraded to debian "unstable", I missed something the process and GTAG and anything depending on gkt started crashing.

I knew, I can fix this but I wanted to try Yoper, said to be the fastest distro out of the box (i686 optimized).

./a.out : permission denied

Sometimes, you download source of a utility, decompress it and run

it returns error

./a.out : permission denied

you try it manually (creating a a.out file and try running it) and face the same problem!!!

might be your partition is mounted with "noexec" option.......... Check it in /etc/fstab

DRI on S3 Savage IX/MX

Finally, after searching the net for months earlier and again this time for information on S3 Savage IX/MX, I'll be able to play games on my Linux box.

Without DRI, it was impossible to play games like tux-racer. The frame rate was too slow. I tried to enable DRI support earlier but could not succeed. I almost lost hope of playing games in Linux on my notebook.

This time I came across this wonderful post at www.linuxquestions.org.
Here people were discussing same problem, i.e. making S3 Savage have DRI support. I followed the instructions in post #40 and things went well without any errors. But still, DRI did not work. I checked the X log (/var/log/XFree86-0) and found the error
(II) SAVAGE(0): 9348 kB of Videoram needed for 3D; 8192 kB ofVideoramavailable

(EE) SAVAGE(0): Insufficient Videoram available for 3D

(EE) SAVAGE(0): Try a lower color depth or smaller desktop

I changed, default color depth to 16bpp and Wow, glxgears shows a frame rate of 160fps (in comparison to 38fps without dir).

During this process, I came across a webpage on DuoView (DuoVue) feature of S3 Savage video card.

I exchanged some mail with the author Alex (who is a wonderful person to reply to all my mails with accurate information) and he helped me to confirm my solution to enable DRI.

Thank you Alex.

ALSA - advanced linux sound architecture

Alsa was not working....

But making ALSA work was easy because I already had my earlier experience listed at www.azeemarif.co.nr

but this time it was easier ... just install correct packages

and run

thats it.

Laptop almost burnt (ACPI not working)

Last night I left my notebook open (running debian).... by the morning it was too hot to event touch it.

I checked acpi function and realized that it is not working properly.

It was not a surprise as I had gone through all this before.

All I needed to do was to read my own instructions from www.azeemarif.co.nr

write permissions for mounted ext3 filesystem

In words of an experienced user at Suse forum

> The permissions aren't set to the user when it's mounted, that is
> correct. ext3 stores the user permissions internally. You need to
> change the permissions of the disk when it's mounted, the same way
> you would any other file or directory. So, when the disk is
> mounted, do
> chmod 777 /mnt/fwdisk1/
> Note that the disk *has* to be mounted when you run this, otherwise
> it won't work

Captive NTFS


captive ntfs is wonderful. When it works, it works great.

but remember, don't forget to install and configure lufs.

The external usb harddisk's NTFS partition was showing up as /dev/sda5 (/dev/sda2 for whole HDD, I think, and /dev/sda5 for the first partition).

not only captive-ntfs fount all the windows ntfs partitions but also modified /etc/fstab to make them usable.