[Pajoe]

In preparation of getting our new Chromebook 3, I used the version 9 update channel on our older Chromebook, updating it to 18.0-RC4. 
ssh login shows : LibreELEC (official): 8.95.002 (Generic.x86_64)
It did have the smb problem so I followed the instructions to edit the extlinux.conf (adding pci=nomsi) .

However, I have another question, it appears the Chromebox is still using the Krypton MyVideo107.db and MyMusic60.db. after the Leia update. This is OK except when I tried  a second Leia installation, it converted the shared mysql database and then the  Chromebox with Leia no longer recognized the database that was upgraded by the 2nd Leia installation, resulting  in nothing showing  in the library on the Chromebox.  I looked and Leia should use MyVideo116 & Mymusic72.  I moved everything back to Krypton and now only have the Chromebox using Leia and it reads the original Krypton shared database ok. 

Do I need to run something special to actually update the database to the Leia version on the original Chromebox?

thanks

joe

[Matt Devo]

In preparation of getting our new Chromebook 3, I used the version 9 update channel on our older Chromebook, updating it to 18.0-RC4. 
ssh login shows : LibreELEC (official): 8.95.002 (Generic.x86_64)
It did have the smb problem so I followed the instructions to edit the extlinux.conf (adding pci=nomsi) .

However, I have another question, it appears the Chromebox is still using the Krypton MyVideo107.db and MyMusic60.db. after the Leia update. This is OK except when I tried  a second Leia installation, it converted the shared mysql database and then the  Chromebox with Leia no longer recognized the database that was upgraded by the 2nd Leia installation, resulting  in nothing showing  in the library on the Chromebox.  I looked and Leia should use MyVideo116 & Mymusic72.  I moved everything back to Krypton and now only have the Chromebox using Leia and it reads the original Krypton shared database ok. 

Do I need to run something special to actually update the database to the Leia version on the original Chromebox?

thanks

joe

 you'd have to pull the log and see why it's not recognizing the mysql/shared database.  Mine upgraded without issue here.  Probably a question best for the LE forums since nothing to do with the hardware/platform, just something specific to that one device, likely config wise.

[vult2000]

I have an HP Chromebox which I had used the E-Z Setup Script on for Kodi 17 which has been working great.  I decided to try the LibreELEC 8.95.2 beta a few days ago running Kodi 18 RC4 and it seemed like perhaps there are network issues in the kernel?  I couldn't play anything from my NAS via SMB without major buffering, nor could I use streams direct from my Emby server without buffering.  Even using the Kodi app from my phone to act as a remote control seemed almost jittery when using the arrows.  Has anyone else tried this and perhaps had a similar experience?

 fix here: https://forum.kodi.tv/showthread.php?tid...pid2798901 

 I modified the syslinux.cfg file and rebooted, but the performance does not seem any different when playing videos via an SMB share.  I am using a wired connection if that makes a difference?  If I revert back to the Krypton LibreELEC release everything works great again.

[D-an-W]

Read my post above dated 13th, you might have two copies of that file as I did.

[vult2000]

Read my post above dated 13th, you might have two copies of that file as I did.

 Bingo!  Thanks!

[Pajoe]

After much trouble getting the mysql databases to share, I tried the latest  Millhouse test build. It was great and the database matched with my Debian and CoreElec Leia Beta releases.  Library worked as it should, watched a little tv and was happy. However after a few hours I went back and learned it had no sound and no option to change the sound in system-settings The Pulse Audio was darkened and no way to select Alsa HDMI 1. I tried different monitors, different cables and re-installed various LibreElec releases. Every time, sound and choices in system-settings are OK but as soon as I update it to one of the later Millhouse test builds, there is no sound.

Is there some configuration file to force the CB3 to use Alsa  rather than Pulse Audio with bluetooth etc ?

thanks


joe

[Matt Devo]

After much trouble getting the mysql databases to share, I tried the latest  Millhouse test build. It was great and the database matched with my Debian and CoreElec Leia Beta releases.  Library worked as it should, watched a little tv and was happy. However after a few hours I went back and learned it had no sound and no option to change the sound in system-settings The Pulse Audio was darkened and no way to select Alsa HDMI 1. I tried different monitors, different cables and re-installed various LibreElec releases. Every time, sound and choices in system-settings are OK but as soon as I update it to one of the later Millhouse test builds, there is no sound.

Is there some configuration file to force the CB3 to use Alsa  rather than Pulse Audio with bluetooth etc ?

thanks


joe

 I need better than "latest Milhouse build." exact version, with logs.  There's a log posting function built-in

FWIW, working fine here for me on MH #0113

[Pajoe]

Thanks Matt!

I will try MH #0113 today

I am not sure of the log posting but these are the tar files, I started with #0117, and as I posted, I thought it was great.
After problems I tried going back to where I first saw Kodi RC5 knowing that is the version my Debian is using. Then tried a third.


