I have dual boot with Chrom and Kodibuntu operationg systems on my HP Chrombox. I don't think I will use Chrome operating system, and want to have only single boot with kodibuntu. I want to make sure that I can do it by downloading the script again from the bash shell when I start the kodibuntu and install coreboot. Since the kodibuntu is already installed, I do not need to reinstall it by creating the usb install media. Please let me know if I am understanding this correctly. I know that safe way would be to start from step 1, and install coreboot, and then create usb install media, and then install kodibuntu. I am just trying to keep the already configured kodibuntu with x11vnc and other kodi customizations and trying to avoid reinstall. Thanks.
If you don't care about regaining the disk space allocated to ChromeOS, then simply flashing the coreboot firmware is sufficient
How to check the version of the firmware installed ?
Hello!
i hope this is the right place to ask it!
I have a problem: i installer last openelec build (OpenELEC-Generic.x86_64-5.0.6-efi.img.gz) but:
1) i don't have the suggested kernel and i didn't understand how to update it
2) i use a smb windows shared folder, but i have a really poor performance!
CPU usage is very low (always less then 15%) but i have really poor network performance!
A 720p file will end cache in about 20 seconds.
I can incrase it but i don't think that can be a solution!
Can u help me?
thanks in advance
Merlino
Quote:1) i don't have the suggested kernel and i didn't understand how to update it
Nothing needs updating on OpenELEC
Quote:2) i use a smb windows shared folder, but i have a really poor performance!
If that is wireless, fix the root cause -> get a cable.
(2015-03-21, 15:33)fritsch Wrote: [ -> ]Quote:1) i don't have the suggested kernel and i didn't understand how to update it
Nothing needs updating on OpenELEC
Quote:2) i use a smb windows shared folder, but i have a really poor performance!
If that is wireless, fix the root cause -> get a cable.
hi!
Thanks for your help!
i'm using gigabit eth cable.
On the same switch i have also another pc with gigabit that works perfectly!
Thanks
You could test transferring data over ftp to see if it's as slow. I get 31-33 MB/s over ftp on a gigabyte network.
(2015-03-21, 14:28)Roby77 Wrote: [ -> ]How to check the version of the firmware installed ?
power on with a bootable USB device connected; the last part of SeaBIOS version string is the date, which is the closest thing to the version.
(2015-03-21, 16:29)Boulder Wrote: [ -> ]You could test transferring data over ftp to see if it's as slow. I get 31-33 MB/s over ftp on a gigabyte network.
that's far below optimal for a gigE network. I get close to 100MB/s to/from my NAS via SMB; the ChromeBox is limited to around 70MB/s sustained in practice, but pretty sure that's a limitation of the write speed of the internal ssd (or M.2 SATA interface).
I'm writing to an external USB drive attached to the Chromebox, maybe that's the reason. According to Windows Task Manager, network usage hovers around 40-50% during the transfer.
EDIT: and of course, the router itself can limit the transfer rate. I've got an Asus RT-N56U which should be quite good but probably not the best there is
(2015-03-21, 17:49)Boulder Wrote: [ -> ]I'm writing to an external USB drive attached to the Chromebox, maybe that's the reason. According to Windows Task Manager, network usage hovers around 40-50% during the transfer.
if it's USB2, then that's likely it.
Quote:EDIT: and of course, the router itself can limit the transfer rate. I've got an Asus RT-N56U which should be quite good but probably not the best there is
the LAN switch on any modern router should handle gigE traffic without breaking a sweat. It's the NAT overhead for WAN-->LAN traffic that limits some of the lower performing ones.
(2015-03-21, 10:30)Matt Devo Wrote: [ -> ]If you don't care about regaining the disk space allocated to ChromeOS, then simply flashing the coreboot firmware is sufficient
Thanks Matt. I appreciate the help. I don't really need the space taken by Chromeos, just trying to avoid 30 sec delay.
By the way, is there some way to back up the kodibuntu system on Chrombox to usb drive?
(2015-03-21, 22:01)jhaveri Wrote: [ -> ] (2015-03-21, 10:30)Matt Devo Wrote: [ -> ]If you don't care about regaining the disk space allocated to ChromeOS, then simply flashing the coreboot firmware is sufficient
Thanks Matt. I appreciate the help. I don't really need the space taken by Chromeos, just trying to avoid 30 sec delay.
By the way, is there some way to back up the kodibuntu system on Chrombox to usb drive?
if you just want to get rid of the boot delay, then you can use the script to set it to a 1s delay and default to booting Kodibuntu. But if you have no plans to use ChromeOS then flashing the standalone firmware is a better option.
I'm not aware of any specific tools for backing up a Ubuntu system, though I'm sure some exist. If you only care about the Kodi settings etc, then there are add-ons available to back that up.
Hello! Guys I'm in so much trouble here. I really hope you can help me.
I have an Asus Chromebox. Had the dual setup, then attempted to go for the standalone. Did the factory reset, firmware backup, flashed the custom firmware but something went wrong, cause now It won't boot.
The log says:
Booting the kernel.
drm:i915_write32 Error Unknown unclaimed register before writing to a090
i8042: No controller found
gsmi: exec 0xc1ef: Unknown error 0xc1ef
usb1-4
tring descriptor 0 mlformed (err=-61), defaulting to 0x0409
sdb No Caching mode page present
sdb Assuming drive cache: write through
.
.
.
I tried booting from a usb stick with Chromium, but couldn't, cause I forgot to reset the boot options, and I can't choose the usb drive. I press Escape but nothing happens, the boot menu disappears in a second, goes directly to the hard dirve.
Please tell me there is another way to boot from an external drive, so I can restore the firmware backup I got here. Or what can I do to fix this?
Thanks in advance!
(2015-03-22, 04:49)code_19 Wrote: [ -> ]Hello! Guys I'm in so much trouble here. I really hope you can help me.
I have an Asus Chromebox. Had the dual setup, then attempted to go for the standalone. Did the factory reset, firmware backup, flashed the custom firmware but something went wrong, cause now It won't boot.
if you did a factory reset (which you didn't need to do before switching to a standalone setup), then you no longer have OpenELEC installed, so you need to install it, just like you would if you'd never done the dual boot setup before
Quote:I tried booting from a usb stick with Chromium, but couldn't, cause I forgot to reset the boot options, and I can't choose the usb drive. I press Escape but nothing happens, the boot menu disappears in a second, goes directly to the hard dirve.
Please tell me there is another way to boot from an external drive, so I can restore the firmware backup I got here. Or what can I do to fix this?
Thanks in advance!
no, the boot options have no effect now - you wiped them out when you installed the custom firmware. You're not getting a boot menu b/c the ChromeBox doesn't like your USB stick for whatever reason. All you need to do now is create an OpenELEC usb installer by following the instructions on the OpenELEC wiki, which are linked from the ChromeBox wiki. If it doesn't work with one USB stick, try another or a SD card instead. Once you get OE (re)installed everything will be fine
(2015-03-21, 22:23)Matt Devo Wrote: [ -> ] (2015-03-21, 22:01)jhaveri Wrote: [ -> ] (2015-03-21, 10:30)Matt Devo Wrote: [ -> ]If you don't care about regaining the disk space allocated to ChromeOS, then simply flashing the coreboot firmware is sufficient
Thanks Matt. I appreciate the help. I don't really need the space taken by Chromeos, just trying to avoid 30 sec delay.
By the way, is there some way to back up the kodibuntu system on Chrombox to usb drive?
if you just want to get rid of the boot delay, then you can use the script to set it to a 1s delay and default to booting Kodibuntu. But if you have no plans to use ChromeOS then flashing the standalone firmware is a better option.
I'm not aware of any specific tools for backing up a Ubuntu system, though I'm sure some exist. If you only care about the Kodi settings etc, then there are add-ons available to back that up.
Matt: I have got into trouble, I hope you can help. After I installed the coreboot, prepared Kodibuntu usb boot disk, installed kodibuntu, and rebooted the hp chrombox, I do not see any display on the tv. The chrombox is connected by hdmi to denon avr 891, and from denon to samsung ultra hd 4k tv through hdmi from denon. Everything was fine in dual boot. When I went upstairs to my pc, I saw that wireless was working in the kodibuntu, but I could not ssh. So I disconnected chrombox, and brought it upstairs and connected to my hidef samsung monitor through hdmi. Kodibuntu boots fine, and I see display on the monitor. I took the chrombox again to denon/tv connection, and still no display. The tv briefly says resolution not supported, but upstairs monitor says it was 1920x1080. I am completely lost. Thanks for your help.