Beiträge von linuxnoob

    Currently compiling kodi matrix


    I think I have made some progress not getting the error message anymore when I start vdr.service


    vdr.service - Video Disk Recorder

    Loaded: loaded (/usr/lib/systemd/system/vdr.service; disabled; vendor pre>

    Active: active (running) since Sun 2021-10-24 21:47:08 BST; 7s ago

    Main PID: 59255 (vdr)

    Status: "Ready"

    Tasks: 9 (limit: 9454)

    Memory: 32.2M

    CPU: 162ms

    CGroup: /system.slice/vdr.service

    └─59255 /usr/bin/vdr


    Oct 24 21:47:08 pc vdr[59255]: [59255] VNSI: VNSI Server started

    Oct 24 21:47:08 pc vdr[59255]: [59255] VNSI: Channel streaming timeout: 10 sec>

    Oct 24 21:47:08 pc vdr[59255]: [59255] switching to channel 1 S19.2E-1-1089-12>

    Oct 24 21:47:08 pc systemd[1]: Started Video Disk Recorder.

    Oct 24 21:47:08 pc vdr[59255]: [59267] SVDRP pc opening port 6419/tcp

    Oct 24 21:47:08 pc vdr[59255]: [59267] SVDRP pc listening on port 6419/tcp

    Oct 24 21:47:08 pc vdr[59255]: [123B blob data]

    Oct 24 21:47:08 pc vdr[59255]: [12B blob data]

    Oct 24 21:47:08 pc vdr[59255]: [45B blob data]

    Oct 24 21:47:13 pc vdr[59255]: [59265] VNSI: Requesting clients to reload time>


    Although having an issue installing vdr-live - it needs 'tntnet' and 'cxxtools'


    cxxtools fails to compile although I do not understand (not experienced enough) this because cxxtools is being used currently to build kodi


    Building CXX object build/xbmc/CMakeFiles/xbmc.dir/CueDocument.cpp.o


    Lets see what happens once kodi is finished

    [gary@pc conf.d]$ ls

    00-vdr.conf 50-vnsiserver.conf

    [gary@pc conf.d]$ cd

    [gary@pc ~]$ systemctl start vdr.service

    [gary@pc ~]$ systemctl status vdr.service

    ● vdr.service - Video Disk Recorder

    Loaded: loaded (/usr/lib/systemd/system/vdr.service; disabled; vendor pres>

    Active: active (running) since Sun 2021-10-24 20:18:33 BST; 12s ago

    Main PID: 2269 (vdr)

    Status: "Ready"

    Tasks: 9 (limit: 9454)

    Memory: 16.0M

    CPU: 125ms

    CGroup: /system.slice/vdr.service

    └─2269 /usr/bin/vdr


    Oct 24 20:18:33 pc vdr[2269]: [2269] starting plugin: vnsiserver

    Oct 24 20:18:33 pc vdr[2269]: [2269] VNSI: Starting vnsi server at port=34890

    Oct 24 20:18:33 pc vdr[2269]: [2269] VNSI: VNSI Server started

    Oct 24 20:18:33 pc vdr[2269]: [2269] VNSI: Channel streaming timeout: 10 seconds

    Oct 24 20:18:33 pc vdr[2269]: [2269] switching to channel 1 S19.2E-1-1089-12003>

    Oct 24 20:18:33 pc vdr[2269]: [2281] SVDRP pc opening port 6419/tcp

    Oct 24 20:18:33 pc systemd[1]: Started Video Disk Recorder.

    Oct 24 20:18:33 pc vdr[2269]: [2281] SVDRP pc listening on port 6419/tcp

    Oct 24 20:18:33 pc vdr[2269]: [2269] ERROR: no OSD provider available - using d>

    Oct 24 20:18:38 pc vdr[2269]: [2279] VNSI: Requesting clients to reload timers


    That is with the AUR package and NOT vdr4arch

    Ok I am back I have just reflashed the pc


    Sorry I should have explained my setup earlier I want to had vdr running on the machine I am using


    It is connected to a 55 inch OLED tv, what I used to do in windows was have smartdvb or dvbviewer running in the corner of the the screen (or full screen) whilst I was browsing other stuff


    My assumption was I could have it running and play around with it in the web interface


    I am not stuck on Arch, I would use another distro if I had to the only reason I am using Arch is because I keep hearing snaps/flatpaks are evil :S


    So I will start again from the beginning:


    Install: https://aur.archlinux.org/packages/vdr/ or should I install: https://github.com/VDR4Arch/vdr4arch


    Then install: https://aur.archlinux.org/packages/vdr-vnsiserver/


    Then report back

    Yes it is arch gnome and what I was going to do was install kodi similar to tvheadend


    Was thinking it was similar as I could play around with it in the web interface?


    I would be watching tv on the same pc vdr is installed on


    Trying the ctrl alt f6 i can login and issue the command 'systemctl disable vdr.service' but still unable to get past login screen


    Fun and games lol

    Well after I saw your post i installed vdr-xorg and xlogin from the aur


    now i cannot login to my pc, it just returns me to the login page - I am typing this on my sons pc


    no biggie, all of my data is on a separate ssd i will have to reflash endeavour os

    Hi I installed the softhdevice https://aur.archlinux.org/packages/vdr-softhddevice/


    Still the same output as before


    Oct 24 18:42:33 pc vdr[1762]: [1762] frontend 1/0 provides DVB-S,DVB-S2,DSS wit>

    Oct 24 18:42:33 pc vdr[1762]: [1762] found 2 DVB devices

    Oct 24 18:42:33 pc vdr[1762]: [1762] setting primary device to 1

    Oct 24 18:42:33 pc vdr[1762]: [1762] device 1 has no MPEG decoder

    Oct 24 18:42:33 pc vdr[1762]: [1762] setting current skin to "lcars"

    Oct 24 18:42:33 pc vdr[1762]: [1762] loading /var/lib/vdr/themes/lcars-default.>

    Oct 24 18:42:33 pc vdr[1762]: [1771] SVDRP pc opening port 6419/tcp

    Oct 24 18:42:33 pc systemd[1]: Started Video Disk Recorder.

    Oct 24 18:42:33 pc vdr[1762]: [1771] SVDRP pc listening on port 6419/tcp

    Oct 24 18:42:33 pc vdr[1762]: [1762] ERROR: no OSD provider available - using d>


    vdr/plugins folder


    libvdr-epgtableid0.so.2.4.7 libvdr-softhddevice.so.2.4.7

    libvdr-hello.so.2.4.7 libvdr-status.so.2.4.7

    libvdr-osddemo.so.2.4.7 libvdr-svccli.so.2.4.7

    libvdr-pictures.so.2.4.7 libvdr-svcsvr.so.2.4.7

    libvdr-skincurses.so.2.4.7 libvdr-svdrpdemo.so.2.4.7

    OS: EndeavourOS Linux x86_64

    Kernel: 5.10.75-1-lts

    CPU: Intel Pentium G3258 (2) @ 2.550

    GPU: NVIDIA GeForce GT 1030

    Memory: 1502MiB / 7897MiB


    Sorry have just realised there is a newbie and international section feel free to move

    Hi first post sorry it is in english, I am from the Uk


    Currently just moving from windows to linux and have settled on endeavour os


    Have used smartdvb, dvbviewer etc for many years and know absolutely nothing about linux :|


    Anyhow I went to the AUR and installed the driver for my TBS6903 here: https://aur.archlinux.org/packages/tbsecp3-driver-git-dkms/

    Then installed vdr from here: https://aur.archlinux.org/packages/vdr/


    I then installed using the makepkg - si and systemctl start vdr.service


    ● vdr.service - Video Disk Recorder

    Loaded: loaded (/usr/lib/systemd/system/vdr.service; disabled; vendor pres>

    Active: active (running) since Sat 2021-10-23 18:15:50 BST; 10s ago

    Main PID: 3775 (vdr)

    Status: "Ready"

    Tasks: 6 (limit: 9454)

    Memory: 100.7M

    CPU: 484ms

    CGroup: /system.slice/vdr.service

    └─3775 /usr/bin/vdr


    Oct 23 18:15:50 pc vdr[3775]: [3775] found 2 DVB devices

    Oct 23 18:15:50 pc vdr[3775]: [3775] setting primary device to 1

    Oct 23 18:15:50 pc vdr[3775]: [3775] device 1 has no MPEG decoder

    Oct 23 18:15:50 pc vdr[3775]: [3775] setting current skin to "lcars"

    Oct 23 18:15:50 pc vdr[3775]: [3775] loading /var/lib/vdr/themes/lcars-default.>

    Oct 23 18:15:50 pc vdr[3775]: [3775] switching to channel 1 S19.2E-1-1089-12003>

    Oct 23 18:15:50 pc vdr[3775]: [3784] SVDRP pc opening port 6419/tcp

    Oct 23 18:15:50 pc vdr[3775]: [3784] SVDRP pc listening on port 6419/tcp

    Oct 23 18:15:50 pc systemd[1]: Started Video Disk Recorder.

    Oct 23 18:15:50 pc vdr[3775]: [3775] ERROR: no OSD provider available - using d>

    lines 1-21/21 (END)


    Now I have not touched any configuration files nor any groups etc, I just wanted to get it up and running and have a play around with it (I assume you can scan from within the UI?)


    If I go into plugins this is what is available:


    libvdr-devstatus.so.2.4.7 libvdr-skincurses.so.2.4.7

    libvdr-epgtableid0.so.2.4.7 libvdr-status.so.2.4.7

    libvdr-hello.so.2.4.7 libvdr-svccli.so.2.4.7

    libvdr-osddemo.so.2.4.7 libvdr-svcsvr.so.2.4.7

    libvdr-pictures.so.2.4.7 libvdr-svdrpdemo.so.2.4.7


    Is this enough just to get it up and running?


    Also if I navigate to localhost:6419 I eventually get this message:



    My setup is a vbox with a 36 inch actuator using gotox, I take it that is compatible with this programme? also can we use temporary feeds with biss....