Hello, my apologies if I am unaware of certain best practices regarding my first post and I am not a Linux expert, just a self-taught active learner here…
I was successful in installing MicroOS Desktop/Aeon on an old desktop computer, but I am having issues trying to install it on my laptop. YaST doesn’t seem to be able to find my SSD. I thought maybe I did something early on because my old installation (Fedora Silverblue) was encrypted with LUKS, but I was able to install a few other distributions including the most recent version of Leap on my laptop. I believe MicroOS Desktop/Aeon is based off of Tumbleweed and for some reason both installers on the most recent ISO’s cannot find my NVME drive to partition and install.
BIOS settings are not raid, I have it on AHCI, Secureboot is off during install.
During the install I am able to find my drive through lsblk, but not with blkid. It shows under the /dev folder. I can also find it under in the disk utility and gparted, but YaST doesn’t see it.
I went into another tty and noticed there were some setup scripts in the file system. One specifically called udev_setup and it says a few files are don’t exist, but what caught my eye was the line that said
line51: /sys/class/fc/fc_udev_device/nvme_discovery: no such file or directory
I tried to create the file, but I don’t think the system is not allowing me to do that.
I also found the device under /etc/nvme, both hostid and hostnqn show the UUID for the device.
Does anyone have any idea of what might be going on here? Please let me know if I can provide any information I overlooked that might be helpful.
Thank you!
You could start with showing full dmesg output (upload to https://susepaste.org).
Thank you @arvidjaar
Attached is the link to the output of dmesg.
https://paste.opensuse.org/pastes/b6ba1a2b35f1
Here is the raw output.
tty?: install:/ # dmesg -H
[Jul 6 00:44] zram: Added device: zram1
[+0.0013331] zram1: detected capacity change from 0 to 2097152
[+0.0075351] Adding 1048572k swap on /deu/zram1. Priority:-2 extents:1 across:1048572k SSFS
[+1.200491] nouveau 0000:02:00.0: Enabling HDA controller
[+0.936688] pcieport 0000:00:1d.4: AER: Corrected error received: 0000:00:1d.4
[+0.000006] pcieport 0000:00:1d.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[+0.000001] pcieport 0000:00:1d.4: device (8086:02b4] error status/mask=00002001/00002000
[+0.000002] pcieport 0000:00:1d.4: [ 0] RxErr
[+7.920755] memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL, pid=4069 ‘Xorg.bin’
[+2.962534] pcieport 0000:00:1d.4: AER: Corrected error received: 0000:00:1d.4
[+0.000014] pcieport 0000:00:14.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[+0.000002] pcieport 0000:00:1d.4: device [8086:02b4] error status/mask=00000001/00002000
[+0.000002] pcieport 0000:00:1d.4: [ 0] RxErr (First)
[+4.972002] pcieport 0000:00:1d.4: AER: Corrected error received: 0000:00:1d.4
[+0.000010] pcieport 0000:00:1d.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[+0.000002] pcieport 0000:00:1d.4: device [8086:02b4] error status/mask=00000001/00002000
[+0,000003] pcieport 0000:00:1d.4: [ 0] RxErr (First)
[Jul 6 00:45] ISO 9660 Extensions: Microsoft Joliet Level 3
[*0.001103] ISO 9660 Extensions: RRIP_1991A
[+0.065723] ISO 9660 Extensions: Microsoft Joliet Level 3
[+0,001095] ISO 9660 Extensions: RRIP_1991A
[+0.071855] ISO 9660 Extensions: Microsoft Joliet Level 3
[+0.001098] ISO 9660 Extensions: RRIP_1991A
[+1.578437] ISO 9660 Extensions: Microsoft Joliet Level 3
[+0.001275] ISO 9660 Extensions: RRIP_1991A
[+0,111732] ISO 9660 Extensions: Microsoft Joliet Level 3
[+0.001427] ISO 9660 Extensions: RRIP_1991A
[+0.116441] ISO 9660 Extensions: Microsoft Joliet Level 3
[+0.001670] ISO 9660 Extensions: RRIP_1991A
[+0.116359] ISO 9660 Extensions: Microsoft Joliet Level 3
[+0.001289] ISO 9660 Extensions: RRIP_1991A
[+9.889087] nouveau 0000:02:00.0: Enabling HDA controller
I figured it out! My drive was turning off because of some power management settings. I had to disable those settings on boot or my drive would power off.
I added these options to the grub boot entry. My entry ended up looking like this:
linux /boot/x86_64/loader/linux splash=silent apm=off noresume nomodeset nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off
-
apm=off is to turn off advanced power management
-
noresume Restarts the Linux kernel without resuming a previously suspended Linux instance
-
nomodeset tells the kernel to not start video drivers until the system is up and running. This made the resolution better and everything looked sharper during the install.
The last three were what turned off the power management modes for my SSD. I was using nvme_core.default_ps_max_latency_us=0 and pcie_aspm=off and that seemed to help sometimes, but it would still turn off right before the install started installing packages.
Once I added pcie_port_pm=off it completed the install without any issues.
1 Like