Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added paragraph about SSE3 support to build-instructions.md. #76

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

osxaudio
Copy link

@osxaudio osxaudio commented Jun 27, 2024

What

Added a small paragraph on how to fix missing SSE3 Support by installing the opemu-linux kernel module.

Why

I just want to save others from going through these two issues: darlinghq/darling#776, darlinghq/darling#882, before arriving at darlinghq/darling#1497 and figuring out the solution by @Mabbs works for them too.

Why like this

Yes build instructions might not be the perfectly correct page for this paragraph, but I didn't find any other “Known Issues Section” and the ZFS problem is also handled here, therefore I think it is not too out of place

Open questions/concerns

Only question, should I add a warning about installing some random kernel module from GitHub ?

Comment on lines +319 to +330
To install [opemu-linux](https://github.com/mirh/opemu-linux) first clone the repository:
```bash
git clone https://github.com/mirh/opemu-linux
```
then switch directories & compile the kernel module:
```bash
cd opemu-linux && make
```
and load it:
```bash
sudo insmod op_emu.ko
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have mixed feelings about including build instructions for projects that the Darling team does not manage. Ideally, you should submit a PR request to the opemu-linux to add build instructions.

With that being said, it's looks like that project is no longer in active development.

or more likely

```
user$ sudo darling shell
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't like the implication of including a command like sudo darling shell in the wiki. I don't want the wiki to imply that this is an okay thing to do.

I recommend removing the user$ darling shell and user$ sudo darling shell part.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants