Performance and mouse problems
doug at fledge.watson.org
Wed May 2 19:39:51 UTC 2012
On Wed, 2 May 2012, Jerome Herman wrote:
> On 02/05/2012 19:40, Jerry wrote:
>> On Wed, 2 May 2012 13:19:05 -0400 (EDT)
>> doug at safeport.com articulated:
>>> On Wed, 2 May 2012, Warren Block wrote:
>>>> On Wed, 2 May 2012, Albert Shih wrote:
>>>>> I think the problem is indeed comme from Xorg.
>>>> Just to repeat: on this Gateway notebook, only one or the other of
>>>> the touchpad or mouse would work until I enabled moused
>>>> in /etc/rc.conf. Now either or both work, including when the USB
>>>> mouse is connected after X starts.
>>> My experience corresponds with Warren's thoughts on this. I was
>>> running the exact levels of software on an old Dell 800Mhz desktop and
>>> new aDell laptop many many times faster, 4 cpu's etc, etc. HAL (which
>>> is well named I think) did not work very well on the laptop and I
>>> would lose the mouse and keyboard when I disabled the touchpad. On the
>>> Desktop HAL worked fine. The laptop (keyboard and mouse anyway) works
>>> fine without HAL.
>> HAL is now deprecated on GNU/Linux systems. Why it is still being kept
>> on life support in FreeBSD is the question that needs to be addressed.
>> This didn't just happen yesterday either. We continue to bump version
>> numbers yet fail to repair/replace crucial elements of the
>> operating system. What is even better, depending on whose forum you
>> choose to read, the problem is FreeBSD -- Linux -- Gnome -- KDE -- "The
>> Cat in the Hat" (no one has blamed Microsoft for this fiasco as far as
>> I know) yet the problem still exists. Since 2008, when HAL was being
>> deprecated, no one has properly addressed the problem. Everyone plays
>> the "blame game".
> Be carefull that Linux notion of "Deprecated" is not exactly on par with
> standard meaning of the term. ifconfig has been deprecated since 1999 in
> Linux, OSS since 2001. Both are still alive and kicking. So it might be that
> Linux will keep HAL for a while still.
I guess my comments were not clear. If something does not work for a particular
configuration, why use it? Given the 1000s of different BIOSs, PCs and the fact
that everything is written to work with windows, to expect no issues is not
realistic. My only point was/is if it does not work for your configuration, you
are not likely (in my experience) to be able to get it working without a pretty
good knowledge of fbsd, xorg and C. The handbook is very clear on how to
configure without HAL, so that should be the first thing to try.
More information about the freebsd-questions