I have Beelink GT1 Mini w/Latest firmware build: 004P0, runs Android 9
CoreELEC-Amlogic-ng.arm-9.2.1-Generic S905X2.img.gz and I’m using the correct image for this unit but the USBv2 port does not function, or at least testing USB devices don’t work.
Any suggestions? Fixes? Thanks in advanced.
Have dmesg logs of USB activity under both Android and CoreELEC.
CoreELEC
CoreELEC (official): 9.2.1 (Amlogic-ng.arm)
CoreELEC:~ # dmesg | grep -i usb
[ 0.457334@1] usbcore: registered new interface driver usbfs
[ 0.457391@1] usbcore: registered new interface driver hub
[ 0.457482@1] usbcore: registered new device driver usb
[ 0.604258@2] ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
[ 0.604285@2] ohci_hcd: USB 1.1 ‘Open’ Host Controller (OHCI) Driver
[ 0.604716@2] usbcore: registered new interface driver cdc_acm
[ 0.604735@2] cdc_acm: USB Abstract Control Model driver for USB modems and I SDN adapters
[ 0.604827@2] usbcore: registered new interface driver usb-storage
[ 0.604947@2] usbcore: registered new interface driver usbserial
[ 0.605008@2] usbcore: registered new interface driver usbserial_generic
[ 0.605068@2] usbserial: USB Serial support registered for generic
[ 0.608755@3] usbcore: registered new interface driver usbhid
[ 0.608775@3] usbhid: USB HID core driver
[ 2.829634@3] amlogic-new-usb2-v2 ffe09000.usb2phy: USB2 phy probe:phy_mem:0x ffe09000, iomap phy_base:0xffffff80083fa000
[ 2.839674@3] amlogic-new-usb3-v2 ffe09080.usb3phy: USB3 phy probe:phy_mem:0x ffe09080, iomap phy_base:0xffffff80083fe080
[ 4.981821@2] usbcore: registered new interface driver snd-usb-audio
[ 5.549897@2] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
[ 5.557705@2] usb: xhci: determined sg_tablesize: 4294967295
[ 5.578164@2] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 5.584994@2] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumbe r=1
[ 5.592363@2] usb usb1: Product: xHCI Host Controller
[ 5.597386@2] usb usb1: Manufacturer: Linux 4.9.190 xhci-hcd
[ 5.603024@2] usb usb1: SerialNumber: xhci-hcd.0.auto
[ 5.608447@2] hub 1-0:1.0: USB hub found
[ 5.621748@2] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
[ 5.629550@2] usb: xhci: determined sg_tablesize: 4294967295
[ 5.635032@2] usb usb2: We don’t know the algorithms for LPM for this host, d isabling LPM.
[ 5.643303@2] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[ 5.650169@2] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumbe r=1
[ 5.657536@2] usb usb2: Product: xHCI Host Controller
[ 5.662560@2] usb usb2: Manufacturer: Linux 4.9.190 xhci-hcd
[ 5.668197@2] usb usb2: SerialNumber: xhci-hcd.0.auto
[ 5.673723@2] hub 2-0:1.0: USB hub found
[ 5.689525@2] dwc_otg: usb0: type: 2 speed: 0, config: 0, dma: 0, id: 0, phy: ffe09000, ctrl: 0
[ 5.946546@2] usb 1-1: new full-speed USB device number 2 using xhci-hcd
[ 6.090404@2] usb 1-1: config 1 has an invalid interface number: 4 but max is 3
[ 6.090411@2] usb 1-1: config 1 has no interface number 2
[ 6.092971@2] usb 1-1: New USB device found, idVendor=248a, idProduct=871f
[ 6.092976@2] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber =3
[ 6.092978@2] usb 1-1: Product: 2.4G Wireless Air Mouse
[ 6.092981@2] usb 1-1: Manufacturer: www.videocon.com
[ 6.092983@2] usb 1-1: SerialNumber: Belon SmartMouse
[ 6.123665@2] input: www.videocon.com 2.4G Wireless Air Mouse as /devices/pla tform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1:1.3/0003:248A:871F.0001/input/i nput2
[ 6.183008@2] hid-generic 0003:248A:871F.0001: input,hiddev0,hidraw0: USB HID v1.01 Keyboard [www.videocon.com 2.4G Wireless Air Mouse] on usb-xhci-hcd.0.aut o-1/input3
[ 6.186727@2] input: www.videocon.com 2.4G Wireless Air Mouse as /devices/pla tform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1:1.4/0003:248A:871F.0002/input/i nput3
[ 6.187141@2] hid-generic 0003:248A:871F.0002: input,hidraw1: USB HID v1.01 M ouse [www.videocon.com 2.4G Wireless Air Mouse] on usb-xhci-hcd.0.auto-1/input4
CoreELEC:~ #
Under Android Pie
[ 0.563560] usbcore: registered new interface driver usbfs
[ 0.563626] usbcore: registered new interface driver hub
[ 0.563727] usbcore: registered new device driver usb
[ 0.733067] usbcore: registered new interface driver asix
[ 0.733165] usbcore: registered new interface driver ax88179_178a
[ 0.733222] usbcore: registered new interface driver cdc_ether
[ 0.733279] usbcore: registered new interface driver net1080
[ 0.733334] usbcore: registered new interface driver cdc_subset
[ 0.733393] usbcore: registered new interface driver zaurus
[ 0.733479] usbcore: registered new interface driver cdc_ncm
[ 0.734030] ehci_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver
[ 0.734101] ohci_hcd: USB 1.1 ‘Open’ Host Controller (OHCI) Driver
[ 0.734697] usbcore: registered new interface driver cdc_acm
[ 0.734744] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 0.734823] usbcore: registered new interface driver usb-storage
[ 0.734933] usbcore: registered new interface driver usbserial
[ 0.735548] usbcore: registered new interface driver xpad
[ 0.736107] usbcore: registered new interface driver uvcvideo
[ 0.736114] USB Video Class driver (1.1.1)
[ 0.736176] usbcore: registered new interface driver cx231xx
[ 0.742871] usbcore: registered new interface driver usbhid
[ 0.742888] usbhid: USB HID core driver
[ 3.143696] amlogic-new-usb2-v2 ffe09000.usb2phy: USB2 phy probe:phy_mem:0xffe09000, iomap phy_base:0xe06d2000
[ 3.152990] amlogic-new-usb3-v2 ffe09080.usb3phy: USB3 phy probe:phy_mem:0xffe09080, iomap phy_base:0xe06dd080
[ 3.669399] usbcore: registered new interface driver snd-usb-audio
[ 3.974357] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
[ 3.975484] hub 1-0:1.0: USB hub found
[ 3.975877] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
[ 3.975932] usb usb2: We don’t know the algorithms for LPM for this host, disabling LPM.
[ 3.976455] hub 2-0:1.0: USB hub found
[ 3.981147] dwc_otg: usb0: type: 2 speed: 0, config: 0, dma: 0, id: 0, phy: ffe09000, ctrl: 0
[ 4.310739] usb 1-1: new full-speed USB device number 2 using xhci-hcd
[ 4.462775] usb 1-1: config 1 has an invalid interface number: 4 but max is 3
[ 4.462779] usb 1-1: config 1 has no interface number 2
[ 4.496595] input: www.videocon.com 2.4G Wireless Air Mouse as /devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1:1.3/0003:248A:871F.0001/input/input2
[ 4.551207] hid-generic 0003:248A:871F.0001: input,hiddev0,hidraw0: USB HID v1.01 Keyboard [www.videocon.com 2.4G Wireless Air Mouse] on usb-xhci-hcd.0.auto-1/input3
[ 4.555845] input: www.videocon.com 2.4G Wireless Air Mouse as /devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1:1.4/0003:248A:871F.0002/input/input3
[ 4.556202] hid-generic 0003:248A:871F.0002: input,hidraw1: USB HID v1.01 Mouse [www.videocon.com 2.4G Wireless Air Mouse] on usb-xhci-hcd.0.auto-1/input4
[ 4.822733] usb 1-2: new low-speed USB device number 3 using xhci-hcd
[ 4.980303] input: HID 6901:1224 as /devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-2/1-2:1.0/0003:6901:1224.0003/input/input4
[ 5.043351] hid-generic 0003:6901:1224.0003: input,hidraw2: USB HID v1.10 Keyboard [HID 6901:1224] on usb-xhci-hcd.0.auto-2/input0
[ 5.050593] input: HID 6901:1224 as /devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-2/1-2:1.1/0003:6901:1224.0004/input/input5
[ 5.111152] hid-generic 0003:6901:1224.0004: input,hidraw3: USB HID v1.10 Mouse [HID 6901:1224] on usb-xhci-hcd.0.auto-2/input1
[ 19.841763] aml_wifi wifi: [usb_power_control] Set WiFi power down
[ 20.085532] aml_wifi wifi: [usb_power_control] Set WiFi power on !
[ 20.413732] aml_wifi wifi: [usb_power_control] Set WiFi power on !
#
I know this port that isn’t working under CoreELEC is the USB-OTG (USBv2) port for the Beelink GT1 Mini. Having done some researching, It seems CoreELEC is specifying OTG mode so It works ONLY as gadget instead of a working USB port for devices like Mouse, Keyboard and storage devices.
… In hopes there’s means for the enduser to tweak and change it’s mode. No need for OTG mode under CoreELEC.
It works fine in the nightly builds.
Hi TheCoolest. Cool! I’ll go test it out and report back. Thanks 
I’ve tested, and unfortunately…, no it doesn’t for this Beelink GT1 Mini 4GB+64GB.
I have a GTmini-A, which is the same device, and it works fine here.
Two different units. I have the original GT1 Mini… GT1 Mini-A is something newer
All S905X2 devices share the same DTB, I highly doubt that the only one that stands out is the GT1 Mini.
It has the same hardware and configuration as the GTmini-A.
CPU, GPU, Video Playback, Connectivity, USB, Power Supply, Dimensions and Weight all exactly the same.
Memory, the original also shipped w/2GB of RAM.
Storage, the original also shipped w/16GB of RAM.
Video & Audio Output almost reads exactly the same except for the original only w/HDMI 2.0a and the Mini-A shipped with HDMI 2.1
Like you say it uses the same dtb file, so it’s very strange.
Post time 2019-05-10 17:14:36
http://www.bee-link.com/forum.php/forum.php?mod=redirect&goto=findpost&ptid=44799&pid=63592
Figured it out thanks to you ( TheCoolest )!
The issue with GT1 Mini is the USBv3 port isn’t the blue colour-coded port for quick identification, that’s next to the Micro-SD / TF reader. It’s actually the black colour-coded port that’s actually the USB-v3 port.
There need to be a specific DTB for GT1 Mini, because the parameters used for calling needs to be reversed.
How do you know that? And how does this solve “not working usb”?
And how is anyone at CE team able to get the Android DTB from your box ?
Unless you extract it and upload it to compare.
Well considering the black coloured USB-port is NOT suppose to be USBv3 port… Take various official Beelink flashing tutorials I’ve seen thus far, the USB-OTG port for flashing is always over the black coloured USBv2 port.
Remember I only had one working USB port, it’s the blue coloured and that suppose to be an USBv3 port. It’s the only functional USB port under CoreELEC.
Then one simple ssh command…, well I’ve used two, that clearly speaks volumes.
At this time I can only use it as a charging port. Hard to believe that this can’t be corrected, considering GT1 Mini-A uses the same dtb image and works fine.
I don’t have GT1 Mini-A, just the original GT1 Mini, but I bet the USB ports are likely properly coloured on that other one. At this time I only can use the USBv2, when I should be using also USBv3.
CoreELEC (official): nightly_20200116 (Amlogic-ng.arm)
CoreELEC:~ # dmesg | grep xhc
[ 4.716572@3] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[ 4.719544@3] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
[ 4.727796@3] xhci-hcd xhci-hcd.0.auto: hcc params 0x0228fe6c hci version 0x110 quirks 0x20010010
[ 4.736206@3] xhci-hcd xhci-hcd.0.auto: irq 14, io mem 0xff500000
[ 4.761563@3] usb usb1: Manufacturer: Linux 4.9.113 xhci-hcd
[ 4.767199@3] usb usb1: SerialNumber: xhci-hcd.0.auto
[ 4.780520@3] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[ 4.785924@3] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
[ 4.821277@3] usb usb2: Manufacturer: Linux 4.9.113 xhci-hcd
[ 4.826912@3] usb usb2: SerialNumber: xhci-hcd.0.auto
[ 5.111346@3] usb 1-1: new low-speed USB device number 2 using xhci-hcd
[ 5.262024@3] input: HID 6901:1224 as /devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1:1.0/0003:6901:1224.0001/input/input1
[ 5.319887@3] hid-generic 0003:6901:1224.0001: input,hidraw0: USB HID v1.10 Keyboard [HID 6901:1224] on usb-xhci-hcd.0.auto-1/input0
[ 5.326225@3] input: HID 6901:1224 as /devices/platform/ff500000.dwc3/xhci-hcd.0.auto/usb1/1-1/1-1:1.1/0003:6901:1224.0002/input/input2
[ 5.384283@3] hid-generic 0003:6901:1224.0002: input,hidraw1: USB HID v1.10 Mouse [HID 6901:1224] on usb-xhci-hcd.0.auto-1/input1
CoreELEC:~ # lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 6901:1224
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
CoreELEC:~ #Here’s what we know…;
Two ports are both functional under Android, however under CoreELEC latest…, only USB that’s functional is the USB version 2 which is incorrectly colour-coded as the blue port on this here GT1 Mini box.
USB version 3 is recognized in CoreELEC but different types of drives and other types of USB devices does not work. However It can be used as a charging port, during the operation of box and running CoreELEC.
GT1 Mini-A pretty much same box, and uses same dtb image, the both USB ports works. I don’t know if the USB ports are properly colour coded on that one, I imagine It might be.
… Alright. I give up, thanks anyways.
What revision do you have?
S/N 95X2 or B95X?
And also link on full dmesg log collected after CE start:
dmesg|paste
Hi boot2k3.
GT1 Mini, S/N: 95X2… The CPU is revision b. This one w/ 4GB of RAM, 64GB of Storage.
Thank you.
About | FAQ | Terms of Service | Privacy Policy | Legal Notice