Release 1.12.0-RC1

I also tried with Windows 10 and didn’t worked (but maybe there was missing a driver).

dmesg

[  338.298838] usb 1-2: new high-speed USB device number 5 using xhci_hcd
[  338.452139] usb 1-2: New USB device found, idVendor=1d6b, idProduct=0104, bcdDevice=32.30
[  338.452142] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  338.452144] usb 1-2: Product: MOD Dwarf
[  338.452145] usb 1-2: Manufacturer: MOD Devices
[  338.452147] usb 1-2: SerialNumber: 00523
[  338.481407] cdc_ether 1-2:1.0 usb0: register 'cdc_ether' at usb-0000:00:14.0-2, CDC Ethernet Device, 12:00:52:ff:ff:ff
[  338.481635] usbcore: registered new interface driver cdc_ether
[  338.482308] usbcore: registered new interface driver snd-usb-audio
[  338.502078] cdc_ether 1-2:1.0 enx120052ffffff: renamed from usb0

When I connect, appears
image

But after some time there was appears some message error and dmesg added

[  382.924606] iwlwifi 0000:03:00.0: Unhandled alg: 0x71b
[  382.924643] iwlwifi 0000:03:00.0: Unhandled alg: 0x71b
[  387.662454] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7
[  390.602359] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7

and shows
image

After tried to reconnect, I checked ip addr. Connection is apparently ok

9: enx120052ffffff: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 12:00:52:ff:ff:ff brd ff:ff:ff:ff:ff:ff
    inet 192.168.51.119/24 brd 192.168.51.255 scope global dynamic noprefixroute enx120052ffffff
       valid_lft 43151sec preferred_lft 43151sec
    inet6 fe80::d903:6559:1819:1a02/64 scope link noprefixroute 
       valid_lft forever preferred_lft foreve

If I try to access

$ ssh root@192.168.51.1 -vvv
OpenSSH_8.2p1 Ubuntu-4ubuntu0.5, OpenSSL 1.1.1f  31 Mar 2020
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug2: resolve_canonicalize: hostname 192.168.51.1 is address
debug2: ssh_connect_direct
debug1: Connecting to 192.168.51.1 [192.168.51.1] port 22.
debug1: Connection established.
debug1: identity file [...]
debug1: identity file [...]
debug1: identity file [...]
debug1: identity file [...]
debug1: identity file [...]
debug1: identity file [...]
debug1: identity file [...]
debug1: identity file [...]
debug1: identity file [...]
debug1: identity file [...]
debug1: identity file [...]
debug1: identity file [...]
debug1: identity file [...]
debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.5

and nothing occurs

1 Like

I tried the SPDIF option, it seems very convenient. A question about audio quality here: What is convenient to use? the analog or digital outputs? Does the A / D conversion for your benchmarks create noticeable aliasing or can it be used for recording?

Only thing I noticed is an increase in volume / headroom on SPDIF.

Thanks

1 Like

I tried a lot of combination of turn off and turn on and no one worked.

@falkTX, is it possible to downgrade the mod version without losing the user data? I didn’t backup the pedalboards :frowning:

1 Like

You can always safely downgrade, only the factory-reset images will delete/format user data.

But we are moving forwards with 1.12, not backwards. So it is best to try to find the reason this fails.
From what I have seen, you are the first one to have this issue.

The line from your system:

[  387.662454] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7

look very suspicious. perhaps you are running a hardened/locked down kernel?

2 Likes

this is something which will make MOD footswitch even more super tweakable unit.

5 Likes

This is great!

4 Likes

Appreciate the continued development to bring the DuoX up to parity…

…apart from the bank and snapshot management system

Any idea when these might arrive?

2 Likes

Just to describing clearly when I detected the problem at the first time:

  1. I connected the mod dwarf on my computer;
  2. I open http://moddwarf.local
  3. The website recommended a system update (because I’m in the beta testers)
  4. I updated
  5. I waited the mod dwarf reboot, and it occurred
  6. I waited the http://moddwarf.local autoreload after update, as usual. But it didn’t occurred;
  7. I tried reload the page, reconnect mod dwarf, reboot mod dwarf, reboot my laptop and all of them didn’t worked.

