2016-12-24, 21:46
(2016-12-24, 19:55)giant25 Wrote: Thanks Matt, sounds good. No rush, enjoy the holidays. I'm also game to test things out for you in general if you need a hand.
as I said, shoot me an email and we'll get this sorted
as I said, shoot me an email and we'll get this sorted
2016-12-26, 00:17
If I want to run Linux/LibreELEC for my OS and use Kodi...... is the Asus Chromebox still king of the hill? (I don't need 4K support.)
2016-12-26, 00:55
(2016-12-26, 00:17)gene0915 Wrote: If I want to run Linux/LibreELEC for my OS and use Kodi...... is the Asus Chromebox still king of the hill? (I don't need 4K support.)
IMO yes, if you can get one at a good price -- I wouldn't pay new retail for one now for a dedicated Kodi box
and if you can't find one at a good price, PM me and I can probably help
2016-12-26, 23:28
(2016-12-26, 00:17)gene0915 Wrote: If I want to run Linux/LibreELEC for my OS and use Kodi...... is the Asus Chromebox still king of the hill? (I don't need 4K support.)
We have a Chromebox, WeTek Play 2 and a Raspberry Pi 2 all running LibreElec and we use the Chromebox 99% of the time, it is the only player that works well enough for heavy daily use. Even with LibreElec 7.9.09 Alpha ? it is stable, but may need a reboot now and then. We prefer LibreElec Alpha because it does some things much better, looks better and with Tvheadend 4.2 / zap2xml-0.5.0 script it really plays well with our HDHomerun tuner. We have 3 self powered external drives hooked up to ours, and use a FLIRC usb reciever.
On Edit: LibreElec boot up says Alpha, so I changed the orgiinal post from beta to alpha
2016-12-27, 18:00
(2016-12-24, 03:22)Matt Devo Wrote:(2016-12-24, 03:16)t2ffn Wrote: I think it's somewhat down to the refresh rate / maybe plus the resolution. If the refresh rate is set at certain values, such as 60hz, the input is seen as a PC input, but if you change it to 30hz the regular TV options come back. I'll need to do some further testing but it could be as simple as ensuring to stay away from what Samsung sees as a 'PC refresh rate'.
Should've bought a Sony!
potentially 60.0Hz vs 59.97Hz? there are various standards for timings, it could be as simple as that. Either way it seems like Samsung's firmware on these sets is pretty buggy and inflexible.
If you'd like, I can provide you with a custom firmware that is limited to 1080p and uses different timings to try and sort out the issue -- shoot me an email at mrchromebox at gmail
Thanks for all your help with this Matt. For now, it's working like a champ so I'll leave it be for now. The only oddity is there seems no way to pull up the detailed info (usually via o) when playing a video, the screen that shows dropped frames etc. This could be a bug in the LE alpha (beta) or the skin etc. but it's low priority, so I'll see if this corrects itself as the RC rolls out.
For anyone wanting a stable Kodi box that handles most anything, the Chromebox with LE and the UEFI boot is it.
2016-12-27, 20:06
(2016-12-27, 18:00)t2ffn Wrote: Thanks for all your help with this Matt. For now, it's working like a champ so I'll leave it be for now. The only oddity is there seems no way to pull up the detailed info (usually via o) when playing a video, the screen that shows dropped frames etc. This could be a bug in the LE alpha (beta) or the skin etc. but it's low priority, so I'll see if this corrects itself as the RC rolls out.
For anyone wanting a stable Kodi box that handles most anything, the Chromebox with LE and the UEFI boot is it.
codec info via 'o' has been replaced by PlayerProcessInfo, which provides most of the same information. Skins will have to be updated to make use of that, so if you're not using the stock Estuary skin, it's possible you're not seeing the new info overlay.
2016-12-28, 03:12
Thanks Matt, I think the skins are just not up to speed with the change yet.
On the front page it says your script supports 3205U Broadwell, but in the UK our spec says 3215U. Can you confirm if this is also supported by your script / UEFI firmware?
Thanks
On the front page it says your script supports 3205U Broadwell, but in the UK our spec says 3215U. Can you confirm if this is also supported by your script / UEFI firmware?
Thanks
2016-12-28, 20:39
(2016-12-28, 03:12)t2ffn Wrote: Thanks Matt, I think the skins are just not up to speed with the change yet.yep all Haswell and Broadwell ChromeOS devices are supported regardless of CPU
On the front page it says your script supports 3205U Broadwell, but in the UK our spec says 3215U. Can you confirm if this is also supported by your script / UEFI firmware?
Thanks
2016-12-28, 20:59
Hey Matt and everybody,
I have a quick question...
I flashed my Asus Chromebox to the full ROM. Installed Windows and all was good.
I booted a Ubuntu 16.04 USB, it booted, I installed it, but upon reboot I found myself at the shell prompt. In the BIOS I was able to boot Ubuntu by choosing the grub file on the UEFI partition. How do I make it boot automatically?
Thanks.
PS
Just noticed the PM.
I have a quick question...
I flashed my Asus Chromebox to the full ROM. Installed Windows and all was good.
I booted a Ubuntu 16.04 USB, it booted, I installed it, but upon reboot I found myself at the shell prompt. In the BIOS I was able to boot Ubuntu by choosing the grub file on the UEFI partition. How do I make it boot automatically?
Thanks.
PS
Just noticed the PM.
2016-12-28, 21:06
(2016-12-28, 20:59)gixie Wrote: I booted a Ubuntu 16.04 USB, it booted, I installed it, but upon reboot I found myself at the shell prompt. In the BIOS I was able to boot Ubuntu by choosing the grub file on the UEFI partition. How do I make it boot automatically?
Thanks.
on the EFS partition, (sudo) copy /EFI/ubuntu/grubx64.efi to /EFI/BOOT/BOOTX64.efi observing case and creating the BOOT directory if needed
2016-12-28, 21:14
Hmm...says it can't create the dir
user@chromebox:~$ sudo cp /EFI/ubuntu/grubx64.efi to /EFI/BOOT/BOOTX64.efi
cp: target '/EFI/BOOT/BOOTX64.efi' is not a directory
user@chromebox:~$ cd /efi
bash: cd: /efi: No such file or directory
user@chromebox:~$ cd /EFI
bash: cd: /EFI: No such file or directory
user@chromebox:~$ sudo mkdir /EFI/BOOT
mkdir: cannot create directory ‘/EFI/BOOT’: No such file or directory
user@chromebox:~$ sudo cp /EFI/ubuntu/grubx64.efi to /EFI/BOOT/BOOTX64.efi
cp: target '/EFI/BOOT/BOOTX64.efi' is not a directory
user@chromebox:~$ cd /efi
bash: cd: /efi: No such file or directory
user@chromebox:~$ cd /EFI
bash: cd: /EFI: No such file or directory
user@chromebox:~$ sudo mkdir /EFI/BOOT
mkdir: cannot create directory ‘/EFI/BOOT’: No such file or directory
2016-12-28, 21:17
How do I go to the uefi partition? Sorry for my noob questions
2016-12-28, 21:20
(2016-12-28, 21:14)gixie Wrote: Hmm...says it can't create the dir
user@chromebox:~$ sudo cp /EFI/ubuntu/grubx64.efi to /EFI/BOOT/BOOTX64.efi
cp: target '/EFI/BOOT/BOOTX64.efi' is not a directory
user@chromebox:~$ cd /efi
bash: cd: /efi: No such file or directory
user@chromebox:~$ cd /EFI
bash: cd: /EFI: No such file or directory
user@chromebox:~$ sudo mkdir /EFI/BOOT
mkdir: cannot create directory ‘/EFI/BOOT’: No such file or directory
if you booted the Ubuntu USB, you'll have to mount the EFS partition on the SSD first. Something like:
mkdir /tmp/efs
sudo mount /dev/sda1 /tmp/efs
sudo mkdir /tmp/efs/EFI/BOOT
sudo cp /tmp/efs/EFI/ubuntu/grubx64.efi /tmp/efs/EFI/BOOT/BOOTX64.efi
2016-12-29, 23:16
Please forgive me if this has been answered, I couldn't find the answer. I have a chromebox running openelec version 6.0.3 standalone, and want to update to 7. Says I have to do it manually. Any instructions on this process? Do I need to use google EZ Script? If so do I need to bring the grime box back to google OS? Any help is appreciated.
