Indeed, this was not a problem with systemd, I just did not check the
device permission.
Chmod fixes it for the current boot, and a new udev rule fixes the issue
permanently.
Kevin P.
Il giorno ven 11 mar 2022 alle ore 04:09 Cristian RodrÃguez <
crrodrig...@opensuse.org> ha scritto:
> On Wed, Ma
On Wed, Mar 9, 2022 at 12:09 PM Kevin P wrote:
>
> Hello Greg and thanks for answering :)
> I never used strace, so I couldn't figure from the output, but further
> research led me to this post:
> http://www.pclinuxos.com/forum/index.php?topic=135714.0
> So I just tried (on the host):
> chmod o+
Hello Greg and thanks for answering :)
I never used strace, so I couldn't figure from the output, but further
research led me to this post:
http://www.pclinuxos.com/forum/index.php?topic=135714.0
So I just tried (on the host):
chmod o+rw /dev/bus/usb/001/005
And it is now working. I was not expecti
On Wed, Mar 09, 2022 at 03:04:00PM +0100, Kevin P wrote:
> Good evening everyone.
> I would like a nspawn container on my Raspberry Pi (Raspbian, systemd 247)
> to access a RTL2838 DVB-T USB stick.
> Inside the container, dump1090 will run and feed aircraft data (piaware and
> adsbexchange projects
Good evening everyone.
I would like a nspawn container on my Raspberry Pi (Raspbian, systemd 247)
to access a RTL2838 DVB-T USB stick.
Inside the container, dump1090 will run and feed aircraft data (piaware and
adsbexchange projects).
lsusb gives:
Bus 001 Device 005: ID 0bda:2838 Realtek Semicondu
