JP1 Remotes

[mathdon]

Some progress, but rather confusing results. With the line ending issue fixed and your files all installed, when I plug in the remote it creates the /media/REMOTE folder but it is empty and the remote is not mounted. I then unplugged the remote and tried to delete the REMOTE folder, but could not as I got a message that it is busy. After a restart, though, I could delete it.

I then deleted your file in /etc/udev/rules.d, plugged in the remote and did sudo sh mount_ofa in Terminal from the /usr/local/bin folder. That worked and RMIR could download the remote. Unplug the remote, it stays mounted. Do sudo sh umount_ofa and the unmount works.

So it appears that the rules file works and executes mount_ofa but that does not complete properly. However, both mount_ofa and umount_ofa work correctly when executed separately, which is why I describe the findings as confusing.

No more time for testing now, but hope to do more later in the day.
_________________
Graham

[davecs]

[mathdon]

[davecs]

/usr/local/bin is usually on the path, so you should be able to run the commands from anywhere. If you can run them without the "sh", and they work, they must be OK.

I'm about to install a test version of MX Linux, but what I'll do before that is to install Ubuntu 22.04 on the partition I was going to use, if it lets me do that without wanting to wipe the entire disk. Then I will try to see what the problem is. I'll have a go when I get the chance over the next few days.
_________________
URC7560/URC7562, URC8910, URC7980, URC6440/OARUSB04G and URC3661

[mathdon]

Yes, I find I can run sudo mount_ofa from anywhere, thanks.

I thought I had found the cause of my issues, but alas not. I have found where the /media/urc6440 folder comes from, and might have guessed it earlier if I knew more about Linux. There was an entry in /etc/fstab that I clearly added a long time ago from some previous forum post about the 6440 in Linux. I deleted that entry and the /media/6440 folder but the behaviour of your files is unchanged. If I plug in the remote, the /media/REMOTE folder is created but is empty and RMIR does not find the remote. The new info is that if I then unplug the remote without running sudo mount_ofa, the /media/REMOTE file is deleted, so umount_ofa is being run.

I understand that the "&" at the end of the lines in the rules file makes the commands run in the background. I wondered if this prevented the mount command from working properly, so I tested by deleting the second rule and the "&" at the end of the first one, but still the same behaviour. The REMOTE folder is created but is empty.
_________________
Graham

[mathdon]

SOLVED!!

I found the following link when searching to see if this was a problem experienced elsewhere:

Linux - mount command returns zero/o but not working

There is a quote in that from another source which reads:

[davecs]

[mathdon]

I have posted a draft for your comments of what I suggest for inclusion in the next RMIR release, It is a folder with full instructions that I hope will be more understandable than the web sources on which it is based.

Edit: Did you reboot after changing PrivateMounts?
_________________
Graham

[davecs]

[davecs]

The theoretical solution was test whether using systemd-mount in Ubuntu fared any better than mount, but alas, it did not. It might have been a case of writing a script with an outline:

mkdir /media/REMOTE
if systemd is running
then systemd-mount /dev/etc
else mount /dev/etc

And umount is replaced by systemd-mount -u

Not sure why Ubuntu hates me so much, I think it might be returning my feelings. An hour with the Unity desktop is enough to put me off computers for life.

But Mint Linux is derived from Ubuntu but uses the friendlier Cinnamon desktop so I might replace the Ubuntu partition with that, and test again.

Then I realised that MX-Linux can be booted using systemd or the traditional sysV-init. I never use the systemd boot up and mounting the remote always worked for me. I tried the alternate systemd bootup and of course the remote didn't mount! I tried the solution you found, to copy that file and change PrivateMounts to no, rebooted to systemd and it worked!!

I'm going to overwrite Ubuntu with Mint and see how that behaves.
_________________
URC7560/URC7562, URC8910, URC7980, URC6440/OARUSB04G and URC3661

[davecs]

Exactly the same with Mint as with Ubuntu except that the user interface is far more to my liking. Even though I made that alteration in the file to PrivateMounts=no, it wouldn't mount the remote. And as for my other theory, neither would systemd-mount from udev. So that was a non-starter.

EDIT: Got it working in Mint!

I found another site which told me to remove a further line in system-udevd.service but I hashed it out as follows:

# SystemCallFilter=@system-service @module @raw-io bpf

Once I did this, after a reboot, my 6440 remote started mounting, though it also put up an error to say it was already mounted! But that's OK by me. But yes it becomes available when plugged in, and when removed unmounts though sometimes it wants a password to unmount. But it's working! I have no doubt that I needed to make the same second alteration in Ubuntu but please don't make me install it again!!
_________________
URC7560/URC7562, URC8910, URC7980, URC6440/OARUSB04G and URC3661

[HamburgerHelper1]

I use xubuntu with xfce and "Barfs" code From this thread http://www.hifi-remote.com/forums/viewtopic.php?t=102592&postdays=0&postorder=asc&&start=0
I do not use mount or unmount from command line I just click it in my file manager to mount.
I am surprised Barf has not commented

With the line
Code:
/dev/disk/by-id/usb-UEI_Remotes_UEI_Mass_Storage_000000000001-0:0-part1 /urc6440 vfat user,noauto,umask=0,nosuid,nodev,nofail,x-gvfs-show 0 0

in /etc/fstab you can mount it without root/sudo. Just
Code:
mount /urc6440

The directory in the second position can be any existing directory. Before removing the remote, do
Code:

umount /urc6440

otherwise the system might misbehave.

Tested with Fedora.

[davecs]

[HamburgerHelper1]

I think in xubuntu usb_modeswitch changes it to a serial device,instead of leaving it as a mass storage device
Not sure but as a mass storage device it might auto mount in xubuntu

[HamburgerHelper1]

Further reading and testing of usb-modeswitch did not work for auto mounting