How to get the debug log when insmod a driver module?

[Honghe Wu]

On version Android jb-x86:

We are developing a multi-touch driver, but the driver demo has some serious bug, and the kernel breakdown when the driver module was manually loaded.

Whereas Android-x86 has no `/var/log` directory, and the kernel breakdown. So how can we get the debug log?

Thanks!

[Michael Cunningham]

option 1)

   After booting into the GUI, connect a physical keyboard, and press Alt+F1, then issue the dmesg command; you will have to scroll through alot of random stuff, but what your looking for should be in there.

# dmesg | more

option 2)

   If you have a working network interface, on the build platform:

cd to the out/host/linux-x86/bin directory:

   $ cd ~/android-x86/out/host/linux-x86/bin

kill the previous connection (if any):

   $ ./adb kill-server

connect adb to your android device:

   $ ./adb connect 192.168.0.123 (replace with the ip of your android device; can be viewed with the netcfg command from the android device)

view the log.. usually VERY long, and un-informative.. exit with ctrl+c

   $ ./adb logcat

if the logcat doesn't have what you need, run a remote shell to your android device, and view the dmesg

   $ ./adb shell

   # dmesg | more

V/r,

Mike

[Masaki Muranaka]

Hi,
Option 3)
$ ./adb shell dmesg | more
As busybox's "more" is poor.

2013/9/16 Michael Cunningham <comm...@android-x86.org>:

> --
> You received this message because you are subscribed to the Google Groups
> "Android-x86" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-x86...@googlegroups.com.
> To post to this group, send email to andro...@googlegroups.com.
> Visit this group at http://groups.google.com/group/android-x86.
> For more options, visit https://groups.google.com/groups/opt_out.



--
--
Masaki Muranaka
Monami-ya LLC, Japan.

[Honghe Wu]

When insmod the multi-touch driver, the whole kernel shutdowns immediately, so I can not get the log of what happen when the driver is loading through `dmesg`.

Thanks.