LinuxMCE Forums
General => Installation issues => Topic started by: hcaine on September 09, 2015, 08:35:32 pm
-
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))
-
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.
-
Thank you for your efficiency posde.
-
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.
-
I've re-pointed the links back to my dropbox (not sure why they changed). They should be active again.
J.
-
They were moved by me, as they belong on one our servers. ocho is working on fixing the issue.
-
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...
-
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:
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.
-
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:
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...
-
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.
-
Yup its jessie.
-
Thanks! There'll be a permanent fix for this out soon.
J.
-
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:
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:
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
-
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.
-
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!!!
-
Thanks! Feel free to jump into IRC freenode #linuxmce
J.
-
Hi,
sorry to disturb, I'm trying to install rpi2:
jessie does't boot (25-10-15)
wheezy and ubuntu end up in a login that no password seem to work.
can somebody help?
thanks
Nelsito
-
The jessie image has successfully been installed by a few users at the moment. The other images are old or for those who are testing/developing.
Can you be more specific than "doesn't boot" ?
J.
-
Hi Phenigma,
with jessie when I boot the card with rpi2 it stops with this error:
ERR: interactor has not yet created ' /etc/Disked_DeviceID' .
# FIRSTBOOT NOT COMPLETE, CANNOT CONTINUE LOADING LINUXMCE.cat: /etc/pluto/Disked_DevData: No such file or directory
IP: 192.168.1.151 mac b5:27:eb:29:59:de; Gateway: 192.168.1.254; DeviceData: armv7l|9|0|7|22|262| jessie|209|Raspbian|; DT/endor:rpi_b;Command: select
connect: Connection times out
with the other images it boots to a login but I don't know the password.
I have intalled 12.04 Hybrid, DHCP
I am new to Linux and MCE so thanks in advance for your help.
regards
Nelsito
-
ERR: interactor has not yet created ' /etc/Disked_DeviceID' .
# FIRSTBOOT NOT COMPLETE, CANNOT CONTINUE LOADING LINUXMCE.cat: /etc/pluto/Disked_DevData: No such file or directory
IP: 192.168.1.151 mac b5:27:eb:29:59:de; Gateway: 192.168.1.254; DeviceData: armv7l|9|0|7|22|262| jessie|209|Raspbian|; DT/endor:rpi_b;Command: select
connect: Connection times out
Welcome to LinuxMCE!!
Based on the IP address and Gateway it appears that you are trying to boot the rpi on the external network rather than the internal network. Make sure that your rpi is connected to the internal network of lmce or it will not be able to connect to the core.
Jason
-
Hi phenigma,
I changed the rpi to be inside internal network, but still could not install.
first try, it booted and announced to mce, I chose template as MD, and it created template. the router was reloaded, and the pi booted again but didn´t finish install. I repeted the proccess a lot of times but no success. deleted the template as md, to start fresh, but it never showed up again in router as md to choose. showed twice as a windows share, that i ignored.
I have now 14.04, and updated just before the last try, still no joy.
it stops responding and last lines:
1 12/12/15 12:40:04 SetupAudioVideo (server) Starting
1 12/12/15 12:40:04 SetupAudioVideo (server) '
1 12/12/15 12:40:04 SetupAudioVideo (server) DBSetting: Reboot: Script Path: /usr/pluto/bin/
[ ok ] Setting Coredump Location: /usr/pluto/bin/corefile.sh.
[ ok ] Configure Device Changes: /usr/pluto/bin/Config_Device_Changes.sh.
[ ok ] Starting LinuxMCE Launch Manager: /usr/pluto/bin/LaunchManagerDaemon.sh.
[ ok ] Enable Wake-on-LAN: /usr/pluto/bin/enable_wol.sh.
[ ok ] Configuring Pluto Storage Devices: /usr/pluto/bin/StorageDevices_Setup.sh.
[ ok ] Starting Status Radar: /usr/pluto/bin/StorageDevices_StatusRadar.sh.
[ ok ] Reporting Machine Status: /usr/pluto/bin/Report_Machine_Status.sh.
[ 993.667753] init: smbd main process (511) killed by TERM signal
[ 1055.567997] init: smbd main precess (14223) killed by TERM signal
and stops there...
-
That is odd. Many people have been successful and my latest test was flawless. I'm at a loss at the moment as to what could be interfering on your system.
J.
-
Hi phenigma,
do you think it can be the ethernet switch. i'm using an HP procurve 2500PWR, I think it acquires an IP.
well what I did was disconnect every other equipment from the switch, and leave only the pi, and did a new card, and booted. it ends like this:
[ ok ] Setting Coredump Location: /usr/pluto/bin/corefile.sh.
[ ok ] Configure Device Changes: /usr/pluto/bin/Config_Device_Changes.sh.
[ ok ] Starting LinuxMCE Launch Manager: /usr/pluto/bin/LaunchManagerDaemon.sh.
[ ok ] Enable Wake-on-LAN: /usr/pluto/bin/enable_wol.sh.
[ ok ] Configuring Pluto Storage Devices: /usr/pluto/bin/StorageDevices_Setup.sh.
[ ok ] Starting Status Radar: /usr/pluto/bin/StorageDevices_StatusRadar.sh.
[ ok ] Reporting Machine Status: /usr/pluto/bin/Report_Machine_Status.sh.
ERROR 1045 (28000): Access denied for user 'root'@'192.168.80.3' (using password: NO)
[ 993.667753] init: smbd main process (511) killed by TERM signal
[ 1055.567997] init: smbd main process (14223) killed by TERM signal
I rebooted the pi a few times and also reloaded the router.
The very first time I tried the core acquired the pi and prompted a choice for MD or qMD or squeezebox, but now it doesn't even if I try everything from scratch (new card and delete all devices in core)
thanks
cheers
-
Not your switch. You've identified where the issue is though :)
ERROR 1045 (28000): Access denied for user 'root'@'192.168.80.3' (using password: NO)
This line here means that database access has not been granted for this media director. That should happen automatically in Disked_Setup.sh on the core when the MD is first announced to the router. Something must have failed there, or that's my primary theory atm.
On the core try running:
/usr/pluto/bin/Diskless_Setup.sh
/usr/pluto/bin/Disked_Setup.sh
and see if any errors pop up.
Now though... check in webadmin Advanced->Configuration->Unknown Devices and see if the Pi's MAC address is in there. Remove it from that list if it is and it'll start showing back up again.
It looks like *almost* everything has gone perfectly.
I hope that helps.
J.
-
Hi phenigma,
I think I might have identified the problem. My core has only one NIC,so I'm using a USB adapter for second card, that I think is badly configured. I'm no expert but, I had the onboard nic conected to adsl router and the usb nic as internal nic, and three devices conected to the switch (the rpi i was Trying to boot into LMCE, a VU Zero receiver, and a hummingboard running openelec).Both the humming board and the VU zero got internet through the Core. So I assumed everything was ok with the usb card. I even reinstalled the core...
Like this, the core assumes IP 192.168.1.172 from my adsl router.
if I change the cable, connect the adsl router to the usb nic, I still get internet, but going to webadmin network config, it shows an ip that is not in my adsl router range (169.128.8.69), and the core identifies other devices that run in the adsl router network (PC, cable box, etc.)
so I'M thinking the USb nic doesn't show the correct IP adress and when the pi boots second time is doesn't find the core.
I'd Like to knoe 2 thingd if you can help. First is if to boot pi as MD do I have to have Internet on the core, or can I just update the core and then use the on board nic as eth1, and boot the MD.?
and if I chage the onboard nic to eth1 and the usb to eth0, if it is badly configured but still has internet is that a problem?
don´t mind of other devices because this core is only for testing purposes, so I can test before I use it in me home setup.
I'd like to know if you think this might really be the problem, and about the changes to do, or if there is another way.
Thanks
NM
-
If you change your internet around from one nic to the other you should use the "Swap Devices" button in the webadmin config for the network.
It is best if you have internet during the rpi setup/installation but, to my recollection, it is not required to boot it.
I hope that helps.
J.
-
well...the usb to ethernet that i have just doesn't work with LMCE. I checked compatible but the gembird nic-U1 is not available anymore. so I have a wireless adapter from asus i think works with LMCE (wl-167g), and i'd like to use it as my external nic. the probles is I've searched a lot in the forum and didin't find nothing that shows how to choose the network, and wireless password from within webadmin.
do you know any such post please rederect me, or if you can just tell me where to go.
thanks
NM
-
atm there is no direct support for wireless network adapters inside the LinuxMCE UI