Repository navigation
v1.5.0-beta.1 is up #524
Closed
darrylmorley
announced in
Announcements
Replies: 6 comments 1 reply
|
Everything looks good on my setup. Not much for me to test this time round, but I've ran a diagnostic suite for good measure. |
0 replies
|
Mac mini m1 with a couple of docks (one usb hub in the monitor and one at the base with an nvme drive, and I stuck a usb stick in the hub at the base
Hub is connected usb-c, monitor connected usb-a
The hub under the Mac mini has a built in usb-c cable, can’t be removed
https://satechi.com/products/stand-hub-for-mac-mini-studio-with-nvme-ssd-enclosure?srsltid=AfmBOorqeviCeArREqoXYrYVelKLE4tV447wnVucJqwRc0xd6iz5QcRl
Stand & Hub For Mac Mini / Studio With NVMe SSD Enclosure
satechi.com
Monitor with usb ports is just a dell screen. Its connected to a KVM so it goes
M1Macmini > kvm > monitor > apple usb keyboard > apple usb mouse (connected via keyboard)


… On 10 Aug 2026, at 10:02 pm, Darryl Morley ***@***.***> wrote:
@jimmyorz <https://github.com/jimmyorz> @aguilaair <https://github.com/aguilaair> @cannotcollide <https://github.com/cannotcollide> @Caruso8677 <https://github.com/Caruso8677> @Mostxlnt <https://github.com/Mostxlnt> @aldobalducci <https://github.com/aldobalducci> @themadturk7 <https://github.com/themadturk7>
New beta: https://github.com/darrylmorley/whatcable/releases/tag/v1.5.0-beta.1
The main thing to check this round is the Built-in USB ports section on desktop Macs:
It now shows one device tree per physical port, with headers like "Built-in USB-A port 1", instead of one big mixed tree. When everything is on USB-A, the section title says "Built-in USB-A ports" outright.
@aldobalducci <https://github.com/aldobalducci>, your M1 Mac mini is the perfect test: plug things into both USB-A ports (a hub with devices behind it too, if handy) and check each device appears under the right port.
@jimmyorz <https://github.com/jimmyorz>, on your M4 mini the front USB-C ports go through the same section, so a quick look that nothing regressed there would be great.
Laptops should see no change at all in this area.
Also in this build: a new diagnostic probe in the test kit (Thunderbolt 5 PHY data), a fix for preferred refresh rate on some displays, and a cable-trust fix. If anyone with TB5 gear runs "Contribute Diagnostic Data" from Settings, that new probe data would be genuinely useful.
As always: use it normally and reply here with anything odd, or "looks fine on [hardware]". Anything that looks like a real bug gets its own issue.
—
Reply to this email directly, view it on GitHub <#524?email_source=notifications&email_token=AITKVI2ZICRLAC5FU2SP6IT5JG2UJA5CNFSNUABBM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63RPGEYDKOBXGMYDNJTSMVQXG33OU5WWK3TUNFXW5JLFOZSW45FMMZXW65DFOJPWG3DJMNVQ>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AITKVI64IJ2WQFQ6TG5P3A35JG2UJAVCNFSNUABJKJSXA33TNF2G64TZHMYTEMRWGI4DMOJRGA5UI2LTMN2XG43JN5XDWMJQGU4DOMZQG2QXMAQ>.
You are receiving this because you were mentioned.
|
1 reply
|
Mac OS 26.6.1 (25G76)
Is this what you were looking for

… On 11 Aug 2026, at 7:06 am, Darryl Morley ***@***.***> wrote:
@aldobalducci <https://github.com/aldobalducci> Thanks for the setup detail. Nice test case, especially the keyboard-behind-monitor-behind-KVM chain. When you get a minute, could you paste a screenshot of the "Built-in USB ports" section? On macOS 26 it should now split per port with a "Built-in USB-A port 1" heading above your KVM chain, and I'd like to see it on real hardware. If you're on an older macOS it'll look unchanged, that's expected there.
—
Reply to this email directly, view it on GitHub <#524?email_source=notifications&email_token=AITKVI3OBKOPP6BTWJ7KDYT5JI2MFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZZGY4DANZWUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17968076>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AITKVI7FE4OQ2VSZHVYHN435JI2MFAVCNFSNUABJKJSXA33TNF2G64TZHMYTEMRWGI4DMOJRGA5UI2LTMN2XG43JN5XDWMJQGU4DOMZQG2QXMAQ>.
You are receiving this because you were mentioned.
|
0 replies
|
Oops, I reverted back to see if I can get one of my license keys to work, but it didnt
Back on beta now

… On 11 Aug 2026, at 7:13 am, Aldo Balducci ***@***.***> wrote:
Mac OS 26.6.1 (25G76)
Is this what you were looking for
<PastedGraphic-1.png>
> On 11 Aug 2026, at 7:06 am, Darryl Morley ***@***.***> wrote:
>
>
> @aldobalducci <https://github.com/aldobalducci> Thanks for the setup detail. Nice test case, especially the keyboard-behind-monitor-behind-KVM chain. When you get a minute, could you paste a screenshot of the "Built-in USB ports" section? On macOS 26 it should now split per port with a "Built-in USB-A port 1" heading above your KVM chain, and I'd like to see it on real hardware. If you're on an older macOS it'll look unchanged, that's expected there.
>
> —
> Reply to this email directly, view it on GitHub <#524?email_source=notifications&email_token=AITKVI3OBKOPP6BTWJ7KDYT5JI2MFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZZGY4DANZWUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17968076>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AITKVI7FE4OQ2VSZHVYHN435JI2MFAVCNFSNUABJKJSXA33TNF2G64TZHMYTEMRWGI4DMOJRGA5UI2LTMN2XG43JN5XDWMJQGU4DOMZQG2QXMAQ>.
> You are receiving this because you were mentioned.
>
|
0 replies
|

… On 10 Aug 2026, at 10:02 pm, Darryl Morley ***@***.***> wrote:
@jimmyorz <https://github.com/jimmyorz> @aguilaair <https://github.com/aguilaair> @cannotcollide <https://github.com/cannotcollide> @Caruso8677 <https://github.com/Caruso8677> @Mostxlnt <https://github.com/Mostxlnt> @aldobalducci <https://github.com/aldobalducci> @themadturk7 <https://github.com/themadturk7>
New beta: https://github.com/darrylmorley/whatcable/releases/tag/v1.5.0-beta.1
The main thing to check this round is the Built-in USB ports section on desktop Macs:
It now shows one device tree per physical port, with headers like "Built-in USB-A port 1", instead of one big mixed tree. When everything is on USB-A, the section title says "Built-in USB-A ports" outright.
@aldobalducci <https://github.com/aldobalducci>, your M1 Mac mini is the perfect test: plug things into both USB-A ports (a hub with devices behind it too, if handy) and check each device appears under the right port.
@jimmyorz <https://github.com/jimmyorz>, on your M4 mini the front USB-C ports go through the same section, so a quick look that nothing regressed there would be great.
Laptops should see no change at all in this area.
Also in this build: a new diagnostic probe in the test kit (Thunderbolt 5 PHY data), a fix for preferred refresh rate on some displays, and a cable-trust fix. If anyone with TB5 gear runs "Contribute Diagnostic Data" from Settings, that new probe data would be genuinely useful.
As always: use it normally and reply here with anything odd, or "looks fine on [hardware]". Anything that looks like a real bug gets its own issue.
—
Reply to this email directly, view it on GitHub <#524?email_source=notifications&email_token=AITKVI2ZICRLAC5FU2SP6IT5JG2UJA5CNFSNUABBM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63RPGEYDKOBXGMYDNJTSMVQXG33OU5WWK3TUNFXW5JLFOZSW45FMMZXW65DFOJPWG3DJMNVQ>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AITKVI64IJ2WQFQ6TG5P3A35JG2UJAVCNFSNUABJKJSXA33TNF2G64TZHMYTEMRWGI4DMOJRGA5UI2LTMN2XG43JN5XDWMJQGU4DOMZQG2QXMAQ>.
You are receiving this because you were mentioned.
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
@jimmyorz @aguilaair @cannotcollide @Caruso8677 @Mostxlnt @aldobalducci @themadturk7
New beta: https://github.com/darrylmorley/whatcable/releases/tag/v1.5.0-beta.1
The main thing to check this round is the Built-in USB ports section on desktop Macs:
Also in this build: a new diagnostic probe in the test kit (Thunderbolt 5 PHY data), a fix for preferred refresh rate on some displays, and a cable-trust fix. If anyone with TB5 gear runs "Contribute Diagnostic Data" from Settings, that new probe data would be genuinely useful.
As always: use it normally and reply here with anything odd, or "looks fine on [hardware]". Anything that looks like a real bug gets its own issue.
All reactions