Messages

1

Users / Re: [RESOLVED] Media Files Sync - storage drives missing from tree

« on: February 26, 2018, 01:10:50 pm »

Interesting.

Could a hidden .id3 file cause this?  Remember this drive was on another core at a different device number

Sent from my SM-G900V using Tapatalk

2

Users / Re: Media Files Sync - storage drives missing from tree

« on: February 26, 2018, 12:06:05 am »

That I did sir.

I did find a resolution.   I re-named the 'data' directory under /mnt/device/xx/public/ and created a new one.  Then moved my 'videos' folder into the new data directory... and 'bang!!!' it fixed the issue.   Moved the remaining folders into the new 'data' folder and everything is good.

Permissions look exactly the same.. bizarre indeed.

Thanks for your attention.

Dennis

3

Users / Re: Media Files Sync - storage drives missing from tree

« on: February 25, 2018, 03:52:24 pm »

Did you manually add the drives to the devices tree, or did you wait for LinuxMCE to detect the drives?

I let it detect

Sent from my SM-G900V using Tapatalk


Update:    The folder links are created in /home/public/data as seen on the attachment.

I did an experiment by removing the drives from the system via web administration.   I then rebooted and let it re-discover the drives and recreate.    Again, all the links are there, but the tree on the left is not populated with the drives under 'audio' or 'video' or the others.   

there are no segfaults in dmesg.

4

Users / [RESOLVED] Media Files Sync - storage drives missing from tree

« on: February 25, 2018, 02:41:02 pm »

I did a fresh install on new hardware.    After the install, I shut down and added my storage drives from the previous server.
On reboot, going into Media Files Sync, I cannot access the drives... they don't show up in the tree... see the image.

Anyone else experience this and know how to resolve it?

The media IS showing up on the MD Media pages, but the metadata is incorrect... I cannot get to it to fix it.

Thanks,
Dennis

5

Installation issues / Re: AVWizard Problem (Fresh Installation)

« on: December 01, 2017, 11:00:34 pm »

weekly i try to install.... no chance... it loops when trying the nvidia.

Any solution in sight?

With best regards,

Can you verify that the nvidia driver is loading?

lsmod | grep nvidia

If "nvidia" is not listed from the command, you must look into dmesg to see what is going on with the driver not loading

dmesg | grep -i nvidia

The above command should list several lines of information.  One line should indicate what driver is trying to load  (304.xx, 340.xx, 352.xx, or 361.xx where xx is a number)   if the driver is failing to load, you should see a message stating that your card is not supported by the driver or some other reason for failure to load.

If the driver is loading as indicated by lsmod comnand, try forcing a re-execute of AVWIZARD by running the command

/usr/pluto/bin/RebootWithAVWizard.sh

OR

modify /etc/pluto.conf as indicated in this thread, delete any xorg.conf file in /etc/X11. Then reboot

If this still does not work, then you have to look in system logs and look for errors that you can provide in this thread

Sent from my SM-G900V using Tapatalk

6

Installation issues / Re: AVWizard Problem (Fresh Installation)

« on: November 28, 2017, 08:55:48 pm »

As I told golgoj4 yesterday in IRC, make sure that if you do have a specific version of the nVidia driver you use, change it in *both* scripts. nvidia-install.sh AND Utils.sh. Please report back if it helps.

Hmmm. Didn't know about Utils.sh...but I never had to modify it to resolve my install issues.

Thanks for the info.

Sent from my SM-G900V using Tapatalk

7

Installation issues / Re: AVWizard Problem (Fresh Installation)

« on: November 27, 2017, 06:45:37 pm »

So is there any clear way to fix this or just guess until something works?

Been stuck for over a week trying to install lmce again. close to giving up at this point.

golgoj4,
Once you can determine if the installation is loading the wrong nvidia driver, it should be an easy fix by modifying the nvidia-install.sh script to only let it select a workable version of the nvidia driver. 

I cannot say that it MUST be done, but I modified (toggled) the value of 'firstboot' in /etc/pluto.conf, and delete the xorg.conf file in /etc/X11 before rebooting.

I have submitted a bug issue for the problem of the script not selecting a compatible driver for the card installed.

If you determine that the correct video driver is being installed, and the system device is created for the video card, then the problem may lie elsewhere. 

I have not had any other install issues other than the nvidia issue on 12.04 and 14.04. 



Sent from my SM-G900V using Tapatalk

8

Installation issues / Re: AVWizard Problem (Fresh Installation)

« on: November 25, 2017, 05:52:54 pm »

so, today i finally could try some things.

this is the output of dmesg | grep -i nvidia on the fresh installation:

Code: [Select]

[    2.852129] nvidia: module license 'NVIDIA' taints kernel.
[    2.861367] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[    2.867746] nvidia-nvlink: Nvlink Core is being initialized, major device number 245
[    2.868436] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 PDT 2017 (using threaded interrupts)
[    2.870135] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  384.90  Tue Sep 19 17:05:19 PDT 2017
[    2.871016] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[    7.602554] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card1/input15
[    7.602618] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card1/input16
[  157.531321] init: nvidia-prime main process (2182) terminated with status 127

this is the output using my working partition:

Code: [Select]

[    3.219240] nvidia: module license 'NVIDIA' taints kernel.
[    3.227886] nvidia: module verification failed: signature and/or  required key missing - tainting kernel
[    3.232761] nvidia-nvlink: Nvlink Core is being initialized, major device number 249
[    3.232775] NVRM: loading NVIDIA UNIX x86 Kernel Module  375.66  Mon May  1 14:31:26 PDT 2017 (using threaded interrupts)
[    3.234265] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  375.66  Mon May  1 15:12:41 PDT 2017
[    3.236409] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[    9.693388] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card1/input16
[    9.693516] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card1/input15
[   33.291712] init: nvidia-prime main process (2062) terminated with status 127
[   40.325397] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card1/input26
[   40.325499] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card1/input25
[   40.692447] nvidia 0000:01:00.0: irq 52 for MSI/MSI-X
[   41.625633] nvidia-modeset: Allocated GPU:0 (GPU-51245e54-2a3b-ff70-a556-af13c9841b10) @ PCI:0000:01:00.0

i tried using the nouveau driver to get into avwizard by edditing the driver part in xorg.conf and making nvidia-install.sh unusable by just writing "exit 0" into it. (recovery mode;mount -o remount,rw / )
i got then a xserver as it seems but no avwizard. it installed a few things writing in the well known red text but ended with a low resolution windows and a mousepointer.
I executed Rebootwithavwizard.sh for that.

i thought i also tried to use nvidia-375 for the new installation but will try that again.

as i read in the wiki (http://wiki.linuxmce.org/index.php/Display_Drivers#The_AVWizard_crashes_X-windows) can it be that only the avwizard don`t like the graphic device / driver?

KDE seem to work okay after installation.

is it possible to just use some config-files from my other working partition of linuxmce?

how can i make avwizard run with the nouveau driver and defuse nvidia-install.sh?

In the installation that is failing, the nvidia driver is 384.xx and it doesn't create the system devices needed. 

Your working installation is loading nvidia 377.xx driver and it does create the system devices.

I would get to a terminal and edit the nvidia-install.sh file replacing any nvidia-384 reference to either nvidia-340 or nvidia-377 ...  save the changes and to force AVWIZARD to run, execute the following

/usr/pluto/bin/RebootWithAVWizard.sh

It should run the wizard after the reboot

Good luck

Sent from my SM-G900V using Tapatalk

9

Installation issues / Re: AVWizard Problem (Fresh Installation)

« on: November 21, 2017, 09:51:36 pm »

I'm moving my server to a new location in my home and my system is apart now. I did a virtualbox install on a laptop and saw same behavior with VB driver. Before I took it apart I entered recovery and did lsmod. It showed nvidia module loaded and no nouveau. But that is in recovery and it is stable. When I can power it up again, what logs should I check?

dmesg log should indicate if loaded nvidia driver supports the video card installed.  In my case I  saw the nvidia driver indicate what particular driver to use with my card. 

I believe that using the nouveau driver still allowed the AVWizard to run.  It's been quite along time since I got my server set up on 14.04, but I believe the setup video did eventually run.

Sent from my SM-G900V using Tapatalk

10

Installation issues / Re: AVWizard Problem (Fresh Installation)

« on: November 18, 2017, 11:37:53 pm »

I am having the same issue with net-install. I get flash of Screen with mouse cursor and flash of black screen and flash of screen with 0 in top corner. I am unable to get to a console. My card is verified to work with nvidia-340. I have done all the driver workarounds in nvidia-install.sh and even removed it. I don't think it is a driver issue but i can't sign into a console because the screen with the 0 becomes a flash of the console too fast to sign into.

You can boot into recovery mode and investigate if nvidia driver is loading.

Sent from my SM-G900V using Tapatalk

11

Installation issues / Re: AVWizard Problem (Fresh Installation)

« on: November 18, 2017, 06:11:15 pm »

Hello,

the last "fresh" installation is some time ago and i am getting more RAM and more HD space for my core, so i thought to try a 64bit-installation.

I downloaded kubuntu 14.04.5 and executed the mce-install script.
After finishing i did a reboot.
But after rebooting again i am not able to see the calming screen of the avwizard.
It is stucked with trying to maybe start it and something else.

I tried different nvidia versions as mentioned here in the forum with manipulating nvidia-install.sh but without any success.

I was searching the log files for any hint.
One thing i found, which looks a little bit strange, was this, but i am not really an expert in this and not sure that it is of any relevance

AVWizard_Run....log is the first log after running mce-install script:

Code: [Select]

==) Log file: "/var/log/Xorg.1.log", Time: Tue Nov 14 16:11:45 2017
(++) Using config file: "/etc/X11/xorg.conf.pluto.avwizard"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
>                   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server

  Attribute 'SyncToVBlank' (dcerouter:1.0) assigned value 1.


