TonyMac32

The 3.5 is just a USB device directly soldered to the board, so yes, that's the one that took some adjustment. There have been some reports of I2S through HDMI not working properly lately, I need to review Sent from my Pixel using Tapatalk

I don't control the package system, I just do the dusting and upkeep of the kernel on the board. As far as that goes, the newest 4.14 source available should not be significantly different to the current, and you can find the patches we use HERE Any patches newer than the source package could be applied, then built. @Igor can speak to the source packages.

Do you have a voltmeter to make sure it is actually outputting the rated power? it is not uncommon to get a crappy supply. As is widely said in many languages: "Trust, but verify" It is an img file, use Etcher to write the image to an SD card. Is this a Tinker Board or Tinker Board S? https://tinkerboarding.co.uk/wiki/index.php/Setup Shows the jumper positions for the Tinkerboard S and some explanation.

If you have a Bionic host, or Docker, you can simply clone the Armbian build system and build an image for the Tinker Board. read up in docs.armbian.com for details. I'm currently working on 4.18 and trying to restabilize 4.4, there were some... unfortunate events to happen with the Rockchip repo we were using.

I have no intentions of letting the board die, and it is supported well in mainline. I don't see Armbian going anywhere in the meantime. Audio should "just work", but I admit I haven't checked in a while, and kernels have been changed. Worst case you should just have to select the proper output in PA.

Please read the giant red banners at the top of the screen that you must have dismissed, we need more information in general. armbianmonitor -u, please.

Another update, I experimentally built a 4.17.8 image today and USB is working again. @Igor if you have the C2 it would be good to verify there as well, we should roll out new meson64-next images that work. Also still getting spammed with "failed to change CPU Frequency: -5" here.

@Neil Armstrong Awesome, I just want to make sure if I'm seeing anything new and exciting, you know about it.

Ah, nice, one that plugs up that 4the USB hole.

I would recommend reflashing 4.14 and freezing the kernel for now using the armbian-config tool. We will have to verify this failure (I was not aware of it) and look for a solution.

I'd say open it up and see what the hardware inside is, and give it a try. We don't support TV boxes because even our worst single board computers are typically better documented. However, there is a community recipe for a Z28Pro in the build system if you wish to follow docs.armbian.com and build it yourself and give it a try. Sent from my Pixel using Tapatalk

I assume you are using a Stretch image then? We are not always the fastest to react when a new Debian release occurs, but as long as there is mainline support I plan on keeping the board maintained.

The aluminum brick on my RPi 3 doesn't block wifi completely, but I haven't tested how much it reduces the capabilities. As far as the IR-port goes, I'm afraid that's universal, for any of those you will probably have to get out a drill.

@guidol has a good looking case mentioned in the NanoPi K1+ thread:

I see that on Amazon.de, but not amazon.com for us colonists... top and bottom have no holes, but that certainly looks sharp. Add it to the "Pi-factor cases" topic?

Yes, that one is still counting from 1000. Do you need multimedia or touch screen/camera? If not I recommend a mainline kernel, the legacy kernel has sadly taken a turn for the worse recently and needs some work. Sent from my Pixel using Tapatalk

I get this anytime after I update my build machine: dpkg: warning: downgrading aptly from 1.3.0 to 1.2.0

The mainline staging driver is quite old base source, while it has gotten a lot of attention, I think it still has some issues. The latest Tinker OS (and until the issue with upstream Rockchip, Armbian Default) uses a brand new driver with some bugfixes. I am trying to establish what has and hasn't been included in the "snapshot" source package we've fallen back to while Rockchip's kernel is sorted out (or not), and will be rebuilding from there. As it stands the 4.4 Armbian build currently available is a newer driver than used in mainline.

Please provide the output of armbianmonitor -u I had the gpio returned to base 0 (Rockchip decided it should be base 1000 at some point for unclear reasons involving Android if I remember correctly.) If that is not still the case, it could be due to the recent issue with kernels resulting in us reverting to an older kernel source. Some of the the patches that were no longer needed may again need added.

*rabble rabble* I wrote utilities whose lengths were measured in bytes *rabble rabble* But to be fair, 20 MB seems about 18 MB too big at least.

... and I have another gem I hadn't noticed before: It hasn't crashed X or anything, probably why I didn't note it before, I decided to spit out the dmesg after a night of running to see if I got more cpufreq errors. It would seem that the errors are occurring at boot time, but not thereafter, frequency scaling is working fine.

Ah, a XEON would be nice. my machine won't boot an nvme directly so I have a spinner for the system, I put the ccache local on the ssd. 16 GB DDR3. I also have a setup on a cheap $300 ASUS laptop, i3 and spinning disk. It is slow, but works if I'm wanting time away form my in-laws.

There are a few things we can patch into it that were bugfixes, I'll dig around and figure out what is what. (the new wifi driver is one I can think of). Feature wise it was complete other than camera (which I think just needs time and someone actually working on it who cares)

So far the K2 has behaved for me, but obviously 1 guy may not provide an exhaustive enough test. I pushed HDMI audio fixes for the Next kernel, which is currently 4.17 if anyone was getting frustrated over that. Despite the applicable patch, DVFS is still showing me clock setting failures, it will change clock speed (according to the kernel, but we know it actually has little to no control of that), but only toggles between min and max (at least in my experience so far) [edit] I have found that I have no USB peripherals on the K2 with 4.17. Will check into it. SSH'd in: dwc2 c9000000.usb: c9000000.usb supply vusb_d not found, using dummy regulator [ 2.614838] dwc2 c9000000.usb: c9000000.usb supply vusb_a not found, using dummy regulator [ 2.627851] dwc2 c9000000.usb: dwc2_check_params: Invalid parameter lpm=1 [ 2.627856] dwc2 c9000000.usb: dwc2_check_params: Invalid parameter lpm_clock_gating=1 [ 2.627859] dwc2 c9000000.usb: dwc2_check_params: Invalid parameter besl=1 [ 2.627863] dwc2 c9000000.usb: dwc2_check_params: Invalid parameter hird_threshold_en=1 [ 2.628240] dwc2 c9000000.usb: DWC OTG Controller [ 2.628259] dwc2 c9000000.usb: new USB bus registered, assigned bus number 1 [ 2.628287] dwc2 c9000000.usb: irq 32, io mem 0xc9000000 So, everything is powered, but no one is home.

OK. I had forgotten the source packages being built, stupid me...