bedalus

This might just be the best opener I've ever seen! Made me smile, thanks

I don't think I can help diagnose the problem. After I changed the TV mode, the picture was there, and the display options recognised the TV model and provided the option for 3840x2160. I selected that and the resolution worked fine. I've now added that to the xorg conf and rebooted. The desktop appeared in the new resolution, but I'm not sure which thing I did that fixed it. Sorry, this was pretty useless for debugging the problem. I've noticed that in this this resolution, when I drag windows around they leave trails and lag behind the mouse. Is this normal due to the limited ability of the chip?

I bought myself a wired USB keyboard so I could try this tutorial. I've got the new March 4.4 kernel xenial desktop image, and I followed the instructions. I got to the point where you restart x, so I issued sudo systemctl restart nodm.service and got booted back to the full-screen root terminal. Is this the wrong command? I issued 'reboot' and got a black screen, then a full power cycle, and got a black screen. Any ideas? Ninja edit: I just cycled my TV through it's HDMI modes, and the picture is back. Not sure what the difference between mode 1 and mode 2 on the TV is, but I now have a signal. Is there supposed to be a 4k setting in the xorg conf file, e.g 3840 x 2160 or 4096 x 2160?

Good memory, yes I tried to diff the config on the page 14, but page 15: ...is where I detailed most of my findings. Looks like the dongle started working between 4.11 and 4.12

Does this improve the chances of my wireless keyboard working? It's not bluetooth exactly, it's got it's own proprietary dongle. It works on the mainline kernel, but not 4.4, even though the keyboard is ancient. I wonder if there are some kernel config options that are needed to support USB interfaces that are enabled in the mainline, but not in 4.4? I'm really looking forward to the new image, even if I have to bring my keyboard home from work to test!

Ah... I wonder if this is what happened to me. Maybe if I'd left it long enough the CLI would have appeared. I'll give it another go. If I get a CLI I'll run armbianmonitor -u UPDATE: I left it on for several hours and checked it again, but no output on HDMI. I disconnected the power, then reconnected, and thought I had a black screen, when in fact I had output. On the quad HD screen, the login console is tiny at the top left! I barely noticed it. Unfortunately I can't run armbianmonitor -u since my keyboard won't connect on this version of the kernel. It works on the mainline version though.

I couldn't install the debs since there was no video. When the new images are released I'll have another try and get back to you

I've hit a snag. With the default download (Armbian_5.38_Tinkerboard_Ubuntu_xenial_default_4.4.112_desktop) I get nothing on the screen. I also tried a different image for good measure (Armbian_5.37_Tinkerboard_Debian_jessie_default_4.4.104). I think maybe the issue is that it's a 4K TV. I didn't have any issues with my old HD TV, but we got rid of it! Any config changes I can apply after flashing the image so I get an output?

Righto, will do!

I'm happy to do some testing. What's the ideal set-up? Download the legacy version and then dpkg the debs? After that, what are we testing for, working features and uptime without random reboots?

bedalus@tinkerboard:~$ psd p Profile-sync-daemon v6.31 on Ubuntu 16.04.3 LTS Systemd service is currently inactive. Systemd resync-timer is currently inactive. Overlayfs v23 is currently active. Psd will manage the following per /home/bedalus/.config/psd/psd.conf: browser/psname: chromium/chromium owner/group id: bedalus/1000 sync target: /home/bedalus/.config/chromium tmpfs dir: /run/user/1000/bedalus-chromium profile size: 42M overlayfs size: recovery dirs: none

I've been waiting for my Sentio Superbook to turn up (I think it will arrive in a month or two) so I haven't had much use for my tiny portable desktop, which has gathered some dust over the last few weeks. I've sneezed it off, and flashed the lastest nightly Armbian_5.32.170916_Tinkerboard_Ubuntu_xenial_dev_4.13.0_desktop.7z (2017-09-15 08:10 589.2 MB) I'm happy to report that my bluetooth keyboard continues to work with the nightlies, and since the last version I tested, I'm extremely pleased to now find that there is a login screen. Also, Chromium now works again. Another thing that had bugged me, being prompted for admin password for wifi reconnect, has now been fixed. I'm well chuffed.

