Ask Your Question

steve99's profile - activity

2017-07-03 04:07:32 -0600 received badge  Notable Question (source)
2017-06-03 12:47:44 -0600 received badge  Good Question (source)
2017-06-02 09:50:48 -0600 received badge  Famous Question (source)
2017-05-25 13:28:37 -0600 commented question Fedora 26 Won't Boot if USB 3.0 Hub is Connected

Yes, I have tried different cables and I have tried plugging the hub into a different port. Neither make any difference. Note that with Windows 8.1 and Windows 10 which I multi-boot on the same machine, I don't have the problem.

2017-05-25 13:26:13 -0600 commented question Fedora 26 Won't Boot if USB 3.0 Hub is Connected

I see USB references in Journalctl -b output, but no specific USB hub errors. In dmesg, I see the following errors: [ 4.055971] hub 3-13.3.1:1.0: USB hub found [ 4.056020] hub 3-13.3.1:1.0: 4 ports detected [ 4.131038] usb 3-4.2: new full-speed USB device number 12 using xhci_hcd [ 4.131265] usb 3-4.2: Device not responding to setup address. [ 4.334193] usb 3-4.2: Device not responding to setup address. [ 4.541961] usb 3-4.2: device not accepting address 12, error -71

2017-05-25 12:11:41 -0600 received badge  Popular Question (source)
2017-05-11 14:40:19 -0600 commented answer How to Fix Fedora 25 4.10.10 login screen on wrong monitor

Hi FedUser1975, Have you had a chance to look into this any further as you suggested you would above? Thanks in advance for any new information you can provide.

2017-05-08 11:11:44 -0600 commented answer Fedora 26 Won't Boot if USB 3.0 Hub is Connected

Since both Windows 10 and 8.1 boot fine, I believe that it is a driver problem in Fedora, not a hub problem. I've tried several different brand USB 3.0 hubs, and the all had the same problem.

2017-05-05 11:25:41 -0600 commented answer Fedora 26 Won't Boot if USB 3.0 Hub is Connected

Yes I do use it for flash and hard drives. I should not have to unplug the Hub every time I boot Fedora from a powered off system.

2017-05-03 11:43:30 -0600 received badge  Notable Question (source)
2017-05-02 14:39:22 -0600 received badge  Nice Question (source)
2017-05-01 12:10:03 -0600 asked a question Fedora 26 Won't Boot if USB 3.0 Hub is Connected

My Fedora 26 hangs with the Fedora Boot Logo when booting from the internal hard drive if a USB 3.0 Hub with nothing plugged into it it is connected to the computer. This Dell M2800 laptop in a Dell e-Port Plus docking station is set up to multi-boot Fedora, Windows 10 and Windows 8.1. All are on the laptop's internal hard drive, not a drive through the Hub and nothing is connected to the USB 3.0 Hub. The Grub boot loader comes up fine and I can select Fedora, but then Fedora hangs with its logo on the screen. If I unplug the hub during the hang, the boot continues correctly. If I boot either Windows OS first and then boot Fedora it does not hang. In Windows, I had a problem with the hub not working in Windows 8.1 and 10, but turning off Power Save Mode in the device drivers solved that. Windows did not have a problem booting though. Is the problem in Fedora a Power Save Mode in the hub and it doesn't respond to Fedora when it boots? Is this a bug in the Fedora USB drivers?

How do I get Fedora to boot from power off with the USB Hub connected? I should not have to unplug the Hub every time I boot Fedora from a powered off system.

UPDATE:
I've tried several different brand USB 3.0 hubs and all had the same problem.
I see the following error messages during boot:
can't read hub descriptor (err -22)
hub 4-3.1:1.0: config failed, can't read hub descriptor (err -22)

Thanks in advance for any help on this.

2017-04-29 18:18:18 -0600 commented answer How to Fix Fedora 25 4.10.10 login screen on wrong monitor

OK, your explanation makes sense, but what do you think changed with the Fedora update to cause the login monitor to change? Did there used to be a monitors.xml file in /var/lib/gdm/.config which was deleted, or is this just a work-around to solve the problem because something else changed somewhere else in the update? Will monitors.xml be deleted by future updates and have to be put back after the update? I haven't tried booting Fedora out of the docking station with just the laptop screen - Will the login screen come up on the laptop with this file in place? Again, thank you very much!!!

2017-04-28 17:16:49 -0600 commented answer How to Fix Fedora 25 4.10.10 login screen on wrong monitor

Hi FedUser1975,

THIS WORKED!! My monitors.xml file had the correct monitor set as the primary, but the file was not in the /var/lib/gdm/.config directory. I copied it there without making any changes to it and now the Fedora login screen is on the correct monitor.

How did you find this? Was this file in that directory in prior versions of Fedora, or is this a work-around for another problem? Will this file need to be copied with future updates of Fedora until they fix the root cause of the problem?

Thank you very much for your efforts in this solution!!

2017-04-28 17:10:17 -0600 edited question How to Fix Fedora 25 4.10.10 login screen on wrong monitor

After update from Fedora 25 4.10.9-200 to 4.10.10-200 the login screen changed to the wrong monitor. Fedora 25 is on a Dell M2800 laptop on a Dell ePort Plus docking station. All prior versions of Fedora for years have worked fine with the login screen on the desktop monitor. With this update, the grub boot menu and the boot process messages display on the desktop monitor, but, the Fedora login screen displays on the closed laptop screen (I checked this by opening it) and the Desktop monitor has a blank screen. If I hit return and type in the login password and hit return again, Fedora logs in and comes up on the desktop monitor. I tried a boot with 4.10.9-200 and the login screen comes up correctly on the desktop monitor. I've looked through all the settings in both versions and they are the same. What is wrong with Fedora 25 4.10.10-200 and why did this change??? Am I missing something or is this a bug in this release???

Thanks in advance for any help on this.

UPDATEs: Fedora 25 4.10.10.11 update has the same problem. Fedora 25 4.10.10.12 update also has the same problem. FedUser1975's answer below solved the problem, at least for the current Fedora update or until the Fedora developers resolve the root cause of the problem. The problem has remained fixed with FedUser1975's fix below now for several Fedora updates. FedUser1975 also said below that he would dig deeper and try to understand what changed. Still need the root cause to be addressed by the developers.