• 0 Posts
  • 35 Comments
Joined 23 days ago
cake
Cake day: March 28th, 2025

help-circle




  • I’ve had Windows and Linux installed on the SAME drive for decades and don’t have this issue. Install Windows first because it WILL fuck up the EFI boot partition, that’s inevitable because Windows sucks, then install Linux, use the manual partition option and simply select the existing EFI System partition for the EFI and DO NOT mark format, Linux will then install and leave the Windows boot loader in the EFI partition undisturbed.

    Linux WILL overwrite the boot block to start grub instead of the Windows boot loader, but most Linux distros will automatically add a chain boot loader entry to the grub menu to allow you to boot Windows, at least Debian and Redhat derived distros will do this, probably a more manual process in Arch derived distros.

    If it does become necessary to install Whendoze after Linux, you can use boot-repair to automatically fix the EFI System partition Windows fucked up or you can boot off of a flash drive, and fix it manually.



  • One of the things you run into with audio production software is that in order to maintain accuracy with respect to phasing between channels, they require very accurate timing, this usually comes at the expense of very high interrupt rates and context switching and under the best of circumstances this is hardware intensive, more so with older processors that don’t have single instructions for storing the entire register set or restoring the entire register set to the stack with one instruction as many modern CPUs do. So hate to say it but you may need to upgrade to something less geriatric. You might also try a real-time kernel, it might allow the application to keep things sync’d up with less hardware interrupts though it will rely more on software interrupts do do the same. Unfortunately, I have found that while I can get the performance I require on my six year old processor using a realtime kernel, it has come with a sacrifice of stability, that is to say real time on my hardware at least has not been terribly stable.






  • @marauding_gibberish142 I personally find the Intel ME a useful feature, it’s nice for example to be able to upgrade BIOS without a CPU and/or memory, this has allowed me for example to upgrade the BIOS to a version needed for a newer CPU on a board with a BIOS that didn’t initially support it without needing the older CPU to perform the upgrade. And from a security standpoint, if you do not enable and configure the network stack, and you don’t have a DHCP server available to it for it do so on it’s own, I really don’t see what it can do that is harmful.


  • @jeena I grant you that is true, but under Linux, the kernel talks to the hardware directly after boot, not through BIOS calls. About the only time you would talk to the BIOS after boot is for sleep/suspend, or in rare cases such as the server my friendica instance runs on, for temp/CPU speed control because Linux kernel has issues properly using the MSR on the i9-10980xe, oddly it does not seem to have the same issue on the i9-10900x which is a ten core CPU in the same family, so I am forced to depend upon ACPI since talking to the hardware directly in this specific case is problematic. If you were running Windows or if you had weird hardware that is somewhat broken under Linux like mine, I can see the need, or if a laptop and you wanted sleep/suspend functionality. But for what you describe it isn’t clear the benefits. And there are some risks like it probably isn’t going to do the extensive memory training of a more advanced UEFI bios like American Megatrends, so your memory access may not be as efficient as it could be, and you’re more limited in hardware selection.