Linux Newbie help
 help / color / mirror / Atom feed
From: Rohit Sarkar <rohitsarkar5398@gmail.com>
To: Hubert CHAUMETTE <hubert.chaumette@kolabnow.com>
Cc: Oliver Neukum <oneukum@suse.com>,
	linux-usb@vger.kernel.org, linux-newbie@vger.kernel.org
Subject: Re: Beginner query regarding usbhid
Date: Wed, 25 Mar 2020 22:43:07 +0530	[thread overview]
Message-ID: <5e7b9127.1c69fb81.f2f8b.582c@mx.google.com> (raw)
In-Reply-To: <b799aa1720fecb94d832264b4561eb8a@kolabnow.com>

On Wed, Mar 25, 2020 at 04:41:38PM +0100, Hubert CHAUMETTE wrote:
> Le 25/03/2020 15:47, Rohit Sarkar a écrit :
> > I was trying to mess around with the driver that drives my mouse. I
> > found out that it is usbhid. I then added a printk statement to the init
> > and exit function of usbhid.
> > I then compiled and installed the usbhid drivers. Post that I ran
> > `sudo modprobe -r usbhid` and `sudo modprobe usbhid` but couldnt observe
> > any logs in dmesg.
> > 
> > I am certain I am missing something fundamental. Could someone help me
> > with this.
> 
> Hi,
> 
> Did you check whether your module was effectively loaded with lsmod?
> What log level did you use in your printk statement? Depending on your
> system default loglevel your logs might not be printed. A quick fix
> would be to use one of the lowest levels (pr_emerg, but pr_err might
> suffice).
> Regards,

Hey,
I did check that module was loaded. And one of the signs was that my
mouse started working after insmod :).

I used printk(KERN_ALERT "some message") for logging. I also tried with
KERN_ERR but no luck. 

The command I used for building was "make -C /home/rohit/LINUX/kernels/staging  M=$(pwd)"
and for installing the modules: "sudo make -C /home/rohit/LINUX/kernels/staging  M=$(pwd) modules_install"
both were executed from the usbhid directory.
from the usbhid directory.
> Hubert Chaumette

Thanks,
Rohit

  reply	other threads:[~2020-03-25 17:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 13:42 Beginner query regarding usbhid Rohit Sarkar
     [not found] ` <5e7b5fbc.1c69fb81.cace7.7aa1-ATjtLOhZ0NVl57MIdRCFDg@public.gmane.org>
2020-03-25 14:45   ` Oliver Neukum
     [not found]     ` <1585147543.3831.8.camel-IBi9RG/b67k@public.gmane.org>
2020-03-25 14:47       ` Rohit Sarkar
     [not found]         ` <5e7b6f15.1c69fb81.d92d3.facb-ATjtLOhZ0NVl57MIdRCFDg@public.gmane.org>
2020-03-25 15:41           ` Hubert CHAUMETTE
2020-03-25 17:13             ` Rohit Sarkar [this message]
2020-03-25 21:40               ` Randy Dunlap
2020-03-26  5:31                 ` Rohit Sarkar
2020-03-26  6:07                   ` Randy Dunlap
2020-03-26  6:53                     ` Rohit Sarkar
     [not found]                     ` <fdc818d7-842c-cfef-3654-0478e74bfa73-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2020-03-26  7:34                       ` Rohit Sarkar
2020-03-26 16:02                         ` Randy Dunlap
2020-03-26 16:14                           ` Rohit Sarkar
     [not found]                             ` <5e7cd502.1c69fb81.2402c.714b-ATjtLOhZ0NVl57MIdRCFDg@public.gmane.org>
2020-03-26 16:16                               ` Randy Dunlap
2020-03-26 11:48                       ` Rohit Sarkar
2020-03-26 16:04                         ` Randy Dunlap

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=5e7b9127.1c69fb81.f2f8b.582c@mx.google.com \
    --to=rohitsarkar5398@gmail.com \
    --cc=hubert.chaumette@kolabnow.com \
    --cc=linux-newbie@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    /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