Xorg mouse and massive error log messages problems
Just installed Xorg package from parkages-current hoping to get
environment containing all the fixes. Still have the no mouse curser
movement on xfce desktop.
Adding
Option AllowEmptyInput Off
statement to ServerLayout section of /etc/X11/xorg.conf
got the mouse curser moving.
But I still get the the mouse error messages in the X11 log.
{EE) xf86OpenSerial: Cannot open device /dev/psm0 Device busy.
(EE) PS/2 Mouse: cannot open input device
(EE) PreInit failed for input device PS/2 Mouse
(EE) config/hal: NewInputDeviceRequest failed
Is there some other correct solution?
I am receiving massive flooding of the Log file: /var/log/Xorg.0.log
with the follow messages
Xlib: extension Generic Event Extension missing on display :0.0.
Xlib: extension Generic Event Extension missing on display :0.0
I found a post in the questions archives where the person was saying
these messages are meaningless and can be ignored. It's not a problem
the ignore them, but my log get massive in size and consumes my free
disk space. I know i can configure to rotate the log at a given size.
But that is not the solution. I need to know how to stop these messages
from being issued in the first place.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg mouse and massive error log messages problems
Fbsd1 wrote:
Just installed Xorg package from parkages-current hoping to get
environment containing all the fixes. Still have the no mouse curser
movement on xfce desktop.
Adding
Option AllowEmptyInput Off
statement to ServerLayout section of /etc/X11/xorg.conf
got the mouse curser moving.
But I still get the the mouse error messages in the X11 log.
{EE) xf86OpenSerial: Cannot open device /dev/psm0 Device busy.
(EE) PS/2 Mouse: cannot open input device
(EE) PreInit failed for input device PS/2 Mouse
(EE) config/hal: NewInputDeviceRequest failed
Is there some other correct solution?
I am receiving massive flooding of the Log file: /var/log/Xorg.0.log
with the follow messages
Xlib: extension Generic Event Extension missing on display :0.0.
Xlib: extension Generic Event Extension missing on display :0.0
I found a post in the questions archives where the person was saying
these messages are meaningless and can be ignored. It's not a problem
the ignore them, but my log get massive in size and consumes my free
disk space. I know i can configure to rotate the log at a given size.
But that is not the solution. I need to know how to stop these
messages from being issued in the first place.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
freebsd-questions-unsubscr...@freebsd.org
Under xorg 7.4 you need to gave both dbus and hald running... as to the
error message there is not much you can do until every X app is upgraded
to support 7.4
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Xorg mouse and massive error log messages problems
Xorg 7.4 has some major problems on FreeBSD my Xorg shows my cards bios screen when booting but yeah you need dbus and hal running unless you add the option that is in /usr/ports/UPDATING to your ServerLayout ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Error in messages.
On Thu, 5 Feb 2004 18:58, Derrick MacPherson wrote: I started seeing this today: Feb 4 07:00:00 mail /kernel: (da1:ahc0:0:2:0): READ(10). CDB: 28 0 2 c 1 5f 0 0 10 0 Feb 4 07:00:00 mail /kernel: (da1:ahc0:0:2:0): MEDIUM ERROR info:20c0168 asc:11,0 Feb 4 07:00:00 mail /kernel: (da1:ahc0:0:2:0): Unrecovered read error sks:80,35 I umounted the disk, dumped it's contents to a spare disk. Can you suggest some tests for this drive, or should I just get it replaced? Manufacturers often provide downloadable software for evaluating the state of their drives. But you'll probably need an MS OS to run it. But it is pretty certain that you have a corrupt sector which is probably not repairable. The software might allow you to encourage the drive to remap this sector to a spare. An odd error report in normal operation might indicate just another random sector failure and there are many; but most are repeatedly read until a valid read is obtained and then an alternate sector is mapped in its place by the software/hardware in the drive itself. Frequently however the first reported error is an indicator of a failing drive. Test software can tell you the current state of the drive but is unlikely to be a safe indicator for the early occurence of further failures. Your best approach would depend on the value you put on the future integrity of the drive. If you were told that there was a 20% chance that your drive would deteriorate rapidly would you be prepared to trust your data to it, for the 80% chance that it will be OK. The 20/80% figures are of course just plucked out of the air - they may or may not be realistic in your case. My guess would be that if the drive ihas been in service for a few years the probability that it has reach its end of life is higher than 20%. Only in the case of a quite new drive that has shown no other signs of weakness would I possibly rate at less than 20%. Then how much is your time worth to spend it on exhaustive testing. Drives are really rather cheap. I guess even for home use I would dump it without investing any more time. Malcolm ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Error in messages.
I started seeing this today: Feb 4 07:00:00 mail /kernel: (da1:ahc0:0:2:0): READ(10). CDB: 28 0 2 c 1 5f 0 0 10 0 Feb 4 07:00:00 mail /kernel: (da1:ahc0:0:2:0): MEDIUM ERROR info:20c0168 asc:11,0 Feb 4 07:00:00 mail /kernel: (da1:ahc0:0:2:0): Unrecovered read error sks:80,35 I umounted the disk, dumped it's contents to a spare disk. Can you suggest some tests for this drive, or should I just get it replaced? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Error in messages.
this reminds this newbie: is there any documentation on freebsd (system) error messages ? Derrick MacPherson wrote: I started seeing this today: Feb 4 07:00:00 mail /kernel: (da1:ahc0:0:2:0): READ(10). CDB: 28 0 2 c 1 5f 0 0 10 0 Feb 4 07:00:00 mail /kernel: (da1:ahc0:0:2:0): MEDIUM ERROR info:20c0168 asc:11,0 Feb 4 07:00:00 mail /kernel: (da1:ahc0:0:2:0): Unrecovered read error sks:80,35 I umounted the disk, dumped it's contents to a spare disk. Can you suggest some tests for this drive, or should I just get it replaced? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
