MichaelOF has quit [Quit: Konversation terminated!]
andy-burns has quit [Ping timeout: 272 seconds]
Gittun has quit [Quit: UPP]
_abbenormal has joined #libreelec
_abbenormal has quit [Client Quit]
_abbenormal has joined #libreelec
Fenster has quit [Read error: Connection reset by peer]
Fenster has joined #libreelec
tsal_ has joined #libreelec
tsal has quit [Ping timeout: 240 seconds]
_abbenormal has quit [Read error: Connection reset by peer]
fuxxy has joined #libreelec
<fuxxy>
attempting to get Kodi to control my network-attached Onkyo reciever using eISCP commands. There's a python project available at [https://github.com/miracle2k/onkyo-eiscp] that works perfectly from my debian laptop. Is there a way to install it on LibreELEC?
<}8]>
you can bind remote control keys to use RunScript()
buzzmarshall has quit [Remote host closed the connection]
<fuxxy>
}8], That's what I was thinking, but I need the eiscp interposer program to actually talk to the receiver.
held has quit [Ping timeout: 272 seconds]
fraggle_laptop has quit [Ping timeout: 256 seconds]
donofrio has quit [Remote host closed the connection]
JohnDoe_71Rus has joined #libreelec
javi404 has quit [Quit: No Ping reply in 180 seconds.]
<damex>
hi, is there a way to debug that nuc6cayh + pulse-eight CEC adapter (internal) does not always resume along with NUC or even bring it back from sleep? currently on last LibreELEC release. Both NUC and CEC adapter have last firmware versions installed. i had it working before and nuc have usb sleep power-on option enabled to make nuc be powered from usb port (that is how CEC is connected internally, usb and cec headers).
<damex>
so occasionally it does not power on from being 'off' commend from TV CEC and sometime you power on NUC and CEC adapter does not respond unless you reconnect hdmi cable or reboot nuc.
<Colti>
Okay, so is there no automatic routine that already tried fsck on the rpi itself? It hangs a few seconds with a black screen but not sure if that was enough tiome to auto try a fsck
<Colti>
so it seems best option is to fix a from a linux computer not the debug shell?
<Colti>
sadly this error message is not delivering much information :-(
<MrTAP>
I'm by no means an expect but I presume it can't find that partition at all rather than it's broken, but attempting an fsck would let you know
St3ak has quit [Remote host closed the connection]
St3ak has joined #libreelec
<Colti>
okay i dont think the partition is gone. The stick was working and just failed after a reboot. So i think the only options are the storage partition is corrupt or the usb stick is dying, but its a new one so i belive in a corrupted partition.
<Colti>
seems without a linux computer i have not much options yet.
<Colti>
perhaps the partition is flagged for fsck then it is not mounted i think
<MrTAP>
can you plug a keyboard into your pi so you can just type fsck LABEL=Storage to see wha tit comes up with?
<Colti>
only got a bluetooth one. Need to search for an old usb keyboard tomorrow only got a usb mouse yet
<Colti>
is fsck working from debugging shell?
<MrTAP>
I expect it would but I can't say for sure
<Colti>
tought fsck is also on the broken partition
<Colti>
i would expect otherwise fsck would be started after that error message
<MrTAP>
Well as mentioned the first step is to find out why it can't mount it. That's just the first place to start to see what it has to say
<Colti>
yes, will do an fsck first hopefully it will fix it. What is my best option if it wont?
<MrTAP>
Depends what it says :)
<MrTAP>
IO error or similar would suggest your storage has failed
<MrTAP>
partition not found would mean your partition table is corrupted or the label got changed
<MrTAP>
etc
<Colti>
Okay corrupted partition table sounds very bad, then there is not much hope right?
<MrTAP>
Again it depends
<MrTAP>
Need more info to see if it's a trivial issue or something larger
<Colti>
ok any output from fsck is helpful to analyze the problem? Or should i try to get the latest logs from the usb stick with the pc?
<MrTAP>
There won't be any logs if it can't boot
pauljw has joined #libreelec
<MrTAP>
so fsck is just step 1. maybe the output of 'dmesg' would help
<Colti>
ah ok
<Colti>
thanks for your help, will try this steps tomorrow hopefully it solves it.