LibreELEC-Generic.x86_64-9.0-Milhouse-20190117210258-#0117-ge23e672.tar
https://forum.kodi.tv/showthread.php?tid...pid2810084


LibreELEC-Generic.x86_64-9.0-Milhouse-20190112210257-#0112-g84c634a.tar
https://forum.kodi.tv/showthread.php?tid...pid2808323

LibreELEC-Generic.x86_64-9.0-Milhouse-20181229210312-#1229-ga98586b.tar
https://forum.kodi.tv/showthread.php?tid...pid2803544


on edit: same thing with MH #0113

[Matt Devo]

Thanks Matt!

I will try MH #0113 today

I am not sure of the log posting but these are the tar files, I started with #0117, and as I posted, I thought it was great.
After problems I tried going back to where I first saw Kodi RC5 knowing that is the version my Debian is using. Then tried a third.

on edit: same thing with MH #0113

 

  
LibreELEC makes it stupid easy to post logs in order to get help, and I can't tell you what the issue is without looking at them. Screenshots are useless.
Do a clean boot. Go into the LibreELEC addon, General (or System) settings, and at the bottom are two options to upload log files. Choose the first, and provide me with the resulting URL.

Also, would be very useful to know what connection type you are using, and to what you are connected.

And the latest MH #0118 works fine here.

[Pajoe]

Log:

http://ix.io/1yI2



Thanks, I ,misunderstood this morning. Fresh install of the LibreElec Beta, copied LibreELEC (Milhouse): devel-20190118210257-#0118-ge23e672 [Build #0118] to updated , rebooted and back to no sound. It did have sound after the initial install. Currently connected using HDMI to a HDMI Hanspree TV.

thanks again

​​​​​​​joe

[Matt Devo]

Log:

http://ix.io/1yI2



Thanks, I ,misunderstood this morning. Fresh install of the LibreElec Beta, copied LibreELEC (Milhouse): devel-20190118210257-#0118-ge23e672 [Build #0118] to updated , rebooted and back to no sound. It did have sound after the initial install. Currently connected using HDMI to a HDMI Hanspree TV.

thanks again

joe

 assuming you can access your Chromebox via SMB, go into the configfiles share, modprobe.d folder, and create a new text file blacklist.conf.  Edit that file to have a single line, "blacklist snd_soc_skl" then save it and reboot.

[Pajoe]

 assuming you can access your Chromebox via SMB, go into the configfiles share, modprobe.d folder, and create a new text file blacklist.conf.  Edit that file to have a single line, "blacklist snd_soc_skl" then save it and reboot. 

 Once again, thank you,

Our ChromeBox3 now has the ALSA sound options with the Millhouse build.
Switching to ALSA HDMI #0 and sound is good again

[Matt Devo]

 assuming you can access your Chromebox via SMB, go into the configfiles share, modprobe.d folder, and create a new text file blacklist.conf.  Edit that file to have a single line, "blacklist snd_soc_skl" then save it and reboot. 

 Once again, thank you,

Our ChromeBox3 now has the ALSA sound options with the Millhouse build.
Switching to ALSA HDMI #0 and sound is good again

I've added this note to the troubleshooting section of the wiki

[giant25]

Hey Matt,
I've been having an issue for some time where sometimes when I turn the TV on, there's a blank screen that I can't fix until reboot.  When I view xrandr, 1080p 60Hz is selected, which is proper.  It almost looks like Kodi is crashing or video drivers are having issues, not sure.  This happens maybe every other day or so, no pattern yet I can see.  My setup:
Standalone ASUS CN60 Panther, UEFI 8/27/18 Firmware, LE 8.2.5 (fresh install) connected to Samsung 4k UN65JU6500.  I have loaded PVR WMC addon, which could be pertinent.  I've turned on debugging to see if I can capture this issue again.  Below are log and crash logs.  Any ideas?

Log file (13:47 at bottom of log is when TV is turned on):
https://paste.kodi.tv/qanixiqipi.kodi

Crash log with slightly different final message than log:
https://paste.kodi.tv/acitagevel.kodi

 I'd try booting a Live session from USB to see if the same issue occurs there, and/or try the latest Kodi 18RC build (LibreELEC 8.90.009 IIRC).  I know there are some issues with 4K sets, but I don't have one myself, and nothing jumps out at me in the logs.  Maybe try starting a new thread in the Linux support forum or the LE support forums 

Just for closure:  I figured out that an EDID handshake was having issues, mainly if there was some type of system crash while sitting idle.  The solution was to save/dump the EDID from the TV and save it, I used libreelec's script to do so: https://wiki.libreelec.tv/custom_edid
Hope this helps anyone else with black screen issues when turning on their TV.

[Matt Devo]

Just for closure:  I figured out that an EDID handshake was having issues, mainly if there was some type of system crash while sitting idle.  The solution was to save/dump the EDID from the TV and save it, I used libreelec's script to do so: https://wiki.libreelec.tv/custom_edid
Hope this helps anyone else with black screen issues when turning on their TV. 

 
thanks for closing the loop on this