Posts by sonofdibnah

Quote from salongo

Anyone please?

Have you tried all 3 of the remote.conf files listed in the installation instructions? I have a box that needs the HD18q remote.conf with the remote.conf from M201.

Quote from kszaq

sonofdibnah I will check if I can bring the driver back to 8.x builds. I had issues compiling it.

Thanks for trying kszaq. If I need wifi, I can always use the wifi dongle so there's no problem if it can't be done.

Sorry for the delay kszaq - the whole ssh thing is very new to me and I had to do a fair bit of reading to get you the results. You are right that the wifi did work in earlier builds, probably the 7 versions because I'd let a friend borrow the box and upgraded it when he returned it. I can restore earlier versions to test if this helps but i can't be any more specific from memory.

I hope this means something to you!

# udevadm info /sys/bus/sdio/devices/sdio*

P: /devices/platform/aml_sdio.0/mmc_host/sdio/sdio:0001/sdio:0001:1

E: DEVPATH=/devices/platform/aml_sdio.0/mmc_host/sdio/sdio:0001/sdio:0001:1

E: MODALIAS=sdio:c07v3030d3030

E: SDIO_CLASS=07

E: SDIO_ID=3030:3030

E: SUBSYSTEM=sdio

kszaq, here's another try. Thanks for looking into this for melog-2017-07-24-20.34.29.zip

So sorry kszaq. Like so many others before me I thought I could skip the rules for bug reporting and someone would fix it blind. Anyhow, if I've done it right here's something to go on. I took recreation to be going to the Network settings screen where only the wired option is available. As you'll see, I'm using 8.1.1 that you don't seem to have announced yet but the problem was there before when I was on 8.0.2e.

forum.libreelec.tv/core/attachment/1743/

Sorry my signature is way out of date.

I have a box labelled A85 which works with Libreelec on the HD18q version using the remote from the M201. I know that wifi worked when I first set Libreelec up. It doesn't now. What's happened is that "Wireless Networks" is missing from Libreelec network settings. If I connect a USB wifi dongle, these settings reappear.

Does anyone in this excellent community have any tips on what I can do to restore the inbuilt wifi or to confirm that the wifi module has failed?

Thanks for reading

Does anyone here know why I only get file copy/move speeds of around 900KB/s when copying/moving files between 2 boxes (nexteon red tick) both of which have portable hard discs attached? Box 1 is connected directly to my router by cat5e, Box 2 by Av200 powerline.

Unfortunately I can't attach both drives to the same box as there seems to be insufficient power to run both. I have, however attached a drive to my router using its Samba capabilities. The box that's directly connected to the router will transfer at about 5MB/s. That's still slower than I'd have thought for throughput on 100Mb LAN (100Mb being 12.5MB and all that).

I hope someone can shed some light on this even if it is to say that this is a feature I'll have to live with.

The issue is that I get extremely low file transfer speeds using file manager when I try to move a file between two external hard drives:

• Directly connected to one box (I have upped the power supply to support both drives).
• Each connected to a box connected by either wifi or ethernet (via powerline). In this case, one drive is set up as a windows share on the receiving box.

I've connected the 2 drives to my laptop and can transfer at about 25MB/s but when connect the drives to a box I get

Quote from The Coolest

My T95M boots into LE by default (on SD card), from there I can reboot it into Android. If I reboot from Android, it just boots back up into LE.

Sounds right to me.

Kszak, Sorry for the misleading statement that all remote keys work in Estuary. I've just realised that I'd gone back to a previous version to see if Reboot From Internal was available on it. When I read your reply, I changed the skin to Estuary and simply forgot what I'd done.

Can't believe that I could be so daft.

Quote from kszaq

sonofdibnah "Reboot from internal" is only available in Estuary Skin but should be always available.

Thanks kszaq. I'd changed to confluence skin but never considered that as the cause. It looks like this dinosaur needs to get used to Estuary.
[hr]
All my remote buttons work in Estuary!

I've installed 7.90 beta1 as an update to 7.0.3.1 (MXQ version) running from SD card. 7.0.3.1 also runs from NAND.

The NAND version offers reboot and reboot from NAND when I select the power icon on the kodi main screen. The SD version only offers reboot.

Is this what should happen? I'm sure that I remember both versions offering reboot from NAND when I've used dual boot before.

Hi kszak and happy Christmas to you and yours.

Still having boot problems with the modified 32 bit kernel on nand with my mini mx 1g/8g giga ethernet. I haven't kept count as Kashmoney has so I can't tell you if there's been any improvement.

I'm having fun learning how to do the ssh stuff.

I was just about to report problems with booting/rebooting when the post 7.0.3.10 build was released. Looks like I wasted my time updating android firmware on my Beelink mini MX. Thinking about it now, it seems obvious that if Libreelec would boot without issue before, it was the changes to Libreelec that had caused the problem.

Done several reboots on the new version without problem. Thanks as ever for this superb build.

Pajo, the box you show is the red stripe MXQ that's mentioned in the original release post. Libreelec will run like a dream on it.

Download page not working for me either.

I can't get my browser to connect to the downloads page. Is there something wrong with the page?

If you're worried about bricking, follow the advice that's already there and install to sd card. This will not brick your box if you have the wrong files. If you have and it won't run, all you have to do is remove the sd card and reboot and you will be back to android running from Nand.

You can then try other files until you get it right.

I run from sd all the time on my S905 box.