Quantcast

doubt Lirc and raspberry pi

classic Classic list List threaded Threaded
22 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

doubt Lirc and raspberry pi

gdbabu Krishnan
Hi,


I am working with LIRC for Raspberry pi, my lirc version is "lirc 0.9.39".

after i did  irrecord -d /dev/lirc0 ~/lircd.conf i can able to create 'irrecord-temp-xxxx" then i have change file name as lircd.conf then moved to "/etc/lirc" directory  after that i have restart my service.

then i gave "irw" command in terminal it does not response when i press button on remote.

i have already configure LIRC for raspberry pi by the help of Internet but now  i have build  image from buildroot so completely difference from that. 

it required any configuration? if it so help me to resolve my problem.



thank you

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: doubt Lirc and raspberry pi

Alec Leamas
Hi gdbabu (?)


On 02/06/16 15:16, gdbabu Krishnan wrote:
> Hi,
>
>
> I am working with LIRC for Raspberry pi, my lirc version is "lirc 0.9.39".

Really? What does lircd --version display?

>
> after i did  irrecord -d /dev/lirc0 ~/lircd.conf i can able to create
> 'irrecord-temp-xxxx" then i have change file name as lircd.conf then
> moved to "/etc/lirc" directory  after that i have restart my service.

irrecord-temp-xxxx is just a temporary file, it can't be used as
lircd.conf. If this file is present, something went wrong while running
irrecord. Could you please post the complete output from running
irrecord (preferably as a pastebin link or so).

> then i gave "irw" command in terminal it does not response when i
> press button on remote.

According to above, this is as expected....
>
> i have already configure LIRC for raspberry pi by the help of Internet
> but now  i have build  image from buildroot so completely difference
> from that.

The internet is pretty big, and there are a lot of advices out there
even on lirc. Not all of them are good. Have you found
http://lirc.org/html/configuration-guide.html?
>
> it required any configuration? if it so help me to resolve my problem.
>
>
It depends... the first step is to use mode2 as described in the guide
(above) to verify that you are using the correct --driver and usually
also --device.


Cheers!

--alec

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: doubt Lirc and raspberry pi

gdbabu Krishnan
In reply to this post by gdbabu Krishnan
Hi,

i have successfully create lircd.conf and move to /etc/lirc/ directory now 'irw" command working fine.

but it didn't create "eventx" in "/dev/input' directory,

in older version i have edited "hardware.conf" file following format it created 'eventx" in /dev/input"
# /etc/lirc/hardware.conf
#
# Arguments which will be used when launching lircd
LIRCD_ARGS="--uinput"

# Don't start lircmd even if there seems to be a good config file
# START_LIRCMD=false

# Don't start irexec, even if a good config file seems to exist.
# START_IREXEC=false

# Try to load appropriate kernel modules
LOAD_MODULES=true

# Run "lircd --driver=help" for a list of supported drivers.
DRIVER="default"
# usually /dev/lirc0 is the correct setting for systems using udev
DEVICE="/dev/lirc0"
MODULES="lirc_rpi"

# Default configuration files for your hardware if any
LIRCD_CONF=""
LIRCMD_CONF=""
 
it still working  remote as keyboard but in newer version(0.9.3) in /etc/lirc/ directory there is no "hardware.conf" file instead of that "lirc_option.conf" how to give
LIRCD_ARGS="--uinput"
i don't know how to configure this file for remote as keyboard.



could you help me to solve this problem,

thank you 

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: doubt Lirc and raspberry pi

Alec Leamas



On 03/06/16 17:09, gdbabu Krishnan wrote:
Hi,

i have successfully create lircd.conf and move to /etc/lirc/ directory now 'irw" command working fine.

Great!

I still wonder what version you are using. What does 'lircd --version' print?

but it didn't create "eventx" in "/dev/input' directory,
in older version i have edited "hardware.conf" file following format it created 'eventx" in /dev/input"

This is (was)  created by the kernel, not lirc. Since you seem to be using the default driver the /dev/input devices are not involved so this is just fine anyway.

# /etc/lirc/hardware.conf
#
# Arguments which will be used when launching lircd
LIRCD_ARGS="--uinput"

# Don't start lircmd even if there seems to be a good config file
# START_LIRCMD=false

# Don't start irexec, even if a good config file seems to exist.
# START_IREXEC=false


# Run "lircd --driver=help" for a list of supported drivers.
DRIVER="default"
# usually /dev/lirc0 is the correct setting for systems using udev
DEVICE="/dev/lirc0"
That is, you should set

driver = default
device = /dev/lirc0

in lirc_options.conf

# Try to load appropriate kernel modules
LOAD_MODULES=true

MODULES="lirc_rpi"

For now, the easiest path is that you load this manually using 'modprobe lirc_rpi' before starting lircd.
 
it still working  remote as keyboard but in newer version(0.9.3) in /etc/lirc/ directory there is no "hardware.conf" file instead of that "lirc_option.conf" how to give
LIRCD_ARGS="--uinput"

There is a commented line #uinput = ....  in lirc_options.conf. Change that to (or just add)

uinput = True


Cheers!

--alec



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: doubt Lirc and raspberry pi

gdbabu Krishnan
In reply to this post by gdbabu Krishnan
Hi,

LIRC version is "lircd 0.9.3a"

i have changed all configuration in "lirc_options.conf" and restart service but "irw" command did not print any thing when i press button on remote.

but when i commented #uinput =... in lirc_options.conf and restart my service "irw" command working fine.

 if i made any mistake please correct me.


Another doubt,

when i "dmesg" in older version LIRC with Raspberry pi i got this message

"input: lircd as /devices/virtual/input/input0"
 
but in newer version i didn't get that why?,

in older version LIRC and pi i just open the terminal and press button on remote that print what i allocate to each button.

how to get those thing in Newer version.


thank you,
 



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: doubt Lirc and raspberry pi

