You will need a PSU that delivers 2.5-3 amps and a heatsink to have reasonably stable overclocking on any pi board. If you're using MPEG2 encoded media you'll also want the codec license so things are hardware decoded.
Posts by chewitt
-
-
There are no legitimate uses for usenet on a mediacentre box; only content theft. You won't get much advice on that in this forum.
-
You're already using the preferred combination.
-
You need to provide the boot log so we can see what freaks out and causes the reboot. It's not a normal experience, but with older AMD cards there are enough weird driver bugs that remain unresolved that it's no great surprise.
-
IP licensing is ARM's entire business model. You're suggesting they give it all away for free. I'm pretty confident that isn't going to happen.
-
It works for everyone else..
-
In the ARM license model the SoC vendor licenses features for their devices and ARM provides a driver (or drivers) built specifically for that silicon manufacturer. So the ARM provided driver for Mali T820/830 chip in the Amlogic S912 boxes only works on Amlogic boxes.
-
Not supported. Might eventually be supported, but will require you to nuke the Armbian install.
-
Nothing official for some time. Maybe for Kodi Leia release (no date is scheduled). The current Kodi Krypton builds in circulation from the git repo from Kwiboo are effectively discontinued as developers have now switched to the Leia codebase which is still rather experimental for DRM/KMS and V4L2 things.
-
You don't think an online petition would help?
The number of users with an S912 device is statistically insignificant as a percentage of our total userbase and our entire userbase (including all the pi users, NUC users, etc.) is statistically insignificant against the number of "Kodi on Android" devices with an S912 chip that work fine. The sum of money involved to license all S912 chips produced is non-trivial so I don't see a compelling business case that would suddenly make Amlogic have a change of heart. You're welcome to do something if you want, but in the grand scheme of things I don't see this helping.
-
Current testing has been done on RK3328 and RK3288, not RK3229, and there are no official releases for any RK devices. The proof of concept images for TinkerBoard etc. that are in circulation using Kodi Krypton are now discontinued as the developers working on RK support switched to Kodi Leia in recent weeks, i.e. there will be no further improvements/updates to the Krypton images.
-
block devices detected by the kernel are automounted via udev, e.g. /usr/lib/udev/rules.d/60-block.rules
-
But what about other solutions like DLNA or UPNP?
Neither of them are "casting" protocols which is what you are asking for, and there are no broadly supported open source "works on all devices" casting protocols available, which is why Kodi hasn't evolved support for them. If/when that changes, Kodi will change.
-
Create a DHCP reservation for the NUC in your router so you can predict what IP it receives. Now create a USB and install LE normally (to USB or HDD it doesn't matter). After install it will boot and you end up with a black screen, but this is normally an Xorg issue and not a total failure to boot the core OS. Now SSH into the box's IP and run "cat /var/log/Xorg.0.log | paste" so we can see why there is no display. I have a hunch that this is an Xorg modeline issue.
-
It's a perfectly stable beta release though, and my comment is more directed at your moaning about being unable to collect logs off the box due to your broken samba configuration which is (from our perspective) a self-inflicted problem.
-
Current intention is 8.2.0 once Kodi 17.5 is released.
-
Two suggestions if there is no "network" solution to the stupid ISP:
#1. Get an RTC board for the pi so that date/time is remembered over reboots and doesn't have to depend on NTP updates.
#2. Try setting the router IP as an NTP source; as some/many routers will respond to the request. As long as the router's internal clock is fairly accurate on current time the pi will get a time/date that's close enough for YouTube etc. to work and you have a workaround. You can also get an NTP server app for other machines in the house Win/Linux with a persistent (if not accurate) clock to pull the same trick.
-
Do you guys think we'll ever get proper fbdev Mali libraries?
No. Never. Amlogic has no commercial interest in paying a large amount of $$$ to appease the small number of Linux users hacking their Android product. It sucks for us, but if I were them I'd probably make the same business decision so I don't blame them.
