top of page

Market Research Group

Public·36 members
Yeremey Fomin
Yeremey Fomin


Before we proceed, keep in mind as well that I ran all the tests on the software available for the Flow Z13 as of mid-March 2022 (BIOS 308, Nvidia 511.79 drivers, Armory Crate). Some aspects might change with later updates.


Once Asus figures out the drivers, I still expect the Intel configuration to have an advantage of up to 15% in games at FHD+ resolution, and lower at QHD, based on our previous tests of similar AMD 6000/Intel 12th-gen implementations with the same kind of RAM and GPU. Plus, the Z13 has an advantage in cooling.

i have an asus ux501vw, i tried to install nvidia driver few times, but everytime i lost my desktop and system dead! and i started again and reinstall the freezed in booting section and do something like refreshing a web page every second! and i tried to log into tty by pressing alt+f[1-7] but is was so messy! anyway..i reinstalled be loved archlinux for i think 7-8 times! but this time i want to install NVIDIA correctly by your help

The most well supported wifi adapter's are usually older, (and cheaper), with more reliable drivers. Old N based adapters are slower, but they are usually rock solid if you go with say an Atheros ath9k based adapter. The Atheros ath9k driver has been around for a long time, has good in kernel support, and is relatively fast, (but definitely far slower than very recent models), and usually very reliable.

Unfortunately, newer is not necessarily better when it comes to Linux hardware support, as you've now discovered. New Wifi drivers even from well respected companies like Intel have been prone to many issues and breakages with the newest models. Frankly your Mediatek adapter has proved to be a steaming pile of dung, and my feeling is the only reason Asus included it in their recent offerings was because of supply chain issues brought on by Covid.

I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing.When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again.On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

---ProblemType: Bug.proc.driver.nvidia.gpus.0000.01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/0000:01:00.0'.proc.driver.nvidia.registry: Binary: "".proc.driver.nvidia.suspend: suspend hibernate resume.proc.driver.nvidia.suspend_depth: default modeset uvm.proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version:ApportVersion: 2.20.11-0ubuntu27.3Architecture: amd64CasperMD5CheckResult: skipCompositorRunning: NoneDistUpgraded: Fresh installDistroCodename: focalDistroRelease: Ubuntu 20.04DistroVariant: ubuntuGraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1c5d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1c5d]InstallationDate: Installed on 2020-06-19 (20 days ago)InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)MachineType: ASUSTeK COMPUTER INC. GL552VWNonfreeKernelModules: nvidia_modeset nvidiaPackage: xserver-xorg-video-intel 2:2.99.917+git20200226-1PackageArchitecture: amd64ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bashProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=cf568657-da1a-41b6-8375-2d74050df2ce ro quiet splash i915.enable_rc6=0 vt.handoff=7ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44Tags: focal ubuntu third-party-packages ubuntuUname: Linux 5.4.0-40-generic x86_64UpgradeStatus: No upgrade log present (probably fresh install)UserGroups: N/A_MarkForUpload: 04/25/2019dmi.bios.vendor: American Megatrends Inc.dmi.bios.version: GL552VW.304dmi.board.asset.tag: GL552VWdmi.board.vendor: ASUSTeK COMPUTER INC.dmi.board.version: 1.0dmi.chassis.asset.tag: ATN12345678901234567dmi.chassis.type: 10dmi.chassis.vendor: ASUSTeK COMPUTER INC.dmi.chassis.version: 1.0dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.304:bd04/25/ GL552VWdmi.product.sku: ASUS-NotebookSKUdmi.product.version: 1.0dmi.sys.vendor: ASUSTeK COMPUTER INC.version.compiz: compiz N/Aversion.libdrm2: libdrm2 2.4.102+git2006181830.f44908oibaffversion.libgl1-mesa-dri: libgl1-mesa-dri 20.2git2007090730.02a578oibaffversion.libgl1-mesa-glx: libgl1-mesa-glx N/Aversion.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/Aversion.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/Aversion.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

Ok... Problem is solved by ... puling out POWER from monitor! It is weird but for some reason when i unplugged monitor from power and pulled it again it start showing my screen. It is weird but to be honest I've tried sooooo many things before and nothing helped... I've changed drivers few times... so many restarts... I've even changed hdmi cabel.

On supported releases, the Vulkan loader and libraries are installed automatically and you do not need to do anything to enable support in the drivers. CentOS and Red Hat Enterprise Linux 6 does not have Vulkan.

Here is a rundown of Nvidia supported drivers and options split by distribution. Basically, CentOS/RHEL will always get a Long Lived branch release if possible, Fedora always a Short Lived branch release, and unreleased distributions will always get a Beta driver.

The limitations are the same as provided by the Nvidia driver, this means that if you are running it on an Optimus laptop, the Intel card can never power off. Which means higher power consumption, unfortunately. If you have an Optimus laptop and absolutely need the proprietary drivers, my suggestion is still to disable Optimus in the Bios.

As you can see, this system has akmod enabled kernel modules and libraries for running 32 bit applications. The amount of data to download for the drivers is really small compared to packages that contain CUDA libraries and tools.

In this example we have 2 video cards with one monitor each, so we enabled SLI, Base Mosaic to have multi monitor support on SLI and make a layout with the second GPU monitor on the right of the first one. Also, we fix the DPI to 9696, which is the hardcoded default in Gnome and in Open Source drivers.

As you can see, there are no components providing OpenGL or DDX drivers installed on the system. This will not use any X (or Wayland) configuration compared to what has been installed by default on your system.

Hi, are there any plans to support beta driver soon?I tried to setup releasever=rawhide but your repo does not seem to support it, even though you said rawhide would have beta drivers. Am I missing something?

total 20drwxr-xr-x. 2 root root 4096 mar 21 13:36 bbswitchdrwxr-xr-x. 10 root root 4096 mar 21 13:20 driversdrwxr-xr-x. 13 root root 4096 mar 21 13:20 fsdrwxr-xr-x. 13 root root 4096 mar 21 13:20 netdrwxr-xr-x. 2 root root 4096 mar 21 15:56 nvidia

It seems to be related to this: -x11-drv-nvidia.git/commit/?id=de92ef6e74aa29ca8648622692670d3e893b9061So now the RPMFusion repository has a higher epocj for the Nvidia modules. Will look into it, but I suggest that you just remove my repository and use the RPMFusion provided drivers if you need to use RPMFusion on your system.

Hi there, I know that this is not your problem but I would like to install and manage my nvidia drivers through the negativo repo. But I have installed them with this guide through nvidia:

I just updated my f26 machine to the 387.22 nvidia drivers, and they produce errors / soft+hard lockups / udev crashes on my system. Any idea what could cause that? Downgrading the drivers to 384.90 again resolves the issue.Comparing logs between booting with old and new drivers, the only difference are those log entries concerning lockups and crashes:

After more testing, have been unable to get nvidia drivers working at all now with wayland or xorg. Even removed gdm, mutter, wayland and all nvidia packages regardless of how I do it. Even with the linked mutter. Nothing at all.


Welcome to the group! You can connect with other members, ge...
Group Page: Groups_SingleGroup
bottom of page