I'm dual booting Windows 7 and Fedora 26, both 64-bit, both in EFI mode. When I boot into Windows one of the USBs keeps plugging in and getting unplugged very quickly repeatidly (like once every half a second) nonstop.
When I use the Grub2 bootloader I don't have this problem. But, the reason I switched to rEFIed from Grub2 is because I couldn't get either of my OSes to detect all of my ram (even when trying to set the mem=xxM to a value), which is why I switched to rEFIed, but now I have this USB problem. I can't win!!!
Anyways, thank you. Let me know what I need to do in order to help investigate this problem and fix it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm afraid I've never heard of this problem before, but I do have some suggestions for fixes, or at least workarounds:
Ensure you have the latest USB drivers installed for your computer. This probably means the latest Windows updates, but in some cases you might need to install an update from your computer's manufacturer.
You might try moving the troubled USB device to another USB port on the computer. (The port itself might be defective, or there might be a problem with one USB controller but not another, if the computer has multiple USB controllers.)
If you're using a USB hub, try plugging the device in directly, bypassing the hub.
If you have a USB hub but are not using it, you could try plugging the device in via the USB hub. This is a long shot, though.
Check your firmware for options related to USB devices and try adjusting them. There may be "legacy USB support" options that could affect the way it operates in the target OS, for example.
If you've uncommented the enable_touch line in refind.conf, try commenting it out again.
There may also be options in the Windows boot loader that would help, but I'm not familiar enough with it to offer any specific suggestions.
FWIW, rEFInd doesn't do anything in the firmware that I'd expect would affect USB devices, with the possible exception of the touch screen support (hence my final bullet-point suggestion). GRUB launches Windows in pretty much the same way rEFInd does, so it's puzzling that there's any difference in the way Windows works depending on which boot manager launches the Windows boot loader.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
With windows native bootloader and with grub booting windows I don't have any USB problems whatsoever, so it's gotta be a rEFInd problem. I haven't made any changes to to rEFInd after installing it, so it's at teh defult setup right now. Also, I'm freshly installing both fedora and windows on this computer and have been updating them to the most recent updates as possible, so everything is super up to date.
In addition, when I boot using rEFInd I get graphical glitches in the KDE desktop on Fedora, see attached.
Do you happen to know any way of fixing the grub2 memory issue besides writing the "mem=xxM" in the grub script (since I have tried this already many times with no effect)? Grub basically works perfectly with the exception of this memory issue, but I feel like I just trade the memory issue for other random issues when I try rEFInd. As I don't see really any other bootloaders with UEFI dual-boot Windows/Linux support, my options feel quite limited.
Here's some info about my hardware in case that possibly gives any insight/clues as to what could be going on:
Motherboard: DX79SI
GPU: NVIDIA GeForce 680
CPU: Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz
Actually, in terms of the USB thing. It seems that something else had gone wrong, because it's doing it everywhere now. So disregard that issue.
I recently installed new firmware for the motherboard, but since nothing seemsed to be affected immediately after I didn't consider it to be the source. but it's possible it has to do with that.
Thanks for your help
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The video glitch looks like a driver issue. Video issues occasionally interact with the boot loader -- but note that technically, rEFInd is not a boot loader; it's a boot manager. If the boot loader is interacting with the video drivers in a negative way, it's the EFI stub loader, not rEFInd, that's at fault. I know this distinction isn't a big help, but it may help you isolate the source of the problem. The solution could come in an EFI stub (and therefore kernel) update or in a change to your video drivers. Since you say you've got an Nvidia GPU, that means you at least have a choice between the open source and proprietary drivers, so switching the video drivers might help.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I'm dual booting Windows 7 and Fedora 26, both 64-bit, both in EFI mode. When I boot into Windows one of the USBs keeps plugging in and getting unplugged very quickly repeatidly (like once every half a second) nonstop.
When I use the Grub2 bootloader I don't have this problem. But, the reason I switched to rEFIed from Grub2 is because I couldn't get either of my OSes to detect all of my ram (even when trying to set the mem=xxM to a value), which is why I switched to rEFIed, but now I have this USB problem. I can't win!!!
Anyways, thank you. Let me know what I need to do in order to help investigate this problem and fix it.
I'm afraid I've never heard of this problem before, but I do have some suggestions for fixes, or at least workarounds:
enable_touchline inrefind.conf, try commenting it out again.There may also be options in the Windows boot loader that would help, but I'm not familiar enough with it to offer any specific suggestions.
FWIW, rEFInd doesn't do anything in the firmware that I'd expect would affect USB devices, with the possible exception of the touch screen support (hence my final bullet-point suggestion). GRUB launches Windows in pretty much the same way rEFInd does, so it's puzzling that there's any difference in the way Windows works depending on which boot manager launches the Windows boot loader.
With windows native bootloader and with grub booting windows I don't have any USB problems whatsoever, so it's gotta be a rEFInd problem. I haven't made any changes to to rEFInd after installing it, so it's at teh defult setup right now. Also, I'm freshly installing both fedora and windows on this computer and have been updating them to the most recent updates as possible, so everything is super up to date.
In addition, when I boot using rEFInd I get graphical glitches in the KDE desktop on Fedora, see attached.
Do you happen to know any way of fixing the grub2 memory issue besides writing the "mem=xxM" in the grub script (since I have tried this already many times with no effect)? Grub basically works perfectly with the exception of this memory issue, but I feel like I just trade the memory issue for other random issues when I try rEFInd. As I don't see really any other bootloaders with UEFI dual-boot Windows/Linux support, my options feel quite limited.
Here's some info about my hardware in case that possibly gives any insight/clues as to what could be going on:
Motherboard: DX79SI
GPU: NVIDIA GeForce 680
CPU: Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz
Thank you
Actually, in terms of the USB thing. It seems that something else had gone wrong, because it's doing it everywhere now. So disregard that issue.
I recently installed new firmware for the motherboard, but since nothing seemsed to be affected immediately after I didn't consider it to be the source. but it's possible it has to do with that.
Thanks for your help
The video glitch looks like a driver issue. Video issues occasionally interact with the boot loader -- but note that technically, rEFInd is not a boot loader; it's a boot manager. If the boot loader is interacting with the video drivers in a negative way, it's the EFI stub loader, not rEFInd, that's at fault. I know this distinction isn't a big help, but it may help you isolate the source of the problem. The solution could come in an EFI stub (and therefore kernel) update or in a change to your video drivers. Since you say you've got an Nvidia GPU, that means you at least have a choice between the open source and proprietary drivers, so switching the video drivers might help.