My company provides a driver that utilizes a codeless kext to prevent the system IOHID driver from taking over any device we support. However, after uninstalling our software, we'd like for the system driver to take over the device again. In previous versions of macOS, after uninstalling our kext, re-enumerating the device would get it to load the default system driver. However in Big Sur that is not working any longer, and the system doesn't take control of the device until after the system has been rebooted. Is there any way to get this to happen without requiring a reboot in Big Sur?
Search results for
smb big sur
11,741 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hi, I know the font smoothing option has been removed in Big Sur. Is there a console command one can enter to disable font smoothing? The font on title bars and in some app look very thick, with the letters almost touching. My laptop is a Macbook Air 7,2 - 13 2017 model. Any help is appreciated. Thanks! Louis
The problem seems to be related to Big Sur 11.3 and Big Sur 11.4. Not to specific Xcode version (Xcode 12.4 got about the same results that 12.5). I do some measures for 2 applications in debug on Big Sur 11.1 and Big Sur 11.4. Here the launch time results: App1 - Big Sur 11.1 = 0m21s - Big Sur 11.4 = 1m20s App2 - Big Sur 11.1 = 0m31s - Big Sur 11.4 = 5m08s Conclusion: Debugging Application on 11.4 is between 4 to 10 time slower than 11.1. Note App2 have nearly 100 dylib to load while App1 have only 30.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Ok, so installed Big Sur a day or so ago and haven't had any issues, awesome. I downloaded Xcode 12 beta and installed it without issues. I needed to restart, got to the login screen, entered my credentials and now I'm stuck on the login progress screen, which seems to be stuck at 100% and not going any where I've tried hard power cycling the laptop without any success ... Any suggestions? (ie safe mode)
I have a Mac catalyst app that has a root view controller of a UIDocumentBrowserViewController. When a document is selected, the editor view controller is presented modally (in fullscreen mode). This worked fine on iOS 14, and macOS Catalina, but when I run it on Big Sur, the editor VC will appear for a second, and then disappear, and the UIDocumentBrowserViewController gets shown again. (Not sure if the editor is being dismissed, or if another UIDocumentBrowserViewController is being shown on top.)
Hi, macOS Big Sur works for me perfectly until I upgraded iCloud to 2TB. While syncing, Finder crashes and cannot be reopened again. Open Finder will result in -1 error. Trying safe mode, closed WiFi (to prevent syncing) and the result is the same. Since I cannot access Finder, I can't redownload the beta (downloading to a folder will hung). What shall I do?
I'm running the Big Sur beta on a small partition, and after downloading the beta 2 update today, my laptop suffered a kernel panic and restarted. After restarting I tried continuing with the update, but I didn't have enough free space in the partition because of the existing download of the beta. Does anyone know how I can delete that and redownload it, or point the updater to those existing files? Thanks!
Since sudo mount -uw / no longer works on Big Sur, I am no longer able to modify the charging sound on my MacBook Pro. Does anyone know how else I could do this?
FWIW here are some screenshots that demonstrate how much the usability has deteriorated in Big Sur. Before Big Sur: imgur.com/90mR8Mm Big Sur: imgur.com/JIMF29h Any ideas on how to change this back to being usable on Big Sur..? Cheers, Jan
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I'm trying to set up a Swift Package that target's macOS Big Sur. From the documentation, it looks like v11 should be the new property. https://developer.apple.com/documentation/swift_packages/supportedplatform/macosversion/3632902-v11 platforms: [.macOS(.v11)], But it crashes with the following error. error: manifest parse error(s): Package.swift:9:17: error: reference to member 'v11' cannot be resolved without a contextual type tttt.macOS(.v11) Oddly, an undocumented v10_16 works! platforms: [.macOS(.v10_16)], Looking at the open source code, it appears both values should work. https://github.com/apple/swift-package-manager/blob/6cfe2de63e53dd9cb75e7bf910277e699d9383a2/Sources/PackageDescription/SupportedPlatforms.swift#L212-L223 Is there a bug in this release of Xcode's Swift tool chain? What platform property should I be using to target Big Sur? Xcode Version 12.0 beta (12A6159) $ swift --version Apple Swift version 5.3 (swiftlang-1200.0.16.9 clang-1200.0.22.5) Target:
I have the same problem as hundreds of people: after updating to Big Sur, my MacBook is overheating and the battery is empty in no time at all. Never had this problem before.
I’m on a MacBook Pro 13inch early 2015 and I just updated to macOS Big Sur and i can’t connect to internet, when I try to connect to a website on safari I have an error saying that it can’t connect with a secure connection, and when I go to system preference/software update I get an ssl error and a secure connection cannot be made
Hi I just did the update to Big Sur on my Mac and now all my applications won’t work because of no internet connection but I opened Goggle Crome and that works so there is internet connection what do I do to fix that?
I had the same problem, also Ubuntu 20.04 and Samba 4.11.6 My backup machine is on btrfs and not on zfs, but ScruffyDans solution put me on the right track I think (still testing). I modified my smb.conf to include as global options: fruit:nfs_aces = no inherit permissions = yes I got it from here: https://stackoverflow.com/questions/58496277/samba-4-10-server-config-using-module-vfs-fruit-changes-file-creation-mask-fo Changing these settings allowed my MacBook Pro with Big Sur to connect to a network share, create a new .sparsebundle and it is now backing up to it. I can also confirm that the container created in the .sparsebundle is an APFS container! Before changing these settings it would just throw the error as described in the OP. I'm not sure why this seems to solve the problem....anyone?
Topic:
App & System Services
SubTopic:
Core OS
Tags:
Are there any plans to fix the slow unpacking speeds using Unrar? My 100MB test file takes 4 seconds when NFS is enabled. It takes 90 seconds when Samba is enabled.This all started after Yosemite.By the way, System Preferences/Login Items is broken with NFS like it was for Samba prior to El Capitan's release. You can map different folders (Apples, Oranges) but after reboot, they change to Apples and Apples in Login items. Apple, please fix this.