• 1
  • 288
  • 289
  • 290(current)
  • 291
  • 292
  • 553
Linux ChromeBox Kodi E-Z Setup Script (LibreELEC/Linux+Kodi) [2017/02/21]
Well I guess I'm failing at the mounting the openelec partition part.

I'm not sure what option I need to start with to get there. Any of the first two options "install lubuntu" or "try lubuntu" immediately make the system reboot.

All of the other options seem to have nothing to do with this.

I'm pretty new to this stuff. I guess I'll have to take the long route, clear the chromebox, run the script and just continually do this until it accepts an advancedsettings.xml file.
Reply
(2015-05-05, 21:13)Living Legend Wrote: Well I guess I'm failing at the mounting the openelec partition part.

I'm not sure what option I need to start with to get there. Any of the first two options "install lubuntu" or "try lubuntu" immediately make the system reboot.

All of the other options seem to have nothing to do with this.

I'm pretty new to this stuff. I guess I'll have to take the long route, clear the chromebox, run the script and just continually do this until it accepts an advancedsettings.xml file.

sounds like there's an issue with the way you created the lubuntu installation media. Use UUI (universal usb installer) as recommended.

you are running a standalone OpenELEC setup, correct? Then you're past the point of needing (or being able to use) the script. Just boot the OE USB installer and reinstall like you did before. Or if you don't have the USB installer, create one on another PC using the instructions linked in the wiki
Reply
(2015-05-05, 21:17)Matt Devo Wrote:
(2015-05-05, 21:13)Living Legend Wrote: Well I guess I'm failing at the mounting the openelec partition part.

I'm not sure what option I need to start with to get there. Any of the first two options "install lubuntu" or "try lubuntu" immediately make the system reboot.

All of the other options seem to have nothing to do with this.

I'm pretty new to this stuff. I guess I'll have to take the long route, clear the chromebox, run the script and just continually do this until it accepts an advancedsettings.xml file.

sounds like there's an issue with the way you created the lubuntu installation media. Use UUI (universal usb installer) as recommended.

you are running a standalone OpenELEC setup, correct? Then you're past the point of needing (or being able to use) the script. Just boot the OE USB installer and reinstall like you did before. Or if you don't have the USB installer, create one on another PC using the instructions linked in the wiki

I'm actually running dual boot with Chrome OS. I guess there's probably an easier way to access this partition from the Chrome OS?
Reply
(2015-05-05, 21:26)Living Legend Wrote: I'm actually running dual boot with Chrome OS. I guess there's probably an easier way to access this partition from the Chrome OS?

oh, well that explains why you're not able to boot the lubuntu USB - certain bootloaders don't work well with the stock firmware, and often you need additional kernel parameters to boot Linux

to mount the partition in ChromeOS, open a shell terminal like you would to open the script, then:

Code:
mkdir /tmp/storage
sudo mount /dev/sda7 /tmp/storage
rm /tmp/storage/.kodi/userdata/advancedsettings.xml

then reboot into OE and try again. You could edit the file from ChromeOS vs deleting it, but if you don't know how to use vi, it's better you don't.
Reply
(2015-05-05, 21:37)Matt Devo Wrote:
(2015-05-05, 21:26)Living Legend Wrote: I'm actually running dual boot with Chrome OS. I guess there's probably an easier way to access this partition from the Chrome OS?

oh, well that explains why you're not able to boot the lubuntu USB - certain bootloaders don't work well with the stock firmware, and often you need additional kernel parameters to boot Linux

So with that said, do I have any options for accessing the any files from the openelec partition such as the log or the advancedsettings.xml file? Or am I out of luck and I need to re run the script?
Reply
see edit above
Reply
(2015-05-05, 21:37)Matt Devo Wrote:
(2015-05-05, 21:26)Living Legend Wrote: I'm actually running dual boot with Chrome OS. I guess there's probably an easier way to access this partition from the Chrome OS?

oh, well that explains why you're not able to boot the lubuntu USB - certain bootloaders don't work well with the stock firmware, and often you need additional kernel parameters to boot Linux

to mount the partition in ChromeOS, open a shell terminal like you would to open the script, then:

Code:
mkdir /tmp/storage
sudo mount /dev/sda7 /tmp/storage
rm /tmp/storage/.kodi/userdata/advancedsettings.xml

