Raspberry pi 2 installation

[hcaine]

The links to download the images on the page do not work

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

Speaking about this links:
Setup Steps
Download the rpi2 uSD card image (raspbian (recommended)
Download the rpi2 uSD card image (raspbian (deprecated)
Download the rpi2 uSD card image (ubuntu (on your own here atm))

[Marie.O]

I've notified our webmaster to look at it. Unfortunately, he is currently on vacation in Australia, and I have no idea if he has access. Might be a week or two, before he returns.

[hcaine]

Thank you for your efficiency posde.

[phenigma]

Those links should point to my personal dropbox account at the moment.  I'm not sure why they would not be working, I'll check.  And we'll move them over to linuxmce servers as well.

J.

[phenigma]

I've re-pointed the links back to my dropbox (not sure why they changed).  They should be active again.

J.

[Marie.O]

They were moved by me, as they belong on one our servers. ocho is working on fixing the issue.

[omskie]

hcaine did you get your RPI2 working?

In my case, installation went well but the screen appears small & mouse clicks doesn't seem to work, but the keyboard does.

I wonder if you are experiencing the same thing...

[phenigma]

Ick.  Ok, run /usr/pluto/bin/SetupAudioVideo.sh which should setup your AV settings.  Do a full regen of the rpi orbiter.  Check if the file /etc/asound.conf exists on the pi after SetupAudioVideo runs and remove it if it does, we don't want it there.  Check the AV setting for the MD and for the Orbiter on the MD, see if they match.  They should be the same resolution, and should be set by SetupAudioVideo. 

If you continue to have issues then run the following:

Code Select Expand


cat /proc/cmdline


and paste the output here. 

You'll find the mouse is probably working, but the mouse thinks the display is full screen not small.  So if you click where the button would be if it was full screen it likely works. 

Let me know how things go!

J.

[omskie]

Hi Phenigma,

Thanks for your help, as suggested I just changed my Orbiter size to 1080p & did a full regen.

Also run SetupAudioVideo.sh on the MD & deleted asound.conf, then router reload.  But the video setting on the MD is still empty.

The output of /proc/cmdline:

Code Select Expand


root@raspbian:~# cat /proc/cmdline
dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2709.boardrev=0xa01041 bcm2709.serial=0x1bbd0df0 smsc95xx.macaddr=B8:27:EB:BD:0D:F0 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000  dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootwait


Anyways I'm happy with what I have now.  Thanks a lot...

[phenigma]

Thanks for the feedback, one more question: Is this the jessie image you used?  I need to update that image so SetupAudioVideo works properly in jessie.

J.

[omskie]

Yup its jessie.

[phenigma]

Thanks!  There'll be a permanent fix for this out soon.

J.

[SBCC]

Hi Jason

Thanks for all your hard work!!!

Using RPI 2 Jessie, I get an error for a GSD device with a simple routine as:

Code Select Expand

375
def log(line)
# This function logs a line to the log file of the device
log = File.open("/var/log/pluto/" + device_.devid_.to_s + "_Generic_Serial_Device.log", "a")
log.puts Time.now.to_s + " (Ruby script):" + line.to_s
log.close
end


def time_check()
now = Time.new

if ((@last_check + 15) < now)
log(Time.now)
@last_check=Time.now
end


end

355
@last_check = Time.now

351
time_check()


The error comes after running anywhere from 1 minute to 2 hours and not consistent. I double checked this with a separate RPI 2:

Code Select Expand

2015-09-21 12:20:10 +0000 (Ruby script):2015-09-21 12:20:10 +0000
2015-09-21 12:20:26 +0000 (Ruby script):2015-09-21 12:20:26 +0000
01 09/21/15 12:20:28.313 A CRITICAL ERROR HAS OCCURED (CHECK YOUR RUBY CODE) <0x740ff450>
Return code: 1

I noticed that the Ruby version on the RPI is not the same as the core. Not sure if that matters.

Thanks

Jim

[phenigma]

Hi,

Ruby has three different versions out there atm: Ruby 1.8 on intrepid and lucid, Ruby 1.9.1 on precise and wheezy, Ruby 2.0 on trusty and jessie.

We are seeing intermittent issues on GSD devices currrently.  We could use assistance in tracking this down as not a lot of people are reporting.  I'm aware of issues, and I am experiencing these issues at seemingly random intervals from minutes to days.  I have not had any time to dig into it yet.  Thanks for reporting!  And thanks for testing!

J.

[SBCC]

Let me know how I can help. I am trying wheezy now on the RPI 2. I'll let you know what I see there if anything.

Thanks again!!!