Quote:post the required info as directed at the top of the first post
Quote:***************************************************
THREAD RULES: Read before posting
***************************************************
Playback related issues should be discussed in the Linux support forum (or, if add-on related, in the correct forum/thread), as they are 99% likely not ChromeBox-specific.
Post your Logfiles there, describe your Issue as detailed as possible and the Timeslot when the Issue happened in the Logfiles.
I used the default size (9 GB) for my openelec partition. I am running out of space on the ChromeOS side as I can't use offline Google Drive. Can I use the script to resize the position or what would be the best way to increase the ChromeOS size?
(2015-01-16, 21:41)VanillaXtract Wrote: [ -> ]I used the default size (9 GB) for my openelec partition. I am running out of space on the ChromeOS side as I can't use offline Google Drive. Can I use the script to resize the position or what would be the best way to increase the ChromeOS size?
Use OE's backup function, copy backup file to another machine, do a factory reset, re-run script and set smaller partition size, restore OE backup
(2015-01-16, 20:31)movie78 Wrote: [ -> ]Log file.
http://paste.ubuntu.com/9762968/
I thought you were complaining about lockups with OE 5.0.0 - this log is from Kodibuntu.
You're running an ancient kernel that doesn't have any of the fixes, of course you're seeing issues. Fritsch linked to an updated 3.18 kernel he built a few pages back, or you can install an off-the-shelf 3.19-rc2 (or newer) kernel. OE already has all these fixes, which is why it's the preferred platform for the ChromeBox
3.19-rc2 or newer (to be fully correct there).
(2015-01-16, 22:27)Matt Devo Wrote: [ -> ] (2015-01-16, 20:31)movie78 Wrote: [ -> ]Log file.
http://paste.ubuntu.com/9762968/
I thought you were complaining about lockups with OE 5.0.0 - this log is from Kodibuntu.
You're running an ancient kernel that doesn't have any of the fixes, of course you're seeing issues. Fritsch linked to an updated 3.18 kernel he built a few pages back, or you can install an off-the-shelf 3.19-rc2 (or newer) kernel. OE already has all these fixes, which is why it's the preferred platform for the ChromeBox
Had more stuttering issue with OE 5.0 than Kodibuntu.
Kodibuntu runs much better than the OE 5.0.
Before i install Kodibuntu, i did eveything you told me to do on OE 5.0 and still had had the same problem.
well you seem to be the only one with the problem, and since you can't provide adequate information to diagnose the issue, I'm afraid there's nothing we can do for you
(2015-01-16, 22:43)fritsch Wrote: [ -> ]3.19-rc2 or newer (to be fully correct there).
With Putty.exe
How can i update the kernel to 3.19 rc2?
(2015-01-16, 23:19)Matt Devo Wrote: [ -> ]well you seem to be the only one with the problem, and since you can't provide adequate information to diagnose the issue, I'm afraid there's nothing we can do for you
That was not enough information in the log file?
Anyone referring to ssh as "putty.exe" should not be manually upgrading their kernel.
(2015-01-16, 23:32)rodalpho Wrote: [ -> ]Anyone referring to ssh as "putty.exe" should not be manually upgrading their kernel.
SSH
Terminal
winscp
All i need to know is how to get the package.
(2015-01-16, 23:23)movie78 Wrote: [ -> ] (2015-01-16, 23:19)Matt Devo Wrote: [ -> ]well you seem to be the only one with the problem, and since you can't provide adequate information to diagnose the issue, I'm afraid there's nothing we can do for you
That was not enough information in the log file?
as I said, the the log file told me you're running an outdated and unsupported kernel, so there's no point in trying to diagnose issues experienced with it. If you provide a similar log from OE 5.0.0 (along with a complete description of the problem and test conditions), then we have something. There's a gazillion guides out for how to update a Ubuntu kernel
I'm having an issue with seeing the boot menu in seabios. when i press esc within 5 secs of powering on to get to the boot menu, my monitor doesn't detect a signal from the chromebox, and when i press the power button, it just turns off.
i originally wanted a standalone ubuntu setup and went through all the steps before rebooting, then decided i wanted a dual boot chromeos + ubuntu setup. so i went back and selected that option and then rebooted. now it just hangs on 'booting from kernel' if i don't press esc, or the above if i press esc on time. i've tried to restore the stock firmware as well as using an openelec image on a usb stick. but nothing worked.
(2015-01-17, 03:52)nolfan Wrote: [ -> ]I'm having an issue with seeing the boot menu in seabios. when i press esc within 5 secs of powering on to get to the boot menu, my monitor doesn't detect a signal from the chromebox, and when i press the power button, it just turns off.
i originally wanted a standalone ubuntu setup and went through all the steps before rebooting, then decided i wanted a dual boot chromeos + ubuntu setup. so i went back and selected that option and then rebooted. now it just hangs on 'booting from kernel' if i don't press esc, or the above if i press esc on time. i've tried to restore the stock firmware as well as using an openelec image on a usb stick. but nothing worked.
you broke it good - real good. Your best bet is going to be booting from a ChromiumOS USB stick, but I can't guarantee even that will work since you botched the firmware by doing a dual boot install after a standalone install. If you are able to boot a ChromiumOS USB, then you can restore the stock firmware from there using the instructions in the wiki -- You can't do it from OpenELEC.
If that doesn't work, PM me for help or hit me up on the OpenELEC IRC channel