[nikto]

Ok after

Code:

sudo nano /etc/udev/rules.d/10-persistent-ir.rules

a very strange window appeared...
I pasted in the first of the 2 codes you proprosed but... I found it strange that you said:

And paste one of those lines at the end

because the window was totally empty as you can see here

So what you mean for "at the end"?
there must be something else in that window?
anyway ... I have not even figured out how to save after I've pasted the code .. beacuse it said to do "^0" to save and I have no idea what does it mean.. So I just shut the terminal..

Now in /etc/udev/rules.d/ directory I see 2 files
- 1 that is called .10-persistent-ir.rules.swp
- 1 that is called 10-persistent-ir.rules.save

If I open 10-persistent-ir.rules.save I can read only this:
KERNEL=="event*",ATTRS{phys}=="usb-0000:00:1d.3-1/input0", SYMLINK="/dev/input/myremote"
That is what I pasted. Is it ok?
if so, what should I do now?

p.s. I repeat that I thank you very much .. You are a saint. However, if you are tired of having to do all this trouble because of me and because of something so stupid .. I'll understand if you decide to stop. believe me it would be completely understandable.

[3dfx]

Maybe you should to it with the echo command (which pipes that line into the file) or easier, use WinSCP as you can edit files in Windows.
Rename that '10-persistent-ir.rules.save' file to '10-persistent-ir.rules'. Sorry, my fault. That file isn't there, you created it
Delete the '.swp' file.

No problem, we're trying to help each other out

[nikto]

Ok thanks again
To change the file name to 10-persistent-ir.rules and to delete the .swp file I simply used my file manager pcmanfm as root.
Sorry I don't know if is ok but I didn't undertand how to use WinSCP.
Maybe should I had to edit the files in remote from another Windows PC?
Now I have just one file in /etc/udev/rules.d/
its name is 10-persistent-ir.rules and inside it there is only this:

Code:

KERNEL=="event*",ATTRS{phys}=="usb-0000:00:1d.3-1/input0", SYMLINK="/dev/input/myremote"

Am I ready to go on?

[3dfx]

Worth a try
Now you have to run the commands regarding the udev from the how-to

[nikto]

Do you mean this?

Code:

udevadm info -a -p $(udevadm info -q path -n /dev/input/event3)

As I sad I'm completely lost, I'm follwing
this How-to: http://kodi.wiki/view/HOW-TO:Setup_Lirc
this How-to: http://kodi.wiki/view/HOW-TO:Set_up_an_M...l_in_Linux
and you... so when you say

the commands regarding the udev from the how-to

The only "udev something" I can find is only that. But I don't understand because I had already posted it in my #5 post
anyway that command gives me:

Code:

franz@ZAVAGLIO-PC:~$ udevadm info -a -p $(udevadm info -q path -n /dev/input/event3)

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/devices/pci0000:00/0000:00:1d.3/usb4/4-1/4-1:1.0/0003:1241:E000.0001/input/input5/event3':
    KERNEL=="event3"
    SUBSYSTEM=="input"
    DRIVER==""

  looking at parent device '/devices/pci0000:00/0000:00:1d.3/usb4/4-1/4-1:1.0/0003:1241:E000.0001/input/input5':
    KERNELS=="input5"
    SUBSYSTEMS=="input"
    DRIVERS==""
    ATTRS{name}=="HOLTEK     PC receiver "
    ATTRS{phys}=="usb-0000:00:1d.3-1/input0"
    ATTRS{properties}=="0"
    ATTRS{uniq}==""

  looking at parent device '/devices/pci0000:00/0000:00:1d.3/usb4/4-1/4-1:1.0/0003:1241:E000.0001':
    KERNELS=="0003:1241:E000.0001"
    SUBSYSTEMS=="hid"
    DRIVERS=="hid-generic"
    ATTRS{country}=="00"

  looking at parent device '/devices/pci0000:00/0000:00:1d.3/usb4/4-1/4-1:1.0':
    KERNELS=="4-1:1.0"
    SUBSYSTEMS=="usb"
    DRIVERS=="usbhid"
    ATTRS{authorized}=="1"
    ATTRS{bAlternateSetting}==" 0"
    ATTRS{bInterfaceClass}=="03"
    ATTRS{bInterfaceNumber}=="00"
    ATTRS{bInterfaceProtocol}=="01"
    ATTRS{bInterfaceSubClass}=="01"
    ATTRS{bNumEndpoints}=="01"
    ATTRS{supports_autosuspend}=="1"

  looking at parent device '/devices/pci0000:00/0000:00:1d.3/usb4/4-1':
    KERNELS=="4-1"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{authorized}=="1"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bDeviceClass}=="00"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bMaxPacketSize0}=="8"
    ATTRS{bMaxPower}=="100mA"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bNumInterfaces}==" 2"
    ATTRS{bcdDevice}=="235a"
    ATTRS{bmAttributes}=="a0"
    ATTRS{busnum}=="4"
    ATTRS{configuration}==""
    ATTRS{devnum}=="2"
    ATTRS{devpath}=="1"
    ATTRS{idProduct}=="e000"
    ATTRS{idVendor}=="1241"
    ATTRS{ltm_capable}=="no"
    ATTRS{manufacturer}=="HOLTEK"
    ATTRS{maxchild}=="0"
    ATTRS{product}=="    PC receiver "
    ATTRS{quirks}=="0x0"
    ATTRS{removable}=="unknown"
    ATTRS{speed}=="1.5"
    ATTRS{urbnum}=="21"
    ATTRS{version}==" 1.10"

  looking at parent device '/devices/pci0000:00/0000:00:1d.3/usb4':
    KERNELS=="usb4"
    SUBSYSTEMS=="usb"
    DRIVERS=="usb"
    ATTRS{authorized}=="1"
    ATTRS{authorized_default}=="1"
    ATTRS{avoid_reset_quirk}=="0"
    ATTRS{bConfigurationValue}=="1"
    ATTRS{bDeviceClass}=="09"
    ATTRS{bDeviceProtocol}=="00"
    ATTRS{bDeviceSubClass}=="00"
    ATTRS{bMaxPacketSize0}=="64"
    ATTRS{bMaxPower}=="0mA"
    ATTRS{bNumConfigurations}=="1"
    ATTRS{bNumInterfaces}==" 1"
    ATTRS{bcdDevice}=="0404"
    ATTRS{bmAttributes}=="e0"
    ATTRS{busnum}=="4"
    ATTRS{configuration}==""
    ATTRS{devnum}=="1"
    ATTRS{devpath}=="0"
    ATTRS{idProduct}=="0001"
    ATTRS{idVendor}=="1d6b"
    ATTRS{interface_authorized_default}=="1"
    ATTRS{ltm_capable}=="no"
    ATTRS{manufacturer}=="Linux 4.4.0-62-generic uhci_hcd"
    ATTRS{maxchild}=="2"
    ATTRS{product}=="UHCI Host Controller"
    ATTRS{quirks}=="0x0"
    ATTRS{removable}=="unknown"
    ATTRS{serial}=="0000:00:1d.3"
    ATTRS{speed}=="12"
    ATTRS{urbnum}=="25"
    ATTRS{version}==" 1.10"

  looking at parent device '/devices/pci0000:00/0000:00:1d.3':
    KERNELS=="0000:00:1d.3"
    SUBSYSTEMS=="pci"
    DRIVERS=="uhci_hcd"
    ATTRS{broken_parity_status}=="0"
    ATTRS{class}=="0x0c0300"
    ATTRS{consistent_dma_mask_bits}=="32"
    ATTRS{d3cold_allowed}=="0"
    ATTRS{device}=="0x27cb"
    ATTRS{dma_mask_bits}=="32"
    ATTRS{driver_override}=="(null)"
    ATTRS{enable}=="1"
    ATTRS{irq}=="16"
    ATTRS{local_cpulist}=="0-3"
    ATTRS{local_cpus}=="f"
    ATTRS{msi_bus}=="1"
    ATTRS{subsystem_device}=="0x2651"
    ATTRS{subsystem_vendor}=="0x1019"
    ATTRS{vendor}=="0x8086"

  looking at parent device '/devices/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""

