Mac Issues

[portapack-mayhem]

Mac Issues

[tomzhu1024]

Similar issue: it can connect, but when I try to update to the latest release, both the web app and pp freeze.

2021 MacBook Pro w/ M1 Pro, macOS: Sonoma 14.2.1, Chrome: 121.0.6167.184, Mayhem: n_240214

[u-foka]

Same here: it connects, but when trying to send files larger thatn ~256 bytes the pp freezes.

M1 Pro in a 2021 MBP, Sonoma 14.2.1, Chrome 121.0.6167.85, Mayhem: n_240128

[pedroCX486]

Interestingly I seem to not have those issues on my MBP M1 Pro, could it be an issue with only certain clones or MacOS versions?

[loewal]

Similar issue: it can connect, but when I try to update to the latest release, both the web app and pp freeze.

2021 MacBook Pro w/ M1 Pro, macOS: Sonoma 14.2.1, Chrome: 121.0.6167.184, Mayhem: n_240214

Same here on Mac Mini M2 Sonoma

[e-minguez]

Same here: it connects, but when trying to send files larger thatn ~256 bytes the pp freezes.

M1 Pro in a 2021 MBP, Sonoma 14.2.1, Chrome 121.0.6167.85, Mayhem: n_240128

Same MBP M2. Portapack frozen after trying to send a small 5KB file.

[EricBoily]

same but with intel mac. 2018 MBP16. brand new portapack.
when I click on "update" this happend in the command windows and the connection is cut.

ch> mkdir /FIRMWARE
Error calling delete_file: 8 exists
ch> fclose
no open file
ch> fopen /FIRMWARE/mayhem_nightly_n_240227_OCI.ppfw.tar
ok
ch> fseek 0
ok
ch> fwb 100000
send 100000 bytes

[tony1tf]

I'm getting the same error on an M2 MacBook Pro when trying to update the firmware to the nightly release.

mkdir /FIRMWARE
Error calling delete_file: 8 exists
ch> fclose
no open file
ch> fopen /FIRMWARE/mayhem_nightly_n_240312_OCI.ppfw.tar
ok
ch> fseek 0
ok
ch> fwb 100000
send 100000 bytes

[tony1tf]

Further to the above, going to the Flash Utility, the firmware folder shows the nightly build is present. Using the flash utility shows it to be a 'BAD FIRMWARE FILE', so it won't flash.

[tony1tf]

Is anyone who understands Macs and PortaPack looking into this problem? What debugging can we do to help?

[gullradriel]

The issue is on hold at the moment.
Please wait for us to resume it, soon, when our schedule will allow it.

[tony1tf]

Hi gullradriel,
Thanks for replying. As I said in my post, is there anything us users can do to help debug the problem? I've started looking at the code, but it is a bit outside my abilities.
Tony

[jLynx]

Not at the moment. The main issue we are having is we lack mac developers for MayhemHub making it hard to debug and develop for

[fuomag9]

m1, live screen updates are VERY slow. Commands to control seem to work but have some seconds latency