T3 will not boot up when DVBT USB Tuner and USB WiFi Adapter (RTL8192CU) Both connected to rear USB
Issue #186
resolved
If you connect both the Beyonwiz Shop supplied DVBT USB Tuner and the Beyonwiz Shop supplied USB WiFi Adapter to the rear USB ports, either directly or via extension cable, the T3 will get stuck in Booting. If you move the USB WiFi Adapter to the front the T3 boots up as normal. When the USB DVBT tuner or the USB WiFi Adapter is connected to the rear alone the T3 boots up as normal. If you have the USB DVBt tuner in the rear USB and the USB WiFi Tuner in the Front the T3 boots as normal. And lastly if you connect 2 other items to the rear such as USB DVBt tuner and Samsung 1TB External HDD bot to the rear the T3 boots up as normal.
Reproduction steps
Connect the Beyonwiz supplied DVBt USB tuner and USB WiFi Adapter to rear USB ports and power up, T3 will get stuck in booting.
Comments (12)
-
-
A file was uploaded. reference to attachment NormalUSBDevicesNoBoot.log (Boot failure with HUB, USB tuner, WiFi dongle, Bluetooth dongle and keyboard connected.)
-
A file was uploaded. reference to attachment HubWithFirmwareStickOnlyBoot.log (Boot successful with only firmware stick attached to hub but firmware stick unreadable.)
-
A file was uploaded. reference to attachment PlugInHub.log (During operation I plugged in the hub with the questionable USB stick attached.)
-
I should also note that the USB stick used in the logs above when connected after booting the unit appeared to work normally (despite the errors logged via the serial port).
-
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from New to Confirmed.
-
- removed issue_priority
- removed issue_severity
The issue was updated with the following change(s):
- The severity has been updated, from Normal to Major.
- The priority has been updated, from Normal to High.
-
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Confirmed to Delegated.
-
- removed issue_category
The issue was updated with the following change(s):
- The category has been updated, from Not determined to Driver / Hardware.
-
- removed issue_severity
The issue was updated with the following change(s):
- The severity has been updated, from Major to CRASH.
-
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Delegated to Testing.
-
- removed issue_resolution
- removed issue_percent
- removed issue_close
- removed issue_status
The issue was updated with the following change(s):
- The status has been updated, from Testing to Closed.
- This issue has been closed
- This issue's progression has been updated to 100 percent completed.
- The resolution has been updated, from Not determined to Fixed.
- Log in to comment
While Jai has a device specific example this problem can and does affect a large range of USB devices attached to the T3.
I have found that removing all devices from the T3 and connecting them to a powered hub which is the only device attached directly to the T3 usually makes the problem go away.
The only time this hasn't worked for me is when I attached a USB memory stick that used to work but after about 10 weeks of use suddenly stopped working. The T3 claimed that the device was "not ready". I swapped to a different memory stick and the USB hub solution continues to avoid boot failures.
I have attached some serial port logs to show some of the issues I noted.