2014-12-04, 20:32
(2014-12-04, 14:05)john.cord Wrote: Ok, the Problem with the "No Signal" to TV is still present. Today i wanted to start the Box from Sleep and got "No Signal" to the TV. TV is on the right Channel, HDM Switch is On. But if i turn the HDM Switch off, start the Box and turn the HDMI Switch on after the Box is Turned on i got a Signal to the TV. Its exact the same Problem mentioned here: http://www.google.at/url?sa=t&rct=j&q=&e...2063,d.bGQ
On my Computer Monitor everything is fine via HDMI and DP. Wierd. Is there a chance that a standalone install with coreboot solves the problem?
I never had any HDMI Issues with this TV with various devices (DVD Player, BD Player, Streming Box (Xstreamer), Video Game Consoles or a PC connected vie DVI-D 2 HDMI Cable) so in my oppinion this is a Issue related to the chromboxes Video Bios or the HDMI Handshake Procedure. The TVs native Resolution is 1366x768 and according to the manual it is capable of displaying 1024x768 @ 60Hz, 720p and 1080i.
The standalone firmware uses the same VGA BIOS as my fixed SeaBIOS payload for the stock firmware, so if it is the issue, flashing the standalone firmware won't fix it. Have you tried using the suspend/resume script in the wiki? It forces the video/audio to reconnect upon resume.
(2014-12-04, 17:42)megamanwilson Wrote: Did some digging and found the command to check the kernel version: uname -r and I get this
3.2.0-23 generic. So if is not the kernel maybe the mistake I made cause this or is it the linux mint is to resource hungry for chromebox? maybe I should look into xubuntu or lubuntu?
Why are you running such and old version of Mint? The 3.2 kernel is definitely your issue; you should be running Mint 17 with kernel 3.14 or newer
(2014-12-04, 12:51)wackid Wrote: Just curious, I have a HP with 4gb ram.
When I upgrade to 8gb will it be noticeable? Or is it overkill?
for OpenELEC/Kodi? anything over 2GB is unnecessary.
