1 (edited by fish 2015-10-10 19:44:36)

Topic: hunkmegs error on raspberry pi

hey,
i know this is a really special case, but im trying to run a coop server on a rpi.

if i start the server i get following error.

[quake3@alarmpi rtcw]$ ./rtcwcoopded.arm +map forest
RTCWCoop 1.0.2 linux-arm Oct 10 2015
----- FS_Startup -----
Current search path:
/home/quake3/.wolf/coopmain
/home/quake3/.wolf/main
./coopmain
./coopmain/bin.pk3 (14 files)
./coopmain/sp_pak_coop1.pk3 (658 files)
./main
./main/sp_pak4.pk3 (21 files)
./main/sp_pak3.pk3 (14 files)
./main/sp_pak2.pk3 (232 files)
./main/sp_pak1.pk3 (1342 files)
./main/pak0.pk3 (4775 files)
./main/mp_pak5.pk3 (77 files)
./main/mp_pak4.pk3 (5 files)
./main/mp_pak3.pk3 (76 files)
./main/mp_pak2.pk3 (3 files)
./main/mp_pak1.pk3 (308 files)
./main/mp_pak0.pk3 (783 files)

----------------------
8308 files in pk3 files
execing default.cfg
execing wolfconfig_ded.coop.cfg
couldn't exec autoexec.coop.cfg
Hunk_Clear: reset the hunk ok
Bypassing CD checks
logfile opened on Sat Oct 10 19:41:43 2015

--- Common Initialization Complete ---
IP: 127.0.0.1
IP: 195.93.242.155
IP6: ::1
IP6: fe80::ba27:ebff:fe02:cc8%eth0
Opening IP socket: 0.0.0.0:27960
------ Server Initialization ------
Server: forest
Hunk_Clear: reset the hunk ok
********************
ERROR: Hunk_Alloc failed on 301989888
********************
----- Server Shutdown (Server crashed: Hunk_Alloc failed on 301989888) -----
---------------------------


the iortcw server for example runs fine without errors.

[quake3@alarmpi rtcw]$ ./iowolfded.arm +map mp_beach +set sv_pure 0
iortcw 1.42d linux-arm Oct 10 2015
----- FS_Startup -----
Current search path:
/home/quake3/.iortcw/main
./main
./main/mp_pak5.pk3 (77 files)
./main/mp_pak4.pk3 (5 files)
./main/mp_pak3.pk3 (76 files)
./main/mp_pak2.pk3 (3 files)
./main/mp_pak1.pk3 (308 files)
./main/mp_pak0.pk3 (783 files)
./main/pak0.pk3 (4775 files)

----------------------
6027 files in pk3 files
execing default.cfg
execing wolfconfig_server.cfg
couldn't exec autoexec.cfg
Hunk_Clear: reset the hunk ok
Bypassing CD checks
--- Common Initialization Complete ---
IP: 127.0.0.1
IP: 195.93.242.155
IP6: ::1
IP6: fe80::ba27:ebff:fe02:cc8%eth0
Opening IP socket: 0.0.0.0:27960
------ Server Initialization ------
Server: mp_beach
Hunk_Clear: reset the hunk ok
----- FS_Startup -----
Current search path:
/home/quake3/.iortcw/main
./main
./main/mp_pak5.pk3 (77 files)
./main/mp_pak4.pk3 (5 files)
./main/mp_pak3.pk3 (76 files)
./main/mp_pak2.pk3 (3 files)
./main/mp_pak1.pk3 (308 files)
./main/mp_pak0.pk3 (783 files)
./main/pak0.pk3 (4775 files)