then reboot into OE and try again. You could edit the file from ChromeOS vs deleting it, but if you don't know how to use vi, it's better you don't.

I'm used to using nano vs vi so I'll stick with winscp and upload a new version.

I'm assuming this is just a temporary mount?
Reply
(2015-05-05, 21:44)Living Legend Wrote: I'm used to using nano vs vi so I'll stick with winscp and upload a new version.

I'm assuming this is just a temporary mount?

correct, it goes away upon reboot
Reply
This is very weird.

So I can finally view the log file and I see:

20:21:19 T:140242787100544 NOTICE: Loaded settings file from special://xbmc/system/advancedsettings.xml
20:21:19 T:140242787100544 NOTICE: Contents of special://xbmc/system/advancedsettings.xml are...
<?xml version="1.0" encoding="UTF-8" ?>
<advancedsettings>
<showexitbutton>false</showexitbutton>
<cputempcommand>cputemp</cputempcommand>
<gputempcommand>gputemp</gputempcommand>
<video>
<latency>
<delay>0</delay>
<refresh>
<min>23</min>
<max>24</max>
<delay>175</delay>
</refresh>
</latency>
<busydialogdelayms>750</busydialogdelayms>
</video>
<samba>
<clienttimeout>30</clienttimeout>
</samba>
<network>
<readbufferfactor>4.0</readbufferfactor>
</network>
</advancedsettings>

Then it begins to load my XML file.

20:19:08 T:139882818934656 NOTICE: Loaded settings file from special://profile/advancedsettings.xml
20:19:08 T:139882818934656 NOTICE: Contents of special://profile/advancedsettings.xml are...
<advancedsettings>
<videodatabase>
<type>mysql</type>
<host>192.168.1.3</host>
<port>3306</port>
<user>kodi</user>
<pass>kodi</pass>
</videodatabase>
<musicdatabase>
<type>mysql</type>
<host>192.168.1.3</host>
<port>3306</port>
<user>kodi</user>
<pass>kodi</pass>
</musicdatabase>
</advancedsettings>

Why is it trying to load this different advancedsettings.xml file first?
Reply
It's loading from the default file, the copy in userdata is loaded later in the startup process
Reply
(2015-05-05, 22:32)Matt Devo Wrote: It's loading from the default file, the copy in userdata is loaded later in the startup process

So is this what's causing the error? Trying to load two advancedsettings.xml files? I'm relatively sure my other devices only load the one I've uploaded...

And if that's the case, how do I get it to bypass the first one?
Reply
No, that's normal
Reply
(2015-05-05, 22:44)Matt Devo Wrote: No, that's normal

Well I'm at a loss I guess.

I see no errors with the XML file.

And I'm going bonkers here with SSH. I connect with WinSCP and then within a minute it disconnects me and when I try to relog in it says "access denied"!
Reply
I suggest you put a complete debug log on pastebin and provide the link.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Reply
Hi All

I wonder if anybody here can help me. I have googled and googled to death but getting nowhere.

I purchased my chromebox refurbished (As new) and to be fair it appeared new. Installed Openelec and got kodi going everything running perfect no issues.

Few days later i notice the box would suddenly restart and then sometimes just turn itself off. This happened frequently in a short period at one point but then stopped.

I couldnt pin it down what was causing it but noticed that if i left the box running overnight nothing would happen. so it was only when navigating about, installing add ons , loading videos etc etc but no pattern.

I hoped it would be software issue so i reset it back to factory and then re-installed openelec in a dual boot setup. Same again - worked fine for awhile and then started doing it again. Oddly for last 2 days its been running fine with no shutdowns or restarts. I turned the box off today before work - since tunrirng it back on its doing it again like before.

Has anybody heard or run into anything like this before?

Does this sound like a hardware issue ? Any pointers or ideas would really help as i need to decide whether to contact the seller and try and get a refund.

Thanks in advance all!!
Reply
  • 1
  • 288
  • 289
  • 290(current)
  • 291
  • 292
  • 553

Logout Mark Read Team Forum Stats Members Help
ChromeBox Kodi E-Z Setup Script (LibreELEC/Linux+Kodi) [2017/02/21]37