Forum Replies Created
Yes, you can forward audio on M1 Mac NoMachine client, but currently, audio forwarding for M1 Mac servers is not available. This TR is about M1 Mac client.
This TR’s fix and audio forwarding for M1 mac servers will be available in the next release.
thank you for reporting it. In general it is, but currently it is not for Windows.
We opened a Trouble Report for it:
You can use the link to monitor its status.August 27, 2021 at 09:06 in reply to: No Mac audio driver after update to Big Sur 11.5.2 #35003
I’m glad to hear that a problem is solved.August 25, 2021 at 08:50 in reply to: No Mac audio driver after update to Big Sur 11.5.2 #34973
when you manually load nxaudio it still doesn’t appear in output audio device list? or it does (it should) and it does disappear again after restart?
after restart, can you show me output of:
kextstat | grep nxau
after restart when it gone again, run:
sudo touch /Library/Extensions/
and restart machine, does it help?
and can you show me output of again:
kextstat | grep nxau
yes I saw your logs. That’s because initialization is done only once in session, when you first tried to forward disk, so all corresponding lines are how MacOs handles and checks if it is able to run kext. Then when it is sure that kext is runnable nxfs is run when it is needed. That’s why you see only those two lines for the next attempts. But somehow according to that deny log your system still thinks it has no access. Also, you can check if you close the session and open a new one, when you will try forward disk you will still see the first initialization logs.
You can find the instructions on how to collect server-side logs here: https://knowledgebase.nomachine.com/DT11R00182 and upload it.
I ran out of ideas, but it still seems like, nxfs is blocked and not loaded that’s why you see deny error log.
When you are connected to Mac, run:
sudo kextload -vvv /Library/Application\ Support/NoMachine/Extensions/nxfs.kext
And copy its output, if it gives any.
when I first try to mount it does everything but once it fails and I try to mount, it just has the two lines at then end displayed
What do you mean here? Did it work at least once?
what is explained in the TR is different in your case, why do you think it’s the same? Do you do any operation (described in TR) too?
I also checked again replicating your set up and it is working for me. I see same warning in logs as well, wheel group and usually only root user is part of it. But this is not a problem, forwarding should work.
even though pipewire-pulseaudio (specially the latest release) implements a lot of components of Pulse Audio, it still misses some important components to fully support all features that NoMachine achieves using Pulse Audio.
As mentioned in the article you can just switch to Pulse Audio in the meantime.
kextstat output shows that it is loaded also, kextutil output would be different if you didn’t approve it, so you have done it already.
You should have 2 NoMachine audio device.
Can you attach audio MIDI setup’s screens (during the session, while you are connected to your mac)?
1. let’s load nxaudio kext manually:
sudo kextutil -vvv /System/Library/Extensions/nxaudio.kext/
2. if you did not approve it, do::
Access System Preferences -> Security&Privacy -> General panel. Click on the “Allow” button
3. if it finished without any error, check if it’s loaded properly:
kextstat | grep nxau
you should get similar output:
180 0 0xffffff7f83d9c000 0x5000 0x5000 com.nomachine.driver.nxau (4.1.b2) 78172556-B6A4-3112-BA41-E79D18108476 <93 6 5 3 1>
4. restart NoMachine server:
sudo /etc/NX/nxserver --restart
If audio still does not work, please send us the output of kextutil command (point 1) in your reply.
these messages seem ok for disk forwarding, network agent extension shouldn’t do anything with disks.
From previously reply, I see that when you try to forward disk nxfs loading, but to be sure we don’t miss something, can you do the following:
– open the console app on Mac.
– enable/start log messages.
– connect again from Windows and try to forward disk.
– when you reproduce the same behavior, you can stop logging in console app.
– filler log messages with nxfs.
– check if there is some unusual message or error/warning for it.
– if it’s possible, copy all of them and I’ll check too.
I tried many times but was never able to reproduce that issue (with the same setup, same versions), can you check while you getting this behavior, if there are some crashes related to nxnode?
If yes, please upload the corresponding crash report(s).
when you mention that Mac starts hanging, do you mean NX session (do you use terminal in session or are you checking it on actual machine) or actual system starts hanging?
When you press connect button, does it show up permission asking widget for nxfs? or does it show that it is blocked?
https://knowledgebase.nomachine.com/AR01P00962 even if you already allowed it? Can you check does it actually blocked?
Also, can you run again this command while you are forwarding disk and when it fails after too:
After forwarding fails, can you click again on disk (it will show red exclamation mark on it) and check does it show some error message above “export this disk at session startup” option?
to help and to be more clear, can you tell me:
1. What are you doing exactly? When you connect from the Windows client to the Mac server, do you forward Mac’s disk on Win or Win’s disk on Mac?
2. Does it succeed or not? If not, what do you get as an error?
3. What are the client and server NoMachine versions?
4. What are the Mac and Windows versions?
5. When does the Mac hanging starts? While trying to forward disk or after also when if it succeeded?
6. What is the output of the command below on Mac?
glad to hear that it helped.