This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 2 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
TinkerOS_Debian V1.9 (Beta version) Released
#1
Curious to see if anyone has tried the new TinkerOS_Debian V1.9 yet. Any major improvements that you can see in your day to day use? 

Download from here: Download Page

Direct Link : linaro-stretch-alip-v1.9.zip

Changelog on V1.9
1.Enable iptables related kernel configs.
2.Enable boot animation.
3.Support PXE.
4.Support boot from USB flash.
5.Add ASUS wallpaper.
6.Disable some log.
7.Hold libsbc1_1.3-1_armhf.deb since the newer builds have problem.
8.Preload the package blueman.
9.Enable more NFS related kernel configs.
10.Preload packages exfat-fuse, exfat-utils, and gnome-screenshot.
11.Enable kernel config CONFIG_USB_IPHETH.
12.Enable multiple devices driver and RAID driver for RAID disk function.
13.Enable CHICONY HID driver.
14.Improve the stability of 4K media player.
15.Fix some issues for 4K Display.
16.Tune DSI output.
17.Add Option "Dri2Vsync" "FALSE" to disable wait vsync in /etc/X11/xorg.conf.d/20-modesetting.conf.
18.Don't hold libsbc1 at 1.3-1 and update to latest libsbc1 since the issue for A2DP has been resolved.
19.Fix the system freezing issue for "echo b > /proc/sysrq-trigger".
20.Enable CONFIG_OF related kernel configs.
21.Preload man-db package.
22.Update packages since Debian 9 is offically released.
23.Fix the problem that CSI camera can not work.
24.Support more HDMI resolutions.
25.Check the flag Dri2Vsync to skip waitting for vsync in fullscreen mode.
26.Enable PCM5122.
Reply
#2
The one thing I haven't had trouble with on any of the Linux or Android images from ASUS is the display. So when I burned this image this morning and booted it I was a little surprised that the display wouldnt work. It flashes the home screen every once in a while and occasionally the monitor displays "mode not supported".

I should have stuck with my rule of never loading beta software.

Oh Well!!
Reply
#3
Bug 
Hello, the last post.

I do some test with "new" TinkerOS 1.9 (beta) but ... Angry

- Modified kernel sources are now published with only ~25 commits (hundreds of rk3288 commits from rockchip-linux are not taken !) ?
- SPI does not work.
- GPIO pull-up/-down in python library does not work.
- HDMI DMT output modes does not work. It is even worse than previous release. Now instead of ignoring "unsupported" modes DRM driver sets totally invalid pixel clock (for modes >1024x768@60):

Code:
# xrandr --display :0
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 4096 x 4096
HDMI-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 380mm x 300mm
  1280x1024     60.02 +  75.02*
  1152x864      75.00  
  1024x768      75.08    70.07    60.00  
  832x624       74.55  
  800x600       72.19    75.00    60.32  
  640x480       75.00    72.81  
  720x400       70.08  


# ### FAILED:

# xrandr --display :0 --output HDMI-1 --mode 1280x1024 --refresh 75
# sudo grep dclk_vop0 /sys/kernel/debug/clk/clk_summary
         dclk_vop0                       2            3   105000000          0 0  
# ### [drm:drm_mode_debug_printmodeline] Modeline 73:"1280x1024" 75 135000 1280 1296 1440 1688 1024 1025 1028 1066 0x40 0x5
# ### NOT MATCH 105 Mhz != 135 Mhz
# xrandr --display :0 --output HDMI-1 --mode 1280x1024 --refresh 60
# sudo grep dclk_vop0 /sys/kernel/debug/clk/clk_summary
         dclk_vop0                       2            3    77142857          0 0  
# ###  [drm:drm_mode_debug_printmodeline] Modeline 67:"1280x1024" 60 108000 1280 1328 1440 1688 1024 1025 1028 1066 0x48 0x5
# ### NOT MATCH 77 Mhz != 108 Mhz
# xrandr --display :0 --output HDMI-1 --mode 1152x864 --refresh 75
# sudo grep dclk_vop0 /sys/kernel/debug/clk/clk_summary
         dclk_vop0                       2            3    77142857          0 0  
# ###  [drm:drm_mode_debug_printmodeline] Modeline 80:"1152x864" 75 108000 1152 1216 1344 1600 864 865 868 900 0x40 0x5
# ### NOT MATCH 77 Mhz != 108 Mhz
# xrandr --display :0 --output HDMI-1 --mode 1024x768 --refresh 75
# sudo grep dclk_vop0 /sys/kernel/debug/clk/clk_summary
         dclk_vop0                       2            3    56285714          0 0  
