smb big sur

I'm trying to debug a kernel extension on Big Sur (xnu-7195.0.0.141.5). In the past, I've successfully used kdp-remote from lldb to attach to the crashed kernel and debug it. However, this doesn't seem to be working on Big Sur. The serial console of the crashed machine shows: ethernet MAC address: 00:0c:29:43:dd:b5 ip address: 192.168.1.250 Waiting for remote debugger connection. as expected, but there's no response to packets sent to that address by lldb. Is this working for anyone else? Thanks, Simon

my MacBook is on 10.15.6 beta, I already tried before but it froze and I had no choice so I reset and restart my Mac from high Sierra and now I'm on 10.15.6 again, but this time, it doesn't show Big Sur update. help!!

Still cannot connect an external monitor after upgrading to Big Sur using a USB-C to DisplayPort cable. I've combed the web far and wide but have seen no solutions to this specific issue on Big Sur 11.2.3. My job is very hard to do without an external monitor 😅

I've tried to install Big Sur, in a separate volume APFS, but the Mac go in boot loop for entire night. I've tried many times, but it's impossible to solve. Then I've create a bootable usb with Big Sur, by terminal, and the problem to install the OS is, permission denied. In the last, I've installed a new copy of Catalina in a new Volume, and I've tried to update to Big Sir by beta profile procedure. And the Mac go in boot loop again . Please help !!! 😭

After installing Big Sur Beta 1, a Time Machine dialog popped up that I thought I ignored. Later I see that it backed up my iMac onto a volume called TimeMachine Backup (which is not the name of my main TM Backup so I felt this was fine). Today I actually started to look at what was happening. Big Sur renamed my TM Volume from the previous name to this TimeMachine Backup and has intermingled it's backup files with my previous Catalina ones. Quick note about my setup. I'm running Catalina on a stock SSD in the iMac. I have a USB enclosure with 4 HDs in it. One of the 4 drives is dedicated to TM Backups. I partitioned that drive to install Big Sur onto. So I run Big Sur from a 100GB Partition on this 4TB drive. Is there any way to: Break this intermingling or do I just erase the backup and have it start again from Catalina? Is TM smart enough to know which files belong to which backup OS? I booted into Catalina today and see that it thinks

I have just updated my MBP from Big Sur Beta 2 to Big Sur Beta 3 (11.0), but when I try to log in, the screen goes black a couple of seconds, and I am presented with another login screen, where I have to type in my username and password. When I do that, the screen goes black again for a couple of seconds, and the log in screen reappears. I have tried to run in recovery mode, but that just gives a black screen after login, and never gets any further. I have tried to reinstall Big Sur Beta 3, but with the same result. I have reset NVRAM with same result. I have run out of things to try and really need some help

I have Big Sure Dev Beta 1 installed on an external USB-C SSD drive. Mac is a brand new 2018 Mac mini (most recent Intel model). Beta 1 works fine (well, for the purpose of beta testing anyway Big Sur Dev Beta #2 is out now. Software Update GUI Pane and CLI both see the new update, but I'm unable to downed/install it. Here is the error I see from running 'softwareupdate -d -a' from Terminal: 'Failed to download & prepare update: Error Domain=SUMacControllerError Code=7722 [SUMacControllerErrorPreflightPrerequisiteCheckFailed=7722] Failed to perform PreflightPrerequisite operation: com.apple.MobileSoftwareUpdate.preflight.error(Preflight):MSUPreflightErrorTargetIsNotSnapshotBooted(6) | The volume can not be used because it is not snapshot booted.'

Hi, I recently updated to the Big Sur beta and noticed the control center isn't in the top right corner like in the demos, pictures, etc. Instead there is a spotlight icon that won't go away even when I turn it off in the menu bar settings. Is anyone else getting this error and if so has anyone resolved it? I understand this is a beta, but this doesn't seem to be an error that is prevalent in the other systems that upgraded. Thanks.

The system call ntp_adjtime sets and returns various attributes associated with the NTP phase locked loop in the Darwin kernel via a struct timex argument. The frequency of the the loop is passed back and forward in this struct as a signed fractional number. In Big Sur, instead of returning a negative number for the frequency when required, ntp_adjtime returns the unsigned representation of the number - i.e. the value is always positive and can be 'off' by 65536. I have submitted FB8561779, along with a simple test case demonstrating the problem. I hope it will be fixed soon.

OS11 Big Sur Updated System Extensions Blocked. I click allow and check the items (have tried individually and all at once) it then ask to restart but all of them show back up as needed to allow in system security preferences.

Everything was fine till Apple dumped this half baked Big Sur on me. Now I cannot Print! Apple is playing Ostrich here by pretending not to see this problem even though users have been complaining. Do something Apple!

Hi! I just updated my Macbook Pro 2017(with Touchbar) to Big Sur 11.3 and I cannot adjust the brightness of my screen. The slider in the touchbar moves but does nothing, and the slider in the control panel is grayed out. Please help!

Hi I'm developing USB network driver with NetworkingDriverKit. develop environment MacOS 10.15.4 XCode 11.6 My USB Networking Driver works fine in MacOS 10.15. But in MacOS 11(Big Sur) GetDataLength method in IOUserNetworkPacket class always failed with kIOReturnBadArgument . IOUserNetworkPacket get from txSubmissionQueue. GetDataLength Document link : https://developer.apple.com/documentation/networkingdriverkit/iousernetworkpacket/3294975-getdatalength And my code similar below IOUserNetworkPacket *packet; uint32_t packetLength = 0; ret = txSubmissionQueue->DequeuePacket(&packet);- if success ret = packet->GetDataLength(&packetLength); // ret always kIOReturnBadArgument in Big Sur Does anyone have any ideas on how I can solve this?

I've got a WD My Passport 1TB SSD external drive. I also have 2 MacBook Airs, one mid 2013 and one less than a month old. I used the hard drive to transition from the old one to the new one. Both worked great. I had the old one enrolled in the beta program so of course after moving to the new one it was too. They both upgraded to Big Sur one night. Long story short one of the programs I use regularly wasn't ready for Big Sur so I attempted to go back to Catalina. I plugged in the hard drive and it just sat there steadily flashing the light. No access in Finder. I opened DiskUtility and there it was, greyed out with no access.. No mount, no first aid, nothing. So I opened Safari and did some looking. Meanwhile, I cleared out the old MacBook and loaded a new version of Catalina. Turns out, when I force quit fsckhfs, the drive is accessible and I can access it. While it passes all tests on WD's utility app, when I try to run first aid it fails after about 4 hours. Though I can

I recently installed the Big Sur beta on my 2019 16 Macbook Pro. I tried to run Parallels, only to be given a message saying to restart to complete the installation. The trouble is, whether I choose to restart or quit Parallels, the application hangs. If I then restart and try to run it again, I get the same message. I looked at the logs, and it appears that it is failing when trying to load one of its kernel extensions, and then assuming that a restart is needed to enable them. It tries to issue the following command: /usr/bin/kmutil load -p /Applications/Parallels Desktop.app/Contents/Library/Extensions/10.9/prl_vnic.kext -r /Applications/Parallels Desktop.app/Contents/Library/Extensions/10.9 which fails with the following error: Error: Error Domain=KMErrorDomain Code=1 Kernel request failed: (libkern/kext) kext (kmod) start/stop routine failed UserInfo={NSLocalizedDescription=Kernel request failed: (libkern/kext) kext (kmod) start/stop routine failed} Does anyone else have this problem? I