(At the risk of being a bit rude, I want to start the post by noting that I have no interest in running the open source Tux Racer or any of its ports. I'm thus not interested in hearing that this is a 20 year old program)

I'd like to specifically run 1.1 of Tux Racer, the finished commercial release of the program from 2000, shown here running on a (at the time of the video's posting) modern version of OpenSUSE. But this version is infamously closed source, hence why forks of it are usually based on the free, open source, but not very good beta version of it. About three weeks ago I contacted the original developer asking if he was interested in making it open source, but he never got back to me, so I've chosen to continue to try and get the pre-built binary working. (Another side note: the Windows version doesn't run very stable in a Windows XP VM, and on wine it has weird sound issues + doesn't have all of the graphics options available, so I'm specifically looking to get the Linux version running.)

I actually solved the dependencies of it, by copying the dependencies the CD comes with into (I suppose I'll find out later if this was a bad idea, but it seems their modern counterparts are stored in ), and then filling in the rest through and . The problem is launching the game, which results in a segmentation fault. Looking up the segmentation fault in relation to 32-bit programs on 64-bit Linux, a proposed solution was to set to 0 in , but the error persists.

Without access to the source or any knowledge of debugging tools, I'm not sure what the problem could be, so I was hoping somebody here could guide me to getting this program working? My last resort would be visualizing an older Linux distro or AntiX, but given that I've supposedly seen it run on a somewhat modern distro I'd love to see it working natively. Thank you.

Hello, ioi_xd & welcome to LQ.

I think you may well find out there's trouble ahead.

If this is a 20 year old game, you need to know that kernel changes around 2004 converted linux to a fully contiguous model, and away from the fixed I/O adresses and A20 handler used in Dos. That may cause problems.

There is also the fact that all libraries will be 32 bit and you have a 64 bit system. So when tux wants/lib/ld-linux.so (which every program uses), it wants a 32bit version. When your system wants/lib/ld-linux.so, it wants 64 bit version and 32 ≠ 64! You will need a 32bit OS, or a multilib system. They are some obvious failings.

When you post in future post program logs. A simple command like will catch the output to stdout in a file in your home dir every time, and you can post the juicy bits so we can see how you're getting on. Don't post big files without reading them. Why should we read them if you won't?

Debian - amd64: The 'Tux Racer' package name is extremetuxracer
https://packages.debian.org/search?s...rds=extremetux

The game runs OK.

-

No. The OP asks about the commercial version which does not have a lot in common with its open-source incarnations. I remember to have installed it quite simply on a Linux-machine, but by following a routine layed-out in detail... there must be an easy way, like with dpkg -i or alienate for RPM or something like an install-script...

I do not remember. But copying libraries by hand to anywhere was *not* part of the procedure. A structured approach to problem-solving should precede the discussion.

[deleted my link to the 0.61 installation – same error on my side ]

I wouldn't go that far.
I looked at the video; it has a lot in common with the extremetuxracer (etr) I tried on my machine, but I can see how it has different tracks and looks generally more polished and fun.

Okay. A complete re-write which approached sufficiently the original free version. Writing tracks for the commercial tuxracer was however a chore, compared to the simplicity of combining a few image-files for 0.61.