Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[kpeters59]

I'm new to jriver and even newer to getting it to run on Raspberry PI.

I installed the latest Raspbian on a Raspberry PI 2.   Then I immediately installed XVNC for RDP support because I have limited keyboards and because Mediacenter will need to be headless.

We're experimenting with how we'd like to end up using Mediacenter.  Currently we're trying MC21 running on the 'Family' Windows 10 PC and are successfully  getting the Oppo 103 to render.  We also have an older Dual-Core Macbook we might use.  But, we also thought maybe using a PI would be a fine choice since the Oppo will be the renderer and all the Media Files are on a NAS Drive.

So, I got MC22 installed and (apparently) if I launch it from the console, it seems to load to the 'nag' screen and I can click the continue button and get to the main MC screen.  Great!  But, if instead I try to launch from the XVNC login, the MC window never fully loads and stays a washed-out white screen and never presents any text or buttons to click.  Randomly clicking around on it never produces the desired result.

Anybody got a clue how to get past this?  I'm posting this now from the PI via RDP on my Windows box using Firefox/IceWeasel, so I know XVNC is (mostly) OK.  Maybe some setting I'll never find on my own?

Eventually, we'll want a fully 'headless' install as we just want to access the Server via an iPad.

Thanks,

-Kyle

[kpeters59]

I thought maybe my config.txt file might be hepful?

I did (kind of randomnly) change the HDMI settings...to no effect...

# For more options and information see
# http://www.raspberrypi.org/documentation/configuration/config-txt.md
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
 no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

framebuffer_depth=32
framebuffer_ignore_alpha=1


Thanks,

-Kyle

[mwillems]

I'm a little confused because you seem to be using the terms VNC and RDP interchangeably, but they're distinct protocols and not all software that supports one supports the other.  Xvnc for example is an X11 server with vnc capability that doesn't (to my knowledge) support RDP, so I'm a little confused about your setup.  

Have you tried using the basic VNC method described in the quick start guide stickied at the top of the forum using tightvncserver and a windows vnc viewer?  VNC is easy, but my recollection is that there were some strange quirks getting RDP to work (assuming you actually mean the RDP protocol). I only use VNC myself so I can't offer much advice on RDP.  I can confirm that the step by step instructions for VNC in the quick start guide work perfectly, I'm currently looking at MC on a pi via the TigerVNC client for windows.  

If you could specify which specific software you're using on both ends of the connection, and what protocol you're using, I can offer more specific advice.

[kpeters59]

I used this to setup RDP using XVNC:

http://www.circuitbasics.com/access-raspberry-pi-desktop-remote-connection/


It seems to work as expected.  And since I had RDP and about a dozen desktops I connect to regularly and I don't have VNC installed, it seemed like a good choice for me.  I'll have to try a VNC client.

Thanks,

-Kyle

[kpeters59]

I was able to connect and get MC22 to launch succesfully under TightVNC.

Wow! did lots of goofy things happen running 2 different VNC installs.  I was using RDP to install TightVNC and launched it.  Then I connected on port 5901 (Desktop 1?), but it seemed to launch a 3rd desktop?  The (unlogged on) console, the RDP session and the TightVNC desktop.  When I went to logoff of the the TightVNC session, it logged off the RDP session...!

Not that that really matters.  Ultimately, I'd prefer to use RDP if it was possible to solve the issue with it.  I often find myself at workstations that are not mine.  Most of them already have RDP installed, so connecting to the already setup machines is pretty straight-forward if I don't have to install software...

Thanks,

-Kyle

[bob]

Whatever you do make sure it's using 24 bit color. The white screen thing sounds exactly what MC looks like on a 16 bit color display.

[kpeters59]

Well, I tried that straight-away and it worked!

Sweet!

I'll give it a workout and see if I can break it further...

Thanks,

-Kyle