I don’t know. But I remember that I updated the kernel recently by the usual process: the update software recommends me to install the updated versions and I agreed.

Edit: dmesg shows me

> dmesg | grep lockdown
[    0.000000] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7
[    0.758835] Lockdown: swapper/0: hibernation is restricted; see man kernel_lockdown.7
[    1.088470] Lockdown: systemd-udevd: unsigned module loading is restricted; see man kernel_lockdown.7
[    1.311098] Lockdown: systemd-udevd: unsigned module loading is restricted; see man kernel_lockdown.7
[    3.267303] Lockdown: systemd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7
[    4.472297] Lockdown: systemd-udevd: unsigned module loading is restricted; see man kernel_lockdown.7
[    4.873894] Lockdown: systemd-udevd: unsigned module loading is restricted; see man kernel_lockdown.7
[    7.035138] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7
[    7.082725] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7
[    7.481161] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7
[    7.996648] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7
[    8.341536] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7
[    9.001813] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7
[    9.293058] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7
[    9.735359] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7
[   10.081884] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7
[   10.674749] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7
[   10.909992] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7
[   17.422051] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7
[   17.675217] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7
[   19.971157] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[   19.977057] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[   19.978826] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[  234.980546] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7
[  235.150850] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7
[  235.469220] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7
[  235.472590] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[  235.474357] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[  235.474592] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[  235.474804] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[  235.474812] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[  242.056668] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7
[  395.639134] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7
[  397.188894] Lockdown: modprobe: unsigned module loading is restricted; see man kernel_lockdown.7
[  558.080931] Lockdown: fwupd: /dev/mem,kmem,port is restricted; see man kernel_lockdown.7

Some other tests that I did:

  • I tested the dwarf on a Windows 10 on the same computer and didn’t worked;
  • I tested the dwarf on a Kubuntu 22.04 live cd on the same computer and didn’t worked;
  • I tested the equipment on other computer with Windows 10 and didn’t worked;
  • I took the dwarf to my work and tested with an Ubuntu 22.04 and an Ubuntu 20.04 and they worked!

I don’t know what is happening :thinking:

1 Like

For now it seams all right !
Thanks a LOT for making the possibility to dim LEDs !

3 Likes

Same here on Dwarf :pensive:

1 Like

Fixed himself after a couple of reboots.

4 Likes

I have a Mod Duo X (mdx) and with the 1.12.0-RC1 it runs so far without problems. After the update I had to reboot the mdx several times because it was not recognized by the computer (Web Gui), then everything was fine.
Separate SPDIF is so cool, so you have more routing options. …

2 Likes

For those that had issues with USB not being recognized, do you mind if I open a private/direct message with you with links to an updated build?
It supposedly fixes the behaviour, would be great to confirm before doing an RC2.
Thanks!

8 Likes

Please! I would appreciate.

3 Likes

Please!

3 Likes

I’m using this new release last days with my dwarf. I liked a lot the new LED brightness and the go back control page is perfect… Thanks a lot!

Only my bluetooth 5 dongle is not working anymore. Will you include the rtl8761bu_fw.bin firmware file in the next RC??

Apart from that, I think it will be great to have the go back function aswell when you assign the plugin presets to one footswitch (… and simetrical :blush: )

4 Likes

THX

A few ideas:

  • If you could rename the output e.g. “Hardware Playback 1/2 Analog” and “Hardware Playback 3/4 SPDIF” in the web GUI I would find my way around even faster.

And some more:

  • Is it possible to display (and disconnect, …) the connections to the other plugins at the I/O of the plugins when the mouse pointer is over a connection? I find that very helpful with Cardinal/vcf rack.

  • Also if you could set the relative length of patch cables would be useful. Like you can do with Cardinal/vcf rack.
    VCV Manual - Menu Bar

2 Likes

We do not include any radio-like (bluetooth/wifi) firmware, at all.

If you have placed firmware on the dwarf user data, alike done with wifi, it will remain across updates unless you factory reset it.

2 Likes

Good enough for me. Thanks!

Strangely I don’t recall to have done it before, and it was working before 1.12-RC1… with no factory reset yet.

2 Likes