Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - G.I.R.

Pages: [1] 2 3 4
1
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....
 


2
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....

3
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?
 

4
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!



5
Installation issues / AVWizard Problem (Fresh Installation)
« on: November 15, 2017, 04:24:01 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!

6
Users / Timed Events / Play Media via Raspberry Pi
« on: December 02, 2016, 11:26:06 am »
Hello,

now as i got this silent and fabulous media director doing his job, the next step would be using it for timed events.

I used the commands "Load Playlist" and "MH Set Volume" with Media Plug-in for my zotac zbox.

It seems that this is not working with the Raspberry.

Then i thought using the OMX Player Plugin would be the right way but i am a little bit confused about the configuration and cannot get it to work.
I have looked into the DCErouter.log if i can find something usefull when i start playing media with an orbiter but i cannot figure out what to use.

Can somebody give me a hint?
Is this possible?


7
Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: December 02, 2016, 10:22:07 am »
phenigma, You were right, sorry!
it had been a problem with a/my router/switch...

i have changed my thread to "solved".
https://forum.linuxmce.org/index.php?topic=14392.msg103522#msg103522

mea culpa....sorry


8
Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 25, 2016, 07:10:25 pm »
good news!   :D
i made a fresh installation today and there it works perfectly.
I can even see the rainbow now at the start.  :)

i could only found pluto-boot-scripts. is that the right one?

i compared the version of the new installation
https://paste.ubuntu.com/23230006/

with my "old" installation:
https://paste.ubuntu.com/23230134/

don`t know whats wrong with my old installation...

now i only have my old problems with my new installation, that i cannot listen to any music or see any video from my hybrid/core.
i think it is again the low nfs-speed.
will investigate that problem now. ( will try to watch something from another location than my media hd in my core )

So thank You very much for You help and Your work!
Q.E.D. It works!  :)


Shall i provide any more information or should i just switch to my new installation?



9
Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 25, 2016, 01:32:58 pm »
hey, then there is hope on the horizont! :)

i did a

Code: [Select]
apt-get update
apt-get dist-upgrade

and then i ran DHCP_Config.sh:

Code: [Select]
dcerouter_1047514:/home/linuxmce# /usr/pluto/bin/DHCP_config.sh
2
20282 So 25. Sep 13:07:01 CEST 2016 WaitLock 'PlutoDHCP' (PlutoDHCP_config)
20282 So 25. Sep 13:07:01 CEST 2016 WaitLock 'PlutoDHCP' (PlutoDHCP_config) success
Device 1 has bad mac address
isc-dhcp-server stop/waiting
isc-dhcp-server start/running, process 20466
20282 So 25. Sep 13:07:01 CEST 2016 Unlock 'PlutoDHCP' (PlutoDHCP_config)
20282 So 25. Sep 13:07:01 CEST 2016 Unlock 'PlutoDHCP' (PlutoDHCP_config) success

is the warning about the mac adress normal?

but dhcpd.conf looks exactly the same:
http://paste.ubuntu.com/23228904/

there were no lmce packets shown to update.
maybe there is something wrong with my sources list?
https://paste.ubuntu.com/23228881/


10
Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 24, 2016, 08:21:56 am »
good morning!

this is /etc/dhcp/dhcpd.conf
http://paste.ubuntu.com/23223444/

and this is the output of tcpdump:

Code: [Select]
dcerouter_1047514:/home/linuxmce# tcpdump -i eth1 -vv | grep "tftp"
tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes
          file "/tftpboot/pxelinux.0"
          file "/tftpboot/pxelinux.0"
          file "/tftpboot/pxelinux.0"
          file "/tftpboot/pxelinux.0"
          file "/tftpboot/pxelinux.0"
    0.0.0.0.49153 > 0.0.0.0.tftp: [no cksum]  35 RRQ "71638953/start.elf" octet tsize 0
    0.0.0.0.49154 > 0.0.0.0.tftp: [no cksum]  29 RRQ "autoboot.txt" octet tsize 0
    0.0.0.0.49155 > 0.0.0.0.tftp: [no cksum]  27 RRQ "config.txt" octet tsize 0
    0.0.0.0.49156 > 0.0.0.0.tftp: [no cksum]  29 RRQ "recovery.elf" octet tsize 0
    0.0.0.0.49157 > 0.0.0.0.tftp: [no cksum]  26 RRQ "start.elf" octet tsize 0
    0.0.0.0.49158 > 0.0.0.0.tftp: [no cksum]  26 RRQ "fixup.dat" octet tsize 0
          file "/tftpboot/pxelinux.0"

sorry, need to figure out howto use pastebinit with tcpdump...


11
Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 23, 2016, 11:21:48 pm »
hmm, sorry no luck.

just to be sure not to make any stupid mistakes somewhere:
i installed the linux-image-default-raspbian-jessie_4.4.17-v7+-lmce5_all.deb with dpkg -i.
then i made a new diskless image.
i copied the diskless image to the sdcard:
Code: [Select]
dd bs=4M if=2016-09-20-netboot-lmce.img of=/dev/sdbstarted the raspberry.
it boots, doing the programming things and then it reboots (sdcard still inside).
but all i can see at this time is "no signal".

tcpdump i showing this:
Code: [Select]
          file "/tftpboot/pxelinux.0"
          file "/tftpboot/pxelinux.0"
          file "/tftpboot/pxelinux.0"
    192.168.80.198.49153 > 0.0.0.0.tftp: [no cksum]  35 RRQ "71638953/start.elf" octet tsize 0
    192.168.80.198.49154 > 0.0.0.0.tftp: [no cksum]  29 RRQ "autoboot.txt" octet tsize 0
    192.168.80.198.49155 > 0.0.0.0.tftp: [no cksum]  27 RRQ "config.txt" octet tsize 0
    192.168.80.198.49156 > 0.0.0.0.tftp: [no cksum]  29 RRQ "recovery.elf" octet tsize 0
    192.168.80.198.49157 > 0.0.0.0.tftp: [no cksum]  26 RRQ "start.elf" octet tsize 0
    192.168.80.198.49158 > 0.0.0.0.tftp: [no cksum]  26 RRQ "fixup.dat" octet tsize 0

Should the other files You had in Your tcpdump and that gets transferred be also in the /tftboot/ folder?

I will try to install a shiny new linuxmce system on sunday on my old 12.04 partition.
maybe i wrecked something else...

thanks again!

12
Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 23, 2016, 10:09:04 am »
okay thanks.

the last boot attempts i was using the sdcard from the wiki.

but  it didn`t show the rainbow. my lcd is just saying "no signal".

