Kxg50znv512g Driver
Piperion Giles
Hi Fernando. Thank you for your help. I just tried to start the installation with a new build where I integrated this new fix. I do not know, maybe I did something wrong, but as soon as I start the installation I always have the message asking me to select a driver.
There was a difference now, however, because from the driver selection windows I can see the NVMe drive that was not there before.
For some reason, however, I can not proceed with the installation. Is this a problem related to the dual boot? I remember reading it somewhere in the forum
@Fernando
A test done with OFA driver does dive less ANVIL score [14684] than with Samsung driver [15418].
I do observe to use the F7 touch to bypass driver signature checking. Can we do another way ?
@x58haze: Thank you very much for having done the benchmark comparison tests and for the screenshots, which verify, that there is no measurable performance difference between the MS in-box AHCI driver and the mod+signed AMD AHCI driver v1.3.1.277.
Conclusion: Only the stability of the driver will decide, which driver is the better choice.
Your welcome. Btw i can help you for further test if you want. Also wanted to tell you that I had to back to the Microsoft Ahci, because i was getting insane latencies on the storport.sys reported by last version of Latency Mon, over 2500us
EDIT by Fernando: Unneeded parts of the fully quoted post removed (to save space and for a better readability)
I have a general question about manual installation of various pure drivers (for example: AHCI, IME, USB, LAN) by using their *.inf files instead of full instalation (with "bloatware") from official *.exe files.
I think such installations are not registered in "Control Panel" -> "Uninstall a program" table. Now what about any updates? If I manually install new *.inf version of specific driver then do all files from previous version get removed / replaced? Or there will be any leftovers?
Hi Fernando,
I was wondering if you could help me out with my issue. I ran a clean install on an XPS 15 9560 in AHCI mode with a Samsung PM981 SSD.
When I attempted to install the Samsung NVMe driver v2.3 I received the following error message:
"Samsung NVM Express Device is not connected. Connect the device and try again."
After some searching, I found myself in this post and I believe I need to update my AHCI drivers before I can install the Samsung PM981, however, I am not sure which to choose.
The following is what my computer displayed under HardwareIDs:
I would truly appreciate any assistance. Also, after I manage to update these drivers without causing a fire, should I add them to the Group Policy to protect them from Windows Update? Thank you in advance and for this post.
Based on the guides I found on how to do a clean install on the Dell 9560 I was instructed to put the computer into AHCI mode in Bios. I attached a screenshots of where I did that and also another screenshot of the device information.
The computer has Win10 installed on it. Thank you so much for your help.
EDIT by Fernando: Unneeded part of the quoted post removed and reformatted the post structure (to save space and for a better readability)
@drmindriot:
Thanks for having posted the requested details.
Here is my comment:
1. The NVMe Controller, which is located within your Samsung NVMe SSD, cannot be managed by your on-board Intel SATA Controller, because it uses the NVMe interface and not the AHCI one.
Hey, I am just curious. Are you saying that my system specifically cannot take advantage of NVMe or I do not have it configured properly? Would it be better for me to do a fresh install with Raid On?
No, your NVMe SSD is obviously working fine with the Win10 in-box NVMe driver and there is no reason to change anything regarding your current configuration.
Since there is no disk drive connected to your on-board Intel SATA ports, the related BIOS settings regarding the SATA mode (IDE/AHCI/RAID) are irrelevant.
The Dell XPS 13 Early 2018 (9370) is the fifth-generation model of the XPS 13 line. The laptop was released in January 2018 in both a standard edition with Windows installed, as well as a Developer Edition with Ubuntu installed.
dell-command-configureAUR can be used to modify settings without having to reboot to enter UEFI menu. For example, to configure the battery to stop charging at 75% and only begin charging again when depleted to 60%:
Dell provides firmware updates via Linux Vendor Firmware Service (LVFS). Refer to Flashing BIOS from Linux#fwupd for additional information. A package is readily available at fwupd. Updates are provided for the Thunderbolt controller as well. There is an issue where the Thunderbolt version number is detected as 00.00 after re-flashing (currently being investigated).
Alternatively, for the BIOS update, you can simply copy the .exe file from the Dell Support page to any FAT32 drive (even the boot partition seems to work). Then boot into the "BIOS Flash Update" utility by hitting F12 at boot time.
In the XPS 13 the display panels (both FHD and 4K UHD) come with Content Adaptive Brightness Control (usually referred to as CABC or DBC, sometimes also as "EcoPower") enabled by default. While disabling required flashing the display firmware in previous generations, DBC can now be disabled in recent BIOS versions in the "Video" section. To test if DBS is enabled, go to this test page.
The NVMe SSD is a Toshiba KXG50ZNV256G, KXG50ZNV512G or KXG50ZNV1T02. The stock firmware version AADA4102 has severe problems when the SSD enters the lowest power state. This results in a unresponsive device (kernel complains about read-only filesystem) The problems can occur any time, but seem to have become way more common on Kernel 4.18 on battery power. Firmware Version AADA4107 seems to fix the problem. The firmware is available for Windows only but can be updated under Linux at your own risk.
As the upgrade is only possible under Windows, and as even with upgraded driver the disk may be completely undetected by the kernel because of the SSD not being responsive in the deepest sleep mode, the following kernel parameter work as a workaround, preventing the disk to enter the problematic sleep mode (see Solid state drive/NVMe):
If the system becomes unresponsive when creating any kind of large file or when data is being swapped then you may need to disable Native Command Queuing by adding the kernel parameter libata.force=noncq.
The keyboard backlight has a feature that makes it automatically turn off after a given timeout. This timeout can be adjusted by writing into /sys/class/leds/dell\:\:kbd_backlight/stop_timeout. For example,
The Bluetooth adapter sometimes becomes unavailable after waking up from suspend and can even stay deactivated and invisible after a warm reboot. End of October 2018 a kernel patch was announced by Dell. However the issue appears to remain unresolved for at least some users.
The 9370 has only three Type-C ports (and no other ports, just an audio jack). Two of these (on the left side) support Thunderbolt 3. There is no power jack. A 45 W USB Type-C charger is included in the box. Any of the three Type-C ports can be used for charging. Since the laptop has no USB-A ports, one Dell-branded Type-C to A adapter is included.
Also all three Type-C ports support DisplayPort alternate mode. It is taken care of by the firmware, so it will work even with older kernels that do not otherwise support it. To the operating system it appears as if the laptop had two DisplayPort connectors (in addition to the embedded DP that the internal screen uses). So far the following adapters have been tested. All of these will appear to the operating system as if you plugged something into one of the DP connectors.
By default, Intel Turbo mode appears to be disabled when on battery to save power. If this is not desired, TLP can be configured to re-enable Turbo on battery, however it is not always successful in doing so. A solution is to use acpid to detect AC charger disconnection and re-trigger TLP after a short delay by adding the following:
This can be resolved using throttled or intel-undervolt, both of which can be used to set a higher trip temperature. Both can also be used to undervolt to further reduce throttling, however system firmware newer than 1.12.1 appear to disable this ability.
Just like in Windows by using Dell Power Manager you can set the thermal configuration and behavior of the fans and CPU of your machine. This is done with the commands below (ensure libsmbios is installed), or alternatively via a KDE Plasma widget, plasma5-applets-plasma-pstateAUR:
For more fine-grained control of the fans, i8kutils can be used to specify the temperature at which either fan should activate. This may conflict with the BIOS fan control, which can be disabled using dell-bios-fan-control-gitAUR.
When attempting to install windows the drives were not showing up as an option. I went to the motherboards website and Intel to grab every single Intel RST VMD driver package. I put them all on a separate USB. (Download and extract them to the USB)
I downloaded that, extracted it on to the USB, and plugged it in. Ran the windows install, hit load driver, and POOF now it shows a compatible driver. I loaded the driver and now all my drives showed up.
If you have access to Windows 10 device, open start and search for feedback and open Feedback Hub app and report this issue.
In case it is urgent, then contact support:
-us/contactus
You may contact Intel's support too.
I found there is a similar issue with yours on dell website, the issue was resolved after switched to AHCI. Please check if it works on your side.
Win10 Installation: "We couldn't find any drives. To get a storage driver, click Load driver."
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.