From: Antoine Martin <antoine@nagafix.co.uk>
To: gentoo-amd64@lists.gentoo.org
Cc: mhaney@ercbroadband.org
Subject: Re: [gentoo-amd64] dmesg output
Date: Tue, 09 Oct 2007 20:34:08 +0100 [thread overview]
Message-ID: <470BD7B0.50806@nagafix.co.uk> (raw)
In-Reply-To: <470B5FA0.3080405@skynet.be>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Cédric Godin wrote:
> Mark Haney wrote:
>> I must be an idiot. I've been asked several times for dmesg output,
>> so, in my debugging interest I try to provide that, but I only seem to
>> get the USB mouse input message in it like this:
>>
>> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 18
[snip]
>> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
>>
>>
>> I've never encountered this before, so how do I get rid of that?
>> Note, I've had to compile my USB as a module so that my synaptics
>> mouse pad on my laptop to work. I know it's related to that, but is
>> there a way to NOT have that in dmesg?
>>
>>
> deactivate event debugging ?
>
> Symbol: INPUT_EVBUG [=n]
> Prompt: Event debugging
> Defined at drivers/input/Kconfig:148
> Depends on: !S390 && INPUT
> Location:
> -> Device Drivers
> -> Input device support
> -> Generic input layer (needed for keyboard, mouse, ...)
> (INPUT [=n])
>
Or if you don't want to rebuild the kernel, just remove evbug.ko
(assuming you built it as a module)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHC9ewGK2zHPGK1rsRCixfAJ97eyK8CSc1zCFibj3tLnl+PgcakgCfWylN
7csEepX3vTC7fg6g+35a1hk=
=Vood
-----END PGP SIGNATURE-----
--
gentoo-amd64@gentoo.org mailing list
prev parent reply other threads:[~2007-10-09 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 22:02 [gentoo-amd64] dmesg output Mark Haney
2007-10-09 11:01 ` Cédric Godin
2007-10-09 19:34 ` Antoine Martin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=470BD7B0.50806@nagafix.co.uk \
--to=antoine@nagafix.co.uk \
--cc=gentoo-amd64@lists.gentoo.org \
--cc=mhaney@ercbroadband.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox