Messages

1

Installation issues / Re: AVWizard Problem (Fresh Installation)

« on: May 17, 2018, 02:28:48 pm »

working on my patience skills

i will check these things on the weekend with a new rasp, maybe it is just another hardware problem....

2

Installation issues / Re: AVWizard Problem (Fresh Installation)

« on: May 16, 2018, 10:39:50 pm »

hmm i think it has been before... so i should rebuild the image, should`t i?
didn`t think of that.
will try that, thanks!

3

Installation issues / Re: AVWizard Problem (Fresh Installation)

« on: May 16, 2018, 07:00:05 pm »

its an raspberry Pi B 3, and i followed the RPiB Diskless mediadirector install method.
everything besides the usb-boot OTP activation, because i already did that in the past for the other installation.

4

Installation issues / Re: AVWizard Problem (Fresh Installation)

« on: May 16, 2018, 02:36:44 pm »

these are the results of my yesterdays attempt:
(i have to admit that i installed it in an kvm/qemu virtualmachine which worked very good)
(following that route, i hope i can work on this without cutting everybody else from the network and getting mad at me )

i installed kubuntu14.04.5 64bit.

After upgrading and rebooting, i installed linuxmce with the internet method.

it got into the loop, trying to start AVWizard. i rebooted using the safe mode and changed autostartmedia to 0.

after rebooting i could register a user in webadmin and added a room.

i installed the raspberry like the wiki said. the system wanted me to choose between MD,qMD or SqueezeOnly.

As i had no orbiter i tried to install a weborbiter2. it would not regenerate and register.
i found somewhere in the logs, that it complained about not finding the font arial.ttf.
I reinstalled ttf-mscorefonts-installer and it started to regenerate the orbiter.

Then i could restart the raspberry and choose MD.

Some things got installed but after the first reboot i could only see the "rainbow" screen.
i tried restarting raspberry and the core but without luck.

it reminds me of this thread:
http://forum.linuxmce.org/index.php?topic=14408.0

this is the output i have got from tcpdump -i eth1 -vv | grep "tftp":
https://paste.ubuntu.com/p/y9KCDJjnp3/

this is my dhcpcd.conf (after executing DHCP_config.sh):
https://paste.ubuntu.com/p/QCy7WqCgpJ/

this is what i also experienced on my other partition with the "old" installation not in a virtual machine.
i thought it woul be a good idea to try a fresh start because my raspberry failed as an md
after updating the core/image.

the other parts of the system seem to work headless like You suggested Posde, thanks!
(i.e. network configuration)
even the usb-passthrough seems to work with kvm/qemu.


i can try it again with a new raspberry as i need another one anyway.

or maybe i should use the 32bit image?

thanks for all the help!

5

Installation issues / Re: AVWizard Problem (Fresh Installation)

« on: May 14, 2018, 02:03:47 pm »

okay, thank You!

Now i will just need some time and worse weather.

I will report back!

6

Installation issues / Re: AVWizard Problem (Fresh Installation)

« on: May 11, 2018, 10:38:37 am »

thanks, that`s a great idea.
will try that.

i was searching a little bit on the forum and in the wiki about information how to get the installation done.

i will try the dvd installation method and choose the core only option.

 

7

Installation issues / Re: AVWizard Problem (Fresh Installation)

« on: May 09, 2018, 02:33:30 pm »

just a little update:
unfortunately, it is my hybrid/core which won`t let me install a new version.

I bought a Radeon HD 6450 graphic card and tried again.

But it shows the same symptoms including the text in kern.log

Code: [Select]