franz@ZAVAGLIO-PC:~$

[3dfx]

I meant this:

Code:

/etc/init.d/udev reload
udevadm trigger

[nikto]

Ah ok sorry
I have launched that comand with root because it asked to do so.
I get this

Code:

franz@ZAVAGLIO-PC:~$ sudo -s
[sudo] password di franz:
root@ZAVAGLIO-PC:~# /etc/init.d/udev reload
root@ZAVAGLIO-PC:~# udevadm trigger
root@ZAVAGLIO-PC:~#

Is it ok?

[nikto]

Sorry I add more info
After that the guide says

There should now be a symbolic link in /dev/input/myremote

if I go to my /dev/input I see this

if I enter in the by-id folder I see this

if I enter in by-path folder I see this


what is the symbolic link that I have to work with?

[3dfx]

Seems that it didn't match the path, there should by "myremote" in there.
Try with:

Code:

KERNEL=="event*",ATTRS{phys}=="usb-0000:00:1d.3-1", SYMLINK="/dev/input/myremote"

Than again:

Code:

/etc/init.d/udev reload
udevadm trigger

[nikto]

I repeated the last passage because I discovered I wrote "event3*" instead of "event3"
But unfortunately no change in /dev/input ....
After that I have modified the 10-persistent-ir.rules with leafpad,
I deleted

Code:

KERNEL=="event3",ATTRS{phys}=="usb-0000:00:1d.3-1/input0", SYMLINK="/dev/input/myremote"

and entered

Code:

KERNEL=="event3",ATTRS{phys}=="usb-0000:00:1d.3-1", SYMLINK="/dev/input/myremote"

after that I entered

Code:

sudo -s

to enter as root and after I entered

Code:

/etc/init.d/udev reload
udevadm trigger

with this result:

Code:

franz@ZAVAGLIO-PC:~$ sudo -s
[sudo] password di franz:
root@ZAVAGLIO-PC:~# /etc/init.d/udev reload
root@ZAVAGLIO-PC:~# udevadm trigger
root@ZAVAGLIO-PC:~#

but my /dev/input doesen't change


I don't know what to do now.
Maybe the the problem is in the creation of the file [b]10-persistent-ir.rules [/ b] because I don't know if I did it in the right way...

[3dfx]

Not "event", use "event3*". That should be correct, test that please.

If not I'm not sure how to help further :/

[nikto]

I re-modified with leafpad the 10-persistent-ir.rules with

Code:

KERNEL=="event3*",ATTRS{phys}=="usb-0000:00:1d.3-1/input0", SYMLINK="/dev/input/myremote"

but no "myremote" appears inside /dev/input/
I re - re -modified with leafpad the 10-persistent-ir.rules with

Code:

KERNEL=="event3*",ATTRS{phys}=="usb-0000:00:1d.3-1", SYMLINK="/dev/input/myremote"

with same result....

Thank you anyway... I have really appreciated your help and your dedication. I can not understand why is so difficult to make Lirc works with my remote... because the remote work perfectly.

My last question is: you said my remote is not a MCE so can I ask you what is it? What's the name of these type of remotes?
Simply HID remote?