Nord User Forum

I received my stage 3 88 on Wednesday which came with OS v1.02. Today I decided to update the OS and since I'm a linux user the task wasn't straight forward as you could imagine. I don't have dual boot and I didn't want to go through that hassle just to use nord software. So I decided to give it a try with a virtual machine. I successfully managed to update the OS, but had some minor issues along the way and I would like to share my story in case someone is in the same position.

I did it in a virtual box machine with windows 10. Keep in mind that to be able to get access to a USB device in the host you have to add your user to the vboxusers group. I also had to install the virtual box extension pack (available in the AUR for arch users https://aur.archlinux.org/packages/virt ... xt-oracle/) to enable support for usb 2.0 and 3.0. If everything goes well you should be able to select the nord USB device as shown in the following image.



After that I installed the driver and the sound manager. Being able to see all my programs in the sound manager gave me the confidence to proceed with the OS update. I opened the update OS utility, which recognized that my current version was 1.02, and then clicked updated. My nord stage rebooted and then everything went to black. After rebooting everything froze and the update utility din't show me the progress bar as it supposed to. I started crying and questioning all the decision I made in my life. After a minute lying in the ground thinking what to do with a 4 thousand dollars set of transistors I started to calm down. When I was deciding if I should disconnect my nord or keep waiting I realized that the USB device was disconnected from the virtual machine and when I connected it again the update utility started to show the progress bar. After the updated finished the USB disconnected again and I had to connect it for the update utility to say that everything was done.

After some though the behavior wasn't strange at all. When the update process starts and ends the nord reboots, meaning that the USB connection is lost. Because I haven't vbox configured to automatically connect the device to the VM the software kept waiting for the nord to reconnect. The same should happen connected directly to a machine. I assume if you add a filter to vbox to automatically connect the device everything should go smoothly.

That's my story

Hello,

Thanks for the feedback. You may have post here:
http://www.norduserforum.com/nord-stage ... lit=ubuntu

Regards

I'm so glad I found this. I have the same issue where the update utility fails to locate the piano after it reboots into update mode. How exactly did you reconnect the usb after it reboots? Nothing seems to work here, neither reconnecting the usb manually or unticking the "clavia usb" in VirtualBox. The piano is stuck on "ready for update"..

Hi
I just bought a nord stage 3 and experienced the trouble described above.

The procedure is:
Launch update software from your VM.
Then when the Nord Stage 3 restarts, it displays 'ready for update' and waits.
In your virtual machine configuration, remove and add the nord stage 3.
Windows reacts as a device (i.e. your brand new nord stage 3) is connected, update software is triggered and updates your nord Stage.
Then again, the Nord Stage 3 restarts.
In your virtual machine configuration, remove and add the nord stage 3 again.
Windows reacts as a device (i.e. your brand new nord stage 3) is connected, update software is triggered and confirms the nord stage 3 update is done.

So glad it works!

Rather than having to install a VM AND windows (for which one needs a license, or am I mistaken?), it would be so cool if Clavia found a way of making their software run though Wine.
Actually the sample editor works fine under wine, but the USB driver does not.

Mr_-G- wrote:it would be so cool if Clavia found a way of making their software run though Wine.

Oh yes ! I definitely second that ! (All Mint machines here, forced to use VirtualBox for updates).