May  8 09:53:21 dcerouter kernel: [   90.920259] AVWizard[29826]: segfault at 0 ip 00007f973774ee9a sp 00007fff58836f80 err
or 4 in libSDL_ttf-2.0.so.0.10.1[7f973774c000+6000

But then it got strange.
I tried the same graphic card with my existing linuxmce installation on the other partition (didnot want to change the card again ) and there AVWizard showed up.

ui2 and hdmi audio were no problem.
(except some problems with screensaver not exiting, if using another orbiter than the one on the hybrid)

if i compare the dates, i get this:

fresh installation:

Code: [Select]

ls -l /mnt/device/137/usr/pluto/bin/AVWizard*
-rwxr-xr-x 1 root root 3111334 Mär 30  2017 /mnt/device/137/usr/pluto/bin/AVWizard
-rwxr-xr-x 1 root root     370 Mär 30  2017 /mnt/device/137/usr/pluto/bin/AVWizard_AudioConnector.sh
-rwxr-xr-x 1 root root     656 Mär 30  2017 /mnt/device/137/usr/pluto/bin/AVWizard_BlindVideoSettings.sh
-rwxr-xr-x 1 root root    3314 Mär 30  2017 /mnt/device/137/usr/pluto/bin/AVWizard-Common.sh
-rwxr-xr-x 1 root root     952 Mär 30  2017 /mnt/device/137/usr/pluto/bin/AVWizard_Gamepad_Detect.sh
-rwxr-xr-x 1 root root    2517 Mär 30  2017 /mnt/device/137/usr/pluto/bin/AVWizard_Remote_Detect.sh
-rwxr-xr-x 1 root root   18915 Mär 30  2017 /mnt/device/137/usr/pluto/bin/AVWizard_Run.sh
-rwxr-xr-x 1 root root    3435 Mär 30  2017 /mnt/device/137/usr/pluto/bin/AVWizard_UpdateResolution.sh
-rwxr-xr-x 1 root root     247 Mär 30  2017 /mnt/device/137/usr/pluto/bin/AVWizard_UpdateVolume.sh
-rwxr-xr-x 1 root root    2351 Mär 30  2017 /mnt/device/137/usr/pluto/bin/AVWizardWrapper.sh
-rwxr-xr-x 1 root root   16523 Mär 30  2017 /mnt/device/137/usr/pluto/bin/AVWizard-XineDefaultConfig.sh

old working installation:

Code: [Select]

ls -l /usr/pluto/bin/AVWizard*
-rwxr-xr-x 1 root root 2993723 Dez 11  2015 /usr/pluto/bin/AVWizard
-rwxr-xr-x 1 root root     370 Dez 11  2015 /usr/pluto/bin/AVWizard_AudioConnector.sh
-rwxr-xr-x 1 root root     656 Dez 11  2015 /usr/pluto/bin/AVWizard_BlindVideoSettings.sh
-rwxr-xr-x 1 root root    3314 Dez 11  2015 /usr/pluto/bin/AVWizard-Common.sh
-rwxr-xr-x 1 root root     952 Dez 11  2015 /usr/pluto/bin/AVWizard_Gamepad_Detect.sh
-rwxr-xr-x 1 root root    2517 Dez 11  2015 /usr/pluto/bin/AVWizard_Remote_Detect.sh
-rwxr-xr-x 1 root root   18915 Dez 11  2015 /usr/pluto/bin/AVWizard_Run.sh
-rwxr-xr-x 1 root root    3435 Dez 11  2015 /usr/pluto/bin/AVWizard_UpdateResolution.sh
-rwxr-xr-x 1 root root     247 Dez 11  2015 /usr/pluto/bin/AVWizard_UpdateVolume.sh
-rwxr-xr-x 1 root root    2351 Dez 11  2015 /usr/pluto/bin/AVWizardWrapper.sh
-rwxr-xr-x 1 root root   16523 Dez 11  2015 /usr/pluto/bin/AVWizard-XineDefaultConfig.sh
As i had nothing to loose, i copied these files to the fresh installation but it didn`t work, due to complaining about fglrx.

I also tried an old kubuntu 14.04.1 image without any better result.

The same with an attempt to install it as a virtualbox system on my laptop.

The next i would try is to use an old image from here:
http://linuxmce.iptp.org/snapshots/

Maybe that is the same route Kramden mentioned?

Is there anything else i could try?

Buying an old intel board/cpu would be another possibility?

8

Installation issues / Re: AVWizard Problem (Fresh Installation)

« on: April 17, 2018, 04:32:04 pm »

hmm, okay maybe that is a good reason to "invest" i a new graphic card.

i know You cannot give recommendations, but i made a quick search and found this one to be good enough for a hplc:

Gigabyte GeForce GT 1030 Low Profile (Silent)

it should be supported by nvidia-384.

9

Installation issues / Re: AVWizard Problem (Fresh Installation)

« on: April 17, 2018, 12:58:51 pm »

hello,

i tried a few things, but nothing really seems to work:
tried both 32bit/64bit kubuntu installations.
tried to set the different nvidia-driver versions in nvidia-installs.sh and Utils.sh.

what i did found in the kern.log after every installation is:

Code: [Select]

Apr 17 12:21:46 dcerouter kernel: [   66.010184] AVWizard[17376]: segfault at 0 ip 00007ff6db0a8e9a sp 00007fff882098a0 error 4 in libSDL_ttf-2.0.so.0.10.1[7ff6db0a6000+6000]

so this seems to be the end of my "debugging" skills, sorry. 
And i don`t know if this is the cause or just a result ...

10

Installation issues / Re: lmce firewall not working correctly?

« on: February 20, 2018, 11:53:21 am »

Hello,

i had also problems to configure the firewall.
so i wrote a config file (iptables.ipt) with entries like:

Code: [Select]

iptables -A INPUT -i eth0 -m state --state NEW -p tcp --dport 32400 -j ACCEPT
and then i have put the line

Code: [Select]

/where/the/file_is/iptables.ipt
into my /etc/rc.local

it is not really lmce style, sorry and you probably already know this but otherwise i didn`t know how to get it working.

11

Installation issues / Re: AVWizard Problem (Fresh Installation)

« on: December 02, 2017, 10:33:57 am »

i tried to mess a little bit with Utils.sh but i don`t know what to change there for loading a specific driver.

is this the right part?

Code: [Select]

InstallVideoDriver() {
local prop_driver="$1"

case "$prop_driver" in

# nVidia cards
nvidia)
if ! PackageIsInstalled nvidia-173 && ! PackageIsInstalled nvidia-304 && ! PackageIsInstalled nvidia-340 && ! PackageIsInstalled nvidia-352 && ! PackageIsInstalled nvidia-375 ; then
VerifyExitCode "Install Pluto nVidia Driver"
. /usr/pluto/bin/nvidia-install.sh
installCorrectNvidiaDriver
ConfSet "AVWizardOverride" "1"

i added my "favorite" driver nvidia-375.

ähemm is this okay? i am actually sure that is not enough.

sorry for my poor cracking skills....
 

12

Installation issues / Re: AVWizard Problem (Fresh Installation)

« on: November 28, 2017, 01:20:12 pm »

until now i had no success. i have tried 304, 340, 375 and 384.
The 375 looked very promising. it flashed a little bit better... but then also looped.
maybe it is not a driver issue. i will try to examine the xorg.conf if maybe the bus is the wrong one mentioned in the AVwizard wiki entry.
And i will try the nvidia ppa. maybe i can find a good driver there.
i hope i will find some time today....

13

Installation issues / Re: AVWizard Problem (Fresh Installation)

« on: November 25, 2017, 03:01:50 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?
 

14

Installation issues / Re: AVWizard Problem (Fresh Installation)

« on: November 20, 2017, 09:13:46 am »

hgrmmmpfff,

sorry, i had the hilarious idea to do a hardware upgrade on my hybrid-core and broke my second networkadapter.
As soon as this is fixed i will post the dmesg output.
i have two partitions, one with the old installation and another with the new one.
i can take a look at the log-files by letting linuxmce mount the other partition when my core is back from the dead.

thanks for replying!

15

Installation issues / AVWizard Problem (Fresh Installation) [solved]

« on: November 15, 2017, 04:24:01 pm »

edit:
after reinstalling ttf-mscorefonts-installer (apt-get install --reinstall ttf-mscorefonts-installer) the AVWizard appears.
at least in my virtual maschine...oh yeahhh!


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!