Latest image
It is working fine I hear 
Posts by vpeter
-
-
I've seen there are parameters for forcedeth module which could help:msi=0 msix=0 but how can I use the parameters? it isnt a module, its compiled directly into kernel
I think you need to add in extlinux.conf as chewitt suggested but it must be in formCodeforcedeth.msi=0 forcedeth.msix=0 -
It should work with any kind of reboot.
It would be good to understand why unmount fail. I assume because one program has open files on it and still running.
-
generally this 4.4-based image works fine for me.
Thank you for the feedback. All good then. Sending pull request for 8.0.2
-
Execute this in console
Codeprintf "killall transmission-daemon\nsleep 1\nkillall -9 transmission-daemon\n" >/storage/.config/shutdown.shand this
Code
Display Morecat << EOF >/storage/.config/system.d/transmission-stop.service [Unit] Description=Transmission stop script After=network.target [Service] Type=oneshot Environment=HOME=/storage ExecStart=/bin/true ExecStop=-/bin/sh -c ". /etc/profile; exec /bin/sh /storage/.config/shutdown.sh" RemainAfterExit=yes [Install] WantedBy=kodi.target EOFReboot and then once again. This second reboot should be better
-
Which transmission addon are you using?
-
Bump!Maybe killing transmission from script /storage/.config/shutdown.sh would help.
Or making new service similar to this and kill it from there. -
In LibreELEC
Codeecho "KERNEL==\"tty[0-9]*\", GROUP=\"tty\", MODE=\"0660\"" >/storage/.config/udev.rules.d/99-input.rules
but I doubt this will make any difference. -
Should it work in full by implementing some key mapping in LibreELEC ?
Probably. But I don't have such experience.-----------------------------------------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------------------------------------------I would like to ask if someone can try image below? It has 2 major changes:
1.) switched to galcore v5 on linux 4.4 and now images/thumbnails works
2.) default ethernet speed is set to 100 mbit/s because this always works reliable. If someone wants gigabit speed lineCode#forcegbit_arg=fec.forcegbit=1
must be uncomment in uEnv.txt file and reboot.
If this all goes well it will be included in LibreELEC 8.0.2. But without more broader testing things like this can be problematic.LibreELEC-imx6.arm-8.0.1-100mbits.img.gz
LibreELEC-imx6.arm-8.0.1-sr-3.14-100mbits.img.gz -
It works here just fine. Enter ip addres, netmask and gateway.
-
Situation with BT is the same as before.Try to debug issue with tools hcitool, hciconfig, ...
-
With this image I have a blank screen instead of menu when movie ends
Strange.
Can you make one fresh sd card and test that. And also official image? In image above I made few changes regarding making pictures thumbs. Maybe something went wrong (even if I don't see anything). -
On "real" ubuntu I did this. I assume you need to do same in docker?
-
Did you have a chance to test bluetooth?
Don't remember if I did at that time. But I did now. And speaker did connect to cuboxi. I selected audio device as pulseaudio and sound come from speaker.
I had to select "trust and pair" or something like that when connecting bt speaker. First I selected pair and it didn't connect. After reboot and using different option it works.Tests were done with LibreELEC-imx6.arm-8.0.1.img.gz image.
-
This Problems must be somewhere within Kodi 17 (Krypton) - or the way Kodi allocates the Memory for Photo Thumbnails.
Under Android (WeOS) and Kodi 17.1 RC I have the very same behavior!
Could be. It was working fine on 7.90.006 for imx6. But now it works also in 8.0.2How big pictures you have? And how much memory your wetek has?
4k images needs more than 60MB of memory per picture. And I think at least two pictures are resized at the same time.
This problem was confirmed also on Wetek Play with Kodi/LE. -
Was using:PROJECT=Generic ARCH=x86_64 tools/download-tool
Why not just use make and download only required packages.
CodePROJECT=Generic ARCH=x86_64 make image -
As long as you know what you're doing, there's no problem building as root.
Maybe. But there were multiple cases in the past where this didn't work as plan :s Better build as user and avoid one possible problem.The main problem here is that sources are now in folder moby-1.13.1 (content has been changed even if filename is the same - happen in the past for other packages). That's why docker package.mk needs new line
CodePKG_SOURCE_DIR="moby-$PKG_VERSION"Time to add SHA256 checksums in our build system. Who will start on that (I have free time)?
-
First of all don't build as root user. Remove complete build folder and start again.
And you build addon with ./scripts/create_addon docker.