Recently Browsing 0 members
No registered users viewing this page.
ASUS Z370/Z390 board owners are furious over the lack of Resizable BAR support [Update]
by Sayan Sen
The PCIe Resizable BAR (ReBAR) feature was first introduced by AMD last year dubbed as 'Smart Access Memory' and since then rivals Intel and Nvidia have also added support for it. Various graphics card AIBs and motherboard vendors have also been gradually rolling out firmware updates to enable the feature. ASUS motherboard owners however are annoyed because the company hasn't yet released any such BIOS to add support for ReBAR on its older high-end Z390 and Z370 chipsets even though others like MSI and Gigabyte are doing so.
In December last year, a thread was started on the ASUS Republic of Gamers (ROG) Official Forum to inquire about ReBAR support on Z390 and Z370 chipsets, and needless to say, after four months of inactivity from ASUS, they are not too happy as nothing has materialized so far. Below is a response from a seemingly loyal ASUS motherboard owner who is annoyed at the negligence from ASUS:
Here's another response from a different user:
Another poster seems more patient about the situation but would still appreciate some response:
While some seem to have given up on the company entirely, like this commenter below:
While the company hasn't officially communicated anything regarding the matter yet, in some of the responses to these posters outside of the thread, it may have hinted that some work may be going on for adding ReBAR support on the last-gen Intel Z-series chipsets. It could possibly be encountering stability issues on such boards in its current state when the ReBAR support is enabled. However, only ASUS knows the real reason for this omission.
The PCIe Resizable BAR function allows the CPU to have full access to the entire memory of the GPU, whereas typically a processor can only address 256MB for compatibility with 32-bit OSes. As a result, thanks to the entire VRAM now being available, requests from the CPU can be performed in parallel instead of sequentially, which in turn improves the speed of their dispatch. It's claimed to be especially helpful nowadays since game assets keep getting bigger.
And although the performance differentials in games today aren't very significant, it could certainly change in the future when titles are better optimized to take advantage of the PCIe ReBAR funcion. So it's easy to see why these ASUS owners are angry at the firm considering how expensive the Z-series chipset boards are, as well as 34 pages (so far) with no official response.
Source: ROG Forum
Update: An admin on the ROG Forum has responded after we posted the article. According to him, the company is working on adding the PCIe Resizable BAR support to ASUS Z390 and Z370 chipset motherboards and the expected rollout of the feature is between late April and early May.
ASUS introduces the ROG Phone 5 series with a Snapdragon 888 and a rear display
by João Carrasqueira
As had been previously revealed, ASUS' ROG division today held an online event to launch the latest iteration of its gaming smartphone lineup, the ROG Phone 5 series. Many of the devices' specs leaked ahead of the official reveal, but the presentation still contained some new information. The lineup consists of the ROG Phone 5, ROG Phone 5 Pro, and limited-edition ROG Phone 5 Ultimate.
As expected, the ROG Phone 5 series is packing a Snapdragon 888 chipset, delivering the top-tier performance you'd expect of a gaming phone, and ASUS has placed the CPU in the middle of the phone to make it easier to dissipate heat evenly. ASUS has also built plenty of performance tuning features into the Armoury Crate app, letting users adjust whether they prefer saving battery or getting more performance.
On that note, the ROG Phone 5 comes with a 6,000mAh battery, which is split into two units. This enables 65W charging for the first time, and that means the phone can go from 0% to 50% in just 15 minutes, in addition to the battery being much larger than most other phones.
The phone promises to deliver up to 144 frames per second in games, and the 6.8-inch AMOLED display from Samsung once again features a 144Hz refresh rate to go along with that, as well as a 300Hz touch sampling rate. The display also features a Delta E below 1, 1ms response times, and HDR10+ support with SDR to HDR conversion.
The rear of the phone features a pixel dot display with the ROG logo which now has two RGB light zones for extra customizability. The ROG Phone 5 Pro and Ultimate also have a customizable display on the back which lets users create imagery for different scenarios like incoming calls or gaming sessions.
For audio, ASUS has done something you'd probably not expect. In addition to the stereo speakers built into the phone, the company has brought back the headphone jack that was removed last year, complete with an ESS DAC. ASUS says this was possible thanks to the 5G modem now being fully integrated and a redesign of the PCB. ASUS has also implemented a new haptic audio feature that generates vibration to go along with certain audio effects in games.
Continuing with gaming features, ASUS has kept the ultrasonic air triggers on the side of the phone, so they're on the top when using the phone in landscape orientation. However, the ROG Phone 5 Pro and Ultimate also have two additional touch areas near the bottom of the phone for even more control options. There are also more motion control options now.
Cameras are never the focus of a gaming phone, and the ROG Phone 5 series ticks to a similar setup to last year's. The main camera uses the same sensor as the ASUS Zenfone 7 Pro from last year, and there's also an ultra-wide camera and a macro sensor.
Should you be interested in the ROG Phone 5 series, it will start at €799 for the ROG Phone 5 with 8GB of RAM and 128GB of storage; €899 for the 12GB/256GB variant; and €999 for the 16GB/256GB model. The ROG Phone 5 Pro will cost €1199 with 16GB of RAM and 512GB of storage, and the ROG Ultimate will be the world's first phone with 18GB of RAM, while keeping the same 512GB of storage for €1299. In addition to the usual black, the ROG Phone 5 will now come in a white model, and the ROG Phone 5 Ultimate will not only be exclusively available in white, but also use a matte finish for the first time.
ASUS also announced a new lineup of accessories for the phones including a new cooling fan, wireless earbuds with and without RGB lighting, an updated Kunai controller, and more.
By Usama Jawad96
Microsoft quietly fixes weird Windows 10 drive corruption bug, but only in Insider build
by Usama Jawad
Last month, it was revealed that Windows 10 contains a weird bug in which the OS throws an error message that the drive is corrupted and that you should reboot the system, when a certain location is accessed via the Command Prompt or a browser. While Microsoft appears to have quietly fixed the issue in the latest Insider Preview build 21322, it still appears to be present in other versions of Windows 10.
Bleeping Computer reports that when you run the change directory "cd" command on the Command Prompt with a specific location, Windows warns that "The file or directory is corrupted and unreadable", recommending that you reboot the machine with chkdsk to fix the drive. This happens even when users with low privileges access the NTFS volume. Microsoft had previously stated that the corruption message is inaccurate and the drive isn't actually corrupted, but another report from OSR claims that in its testing, one instance of Windows 10 failed to reboot even after repeated chkdsk.
Microsoft has fixed the issue in its latest Windows 10 Insider Preview build 21322 pushed out a few days ago, and it does not allow users to access the problematic location as can be seen below:
Naturally, we tested accessing the location on our virtual machines powered by other, older versions of Windows too. On Windows Vista, the location in question is not accessible either:
However, when we tried to access the location via Command Prompt on an old machine with Windows 10 Pro version 1803 - which is an older version of the operating system that is no longer supported. True to reports, there is an error message that the "file or directory is corrupted and unreadable", and the system recommends that you close all apps, restart the PC, and repair drive errors to fix the issue:
In our case, Windows 10 fortunately did manage to reboot with chkdsk and did not get stuck in a loop. We expect other versions of Windows 10 prior to Insider build 21322 to behave in the same way, barring any serious anomalies:
It's a six-year-old PC! It is important to note that other vendors and companies are trying to block access to the problematic location from their end. Mozilla Firefox 85.0.1 has a check which disables access to locations with the ":$" symbol, while OSR has released an unofficial patch which disallows access to the path. That said, it is rather strange that Microsoft is not pushing out a hotfix for older versions of Windows 10. We have seen similar issues with other operating systems such as iOS in the past, and while they may not be dangerous in most cases, it is always worth fixing these issues to prevent viral pranks that can be a nuisance for PC owners who are not tech-savvy.
By Usama Jawad96
The PlayStation Network is down for certain games
by Usama Jawad
Microsoft's Xbox Live service had an outage yesterday, resulting in gamers facing problems in connecting to it. This caused failed purchases, inability to sign in for some users, issues in launching certain games, and unavailability of xCloud gaming. While Microsoft was able to resolve the problem in six hours, it did admit that the fix took longer than anticipated to apply.
Today, it's the PlayStation Network's turn which appears to be down for several games.
According to Sony's dedicated network service status page, the PlayStation Network is facing issues in the "gaming and social" category. This affects the PlayStation Vita, 3, 4, and 5. The company cautions that:
It's unclear exactly how widespread the problem is, but the status appears to be the same across most regions including the US, UK, and Canada. Engadget reports that while some games like Fortnite and Fall Guys work just fine, players are having issues connecting to others such as Call of Duty: Warzone, Minecraft, Destruction AllStars, and Don't Starve Together.
The issue was officially confirmed by Sony on 6:33PM ET, but earlier reports point to it appearing on 1PM ET, which essentially means that it's been almost 12 hours since the partial outage began. It's currently unclear when a fix will be rolled out, but you can keep an eye on the network service status page for updates in the meantime.
By Usama Jawad96
'Hey Google' on Wear OS has been broken for months, but a fix is finally in the works
by Usama Jawad
Wear OS is Google's platform for wearables, and actually only one of the two which supports Google Assistant functionality. The other one being Fitbit, which Google now owns too. While many claim that the firm neglects Wear OS, the platform does receive updates from time to time. However, a new report now claims that the "Hey Google" functionality has been broken on the operating system for several months, with Google only now starting to work on a fix.
9to5Google has cited multiple Reddit and Google Issue Tracker threads which indicate that the "Hey Google" and "OK Google" functionalities are broken on Wear OS. These voice commands are used to immediately trigger Google Assistant and enable ease of access rather than having to physically interact with the wearable.
To be fair, Google Assistant still works but now users have to manually fidget with their device's physical or on-screen controls in order to immediately trigger it. This arguably defeats much of the purpose of having a voice-controlled assistant on your smartwatch.
The good piece of news is that Google has finally acknowledged the flaw and confirmed that it is working on a fix. In a statement to The Verge, the company indicated that it is "aware of the issues some users have been encountering" and will assist partners and OEMs in fixing the problem. It remains to be seen how long Google will take to resolve the issue, but having a major bug on Wear OS for months and not acknowledging it until widespread backlash certainly does not instill confidence in the operating system.