TonyMac32

https://github.com/T-Firefly?tab=repositories I don't see it, but I'm using my cell phone. ;-) Sent from my Pixel using Tapatalk

No, it's not on their github, perhaps it's just the default Rockchip kernel -or- it's from Firefly.

Haha, I have some ideas too, but I'm in the boat with you that it's not high on my to-do list. I'll mess with it some more and see. Sent from my Pixel using Tapatalk

We don't provide a kernel.org LTS 4.4 for Rockchip products, so I would never be referring to such a thing in these forums. . I just changed the 4.4 source from the MiQi vendors to Rockchip directly, so there was a higher than normal chance an issue had been missed there. Sent from my Pixel using Tapatalk

You don't say?!? We provide the vendor kernel based image as well, which is 4.4. I know better than to assume anything based on the thread name, and thought I'd get clarification. Thank you for the PR, I'll test it later today, glad to hear you've had success otherwise with the mainline image. Sent from my Pixel using Tapatalk

ugh, x is just plain failing to find/load the driver.

So far there shouldn't be Bluetooth, but the Tinker mainline does have wifi and should have sound. (I may need to release a new image for sound, I'd been focusing on the 4.4 kernel) This thread answers the question from the other about which kernel we're talking about. I will get to work on that tonight, the "dev" patchset is by no means complete since it's a moving target and I've been otherwise occupied.

Which device tree? In kernel 4.4 or 4.14?

Doh! I forgot that too, it was a side project on the bench last night, did not look carefully. ;-) Sent from my Pixel using Tapatalk

Well, perhaps Swiss? ;-) Sent from my Pixel using Tapatalk

Yes, although I myself have never been able to aggravate it. I've been trying to "diversify" my test methods, but it may be the link partner is partially responsible. Maybe I should get a garbage AP and test against that, some $10 special. Mainline is using a particularly old version of the driver for one reason or another, Rockchip a newer one.

OK, I did not get a bootloop on the eMMC. X did not start automatically, but issuing "startx" as root worked, I'll check it as a non-superuser. glmark2 is telling me it's still on llvmpipe, score of 33. I'm going to guess this has to do with the "odroid" user. armbianmonitor: http://ix.io/WmN xorg: https://pastebin.com/fUdd8mX0

Wirklich? It's a shame there are no German speakers here... How old is this project? Why bigger than a Pi? Sherlock "Tido" Holmes will find the answers.

So, design-off, guys? First one to boot Armbian on their own V3s board wins?

Driver differences, clock source adjustments, etc. There's a lot of difference from one to the other that could be the difference on something so marginal.

A good reason for him to not give me such rights and let me stay free.

Something new to me is a growing list of "we work with Tinker Board" accessories on Amazon: https://www.amazon.com/gp/product/B078WK1R2R/ref=pe_3444240_275372910_em_1p_4_im I am more than a little amused by the size of that fan... Of course remember my solution to throttling... 4x the heat sink and a tiny fan. The reason I didn't post any others is that I wouldn't recommend any of them. None of the supplies are specific about output voltage (if 5.0, just say no) and most of the cases are just rebranded, and many would cause a lot of pain and suffering if you are looking for performance.

you can switch to beta using the armbian configuration tool, I don't think anything in particular has improved with the Tinker between 4.14.14 and 4.14.23

I'm willing to do some testing on this as well, I have an XU4 available. (Otherwise, like tkaiser, my board would never see a monitor).

No worries, I'm fighting off a nasty respiratory infection at the moment and haven't been able to focus properly.

The support for this was never more than experimental, so I wouldn't be surprised to find more bugs. The only reason it got as much support as it has is because it is based on the same family SoC as the Odroid C2 and Le Potato. Can you give me the name of the image file you used? That sounds related to the memory mapping bug that should have been fixed https://github.com/armbian/build/blob/master/patch/kernel/meson64-next/1020_GXBB_memory_allocation_meson_GX.patch This should be the newest download, and should be clean/as up to date as possible: https://dl.armbian.com/nanopik2/Ubuntu_xenial_next_desktop.7z That's a 4.14.15 from January with all known bugfixes.

You are talking (somewhat impatiently) to him. My priorities are bugfixes, then features, I've had a few bugs to look into since releasing the new kernel to the wild. This should be a very simple update, I will post in this thread when it is implemented, should not be long, hopefully I can roll it into a bugfix release for the board. As is rather lengthily described elsewhere, this is a project run by more or less volunteers for limited compensation of any sort. I have been unimaginably grateful for the help I've received getting/keeping this board running, but at the end of the day I am a man, not a wizard, and have only so many hours and so many coffees. And a wish to keep my wife...

Interesting. And this happened on multiple reflashes of the media? (I assume since you tried mainline as well). What is the SD card being used, and do you have another of a different brand/capacity for a quick test?

You can always contribute to the project (big "Donate Now" button at the bottom right of this page), I know that Myy has some links in Github for donations, as for myself I have an amazon wishlist for those interested (only shared on request), it's how I get some hardware for support purposes that I wouldn't buy on my own (like the RPi touchscreen).

I'm afraid at present it only works with 4.4. I can't give you a very good reason for this, the rtk_hciattach program simply refuses to function properly with the Tinkerboard on 4.14. @Myy and myself spent some time working on it https://github.com/Miouyouyou/MyyQi/issues/7, I got some progress toggling the BT gpio's manually, Myy wrote a driver to help, but in the end it simply refused. Now, I lost track of it long before the conversation was over, and I will be trying to move some of the progress from the default image to the Next image, so I will have another go of it, and I know there were some efforts to make it mainline without needing that attach tool at all, I'll have to see what became of that.