Dear all,
thank you very much for possibility to write into this forum.
I am a Slack newbie and I try to install into my Win system (on nvme hd) using Virtualbox tool and its features.
I tried the installation on SATA and UEFI virtual box emulation and it is all OK.I reached to end the process (also with elilo into EFI partition and so on..)
The problem grow-up when I want to try installation choosing the nvme virtualbox support.
The process have problems in installpkg setup part.
Some packages (random in each attempt) seems corrupt or the installer doesn't reach to open the files.
Errors are in "/mnt/var/log/setup/tmplist<numer> read-only filesystem".
So what can I do to tune this situation? Is it a driver issue?
Sorry if I don't explain very well my question and my English is not perfect :-) however thanks to all.
Bye
Alex

Hello, and welcome to this forum.

Slackware 14.2 can't be installed on NVMe devices, this feature will be available when Slackware 15 will be released.

Meanwhile, you can use the ISO that I have uploaded here: http://slint.fr/forSlackware/NVMe/

Just follow the instructions from a) to f)

Hello and thanks for your precious answer.
I downloaded a last version (slackware64-current-DVD.iso dated DEC 2017).
As a consequence can I follow this steps:?

1) open the iso file
2) set the 3 indicated files (setefi.diff,eliloconfig.diff,prob_nvme.diff),into correct directory
3) created a new ISO file
4) proceeding to install like I did for SATA-EFI system in virtualbox (using EFI shell and so on that it goes ahead till the end correctly)

What do you think about?
I thank you again for your help
Have a nice weekend
Alex

The changes are already made in this ISO, so you can just use it as is. I forgot to mention that the recent current ISO are OK on NVMe.

Bonne fin de semaine.

I read on some posts that the problem can be due to the small /tmp directory or corrupted ISO file download.
Taking into accoount that:
I used another dated december support and the problem is the same (at the end of installation phase...)
I used the same file for install the Slack into VB with SATA features (Optic device and virtual hd) and all go ahead correct...
I can suppose that the /tmp space is right idea...what do you think about?
In this case the only solution that I can imagine is modifying the tmp space into ISO file and created the new ISO.
(/mnt/var/log/setup/tmp/tmpsize....).
The problem is that I don't know how I can do this....:-(
Thanks for your assistance
Alex

Now that I read more carefully your first post these messages about a read only file system are really weird... What is the size of your root partition? Maybe it's just to small. Try with 12G or so. And don't set another partition but the one for EFI. Especially, don't set a partition for /tmp. Just two partitions (one of type Linux 12G or moret for / and one of type EFI System Partition of size at least 100M) is enough.

My dubt is exactly that:
I set an EFI partition for 250 Mb and one system partition equal to 19.50G space.
So when I use the SATA features the installation process end without errors and the distro is perfect intalled, when I set nvme features, the process stops with this strange errors. They are found in random packages for each time than I try.
The last test was closely to end (I arrived to KDE installation phase)...but when I started to think that we reach the solution (I change the ISO with December version)...the problem grow-up newly.
Strange, very very strange behaviour
Bye
Alex

Do you have a very recent VirtualBox version? I suggest that you try with the latest (5.2.2) and of course you need the matching extension pack.

All did.Latest version of VB and extension pack.
The problem is in my point of view due to tmpfs that slack fix in the fstab during the installation phase if you consider the different type of capabilities of emulated type between sata & nvme virtual devices.
So i think that the further test is try to change this installation in splitted ISO.
Bye
Ale.

Addendum:I suppose that all used ISO doens't contain your indicated *.diff file...so the problem is into the installer when catch the script into:
/usr/lib/setup/*.I saw that the process views "read-only filesystem" into different lines of different files included there.
Bye
Alex

Hello Didier, perharps I found the original problem.
I suppose it can be a matching NVME drivers between VB and Slack in virtual support hard disk.
If I try to see kmsg (when the setup process stopped with:
/usr/lib/setup/installpkg: line 378 /mnt/var/log/setup/tmp/tmpsize_number read-only filesystem
/usr/lib/setup/installpkg: line 378 /mnt/var/log/setup/tmp/tmplist_number read-only filesystem),
I discovered a lot of this kind of message:
"Buffer I/O error on device nvme0n1p2 logical block
Ext4-fs warning (device): ext4_end_bio: 314 i/o error -5 writing to inode (offset 0 size....starting block...)
Buffer I/O error on device nvme0n1p2 logical block lost async page write"
It ends with "ext4-fs remounting file system read-only"
so..the strange behaviour during the setup phase.
Taking into account that the setup is ok with SATA emulation DVD and VHDL controller.
What do you think about?
Bye

Looks like an issue with the virtual file system.

I just checked, you have e2fsck in /sbin in the installer, run it against the virtual NVMe device before typing setup.

Meanwhile I will setup a VM equipped with a NVMe device and test incoming Slint64-14.2.1 in it. I will let you know the outcome.

Installed with no issue in EFI mode, see the attached pic, with the settings in mate-terminal.

Attached Thumbnails

 

Hello Didier & thanks for your precious assistance.
Within this week I try to follow your steps.
What kind of ISO can I use?(it is to tune and link my tests with your trial).
I think that e2fsck must be used after partition phase (with cfsck) and before running setup. Isn't it?
What option can I put when I run it?
Thanks again
Bye

The ISO I used is not yet released, will be tomorrow if all goes well.
Meanwhile you can try the one in this repo: http://slackware.uk/slint/x86_64/slint-14.2/iso/
Or the ISO with just the installer in the repo linked to in my first post in this thread: http://slint.fr/forSlackware/NVMe/

Yes, run cfdisk first, then e2fsck. For the options I can't really advise, I am not an expert. Just read the man page (I think that's the same version included in an installed system) and/or find examples with an Internet search. The device shouldn't be in use, so yes run e2fsck before setup.