LeetDonkey

Members
  • Posts

    10
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

LeetDonkey's Achievements

Newbie

Newbie (1/14)

3

Reputation

  1. I edited the dockerfile to look for the neolink.toml file in a subdirectory rather than /etc/neolink.toml I don't think this is a good way of doing it since it will no longer follow the thirtythreeforty repository. Anyways, if you'd like you can simply change the repository to leetdonkey/neolink: Then change the neolink_config path configuration: then put neolink.toml in /etc/mnt/user/appdata/neolink/ and start the docker. Note that the container use the name neolink.toml instead of config.toml If there is a way of linking directly to a file instead of a directory I am not aware of it, but I must confess that I am very new at this docker stuff
  2. Hello I hope it is alright I post questions about Neolink here, it wasn't specifically mentioned in the topic. Anyways, I've tried to install Neolink, but I run into a small problem Unraid 6.9.1 seems to insist that the variable 'neolink_config:' is a directory, but it seems that Neolink expects it to be a file: [2021-04-11T09:13:55Z INFO neolink] Neolink 0.3.0 (unknown commit) release Error: IoError(Os { code: 21, kind: Other, message: "Is a directory" }) I've tried deleting the directory and making it a config.toml file, but this causes the docker to throw an error "Execution error: bad parameter" and not start at all. I'm bit at a loss on how to proceed from here, and any help would be greatly appreciated
  3. I decided to give it a try, and it seems to be working. The controller along with the arrays was detected in Unraid 6.9.1 After installing unassigned devices plugin and unassigned devices plus, I was able to mount the arrays. You can even share them via SMB and access them from a windows PC.
  4. Hello Is it possible to use an Adaptec 52445 Controller with 2 RAID 6 arrays in Unraid? It currently has a NTFS partition on each, and I was hoping to copy the content to a new Unraid Array. If the controller is supported I would assume it was just a matter of using unassigned devices to mount it and then copy the contents. Another option would be to install a windows VM and pass the controller to the VM and then copy the contents from there. The machine in question is currently running windows with a few network shares, I would prefer to migrate to Unraid without building an additional machine just to copy the contents Any thoughts on this?
  5. So this helped me alot, to begin with it didn't make sense to me since I was using the same MUX list for both the DVBsky and Terratec adapter, so it should theoretically tune the same channels. After some time and frustration I realized that Terratec H7 isn't a DVB-T2 adapter, it's only DVB-T, and everything I'm trying to do is DVB-T2. This is probably why it complains it can't tune the frequency, if I change it to DVB-T it attempts to tune correctly. I must have remembered incorrectly that it was working in Windows, this is obviously not the case Sorry for wasting your time 😐 It's not completely wasted for me though, I learned alot about tvheadend and DVB adapters in general 😄
  6. Ok, so I decided to start over and it seems I had an error in my TVheadend mux configuration. After correcting that error the DVBsky T680C tunes correctly, but the Terratec H7 still doesn't work: Tvheadend logs show this error for Terratec H7: 2021-03-13 14:10:17.208 [ NOTICE] START: HTS Tvheadend version 4.3-1941~g817a8d4e4 started, running as PID:329 UID:99 GID:100, CWD:/run/s6/services/tvheadend CNF:/config 2021-03-13 14:10:20.602 [ INFO] en50221: dvbca1-slot0-app00030041/0003: CAM supported CAIDs: 0500 (Viaccess) 2021-03-13 14:10:20.715 [ NOTICE] linuxdvb: dvbca0-0: CAM slot 0 status changed to module ready 2021-03-13 14:10:32.131 [ INFO] mpegts: 570MHz in Boxer - tuning on DRXK DVB-C DVB-T #1 : DVB-T #0 2021-03-13 14:10:32.131 [ ERROR] linuxdvb: DRXK DVB-C DVB-T #1 : DVB-T #0 - failed to tune [e=Invalid argument] It would seem that the Terratec H7 is unable to tune correctly This would explain why it's just sitting around doing nothing in Tvheadend: Here's the hardware overview in Tvheadend: The disabled Silicon Labs card is the DVBsky one, the enabled DRXK is the Terratec H7 one
  7. Hello I'm having some issues getting a USB Terratec H7 DVB-T adapter to work. I'm running Unraid 6.9.1 I'm using the librelec driver package. Something is detected, but no version is listed: Note: I have two DVB adapters plugged in, one of them is however attached to a windows VM, only the adapter not attached to a VM is created in /dev/dvb which I figured was just fine. If I remove it from the windows VM the device is created correctly, but it still shows no version. I've tried to use it in both tvheadend and minisatip. Once the container is started the log will show this: Mar 12 16:57:57 Unraid kernel: mt2063: detected a mt2063 B3 Mar 12 16:58:03 Unraid kernel: dvb_ca_en50221: dvb_ca adapter 1: DVB CAM detected and initialised successfully Which I guess means it's detected and running? Now my problem is neither tvheadend or minisatip through dvbviewer media server seems to work, the symptoms are that it seems no signal is available. I''m currently using a DVBsky T680C in my windows VM, and I've tried to remove this from the VM and use it through tvheadend/minisatip and the symptoms are the same, I know this adapter works when attached to the VM though. Now, my problem is, I'm not really sure what my next step is here? The adapter is seemingly detected just fine, it's just not working Any tips would be appreciated
  8. Hello I've given the container a custom IP, or that is, it is assigned via DHCP and is 192.168.0.2: I am also able to ping it from the PC that's trying to connect to noVNC This is the screenshots of the template page: This is the error window: This is the screenshot from the nvidia driver page: And this is the info from systems info page: Thank you for getting back to me
  9. Hello I'm unable to get the Debian-Buster-Nvidia docker to work. Specifically, I'm not able to connect to the novnc server, it simply gives me a 'failed to connect to server' I'm running Unraid 6.9.0-rc2 I have installed this nvidia driver plugin: https://forums.unraid.net/topic/98978-plugin-nvidia-driver/ the card and plugin seems to work just fine, and is currently being used in a Emby docker. This is the log section from the debian-buster-nvidia docker: ---Checking if UID: 99 matches user--- ---Checking if GID: 100 matches user--- ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Trying to get Nvidia device address--- ---Successfully got device ID: 02:00:0--- ---Trying to get Nvidia driver version--- ---Successfully got driver version: 455.45.01--- ---Checking Xwrapper.config--- ---Configuring Xwrapper.config--- ---Version missmatch, deleting local Nvidia Driver v455.45--- rm: cannot remove '/debian/NVIDIA_455.45.run': No such file or directory ---Found NVIDIA Driver v455.45.01 localy, installing...--- ---Configuring Locales to: en_US.UTF-8 UTF-8--- Generating locales (this might take a while)... en_US.UTF-8... done en_US.UTF-8... done Generation complete. ---Checking configuration for noVNC--- Nothing to do, noVNC resizing set to default Nothing to do, noVNC qaulity set to default Nothing to do, noVNC compression set to default ---Starting...--- ---Preparing Server--- ---Checking for old logfiles--- ---Checking for old lock files--- ---Starting dbus service--- ---dbus service started--- ---Starting Xfce4--- ---Starting x11vnc server--- ---Starting noVNC server--- WebSocket server settings: - Listen on :8080 - Flash security policy server - Web server. Web root: /usr/share/novnc - No SSL/TLS support (no cert file) - Backgrounding (daemon) ---Starting Pulseaudio server--- ---------------------------------------------------------------------------------------------------- Listing possible outputs and screen modes: 'Screen 0: minimum 8 x 8, current 1024 x 768, maximum 16384 x 16384 DP-0 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.00*+ 1600x900 59.82 1400x900 59.88 1368x768 59.88 59.85 1360x768 59.96 59.80 1280x800 59.91 59.81 1280x720 59.86 59.74 1152x864 60.00 1024x576 59.90 59.82 960x540 59.82 59.63 864x486 59.92 59.57 800x600 72.19 60.32 56.25 800x450 59.82 700x450 59.88 684x384 59.88 59.85 680x384 59.96 59.80 640x480 59.94 640x400 59.98 59.88 640x360 59.86 59.83 512x384 60.00 512x288 60.00 59.92 480x270 59.82 59.63 432x243 59.92 59.57 400x300 72.19 320x240 60.05 DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 disconnected (normal left inverted right x axis y axis) DP-5 disconnected (normal left inverted right x axis y axis) DP-6 disconnected (normal left inverted right x axis y axis) DP-7 disconnected (normal left inverted right x axis y axis)' ---------------------------------------------------------------------------------------------------- ---Looks like your highest possible output on: 'DP-0' is: '1600x900'--- ---Trying to set the resolution to: '1600x900' on output: 'DP-0'--- ------------------------------------------------------------------------------- --------If you want to set the resolution manually please create a file-------- ---------in /debian/.config/container.cfg with the following contents:--------- ------------------------------------------------------------------------------- Resolution: 1920x1080 Output: HDMI-0 -------------------------------------------------------------------------------- ---Change the resolution and output to your specific configuration/preference--- -------------------------------------------------------------------------------- Current version of pixman: 0.36.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Thu Feb 4 08:11:54 2021 (==) Using config file: "/etc/X11/xorg.conf" (==) Using system config directory "/usr/share/X11/xorg.conf.d" xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) I believe the detected PCI ID is correct The problem is that noVNC just gives me 'failed to connect to server' I've tried installing the debian-buster without nvidia, and it works just fine. Any ideas on what I'm doing wrong? I'll be happy to provide additional info if needed.