From owner-freebsd-questions@FreeBSD.ORG Tue Oct 17 17:57:54 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 7375716A407 for ; Tue, 17 Oct 2006 17:57:54 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 9CEFB43D49 for ; Tue, 17 Oct 2006 17:57:53 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 17 Oct 2006 17:57:52 -0000 Received: from vpn-cl-162-212.rz.uni-karlsruhe.de (EHLO [141.3.162.212]) [141.3.162.212] by mail.gmx.net (mp040) with SMTP; 17 Oct 2006 19:57:52 +0200 X-Authenticated: #5465401 Message-ID: <453519F6.8020502@gmx.de> Date: Tue, 17 Oct 2006 19:59:18 +0200 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5.0.7 (X11/20061015) MIME-Version: 1.0 To: usleepless@gmail.com References: <4533DA97.8060303@gmx.de> In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-questions@freebsd.org Subject: Re: kldunload -f has no effect X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Oct 2006 17:57:54 -0000 usleepless@gmail.com wrote: > Hi Kamikaze, > > On 10/16/06, [LoN]Kamikaze wrote: >> I need to 'kldunload -f drm' in order to go into suspend to ram with my >> thinkpad (suspend works fine with dri disabled). Unfortunately, >> despite the >> claims of the manpage the '-f' flag does not alter the behaviour of the >> kldunload tool. How do I get drm unloaded? > > are you sure you drm is loaded as a module instead of compiled into your > kernel? > Yes I'm certain, it's listed by kldstat after all. Also if I deactivate dri, it doesn't get loaded and I can suspend/resume just fine. If I suspend with dri enabled, the system resumes, but as soon as I switch back to X, X hangs (and shows random screen garbage). The rest of the system still works, though. I can ssh into the box and work on it, as if nothing happened. Only if I try to kill X, the whole system will stop responding.