# ### [drm:drm_mode_debug_printmodeline] Modeline 74:"1024x768" 75 78800 1024 1040 1136 1312 768 769 772 800 0x40 0x5
# ### NOT MATCH 56 Mhz != 78 Mhz
# xrandr --display :0 --output HDMI-1 --mode 1024x768 --refresh 70
# sudo grep dclk_vop0 /sys/kernel/debug/clk/clk_summary
         dclk_vop0                       2            3    53571429          0 0  
# ### [drm:drm_mode_debug_printmodeline] Modeline 75:"1024x768" 70 75000 1024 1048 1184 1328 768 771 777 806 0x40 0xa
# ### NOT MATCH 53 Mhz != 75 Mhz


# ### OK:

# xrandr --display :0 --output HDMI-1 --mode 1024x768 --refresh 60
# sudo grep dclk_vop0 /sys/kernel/debug/clk/clk_summary
         dclk_vop0                       2            3    65000000          0 0  
# ### [drm:drm_mode_debug_printmodeline] Modeline 76:"1024x768" 60 65000 1024 1048 1184 1344 768 771 777 806 0x40 0xa
# xrandr --display :0 --output HDMI-1 --mode 800x600 --refresh 75
# sudo grep dclk_vop0 /sys/kernel/debug/clk/clk_summary
         dclk_vop0                       2            3    49500000          0 0  
# ### [drm:drm_mode_debug_printmodeline] Modeline 78:"800x600" 75 49500 800 816 896 1056 600 601 604 625 0x40 0x5
# xrandr --display :0 --output HDMI-1 --mode 800x600 --refresh 72
# sudo grep dclk_vop0 /sys/kernel/debug/clk/clk_summary
         dclk_vop0                       2            3    50000000          0 0  
# ### [drm:drm_mode_debug_printmodeline] Modeline 79:"800x600" 72 50000 800 856 976 1040 600 637 643 666 0x40 0x5
# xrandr --display :0 --output HDMI-1 --mode 800x600 --refresh 60
# sudo grep dclk_vop0 /sys/kernel/debug/clk/clk_summary
         dclk_vop0                       2            3    40000000          0 0  
# ### [drm:drm_mode_debug_printmodeline] Modeline 68:"800x600" 60 40000 800 840 968 1056 600 601 605 628 0x40 0x5

My opinion: RockChip seems to stop/limit support of old RK3288 chip and focusing to newer RK33xx. My patience with "big" ASUS expired after 6 month with unusable linux betas, without solving bugs, without community support, without publishing full HW schema, with design fails in TinkerBoard (CEC, RESET), with "marketing" driven product management (for example - different timing of release over the world, feed $$$ to marketing presentation and spreading fog about 4K and accelerated video playback (reality)) and finally totally crappy use of MicroUSB as power source ! Conclusion - The product quality does not match my expectation. ASUS recently sent me a note that ... "ASUS have been improved internally" ... "ASUS been discussing this situation for a long time" ... but crappy TinkerOS 1.9 was published. I am leaving this community and moving (with RockChip) to newer RK33xx. Goodbye and Happy tinkering ! Martin

UPDATE 2.0.1 beta:
- modified kernel sources - rebased to rockchip/linux branch release-4.4-miniarm that was rebased from main release-4.4 branch at Jul 21, 2017
- SPI - probably repaired (still randomly crashes)
- GPIO python - should repaired but untested
- HDMI DMT modes - probably repaired (all modes for my monitor)
I left this community in Aug 2017 due to bad product quality and community support that did not match my expectation.  Sad
Reply
#4
I was able to boot it on a different display, so I can report that the bluetooth will now let you pair a device. But it sounds like a ham radio from the 1940s when you use it to play audio. So bluetooth on linux on the Tinkerboard is still useless.

I adjusted the resolution to match my other display and put it back to try again and it worked this time. Until I went into the monitor settings and set it to auto. That made the screen go black and occasionaly flash the home screen.

So I've had enough. I will be looking for a new option for a useful SBC.
Reply
#5
Hi Fellow Tinkers,

We have been made aware that some tinkers are experiencing an HDMI issue with beta v1.9.
At this point in time, we are not able the replicate the issue with any of our monitors, and we have a lot! If anyone is experiencing this issue, please private message us more info and help us bring the firmware out of the beta phase as soon as possible.

Please include information such as:
l OS Version
l Description of the issue experienced
l Monitor model
l Logs (via SSH)
l Log via command “sudo cat /sys/kernel/debug/clk/clk_summary | grep -ie npll -ie vop0”
l Logs from /var/log/*
l If VGA or DVI dongle used and model
l Any photos or screenshots if possible

Thanks and keep tinkering!
Reply
#6
Well i got my tinker out, the "sd card destroyer", this time have used a 16gb kingston card, put 1.9 on it and i found it to be the best so far, i have not put ffmpeg on it this time(card died while converting 500 wmv's to mp4's) but have put a opensim, blender and mono, it will be on 24/7, this one loads a lot faster, have not had any of the "getting the screen size wrong" like before, i really like it, the card i have put in this one i know last more than a year in a raspberry pi, i have not had one of these cards blow yet, but run out of cheap 8gb cards that work fine on the PI, i have the GPIO working just switching a fan on and off, i have noticed that while logged as root that you have to use sudo to get i2cdetect working, also the fan pin would be better if it was pwm and not on/off, anyway i will over the next few days see if it survives and see if i can get i2c working, almost all my projects use the i2c bus and uses the GPIO as a interface, but there are new transceivers being made by the chip companies that will allow long range comms thus not needing the internet that the gpio can interface directly with, GAMMA-868 being an example with a 2km range in a built up area and buildings and a 16 km range in open air, my latest project "environment monitor for COPD sufferers" uses these to operate plant, at the moment Pi's do this job but i will see if the tinker can, gpio switching which it can do and i2c, UART(dont know yet) are needed.

But saying all that i do like 1.9. i get sudo i2cdetect report back to me that there are chips connected to the bus, so good so far, have not seen if i can use them like i can on the PI
Reply
#7
(07-13-2017, 02:24 PM)mcerveny Wrote: Hello.

I do some test with "new" TinkerOS 1.9 (beta) but ... Angry

- Modified kernel sources are now published with only ~25 commits (hundreds of rk3288 commits from rockchip-linux are not taken !) ?
- SPI does not work.
- GPIO pull-up/-down in python library does not work.
- HDMI DMT output modes does not work. It is even worse than previous release. Now instead of ignoring "unsupported" modes DRM driver sets totally invalid pixel clock (for modes >1024x768@60):

Code:
# xrandr --display :0
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 4096 x 4096
HDMI-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 380mm x 300mm
  1280x1024     60.02 +  75.02*
  1152x864      75.00  
  1024x768      75.08    70.07    60.00  
  832x624       74.55  
  800x600       72.19    75.00    60.32  
  640x480       75.00    72.81  
  720x400       70.08  


# ### FAILED:

# xrandr --display :0 --output HDMI-1 --mode 1280x1024 --refresh 75
# sudo grep dclk_vop0 /sys/kernel/debug/clk/clk_summary
         dclk_vop0                       2            3   105000000          0 0  
# ### [drm:drm_mode_debug_printmodeline] Modeline 73:"1280x1024" 75 135000 1280 1296 1440 1688 1024 1025 1028 1066 0x40 0x5
# ### NOT MATCH 105 Mhz != 135 Mhz
# xrandr --display :0 --output HDMI-1 --mode 1280x1024 --refresh 60
# sudo grep dclk_vop0 /sys/kernel/debug/clk/clk_summary
         dclk_vop0                       2            3    77142857          0 0  
# ###  [drm:drm_mode_debug_printmodeline] Modeline 67:"1280x1024" 60 108000 1280 1328 1440 1688 1024 1025 1028 1066 0x48 0x5
# ### NOT MATCH 77 Mhz != 108 Mhz
# xrandr --display :0 --output HDMI-1 --mode 1152x864 --refresh 75
# sudo grep dclk_vop0 /sys/kernel/debug/clk/clk_summary
         dclk_vop0                       2            3    77142857          0 0  
# ###  [drm:drm_mode_debug_printmodeline] Modeline 80:"1152x864" 75 108000 1152 1216 1344 1600 864 865 868 900 0x40 0x5
# ### NOT MATCH 77 Mhz != 108 Mhz
# xrandr --display :0 --output HDMI-1 --mode 1024x768 --refresh 75
# sudo grep dclk_vop0 /sys/kernel/debug/clk/clk_summary
         dclk_vop0                       2            3    56285714          0 0  
# ### [drm:drm_mode_debug_printmodeline] Modeline 74:"1024x768" 75 78800 1024 1040 1136 1312 768 769 772 800 0x40 0x5
# ### NOT MATCH 56 Mhz != 78 Mhz
# xrandr --display :0 --output HDMI-1 --mode 1024x768 --refresh 70
# sudo grep dclk_vop0 /sys/kernel/debug/clk/clk_summary
         dclk_vop0                       2            3    53571429          0 0  
# ### [drm:drm_mode_debug_printmodeline] Modeline 75:"1024x768" 70 75000 1024 1048 1184 1328 768 771 777 806 0x40 0xa
# ### NOT MATCH 53 Mhz != 75 Mhz
# xrandr --display :0 --output HDMI-1 --mode 1024x768 --refresh 75
# sudo grep dclk_vop0 /sys/kernel/debug/clk/clk_summary
         dclk_vop0                       2            3    56285714          0 0  
# ### [drm:drm_mode_debug_printmodeline] Modeline 75:"1024x768" 70 75000 1024 1048 1184 1328 768 771 777 806 0x40 0xa
# ### NOT MATCH 56 Mhz != 75 Mhz


# ### OK:

# xrandr --display :0 --output HDMI-1 --mode 1024x768 --refresh 60
# sudo grep dclk_vop0 /sys/kernel/debug/clk/clk_summary
         dclk_vop0                       2            3    65000000          0 0  
# ### [drm:drm_mode_debug_printmodeline] Modeline 76:"1024x768" 60 65000 1024 1048 1184 1344 768 771 777 806 0x40 0xa
# xrandr --display :0 --output HDMI-1 --mode 800x600 --refresh 75
# sudo grep dclk_vop0 /sys/kernel/debug/clk/clk_summary
         dclk_vop0                       2            3    49500000          0 0  
# ### [drm:drm_mode_debug_printmodeline] Modeline 78:"800x600" 75 49500 800 816 896 1056 600 601 604 625 0x40 0x5
# xrandr --display :0 --output HDMI-1 --mode 800x600 --refresh 72
# sudo grep dclk_vop0 /sys/kernel/debug/clk/clk_summary
         dclk_vop0                       2            3    50000000          0 0  
# ### [drm:drm_mode_debug_printmodeline] Modeline 79:"800x600" 72 50000 800 856 976 1040 600 637 643 666 0x40 0x5
# xrandr --display :0 --output HDMI-1 --mode 800x600 --refresh 60
# sudo grep dclk_vop0 /sys/kernel/debug/clk/clk_summary
         dclk_vop0                       2            3    40000000          0 0  
# ### [drm:drm_mode_debug_printmodeline] Modeline 68:"800x600" 60 40000 800 840 968 1056 600 601 605 628 0x40 0x5

My opinion: RockChip seems to stop support of old RK3288 chip and moving to newer like RK3328. My patience with "big" ASUS expired after 6 month with unusable linux betas, without solving bugs, without community support, without publishing full HW schema, with design fails in TinkerBoard (CEC, RESET), with "marketing" driven product management (for example - different timing of release over the world, feed $$$ to marketing presentation and spreading fog about 4K and accelerated video playback (reality)) and finally totally crappy use of MicroUSB as power source ! Conclusion - The product does not match my expectation. ASUS recently sent me a note that "ASUS have been improved internally" ... "ASUS been discussing this situation for a long time" ... but I am practically leaving this community and moving (with RockChip) to newer RK3328. Goodbye and Happy tinkering ! Martin


Big Grin It just Mpp's support status.

RK3288 is still one of the most important rockchip SOC and no other alternatives. We mainly develop linux stuffs in RK3288, it have the best support.
RK3399 have good performance but expensive.
RK3328/RK3229 are designed for TV Box, it have a weak GPU, few display interface and no isp.


Undecided They should rebase their kernel on rockchip 4.4 branch, otherwise they can't get many bug fixes and new featrues.
(e.g : videobuf2 + v4l2 isp driver, rga driver.....)
Undecided Also, i would suggest them to upgrade their xserver to 1.19, or the system will break when run "apt-get upgrade"
Reply
#8
Well my Asus VGA monitor no longer works with 1.9, worked perfectly on 1.8. I get an out of range message so I'm guessing it boots to 1900*1080 screen size?
Reply
#9
Hi,
I'm new in tinker os, I bought it two days ago.
i run actually 1.9b
i can't say anything about bug correction for now.

display on asus monitor 1920/1080 hdmi (no pb with that)
I've installed firefox ESR with vlc components and it work well (i don't know if accelerated gpu was used but) no lag, audio ok on 1080p video, processor run at -+25%

I use x11vncviewer to monitor the access point and file server raspi3 (x11vncserev) without any pb except a slowdown of the wifi that I do not understand yet (it was not with the 1.8)
With 1.8, when moving windows, a lot of spread appeared, but now 1.9 is correct. As for the keyboard mapping, as in 1.8, no way to change in French (with desktop tools) "to" to "... works well now.

And the strange scratched screen that sometimes appears after the launch of the Tinker board with 1.8 seems to have disappeared hope for a long ...

i will test BT certainely and kodi with curiosity. and trying to find why vncviewer is too slow with 1.9.
Reply
#10
I got an out of range message on my 1440 900 monitor, so I switched to a better monitor and it worked ok
The thread here https://tinkerboarding.co.uk/forum/thread-262.html , should explain how to add the missing monitor resolutions.

I am using a 2amp power supply with a thick micro usb cable, which works fine on all the other distros and android, so i dont think this is a problem .

I am getting black screens every now and again on v1.9 (same as i did on v1.8) when using chromium. Once after closing chromium, the desktop background was still showing half of an image of a youtube video i had been watching (as if the video drivers had messed up)
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)