macOS release does not detect SDRs on M1 MacBooks

[mehdideveloper]

I tried the latest built on M1 MacBook. Although SoapySDR detects my SDRs, SigDigger does not. Even clicking on Refresh in the Devices dialog does nothing. SoapySDR and the modules are compiled from source.

[BatchDrake]

The .DMG is intended for x86_64 targets. I don't have any M1 machines at hand to build SigDigger, and I'm surprised you could even execute it. Does CubicSDR for x86_64 work in your machine?

Cheers,

El lun., 29 nov. 2021 22:41, Mehdi A. @.***> escribió:

I tried the latest built on M1 MacBook. Although SoapySDR detects my SDRs, SigDigger does not. Even clicking on Refresh in the Devices dialog does nothing. SoapySDR and the modules are compiled from source.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/BatchDrake/SigDigger/issues/165, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEVET6IBSBTUZK6V7YSMDTUOPXPLANCNFSM5JAFQENA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[mehdideveloper]

Yes. The new MacBooks (running M1 which itself is ARM-based) run x86 binaries using dynamic binary translation. I have had the laptop for 4 days now and haven't had time to test SDR apps. I will continue to do my tests and will let you know if I have success in getting it to detect and run SDRs (I may compile it)

[mehdideveloper]

And regarding your question on CubicSDR: yes I can run CubicSDR without an issue on the M1 mac (I just use their x86 binary)

[BatchDrake]

Well, I don't think I will be able to debug this issue anytime soon :/

Can you confirm if it works in x86-64 machines? Because if that were the case, it would look like Apple not being able to emulate their own binaries.

El lun., 29 nov. 2021 23:14, Mehdi A. @.***> escribió:

And regarding your question on CubicSDR: yes I can run CubicSDR without an issue on the M1 mac (I just use their x86 binary)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/BatchDrake/SigDigger/issues/165#issuecomment-982072612, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEVET3U52MG2XHGHLSKTMDUOP3L5ANCNFSM5JAFQENA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[mehdideveloper]

No worries. I'll play with the builds and will let you know if I manage to run it. And no it does not run on my Intel laptop. Actually, when I click on Refresh in the Devices dialog, the app exits (seg fault) Here's what the debugger shows me:

thread #13, name = 'QThread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0) frame #0: 0x0000000100b1bed5 libsuscan.0.3.0.dylibsuscan_source_detect_devices + 901 libsuscan.0.3.0.dylibsuscan_source_detect_devices: -> 0x100b1bed5 <+901>: movq (%r12), %rdi 0x100b1bed9 <+905>: testq %rdi, %rdi 0x100b1bedc <+908>: je 0x100b1bec0 ; <+880> 0x100b1bede <+910>: leaq 0x2985e(%rip), %rsi ; "remote"

[BatchDrake]

Damn, so it is not an M1 problem. I'll look into this tomorrow.

El lun., 29 nov. 2021 23:35, Mehdi A. @.***> escribió:

No worries. I'll play with the builds and will let you know if I manage to run it. And no it does not run on my Intel laptop. Actually, when I click on Refresh in the Devices dialog, the app exits (seg fault) Here's what the debugger shows me:

thread #13 https://github.com/BatchDrake/SigDigger/issues/13, name = 'QThread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0) frame #0: 0x0000000100b1bed5 libsuscan.0.3.0.dylibsuscan_source_detect_devices

• 901 libsuscan.0.3.0.dylibsuscan_source_detect_devices: -> 0x100b1bed5 <+901>: movq (%r12), %rdi 0x100b1bed9 <+905>: testq %rdi, %rdi 0x100b1bedc <+908>: je 0x100b1bec0 ; <+880> 0x100b1bede <+910>: leaq 0x2985e(%rip), %rsi ; "remote"

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/BatchDrake/SigDigger/issues/165#issuecomment-982085594, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEVETYXZGF6GUV3CUFV3ZLUOP5ZVANCNFSM5JAFQENA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[BatchDrake]

Just opened this in a Macbook, but I just can't reproduce it. It detects RTL-SDR just fine.

[BatchDrake]

I am talking about the .dmg btw.

[mehdideveloper]

You tried on an x86 MacBook, right? I tried on another x86 MacBook and I don't get the segfault there, but clicking on Refresh does not show the SDR (although SoapySDRUtil detects it)

[BatchDrake]

I've just tested it back in a macbook, it turns out it had the old libraries installed and I was able to reproduce the crash. I'll look into it these days.

[BatchDrake]

I may have fixed it. I have already scheduled a development release and you should have a new .dmg within the hour.

Cheers,

[mehdideveloper]

It actually fixed the other issue (right panel size) but it still does not detect SDRs.

[BatchDrake]

FYI https://github.com/BatchDrake/SigDigger/issues/99#issuecomment-984535948

[mehdideveloper]

Great job! Now it works on my MacBook Pro 14" M1 and detects RTL-SDR. I will continue to test it with other SDRs.

[hpux735]

I can verify this works for me on my M1, also. The rtl-sdr is detected, and works great!

[juanibuqt]

I tested too in an M1 MacBook Pro and I confirm this new release work great. Thanks!

[BatchDrake]

I am marking this as fixed, thanks everyone!