Date: Fri, 5 Dec 2008 06:33:29 +0100 From: Mel <fbsd.questions@rachie.is-a-geek.net> To: freebsd-questions@freebsd.org Cc: Da Rock <rock_on_the_web@comcen.com.au> Subject: Re: FreeBSD 7.0 problems Message-ID: <200812050633.29979.fbsd.questions@rachie.is-a-geek.net> In-Reply-To: <1228416719.79750.25.camel@laptop2.herveybayaustralia.com.au> References: <1228356394.23645.24.camel@laptop1.herveybayaustralia.com.au> <200812040944.38210.fbsd.questions@rachie.is-a-geek.net> <1228416719.79750.25.camel@laptop2.herveybayaustralia.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 04 December 2008 19:51:59 Da Rock wrote:
<snip provided info>
> Why would I install a beta when I'm mainly interested in stable
> releases?
That's why I asked. You're not in a position to troubleshoot this problem,
since the usual suspects (wrong driver, signs of significant acpi problems)
don't apply and you'd have to really be willing to compile custom kernels,
set tunables and apply patches to get to the bottom of this.
The drm devices aren't created, and the reason for that is unclear. Nothing in
dmesg shows a failure.
The iwi problem could be signal strength, driver related or the fact that 7.0
uses SCHED_4BSD instead of the proven better working SCHED_ULE.
And when reporting bugs in the PR system, the first thing developers will ask
you is if you reproduce it on 7.1-BETA or a snapshot. Loads of fixes have
gone into the upcoming 7.1.
--
Mel
Problem with today's modular software: they start with the modules
and never get to the software part.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200812050633.29979.fbsd.questions>