Mac, Calibre don't see Sage

[Quoth]

Originally Posted by Aleron Ives

This is a longshot, but maybe you could try enabling automatic USB mode? Connect the Sage to the PC that works, then edit Kobo eReader.conf to add:

[DeveloperSettings]
AutoUsbGadget=true

and then save it. This will bypass the USB prompt and automatically connect when you plug the Sage in. Now try on the Mac again to see if you can get farther now that it won't freeze on the USB prompt.

It might just freeze and even corrupt the database when connected to Mac. I don't think that would help.

[PlatinumWarlock]

Originally Posted by chrisridd

Instead of just restarting your Mac, try shutting it down and then booting it again. That resets more of the hardware.

No joy... BUT!!!!...

Another thing to try when you've shut down is - if the Mac has one - an SMC reset. This sometimes helps unconfuse hardware. SMC resets are only possible on some Macs, so you'll have to google for specific instructions for your Mac model.

Well, that did it. Sort of... I have a 6yo Mac, so it's not technically an SMC reset, but the SMC reset support page also mentioned (for older Macs) shutting down, unplugging for 15 seconds, replugging, and turning back on, and - for absolutely no reason I understand - that solved the problem.

[PlatinumWarlock]

Thanks, everyone, for the advice and patience - I very much appreciate it. This has been frustrating, but I'm so excited that it's working now and I can let Calibre and the Kobo play together.

[DNSB]

Good to hear your problem has been fixed even if the fix was the equivalent of dancing widdershins around an oak tree at midnight.

[Quoth]

Originally Posted by DNSB

Good to hear your problem has been fixed even if the fix was the equivalent of dancing widdershins around an oak tree at midnight.

Don't try that around a court grave or similar at Samhain.

I'm glad it's sorted.

[chrisridd]

Yay !

[macduck]

Originally Posted by JSWolf

What I want to know is why is it Apple feels it's a good idea to do whatever it takes to break MacOS?

Why do you think it's macOS fault? Or Apple? It might be faulty port/usb controller/etc. I connect Sage directly to my iMac and MBP and have zero issues... am I doing something wrong?

[JSWolf]

Originally Posted by macduck

Why do you think it's macOS fault? Or Apple? It might be faulty port/usb controller/etc. I connect Sage directly to my iMac and MBP and have zero issues... am I doing something wrong?

I'm not saying anything about hardware. But when Apple comes out with a new major version of MacOS, there are going to be a lot of breakages.

[DNSB]

Anyone else remember the Windows preview builds that blue screened when a Kindle connected and would refuse to connect a Kobo ereader? One friend of mine is still having issues with his Surface Pro X (the joy of having accountants purchasing hardware with no input from the end users).

[Sirtel]

Originally Posted by DNSB

Anyone else remember the Windows preview builds that blue screened when a Kindle connected and would refuse to connect a Kobo ereader? One friend of mine is still having issues with his Surface Pro X (the joy of having accountants purchasing hardware with no input from the end users).

I've connected both Kindles and Kobos to my Surface Pros without issues. True, not Pro X (Pro 3 and Pro 6).

[Cootey]

Originally Posted by JSWolf

I'm not saying anything about hardware. But when Apple comes out with a new major version of MacOS, there are going to be a lot of breakages.

It has to do with their corporate philosophy. Windows and PC focused businesses tend to worry about legacy compatibility. Apple is always embracing the new, so they disregard legacy compatibility. Apple abandoned the floppy disk, and the industry thought they were crazy. Same with optical drives, etc. The PC world OTOH iterates internal tech more rapidly. It truly is a difference in business models. Apple sells the whole widget, and PCs are more modular.

Apple's brazen abandonment of legacy support is a great thing when you're buying a brand new Apple computer, but a frustrating thing when you're working with an older model. I'm still cursing Tim Cook for Apple's sloppy upgrade to APFS with Maverick. They changed their OS to optimize for solid state drives instead of older hard drives, which turned my Mac mini into a paperweight. That Mac mini was only four years old at the time, but one OS upgrade crippled it. It took a lot of work to get it up and running again under the new OS, which included swapping out my hard drive to a SSD.

A lot of the recent USB–C problems people have had in these forums were only with the M1 model Macs. When Apple upgraded to the new CPU, they upgraded their USB architecture as well, which did not play nicely with Kobos.

Any rate, I believe Apple does this in part to force Mac users to upgrade their Macs. It's nice from a consumer standpoint to have a computer that will run for 7 to 10 years, but it's not great for a corporation's quarterly earnings.


Sent from my iPad using Tapatalk Pro

[JSWolf]

Originally Posted by DNSB

Anyone else remember the Windows preview builds that blue screened when a Kindle connected and would refuse to connect a Kobo ereader? One friend of mine is still having issues with his Surface Pro X (the joy of having accountants purchasing hardware with no input from the end users).

And that's not really an issue because it's not a release version. That's why it's a preview so any sort of bugs can be found and hopefully fixed before release.

[JSWolf]

Originally Posted by Cootey

It has to do with their corporate philosophy. Windows and PC focused businesses tend to worry about legacy compatibility. Apple is always embracing the new, so they disregard legacy compatibility. Apple abandoned the floppy disk, and the industry thought they were crazy. Same with optical drives, etc. The PC world OTOH iterates internal tech more rapidly. It truly is a difference in business models. Apple sells the whole widget, and PCs are more modular.

Apple's brazen abandonment of legacy support is a great thing when you're buying a brand new Apple computer, but a frustrating thing when you're working with an older model. I'm still cursing Tim Cook for Apple's sloppy upgrade to APFS with Maverick. They changed their OS to optimize for solid state drives instead of older hard drives, which turned my Mac mini into a paperweight. That Mac mini was only four years old at the time, but one OS upgrade crippled it. It took a lot of work to get it up and running again under the new OS, which included swapping out my hard drive to a SSD.

A lot of the recent USB–C problems people have had in these forums were only with the M1 model Macs. When Apple upgraded to the new CPU, they upgraded their USB architecture as well, which did not play nicely with Kobos.

Any rate, I believe Apple does this in part to force Mac users to upgrade their Macs. It's nice from a consumer standpoint to have a computer that will run for 7 to 10 years, but it's not great for a corporation's quarterly earnings.


Sent from my iPad using Tapatalk Pro

I don't see my laptop being unable to run Windows in the future.

If the M1 is so wonderful, Apple should be supporting it for as long as the computer or iPad works.

[DNSB]

Originally Posted by JSWolf

And that's not really an issue because it's not a release version. That's why it's a preview so any sort of bugs can be found and hopefully fixed before release.

Sadly, Jon, I had issues with Windows 10 Anniversary Edition back in 2016 where it showed the exposed USB content as uninitialized storage. This turned out to be due a change made by Microsoft. The thread started with the preview releases but continued on when the Anniversary Edition update showed the same issue. I do recall you happily posting in that thread multiple times.

To refresh your memory: Calibre not seeing Kobo in Windows 10 Preview builds

[JSWolf]

Originally Posted by DNSB

Sadly, Jon, I had issues with Windows 10 Anniversary Edition back in 2016 where it showed the exposed USB content as uninitialized storage. This turned out to be due a change made by Microsoft. The thread started with the preview releases but continued on when the Anniversary Edition update showed the same issue. I do recall you happily posting in that thread multiple times.

To refresh your memory: Calibre not seeing Kobo in Windows 10 Preview builds

I may not have installed the Anniversary edition until the problem was fixed. I know I didn't have the problem.

The difference here is that Microsoft made a mistake and did eventually fix it. Apple makes these as deliberate choices and makes the users figure out a solution (if a solution is possible).