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 - phenigma

Pages: 1 2 [3] 4 5 ... 108
31
Installation issues / Re: "PXE-E77: Bad or missing discovery server list".
« on: September 01, 2016, 05:01:24 pm »
There have been no changes to anything in the main repository related to pxe booting.  There are changes coming but they're are not in the main repository yet.  The atftpd server outputs to syslog.

J.

32
Installation issues / Re: Denon Receiver Control over Ethernet
« on: August 29, 2016, 02:47:31 am »
Phenegma,

Please follow up on your comment regarding $?. Please check the file for this script in your installation. I did not change this.

After many days, the detection script has not run. Is there a way to trigger?

CDM
The PNP scripts will run after a router reload on each MD that has an un-allocated (unused) serial port.

First thing I see now that I have some time is that you seem to have added the "Resp=$?" portion to the echo command, it will not give you the output you are expecting, but the output of the IF statement result.  The "$?" returns the exit code of the last command executed. 

Second thing is "PWSTANDBY\rZMOFF\rZ2OFF\rPWON\rZMON\rZ2ON\r", which shows in your testing output is not the same as what the script you posted is sending, you must be testing with a different script.  This script should be short and only enough to confirm that it responds to commands, adding in zone power off/on is adding a lot of extra commands that are not necessary for detecting the receiver.

You also indicate that the script works 'sometimes' but not others.  This is usually a result of serial based devices that decide not to respond, they can get 'confused' usually based on some bad codes or text sent to its' port.  Some serial devices are really susceptible to this.  If the script works 'sometimes' I would suggest that the exact sequence of commands could be altered or more pause/delay after each command.  The receiver needs to have time to respond prior to another command being sent.

The Denon detection script has worked for me here on my Denon 3311CI.  That was when I first purchased the amp, since then it does not need to be re-detected.  Honestly my best recommendation is to add the device manually if the detection script isn't doing its' thing properly.  After that it's never required again.

J.

33
Installation issues / Re: 14.04 Installation - More Minor Issues
« on: August 27, 2016, 11:50:42 pm »
Great stuff!  Have you done a search for a newer PWC driver at all?

Sent from my Nexus 5 using Tapatalk


34
Installation issues / Re: 14.04 Installation - More Minor Issues
« on: August 26, 2016, 01:11:44 am »
1. Mythfrontend does not save settings. I have changed a few things in the front end, in particular the scaling of the video image as negative percents. These parameters are not saved, even when I exit the frontend setup gracefully.

Ensure that auto configuration is turned off for mythtv, lots of the scripting is broken and may be over-writing your settings.

2. Cannot install a Logitech Quickcam. There is a wiki page for this here:

http://wiki.linuxmce.org/index.php/Logitech_QuickCam_Sphere

I followed the instructions, substituting "**PWC Camera Drivers" for "PWC Camera Drivers" in the instructions. Only the ** version appeared in the dropdown when building the device template. The motion wrapper seems to work fine: I get a grey square with some text overlayed when I choose the camera in the Security scenario. The LED on the camera does not illuminate, as it did when I have this same camera connected to my old 810 installation. I think this means that the camera driver is not working.

The PWC driver was discontinued in 2006 and has failed to build since 1004.

3. The system has still not discovered my Denon 2307 receiver over RS-232. The discovery script does not seem to be running. How can I initiate it? As indicated by Phenigma in an earlier post, there is a question about the syntax in the discovery script, assuming that I can get the script to run again.

I'd forgotten about that.  With a quick second look I think the scripts are okay logic wise, although have a strange use of $?.  Perhaps you can create a issue in gitlab with your findings from the scripts so far.  I can then see what I get from my Denon.

J.

35
Users / Re: Raspberry Pi v3 as media director - slow nfs speed
« on: August 22, 2016, 10:45:49 pm »
I have used both, I created the methods to boot the rpi's.  The currently recommended method is diskless style booting and that will always be the preferred method, now that it is available again.  That being said the updated files to use the diskless boot are not yet in the repository.

J.

36
Users / Re: Raspberry Pi v3 as media director - slow nfs speed
« on: August 22, 2016, 01:42:12 am »
I usually attribute this to bad cabling or switches.  I can say that I have absolutely no problems accessing/playing media with my RPi3s.

J.

37
Developers / Re: booting 1604
« on: August 22, 2016, 01:37:25 am »
The verification is due to spamming, it goes away after making a few posts. 

And as Alblasco points out 1604 has a couple of bugs that prevent daily use atm.  And due to new boot methodologies we may need to alter our dvd creation.  Net install for 1604 can be accomplished.

J.

38
Installation issues / Re: Denon Receiver Control over Ethernet
« on: August 17, 2016, 01:54:41 am »
As soon as I have a moment to I will have a look.

Sent from my Nexus 5 using Tapatalk


39
Installation issues / Re: Denon Receiver Control over Ethernet
« on: August 13, 2016, 10:41:18 pm »
You're issue $? incorrectly.  I'm on my phone an really unable to respond more than that.  I'll try to elaborate whenever I get home.

Sent from my Nexus 5 using Tapatalk


40
Installation issues / Re: Zoom & Aspect Controls In Xine Not Working
« on: August 13, 2016, 10:37:41 pm »
I believe this is an issue in libxine.  The orbiter controls are passed to the player but only work with certain video types.

Sent from my Nexus 5 using Tapatalk


41
Installation issues / Re: Video Quality & Sound with Intel Drivers
« on: August 13, 2016, 10:36:28 pm »
Glad to here it!  Have fun!

Sent from my Nexus 5 using Tapatalk


42
Users / Re: Need some dedicated testers.
« on: August 08, 2016, 09:19:59 pm »
As always you can keep up to date on when new packages are pushed for users by watching: http://wiki.linuxmce.org/index.php/LinuxMCE-1204/1404_Updates#Upcoming_fixes...  No package listed there means it is NOT available in the repository yet.

J.

43
Users / Re: autotagger
« on: August 08, 2016, 09:18:13 pm »
Autotagger *does* run, and spits out that error ;)  Follow the tutorials for how to use it, feel free to check if an issue already exists for the 'bug'.

J.

44
Users / Re: Need some dedicated testers.
« on: August 08, 2016, 08:17:46 pm »
Nice!

Sent from my Nexus 5 using Tapatalk


45
Installation issues / Re: Video Quality & Sound with Intel Drivers
« on: August 08, 2016, 08:14:12 pm »
Since I'm not actually running any newer Intel video I'm only relating what I've heard.  fbdev is a video driver, like Intel or nvidia.  va-api is the acceleration mechanism that Intel uses, like vdpau on Nvidia.  Tearing is related to vsync and must movies are not recorded in the same refresh rate your monitor/card regularly uses.  This option likely adjusts the monitor vsync to equal the film's frame rate, which eliminates tearing.  This is not desirable for most other day to day tasks, or gaming, which wasn't the highest possible refresh rate.  I know the Intel driver is fubar in 1604 and tschak uses frame buffer on his NUCs with newer Intel video built in.

Sent from my Nexus 5 using Tapatalk


Pages: 1 2 [3] 4 5 ... 108