![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
https://bugzilla.suse.com/show_bug.cgi?id=1173682 https://bugzilla.suse.com/show_bug.cgi?id=1173682#c18 --- Comment #18 from Ricardo Minnaard <opensuse@x-labs.nl> --- How do the AMD drives solve this? Or do they have the same issue? I’ve been in Suse since Novell bought it, so I’ll be fine. But I’m noticing a Linux growth around me. As me, more people are switching to Linux. People are playing A+ games now on Linux. See YouTube, it’s flooding with gaming on Linux vids. Not being able to run these drives is a disaster IMO. It sets Linux back several years. Yet I do understand the security trait off. I’m no developer, so I’m not going to lay down some hard critics. And if I was able to be part of the solution I’d try. My understanding is too little. If it was up to me, I’d show a pop-up window or a big splash screen in the GUI informing a user the steps to take to get around this. A text somewhere in some release notes isn’t enough. But that is my personal opinion. Ubuntu has or had this wizard for proprietary drivers. Something like that to explain a user why it doesn’t work with secure boot. -- You are receiving this mail because: You are on the CC list for the bug.