----------------------
6027 files in pk3 files
couldn't exec mapcfgs/mp_beach.cfg
Try loading dll file ./main/qagame.mp.arm.so
Loading DLL file: ./main/qagame.mp.arm.so
Sys_LoadGameDll(./main/qagame.mp.arm.so) found vmMain function at 0xa2461bdc
------- Game Initialization -------
gamename: main
gamedate: Oct 10 2015
------------------------------------------------------------
InitGame: \timelimit\10\sv_hostname\WolfHost\sv_maxclients\20\sv_minRate\0\sv_maxRate\0\sv_dlRate\100\sv_minPing\0\sv_maxPing\0\sv_floodProtect\1\g_friendlyFire\1\g_maxlives\0\g_voteFlags\255\g_antilag\0\g_maxGameClients\0\version\iortcw 1.42d linux-arm Oct 10 2015\com_gamename\wolfmp\com_protocol\61\g_gametype\5\g_gameskill\3\mapname\mp_beach\sv_privateClients\0\sv_allowAnonymous\0\g_minGameClients\8\g_axismaxlives\0\g_alliedmaxlives\0\gamename\main\g_redlimbotime\30000\g_bluelimbotime\30000\g_medicChargeTime\45000\g_engineerChargeTime\30000\g_LTChargeTime\40000\g_soldierChargeTime\20000\g_enableBreath\1
Gametype changed, clearing session data.
func_timer at (3244 2212 1384) has random >= wait
0 teams with 0 entities
24 items registered
-----------------------------------
broadcast: print "Server: timelimit changed to 8\n"
-----------------------------------
Hitch warning: 2731 msec frame time
Resolving dpmaster.deathmask.net (IPv4)
dpmaster.deathmask.net resolved to 107.161.23.68:27950
Sending heartbeat to dpmaster.deathmask.net
Resolving master.ioquake3.org (IPv4)
master.ioquake3.org resolved to 50.161.35.92:27950
Sending heartbeat to master.ioquake3.org
Resolving dpmaster.deathmask.net (IPv4)
dpmaster.deathmask.net resolved to 107.161.23.68:27950
Sending heartbeat to dpmaster.deathmask.net
Hitch warning: 2561 msec frame time

Re: hunkmegs error on raspberry pi

Thank you for reporting we will be resolved AND REPAIRS

Midu RTCW COOP
Server Admin

Re: hunkmegs error on raspberry pi

Your hunkmeg allocation indicates how much memory you've allocated to the game for it to use, Fish. Client-side, in Return to Castle Wolfenstein and Wolf ET, the basic setting was 56 hunkmegs, but this is now way out of date. We all set our hunkmegs in our configs to 512 now.

I'm sure that Fretn, Nate, Sage or MAN-AT-ARMS will help you with your RtCW Coop server problem.

Re: hunkmegs error on raspberry pi

do you use the same com_hunkmegs setting for both servers ?

5 (edited by fish 2015-10-13 14:17:02)

Re: hunkmegs error on raspberry pi

the iortcw server uses com_hunkMegs = "256", which is default there.

the rtcwcoop server seems to use 512, cause of this message "Hunk data failed to allocate 512 megs"
but if i start the rtcwcoop server with for exaple 256 i get the error i posted above on map load.

Re: hunkmegs error on raspberry pi

lower the 512 step by step, until you find a value that works smile

Re: hunkmegs error on raspberry pi

which is 277, but still

ERROR: Hunk_Alloc failed on 301989888
********************
----- Server Shutdown (Server crashed: Hunk_Alloc failed on 301989888) -----

Re: hunkmegs error on raspberry pi

I'm afraid it will not work then, unless I'm missing something, it's been a while smile

Re: hunkmegs error on raspberry pi

There's also other things to take into consideration too, Fish, like soundmegs and zonemegs. Soundmegs are self-explanitory, but zonemegs are related to the textures in maps and therefore have to be taken into consideration when running a server.

Try these settings:

seta com_hunkmegs "512"
seta com_soundmegs "192"
seta com_zonemegs "128"

Please also make sure, in compatibility mode, that you run the game as Administrator.

Re: hunkmegs error on raspberry pi

doesnt work. if i lower the hunkmegs, the server will crash.

Re: hunkmegs error on raspberry pi

Coop has higher requirements because it's loading the MP pk3's too.

Running on a original Raspberry Pi is probably not going work or will be unplayable.

RaspberryPi 2 may work somewhat but it wasn't really test with coop.

Re: hunkmegs error on raspberry pi

you can try by removing mp_pak5, and then mp_pak4 etc
but I cannot guarantee that everything will work as expected

Re: hunkmegs error on raspberry pi

MAN-AT-ARMS wrote:

Coop has higher requirements because it's loading the MP pk3's too.

Running on a original Raspberry Pi is probably not going work or will be unplayable.

RaspberryPi 2 may work somewhat but it wasn't really test with coop.

i tried it at my pi 1 at home, with zram swap and it works fine there, but you are right, rtcwcoop consumes much more hardware.