Posts by chewitt

nickr .. Chromium (for Generic builds) was pushed to the repo last night

Changes were committed to build nand-install images in the past couple of days so this should be 'solved' when 6.95.1 ships, soon.

Can you run "lspci -nn | paste" and share the URL so we can see the PCI device ID's. The bcma driver in the kernel needs patching to remove the ID so that it becomes unsupported and thus defaults to using wl. It might not make the next build (first beta) but should be included fairly soon.

Acestream is frequently found in banned repos but the add-on itself is not on the banned list.

The issue with the addon looks like it's not packed (zipped) correctly .. but this really isn't the forum for figuring out which one of 300+ untested commits added to the OE beta 24-hours before release broke support for something.

Create one thread per issue in future please.

rm /storage/.config/modprobe.d/wl.conf
echo "blacklist bcma" > /storage/.config/modprobe.d/bcma.conf

try the other way around then

Not yet, but I believe CvH has this on his to-do list.

echo "blacklist wl" > /storage/.config/modprobe.d/wl.conf

Please run that and reboot .. let's see if the brcmfmac driver works on that device instead of wl.

The script (or whatever sdbench is) probably assumes "full" bash or awk/cmd tools and we're using busybox applets.

A whole heap 'o repo changes were pushed this morning, including things for VDR, so before we start please reset Kodi to a clean state and try again to see if we already fixed something? (fingers crossed)

The ops team are in the process of setting-up some awesome spec build servers that we've been donated, so once we fork a 7.0 release branch (and master starts to track the 8.0 release) we should be in a position to start publishing a weekly alpha build for people to follow. True nightly builds are something we'll think about in the mid/long term once everything (and everyone) settles into a sensible operating rhythm.

I've come to a similar conclusion but I wouldn't mind if they ended up in Junk to be marked. At the moment they are just eaten

Nothing to do with tapatalk, it's Microsoft being stupid with our registration emails. We've deployed all the correct stuff (SPF, DKIM, DMARC) to ensure that our email is not seen as spam and it is handled normally by all the other services. However for some reason MS considers it bad and messages are silently discarded on their side (we deliver it successfully to them). Sadly the MS help portals are deliberately vague to avoid assisting spammers and are thus not helpful. I have a professional background architecting huge-scale email infrastructures, and honestly, I can't fathom out why they are blocking us.

It's possible, but is that going to give you a good experience? .. probably not. LE (as OE before it) is really intended to be a client OS so I'd recommend a NAS for storage and downloading tasks.

Please run "lspci -k | paste" so we can see the devices vs. driver being used and share the URL here, thanks

dr88dr88: It would be nice to do that, but Kodi settings are part of the compiled kodi.bin binary so to add LE settings there would require us to patch our own C++ code into Kodi and then pray our upstream Kodi brethren don't rearrange and trample all over some bit of code we depend on. It's technically possible but ultimately a lot of work and frequent rework, so it's not something we're likely to tackle anytime soon.

It should be exactly the same as there have been no changes to that part of the OS

All current builds are using Linux 4.4.6, the imx6 project and various experimental things may be on older kernels. What's the reason for asking?