Nobody can help me!?
Beiträge von emsic
-
-
I stumbled over this post. Is there at least a way to quick reconfigure shared folders and windows permissions?
This would help so much to save time after reinstalling -
Hi, after update to OMV 3, I wanted to install vdr-manager again, like I did without problem on OMV 2.
Coderoot@NAS:~# apt-get install vdr-plugin-vdrmanager Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig E: Paket vdr-plugin-vdrmanager kann nicht gefunden werden.
==> VDR Manager not found
Can anybody please help?
-
Thanks Hoppel,
Just 5 minutes ago I got it solved by myself. Simply copied 'dvb-demod-m88ds3103.fw' which I found here to /lib/firmware/
My card is DVBSky S950 V3 and in OMV 2x it was always 'dvb-fe-ds3103.fw', no idea why this has changed.
-
I had new installed OMV 3.x because upgrade from 2x failed. No problem, everything worked fine so far, except VDR. VDR was the reason, why I frist tried to update instead of new install, as I was hoping my card is still recocnized after update.
After new installation I tried to install drivers an firmware as followsCode
Alles anzeigen# Start terminal apt-get update apt-get upgrade # Install required build tools (openSUSE: `zypper install make gcc kernel-devel`) apt-get install kernel-package linux-headers-`uname -r` # Download DVBSky Media build package # (see: http://www.dvbsky.net/Support.html to download the package for your kernel version) cd /usr/src wget http://www.dvbsky.net/download/linux/media_build-bst-14-141106.tar.gz tar xf media_build-bst-14-141106.tar.gz cd media_build-bst-14 # `build_x86.sh` for any 32-bit system with DVB-S/S2/T/T2 OR `build_dvbc_x86.sh` for DVB-S/S2/C driver # `build_x64.sh` for any 64-bit system with DVB-S/S2/T/T2 OR `build_dvbc_x64.sh` for DVB-S/S2/C driver # Run `uname -a` to determine if 32 or 64-bit (x86_64/amd64/ia64) is required. ./v4l/build_x86.sh ~OR~ ./v4l/build_dvbc_x86.sh ~OR~ Für 64bit ./v4l/build_x64.sh ~OR~ ./v4l/build_dvbc_x64.sh make && make install # Download and install firmware cd /usr/src wget http://www.dvbsky.net/download/dvbsky-firmware.zip unzip dvbsky-firmware.zip sh ./bst-firmware.sh # Reboot and check DVB devices reboot ls /dev/dvb dmesg | grep -i dvb
as this was the way I install this several times in OMV 2x
Note: I had to install 'make' and 'zip' 'unzip' firstThe result is as follows:
Code
Alles anzeigenLast login: Thu Jan 4 13:50:04 2018 from localhost root@NAS:~# apt-get install kernel-package linux-headers-`uname -r` Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen.... Fertig E: Paket linux-headers-4.9.0-0.bpo.3-amd64 kann nicht gefunden werden. E: Mittels regulärem Ausdruck »linux-headers-4.9.0-0.bpo.3-amd64« konnte kein Pa ket gefunden werden. root@NAS:~# cd /usr/src root@NAS:/usr/src# wget http://www.dvbsky.net/download/linux/media_build-bst-14- 141106.tar.gz --2018-01-04 14:20:57-- http://www.dvbsky.net/download/linux/media_build-bst-14 -141106.tar.gz Auflösen des Hostnamen »www.dvbsky.net (www.dvbsky.net)«... 94.102.215.112 Verbindungsaufbau zu www.dvbsky.net (www.dvbsky.net)|94.102.215.112|:80... verbu nden. HTTP-Anforderung gesendet, warte auf Antwort... 200 OK Länge: 9140887 (8,7M) [application/x-gzip] In »»media_build-bst-14-141106.tar.gz.1«« speichern. media_build-bst-14- 100%[=====================>] 8,72M 3,72MB/s in 2,3s 2018-01-04 14:21:00 (3,72 MB/s) - »»media_build-bst-14-141106.tar.gz.1«« gespeic hert [9140887/9140887] root@NAS:/usr/src# tar xf media_build-bst-14-141106.tar.gz root@NAS:/usr/src# cd media_build-bst-14 root@NAS:/usr/src/media_build-bst-14# ./v4l/build_x64.sh root@NAS:/usr/src/media_build-bst-14# make && make install make -C /usr/src/media_build-bst-14/v4l make[1]: Entering directory '/usr/src/media_build-bst-14/v4l' No version yet, using 4.9.0-0.bpo.3-amd64 scripts/make_makefile.pl Updating/Creating .config Preparing to compile for kernel version 4.9.0 File not found: /lib/modules/4.9.0-0.bpo.3-amd64/build/.config at ./scripts/make_kconfig.pl line 33, <IN> line 4. Updating/Creating .config Preparing to compile for kernel version 4.9.0 File not found: /lib/modules/4.9.0-0.bpo.3-amd64/build/.config at ./scripts/make_kconfig.pl line 33, <IN> line 4. make[1]: *** No rule to make target '.config', needed by '.myconfig'. Schluss. make[1]: Leaving directory '/usr/src/media_build-bst-14/v4l' Makefile:26: recipe for target 'all' failed make: *** [all] Error 2 root@NAS:/usr/src/media_build-bst-14# cd /usr/src root@NAS:/usr/src# wget http://www.dvbsky.net/download/dvbsky-firmware.zip --2018-01-04 14:24:40-- http://www.dvbsky.net/download/dvbsky-firmware.zip Auflösen des Hostnamen »www.dvbsky.net (www.dvbsky.net)«... 94.102.215.112 Verbindungsaufbau zu www.dvbsky.net (www.dvbsky.net)|94.102.215.112|:80... verbunden. HTTP-Anforderung gesendet, warte auf Antwort... 200 OK Länge: 8536 (8,3K) [application/zip] In »»dvbsky-firmware.zip.2«« speichern. dvbsky-firmware.zip.2 100%[============================================================================================================>] 8,34K --.-KB/s in 0,02s 2018-01-04 14:24:40 (392 KB/s) - »»dvbsky-firmware.zip.2«« gespeichert [8536/8536] root@NAS:/usr/src# unzip dvbsky-firmware.zip Archive: dvbsky-firmware.zip inflating: bst-firmware.sh inflating: dvb-fe-ds3103.fw inflating: dvb-fe-ds300x.fw root@NAS:/usr/src# sh ./bst-firmware.sh Copy Firmware for DVBSky card/box. root@NAS:/usr/src# reboot Root@NAS:~# ls /dev/dvb adapter0 root@NAS:~# dmesg | grep -i dvb [ 6.069727] SMI PCIe driver 0000:02:00.0: card detected: DVBSky S950 V3 [ 6.186803] DVB: registering new adapter (SMI_DVB) [ 6.408619] SMI PCIe driver 0000:02:00.0: DVB: registering adapter 0 frontend 0 (Montage Technology M88DS3103)... [ 6.428318] SMI PCIe driver 0000:02:00.0: DVBSky S950 V3 port 1 MAC: 00:18:33 :54:05:51 [ 6.710671] Registered IR keymap rc-dvbsky [ 6.710820] input: IR (DVBSky S950 V3) as /devices/pci0000:00/0000:00:04.0/00 00:02:00.0/rc/rc0/input3 [ 6.711004] rc rc0: IR (DVBSky S950 V3) as /devices/pci0000:00/0000:00:04.0/0 000:02:00.0/rc/rc0 [ 9.770627] m88ds3103 6-0068: firmware: failed to load dvb-demod-m88ds3103.fw (-2) [ 9.770681] m88ds3103 6-0068: Direct firmware load for dvb-demod-m88ds3103.fw failed with error -2 [ 9.770685] m88ds3103 6-0068: firmware file 'dvb-demod-m88ds3103.fw' not foun d
In the past I needed weeks to get this TV-card working and to create the workarround to install it again and again. Unfortunately it did not work in OMV3. I am still a Linux noob, so please could anybody give me support to adjust my workarround.
Many Thanks
-
Ist eigentlich meine Idee bezüglich Browser Inkombatibilität (siehe oben) so abwegig? Kam Null Reaktion.
-
-
-
-
-
-
-
Code
Alles anzeigenroot@NAS:~# dpkg -l | grep openm ii openmediavault 2.2.2 all Open network attached storage solution ii openmediavault-autoshutdown 1.0.8 all OpenMediaVault AutoShutdown Plugin ii openmediavault-backup 1.0.11 all backup plugin for OpenMediaVault. ii openmediavault-calibre 1.1 all Calibre plugin for OpenMediaVault. ii openmediavault-extplorer 1.2 all OpenMediaVault eXtplorer plugin ii openmediavault-keyring 0.4 all GnuPG archive keys of the OpenMediaVault archive ii openmediavault-links 1.5 all OpenMediaVault links plugin ii openmediavault-minidlna 1.1 all OpenMediaVault miniDLNA (DLNA server) plugin ii openmediavault-mpd 1.0.3 all OpenMediaVault MPD (Music Player Daemon) plugin ii openmediavault-omvextrasorg 2.13.1 all OMV-Extras.org Package Repositories for OpenMediaVault ii openmediavault-shellinabox 1.2 all Web-based SSH client. ii openmediavault-vdr 1.2 all VDR plugin for OpenMediaVault. ii openmediavault-vdr-extras 1.3 all Extras plugin for openmediavault-vdr. ii openmediavault-wol 1.0.4 all OpenMediaVault WOL plugin
-
-
Of course it's "root" . shame on me but thanks to you. But how can I now restore my WebGui?
-
Yes I get login prompt and name is "admin" and my password
-
Hi,
I am getting the "502 Bad gateway" error when I try to reach OMV via Webinterface, but what makes me really nervous is, that I can't login via putty due to wrong password. Server is working as far as I can reach my drives via Samba and VDR is working either. Can somebody help me?
-
I strongly believe you are right. But I can not see there is a password. Is this normal? I made a test and created a new user account "Diana" on my own notebook, and I set windows password same as I might have set in OMV. When I logged in and started explorer, I had immediately access to folder "Diana" on NAS, without asking for any credentials.
-
That's exactly my problem. I am not sure. I think I did, but if I look into OMV user configuration all fields are empty except user name.
I did look into my laptops credential manager and there is NAS with my user name and passwort mentioned, but in OMV the password field is also empty. -
Can't look, because notebook isn't here at the moment. I am also a bit unsure how it works anyway with Samba shares. When I look into OMV I gave user "Diana" read/write permission for folder "Diana" but it seems I haven't set any passwort. The windows account is also "Diana", does that mean, there is automatically access to the folder? I am a bit confused.