ERROR: Error parsing assignment 'XVideoTextureSyncToVBlank=1' (Unrecognized
       attribute name).



ERROR: Error parsing assignment 'XVideoBlitterSyncToVBlank=1' (Unrecognized
       attribute name).


Rate 60.0 Hz not available for this size
Unable to open /usr/pluto/wiz_pixmaps/skin.xml
Warning, CounterFontSize not set!
Warning, CounterFontSize not set!
Unknown type of argument parsing argument: --compositor=off
WizardPageWelcome::WizardPageWelcome
WizardPageWelcome::DefaultSetup
Warning: there is no font setup for rendering!
Warning: there is no font setup for rendering!
Warning: there is no font setup for rendering!

I put the whole log at this place:
http://paste.ubuntu.com/25967676/

My video-card is this:
VGA compatible controller [0300]: NVIDIA Corporation GF119 [GeForce GT 520] [10de:1040]

Kubuntu told me to use nvidia-384.

I divided my harddisk into two partitions. So my old installation (14.04) is running fine with the same hardware.

Does anybody has a helping advice what i can do or have to check?

All the best!

If you can get to a terminal, run 'dmesg | grep -i nvidia'  to determine if the nvidia driver is loading or failing... there might be hints there. 

Sent from my SM-G900V using Tapatalk

12

Installation issues / Re: Upgrading from 10.04 to 16.04

« on: September 09, 2017, 12:55:03 am »

 Issue #2793

13

Installation issues / Re: Upgrading from 10.04 to 16.04

« on: September 08, 2017, 02:43:17 am »

here you go Phenigma:

my CORE (that will only run driver up to version 304.135)

Code: [Select]

00:18:00.0 VGA compatible controller [0300]: NVIDIA Corporation G71 [GeForce 7950 GT] [10de:0295] (rev a1)
my MD (that will only run driver up to version 340.102):

Code: [Select]

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1)

14

Installation issues / Re: Upgrading from 10.04 to 16.04

« on: September 04, 2017, 02:50:45 pm »

I have quite a similiar experience....fresh install of 14.04. i tried the last image as well as net install. Its booting...displays 0 in the top left, goes blank, reboots. All of this continuously. The graphicscard in this case is a cheap gt710.

Along with modifying nvidia-install.sh, delete  /etc/X11/xorg.conf file AND in /etc/pluto.conf, change Firstboot = false to Firstboot = true...and then reboot

Sent from my SM-G900V using Tapatalk

15

Installation issues / Re: Upgrading from 10.04 to 16.04

« on: August 29, 2017, 11:21:46 pm »

Strange indeed.  My core has older nvidia card that only works with 304 driver.  My MD in living room has a card that will only go as high as 340 driver.  Editing nvidia-install.sh has always worked for my situation..  trying other card may resolve your issue

Sent from my SM-G900V using Tapatalk