Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Oct 2006 15:53:26 +0200
From:      "[LoN]Kamikaze" <LoN_Kamikaze@gmx.de>
To:        Nikos Vassiliadis <nvass@teledomenet.gr>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: kldunload -f has no effect
Message-ID:  <4534E056.60608@gmx.de>
In-Reply-To: <200610171031.51350.nvass@teledomenet.gr>
References:  <45338F10.2030006@gmx.de> <200610171031.51350.nvass@teledomenet.gr>

index | next in thread | previous in thread | raw e-mail

Nikos Vassiliadis wrote:
> On Monday 16 October 2006 16:54, [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.  
> 
> In my experience using -f will result in a kernel panic. And
> that's well documented in the manual page. I guess you are
> lucky it didn't work:) So, why don't you just reboot? and keep
> the module off your kernel(if that's an option).
> 
>> How do I get drm unloaded? 
> 
> The easy way, just reboot. Or the hard way, fix the kernel module!

What's the point of suspend if you have to reboot to resume?


home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4534E056.60608>