gdbabu Krishnan
In reply to this post by gdbabu Krishnan
HI,

LIRCD does not Forword the event to the uinput driver, i have changed in "lirc_option.conf" file

"uinput= True"  in  "/dev/input/" directory "event2" has been created after that i have restart lirc service then i have press button on my remote nothing happen

could you tell me how to debug uinput and LIRC

thank you,

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: doubt Lirc and raspberry pi

Alec Leamas


On 07/06/16 14:04, gdbabu Krishnan wrote:

> HI,
>
> LIRCD does not Forword the event to the uinput driver, i have changed
> in "lirc_option.conf" file
>
> "uinput= True"  in  "/dev/input/" directory "event2" has been created
> after that i have restart lirc service then i have press button on my
> remote nothing happen
>
> could you tell me how to debug uinput and LIRC
The first step is to get hold of your logs. I don't know what setup
syslog has on your box, but somewhere it's stored - it's nothing special
for lirc.

What you should do is to raise the loglevel to "debug" or even "trace"
and check the logs. It's a lot of output, but might give a hint. The
loglevel is also in lirc_options.conf. In the last 0.9.4 release it's
commented out and also misnamed to debug. The correct name is 'loglevel'.

I still need to  know your version. What does "lircd --version" print?

Cheers!

--alec

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: doubt Lirc and raspberry pi

gdbabu Krishnan
In reply to this post by gdbabu Krishnan
HI,

i already post lircd --version in my previous post.

lircd version is  "lircd 0.9.3a"



could you tell me how to  check log when i gave command in terminal "lircd -D, --loglevel trace2"

that shows the message      bad debug level:","  i thing i made mistake how to do this.


thank you,


------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: doubt Lirc and raspberry pi

gdbabu Krishnan
In reply to this post by gdbabu Krishnan
HI,

lircd version is  "lircd 0.9.3a" i am using


after startup finish log message from /var/log/message , i did gave irw command

Jan  1 00:03:15 buildroot lircd: Info: Initial device: /dev/lirc0
Jan  1 00:03:15 buildroot lircd: Info: Initial device: /dev/lirc0
Jan  1 00:03:15 buildroot lircd: Warning: Running as root
Jan  1 00:03:15 buildroot lircd: Info: Using remote: /home/pi/llircd.conf.
Jan  1 00:03:15 buildroot lircd: Notice: lircd(default) ready, using /var/run/lirc/lircd


after i have given irw command the log message output

Jan  1 00:03:15 buildroot lircd: Info: Initial device: /dev/lirc0
Jan  1 00:03:15 buildroot lircd: Info: Initial device: /dev/lirc0
Jan  1 00:03:15 buildroot lircd: Warning: Running as root
Jan  1 00:03:15 buildroot lircd: Info: Using remote: /home/pi/llircd.conf.
Jan  1 00:03:15 buildroot lircd: Notice: lircd(default) ready, using /var/run/lirc/lircd
Jan  1 00:04:02 buildroot lircd: Notice: accepted new client on /var/run/lirc/lircd
Jan  1 00:04:07 buildroot lircd: Info: removed client


could you tell me why lircd didn't forward to uinput, the uinput found in /dev/ directory 

thank you

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: doubt Lirc and raspberry pi

Alec Leamas


On 08/06/16 13:47, gdbabu Krishnan wrote:

> HI,
>
> lircd version is  "lircd 0.9.3a" i am using
>
>
> after startup finish log message from /var/log/message , i did gave
> irw command
>
> Jan  1 00:03:15 buildroot lircd: Info: Initial device: /dev/lirc0
> Jan  1 00:03:15 buildroot lircd: Info: Initial device: /dev/lirc0
> Jan  1 00:03:15 buildroot lircd: Warning: Running as root
> Jan  1 00:03:15 buildroot lircd: Info: Using remote: /home/pi/llircd.conf.
> Jan  1 00:03:15 buildroot lircd: Notice: lircd(default) ready, using
> /var/run/lirc/lircd
>
>
> after i have given irw command the log message output
>
> Jan  1 00:03:15 buildroot lircd: Info: Initial device: /dev/lirc0
> Jan  1 00:03:15 buildroot lircd: Info: Initial device: /dev/lirc0
> Jan  1 00:03:15 buildroot lircd: Warning: Running as root
> Jan  1 00:03:15 buildroot lircd: Info: Using remote: /home/pi/llircd.conf.
> Jan  1 00:03:15 buildroot lircd: Notice: lircd(default) ready, using
> /var/run/lirc/lircd
> Jan  1 00:04:02 buildroot lircd: Notice: accepted new client on
> /var/run/lirc/lircd
> Jan  1 00:04:07 buildroot lircd: Info: removed client
>
>
> could you tell me why lircd didn't forward to uinput, the uinput found
> in /dev/ directory
>
> thank you
>
That log didn't say much, you need to raise the loglevel.  In
lirc_options.conf, add a new line

loglevel = debug

Then restart lircd, start irw and push some buttons on the remote. Then
post the new log (if large, it probably is, please post a pastebin link
or so)


Cheers!

--alec

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: doubt Lirc and raspberry pi

gdbabu Krishnan
In reply to this post by gdbabu Krishnan
HI

this my pastebin link:    http://pastebin.com/N8mTguXc


------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: doubt Lirc and raspberry pi

gdbabu Krishnan
In reply to this post by gdbabu Krishnan
HI

after i did  all the step i got the following log message from /var/log/message file

