RaphGro has quit [Quit: Please remember your own message. It'll be read as soon as possible.]
RaphGro has joined #libreelec
andy-burns has quit [Ping timeout: 256 seconds]
mack-- has joined #libreelec
mack- has quit [Ping timeout: 265 seconds]
mack-- is now known as mack-
buzzmarshall has joined #libreelec
psymin__ has joined #libreelec
aphirst has quit [Ping timeout: 264 seconds]
Domin has quit [Ping timeout: 264 seconds]
psymin__ has quit [Remote host closed the connection]
psymin has quit [Ping timeout: 264 seconds]
Domin has joined #libreelec
aphirst has joined #libreelec
psymin has joined #libreelec
buzzmarshall has quit [Quit: Leaving]
buzzmarshall has joined #libreelec
<buzzmarshall>
afternoon all
<buzzmarshall>
looking to pick anyones brains on thoughts to a issue i am trying to solve regarding Libreelecs usb programmer which seems to be present in other appz like balenga as well
<buzzmarshall>
i am getting ready to release a couple of libreelec projects supporting some of the older s812 based kinda on datrh and libreelecs sources but ran into a wierd snag that i am not sure of whats causing it
<buzzmarshall>
essentially i keep running in the can't find the STORAGE snag when trying to run the 1st round on a sd card
<buzzmarshall>
it appears like its some kinda labelling issue and been scouring the sources trying things
<buzzmarshall>
then i realized that same img files using the Libreelec programmer in a win7 machine actually works
<buzzmarshall>
the resulting box actually works quite well
<buzzmarshall>
so far i have tried programming the img file on 3 different unix boxes running 16.04 18.04 and 19.04
<buzzmarshall>
same issue all the time
<buzzmarshall>
2 differnt windows machines program the file fine
<buzzmarshall>
also once the windows version is used on the box it installs and everything works find
<buzzmarshall>
but if i take the sc card out and stick it into any unix box just to check the card it won't load anymore in the box when i put it back
<buzzmarshall>
i suspect somehow something is touching something in the filesystem format but can't seem to isoloate where the issue is coming from
<buzzmarshall>
i also notice in the libreelec program that once the img file is programmed and when looking at the completed sd card in the program that the box with the destination drive in seems to throw some almost like ascii garbage in fromt of the string showing the usb drive name
<buzzmarshall>
anythoughts or ideas would be appreciated
<buzzmarshall>
normally on the le masters that i have been working on everything is fine but thats based on all the newer boxes
<buzzmarshall>
in this case i am trying to add some older s812 boxes on datrh/demetris builds that are pretty much based on le anyways
RedSoxFan07 has joined #libreelec
<buzzmarshall>
the project tho once programmed on a windows box seems to work fine
<buzzmarshall>
ive had kodi add in all the typical plugins and even scanned in over 4K of media from my local storage boxes without any issues
pletopia has quit [Remote host closed the connection]
<buzzmarshall>
its just this programming thing thats preventing me from posting the sources and a couple older releases for some of the s812 boxes running on the latest 18.6
<pragmaticenigma>
buzzmarshall: Do you have anything automounting external drives when they're attached to the *nix boxes?
<buzzmarshall>
nope
<buzzmarshall>
ive got a small usb to sd card adapter that i use which i normally use and thought mabye it was that
<buzzmarshall>
ive used it for years and went got another new one and its the same
<buzzmarshall>
but they work fine on win7 and even my imacs
<buzzmarshall>
wierd
<buzzmarshall>
the bulk of the build is based on datrh's which he is releasing for the minix boxes
<pragmaticenigma>
these are using the two partition approach on the SD card?
<buzzmarshall>
yep
<buzzmarshall>
i even dd'd it manually
<buzzmarshall>
same result
<buzzmarshall>
and when i freeze the box at the storage hang message
<buzzmarshall>
i can see thru the debug a bunch of errors regarding file formats
<buzzmarshall>
but most of them are typical things like no support for ext2/ext3
<buzzmarshall>
being the box isnt finishing booting i cant ssh into it to see and the only other would be to rip the box open and install my serial adapter but was hoping to find the issue without pulling his box apart
<buzzmarshall>
so ive just been using a keyboard once it freezes at the debug message to write the screen to a usb stick to offload them and look at them
<buzzmarshall>
the only other thing ive seen is some error/warning messages about journalling stuff which is kinda what ive been researching trying to isolate the issue
<pragmaticenigma>
wish I knew more on how to help... Rpi and single board computers are all new territory for me
<buzzmarshall>
been doing that most of the week while self isolating
<buzzmarshall>
then last nite i thought it just give a windows box a whirl and it actually worked
<buzzmarshall>
thats cools
<buzzmarshall>
anythoughts or ideas from anyone is appreciated so thanx
<pragmaticenigma>
buzzmarshall: One thing that comes to mind is to monitor DBUS and UDEV on your linux machines... see if their triggering anything when the cards are inserted
<buzzmarshall>
ive been using linux since day one and normally have no issues with things but i suspect something is off in the build scipts someplace and thats still a bit of a new area for me as i normally use my own build/toolchain which is totally custom
<pragmaticenigma>
might also help to expand your net, maybe see if there are some dev channels for other single board machines, including RPi and see if anyone in there knows of any special flags for your builds?
<buzzmarshall>
at 1st i noticed on my main build machine which 18.04 that the constant swapping of the sd card was leaving a persistant drive reference in the /media/buzz that would only go away on reboot of the workstation
<buzzmarshall>
so i was lookin at the udev stuff to see if something had happened to the automount on that machine
<buzzmarshall>
but that didnt seem to be the issue
<buzzmarshall>
i know that the machine > programmer > img > box does work as it should on the normal builds when i build for the S912/S922 and even my RK3399 based stuff
<buzzmarshall>
whatevers going on seems to be rooted in trying to build a project ive inserted into those new build projects
<buzzmarshall>
originally i addedd a project to the conventional le sources
<buzzmarshall>
which had some back ported stuff (mostly build script stuff) from datrh and demertis builds
<buzzmarshall>
then decided to move the project into their builds thinking sticking a project into LE like that was not going to work
<buzzmarshall>
then found thats where it seems to be rooted
<buzzmarshall>
but then released that the windows machines actually worked when programming it which proved the end resulting img files for the box actually works
<ducasse>
i'm running le 9.2.1 on an rpi4 that freezes after a while of video playback. i thought that might be a temperature problem and installed heatsinks, but no luck. any ideas what to try? when it's frozen it's no longer reachable by ssh, doesn't respond to ping, and keyboard has no effect.
<buzzmarshall>
my instincts are telling me its something to do with a difference in how a windows machine sees a ext4 file system when compared to a unix machine
<buzzmarshall>
ducasse: sorry i don't have rpi4 yet or i would try and help
<buzzmarshall>
have you tried looking into the kodi log file thats normally stored in the .kodi/temp directory
<buzzmarshall>
see if it gives you any clue on whats hung
<buzzmarshall>
thats assuming the directory layout on the rpi is the same as the normal boxes
<ducasse>
i had a look, but it seems it had no opportunity to write anything
<buzzmarshall>
when the box is still running can you ssh into it?
<ducasse>
before it freezes, yes
<buzzmarshall>
if so maybe scour thru a dmesg and see if you see anything going on
<ducasse>
i have a 'journalctl -f' running now, will try to freeze it again
<buzzmarshall>
once this virus stuff clears i want to get a rpi4 to play with as they seem to be really popular
<buzzmarshall>
im basically playing with all the normal sbc boards that are around while trying to maintain a pile of older 812's for a bunch of friends that want to wait till matrix is released then they will update
<buzzmarshall>
but the rpi4 looks interesting and even though i am not a big fan of broadcom want to get a couple to play with