[gentoo-amd64] dmesg output

[gentoo-amd64] dmesg output

[Mark Haney]

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
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 18, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 31
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 31, Value: 1
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 31
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 31, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 34
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 34, Value: 1
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 34
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 34, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 28
evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 28, Value: 1
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?


-- 
Recedite, plebes! Gero rem imperialem!


Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415

Call (866) ERC-7110 for after hours support
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] dmesg output

[Cédric Godin]

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
> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 18, Value: 0
> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 31
> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 31, Value: 1
> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 31
> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 31, Value: 0
> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 34
> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 34, Value: 1
> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 34
> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 34, Value: 0
> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 0, Code: 0, Value: 0
> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 4, Code: 4, Value: 28
> evbug.c: Event. Dev: isa0060/serio0/input0, Type: 1, Code: 28, Value: 1
> 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])


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] dmesg output

[Antoine Martin]

-----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