[Matt Devo]

We don't know exactly what it is, since we can't read the text, and it happens before XBMC starts, so it's in a different log file than the one you posted

[nickr]

Yeah, either foucus your camera on the top left of the screen so we can see what it says, or write the text down and post it here (the latter will at least be searchable if someone else has the problem.

I have never seen openelec do a filesystem check with output to the screen like that. Not saying it never happened, but I haven't noticed it!

Of course that is probably because openelec has a read only filesystem that by definition shouldn't become corrupted. Only /storage is RW as far as I know.

[c0mm0n]

I get that, and it sucks, I'm just saying there's no easy fix for the HP. Many people were wondering if it were a firmware issue or simply a noisy part, and that's not the case.

Thanks Matt for confirming that, I'll get rid of the HP and wait for the Dell.

[Matt Devo]

I get that, and it sucks, I'm just saying there's no easy fix for the HP. Many people were wondering if it were a firmware issue or simply a noisy part, and that's not the case.

Thanks Matt for confirming that, I'll get rid of the HP and wait for the Dell.

Might want to wait until I have a chance to play with it first, just to be safe

[-DDD-]

No I am refering to Live TV, all non HD channels in Europe and received by a dish are MPEG2 interlaced. Furthermore I understood that in the US dvb-c is often also MPEG2 based.
As sad before the new hardware decoding options are selectable only on MPEG4 (h264) live tv streams. It s all still very alhpa so, I am sure it will be fine at the final rls of helix

I think we should continue talk about OE Helix Alpha and the new Drivers here: http://forum.xbmc.org/showthread.php?tid=165707

[Islander3153]

[quote uid=49343 name="pettergulbra" post=1792416 timestamp=1410470282]Yes it is. SMB, with username/password.[/quote]<br />
Enable wait for network start and your problems should go away.<br/>

Out of curiosity I went looking for this option. The left side shows System then Network abd both show different help text at the bottom right of the screen. The odd thing is that the right side content for both menus is that of the System. I am guessing nothing to do with the script as it is inside OE?

[Matt Devo]

Out of curiosity I went looking for this option. The left side shows System then Network abd both show different help text at the bottom right of the screen. The odd thing is that the right side content for both menus is that of the System. I am guessing nothing to do with the script as it is inside OE?

I ran into this too at some point, something's corrupted, and clearing the user data (Settings -> OpenELEC -> General -> soft reset) will take care of it at the cost of having to redo a few things.

[noggin]

XBMC/Kodi 14 (Helix) OpenELEC nightly. Has hardware MADI and MCDI enabled. Experimental. Do a fresh install, and beware the dragons

https://dl.dropboxusercontent.com/u/9830...d9c62b.tar

Just tried this - and no MADI or MCDI options were visible? (However the Kodi build didn't look like FernetMenta's fork as it didn't have the Prefer VAAPI method and still included the SW deinterlace?)

[Islander3153]

Out of curiosity I went looking for this option. The left side shows System then Network abd both show different help text at the bottom right of the screen. The odd thing is that the right side content for both menus is that of the System. I am guessing nothing to do with the script as it is inside OE?

I ran into this too at some point, something's corrupted, and clearing the user data (Settings -> OpenELEC -> General -> soft reset) will take care of it at the cost of having to redo a few things.

Matt thanks for the response. What sort of things will need to be redone? The help text says OE configurations which I guess ok but it also says "xbmc to default including your library".

Does the last bit means that all xbmc settings will go to their default and the library items will have to be rescan as well. Will all sources be also reset needing setup?

Lastly, any idea if just waiting for next update to install over will fix whatever corruption happen?

Thanks again.

[pettergulbra]

We don't know exactly what it is, since we can't read the text, and it happens before XBMC starts, so it's in a different log file than the one you posted

Yeah, either foucus your camera on the top left of the screen so we can see what it says, or write the text down and post it here (the latter will at least be searchable if someone else has the problem.

I have never seen openelec do a filesystem check with output to the screen like that. Not saying it never happened, but I haven't noticed it!

Of course that is probably because openelec has a read only filesystem that by definition shouldn't become corrupted. Only /storage is RW as far as I know.

Right now I can`t reproduce the problem. But I will have the camera ready each time I start the box from sleep.

One more question:
I have many movies, MKVs that wont play, but they play nicely on the Windows Machine with XBMC on.
Is this normal for this box, or is it something I can do to make it play more MKVs?

[Matt Devo]

Just tried this - and no MADI or MCDI options were visible? (However the Kodi build didn't look like FernetMenta's fork as it didn't have the Prefer VAAPI method and still included the SW deinterlace?)

not sure what to say, I did a clean install on my CB and tested both of those options with 50i content.

Matt thanks for the response. What sort of things will need to be redone? The help text says OE configurations which I guess ok but it also says "xbmc to default including your library".

Does the last bit means that all xbmc settings will go to their default and the library items will have to be rescan as well. Will all sources be also reset needing setup?

Lastly, any idea if just waiting for next update to install over will fix whatever corruption happen?

Thanks again.

you'll have to redo everything essentially, same as a clean install, though it won't delete any files you have on the disc (that's what the 'hard' reset does). No idea what causes the issue or if it can be fixed without wiping clean. Part of the fun when running beta software.

Right now I can`t reproduce the problem. But I will have the camera ready each time I start the box from sleep.

One more question:
I have many movies, MKVs that wont play, but they play nicely on the Windows Machine with XBMC on.
Is this normal for this box, or is it something I can do to make it play more MKVs?

MKV is a container, just like AVI - it tells us nothing about the audio/video streams contained therein. If a specific file won't play, turn on debug logging, attempt to play the file, then turn off debug logging, and post the log (using pastebinit) - there's plenty of instructions on the site on how to do so. So far, I've yet to run across anything the Chromebox flat out "won't play" so my guess is that the file is encoded in a non-standard way or somehow damaged, and for whatever reason Windows is able to handle that a bit more gracefully.

[PityOnU2]

Thanks for all the great work here, specifically with coreboot and SeaBIOS. Two quick questions though;

1. What key do I press to get into the BIOS options at boot? I know ESC opens boot options, but what about the oh-so-important BIOS options?

2. Rocking Windows Server I found a device with vendor ID GOOG and device ID 9999. Can any Linux users give me info as to what that is? My guess is it's related to TPM, but my Google Pixel's "GOOG" device is much more important so I figured I'd ask.

1) There's no BIOS to get into. (in the sense you're thinking of it like a conventional PC)

this. No idea on that device however.

Thanks guys. That's interesting. Are all of the changes required for coreboot to work correctly propagated to the public source repository? I am interested in building my own copy so I can look into what options are possible to enable/disable.

Also, when running Windows, the Intel Display Audio Out does not function correctly. Using generic class drivers, HDMI audio shows it is unplugged all the time. With the vendor (Intel) drivers, it doesn't even show up in the audio tray menu anymore. Do you guys have any idea what might be causing this? This would make for one heck of a HTPC if I can just get HDMI audio out working.

[pettergulbra]

MKV is a container, just like AVI - it tells us nothing about the audio/video streams contained therein. If a specific file won't play, turn on debug logging, attempt to play the file, then turn off debug logging, and post the log (using pastebinit) - there's plenty of instructions on the site on how to do so. So far, I've yet to run across anything the Chromebox flat out "won't play" so my guess is that the file is encoded in a non-standard way or somehow damaged, and for whatever reason Windows is able to handle that a bit more gracefully.

I had to test a little bit more, so I moved all the non working files to another folder. Then I used the file manager inside XBMC to try them.
And, there they work as a charm. So I cleaned the library, then copied back to the movie folder, and re scanned that folder.
Now it seems to work, hope it keeps that way.

Edit: It looks like it can`t add all the movies, even if there is local information. It cant find them with the scraper nether, strange as they have not changed the name on any folder since it worked.
Log while I scanning for new material: http://pastebin.com/P6qDFZiq


Thanks again. Always fast answers! :-)

[fritsch]

Btw. we merged all the vaapi commits into xbmc master. So helix will have all the code we tested for more than a year in the fernetmenta ppa. But yeah to use MCDI, MADI - the relevant driver is needed: https://github.com/fritsch/libva-intel-d...tree/ppa14 or it won't work at all.

[Matt Devo]

Thanks guys. That's interesting. Are all of the changes required for coreboot to work correctly propagated to the public source repository? I am interested in building my own copy so I can look into what options are possible to enable/disable.

Also, when running Windows, the Intel Display Audio Out does not function correctly. Using generic class drivers, HDMI audio shows it is unplugged all the time. With the vendor (Intel) drivers, it doesn't even show up in the audio tray menu anymore. Do you guys have any idea what might be causing this? This would make for one heck of a HTPC if I can just get HDMI audio out working.

yes, all of the coreboot changes I've merged have been accepted upstream. You can extract the config I'm using from my firmware and use that as a starting point. You'll also need to extract all of the binary blobs (which are not open source / not part of coreboot) and merge those in as well. For SeaBIOS, some of the changes I've made have not yet been submitted/merged upstream (eg: display proper text when booting from USB; skip boot menu when only one bootable device attached). Everything I use (build scripts, etc -- except the binary blobs) is posted on my github, which I've added to the OP.

I don't have any idea on the HDMI audio, and since I a) don't run Windows 8, and b) don't have an HDMI-capable receiver to test, it's not something I'm going to spend any time on.