Well as long you SSD is not powered ON , see log it stuckt in D3 nothing can see it.
And even when some build saw it , like you see once you touched it with partition manager is gone.
From the dmesg you now posted you whole PCI bus times out.
Can you please attach lspci output too ?
I got here SSD’s connected to PCIE , M2 slot , M2 ones into PCIE card … and nothing
has any problem with these. However all my SSD’s/NVme’s are EVOs/EVOs PRO.
@bero got such strange issue on one of his boxes too , but these are kernel bugs.
There aare brunch quirck for particular disk in the kernel , just to fix such issues.
As example on this laptop:
[ 2.853586] ata1.00: supports DRM functions and may not be fully accessible
[ 2.854762] ata1.00: ATA-11: Samsung SSD 860 EVO 250GB, RVT01B6Q, max UDMA/133
Same way these quircks will disable or workaround other things are wrong implemented,
make for windows or simple bugs in the firmware.
That means just : these kernel have different versions , are patched , have different configuration.
But it still remains an kernel bug
First need be detected or detected and fully functional by the kernel …
Also can you boot with nvme_core.default_ps_max_latency_us=0 please ?
( from the USB stick )
Yes, card games have been included in ISO live mode only.
From D27’s suggestion :
can you also post me a ‘sudo nvme list’ , output , please ?
Just to see you are not alone just see ubuntu generic bug about exactly that:
last thing I need is output of:
nvme id-ctrl /dev/nvme0
@abucodonosor @D27 Should we have a bug report for this?
@D27 could you file a bug report for this issue? It is always best if someone that has the issue files the bug report.
Also Beta ISO has been made so maybe it’s time for a new thread? If so I wonder if issues would not be easier to track if each issue has it’s own thread. In other words a general thread for people to report their OMLx 4.0 Beta testing but any issues needing attention we start a new thread for that specific issue?
To me it got very confusing trying to keep up with specific issues in one long thread. But I’m a Linux Monkey.
you can start new beta thread but I need some infos from @D27
to be able to workaround this issue.
I just made this a separate thread as it seems important enough. Hope this makes this issue easier to follow.
Post-edit: Please feel free to edit title as you see fit.
OT but need to say: This is more or less in response to discussion on IRC about devs and issues in forum. I’m hoping if we enforce the “One issue, one thread” concept this will make it easier both on devs to follow an issue and for users to find an issue.
Post-edit: And I have been guilty of doing it the other way myself but we/me need to do better.
Right, just I was waiting for Beta release to be announced, or at least Beta candidate
You did it!
Here is what you requested :
1 - lspci :
lspci-OMLx4.txt (2,5 Ko)
2 - nvme list
nvme-list-OMLx4.txt (163 Octets)
From french => No command available
3 - nvme id_ctrl /dev/nvme0
nvme-id-ctrl-OMLx4.txt (183 Octets)
From french => No command available
4 - Then I booted with : nvme_core_default_…us=0
and here is the dmesg (will be send later, lost it at the moment)
5 - Then here is KDE partition program with the SSD => OK with option just above inserted in grub2
6 - And finally Calamares Where the SSD appears now
Nice … and not nice since it seems your SSD need an NVME_QUIRK_NO_APST.
It seems nvme-cli gone from our repos … but I badly need that output of
nvme id_ctrl /dev/nvme0 , to be able adding that to the kernel.
So if is possible for you can you run that command from any other Distribution
and post me the output ?
( PS: we’ll re-add nvmi-cli soon )
Here the dmesg missing above
dmesg-latency_us=0.txt (92,2 Ko)
Concerning command nvme :
Doesn’t work either with Fedora
=> Works with MINT installing “nvme-cli”
First in your command you have to change _ with - beetween “id” and “ctrl”
Then, the results of the plain command or with “-v” or “–vendor” options is quite the same :
nvme-id.txt (1,5 Ko)
nvme-id -v.txt (6,2 Ko)
Hope will be satisfactory.
Thx , preparing patch for your SSD.
( BTW they really hide what Vendor that is …)
Fixed in git for now. Fix will be available after the next kernel rebuild.