Jan  1 00:00:02 buildroot syslog.info syslogd started: BusyBox v1.24.2
Jan  1 00:00:02 buildroot user.notice kernel: klogd started: BusyBox v1.24.2 (2016-06-08 09:02:20 IST)
Jan  1 00:00:02 buildroot user.info kernel: [    0.000000] Booting Linux on physical CPU 0x0
Jan  1 00:00:02 buildroot user.info kernel: [    0.000000] Initializing cgroup subsys cpuset
Jan  1 00:00:02 buildroot user.info kernel: [    0.000000] Initializing cgroup subsys cpu
Jan  1 00:00:02 buildroot user.info kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jan  1 00:00:02 buildroot user.notice kernel: [    0.000000] Linux version 4.4.8 (malar@malar-ubuntu) (gcc version 4.9.3 (Buildroot 2016.05-rc2-00003-g46f9454-dirty) ) #1 Wed Jun 8 11:18:43 IST 2016
Jan  1 00:00:02 buildroot user.info kernel: [    0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d
Jan  1 00:00:02 buildroot user.info kernel: [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Jan  1 00:00:02 buildroot user.info kernel: [    0.000000] Machine model: Raspberry Pi Model B Rev 2
Jan  1 00:00:02 buildroot user.info kernel: [    0.000000] cma: Reserved 8 MiB at 0x19000000
Jan  1 00:00:02 buildroot user.info kernel: [    0.000000] Memory policy: Data cache writeback
Jan  1 00:00:02 buildroot user.debug kernel: [    0.000000] On node 0 totalpages: 105472
Jan  1 00:00:02 buildroot user.debug kernel: [    0.000000] free_area_init_node: node 0, pgdat c087e1f8, node_mem_map d984dc00
Jan  1 00:00:02 buildroot user.debug kernel: [    0.000000]   Normal zone: 927 pages used for memmap
Jan  1 00:00:02 buildroot user.debug kernel: [    0.000000]   Normal zone: 0 pages reserved
Jan  1 00:00:02 buildroot user.debug kernel: [    0.000000]   Normal zone: 105472 pages, LIFO batch:31
Jan  1 00:00:02 buildroot user.debug kernel: [    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
Jan  1 00:00:02 buildroot user.debug kernel: [    0.000000] pcpu-alloc: [0] 0
Jan  1 00:00:02 buildroot user.info kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 104545
Jan  1 00:00:02 buildroot user.notice kernel: [    0.000000] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708.boardrev=0xe bcm2708.serial=0xf9580910 smsc95xx.macaddr=B8:27:EB:58:09:10 bcm2708_fb.fbswap=1 bcm2708.uart_clock=3
Jan  1 00:00:02 buildroot user.info kernel: [    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
Jan  1 00:00:02 buildroot user.info kernel: [    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Jan  1 00:00:02 buildroot user.info kernel: [    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Jan  1 00:00:02 buildroot user.info kernel: [    0.000000] Memory: 400012K/421888K available (6046K kernel code, 436K rwdata, 1836K rodata, 380K init, 726K bss, 13684K reserved, 8192K cma-reserved)
Jan  1 00:00:02 buildroot user.notice kernel: [    0.000000] Virtual kernel memory layout:
Jan  1 00:00:02 buildroot user.notice kernel: [    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
Jan  1 00:00:02 buildroot user.notice kernel: [    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
Jan  1 00:00:02 buildroot user.notice kernel: [    0.000000]     vmalloc : 0xda000000 - 0xff800000   ( 600 MB)
Jan  1 00:00:02 buildroot user.notice kernel: [    0.000000]     lowmem  : 0xc0000000 - 0xd9c00000   ( 412 MB)
Jan  1 00:00:02 buildroot user.notice kernel: [    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
Jan  1 00:00:02 buildroot user.notice kernel: [    0.000000]       .text : 0xc0008000 - 0xc07bacb0   (7884 kB)
Jan  1 00:00:02 buildroot user.notice kernel: [    0.000000]       .init : 0xc07bb000 - 0xc081a000   ( 380 kB)
Jan  1 00:00:02 buildroot user.notice kernel: [    0.000000]       .data : 0xc081a000 - 0xc08872c8   ( 437 kB)
Jan  1 00:00:02 buildroot user.notice kernel: [    0.000000]        .bss : 0xc08872c8 - 0xc093ce70   ( 727 kB)
Jan  1 00:00:02 buildroot user.info kernel: [    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Jan  1 00:00:02 buildroot user.info kernel: [    0.000000] NR_IRQS:16 nr_irqs:16 16
Jan  1 00:00:02 buildroot user.info kernel: [    0.000029] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 2147483647500ns
Jan  1 00:00:02 buildroot user.info kernel: [    0.000071] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns
Jan  1 00:00:02 buildroot user.info kernel: [    0.000169] bcm2835: system timer (irq = 27)
Jan  1 00:00:02 buildroot user.info kernel: [    0.000475] Console: colour dummy device 80x30
Jan  1 00:00:02 buildroot user.info kernel: [    0.000702] console [tty1] enabled
Jan  1 00:00:02 buildroot user.info kernel: [    0.000730] Calibrating delay loop... 697.95 BogoMIPS (lpj=3489792)
Jan  1 00:00:02 buildroot user.info kernel: [    0.060308] pid_max: default: 32768 minimum: 301
Jan  1 00:00:02 buildroot user.info kernel: [    0.060687] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan  1 00:00:02 buildroot user.info kernel: [    0.060717] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan  1 00:00:02 buildroot user.info kernel: [    0.061705] Disabling cpuset control group subsystem
Jan  1 00:00:02 buildroot user.info kernel: [    0.061755] Initializing cgroup subsys io
Jan  1 00:00:02 buildroot user.info kernel: [    0.061791] Initializing cgroup subsys memory
Jan  1 00:00:02 buildroot user.info kernel: [    0.061846] Initializing cgroup subsys devices
Jan  1 00:00:02 buildroot user.info kernel: [    0.061877] Initializing cgroup subsys freezer
Jan  1 00:00:02 buildroot user.info kernel: [    0.061906] Initializing cgroup subsys net_cls
Jan  1 00:00:02 buildroot user.info kernel: [    0.061992] CPU: Testing write buffer coherency: ok
Jan  1 00:00:02 buildroot user.info kernel: [    0.062070] ftrace: allocating 20601 entries in 61 pages
Jan  1 00:00:02 buildroot user.info kernel: [    0.174190] Setting up static identity map for 0x81c0 - 0x81f8
Jan  1 00:00:02 buildroot user.info kernel: [    0.176054] devtmpfs: initialized
Jan  1 00:00:02 buildroot user.info kernel: [    0.184101] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
Jan  1 00:00:02 buildroot user.info kernel: [    0.184637] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Jan  1 00:00:02 buildroot user.info kernel: [    0.186368] pinctrl core: initialized pinctrl subsystem
Jan  1 00:00:02 buildroot user.info kernel: [    0.187222] NET: Registered protocol family 16
Jan  1 00:00:02 buildroot user.info kernel: [    0.192563] DMA: preallocated 4096 KiB pool for atomic coherent allocations
Jan  1 00:00:02 buildroot user.info kernel: [    0.200669] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
Jan  1 00:00:02 buildroot user.info kernel: [    0.200698] hw-breakpoint: maximum watchpoint size is 4 bytes.
Jan  1 00:00:02 buildroot user.info kernel: [    0.200862] Serial: AMBA PL011 UART driver
Jan  1 00:00:02 buildroot user.info kernel: [    0.201267] 20201000.uart: ttyAMA0 at MMIO 0x20201000 (irq = 81, base_baud = 0) is a PL011 rev2
Jan  1 00:00:02 buildroot user.info kernel: [    0.201643] console [ttyAMA0] enabled
Jan  1 00:00:02 buildroot user.info kernel: [    0.202381] bcm2835-mbox 2000b880.mailbox: mailbox enabled
Jan  1 00:00:02 buildroot user.info kernel: [    0.243634] bcm2835-dma 20007000.dma: DMA legacy API manager at f2007000, dmachans=0x1
Jan  1 00:00:02 buildroot user.notice kernel: [    0.245935] SCSI subsystem initialized
Jan  1 00:00:02 buildroot user.info kernel: [    0.246289] usbcore: registered new interface driver usbfs
Jan  1 00:00:02 buildroot user.info kernel: [    0.246435] usbcore: registered new interface driver hub
Jan  1 00:00:02 buildroot user.info kernel: [    0.246643] usbcore: registered new device driver usb
Jan  1 00:00:02 buildroot user.info kernel: [    0.254101] raspberrypi-firmware soc:firmware: Attached to firmware from 2016-05-06 13:53
Jan  1 00:00:02 buildroot user.info kernel: [    0.281698] clocksource: Switched to clocksource timer
Jan  1 00:00:02 buildroot user.notice kernel: [    0.333368] FS-Cache: Loaded
Jan  1 00:00:02 buildroot user.info kernel: [    0.333787] CacheFiles: Loaded
Jan  1 00:00:02 buildroot user.info kernel: [    0.353474] NET: Registered protocol family 2
Jan  1 00:00:02 buildroot user.info kernel: [    0.354805] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
Jan  1 00:00:02 buildroot user.info kernel: [    0.354907] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
Jan  1 00:00:02 buildroot user.info kernel: [    0.355010] TCP: Hash tables configured (established 4096 bind 4096)
Jan  1 00:00:02 buildroot user.info kernel: [    0.355114] UDP hash table entries: 256 (order: 0, 4096 bytes)
Jan  1 00:00:02 buildroot user.info kernel: [    0.355152] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
Jan  1 00:00:02 buildroot user.info kernel: [    0.355522] NET: Registered protocol family 1
Jan  1 00:00:02 buildroot user.info kernel: [    0.356145] RPC: Registered named UNIX socket transport module.
Jan  1 00:00:02 buildroot user.info kernel: [    0.356171] RPC: Registered udp transport module.
Jan  1 00:00:02 buildroot user.info kernel: [    0.356183] RPC: Registered tcp transport module.
Jan  1 00:00:02 buildroot user.info kernel: [    0.356195] RPC: Registered tcp NFSv4.1 backchannel transport module.
Jan  1 00:00:02 buildroot user.info kernel: [    0.357326] hw perfevents: enabled with armv6_1176 PMU driver, 3 counters available
Jan  1 00:00:02 buildroot user.info kernel: [    0.358782] futex hash table entries: 256 (order: -1, 3072 bytes)
Jan  1 00:00:02 buildroot user.notice kernel: [    0.375189] VFS: Disk quotas dquot_6.6.0
Jan  1 00:00:02 buildroot user.info kernel: [    0.375585] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Jan  1 00:00:02 buildroot user.notice kernel: [    0.378370] FS-Cache: Netfs 'nfs' registered for caching
Jan  1 00:00:02 buildroot user.notice kernel: [    0.379788] NFS: Registering the id_resolver key type
Jan  1 00:00:02 buildroot user.notice kernel: [    0.379890] Key type id_resolver registered
Jan  1 00:00:02 buildroot user.notice kernel: [    0.379908] Key type id_legacy registered
Jan  1 00:00:02 buildroot user.info kernel: [    0.384242] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jan  1 00:00:02 buildroot user.info kernel: [    0.384661] io scheduler noop registered
Jan  1 00:00:02 buildroot user.info kernel: [    0.384698] io scheduler deadline registered
Jan  1 00:00:02 buildroot user.info kernel: [    0.385110] io scheduler cfq registered (default)
Jan  1 00:00:02 buildroot user.info kernel: [    0.387813] BCM2708FB: allocated DMA memory 59400000
Jan  1 00:00:02 buildroot user.info kernel: [    0.387890] BCM2708FB: allocated DMA channel 0 @ f2007000
Jan  1 00:00:02 buildroot user.info kernel: [    0.415606] Console: switching to colour frame buffer device 240x67
Jan  1 00:00:02 buildroot user.info kernel: [    1.456962] bcm2835-rng 20104000.rng: hwrng registered
Jan  1 00:00:02 buildroot user.info kernel: [    1.457300] vc-cma: Videocore CMA driver
Jan  1 00:00:02 buildroot user.info kernel: [    1.457324] vc-cma: vc_cma_base      = 0x00000000
Jan  1 00:00:02 buildroot user.info kernel: [    1.457338] vc-cma: vc_cma_size      = 0x00000000 (0 MiB)
Jan  1 00:00:02 buildroot user.info kernel: [    1.457349] vc-cma: vc_cma_initial   = 0x00000000 (0 MiB)
Jan  1 00:00:02 buildroot user.info kernel: [    1.457813] vc-mem: phys_addr:0x00000000 mem_base=0x1ec00000 mem_size:0x20000000(512 MiB)
Jan  1 00:00:02 buildroot user.info kernel: [    1.484153] brd: module loaded
Jan  1 00:00:02 buildroot user.info kernel: [    1.497056] loop: module loaded
Jan  1 00:00:02 buildroot user.info kernel: [    1.498313] vchiq: vchiq_init_state: slot_zero = 0xd9480000, is_master = 0
Jan  1 00:00:02 buildroot user.info kernel: [    1.500828] Loading iSCSI transport class v2.0-870.
Jan  1 00:00:02 buildroot user.info kernel: [    1.502312] usbcore: registered new interface driver smsc95xx
Jan  1 00:00:02 buildroot user.info kernel: [    1.502442] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Jan  1 00:00:02 buildroot user.warn kernel: [    1.703246] Core Release: 2.80a
Jan  1 00:00:02 buildroot user.warn kernel: [    1.703284] Setting default values for core params
Jan  1 00:00:02 buildroot user.warn kernel: [    1.703334] Finished setting default values for core params
Jan  1 00:00:02 buildroot user.warn kernel: [    1.903772] Using Buffer DMA mode
Jan  1 00:00:02 buildroot user.warn kernel: [    1.903802] Periodic Transfer Interrupt Enhancement - disabled
Jan  1 00:00:02 buildroot user.warn kernel: [    1.903815] Multiprocessor Interrupt Enhancement - disabled
Jan  1 00:00:02 buildroot user.warn kernel: [    1.903831] OTG VER PARAM: 0, OTG VER FLAG: 0
Jan  1 00:00:02 buildroot user.warn kernel: [    1.903933] Dedicated Tx FIFOs mode
Jan  1 00:00:02 buildroot user.warn kernel: [    1.904488] WARN::dwc_otg_hcd_init:1047: FIQ DMA bounce buffers: virt = 0xd9414000 dma = 0x59414000 len=9024
Jan  1 00:00:02 buildroot user.warn kernel: [    1.904531] FIQ FSM acceleration enabled for :
Jan  1 00:00:02 buildroot user.warn kernel: [    1.904531] Non-periodic Split Transactions
Jan  1 00:00:02 buildroot user.warn kernel: [    1.904531] Periodic Split Transactions
Jan  1 00:00:02 buildroot user.warn kernel: [    1.904531] High-Speed Isochronous Endpoints
Jan  1 00:00:02 buildroot user.warn kernel: [    1.904531] Interrupt/Control Split Transaction hack enabled
Jan  1 00:00:02 buildroot user.debug kernel: [    1.904569] dwc_otg: Microframe scheduler enabled
Jan  1 00:00:02 buildroot user.warn kernel: [    1.904658] WARN::hcd_init_fiq:413: FIQ on core 0 at 0xc0406cec
Jan  1 00:00:02 buildroot user.warn kernel: [    1.904681] WARN::hcd_init_fiq:414: FIQ ASM at 0xc0406fc8 length 36
Jan  1 00:00:02 buildroot user.warn kernel: [    1.904717] WARN::hcd_init_fiq:439: MPHI regs_base at 0xda098000
Jan  1 00:00:02 buildroot user.info kernel: [    1.904794] dwc_otg 20980000.usb: DWC OTG Controller
Jan  1 00:00:02 buildroot user.info kernel: [    1.904863] dwc_otg 20980000.usb: new USB bus registered, assigned bus number 1
Jan  1 00:00:02 buildroot user.info kernel: [    1.904943] dwc_otg 20980000.usb: irq 56, io mem 0x00000000
Jan  1 00:00:02 buildroot user.warn kernel: [    1.905008] Init: Port Power? op_state=1
Jan  1 00:00:02 buildroot user.warn kernel: [    1.905021] Init: Power Port (0)
Jan  1 00:00:02 buildroot user.info kernel: [    1.905471] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jan  1 00:00:02 buildroot user.info kernel: [    1.905501] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jan  1 00:00:02 buildroot user.info kernel: [    1.905521] usb usb1: Product: DWC OTG Controller
Jan  1 00:00:02 buildroot user.info kernel: [    1.905539] usb usb1: Manufacturer: Linux 4.4.8 dwc_otg_hcd
Jan  1 00:00:02 buildroot user.info kernel: [    1.905554] usb usb1: SerialNumber: 20980000.usb
Jan  1 00:00:02 buildroot user.info kernel: [    1.906791] hub 1-0:1.0: USB hub found
Jan  1 00:00:02 buildroot user.info kernel: [    1.906914] hub 1-0:1.0: 1 port detected
Jan  1 00:00:02 buildroot user.debug kernel: [    1.907866] dwc_otg: FIQ enabled
Jan  1 00:00:02 buildroot user.debug kernel: [    1.907891] dwc_otg: NAK holdoff enabled
Jan  1 00:00:02 buildroot user.debug kernel: [    1.907905] dwc_otg: FIQ split-transaction FSM enabled
Jan  1 00:00:02 buildroot user.debug kernel: [    1.907963] Module dwc_common_port init
Jan  1 00:00:02 buildroot user.info kernel: [    1.908556] usbcore: registered new interface driver usb-storage
Jan  1 00:00:02 buildroot user.info kernel: [    1.909066] mousedev: PS/2 mouse device common for all mice
Jan  1 00:00:02 buildroot user.info kernel: [    1.910287] bcm2835-cpufreq: min=700000 max=900000
Jan  1 00:00:02 buildroot user.info kernel: [    1.910720] sdhci: Secure Digital Host Controller Interface driver
Jan  1 00:00:02 buildroot user.info kernel: [    1.910741] sdhci: Copyright(c) Pierre Ossman
Jan  1 00:00:02 buildroot user.info kernel: [    1.911261] sdhost: log_buf @ d9413000 (59413000)
Jan  1 00:00:02 buildroot user.info kernel: [    1.991862] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
Jan  1 00:00:02 buildroot user.info kernel: [    1.992483] sdhci-pltfm: SDHCI platform and OF driver helper
Jan  1 00:00:02 buildroot user.info kernel: [    1.993118] ledtrig-cpu: registered to indicate activity on CPUs
Jan  1 00:00:02 buildroot user.info kernel: [    1.993310] hidraw: raw HID events driver (C) Jiri Kosina
Jan  1 00:00:02 buildroot user.info kernel: [    1.993628] usbcore: registered new interface driver usbhid
Jan  1 00:00:02 buildroot user.info kernel: [    1.993649] usbhid: USB HID core driver
Jan  1 00:00:02 buildroot user.info kernel: [    1.994506] Initializing XFRM netlink socket
Jan  1 00:00:02 buildroot user.info kernel: [    1.994579] NET: Registered protocol family 17
Jan  1 00:00:02 buildroot user.notice kernel: [    1.994825] Key type dns_resolver registered
Jan  1 00:00:02 buildroot user.info kernel: [    2.017411] registered taskstats version 1
Jan  1 00:00:02 buildroot user.info kernel: [    2.017795] vc-sm: Videocore shared memory driver
Jan  1 00:00:02 buildroot user.info kernel: [    2.017827] [vc_sm_connected_init]: start
Jan  1 00:00:02 buildroot user.info kernel: [    2.018889] [vc_sm_connected_init]: end - returning 0
Jan  1 00:00:02 buildroot user.info kernel: [    2.019567] of_cfs_init
Jan  1 00:00:02 buildroot user.info kernel: [    2.019736] of_cfs_init: OK
Jan  1 00:00:02 buildroot user.info kernel: [    2.020924] uart-pl011 20201000.uart: no DMA platform data
Jan  1 00:00:02 buildroot user.info kernel: [    2.021511] Waiting for root device /dev/mmcblk0p2...
Jan  1 00:00:02 buildroot user.warn kernel: [    2.059611] mmc0: host does not support reading read-only switch, assuming write-enable
Jan  1 00:00:02 buildroot user.info kernel: [    2.062050] mmc0: new high speed SDHC card at address 0002
Jan  1 00:00:02 buildroot user.info kernel: [    2.063148] mmcblk0: mmc0:0002 00000 7.32 GiB
Jan  1 00:00:02 buildroot user.info kernel: [    2.064827]  mmcblk0: p1 p2
Jan  1 00:00:02 buildroot user.warn kernel: [    2.111998] Indeed it is in host mode hprt0 = 00021501
Jan  1 00:00:02 buildroot user.err kernel: [    2.173624] EXT4-fs (mmcblk0p2): couldn't mount as ext3 due to feature incompatibilities
Jan  1 00:00:02 buildroot user.err kernel: [    2.183659] EXT4-fs (mmcblk0p2): couldn't mount as ext2 due to feature incompatibilities
Jan  1 00:00:02 buildroot user.info kernel: [    2.201273] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
Jan  1 00:00:02 buildroot user.info kernel: [    2.201398] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
Jan  1 00:00:02 buildroot user.info kernel: [    2.204386] devtmpfs: mounted
Jan  1 00:00:02 buildroot user.info kernel: [    2.205783] Freeing unused kernel memory: 380K (c07bb000 - c081a000)
Jan  1 00:00:02 buildroot user.info kernel: [    2.291829] usb 1-1: new high-speed USB device number 2 using dwc_otg
Jan  1 00:00:02 buildroot user.warn kernel: [    2.292102] Indeed it is in host mode hprt0 = 00001101
Jan  1 00:00:02 buildroot user.info kernel: [    2.461857] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro,data=ordered
Jan  1 00:00:02 buildroot user.info kernel: [    2.492502] usb 1-1: New USB device found, idVendor=0424, idProduct=9512
Jan  1 00:00:02 buildroot user.info kernel: [    2.492541] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jan  1 00:00:02 buildroot user.info kernel: [    2.493939] hub 1-1:1.0: USB hub found
Jan  1 00:00:02 buildroot user.info kernel: [    2.494137] hub 1-1:1.0: 3 ports detected
Jan  1 00:00:02 buildroot daemon.info kernel: [    2.766192] udevd[85]: starting version 3.1.5
Jan  1 00:00:02 buildroot user.info kernel: [    2.772181] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
Jan  1 00:00:02 buildroot user.notice kernel: [    2.802913] random: udevd urandom read with 68 bits of entropy available
Jan  1 00:00:02 buildroot user.info kernel: [    2.872706] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
Jan  1 00:00:02 buildroot user.info kernel: [    2.872753] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jan  1 00:00:02 buildroot user.info kernel: [    2.876408] smsc95xx v1.0.4
Jan  1 00:00:02 buildroot user.info kernel: [    2.964339] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-20980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:58:09:10
Jan  1 00:00:02 buildroot user.info kernel: [    3.041842] usb 1-1.2: new low-speed USB device number 4 using dwc_otg
Jan  1 00:00:03 buildroot user.info kernel: [    3.165200] usb 1-1.2: New USB device found, idVendor=413c, idProduct=2107
Jan  1 00:00:03 buildroot user.info kernel: [    3.165243] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan  1 00:00:03 buildroot user.info kernel: [    3.165263] usb 1-1.2: Product: Dell USB Entry Keyboard
Jan  1 00:00:03 buildroot user.info kernel: [    3.165285] usb 1-1.2: Manufacturer: Dell
Jan  1 00:00:03 buildroot user.info kernel: [    3.185431] input: Dell Dell USB Entry Keyboard as /devices/platform/soc/20980000.usb/usb1/1-1/1-1.2/1-1.2:1.0/0003:413C:2107.0001/input/input0
Jan  1 00:00:03 buildroot user.info kernel: [    3.243271] hid-generic 0003:413C:2107.0001: input,hidraw0: USB HID v1.10 Keyboard [Dell Dell USB Entry Keyboard] on usb-20980000.usb-1.2/input0
Jan  1 00:00:03 buildroot user.info kernel: [    3.321885] usb 1-1.3: new low-speed USB device number 5 using dwc_otg
Jan  1 00:00:03 buildroot user.info kernel: [    3.351491] lirc_dev: IR Remote Control driver registered, major 244
Jan  1 00:00:03 buildroot user.warn kernel: [    3.381558] lirc_rpi: module is from the staging directory, the quality is unknown, you have been warned.
Jan  1 00:00:03 buildroot user.info kernel: [    3.429099] usb 1-1.3: New USB device found, idVendor=04ca, idProduct=0061
Jan  1 00:00:03 buildroot user.info kernel: [    3.429143] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan  1 00:00:03 buildroot user.info kernel: [    3.429164] usb 1-1.3: Product: USB Optical Mouse
Jan  1 00:00:03 buildroot user.info kernel: [    3.429181] usb 1-1.3: Manufacturer: PixArt
Jan  1 00:00:03 buildroot user.info kernel: [    3.438281] input: PixArt USB Optical Mouse as /devices/platform/soc/20980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:04CA:0061.0002/input/input1
Jan  1 00:00:03 buildroot user.info kernel: [    3.446849] hid-generic 0003:04CA:0061.0002: input,hidraw1: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-20980000.usb-1.3/input0
Jan  1 00:00:03 buildroot user.info kernel: [    3.482373] bcm2835-wdt 20100000.watchdog: Broadcom BCM2835 watchdog timer
Jan  1 00:00:03 buildroot user.info kernel: [    3.528219] gpiomem-bcm2835 20200000.gpiomem: Initialised: Registers at 0x20200000
Jan  1 00:00:04 buildroot user.info kernel: [    4.351801] lirc_rpi: auto-detected active low receiver on GPIO pin 18
Jan  1 00:00:04 buildroot user.info kernel: [    4.352354] lirc_rpi lirc_rpi: lirc_dev: driver lirc_rpi registered at minor = 0
Jan  1 00:00:04 buildroot user.info kernel: [    4.352378] lirc_rpi: driver registered!
Jan  1 00:00:04 buildroot local0.info lircd-0.9.3a[112]: Info: Initial device: /dev/lirc0
Jan  1 00:00:04 buildroot local0.info lircd-0.9.3a[112]: Info: Initial device: /dev/lirc0
Jan  1 00:00:04 buildroot local0.warn lircd-0.9.3a[112]: Warning: Running as root
Jan  1 00:00:04 buildroot user.info kernel: [    4.799962] input: lircd as /devices/virtual/input/input2
Jan  1 00:00:04 buildroot local0.info lircd-0.9.3a[112]: Info: Using remote: /home/pi/llircd.conf.
Jan  1 00:00:04 buildroot local0.notice lircd-0.9.3a[112]: Notice: lircd(default) ready, using /var/run/lirc/lircd
Jan  1 00:00:04 buildroot user.info kernel: [    4.915395] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Jan  1 00:00:09 buildroot user.notice kernel: [    9.123568] random: nonblocking pool is initialized
Jan  1 00:00:13 buildroot daemon.info init: starting pid 143, tty '/dev/console': '/sbin/getty -L  console 0 vt100 '
Jan  1 00:00:13 buildroot daemon.info init: starting pid 144, tty '/dev/tty1': '/sbin/getty -L  tty1 0 vt100 '
Jan  1 00:00:18 buildroot auth.info login[144]: root login on 'tty1'
Jan  1 00:00:54 buildroot local0.notice lircd-0.9.3a[112]: Notice: accepted new client on /var/run/lirc/lircd
Jan  1 00:01:02 buildroot local0.info lircd-0.9.3a[112]: Info: removed client
Jan  1 00:01:04 buildroot user.info kernel: [   64.398525] usb 1-1.3: USB disconnect, device number 5
Jan  1 00:01:05 buildroot user.info kernel: [   65.911779] usb 1-1.3: new low-speed USB device number 6 using dwc_otg
Jan  1 00:01:05 buildroot user.info kernel: [   66.017690] usb 1-1.3: New USB device found, idVendor=04ca, idProduct=0061
Jan  1 00:01:05 buildroot user.info kernel: [   66.017731] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan  1 00:01:05 buildroot user.info kernel: [   66.017753] usb 1-1.3: Product: USB Optical Mouse
Jan  1 00:01:05 buildroot user.info kernel: [   66.017770] usb 1-1.3: Manufacturer: PixArt
Jan  1 00:01:05 buildroot user.info kernel: [   66.032677] input: PixArt USB Optical Mouse as /devices/platform/soc/20980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:04CA:0061.0003/input/input3
Jan  1 00:01:05 buildroot user.info kernel: [   66.035952] hid-generic 0003:04CA:0061.0003: input,hidraw1: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-20980000.usb-1.3/input0
Jan  1 00:01:19 buildroot local0.notice lircd-0.9.3a[112]: Notice: caught signal
Jan  1 00:01:19 buildroot local0.info lircd-0.9.3a[160]: Info: Initial device: /dev/lirc0
Jan  1 00:01:19 buildroot local0.info lircd-0.9.3a[160]: Info: Initial device: /dev/lirc0
Jan  1 00:01:19 buildroot local0.warn lircd-0.9.3a[160]: Warning: Running as root
Jan  1 00:01:19 buildroot local0.info lircd-0.9.3a[160]: Info: Using remote: /home/pi/llircd.conf.
Jan  1 00:01:19 buildroot local0.notice lircd-0.9.3a[160]: Notice: lircd(default) ready, using /var/run/lirc/lircd
Jan  1 00:01:19 buildroot user.info kernel: [   79.821858] input: lircd as /devices/virtual/input/input4
Jan  1 00:01:51 buildroot local0.notice lircd-0.9.3a[160]: Notice: accepted new client on /var/run/lirc/lircd
Jan  1 00:01:58 buildroot local0.info lircd-0.9.3a[160]: Info: removed client
Jan  1 00:02:06 buildroot user.info kernel: [  126.358950] usb 1-1.3: USB disconnect, device number 6
Jan  1 00:02:07 buildroot user.info kernel: [  127.871794] usb 1-1.3: new low-speed USB device number 7 using dwc_otg
Jan  1 00:02:07 buildroot user.info kernel: [  127.977479] usb 1-1.3: New USB device found, idVendor=04ca, idProduct=0061
Jan  1 00:02:07 buildroot user.info kernel: [  127.977523] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan  1 00:02:07 buildroot user.info kernel: [  127.977545] usb 1-1.3: Product: USB Optical Mouse
Jan  1 00:02:07 buildroot user.info kernel: [  127.977563] usb 1-1.3: Manufacturer: PixArt
Jan  1 00:02:07 buildroot user.info kernel: [  127.995847] input: PixArt USB Optical Mouse as /devices/platform/soc/20980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:04CA:0061.0004/input/input5
Jan  1 00:02:07 buildroot user.info kernel: [  127.997140] hid-generic 0003:04CA:0061.0004: input,hidraw1: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-20980000.usb-1.3/input0


thank you,

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: doubt Lirc and raspberry pi

Alec Leamas
In reply to this post by gdbabu Krishnan


On 09/06/16 07:13, gdbabu Krishnan wrote:
> HI
Hi!
>
> this my pastebin link: http://pastebin.com/N8mTguXc

Yes, but...  you have still only messages for the 'notice' level. You
need to raise the debug level to get more output from lircd - have you
set 'loglevel' in lirc_options.conf as I described in last message(s)?


Cheers!

--alec

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: doubt Lirc and raspberry pi

gdbabu Krishnan
In reply to this post by gdbabu Krishnan
HI

This is my " lirc_options.conf " still i got same log message


# These are the default options to lircd, if installed as
# /etc/lirc/lirc_options.conf. See the lircd(8) and lircmd(8)
# manpages for info on the different options.

[lircd]
nodaemon        = False
driver          = default
device          = /dev/lirc0
output          = /var/run/lirc/lircd
pidfile         = /var/run/lirc/lircd.pid
plugindir       = /usr/lib/lirc/plugins
permission      = 666
allow-simulate  = No
repeat-max      = 600
#effective-user =
#listen         = [address:]port
#connect        = host[:port]
#debug          =  6
uinput          = True
#release        = ...
#logfile        = ...
loglevel    = debug


[lircmd]
uinput          = False
nodaemon        = False

[modprobe]
modules         = lircd_rpi


why i could not get more log message from lirc

thank you

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: doubt Lirc and raspberry pi

Alec Leamas


On 09/06/16 13:10, gdbabu Krishnan wrote:

> HI
>
> This is my " lirc_options.conf " still i got same log message
>
>
> #debug          =  6
> uinput          = True
> #release        = ...
> #logfile        = ...
> loglevel    = debug
>
>
>
> why i could not get more log message from lirc
>
> thank you
>
I miss more pieces. How are you running lircd? From the command line? As
systemd service? Operating system?

Just a shot in the dark: Try adding also a line like

debug  = trace

I have a vague reminder there was something broken with the debug option
in 0ö.9.3a...


Cheers!

--alec

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: doubt Lirc and raspberry pi

gdbabu Krishnan
In reply to this post by gdbabu Krishnan
HI,

running lircd as systemd service,

This is my "lirc_options.conf"

# These are the default options to lircd, if installed as
# /etc/lirc/lirc_options.conf. See the lircd(8) and lircmd(8)
# manpages for info on the different options.

[lircd]
nodaemon        = False
driver          = default
device          = /dev/lirc0
output          = /var/run/lirc/lircd
pidfile         = /var/run/lirc/lircd.pid
plugindir       = /usr/lib/lirc/plugins
permission      = 666
allow-simulate  = No
repeat-max      = 600
#effective-user =
#listen         = [address:]port
#connect        = host[:port]
debug           = trace2
uinput          = True
#release        = ...
#logfile        = ...
loglevel    = debug


[lircmd]
uinput          = False
nodaemon        = False

[modprobe]
modules         = lirc_rpi


now debugging working, that command was working, i have checked step by step like trace, trace1, trace2.

The file link attached here 

http://pastebin.com/dQHPRdxt


Thank you,



------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: doubt Lirc and raspberry pi

gdbabu Krishnan
In reply to this post by gdbabu Krishnan
HI,


This is my new log message file

The file link attached here

 http://pastebin.com/bHVaCaY3


Thank you

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: doubt Lirc and raspberry pi

gdbabu Krishnan
In reply to this post by gdbabu Krishnan
HI,

what was problem in my log file,

I am waiting for your Replay,


thank you

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: doubt Lirc and raspberry pi

gdbabu Krishnan
In reply to this post by gdbabu Krishnan
HI,

This is my new  log message file link


http://pastebin.com/a4Tn6ieN


i have working with lirc last three week, still i didn't get output and also i don't know where the problem was created your help is very important for me.


Thank you,

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: doubt Lirc and raspberry pi

gdbabu Krishnan
In reply to this post by gdbabu Krishnan
HI sir,


still i am waiting for replay..

This is my log file link

http://pastebin.com/a4Tn6ieN

thank you,

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381
12
Loading...