Bug 429891

Summary: KDE neon does not see this gen4 NVME ssd
Product: [KDE Neon] neon Reporter: Deckweiss75
Component: Live/Install imagesAssignee: Neon Bugs <neon-bugs-null>
Status: RESOLVED WAITINGFORINFO    
Severity: normal CC: jr, neon-bugs-null, sitter
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Deckweiss75 2020-12-01 13:52:44 UTC 
SUMMARY
I wanted to install kde neon on my new asus vivobook flip 14 tm420. I instantly opened the device and installed a Patriot Viper VP4100 instead of the cheapo kingston one that it came with.

Downloaded the most recent user image 20201126-1349. But it did not detect the nvme ssd. Not in lsblk and not when I tried gparted.

I've searched the web and tried it with the nvme_load=YES kernel parameter, to no avail.

Then I checked: Bios detects the nvme. Debian and Kubuntu detect the nvme. Just not KDE neon.

See literal screenshots: https://imgur.com/a/ILk4jG3


STEPS TO REPRODUCE
1. Have the particular hardware (laptop: asus vivobook flip 14 tm420) (nvme ssd: Patriot Viper VP4100)
2. Boot kde neon 20201126-1349 live install user image.
3. Do lsblk or install and open gparted or attempt to install kde neon

OBSERVED RESULT
nvme ssd not detected at all in KDE neon


EXPECTED RESULT
detect the nvme ssd so the os can be installed on it


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Carlos De Maine 2025-09-20 09:35:26 UTC 
Thank you for your bug report! 
However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since  before 01/01/2025. 
Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's.
Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.
Thanks for understanding!