Connection issue in various Linux Native games. (Slackware 13.1 32-bit)

LSPena · 01-22-2011, 07:56 PM

Hello everyone in the LQ Forums i am experiencing a few connection issues under Slackware 13.1 and came here after lots of searching, and unsuccessful fixes so here it is.

- Problem: I can't join multiplayer matches in various games (Running natively in Linux) some of these are: Open Arena, Urban Terror, Cube 2: Sauerbraten, Quake Live and Planeshift.

- What i did: I tried joining multiplayer matches in these (and a few other) games without success, i get the server list, it says it is connecting and in most of these i get the message: Awaiting Gamestate (except for Planeshift which just fails and Cube 2 that doesn't show anything). Didn't find a fix in the internet and tried some possible ones without success. I even tried forwarding ports on my router/modem, turning on and off UPnP, setting up a firewall and nothing.

- Exceptions: I tried one of these games in my Windows XP 32-bit boot and the same game (Urban Terror) worked, same version number (but the native Windows version) and i could play without lag and any other issue. Cube 2: Sauerbraten manages to connect and lets me play (under Slack) but only on some servers maybe a port or authentication problem i guess.

As said the only message is Awaiting Gamestate in every game except for Cube 2 that doesn't show anything and just doesn't connects and Planeshift that says it wasn't able to reach the server.
This Slackware install is pretty fresh i installed it day 1 of January 2011 with the additional packages during the installation and the only firewall which i set up today was a IPTABLES one generated here but the issues are present since the day i installed Slack (but only in it) the problem persists with and without the firewall.

As far as i remember i didn't have these issues when i installed Ubuntu so i guess it's a configuration that's lacking. I am connected to the internet through a router (with wireless enabled for my notebook) with a cable (eth0), DHCP, Dynamic IP.

- Notes: I installed the PCMCIA thing during the installation and i CAN use the internet (browsing, pidgin, e-mail, youtube) normally.

Sorry if i wrote too much i tried to give as much information as possible and sorry for any grammar errors, English is not my first language.

Please bear in mind that I am new to this and so would appreciate being told in plain English what I need to do or where I need to start

Lucas

H_TeXMeX_H · 01-24-2011, 05:46 AM

What kernel are you using ? The huge install kernel, or generic. Make sure it's generic + initrd.

Disable ipv6.

LSPena · 01-25-2011, 10:01 AM

Ty for the answer, i think it is the huge but i'll check and take a look at disabling ipv6, although it would be nice if someone could help me with disabling ipv6.

EDIT:
I disabled ipv6 through the blacklist method which is adding the line "blacklist ipv6" to the blacklist.conf file inside /etc/modprobe.d/

I checked my kernel version (using the command uname -r) and it says it is kernel 2.6.33.4-smp
which i think it is the generic one as you mentioned.

H_TeXMeX_H · 01-25-2011, 12:05 PM

Does it work ?

Also, generic is not installed by default, the huge kernel is. Run 'ls /var/log/packages | grep kernel'.

LSPena · 01-25-2011, 03:10 PM

Well i tried running the programs and the issue still persists. Is there any way to check is ipv6 is really deactivated ?
Blacklist.conf is like this now:

Quote:

#
# Listing a module here prevents the hotplug scripts from loading it.
# Usually that'd be so that some other driver will bind it instead,
# no matter which driver happens to get probed first. Sometimes user
# mode tools can also control driver binding.

# IPV6 (Internet Protocol 6, comes enabled by default) support
blacklist ipv6

And then the rest of the file (which i didn't touch) and yeah, i added that ipv6 commentary.

I ran the command you told me and here are the results:

Quote:

kernel-firmware-2.6.33.4-noarch-1
kernel-generic-2.6.33.4-i486-1
kernel-generic-smp-2.6.33.4_smp-i686-1
kernel-headers-2.6.33.4_smp-x86-1
kernel-huge-2.6.33.4-i486-1
kernel-huge-smp-2.6.33.4_smp-i686-1
kernel-modules-2.6.33.4-i486-1
kernel-modules-smp-2.6.33.4_smp-i686-1
kernel-source-2.6.33.4_smp-noarch-1

H_TeXMeX_H · 01-26-2011, 12:44 PM

Yes, that is correctly blacklisted.

It looks like you have many kernels installed, just make sure you're booting generic + initrd, see /etc/lilo.conf or grub if you use it.

LSPena · 01-27-2011, 07:39 AM

How can i make Lilo boot generic + initrd ?

This is the content of my lilo.conf

Quote:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255

# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# End LILO global section
# Windows bootable partition config begins
other = /dev/sda1
label = Windows
table = /dev/sda
# Windows bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda3
label = Linux
read-only
# Linux bootable partition config ends

EDIT: I found something around the internet and in Linuxquestions.org but it seems to be pretty "dangerous" if you mess up with it so i'll wait for your answer. If you could help me change it and explain the changes and something you might find important about it and my problem (the causes the solution) i would appreciate (The purpose of installing Slackware is for learning Linux).

EDIT2: I ran ls -al on /boot and it showed this:

Quote:

total 22648
drwxr-xr-x 2 root root 4096 2008-12-30 22:28 ./
drwxr-xr-x 23 root root 4096 2011-01-24 01:16 ../
lrwxrwxrwx 1 root root 37 2008-12-30 22:17 README.initrd -> /usr/doc/mkinitrd-1.4.5/README.initrd
lrwxrwxrwx 1 root root 32 2008-12-30 22:17 System.map -> System.map-huge-smp-2.6.33.4-smp
-rw-r--r-- 1 root root 1282716 2010-05-13 02:00 System.map-generic-2.6.33.4
-rw-r--r-- 1 root root 1322225 2010-05-12 23:41 System.map-generic-smp-2.6.33.4-smp
-rw-r--r-- 1 root root 2041855 2010-05-13 02:28 System.map-huge-2.6.33.4
-rw-r--r-- 1 root root 2086543 2010-05-13 00:48 System.map-huge-smp-2.6.33.4-smp
-rw-r--r-- 1 root root 512 2008-12-30 22:28 boot.0800
-rw-r--r-- 1 root root 209 2008-12-30 22:28 boot_message.txt
lrwxrwxrwx 1 root root 28 2008-12-30 22:17 config -> config-huge-smp-2.6.33.4-smp
-rw-r--r-- 1 root root 108261 2010-05-13 02:00 config-generic-2.6.33.4
-rw-r--r-- 1 root root 108627 2010-05-12 23:41 config-generic-smp-2.6.33.4-smp
-rw-r--r-- 1 root root 108235 2010-05-13 02:28 config-huge-2.6.33.4
-rw-r--r-- 1 root root 108601 2010-05-13 00:48 config-huge-smp-2.6.33.4-smp
-rw-r--r-- 1 root root 5040 2010-02-16 18:44 diag1.img
-rw------- 1 root root 86016 2008-12-30 22:28 map
-rw-r--r-- 1 root root 14174 2010-02-14 23:57 slack.bmp
lrwxrwxrwx 1 root root 29 2008-12-30 22:17 vmlinuz -> vmlinuz-huge-smp-2.6.33.4-smp
-rw-r--r-- 1 root root 2545840 2010-05-13 02:00 vmlinuz-generic-2.6.33.4
-rw-r--r-- 1 root root 2662400 2010-05-12 23:41 vmlinuz-generic-smp-2.6.33.4-smp
-rw-r--r-- 1 root root 5243760 2010-05-13 02:28 vmlinuz-huge-2.6.33.4
-rw-r--r-- 1 root root 5421536 2010-05-13 00:48 vmlinuz-huge-smp-2.6.33.4-smp

It seems initrd isn't there, any other packages other than initrd are missing (I guess it was supposed to be in this folder) to make the transition to generic + initrd from huge ?
I guess these kernel-related packages can be found on the installation CD (I used a DVD), if so it will be easier to get them.

H_TeXMeX_H · 01-27-2011, 07:49 AM

Go into /boot and see what it's booting. It is booting /boot/vmlinuz, which is probably the huge.s kernel.

For initrd see:
http://alien.slackbook.org/dokuwiki/...ting_an_initrd

LSPena · 01-27-2011, 08:13 AM

vmlinuz points to huge:

Quote:

vmlinuz-huge-smp-2.6.33.4-smp

I'll check the link you sent about initrd

EDIT: I'm having some difficulties making initrd i would appreciate help in doing so (some kind of how-to), and about vmlinuz i'll have to simply change it to point to the generic kernel ?

So, setup initrd and change vmlinuz is all i'll need to change to generic + initrd ?

Thanks.

EDIT2:

So i guess i should run:

Quote:

mkinitrd -c -k 2.6.33.4 -m ext3 -f ext3 -r /dev/sda3/

I'm just not sure if my partition is ext3 or ext4, i can't remember. And Lilo says my Linux partition (I'm on dual boot with WXP) is on /dev/sda3/

And then change vmlinuz to point to:

Quote:

vmlinuz-generic-2.6.33.4

Run

Quote:

lilo

And that's it ?

LSPena · 01-28-2011, 08:19 AM

Sorry for the double post but i just noticed my partition is ext4 so all i should do is instead of running

Quote:

mkinitrd -c -k 2.6.33.4 -m ext3 -f ext3 -r /dev/sda3/

run

Quote:

mkinitrd -c -k 2.6.33.4 -m ext4 -f ext4 -r /dev/sda3/

Change vmlinuz to point to generic and run lilo and that's it ?

Do i have to load other modules like the nvidia drivers (im using the proprietary), sata or whatever ?

enorbet · 01-28-2011, 08:53 AM

Quote:

Originally Posted by LSPena

<snip>
Change vmlinuz to point to generic and run lilo and that's it ?

Hopefully, yes. As long as ext4 is checked as built-in at kernel level and not as a module you don;t need initrd. Personally I think initrd is an unnecessary pita on a DIY system.

Quote:

Originally Posted by LSPena

Do i have to load other modules like the nvidia drivers (im using the proprietary), sata or whatever ?

You need to rerun the nVidia installer to be certain the module is installed in /lib/modules/"generic-kernel-version". This also requires fully configured source in /usr/src/"generic-kernel-version" IIRC. So make sure each exists or you'll have to use "nv", "nouveau" or "vesa" in /etc/X11/xorg.conf to get to a DE.

Frankly, and I really hesitate to complicate this thread, but I don;t see why the kernel difference is going to allow a connection to a game server. It seems to me this is far more likely to be an iptables firewall issue where either UDP or more likely the port needed are blocked.

I play a number of native Linux games, especially ioquake3, which is nearly identical in networking to Open Arena. No kernel has ever prevented me from connecting or even running as a server which I do on one of my boxen. BTW, once you get comfortable with playing with kernels I'd highly recommend compiling your own so you can set it up at the very least at 1000Hz instead of the default 250 but best as total low latency kernel. The increase in snappiness and mouse accuracy is a huge return on investment and a major edge over windoze gamers, too.

allend · 01-28-2011, 08:58 AM

I suggest booting with the huge kernel and, as root:
1. 'cd /boot'
2. '/usr/share/mkinitrd/mkinitrd_command_generator.sh'
This will output a suitable line for mkinitrd that you can then execute.
3. Edit lilo as discussed in the link that H_TeXMeX_H gave.
4. '/sbin/lilo'

Note the lines in post#10 will not work. The ext4 file system also needs the jbd2 and mbcache kernel modules included in the initrd.

The modules that you need to boot are required to be in the initrd. Other kernel modules (e.g. nvidia) will be loaded as required.

bgeddy · 01-28-2011, 09:16 AM

Code:

Change vmlinuz to point to generic and run lilo and that's it ?

It's not a good idea to do that - leave the links as they are. I would recommend adding the lilo.conf entries for running the generic kernel but leaving the stanza for the huge kernel intact. That way you have a fall back to boot into if something goes wrong with your initrd.

LSPena · 01-28-2011, 10:05 AM

Quote:

It seems to me this is far more likely to be an iptables firewall issue where either UDP or more likely the port needed are blocked.

I'm not sure too but as far as i know Slack doesn't come in with a iptable firewall setup by default and i haven't setup one but maybe it can be.

Quote:

You need to rerun the nVidia installer to be certain the module is installed

You mean running the drivers again after i switch to generic to make it work if it's not installed to the generic kernel ?

Quote:

It's not a good idea to do that - leave the links as they are.

Yeah I'll leave them alone it's better and just edit lilo.conf

Quote:

I suggest booting with the huge kernel and, as root:
1. 'cd /boot'
2. '/usr/share/mkinitrd/mkinitrd_command_generator.sh'
This will output a suitable....

It's basically the same process right (the same result)? And those modules you mentioned are the only ones needed for a ext4 file system that I'll need to add to the initrd ?

Thanks guys

EDIT!:

Well until now PEBKAC is staying away.

I followed these steps

Quote:

I suggest booting with the huge kernel and, as root:
1. 'cd /boot'
2. '/usr/share/mkinitrd/mkinitrd_command_generator.sh'
This will output a suitable line for mkinitrd that you can then execute.
3. Edit lilo as discussed in the link that H_TeXMeX_H gave.
4. '/sbin/lilo'

I asked a question about the modules but the command gave me the proper line to execute (like allend said i just didn't notice =/)

It booted fine and by paying attention to the lines during the boot i could see that it booted generic now time to do some tests!

EDIT2:

Well i tested Cube 2, OpenArena and Quake live, well the problem persists on OpenArena and Quake live but in Cube 2 it's fine i either got lucky enough to try to connect on the servers that worked for me or they are all working =P.

Any other ideas ? iptables thing maybe ? (i'm still using generic + initrd)

LSPena · 01-30-2011, 10:53 AM

Well the problem persists, even in Cube 2: Sauerbraten (I was just lucky to join some servers i could connect).

Running iptables -L shows this:

Quote:

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

I think this means there's no iptables firewall setup.

Any help ? (I tried playing Savage XR and the problem is in there on the Awaiting State connection stage)