donofrio has quit [Remote host closed the connection]
lolek has joined #libreelec
tsal has quit [Ping timeout: 256 seconds]
tsal has joined #libreelec
tsal has quit [Ping timeout: 246 seconds]
tsal has joined #libreelec
Gittun has joined #libreelec
Tobbi has joined #libreelec
andy-burns has joined #libreelec
nast has quit [Read error: Connection reset by peer]
antlarr has quit [Ping timeout: 256 seconds]
antlarr2 has joined #libreelec
ghostcube has joined #libreelec
Fenster has quit [Ping timeout: 260 seconds]
Fenster has joined #libreelec
lolek has quit [Quit: Leaving.]
RaphGro has joined #libreelec
CYBERDEViL has joined #libreelec
donofrio has joined #libreelec
pragmaticenigma has joined #libreelec
fraggle_boate has quit [Ping timeout: 246 seconds]
fraggle_laptop has quit [Ping timeout: 264 seconds]
psymin has joined #libreelec
fraggle_laptop has joined #libreelec
andy-burns has quit [Ping timeout: 264 seconds]
nast has joined #libreelec
andy-burns has joined #libreelec
lacrimosa has joined #libreelec
lacrimosa has quit [Quit: Konversation terminated!]
lacrimosa has joined #libreelec
lacrimosa has quit [Ping timeout: 244 seconds]
RaphGro has quit [Quit: Please remember your own message. It'll be read as soon as possible.]
LossAngeles has quit [Remote host closed the connection]
LossAngeles has joined #libreelec
gouchi has joined #libreelec
LossAngeles has quit [Ping timeout: 256 seconds]
LossAngeles has joined #libreelec
LossAngeles has quit [Ping timeout: 246 seconds]
LossAngeles has joined #libreelec
andy-burns has quit [Read error: Connection reset by peer]
andy-burns has joined #libreelec
heldchen has joined #libreelec
nickynamy has joined #libreelec
held has quit [Ping timeout: 272 seconds]
<nickynamy>
hi, i have some trouble booting libreelec 9.2.3 on my raspberry pi 1 B. It just gets stuck on boot. I also tried the current master but the boot screen gave me the message from https://github.com/LibreELEC/LibreELEC.tv/pull/3356
<nickynamy>
Did anyone else experince this problem?
<nickynamy>
my boot process never reached network state. actually all subsequent targets failed too
<pragmaticenigma>
nickynamy: have you verified the SD Card has not failed?
<nickynamy>
I have flashed it several times with newly built images... I guess the hw wear leveling should have taken care of problems....
<pragmaticenigma>
nickynamy: that's not what I asked... I asked did you verify the card is not failing... that is not the same thing as "I was able to flash the card"
<nickynamy>
and how would i do that? compare bytewise?
<pragmaticenigma>
nickynamy: The easiest to me is to try a different SD Card
<pragmaticenigma>
the next easiest... try the troubled SD card in a different RPi
|Jeroen| has joined #libreelec
<nickynamy>
i'll try that
<pragmaticenigma>
if using a new SD card fixes the issue, then the old SD card is leaning towards failure. If using a different RPi with the troubled card works, then I'd lean toward the other RPi starting to or is failing
<nickynamy>
Well I guess it's my oldest sd card so failure might be possible
<pragmaticenigma>
SD Cards are virtually limitless when it comes to reads, you won't detect anything with a byte check. It's going to be a fault at the hardware level that would require special tools to figure out
<nickynamy>
unfortunate :(
<nickynamy>
pragmaticenigma: Ok, I have tried a master branch build on a different card but the problem persists. I'll check out the 9.2.3 build
<pragmaticenigma>
nickynamy: does it boot if you use the pre-built images?
<nickynamy>
that will be the next step :)
<nickynamy>
pragmaticenigma: Now I have used the prebuilt images and it boots indeed. I have no clue why...
<nickynamy>
I built exactly the tag that was labeled 9.2.3
<pragmaticenigma>
but was that targetted at the correct RPi ARM version? 1B has a very different chip from the 2 & 3
<nickynamy>
I used this line to build: PROJECT=RPi DEVICE=RPi ARCH=arm make -j16 image
andy-burns has joined #libreelec
<pragmaticenigma>
unfortunatly I'm just a consumer of the pre-builts... I haven't tried to build mine manually. Haven't seen a reason to
<nickynamy>
I just didn't like that the prebuilts are delivered "unverifyable"
<nickynamy>
Seems as if that had been discussed several times in the forums
* nickynamy
tries on their's tinfoil hat
<nickynamy>
maybe I mount both images and compare them bytewise
<pragmaticenigma>
If someone is really that curious about what I'm doing with my LibreElec instance... well... that's on them. Though through all my network monitoring I don't see any unusual traffic that I find concerning from my two instances
buzzmarshall has joined #libreelec
LossAngeles has quit [Quit: Leaving]
<nickynamy>
it's a matter of principle. I like to know that software running on my devices is not sent completely unprotected through the internet. It's not that I don't trust the devs, I don't trust all internet nodes to be benevolent. Especially when I start entering my passwords for all sorts of services in my kodi instance
<pragmaticenigma>
not worth the time or effort. Good password management protects passwords, all of mine are uniquely generated by a password manager, so if one database gets compromised, or someone manages to break through the HTTPS connection, I don't have to worry about it. Second, I don't use my primary e-mail account for any of my entertainment accounts. There is greater risk in the plugins than there is with KODI
<nickynamy>
The plugin security is much more worrysome, indeed :/
<nickynamy>
But I guess what you describe is more of "impact mitigation" than "attack vector protection".
<nickynamy>
In fact the libreelec download seemingly has no https protection. So the "net" is free to tinker with the transmitted data
<pragmaticenigma>
I live by the belief the Internet is no different than standing in the middle of a city park or grocery store. You can kind of hide, but someone somewhere can see you and what you are doing. So better the vary what you tell others whilst in that park, than telling everyone the same thing
TheSilentLink has quit [Quit: Good Bye! My bouncer has probably crashed or lost connection to the internet...]
TheSilentLink has joined #libreelec
ghostcube has quit [Quit: Verlassend]
pragmaticenigma has quit [Quit: Leaving]
Fenster has quit [Ping timeout: 246 seconds]
LossAngeles has joined #libreelec
shibboleth has joined #libreelec
CYBERDEViL has quit [Quit: Leaving]
j0nnymoe has quit [Quit: quit]
andy-burns has quit [Ping timeout: 264 seconds]
gouchi has quit [Remote host closed the connection]
nickynamy has quit [Remote host closed the connection]