• 1
  • 252
  • 253
  • 254(current)
  • 255
  • 256
  • 553
Linux ChromeBox Kodi E-Z Setup Script (LibreELEC/Linux+Kodi) [2017/02/21]
I pushed that fix even to OE 5.0 ... so yes it's most likely not this bug ... debug logfile is needed.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
OK, I'll try to reproduce it with the same DVD video I played yesterday and get you the logfile if I'm successful.
Reply
after some days of tries/installations ive arrived to a stable OSes configuration with a dual boot, but I'm having a slight issue.
I'm used to watch movies in Kodi 14.1 under Lubuntu (latest Intel 1.07, Kodi is configured as supposed to) and *sometimes randomly* the CPU spikes/stucks up and starves Kodi decoding, which litterally stop for a second or two, and then resumes, with of course 2 seconds of dropped frames.

I've studied the taskmanager performances and found no evidence of a *random* task asking for high cpu cycles, and since i'm not running any background task nor server (just a little FTP server, which is mostly off), I'm wondering if Kodi itself could be the reason.
Should I maybe configure/disable something under Kodi (samba, upnp, etc.), which could be cause of this issue?

Is this a known issue or is particular of mine?
Reply
I have some questions please.

In Dual boot mode, one has to keep Developer mode on otherwise CTRL-D to boot to Chrome won't work, correct? If developer mode is turned off what happens to the setup?
With 16GB SSD and allowing 8Gb to Openelec, why is it the free space for ChromeOS Data(documents,etc) ends up to be approx 2GB only?
I have setup the box sucessfully on a small 22" LED Monitor as when i turned developer mode, my old Samsung TV fails to bring up image but should it work after a full setup of OpenElec?

Thank you.
Reply
(2015-03-10, 12:01)AndreaSpooky Wrote: after some days of tries/installations ive arrived to a stable OSes configuration with a dual boot, but I'm having a slight issue.
I'm used to watch movies in Kodi 14.1 under Lubuntu (latest Intel 1.07, Kodi is configured as supposed to) and *sometimes randomly* the CPU spikes/stucks up and starves Kodi decoding, which litterally stop for a second or two, and then resumes, with of course 2 seconds of dropped frames.

I've studied the taskmanager performances and found no evidence of a *random* task asking for high cpu cycles, and since i'm not running any background task nor server (just a little FTP server, which is mostly off), I'm wondering if Kodi itself could be the reason.
Should I maybe configure/disable something under Kodi (samba, upnp, etc.), which could be cause of this issue?

Is this a known issue or is particular of mine?

monitor using top via ssh to see what's causing the CPU spikes. It's not a known issue that I'm aware of.

(2015-03-10, 18:33)minixmt Wrote: I have some questions please.

In Dual boot mode, one has to keep Developer mode on otherwise CTRL-D to boot to Chrome won't work, correct? If developer mode is turned off what happens to the setup?
With 16GB SSD and allowing 8Gb to Openelec, why is it the free space for ChromeOS Data(documents,etc) ends up to be approx 2GB only?
I have setup the box sucessfully on a small 22" LED Monitor as when i turned developer mode, my old Samsung TV fails to bring up image but should it work after a full setup of OpenElec?

Thank you.

If you turn off developer mode, the system will go back to stock -- booting immediately to ChromeOS, with no access to the legacy boot function. Your OE partition/data shouldn't get erased, but won't be accessible.

The ChromeOS disk layout consists of 12 partitions (including the 2 used for OpenELEC), so whatever free space it's reporting is likely only the userdata partition.

There's no reason to think it won't work on your TV, but obviously you'll have to dual boot blindly
Reply
(2015-03-08, 04:58)Matt Devo Wrote: do you have a startup script or anything that's setting the resolution? or have it set in the video output settings? also check your guisettings.xml file in the userdata share -- obviously there is some remnant of your old config there since it likely wouldn't do that on a clean install

Hi Matt,

I dont have any startup script, my autostart is empty. Here's the pastebin of my guysetting, http://pastebin.com/wnkRXfDm got no idea what to look for into that..

Thanks !
Reply
I followed the instructions in the original post and wiki for a standalone setup (I think!).

When I reboot, after the "Run Installer" step, the Chromebox sticks at a grey splashscreen with the OpenElec logo and words "openelec embedded linux entertainment centre".