i will try to reinstall the default image and report back.

there must be away.... :)

13
Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 22, 2016, 10:31:26 am »
Hello,

i tried the sd card provided by the wiki.
But with no luck.

And i run DHCP_config.sh and restarted the service.
It just won`t boot.

I did a tcpdump again.
Searching with wireshark for DHCP, this is what i found:

Code: [Select]
1081 24.256112 0.0.0.0 255.255.255.255 DHCP 362 DHCP Discover - Transaction ID 0x26f30339
1167 29.594817 0.0.0.0 255.255.255.255 DHCP 362 DHCP Discover - Transaction ID 0x26f30339
1201 30.596061 192.168.80.1 192.168.80.143 DHCP 342 DHCP Offer    - Transaction ID 0x26f30339
1300 35.592479 0.0.0.0 255.255.255.255 DHCP 362 DHCP Discover - Transaction ID 0x26f30339
1319 36.593282 192.168.80.1 192.168.80.144 DHCP 342 DHCP Offer    - Transaction ID 0x26f30339
1390 40.592633 0.0.0.0 255.255.255.255 DHCP 362 DHCP Discover - Transaction ID 0x26f30339
1421 41.594131 192.168.80.1 192.168.80.145 DHCP 342 DHCP Offer    - Transaction ID 0x26f30339
1908 45.592694 0.0.0.0 255.255.255.255 DHCP 362 DHCP Discover - Transaction ID 0x26f30339
2003 46.593630 192.168.80.1 192.168.80.146 DHCP 342 DHCP Offer    - Transaction ID 0x26f30339


Edit:
Found this, filtering for the raspberrys mac:

Code: [Select]
1328 43.276709 0.0.0.0 255.255.255.255 DHCP 362 DHCP Discover - Transaction ID 0x26f30339
1344 44.278321 192.168.80.1 192.168.80.140 DHCP 342 DHCP Offer    - Transaction ID 0x26f30339
1458 48.276786 0.0.0.0 255.255.255.255 DHCP 362 DHCP Discover - Transaction ID 0x26f30339
1474 49.278368 192.168.80.1 192.168.80.141 DHCP 342 DHCP Offer    - Transaction ID 0x26f30339
1558 54.276634 192.168.80.141 0.0.0.0 TFTP 77 Read Request, File: 71638953/start.elf, Transfer type: octet, tsize=0
1583 55.293906 192.168.80.141 0.0.0.0 TFTP 71 Read Request, File: autoboot.txt, Transfer type: octet, tsize=0
1609 56.294059 192.168.80.141 0.0.0.0 TFTP 69 Read Request, File: config.txt, Transfer type: octet, tsize=0
1627 57.294111 192.168.80.141 0.0.0.0 TFTP 71 Read Request, File: recovery.elf, Transfer type: octet, tsize=0
1640 58.294142 192.168.80.141 0.0.0.0 TFTP 68 Read Request, File: start.elf, Transfer type: octet, tsize=0
1666 59.913080 192.168.80.141 0.0.0.0 TFTP 68 Read Request, File: fixup.dat, Transfer type: octet, tsize=0

Destination/Source is the mac-address of my raspberry.

I hope this is of any help. i am definitly in no way an expert.
just playing around.

Thanks for Your time!


14
Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 21, 2016, 06:28:25 pm »
thanks for the quick reply.

here is the pastebin (ls -lah /tftpboot/)

http://paste.ubuntu.com/23211976/

and this is /tftboot/rpi

http://paste.ubuntu.com/23211995/

i deleted the manually created device (moon142) via webadmin.

is it okay that there is still this link:
Code: [Select]
boot -> /usr/pluto/diskless/142/boot
i tried booting with a sdcard only having bootcode.bin on it.
but i will try that one from the wiki, when i am at home.

would doing a tcpdump again help?

Thanks for Your help!


15
Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: September 21, 2016, 02:57:51 pm »
Absolut fantastic work!
Thank You very much! A dream comes true! :)
It is near to that point that i would label this whole linuxmce thing as magical...
Affortable and noiseless md for every room. fantastic!

I am already trying to get it working.

Using a raspberry pi model 3b.

Updated and upgraded my linuxmce 14.04 system to the newest available point:
i386 - 201609172308+325de35d (besides the webadmin and the weborbiter are showing older version numbers)

Prepared the raspberry for network/usb booting (it is showing 0x3020000a).
I have not used the sdcard mentioned in the wiki. I used the way it was described there:
https://www.raspberrypi.org/documentation/hardware/raspberrypi/bootmodes/msd.md
Should be the same result?

Installed the default netboot kernel package.

Changed the TARGET_TYPE. (Do i need to change it back after i have created the tarball?)

The raspberry didn`t get recognized. So i even tried to add the template manually, providing a mac address and an ip address.

it won`t boot.

I made a tcpdump on the core/hybrid and all i could find is this:

Code: [Select]
13:48:52.061106 IP moon142.49154 > 0.0.0.0.tftp: 29 RRQ "autoboot.txt" octet tsize 0
13:48:53.061145 IP moon142.49155 > 0.0.0.0.tftp: 27 RRQ "config.txt" octet tsize 0
13:48:54.061306 IP moon142.49156 > 0.0.0.0.tftp: 29 RRQ "recovery.elf" octet tsize 0
13:48:55.061453 IP moon142.49157 > 0.0.0.0.tftp: 26 RRQ "start.elf" octet tsize 0
13:48:56.061562 IP moon142.49158 > 0.0.0.0.tftp: 26 RRQ "fixup.dat" octet tsize 0

I copied something via tft to the core and vice versa without any problem.

I don`t know what i can do. Maybe reinstall everything? Did the netboot kernel package changed since last week? Is it a good idea to reinstall that?

I would really like to have a noiseless raspberry as md.
And i really would be very thankfull for any idea/suggestion/hint!

But again thanks!




Pages: [1] 2 3 4