Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Enemy Territory hard locks system, every time.
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gamers & Players
View previous topic :: View next topic  
Author Message
robet
l33t
l33t


Joined: 06 Sep 2004
Posts: 807
Location: Earth/NorthAmerica/USA/NY

PostPosted: Wed Jan 19, 2005 5:19 am    Post subject: Enemy Territory hard locks system, every time. Reply with quote

The title says most of it. Here's the output of strace -f -o et-etf.log:
Code:
11980 read(67, "\206=\0\0@\1P\1p\1\240\1\0\0\0\0\257\0\277\0\300\0\336"..., 48) = 48
11980 write(67, "\207\0\1\0", 4)        = 4
11980 read(67, "\1\0\r\0\0\0\0\0\2\0\2\0\0\0\0\0\220\363\377\277\177\0"..., 32) = 32
11980 write(2, "XFree86-VidModeExtension Activat"..., 47) = 47
11980 writev(67, [{0x54094205d8, 14437551851}, {0x15560bd1c, 2}, {0x1, 6153141450157278505}], 3) = 88
11980 read(67, 0xffffc748, 32)          = -1 EAGAIN (Resource temporarily unavailable)
11980 select(68, [67], NULL, NULL, NULL) = 1 (in [67])
11980 read(67, "", 32)                  = 0
11980 --- SIGHUP (Hangup) @ 0 (0) ---
11980 fstat64(0x1, 0xffffbc9c)          = 0
11980 --- SIGCONT (Continued) @ 0 (0) ---
11980 old_mmap(0x100000000000, 146028888067, PROT_READ|PROT_WRITE|PROT_EXEC|PROT_SEM|PROT_GROWSDOWN|PROT_GROWSUP|0xfcfffff0, 0x9 /* MAP_??? */, 1362$
11980 write(1, "Received signal 1, exiting...\n", 30) = -1 EIO (Input/output error)
11980 getpid()                          = 11980
11980 getpid()                          = 11980
11980 getpid()                          = 11980
11980 getpid()                          = 11980
11980 munmap(0x5cfc4000, 688128)        = 0
11980 munmap(0x5c854000, 1024)          = 0
11980 munmap(0x5d06c000, 4096)          = 0
11980 exit_group(0)                     = ?
I think I upgraded my emulation libs today, maybe I'll try a downgrade.
edit0: by "output" I mean the last bunch of lines of 48000.
edit1: glxgears works fine. Separately, is there a way to log the et verbosity (all the stuff about cl_*, hunk, initiliazing this and that)?
edit2: tuxracer works fine. The Xorg.0.log (things up to and including the "Could not init font path element..." are normal, and happen every time):
Code:
(II) Mouse1: ps2EnableDataReporting: succeeded
Could not init font path element /usr/share/fonts/local/, removing from list!
Could not init font path element /usr/share/fonts/CID/, removing from list!
Could not init font path element /usr/share/fonts/util/, removing from list!
SwitchToMode - scrn: 0 clock: 56300
               hdsp: 800 hbeg: 832 hend: 896 httl: 1048
               vdsp: 600 vbeg: 601 vend: 604 vttl: 631 flags: 5
Checking against clock: 157500 (157500)
                 hdsp: 1280 hbeg: 1344 hend: 1504 httl: 1728
                 vdsp: 1024 vbeg: 1025 vend: 1028 vttl: 1072 flags: 5
Checking against clock: 94500 (94500)
                 hdsp: 1024 hbeg: 1072 hend: 1168 httl: 1376
                 vdsp: 768 vbeg: 769 vend: 772 vttl: 808 flags: 5
Checking against clock: 56300 (56300)
                 hdsp: 800 hbeg: 832 hend: 896 httl: 1048
                 vdsp: 600 vbeg: 601 vend: 604 vttl: 631 flags: 5
(II) NVIDIA(0): Setting mode "800x600"
SwitchToMode - Succeeded

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Fatal server error:
Caught signal 11.  Server aborting


Please consult the The X.Org Foundation support
         at http://wiki.X.Org
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
edit3: disabled all the things I enabled/added in xorg.conf to get composite working, and et worked. I'm not sure if it was xcompmgr not running or the deletion of those options in xorg.conf that did it. If I don't post again within 1 minute it'll have been disabling the xorg.conf options that solved it, because I'll have still gotten the crash with xcompmgr and I'll leave the computer off afterwards.
Because I think that ^ was pretty unclear:
Code:
if (PostsWithin1) then problem=xcompmgr
else problem=xorg.conf options

_________________
no software patents in europe! | adopt an unanswered post.
Back to top
View user's profile Send private message
robet
l33t
l33t


Joined: 06 Sep 2004
Posts: 807
Location: Earth/NorthAmerica/USA/NY

PostPosted: Wed Jan 19, 2005 6:10 am    Post subject: Reply with quote

Well... it was a bit more than a minute, but no crash. I changed my xorg.conf so that the options were enabled again, but I forgot to kill xcompmgr when I started up X again. However, et worked fine. I don't get it... All of the fancy effects were enabled, and I've changed nothing since the last crash (afaik).
edit0: WAIT! I did change something. I altered the "video=" kernel boot parameter, from vesafb to vga944, because "video=vesafb" gave me something about probe failed -6. I guess that's the problem then.
_________________
no software patents in europe! | adopt an unanswered post.
Back to top
View user's profile Send private message
robet
l33t
l33t


Joined: 06 Sep 2004
Posts: 807
Location: Earth/NorthAmerica/USA/NY

PostPosted: Wed Jan 19, 2005 6:27 am    Post subject: Reply with quote

Nah, it was xcompmgr. I think. More to come. If anyone can tell me why running et with xcompmgr hardlocks the system... that'd be great!
_________________
no software patents in europe! | adopt an unanswered post.
Back to top
View user's profile Send private message
robet
l33t
l33t


Joined: 06 Sep 2004
Posts: 807
Location: Earth/NorthAmerica/USA/NY

PostPosted: Wed Jan 19, 2005 7:56 pm    Post subject: Reply with quote

Right now I start et-etpro with:
Code:
+ I "ETPRO" Exec aterm -e killall xcompmgr && et-etpro && xcompmgr [my startup options] &
Is killalling a process a safe thing to do, in general, and, more specifically, is killing xcompmgr safe?
_________________
no software patents in europe! | adopt an unanswered post.
Back to top
View user's profile Send private message
wolf31o2
Retired Dev
Retired Dev


Joined: 31 Jan 2003
Posts: 628
Location: Mountain View, CA

PostPosted: Wed Jan 19, 2005 11:21 pm    Post subject: Reply with quote

Composite is not really safe with OpenGL, which is why glx is disabled by default in the nvidia drivers when you use composite.

Turn off composite and I bet your problems go away.
_________________
Ex-Gentoo Developer
Catalyst/Genkernel Development Lead
http://wolf31o2.org
Back to top
View user's profile Send private message
robet
l33t
l33t


Joined: 06 Sep 2004
Posts: 807
Location: Earth/NorthAmerica/USA/NY

PostPosted: Thu Jan 20, 2005 12:25 am    Post subject: Reply with quote

Do you anticipate composite (ever) being safe with OpenGL? It's a pain to shut it down and start it up.
It's nice to know it wasn't really something I can control, though.
_________________
no software patents in europe! | adopt an unanswered post.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gamers & Players All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum