Jump to content

Search the Community

Showing results for tags 'm1 mac'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Site Related
    • News & Updates
    • Site / Forum Feedback
    • Member Introduction
  • News
    • General News
    • FileSharing News
    • Mobile News
    • Software News
    • Security & Privacy News
    • Technology News
  • Downloads
    • nsane.down
  • General Discussions & Support
    • Filesharing Chat
    • Security & Privacy Center
    • Software Chat
    • Mobile Mania
    • Technology Talk
    • Entertainment Exchange
    • Guides & Tutorials
  • Off-Topic Chat
    • The Chat Bar
    • Jokes & Funny Stuff
    • Polling Station

Categories

  • Drivers
  • Filesharing
    • BitTorrent
    • eDonkey & Direct Connect (DC)
    • NewsReaders (Usenet)
    • Other P2P Clients & Tools
  • Internet
    • Download Managers & FTP Clients
    • Messengers
    • Web Browsers
    • Other Internet Tools
  • Multimedia
    • Codecs & Converters
    • Image Viewers & Editors
    • Media Players
    • Other Multimedia Software
  • Security
    • Anti-Malware
    • Firewalls
    • Other Security Tools
  • System
    • Benchmarking & System Info
    • Customization
    • Defrag Tools
    • Disc & Registry Cleaners
    • Management Suites
    • Other System Tools
  • Other Apps
    • Burning & Imaging
    • Document Viewers & Editors
    • File Managers & Archivers
    • Miscellaneous Applications
  • Linux Distributions

Categories

  • General News
  • File Sharing News
  • Mobile News
  • Software News
  • Security & Privacy News
  • Technology News

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 4 results

  1. M1 Mac Users Report Excessive SSD Wear Over the past week, some M1 Mac users have been reporting alarming SSD health readings, suggesting that these devices are writing extraordinary amounts of data to their drives (via iMore). Across Twitter and the MacRumors forums, users are reporting that ‌M1‌ Macs are experiencing extremely high drive writes over a short space of time. In what appear to be the most severe cases, ‌M1‌ Macs are said to be consuming as much as 10 to 13 percent of the maximum warrantable total bytes written (TBW) value of its SSD. Flash memory on solid-state drives, such as those used in Macs, can only be written to a certain number of times before they become unstable. Software ensures that load is spread evenly across the drive's memory cells, but there is a point when the drive has been written to so many times that it can no longer reliably hold data. So while SSD wear is normal, expected behavior, drives should not be exhausting their ability to hold data as quickly as some ‌M1‌ Macs seem to be. One user showed that their ‌M1‌ Mac had already consumed one percent of its SSD after just two months, while another ‌M1‌ Mac with a 2TB SSD had already consumed three percent. The total data units written for these machines is running into many terabytes, when they would normally be expected to be considerably lower. 16GB ‌M1‌ MBP, 2TB SSD, 2 months in. pic.twitter.com/SaSmieaT1s — David (@david_rysk) February 15, 2021 The user with three percent usage speculated that, were his machine a 256GB model, it could have used as much as 30 percent to date, and have reached maximum TBW in around two years. An SSD can continue to function once its TBW limit has been reached, but there is no knowing how long it will last past this point. It is not known how widespread the TBW issue is, but reports of strange SSD behavior are also now emerging from users with Intel-based Macs, suggesting that the TBW issue may not be exclusive to ‌M1‌ Macs. The reported wear is so extreme on some ‌M1‌ Macs that it suggests the problem is due to a bug rather than the expected behavior of the ‌M1‌ chip, but it is unclear if the problem pertains to erroneous readings or macOS genuinely writing vast amounts of data to the drive. Drive monitoring tools are sometimes unreliable and it is likely that the issue can be fixed via an update to macOS Big Sur. Source: M1 Mac Users Report Excessive SSD Wear
  2. Recently I was tasked with making some videos of running CrossOver on the new Apple M1 (Apple Silicon) MacBook. What is new and fascinating about this new toy is that it is the 3rd time Apple has switched to a new CPU architecture. A little history lesson for you. Originally back in the 80's the Macintosh used a Motorola 68000 chip. They chugged happily along on these until 1994 when Apple wanted to make the jump to the IBM PowerPC chip. This chip was interesting because it was the first mainstream RISC based CPU. It was also during this timeframe that the largest macOS release X came out. macOS X was largely based on the NeXT core that Steve Jobs and Co. invented while he was away from Apple doing his own thing. Then in 2006 Apple did the what many thought impossible and switched again to the Intel X86 chip. At this time CrossOver was also first released for the Mac. Each time Apple made a switch, they also included an emulation layer so old software would still work. Then during the Intel switch, it was named Rosetta. Now here we are in 2020 and Apple is at it again. This time for the first time, they are making their own chips. Granted, they are based on the established Arm core. Apple has put plenty of their own special sauce into the mixture. Once again, we have an emulation layer included: Rosetta 2. This is how CrossOver is still able to work. Since Wine requires X86 instructions to be able to translate the Windows software over. Now we come to my videos. In Jeremy White's blog post, I ran Team Fortress 2. This was not the best choice as it even on native Mac and Linux it does not run very well. There are legacy Wine bugs that prevent it from reaching the frame rate you would get on Windows. However, it at least ran and did show that CrossOver was able to work on the new M1. My new video, which you can watch right here: In this video I ran 3 different Windows games. Rocket League, Dead Cells, and Untitled Goose Game. The first thing I noticed is that since these 3 games work best with a controller, in Rosetta 2 controllers do not work. This seems to be a bug in Rosetta 2 itself, since I was able to verify that by installing RetroArch and trying to get controllers to work, no joy there I'm afraid. I posted these to my own LaXDragon channel. Free free to like and subscribe to it. I'll be posting more videos in the near future as long as they don't interfere with my other duties too much. 😎 About Jeremy Newman Newman has been the Systems Administrator and Webmaster for CodeWeavers since 2000. He is a Swiss Army Knife of I.T and keeps the hamsters running in all of our Servers. Source
  3. Linux creator Linus Torvalds wants one of Apple’s first machines using in-house silicon—but running his open-source OS. In a response to a Q&A in which a user asked Torvalds what he thought of Apple’s new laptop, Torvalds wrote: Torvalds goes on to point out how “Apple may run Linux in their cloud, but their laptops don’t”. Many people have been waiting for an ARM-based laptop to run Linux for a while now. Torvalds is a member of that group but says he doesn’t have the time to get Linux working on an M1 MacBook. Apple’s new M1 Macs have been receiving glowing reviews for performance and battery life. The praise has been hard to ignore, even for those who’ve historically avoided Macs. While it’d be a surprise to see Apple change course on its attitude towards Linux anytime soon—Microsoft, on the other hand, has been increasingly supportive. Microsoft added a full Linux kernel to Windows 10 with version two of Windows Subsystem for Linux (WSL) earlier this year. During BUILD, Microsoft pledged to improve WSL with full GUI app support and GPU hardware acceleration. Linux 5.10 is due around Christmas and will come with a stocking full of gifts including support for new hardware like AMD Zen 3 and Intel Rocket Lake, Amazon Web Services’ Nitro Enclaves isolation technology, compatibility with the Nintendo Switch’s controller, file system improvements, a whole load of bug fixes, and the removal of a relic from Linux’s early days. Source
  4. Some M1 Mac users reporting screensaver takeover bug Including me Photo by Vjeran Pavic / The Verge I picked up a new MacBook Air with Apple’s M1 chip, and I’ve absolutely loved it so far. It’s really speedy and the battery is fantastic. But I’ve been dealing with one nagging issue. Every once in a while, for reasons that I haven’t been able to figure out, a screensaver will suddenly take over the entire computer — despite the fact that I never use a screensaver. And frustratingly, the screensaver renders my laptop inoperable until I completely close the screen and reopen it. It seems I’m not the only one seeing this bug, according to this MacRumors article. Others have shared similar issues with M1-equipped MacBook Airs, Pros, and Minis on MacRumors’ forums, Reddit (in a few threads), and Apple’s support forums. And one user on MacRumors said they’ve seen the bug on their 16-inch MacBook Pro, which has an Intel chip, so perhaps this is a problem with macOS Big Sur. Here’s a video of the bug, shared by MacRumors forum member dawideksl: Many people reporting the issue in this Reddit thread say they have multiple accounts on the same computer. And for what it’s worth, I’ve set up two accounts on my MacBook Air. One user on Apple’s support forums disabled Fast User Switching and said they weren’t seeing the screensaver, so perhaps that’s a workaround until Apple addresses the bug. Apple didn’t immediately reply to a request for comment. Some M1 Mac users reporting screensaver takeover bug
×
×
  • Create New...