Any idea what I did wrong, and how to fix it? All help appreciated :-)

Asus Chromebox M031U (Celeron 2955U, 1.4GHz, 4 Gb RAM, 16Gb SSD)
Main TV: LibreELEC 7.0.1 / Kodi 16.1, with Xonfluence skin on Asus Chromebox (1.4GHz, 4Gb RAM, 64Gb SSD) + DVB-S and DVB-T with TVH.
Plus testing v17 nighlies on Macbook, and using Estuary skin.
Reply
(2015-03-12, 20:09)gshodg Wrote: I followed the instructions in the original post and wiki for a standalone setup (I think!).

When I reboot, after the "Run Installer" step, the Chromebox sticks at a grey splashscreen with the OpenElec logo and words "openelec embedded linux entertainment centre".

Any idea what I did wrong, and how to fix it? All help appreciated :-)

Asus Chromebox M031U (Celeron 2955U, 1.4GHz, 4 Gb RAM, 16Gb SSD)

so is it freezing when booting the OE install USB, or freezing when booting the hard drive after installation? If the former, I'd try redoing the install media creation using another PC (instructions linked in wiki)
Reply
(2015-03-12, 21:02)Matt Devo Wrote:
(2015-03-12, 20:09)gshodg Wrote: I followed the instructions in the original post and wiki for a standalone setup (I think!).

When I reboot, after the "Run Installer" step, the Chromebox sticks at a grey splashscreen with the OpenElec logo and words "openelec embedded linux entertainment centre".

Any idea what I did wrong, and how to fix it? All help appreciated :-)

Asus Chromebox M031U (Celeron 2955U, 1.4GHz, 4 Gb RAM, 16Gb SSD)

so is it freezing when booting the OE install USB, or freezing when booting the hard drive after installation? If the former, I'd try redoing the install media creation using another PC (instructions linked in wiki)

It's freezing when booting from the USB. Will try what you suggested, thanks.
Main TV: LibreELEC 7.0.1 / Kodi 16.1, with Xonfluence skin on Asus Chromebox (1.4GHz, 4Gb RAM, 64Gb SSD) + DVB-S and DVB-T with TVH.
Plus testing v17 nighlies on Macbook, and using Estuary skin.
Reply
(2015-03-12, 21:02)Matt Devo Wrote:
(2015-03-12, 20:09)gshodg Wrote: I followed the instructions in the original post and wiki for a standalone setup (I think!).

When I reboot, after the "Run Installer" step, the Chromebox sticks at a grey splashscreen with the OpenElec logo and words "openelec embedded linux entertainment centre".

Any idea what I did wrong, and how to fix it? All help appreciated :-)

Asus Chromebox M031U (Celeron 2955U, 1.4GHz, 4 Gb RAM, 16Gb SSD)

so is it freezing when booting the OE install USB, or freezing when booting the hard drive after installation? If the former, I'd try redoing the install media creation using another PC (instructions linked in wiki)

OK, thanks. I'm use a Mac to re-setup the USB. I'm following the steps from this page: http://wiki.openelec.tv/index.php/HOW-TO...ab=Mac_OSX

When I get to the step
Quote: Next we need to zero out the partition map, OSX has an issue if you don't do this
dd if=/dev/zero of=/dev/rdisk1 bs=1024 count=1
I get the following error message in the terminal window:

Quote:0101481ss-MBPBig Grinownloads 0101481s$ dd if=/dev/zero of=/dev/rdisk1 bs=1024 count=1
dd: /dev/rdisk1: Permission denied

Any idea what I can do next?
Main TV: LibreELEC 7.0.1 / Kodi 16.1, with Xonfluence skin on Asus Chromebox (1.4GHz, 4Gb RAM, 64Gb SSD) + DVB-S and DVB-T with TVH.
Plus testing v17 nighlies on Macbook, and using Estuary skin.
Reply
perhaps /dev/rdisk1 is the wrong device.

Or you need to be an admin user (what we call the root user in unix/linux, not sure about OSX although it is fundamentally unix underneath)

what does
Code:
diskutil disk
output?
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
(2015-03-12, 22:10)nickr Wrote: perhaps /dev/rdisk1 is the wrong device.

Or you need to be an admin user (what we call the root user in unix/linux, not sure about OSX although it is fundamentally unix underneath)