Wow, this is such a great contribution for RK3288. It must be immensely satisfying to remake this driver and see it working!

No, I mean the stock Armbian OS of course! Armbian for the win!

Is it possible to get the stock OS with the new kernel? Is this something I should be having a go at building myself? At the moment I can only use the last nightly because of my bluetooth keyboard limitation.

I think this may have gone up recently: http://opensource.rock-chips.com/wiki_Mpp It doesn't mean anything to me, but the vpu is mentioned so maybe it's useful, or if not, maybe will become useful if they add further documentation.

EDIT: I deleted a lot of the results I just posted after re-reading the thread... It's all been done before! I got similar resuls as others who've done the test, around 6.6khash/s followed five minutes later by a decline to around 6.1, caused by thermal throttling to ~1.7GHz. At least I seem to have a stable setup. Any other tests I can run on armbian's behalf? Anything I can do to help, I'm happy to give it a go.

Well, I was allowed to borrow a USB keyboard from work, and I flashed the standard version with the mainline kernel, and... [ 2.033927] usb 1-1.3: new low-speed USB device number 3 using dwc2 [ 2.116818] usb 1-1.3: New USB device found, idVendor=046e, idProduct=5577 [ 2.116831] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2.116841] usb 1-1.3: Product: USB Multimedia Cordless Keyboard [ 2.116850] usb 1-1.3: Manufacturer: BTC [ 2.212636] usb 3-1: config 1 has an invalid interface number: 255 but max is 6 [ 2.212648] usb 3-1: config 1 has no interface number 6 [ 2.214117] usb 3-1: New USB device found, idVendor=0bda, idProduct=481a [ 2.214130] usb 3-1: New USB device strings: Mfr=3, Product=1, SerialNumber=2 [ 2.214139] usb 3-1: Product: USB Audio [ 2.214148] usb 3-1: Manufacturer: Generic [ 2.214156] usb 3-1: SerialNumber: 201405280001 ... [ 4.333263] input: Generic USB Audio as /devices/platform/ff500000.usb/usb3/3-1/3-1:1.255/0003:0BDA:481A.0003/input/input1 [ 4.385590] hid-generic 0003:0BDA:481A.0003: input,hiddev0,hidraw0: USB HID v1.11 Device [Generic USB Audio] on usb-ff500000.usb-1/input255 USB 1-1.3 never gets allocated as an input device, even though it's detected (USB 3-1 later gets a device, which are the bottom two lines after I cut an irrelevant section). So perhaps something to do with some hid options? I took the diff between the configs: > CONFIG_HID_ACCUTOUCH=m ... > CONFIG_HID_CP2112=m ... > CONFIG_HID_NTI=m Not sure if these are relevant, it's difficult for me to guess whether it was a config option that helped, maybe it was just some mainline commit that fixed something between 4.11 and 4.12. Anyway, if you want to pursue the reason, I've attached the output of armbianmonitor -u and the diff between the two kernel configs. I'm out of ideas, but happy and lucky to have a working cordless keyboard! armhwinfo.log config.diff

