Based on Google
pci=nomsi means
In Linux,
pci=nomsiis a kernel boot parameter that tells the operating system to disable Message Signaled Interrupts (MSI) and MSI-X for all PCI/PCIe devices. It forces the system to fall back to older, legacy INTx interrupts. [1, 2]
So, the option you would disable …
Disable IO-APIC
Disables using the IO APIC for interrupt routing, forcing the use of the legacy PIC instead.
( Source HAIKU —> User Guide → Bootloader )
There is no way to disable just MSI.
If I read the sourcecode correctly, IO-APIC is unrelated and will not help. Maybe disabling both lcoal APIC and X2 APIC will work (but will also disable other things such as multiple CPUs support).
We should probably add a new option to disable just MSI? It should be relatively simple to implement.
I do not know the options correctly described in the user guide related to the code, but as in case Linux the nomsi ment that interrupts forced to be legacy INTx, so I selected IO APIC disabling - that seemed covers that based on user guide description - especially then SMP still remain if there’s more cores in this machine’s CPU or it is HT capable.
Otherwise an accurately specific option always better.
Yes, pci=nomsi is the solution for different devices: SIS191 network chips, Intel and Atheros Wi-Fi chips, and NVIDIA graphics—it’s a troublesome mix.
The option of implementing names in the Haiku bootloader would be the solution for older Asus/Dell organizers, etc., with serious restrictions for use only in Windows.
Please, it would be a great help to add support for this command in a new “knight” or better yet include it in an official R1 beta 6.
Io/apic not resolved the problem.
The solution for this machine is pci=nomsi
But pci=nomsi no are implemated in the Haiku boot…and force this options for the intelx64 2 core duo gpus and wify atheros ethernet sis 191 and Nvidia 930 gsm are greats problems for compatibility in other os.
Harass means “to annoy or trouble someone repeatedly”.. how can this be harassment with a single message? It seems quite a significant thing to accuse someone of, and your message tone is almost threatening. I would have said the comment made was just an observation, and not offensive? Or are there other messages I’m not aware of?
Seems like a easy hook to add into msi.cpp.
Also, does disabling AIPC also disable MSI currently?
Yes,and no resolve the problem.
There’s definitely a context related to the ongoing conflict over generative “AI” use on this forum that you may be missing, yeah. “harass” is probably not the correct word to have used there, true, but he’s right to call out the snide comment he was referring to as inappropriate.
I would update EFI bootloader if once new features get in and works for you - I’m extremely cautious with bootloader update
I remained on a bootloader from Beta4 era, still had not caused errors booting Beta5 and Nightlies after 2025 February or March - now I have more updated bootloader, and have a copy – with hrevnumber in their original name, not as the standard required for boot – from older versions on the EFI partition.
This way was a bit nervous when some FAT patches had risked file management under Haiku on EFI partition. For examply when copy seemed to resulted into 0 byte size files - fortunately it was fixed.
Yes harass was probably the wrong term, but I also think interpreting the original comment as “snide” could also be a misinterpretation. It could have been a legitimate suggestion to improve communication. Due to other AI debates on the forum it’s easy to assume malicious intent.
In any event, can we keep threads on topic instead of turning every thread into a fight? How does this bickering help OP resolve their issue?
To me the message is quite hostile. Everyone is free to post on this forum in english without beeing told that their english sucks because they did not use the respondents Pet toy.
If the respondent actually cared about the message content they’d quite obviously have asked about content in the message they did not understand, and not solely advertised their tool.
You are absolutely right.
Both @Akakor and @Munchausen had have a chance to show compassion and offer the topic launcher to use his/her native language to describe the problem, or offer to use Google Translate instead.
When I saw first the No. 20th post with full Portuguese/Spanish(?) or else, I put the whole text into Goggle Translate to add as a new post translated to English, as basically I cannot edit the poster’s post directly, but when I look up, I saw the same text I have in my post, then in the post that was non-English, just some minutes before, so the topic launcher already use the Google Translate instead, and updated to English translated one.
In other cases I can imagine he/she replied e.g. from a smartphone, or from other device, and the translation to English was more hard, or have lesser time to use it, so he/she risked to use his/her abilities to express himself in English.
So really, … before we post a not useful note in a topic, think twice, and rather try to answer any other way … as someone trusted the community to get useful, caring help anyway.
Kindness and thoughtful behavior is cheap in energy, but priceless in mindset and attitude.
It also fosters the image that the Haiku community has of itself - despite the sometimes heated debates and disagreements that occur, but what are basically not universal.
We may be a small community, but we try to help, even if there are more appropriate places than our forum, in the case that you ask for help, or as you ask.
I was not uncompassionate to the poster.. I am not concerned about whether or how anyone translates anything or how well they can write in whatever language they choose, and I made no comment about it. I was only surprised by the suggestion of harassment, because it was a heavy thing to read as the third post in a topic, from a moderator, and it struck me as possibly unfair. You have promoted being kind and thoughtful right after naming some people as lacking compassion, and also promoted staying on topic and then written a long off topic post. I don’t believe it was necessary to say anything more. I appreciated the replies to my post, consider the issue resolved/addressed, and was going to say no more about it. I think the matter should lie and the thread continue.
Well, I started from myself when I wrote my post, and I didn’t write it as a criticism, and I also wrote two forum members as addressees with their nicknames, so that they would be sure to be informed about what I wrote, and that it would not be considered as talking behind their backs in any way. If you assessed it as if I wanted to put you on some kind of shame bench, then that was not my intention.
What I wanted to achieve was that the next time you comment, it would be closer to what you would expect when you ask for help.
I also wrote what Akakor could have done (I won’t address him then, because he expressed that he didn’t want to), instead of what he wrote.
In your case, Munchausen, I recognize that you had the right to speak out that you feel that they exaggerated or that the person who previously indicated that they should rather respond or help.
But I ask, didn’t you have the opportunity, like everyone else, to flag the post you disagree with?
Besides, you can write to me that I have no authority to give a moral lesson if I myself am so clumsy that I didn’t separate the two actions in my post when I mentioned them.
I leave it to the possibility that you are right.
However, my primary instinct remains to express that a person here was waiting for help.
That’s the end of it for me.
Ahoy @Sugusapple ,
I will inform you, if the mentioned patch for bootloader to be able to disable MSI only get into merged ones.
That will get into a nightly image soon, so you have to download that nightly image which exactly the same revision number or above. Depends on how much revision were merged between that patch and when buldmaster (the process that compiles code to executable binaries and config files, and make an image - so a bootable Haiku ISO image itself ) does its scheduled work in the night (night in Europian time 
).
Here you can track patches that merged - yourself - if you want.
==
Te avisaré si el parche mencionado para el cargador de arranque (que permite deshabilitar MSI) llega a integrarse en la rama principal. Esto se incluirá pronto en una imagen nightly, por lo que deberás descargar aquella que tenga el mismo número de revisión o uno superior. Todo depende de cuántas revisiones se hayan integrado entre la aplicación de dicho parche y el momento en que el buildmaster (el proceso que compila el código en binarios ejecutables y archivos de configuración para generar una imagen ISO de Haiku arrancable) realice su tarea programada durante la noche (según el horario europeo ).
Thank you very much from the bottom of my heart.
Your patience and selfless help are commendable.
I will look forward to news regarding Haiku and potential `pci=nomsi` settings for the boot process of a future distro.
I am always grateful for the help from you and your friends on the forum.
I didn’t flag because there wasn’t anything directly breaking the rules. One might as well ask why you did not just flag my post instead of writing a reply to it… I imagine the answer is the same.
I do offer what help I can whenever I am able to. By the time I messaged the OP was already receiving a lot of help.
It appears your suggestion is that if one sees something they think might be wrong they should either flag the post as inappropriate content (generally for swearing, adult content etc) or say nothing because anything else besmirches the image of the forum and is unhelpful to newcomers asking for help. I agree that senseless bickering is off putting, but heavy handed messages from moderators are very discouraging to newcomers too, and not something that should go unquestioned IMO. I concede that in this case there was context I was missing and that the spirit of the message I questioned was OK, but I still do not think the tone of the message was appropriate, I don’t think it was a nice thing for a newcomer to encounter, and I don’t regret calling it out. And I had already conceded that the general intent of the message was fair and OK before you stepped in here and prolonged the off topic discussion.