what does
Code:
diskutil disk
output?

If it's admin user, I don't know what to do to login as root - I'm just at the level of following the wiki, running the script and following step-by-step, but don't know much beyond that. I did what you said, and it came back with this:

Quote:0101481ss-MBPBig Grinownloads 0101481s$ diskutil disk1
diskutil: did not recognize verb "disk1"; type "diskutil" for a list
0101481ss-MBPBig Grinownloads 0101481s$ diskutil
Disk Utility Tool
Utility to manage local disks and volumes
Most options require root access to the device

Usage: diskutil [quiet] <verb> <options>, where <verb> is as follows:

list (List the partitions of a disk)
info[rmation] (Get information on a specific disk or partition)
listFilesystems (List file systems available for formatting)
activity (Continuous log of system-wide disk arbitration)

u[n]mount (Unmount a single volume)
unmountDisk (Unmount an entire disk (all volumes))
eject (Eject a disk)
mount (Mount a single volume)
mountDisk (Mount an entire disk (all mountable volumes))

enableJournal (Enable HFS+ journaling on a mounted HFS+ volume)
disableJournal (Disable HFS+ journaling on a mounted HFS+ volume)
moveJournal (Move the HFS+ journal onto another volume)
enableOwnership (Treat as exact User/Group IDs for a mounted volume)
disableOwnership (Ignore on-disk User/Group IDs for a mounted volume)

rename[Volume] (Rename a volume)

verifyVolume (Verify the file system data structures of a volume)
repairVolume (Repair the file system data structures of a volume)

verifyDisk (Verify the components of a partition map of a disk)
repairDisk (Repair the components of a partition map of a disk)

verifyPermissions (Verify the permissions of a Mac OS X volume)
repairPermissions (Repair the permissions of a Mac OS X volume)

eraseDisk (Erase an existing disk, removing all volumes)
eraseVolume (Erase an existing volume)
reformat (Erase an existing volume with same name and type)
eraseOptical (Erase optical media (CD/RW, DVD/RW, etc.))
zeroDisk (Erase a disk, writing zeros to the media)
randomDisk (Erase a disk, writing random data to the media)
secureErase (Securely erase a disk or freespace on a volume)

partitionDisk ((re)Partition a disk, removing all volumes)
resizeVolume (Resize a volume, increasing or decreasing its size)
splitPartition (Split an existing partition into two or more)
mergePartitions (Combine two or more existing partitions into one)

appleRAID <verb> (Perform additional verbs related to AppleRAID)
coreStorage <verb> (Perform additional verbs related to CoreStorage)

diskutil <verb> with no options will provide help on that verb
Main TV: LibreELEC 7.0.1 / Kodi 16.1, with Xonfluence skin on Asus Chromebox (1.4GHz, 4Gb RAM, 64Gb SSD) + DVB-S and DVB-T with TVH.
Plus testing v17 nighlies on Macbook, and using Estuary skin.
Reply
(2015-03-12, 22:08)gshodg Wrote: When I get to the step
Quote: Next we need to zero out the partition map, OSX has an issue if you don't do this
dd if=/dev/zero of=/dev/rdisk1 bs=1024 count=1
I get the following error message in the terminal window:

Quote:0101481ss-MBPBig Grinownloads 0101481s$ dd if=/dev/zero of=/dev/rdisk1 bs=1024 count=1
dd: /dev/rdisk1: Permission denied

Any idea what I can do next?

the OE instructions need to be updated - you need 'sudo' in front of the command:

Quote:sudo dd if=/dev/zero of=/dev/rdisk1 bs=1024 count=1
Reply
I didn't even know sudo was an OSX thing!
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
Quote:the OE instructions need to be updated - you need 'sudo' in front of the command:

sudo dd if=/dev/zero of=/dev/rdisk1 bs=1024 count=1

Great, thanks! Now I'm into OpenElec/Kodi on the Chromebox :-) Now to play with it :-) Thanks again all
Main TV: LibreELEC 7.0.1 / Kodi 16.1, with Xonfluence skin on Asus Chromebox (1.4GHz, 4Gb RAM, 64Gb SSD) + DVB-S and DVB-T with TVH.
Plus testing v17 nighlies on Macbook, and using Estuary skin.
Reply
  • 1
  • 252
  • 253
  • 254(current)
  • 255
  • 256
  • 553

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