From owner-freebsd-questions@FreeBSD.ORG Wed Oct 6 03:31:20 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C057516A4CE for ; Wed, 6 Oct 2004 03:31:20 +0000 (GMT) Received: from mail.revolutionsp.com (ganymede.revolutionsp.com [64.246.0.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DA1B43D48 for ; Wed, 6 Oct 2004 03:31:20 +0000 (GMT) (envelope-from klr@6s-gaming.com) Received: from mail.revolutionsp.com (localhost [127.0.0.1]) by mail.revolutionsp.com (Postfix) with ESMTP id 89B3A15CD6 for ; Wed, 6 Oct 2004 00:28:15 +0000 (GMT) Received: from 81.84.174.8 (SquirrelMail authenticated user klr@6s-gaming.com); by mail.revolutionsp.com with HTTP; Wed, 6 Oct 2004 00:28:15 -0000 (GMT) Message-ID: <64337.81.84.174.8.1097022495.squirrel@81.84.174.8> Date: Wed, 6 Oct 2004 00:28:15 -0000 (GMT) From: "Hugo Silva" To: freebsd-questions@freebsd.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: DooM3 not working on FreeBSD 5.2.1-RELEASE :/ X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Oct 2004 03:31:20 -0000 Hi, I'm running into trouble trying to run the DooM3 beta on FreeBSD. The screen will stay gray for awhile and then my resolution will be messed up and the system mouseless (cursor won't move) - I can fix this by running Return to Castle Wolfenstein which will give back mouse control and reset resolution. I've digged a bit into the problem, but it's 4.30 AM and I can't think on anything else. Here's how the game stops: game initialized. -------------------------------------- -------- Initializing Session -------- session initialized -------------------------------------- Sys_MapCharForKey: doom key 43 -> keycode failed Sys_MapCharForKey: doom key 126 -> keycode failed --- Common Initialization Complete --- terminal support disabled pid: 36927 496 MB System Memory 64 MB Video Memory Async thread started signal caught: Aborted si_code 0 Trying to exit gracefully.. --------- Game Map Shutdown ---------- -------------------------------------- Shutting down sound hardware ----------- OSS Sound Shutdown ----------- unmap dma sound buffer close sound device ------------------------------------------ idRenderSystem::Shutdown() double fault Aborted, bailing out So it's obvious it's something to do with threading. This makes me think the game will only run on the 5.3 version.. which would be a major drawback for me as I don't plan to install 5.3 on my workstation (everything is working flawlessly, and the idea of upgrading the OS+nvidia drivers+all ports is not so nice..) A ktrace shows this: 36983 doom.x86 RET write 148/0x94 36983 doom.x86 CALL #175(0x2,0,0xbfbfdde8,0x8) 36983 doom.x86 RET #175 0 36983 doom.x86 CALL #179(0xbfbfdde8,0x8) 36983 doom.x86 RET #179 -1 errno -4 Unknown error: -4 36983 doom.x86 PSIG SIG(null) caught handler=0x28345e94 mask=0x80000000 code=0 36983 doom.x86 CALL #119(0xbfbfdaf8) 36983 doom.x86 RET #119 JUSTRETURN 36983 doom.x86 CALL old.sendmsg(0x9078,0,0x80000000,0) 36983 doom.x86 RET old.sendmsg 36984/0x9078 36983 doom.x86 CALL #91(0x2833a000,0x1000) 36983 doom.x86 RET #91 0 36983 doom.x86 CALL exit(0x6) So I'm pretty much out of ideas to make the game work.. Seems to be thread-related, dies with an unknown error. Any ideias ? Regards, Hugo