issoeocio Posted December 26, 2018 Share Posted December 26, 2018 if after adding irqpoll the log is showing errors like "hpet1: lost 7160 rtc interrupts" add hpet=disable in the same line of the kernel Link to comment Share on other sites More sharing options...
lapseart Posted January 5, 2019 Share Posted January 5, 2019 On 12/26/2018 at 4:15 PM, issoeocio said: 4 years later. I solved it. In Linux GRUB, add pci=biosirq irqpoll in the kernel line. Could you please explain how we can do that. Link to comment Share on other sites More sharing options...
issoeocio Posted January 5, 2019 Share Posted January 5, 2019 (edited) 40 minutes ago, lapseart said: Could you please explain how we can do that. Simply add pci=irqpoll in the grub (or you preferred bootloader) kernel line. Something like this: Spoiler kernel /boot/vmlinuz-linux root=/dev/sda3 pci=irqpoll quiet splash You can find better information on how to insert kernel parameters in the Arch Linux wiki. Edited January 5, 2019 by issoeocio Link to comment Share on other sites More sharing options...
lapseart Posted January 7, 2019 Share Posted January 7, 2019 On 1/5/2019 at 1:19 PM, issoeocio said: Simply add pci=irqpoll in the grub (or you preferred bootloader) kernel line. Something like this: Reveal hidden contents kernel /boot/vmlinuz-linux root=/dev/sda3 pci=irqpoll quiet splash You can find better information on how to insert kernel parameters in the Arch Linux wiki. thanks for the information. Is this work for windows ? Link to comment Share on other sites More sharing options...
issoeocio Posted January 8, 2019 Share Posted January 8, 2019 On 1/7/2019 at 3:47 PM, lapseart said: thanks for the information. Is this work for windows ? No. Link to comment Share on other sites More sharing options...
crazyi Posted April 30, 2019 Share Posted April 30, 2019 On 1/9/2019 at 3:22 AM, issoeocio said: No. Do you have any idea to fix this on windows 10? Link to comment Share on other sites More sharing options...
jokerhyc Posted September 6, 2019 Share Posted September 6, 2019 oh my god...i got the same issue here... Link to comment Share on other sites More sharing options...
b3rg3r Posted July 26 Share Posted July 26 Hi, I know this post is quite old but I've just found a solution to share to make it works on Windows 10 for those who had this problem, here is what I did: There is a way to enable (or disable) Message Signaled Interrupts for devices in Windows via Regedit, but strangely it didn't worked with the Windows stock driver, but it worked with other driver versions. For details this is the driver version I used: 7.35.317.3 For the regedit patch you need to go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\YOUR_DEVICE_DETAILS\SOME_STRING\Device Parameters\Interrupt Management\ Then create a new Key called "MessageSignaledInterruptProperties" and inside and new DWORD 32 bits with a value of "1". In my case the Regedit path looks like this HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_14E4&DEV_43B1&SUBSYS_062317AA&REV_03\4&69117cd&0&00E1\Device Parameters\Interrupt Management\MessageSignaledInterruptProperties Then either reboot or just disable/enable the device in Hardware manager and it should be fine. Screenshot of the regedit here: https://imgur.com/a/U5R6tmM Link to comment Share on other sites More sharing options...
Recommended Posts