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

next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 17 October 2006 16:53, [LoN]Kamikaze wrote:
> 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?
> 
> 

none

as I did tell before "Or the hard way, fix the kernel module!"

or send a PR

HTH, Nikos




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