@Tomoms OK, you can see what parameter options are via /sbin/modinfo nvme_core
And in grub if you select rescue mode, does it boot?
Can you show the output of the command lsblk
as well.
@Tomoms OK, you can see what parameter options are via /sbin/modinfo nvme_core
And in grub if you select rescue mode, does it boot?
Can you show the output of the command lsblk
as well.
This what happened to me as well but not only that it brick my system lol. Now I don’t have PC . The 6.6.1 Kernel is really something though
@projectmirai39 No issues here with 6.6.1 kernel (I’d watch out for 6.6.6 one though) with MicroOS and Tumbleweed.
Ah yes, the sign of the beast … best to avoid that version.
And yea, no issues here with current TW, on four different machines: two AMD specific and two Intel specific.
@malcolmlewis
Rescue mode does not help, the computer keeps hanging at the same point.
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 232,9G 0 disk
└─sda1 8:1 0 187,2G 0 part /mnt/ssd
sdb 8:16 0 931,5G 0 disk
├─sdb1 8:17 0 637,2G 0 part /mnt/ssd/21/prebuilts
│ /mnt/ssd/20/prebuilts
│ /mnt/ssd/18.1/prebuilts
│ /mnt/data
└─sdb2 8:18 0 294,4G 0 part
sdc 8:32 0 447,1G 0 disk
├─sdc1 8:33 0 100M 0 part /boot/efi
├─sdc2 8:34 0 16M 0 part
├─sdc3 8:35 0 124,4G 0 part
├─sdc4 8:36 0 505M 0 part
├─sdc5 8:37 0 24,4G 0 part [SWAP]
├─sdc6 8:38 0 60G 0 part /var
│ /root
│ /usr/local
│ /srv
│ /opt
│ /boot/grub2/x86_64-efi
│ /boot/grub2/i386-pc
│ /.snapshots
│ /
└─sdc7 8:39 0 143,1G 0 part /home
nvme0n1 259:0 0 465,8G 0 disk
└─nvme0n1p1 259:1 0 399,6G 0 part /mnt/nvme
/dev/sdb1 is involved in some bind-mounts, and I have free unallocated space at the end of my SSDs because I’m paranoid with overprovisioning
@malcolmlewis Filing the bug report right now. Removing the intel_iommu cmdline parameter did not help either, FYI. Thank you for your help.
Please share a link to your bug report.
There is a similar case in the german forum. So its author might wish to join in.
Thank you.
Latest tumbleweed snapshot here.
I installed the hard way and got similar issue like the op.
I used the NVIDIA-Linux-x86_64-545.29.06.run installer.
I reinstalled the driver and before rebooting I did dracut -f`
then reboot and I finally got my GUI back.
As an aside, this new .run file has a nice additional/new installer features.
And oh, malcolm 6.6.6. is his lucky number
@malcolmlewis wrote:
@myswtest ooooh it’s in snapshot 20231212…
I should wait for the next kernel update!
Hehe, I did the dup and the next day (today) I won one free lottery ticket and 10 bucks.