root@tinkerboard:/home/bedalus# lsmod Module Size Used by snd_soc_hdmi_codec 16384 0 r8723bs 552960 0 dw_hdmi_i2s_audio 16384 0 mali_kbase 319488 0 Nothing to see with lsmod. However, udevadm gives me: root@tinkerboard:/home/bedalus# udevadm info --query=all /dev/input/by-id/usb-BTC_USB_Multimedia_Cordless_Keyboard-event-kbd P: /devices/platform/ff540000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:046E:5577.0001/input/input0/event0 N: input/event0 S: input/by-id/usb-BTC_USB_Multimedia_Cordless_Keyboard-event-kbd S: input/by-path/platform-ff540000.usb-usb-0:1.3:1.0-event-kbd E: BACKSPACE=guess E: DEVLINKS=/dev/input/by-path/platform-ff540000.usb-usb-0:1.3:1.0-event-kbd /dev/input/by-id/usb-BTC_USB_Multimedia_Cordless_Keyboard-event-kbd E: DEVNAME=/dev/input/event0 E: DEVPATH=/devices/platform/ff540000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:046E:5577.0001/input/input0/event0 E: ID_BUS=usb E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_INPUT_KEYBOARD=1 E: ID_MODEL=USB_Multimedia_Cordless_Keyboard E: ID_MODEL_ENC=USB\x20Multimedia\x20Cordless\x20Keyboard E: ID_MODEL_ID=5577 E: ID_PATH=platform-ff540000.usb-usb-0:1.3:1.0 E: ID_PATH_TAG=platform-ff540000_usb-usb-0_1_3_1_0 E: ID_REVISION=0310 E: ID_SERIAL=BTC_USB_Multimedia_Cordless_Keyboard E: ID_TYPE=hid E: ID_USB_DRIVER=usbhid E: ID_USB_INTERFACES=:030101:030102: E: ID_USB_INTERFACE_NUM=00 E: ID_VENDOR=BTC E: ID_VENDOR_ENC=BTC E: ID_VENDOR_ID=046e E: MAJOR=13 E: MINOR=64 E: SUBSYSTEM=input E: USEC_INITIALIZED=4130433 E: XKBLAYOUT=us E: XKBMODEL=pc105 So usbhid. I think I'll borrow a keyboard from work then we can find out for sure. IKONFIG is set, so if I'm able to use a different keyboard and log in, I can diff the exact config used against the nightly.

I would if I could, but I've no way to log into the device on the standard images as this is my only keyboard! Maybe they'd let me borrow one from work. I have to say thanks thanks for all your work and input in this thread. When I got this device I was unaware of armbian, and happened to discover it because you posted a link in the asus forum: https://tinkerboarding.co.uk/forum/thread-330.html I found armbian and its users so interesting I must have read this entire thread two or three times! If you follow the link above you can see how I followed your example with GPIO power and an uprated heatsink and was able to hacksaw a hole into my case and attach a little fan! You can even see my dongle

http://sprunge.us/fafZ

There's something different about the 4.12.3 kernel, I can use my bluetooth keyboard with it. It's not using the native bluetooth, it's got it's own dedicated dongle. When I tried the stable versions (both legacy and mainline) I couldn't log in, I'm guessing because the drivers aren't enabled in these older kernels. Did the config change in the daily build? Are the commits in the source repo (sorry, this is a passing thought, and I'm at work, so shouldn't really be on here!) Edit: Home from work. I think I found the commit: https://github.com/armbian/build/commit/ffb032449e1063d6f43862a9b2c430d99c54137d but I can't spot what might have been turned on that allowed the bluetooth dongle to function.

Open a terminal then issue: su apt-get install npm git clone https://github.com/Enrico204/Whatsapp-Desktop.git cd Whatsapp-Desktop nano package.json Make this edit: "build:linux": "electron-packager ./app \"WhatsApp\" --out=dist --platform=linux --arch=x64 --version=1.4.3 --icon=assets/win/whatsapp.ico" to "build:linux": "electron-packager ./app \"WhatsApp\" --out=dist --platform=linux --arch=armv7l --version=1.4.3 --icon=assets/win/whatsapp.ico" Exit nano and save changes. Back in terminal, follow the usual build instructions: npm install cd app/ npm install cd .. npm run build:linux Change the current directory to the output folder (after the fairly quick compilation completes) cd dist/Whatsapp-Desktop-armv7l/ Launch the app: ./Whatsapp I set the app to start and automatically log in using the tick-boxes in the settings menu. The app was in the system-tray after a reboot, and worked just fine after a refresh (ctrl+r)

I flashed the file from the download link above: Armbian_5.32.170724_Tinkerboard_Ubuntu_xenial_next_4.12.3_desktop.7z After entering root/1234/etc and getting to the desktop, the first thing I tried was a reboot, and it successfully rebooted back to the desktop. I tried again from the newly rebooted desktop, and success again.