(2017-03-01, 02:42)kidmoe Wrote: [ -> ]Hi everyone...my first post....First of all, big thanks to Matt for creating this script and giving us great operating system flexibility for our boxes/books.
Now, I have a Braswell Samsung Chromebook 3 (xe500c13-k02us) that my son trashed the screen on so I have decided to convert it to a KODI box running into a 1080p Panasonic Plasma via hdmi. I downloaded the script and decided to do a dual boot with LibreElec on a USB stick and the install went perfectly and when I CTRL-L it boot's straight into LibreElec. So far,so good. The issue I'm having is when LibreElec boots it does so at the resolution of the Chromebook, which is 1366x768. So the Chromebook screen is filled completely but the image on the plasma is only a smallish window that occupies about a quarter of the upper left part of the screen. Not a problem, i'm thinking, so I head into the display area of the system settings to change the resolution but the monitor is listed as default and the maximum resolution selection is 1366x768 and not the 1080p that my tv is capable of. So I switch the monitor from default to HDMI2, which is my plasma, but as soon as I do I get a black, blank screen on both tv and chromebook screen and no image and there it stays. I've tried and tried but just can't seem to sync this Samsung book up to my tv. Anyone have a similar issue or thoughts on how to resolve the problem?
I don't think that LE is designed/setup up for multi-monitors that aren't mirrored / aren't the same resolution, so provided the built-in display is completely shot, I would recommend simply taking off the bottom cover and disconnecting the cable for the built-in display. The system should power-on/boot just fine provided the HDMI is plugged in, and LE should init the TV at 1080p that way.
Hi All. This may not be the right place to post but I wanted to rule out this being a problem with LibreElec 8 on my chromebox. In the previous version of Kodi (jarvis) after a suspend, the library would get updated. This allowed me to leave the box in standby mode instead of shutting it down. All this so I didn't have to get up from the couch to press the 'on' button and could do it via my harmony remote.
However after the krypton update, it seems that the 'update library on startup' doesn't seem to work after a 'resume'. Does anyone know if this is because of the way libreelec/chromebox is handling the resume vs startup or is this a Kodi problem?
The other kodi install I have is a windows box but it always gets shutdown and not suspended so i can't test it.
Thanks!
(2017-03-01, 06:31)dukem Wrote: [ -> ]Hi All. This may not be the right place to post but I wanted to rule out this being a problem with LibreElec 8 on my chromebox. In the previous version of Kodi (jarvis) after a suspend, the library would get updated. This allowed me to leave the box in standby mode instead of shutting it down. All this so I didn't have to get up from the couch to press the 'on' button and could do it via my harmony remote.
However after the krypton update, it seems that the 'update library on startup' doesn't seem to work after a 'resume'. Does anyone know if this is because of the way libreelec/chromebox is handling the resume vs startup or is this a Kodi problem?
The other kodi install I have is a windows box but it always gets shutdown and not suspended so i can't test it.
Thanks!
sounds like a change to LE's resume behavior, since Kodi isn't aware of it to my knowledge. The easy fix is probably just to add a command to a suspend/resume script to call the library update on resume, but I'm not sure how to do that offhand. I'd make on a post on the LE forums and I can press the issue in the team slack channel if you don't get a quick reply
(2017-03-01, 06:31)dukem Wrote: [ -> ]Hi All. This may not be the right place to post but I wanted to rule out this being a problem with LibreElec 8 on my chromebox. In the previous version of Kodi (jarvis) after a suspend, the library would get updated. This allowed me to leave the box in standby mode instead of shutting it down. All this so I didn't have to get up from the couch to press the 'on' button and could do it via my harmony remote.
However after the krypton update, it seems that the 'update library on startup' doesn't seem to work after a 'resume'. Does anyone know if this is because of the way libreelec/chromebox is handling the resume vs startup or is this a Kodi problem?
The other kodi install I have is a windows box but it always gets shutdown and not suspended so i can't test it.
Thanks!
The easiest way is to stop kodi before suspend and start it after resume. I'm happy with this configuration for several months
Just put the following into /storage/.config/sleep.d/01-cbox.power (01-cbox is just a name you can change, but leave the number at the beginning and the extension "power"):
Code:
#!/bin/sh
case $1 in
pre)
# before suspend do the following:
systemctl stop kodi;
sync; # this is to make sure the config is written back to the filesystem. I don't know whether it's necessary, but it doesn't harm...
;;
post)
# after resume do the following
systemctl start kodi;
;;
esac
(2017-03-01, 05:25)Matt Devo Wrote: [ -> ] (2017-03-01, 02:42)kidmoe Wrote: [ -> ]Hi everyone...my first post....First of all, big thanks to Matt for creating this script and giving us great operating system flexibility for our boxes/books.
Now, I have a Braswell Samsung Chromebook 3 (xe500c13-k02us) that my son trashed the screen on so I have decided to convert it to a KODI box running into a 1080p Panasonic Plasma via hdmi. I downloaded the script and decided to do a dual boot with LibreElec on a USB stick and the install went perfectly and when I CTRL-L it boot's straight into LibreElec. So far,so good. The issue I'm having is when LibreElec boots it does so at the resolution of the Chromebook, which is 1366x768. So the Chromebook screen is filled completely but the image on the plasma is only a smallish window that occupies about a quarter of the upper left part of the screen. Not a problem, i'm thinking, so I head into the display area of the system settings to change the resolution but the monitor is listed as default and the maximum resolution selection is 1366x768 and not the 1080p that my tv is capable of. So I switch the monitor from default to HDMI2, which is my plasma, but as soon as I do I get a black, blank screen on both tv and chromebook screen and no image and there it stays. I've tried and tried but just can't seem to sync this Samsung book up to my tv. Anyone have a similar issue or thoughts on how to resolve the problem?
I don't think that LE is designed/setup up for multi-monitors that aren't mirrored / aren't the same resolution, so provided the built-in display is completely shot, I would recommend simply taking off the bottom cover and disconnecting the cable for the built-in display. The system should power-on/boot just fine provided the HDMI is plugged in, and LE should init the TV at 1080p that way.
Can't believe I didn't think of that. Did as you suggested and now everything is working perfectly with a LibreElec dual boot to the internal hard drive. Thanks..
Hi All. My first post here so big thanks to Matt for creating and maintaining the script. I have been following this thread quite log time as you will see it from my question
Is there any info somewhere how to update asus chromebox openelec 4.2 build to newest LE? Do I also need to update bios?
Thanks!
(2017-03-02, 21:08)havila Wrote: [ -> ]Hi All. My first post here so big thanks to Matt for creating and maintaining the script. I have been following this thread quite log time as you will see it from my question
Is there any info somewhere how to update asus chromebox openelec 4.2 build to newest LE? Do I also need to update bios?
Thanks!
honestly, with a setup that old, a clean install (via USB) of LibreELEC 8.0 would be best. You don't need to update the firmware if everything is working fine, but it's not a bad time to do so, since updating to the latest UEFI firmware would require an OS reinstall. You can do that by booting a Linux ISO from USB and running the EZ Setup script from there (use that to create the install media too if you want)
(2017-03-02, 21:20)Matt Devo Wrote: [ -> ] (2017-03-02, 21:08)havila Wrote: [ -> ]Hi All. My first post here so big thanks to Matt for creating and maintaining the script. I have been following this thread quite log time as you will see it from my question
Is there any info somewhere how to update asus chromebox openelec 4.2 build to newest LE? Do I also need to update bios?
Thanks!
honestly, with a setup that old, a clean install (via USB) of LibreELEC 8.0 would be best. You don't need to update the firmware if everything is working fine, but it's not a bad time to do so, since updating to the latest UEFI firmware would require an OS reinstall. You can do that by booting a Linux ISO from USB and running the EZ Setup script from there (use that to create the install media too if you want)
ok, I will do the clean install and update firmware also. Can I backup the info of my watched tv shows and movies somehow? I already made a backup using the openelec tool but does it work with LE?
(2017-03-02, 21:52)havila Wrote: [ -> ]ok, I will do the clean install and update firmware also. Can I backup the info of my watched tv shows and movies somehow? I already made a backup using the openelec tool but does it work with LE?
a backup made using the built-in OE function is unlikely to work properly when moving so many versions ahead. I'd recommend using the built-in option to export the video library (and copy to USB), then re-import after doing a clean install
Hi
Looks like I need to do some catch-up for my (2) Asus N60 (M004U) Haswell Chromeboxes.
In early 2015, I used Matt's scripts to go standalone using legacy Seabios, EZ SCRIPT, and Ubuntu (which shows up as "LuBuntu 14.04 on my shutdown screens). I noticed Matts version History basically eliminates Ubuntu, and he made upgrades to the Firmware too (UEFI Full Rom, etc.). So, looking for upgrade path suggestions. Willing to do what it takes to get there. Have a windows 10 NUC too that I network with the others. It's running Kodi 17 and other 2 are not. Guess I'll try to pull scripts to USB on the WIN10 with RUFUS and plug them to the Chromeboxes. Can someone point me to the correct combo and sequence of installs to do this? Spent time on Matt's site, but I am kinda lost.Thanks!
(2017-03-04, 01:22)GSA1 Wrote: [ -> ]Hi
Looks like I need to do some catch-up for my (2) Asus N60 (M004U) Haswell Chromeboxes.
In early 2015, I used Matt's scripts to go standalone using legacy Seabios, EZ SCRIPT, and Ubuntu (which shows up as "LuBuntu 14.04 on my shutdown screens). I noticed Matts version History basically eliminates Ubuntu, and he made upgrades to the Firmware too (UEFI Full Rom, etc.). So, looking for upgrade path suggestions. Willing to do what it takes to get there. Have a windows 10 NUC too that I network with the others. It's running Kodi 17 and other 2 are not. Guess I'll try to pull scripts to USB on the WIN10 with RUFUS and plug them to the Chromeboxes. Can someone point me to the correct combo and sequence of installs to do this? Spent time on Matt's site, but I am kinda lost.Thanks!
whether or not you need to do anything at all really depends on if your current setup is effectively meeting your needs. If so, then just update Kodi and leave everything else alone. If not, then let's talk about what you want and why your current setup isn't optimal, and we can figure out the best path forward. The UEFI firmware is definitely the best option for new setups, but no need to unnecessarily blow up an existing install just to "upgrade."
Matt, thanks for the quick response. This started with not being able to "git" PPA for Kodi 17 successfully. Started looking around and found Ubuntu was no longer supported and LibreElec was being updated regularly. Then I see the Full ROM option now as well. I know my CPU idle isn't as low as I have read others have. Started feeling my system was gonna die on the vine, so to speak. Don't know what I would need the upgrade for since I have no idea what else I could possibly do with these bare bones systems. If you think I should just deal with it, can you recommend where to "git" a Kodi Distro thanks would actually not hobble me?
LibreELEC, unless you need stuff it doesn't provide.
(2017-03-04, 03:36)GSA1 Wrote: [ -> ]This started with not being able to "git" PPA for Kodi 17 successfully.
you don't "git" a ppa. git is a version control system (mainly used for source code); ppa stands for Pre-Packaged Archive, and is a way of defining repositories (which can be binary or source). 'sudo apt-get update kodi' should have been all you needed to do
Yes, thanks, Matt. I was using quotes around "git" to imply a (sic). Bad joke... I wasn't able to get Kodi through that command. But, instead, I figured out the process for updating your Full Rom script and installing Libre Elec. All is well. Assuming you are pushing the UEFI automatically with the update, I should be done. Now working on adding Chromium, Emby, and some addons I always had. Then I will repeat for the other box. THANKS SOOOO MUCH FOR ALL YOUR HELP THOUGH THE YEARS!!!