Jump to content

Alex M

Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. Thank you so much, @tooz! I have a couple questions -- 1. Is there a specific repository or archive I can access that has these custom chromium x11 builds? 2. Is it possible to get chromium x11 versions 87 and 112?
  2. I've upgraded my device to the latest TinkerOS image (Debian-Bullseye-v3.0.20-20240527). Since then, I've been trying to re-setup my programs and environment. I have a python program that used Selenium and Chrome Driver to automatically launch the browser in in full screen to a specific URL, among other things. The issue I'm having is in the latest version of OS the device is running chromium x11 (v. 114.0.5735.198). For Chrome Driver to work, it must have the matching major version of Chromium (Chromium x11 is fine) installed. Unfortunately, I've been unable to find a Linux Debian (arm64) compatible version of chromium-driver (chromedriver) that works with this particular version of chromium x11. The latest chromedriver version that's supported for the architecture is v112. I urgently need to find a solution. My best guess is I have 3 options? 1.) Find a way to update the chromium x11 version to a newer version that has a matching and supported version of chromedriver. I haven't found a way to update the chromium x11 version 2.) Find a way to downgrade chromium x11 version. I haven't found a way to downgrade the chromium x11 version 3.) Replace chromium x11 with regular chromium. Last time I attempted this, the regular chromium version had issues with videos (ffmpeg) and would crash ("Aw Snap" screen). My understanding is chromium x11 is used because it's optimized for this board and architecture. If that's the case, it would be ideal to stick with chromium x11 to avoid potential performance issues. Ideally, I need advice on how to install specific versions of chromium x11. At this point, I'm desperate for any guidance, assistance, or thoughts on my situation. This python program and using selenium and chromedriver is critical.
  3. I have an ASUS Tinkerboard 2S, running TinkerOS Debian-Buster v2.0.4. I've come across an issue where if I plug in a USB 2.0 device, it will not work...but also kills all other USB device connections. The device I'm plugging in is: http://www.ikkegol.com/ikkegol-4-keys-usb-handle-keyboard-gaming-switch-pedal-p-62.html. Unfortunately, there is no real spec sheet for it, but I did run "USB Device Tree" on my Windows machine to try and pull additional information on the device. Effectively, it just emulates a USB keyboard. Numbers 1,2,3,4 correspond to A,B,C,D. It's an extremely basic device. I have not had any issues with it on other machines (Windows & Linux). I have also tested that this issue occurs across 3 different Tinkerboard 2S devices, so I know it's not board/hardware issue isolated to a single device. Looking at the log (/var/log/kern.log), I can see the lines shown below. My suspicion is the Tinkerboard is trying to exclusively use USB 3.0 drivers and is incorrectly identifying my device. Has anyone experienced this issue? Is it possible to force the use of USB 2.0? I attached some of the log, as well as info on my USB device. Oct 13 12:09:00 NPU-Display kernel: [ 156.921029] usb 5-1.1: new full-speed USB device number 5 using xhci-hcd Oct 13 12:09:00 NPU-Display kernel: [ 157.027584] usb 5-1.1: New USB device found, idVendor=413d, idProduct=2107 Oct 13 12:09:00 NPU-Display kernel: [ 157.034544] usb 5-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 13 12:09:00 NPU-Display kernel: [ 157.045637] usb 5-1.1: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes Oct 13 12:09:00 NPU-Display kernel: [ 157.054833] usb 5-1.1: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes Oct 13 12:09:00 NPU-Display kernel: [ 157.064858] usb 5-1.1: ep 0x2 - rounding interval to 64 microframes, ep desc says 80 microframes Oct 13 12:09:00 NPU-Display kernel: [ 157.106314] input: HID 413d:2107 as /devices/platform/usb1/fe900000.dwc3/xhci-hcd.11.auto/usb5/5-1/5-1.1/5-1.1:1.0/0003:413D:2107.0003/input/input6 Oct 13 12:09:00 NPU-Display kernel: [ 157.178021] hid-generic 0003:413D:2107.0003: input,hidraw2: USB HID v1.11 Keyboard [HID 413d:2107] on usb-xhci-hcd.11.auto-1.1/input0 Oct 13 12:09:10 NPU-Display kernel: [ 167.200962] xhci-hcd xhci-hcd.11.auto: xHCI host not responding to stop endpoint command. Oct 13 12:09:10 NPU-Display kernel: [ 167.209158] xhci-hcd xhci-hcd.11.auto: Assuming host is dying, halting host. Oct 13 12:09:10 NPU-Display kernel: [ 167.231429] xhci-hcd xhci-hcd.11.auto: HC died; cleaning up Oct 13 12:09:10 NPU-Display kernel: [ 167.237690] usb 5-1: USB disconnect, device number 2 Oct 13 12:09:10 NPU-Display kernel: [ 167.242882] usb 5-1.1: USB disconnect, device number 5 Oct 13 12:09:10 NPU-Display kernel: [ 167.248435] usb 6-1: USB disconnect, device number 2 Oct 13 12:09:10 NPU-Display kernel: [ 167.281162] usb 5-1.2: USB disconnect, device number 3 Oct 13 12:09:10 NPU-Display kernel: [ 167.337275] usb 5-1.3: USB disconnect, device number 4 4-button Remote USB info.txt
×
×
  • Create New...