Jump to content

Search the Community

Showing results for tags 'tinkerboard'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK 5B
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL







  1. Hi, I'll install OpenMediaVault and Nextcloud on a tinkerboard and I would like to know if there is any advantage on run system on SATA / USB in this case and if it is possible to do this on tinkerboard since it was not clear for me on the docs. Thank you
  2. My current setup is the tinkerboard powered by the raspberry pi universal adapter connected to ethernet and a external HDD(Maxtor M3) powered by the Tinkerboard's usb. I have used it very lightly in this configuration (ssh-ing into it and copying some files to the hdd) but from what I have gathered from the information available here this powering setup is inedequate and will lead to problems. So I want to follow the recommended method and power it through the GPIO pins. I am considering using this or this powersupply. (I realize 10A on the second one is overkill for the tinkerboard, but the price difference from the 3A rated one is minimal and I could find some other use for it in the future). Is any of this a reasonable choice? TonyMac32 warns not to exceed 5.5v but both list a voltage protection range higher than that. TonyMac32 also mentions using a zener diode and a capacitor to filter power and protect the board from overvoltage. While I have a basic understanding of electronics, I don't know how to make that circuit or the exact values of the components that I would need. Could someone elaborate on how to make this circuit and the difference it would make over plugging straight to the GPIO pins? Thank you
  3. probably a post bragging of my christmas gifts, but mostly just documentation because it really confused and stumbled me from the get go so, my setup was powering tinkerboard (the first revision, without the new fangled eMMCs) via GPIO because it confused the hell out of me how to power this beast. this was powered through the XL4015 buck converter 12.1/12.2 V on input, with ammeter and voltmeter included on the board. (the board was current limited to 5A, because why not? the rk808 is 6A tops) ok from the get go the board powers (not load tested, just power through and run kodi-gbm UI) from 3.4V to 6.2V. undervolting or overvolting it doesnt shuts itself down (no red light), then bringing back to operating voltages boots the board up also take not that operating voltages for RK808 was 2.7V to 5.5V. the missing 0.7V was probably the diode drop people are talking about. maybe? without a multimeter (only using the power supply's voltmeter-ammeter) i can't check it that much. but i'm fine that it has wide range of operating voltages. on all observed voltages, 3A seems to be the max current. it needs to be sustained though. also full load without peripherals (and HDMI, HDMI seems to be active than passive) is observed 2.3-2.5A. booting up the board needs about 0.7A to keep on going this would probably contradict as well the "increase voltage to 5.25 or smthing" given that no matter how many volts you put into it, it would only use 3A. weirdly (since this contradicts the block schematics from tinkerboard), #1 and #2 are observed in both USB and GPIO with no difference (significant or not) under load. it's weird since 3.1. if USB lines were protected, there should be a diode drop *only* on USB lines. but this was seen on GPIO as well. 3.2. some claims microUSB only has max 2.5A but this is not seen in this case: the setup sustained 2.7A going 2.9A. also, powering both GPIO and USB with the same power block doesnt seem to affect stability at all (still hard limits at 3A.) so with that, there are few suggestions for powering the board as well (and minor observations. opinionated parts ahead) people talking about overvolting or undervolting the power rails doesnt really help at all at slightest. it'll still top at 3A. what overvolting could help were powering via USB peripherals, but i wouldnt recommend it plugging straight given the fact that 2.5A on full load? you only have 0.5A to spare on heavy load. get a usb y splitter (tape over the USB power lines to the board. idk why but i have usb resets whenever i dont have them. then again plugging a hard drive in there shouldnt be happening in the first place) the raspberry pi 3B+ adaptor (5.25V, 2.5A)? good enough actually! as long as it can deliver 5V across the device, AND as long as you dont have power heavy devices on it. it doesnt matter that much so long as your USB cable can handle phone-charger level of amps. rk3288 was designed with mobile phones in mind. it'll always power at 3.7V. i always having issues when im using a cable that can only do 0.5A across it. no can do. probably for me, but this is why you dont need to be hung with the minor details. starting from this, im wracking my brain around if tinkerboard was sensitive to power drops (like 5.1v or 5.2v would show stability improvements) but nope! just chuck it right in, it'll be fine. just check your connections and stuff. powering through the GPIO pins is recommended of course, but it's an overkill. probably the reason for it was most USB chargers only go 2A max and that would underpower the tinkerboard, doing boot loops instead of starting correctly. then again YMMV: my place has 3A or 5A chargers everywhere. and with the introduction and interests of fast chargers, you'll find chargers (and cables) that can deliver more than you expect. on sidenote on powering through the GPIO: PLEASE GET YOUR GAUGES RIGHT. i powered it via the ATX FDD (remember those?) connector, with 12V pin removed. it turns out for some reason its max current is 1A and its just thin flimsy as hell. get a thicker wire. it didnt drop the current (thankfully) but the wire became so warm to touch, it's weird. i wouldnt wanna run this on full load. at least i didnt get burned wires. cooling fan helps a lot also you cant bypass that 3A limit. that's 3A total, both GPIO and USB inputs. even powering both USB and GPIO (like that one person suggested) doesnt really do anything. you wouldnt get that much power in, but at least you can protect your wires? which is weird since block schematics shows GPIO and USB has different lines? so it should have different protections and stuff. a multimeter can help see if those inputs are shorted (GPIO vs microUSB vs peripherals) but i dont have one at the moment i would also like to measure the voltage across the peripherals if any load situations will lead to undervolting the outputs, but i dont have a USB tester at the moment. RK808 seems to be programmable but interfacing with it is outside of my skill set. any help would do i hope this post helps everyone well. no one uses these boards anymore except for niche use cases but i still enjoy it. i hope in the future i can get myself a huge NAS server with an RK3588S on it. kinda lonely to be honest
  4. i'm stuck with this since day 1 but now i upgraded to armbian (with kodi-gbm) i had this problem worse stress testing the board with stress -c 4 doesn't bring the board into shutdown, but logging in to kodi-gbm or using graphical interface? it brings instability all of a sudden. there's no inherent pattern from the shudowns except when i launch kodi or access some files (emby transcoding doesn't cause any instability). anything outside the text mode should cause it to shutdown. weirdly enough, when i removed the USB peripherals (2xUSB HDD, own power supply for both cases) the instability worsens and doesn't boot or sometimes reboot cycle after fsck.ext4 on startup. this board was powered by an ATX PSU (using the FDD connector). measured 5.1V across it. is there a possibility i tripped some overcurrent protection or something? any suggestions how to fix it? can i actually power it using a separate usb 5v/3a connector as stated here? https://github.com/berinc/Asus-Tinker-Board i don't have any troubleshooting tools at the moment. i don't have a usb tester or a multimeter (leads broke.) thanks for your help.
  5. hi , i installed Armbian 22.11 Jammy minimal image for headless console only usage. uname -a Linux tinkerboard 5.15.80-rockchip #22.11.1 SMP PREEMPT Wed Nov 30 11:05:19 UTC 2022 armv7l armv7l armv7l GNU/Linux i installed teamviewer and if device rebooted with hdmi connected, i am able to use teamviewer and teamviewer shows shell output but when rebooted without hdmi cable connected, teamviewer seems working on device , but cant connect it.. here is teamviewer info TeamViewer 15.37.3 (DEB) TeamViewer ID: 1374960804 teamviewerd status ● teamviewerd.service - TeamViewer remote control daemon Loaded: loaded (/etc/systemd/system/teamviewerd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2022-12-23 13:40:52 +03; 6min ago Process: 1659 ExecStart=/opt/teamviewer/tv_bin/teamviewerd -d (code=exited, status=0/SUCCESS) Main PID: 1758 (teamviewerd) Tasks: 18 (limit: 4734) Memory: 13.3M CPU: 6.351s CGroup: /system.slice/teamviewerd.service └─1758 /opt/teamviewer/tv_bin/teamviewerd -d Dec 23 13:40:47 tinkerboard systemd[1]: Starting TeamViewer remote control daemon... Dec 23 13:40:52 tinkerboard systemd[1]: teamviewerd.service: Can't open PID file /run/teamviewerd.pid (yet?) after start: Operation not permitted Dec 23 13:40:52 tinkerboard systemd[1]: Started TeamViewer remote control daemon. so what i tried on armbianEnv.txt with several combinations (even one by one and with different combinations) setenv video-mode sunxi:640x480-24@60,monitor=dvi,hpd=0,edid=0 setenv videoconfig "drm_kms_helper.edid_firmware=edid/1024x768.bin" setenv HPD "false" setenv vout "dvi" saveenv and recompiled boot.cmd with: sudo mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr still cant connect teamviewer without hdmi cable.. so what am i missing? or how to do it properly on tinkerboard with armbian? ps: it was easy on raspberrypi , just change resolution in raspi-config and save.. teamviewer started to work.. thanks..
  6. Good evening, last week they changed the electric meter in my building, but in order to do so they cut the power, and my Tinkerboard (the first model, the one issued back in 2017, Asus first's SBC), that I use as my "Save for later, and never look at it again" network folder, suffered. It continued to reboot from some kernel panic, which I forgot to take note; but since it hadn't been upgraded to jammy, I took the opportunity to do it. Pluging in the uSD card (with the newly released jammy version, just downloaded here), power, and all (including the ethernet cord!!), first boot I have to create my user (which, for some reasons refuses to let me put my usual fr3d tag, obliging me to go with the common "fred", but OK ), then all the trivial steps to set my locale settings. Then the beautiful armbian desktop penguin greats me. Nice now some more little custumisations and I'm ready to go, or so I thought; the wireless connection doesn't work, it fails to connect (and it is only 2m away from my router), it continues to ask me for the password, which has was not changed in the meantime. I tried nmtui But nothing change, well I only got the funny message I also tried to fix it by looking into armbian-config but nothing, after the third time, I get the same message about "secrets" not being given. I also tried installing "non-free" package, hoping it would find missing piece of software/firmware/driver to solve my issue, but as you can immagine it doesn't. And I also found out the "browser" can't be opened, as it gives me some kind of Input/output errors, yet if I scroll down to the internet program section, I can open firefox, and it seems (only used it for 1h, more or less) to be working properly. Would some good soul help me find a solution?? As soon as I'm able to send some screenshots i'll do it. Thanks in advance, fr3d
  7. Keep getting the error below when trying to run docker containers. I have a first gen Tinkerboard with Armbian on a SSD. Seen some post's about some error with cgroups v2, and using kernels below 5.x sudo docker run -d --name hello hello-world b22653867370a24ab900fc077f50fc6b05bb6eb986906caee88250fc9e9f5433 docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting cgroup config for procHooks process: bpf_prog_query(BPF_CGROUP_DEVICE) failed: function not implemented: unknown. docker --version Docker version 20.10.21, build baeda1f uname -a Linux tinkerboard 5.15.74-rockchip #22.08.6 SMP PREEMPT Tue Oct 18 06:40:37 UTC 2022 armv7l armv7l armv7l GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy
  8. Hello, I'm trying to setup a hotspot on a tinkerboard S running bullseye. Following the procedure from https://docs.armbian.com/User-Guide_Advanced-Features/ at the point where it requires: 2. Copy /etc/network/interfaces.hostapd to /etc/network/interfaces i realize the file interfaces.hostapd is missing, even though hostapd is installed hostapd is already the newest version (3:2.10-6~armbian22.02.3+1) I manually created the file with the following content even though I'm not sure if that's correct (as referred in one post on the forum): auto lo br0 iface lo inet loopback allow-hotplug eth0 iface eth0 inet manual allow-hotplug wlan0 iface wlan0 inet manual iface br0 inet dhcp bridge_ports eth0 wlan0 /etc/network/interfaces.hostapd remains in there without issues, but at the moment of copying its info to /etc/network/interfaces and rebooting, the SBC won't let me log in through ssh. In order to do so i have to comment the added lines to gain back access. Any pointers on how can i finish the process to create the hotspot? Thanks.
  9. Hi. I'm running Armbian 22.05.3 Focal with Linux 5.10.60-rockchip on an Asus Tinker board. Can someone tell me how to enable SPI? I've seen instructions that say you should be able to run armbian-config and go to System > Hardware > spi-spidev, however the Hardware menu does not exist for me.
  10. So I have downloaded several versions of Armbian for Tinkerboard using BullsEye and Yammy. Not one creates a working Access Point. The Bullseye version ends with a message that the hotspot has been activated but nothing appears. The yammy version fails with a message there is no usable driver for hostapd. It appears there are a lot of issues with this function. Why not leave it out or document which boards the feature doesn't support. It would save a lot of time going down rabbit holes.
  11. Hi, I have installed "Armbian_22.08.7_Tinkerboard_bullseye_current_5.15.74_minimal.img.xz" on a Tinkerboard (no S, with RK3288). I have tried to set the output of some header pins without success. I used both "sysfs" and "gpiod" (which uses char-devices). Test procedure, e.g. for pin 36 (gpio223): # echo "223" > /sys/class/gpio/export # cat /sys/class/gpio/gpio223/direction in # cat /sys/class/gpio/gpio223/value 0 # echo "out" > /sys/class/gpio/gpio223/direction # cat /sys/class/gpio/gpio223/direction out # echo "1" > /sys/class/gpio/gpio223/value # cat /sys/class/gpio/gpio223/value 0 # echo "0" > /sys/class/gpio/gpio223/value # cat /sys/class/gpio/gpio223/value 0 The example is for the pin36 is grounded by an resistor with 1kOhm. If the resistor is switched to 3.3V all read values are go to "1". The read values match the measured voltage (~0V for "0", ~3.3.V for "1"). The same behaviour for "gpioset 7 7=0". After this, the "gpioinfo 7" lists the line as output, like expected. Only the voltage remain unchanged (gpioget will change the line to input). With TinkerOS the same test is working (with sysfs only, because old Kernel 4.4.). Afterwards I have also tested some (or all) different options, like "sudo gpioset -m wait -D push-pull -B pull-down gpiochip7 7=0". But no success. Have I something missed to set up in the device tree? I have enabled i2c1 & i2c4 and disabled all other features (uart, spi and w1-gpio etc.) by usage of armbian-config. Thanks for your help in advance
  12. Hallo, Ich habe noch ein Tinkerboard rumfliegen, welches für Office-Anwendungen reichen sollte. Ich suche jetzt schon seit einiger Zeit ein OS dafür, bisher habe ich leider aber noch nichts derartiges gefunden. Vielleicht kennt ja jemand ein entsprechendes Image oder hat Tips wie ich es selbst erstellen könnte Ich bin allerdings bestenfalls Beginner mt Debian- Schon mal vielen Dank
  13. Hello, I am new to this forum and struggling with some stuff on the Tinkerboard S R2.0. I use the CLI-version of Armbian Jammy of 23 october 2022. I have to activate several features. I think two of them might relate to 'missing firmware'. 1. Activating a AccessPoint: during the installation of raspAP I get a set of error on 'missing firmware'. 2. Installing a modem: not a single USB-device gets recognized by lsusb. I am stuck at the very beginning. lsusb is working on the xfce but we want a leaner system. I tried the latest TinkerOS but I require a more updated version of python (3.10) and I also would like to stick to Ubuntu. Can anybody guide me to a firmware upgrade for tinkerboard S R2.0? How do I activate the USB support? Thanks, Luc
  14. Hello I cannot enable the Bluetooth on Tinkerboard device. Tried latest image, fresh install. I've opened the question on StackOverflow: https://superuser.com/questions/1698728/cannot-enable-bluetooth-on-tinkerboard-armbian It contains technical details. The latest what I've found so far is it could be related to Kernel compilation flags: # Extract from the /boot/config-5.10.60-rockchip CONFIG_SERIAL_DEV_BUS=y CONFIG_BT_HCIUART_3WIRE=y CONFIG_BT_HCIUART_SERDEV=y # CONFIG_BT_HCIUART_RTL - is not set # CONFIG_SERIAL_DEV_CTRL_TTYPORT - is not set I tried to download and compile the kernel and stuck. Basically I do not know where to find the kernel used to build the image. And most of all I'm not 100% sure I have to recompile the kernel. I do not believe nobody tested the Bluetooth before. Most probably it is configuration issue. Please assist
  15. Hi all, I have Armbian 22.08.6 Jammy with Linux 5.15.74-rockchip with Desktop running on an "Asus Tinker Board Rev. 1.2". My Problem is that I get no stable HDMI Connection. Picture is appearing and disappearing every few seconds. Changing Cable, Monitors, Resolution and Refreshrate doesn’t change the problem. After Research in the forum I saw that I should provide „armbianmonitor -u“ here: https://paste.armbian.com/oriqiwilah I would be able to compile a custom image, but I don‘t know where to start bugfixing because I am no HDMI Expert. Maybe it has something to do with a Sync-Problem like described here: https://forum.armbian.com/topic/7342-terminal-video-corruptionsync-problem-tinker-board/?do=findComment&comment=56099 Thank you for help! PS: I posted this question accidentally in the wrong language before and tried to contact the moderators, but I am not allowed to post new question or reach them with the private message feature. So I post this here as a new user! Thanks!
  16. Hallo! Habe Armbian 22.08.6 Jammy with Linux 5.15.74-rockchip mit Desktop auf "Asus Tinker Board Rev. 1.2" laufen, aber leider bekomme ich per HDMI keine stabile Verbindung. HDMI Kabel bereits getauscht (geht mit anderen Geräten einwandfrei) auch Montor getauscht (geht mit anderen Geräten auch einwandfrei). Auflösungen und Framerates habe ich durchprobiert - fehlerbild aber immer das gleiche; Bild bleibt bestenfalls ein paar sekunden ein, dann geht es wieder aus für ein paar Sekunden und das setzt sich fort. Hab ein bisschen hier im Forum recheriert und sehe das man ein "armbianmonitor -u" ausführen soll und im Forum posten: https://paste.armbian.com/oriqiwilah Ich bin grundsätzlich in der Lage ein neues Image zu kompilieren aber ich bin noch unsicher wo ich anfangen soll den Fehler zu suchen. Hier ein Forumbeitrag über ein Sync Problem - weiß nicht ob das mit dem zu tun hat. Vielen Dank!
  17. Hi everyone I Install the latest version of Armbian Debian for the TinkerBoard S but at the beginning I have the problem of seeing that the image is always distorted, it is similar to having interference, it had not happened before with other operating systems. It also sometimes turns off meaninglessly or the mouse stops working.
  18. IT'S FINALLY HERE... THE OFFICIAL ROCKCHIP-LEGACY MULTIMEDIA INTEGRATION After two years of using a separate script to enable the multimedia features in RK3288/3328 Legacy Kernel, the whole framework has been incorporated to the official Armbian packaging system. The choice distro for this integration is Debian Buster (see FAQ at the end of this post about the reasons). I. Installation Download a Armbian Buster Legacy Desktop image for your board, and install it with the standard Armbian method. Install the complete multimedia solution with sudo apt update && sudo apt upgrade sudo apt install media-buster-legacy-tinkerboard --install-recommends ## Or ## sudo apt install media-buster-legacy-rk3328 --install-recommends The switch "--install-recommends" will add the whole Kodi binary addons collection (retro-gaming cores, music visualizations, screensavers, additional media decoders/encoders, vfs, etc.), plus the GLES-to-OpenGL wrapper "gl4es". II. Features Accelerated GLES/EGL X desktop: No action needed. Accelerated Chromium, with WebGL and video display acceleration: No action needed Desktop video player capable of smooth 4K HEVC-HDR: Use the "Rockchip Gst Player" from the Multimedia menu, or choose it with right-click on the media file. Command-line 4K playing is also possible with "gst-play-1.0 --videosink=kmssink". RKMPP-accelerated MPV: Use normally for standard operation (windowed with mouse-operated GUI). For fullscreen, keyboard-operated mode, use the command line switch "--gpu-context=drm" (this will allow you to play smooth 4K). - See instructions below, in the next post, for playing Youtube videos up to 4k with this MPV. ISP Camera with real-time h.264/1080p HW encoding (RK3288 only): Using the Gstreamer Plugin. Check this wiki for instructions on how to use it. Most of it applies to Armbian, except for the selection of ov5647/imx219 camera, which must be done using DT overlays. OpenCL 1.2 support (RK3288 only): It will be fully functional, no further action needed. You can download some tests and examples from this link. Kodi 18.9 Leia with full RKMPP+GBM acceleration, 4K-HDR capable: You can start it from Light DM menu as your user account: Alternatively, you can also run it as a system service with these command lines: sudo systemctl disable lightdm sudo systemctl enable kodi-gbm sudo reboot Full collection of Kodi binary add-ons: Includes retrogaming cores, media encoders and decoders, PVR, screensavers, vfs and audio visualizations. They are all installed with the package "kodi-addons-full", but are disabled by default. They need to be enabled individually within the Kodi GUI. OpenGL 2.1 support through the gl4es wrapper: It is installed with the package "gl4es", with no further action needed. III. Sources This is the list of the sources used for the packages: IV. FAQ ¿Why did you use Debian Buster as a base for this implementation? It was the most appropriate for several reasons. Upstream Rockchip-Linux developers use Debian buster, so the software could be ported with less modifications than if we chose a different distro. Besides, it is a completely stable distro, unlike Bullseye, which is a moving target as of today. It also has Chromium as a package, unlike Focal that uses snap instead. For last, it has a good backports repo, with several libs that would otherwise need to be compiled and maintained if we chose, for example, Focal. ¿Why Legacy instead of Mainline? This is an implementation based on the vendor's BSP kernel. It has been tested and is reliable, which many people will prefer rather than having a bleeding-edge, less stable implementation. In addition to that, Mainline upstream multimedia support is still a WIP, and lacks many features that are only present on Legacy kernels. ¿Will you add new features to this implementation? No, this implementation will only receive bug fixes if necessary. From now on, all multimedia work will be focused on Mainline and recent distros (like Focal or Bullseye). All new features will go there.
  19. Hello, I have set kernel.panic=180 in /etc/sysctl.conf to reboot on a kernel panic. Before, the system would keep running/hanging and I could read the errors if I turned on a attached display. Now the result is that the tinkerboard switches off. My expected result would be a reboot. Do I have to set something else? Or do I need to use watchdog? I am using the original tinkerboard with debian bullseye, kernel 5.15.48-rockchip.
  20. I have a question or at last 2. 1.Where to connect outside diode to thinkerboard . 2.How to turn off/on it from command line.
  21. I've been (trying) to move the Tinker and MiQi u-boots to 2020.07, however if I use any of the following: A MiQi, A Tinker S an image for a Tinker S an image for a Tinker on a Tinker S I get stuck in the initramfs busybox with it telling me the filesystem is toast. The only 2020.07 combo I've gotten to boot is the Tinker with the non-eMMC supporting u-boot. As for clues, I haven't found any, the u-boot source code is of course very well organized for debugging purposes :lol:. If anyone has an idea about what could be going on with this let me know, I'm shelving the effort to think about other stuff.
  22. Hi, i want to connect a MCP 2515 (the small modules for arduino) to my tinkerboard "Armbian 22.02.1 Hirsute with bleeding edge Linux 5.17.5-rockchip" I have enabled the SPI0 (and UART1) directly from armbian-config, I have disabled all the other peripherals. The connections are these: INT -------------> pin 32 CLK -------------> pin 11 SI ----------------> pin 13 SO --------------> pin 15 CS --------------> pin 29 in : /boot/armbianEnv.txt i add this: user_overlays=spi-mcp251x but it don't work and i can't find a guide for this board thanks a lot for your help
  23. Hi! I've got a problem getting USB devices to work with Armbian 22.02.1 (Tinkerboard_bullseye_current_5.15.25) - fresh install, bare image without any modifications. While a simple usb keyboard would more or less work, plugging some devices seems to crash the built-in USB hub. This happens in "cold"-plug as in "hot"-plug, whereas there are slight differences. Booting up without any USB device attached: lsusb Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0bda:49f6 Realtek Semiconductor Corp. USB Audio Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub After hot-plugging in any USB device the Genesis USB Hub has disappeared: lsusb Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0bda:49f6 Realtek Semiconductor Corp. USB Audio Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg has these two entries: [ 131.740593] usb 1-1: USB disconnect, device number 2 [ 134.624629] usb usb1-port1: connect-debounce failed So far what I tried to find out a little more: USB Card Readers and Datasticks work if "cold" plugged (=before power on), but crash on hotplug. USB Card Readers crash if hotplugged or "cold" plugged, removed and re-attached. USB stays crashed if the system reboots without a power off in between. Always! Huawei Surfsticks that do a modeswitch (e.g. USB_MODESWITCH etc. to get from storage- to network-mode) crash the system. Maybe modeswitch triggers the same problem as hotplug? I tried Tinkerboard R2.0 and S R2.0 - and serveral of each from my collection. Same problem with every board. Does anyone have more information on or suggestions how to analyse these issues? I read hotplug was in issue in 2018, does this remain?
  24. Hallo, ich habe ein Tinkerboard S und habe per SD Karte Armbian installiert. Dann per ssh root@ip-adresse . Bei der Passowort 1234 eingegeben. Aber das passwort wird nicht anerkannt. Gibt es inzwischen ein neues Passwort? Gruß Eberhard61 Translation: Hello, I have a Tinkerboard S and installed Armbian via SD card. Then via ssh root@ip-address . Entered the password 1234. But the password is not recognized. Is there a new password now? greeting Eberhard61
  25. In Alsamixer its missing the master volume. In older legacy images it was there and driver seemed to be a tinker rockchip driver? Any idea how to enable the master volume slider? If I increase volume in USB sound card (headphones) then no sound comes out at HDMI and only way to restore is to purge deb of pulseaudio and alsa and re-install. There are some errors also the moment i log into cli if I do above. If reproduced ill post here (update). Similar error posted on another topic/board If i test `aplay /usr/share/sounds/alsa/Front_Center.wav` its ok. After any change to alsamixer nothing comes out The errors that started after changing alsamixer volume as per above are:
  • Create New...