path4

Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • in reply to: Mavericks not supported? #556
    Avatarpath4
    Participant

    Thanks! As I remember, it was indeed when loading nxusb something in verbose mode that the kernel crashed.

    If you work for nomachine, please let your developers know that we don’t really need usb support, client or daemon. All we need is a desktop so that we can keep working on a doc file or some other code after we get home. By the way, nomachine rocks! I remote into a linux computer, and it is very fast.

    in reply to: Mavericks not supported? #546
    Avatarpath4
    Participant

    I had the same problem. However, you don’t need to completely remove nomachine app. The client works fine. It is the server that gives you kernel panic. You need to remove the following to avoid kernel panic:

    1. nomachine’s kext in folder /System/Library/Extensions
    2. remove *nx* in /Library/LaunchStartItems, /Library/LaunchAgent, /Library/LaunchDaemon

    I don’t remember the files exactly, but you get the idea — just remove it from start up scripts so that the daemon is not started. The client works fine. Of course, if you removed those, you won’t be able to remote into your mac. If you need that, you may have to look deeper into the scripts and plist to pin point the problem.

Viewing 2 posts - 1 through 2 (of 2 total)