I hope you enjoy it.

The instructions in the previous post are for using lilo. For your case, which is elilo you need

then edit elilo.conf and add an entry like this.
You don't need to reinstall if you screw up the bootloader. You can use the installation media to chroot in the screwd system. Boot the installation media and then do this on the root console

See here for more http://docs.slackware.com/howtos:sla...oot_from_media

Even if you can always do something like this
as I posted above, just make a network share on the windows guest and use this to transfer files. It's much simpler and cleaner than messing directly with permissions on the /dev/bus/usb... files and custom udev rules.

The 70-persistent-net.rules exists in order for the network interfaces to always keep their names the same. You don't need to mess with it at all.

It seems that you are trying many things for the first time. Breaking things is a way to learn things, so keep breaking them and you will get where you want.

I don't believe you can adjust usb permissions with lsusb. What I meant was to view the permissions of a similar device using ls -l, and then mirroring those permissions on the other device using chmod. Unfortunately, I don't even know if /dev/bus/usb/013/001 will exist in your system (if it doesn't, try to find other devices you could use instead), but if it does, you could use the following command to view what the permissions are:

If you aren't familiar with how Linux permissions work and are struggling trying to figure out what to type to change the permissions, feel free to post the output of the above command and we can provide you with the correct chmod command to adjust your initial device.

This is totally true! I tend to learn more when I break something and then figure out how to fix it than if I just get it working the first time. The first time I jacked up my lilo was when I dug into lilo to figure out how it works, and it has still stuck with me over these years.

I found the issue with this:
I simply forgot to remove the loose -usbhost command that existed when I was trying to pass through my external HD. Other than that, not much has changed so far. Ninikos, I will check to see if your solutions will work.

HUGE EDIT
now I understand why this entire debacle has been a wild goose chase for me. I misidentified my GPU. It's the Sapphire RX 480 nitro+, not the 580 nitro+.



well... I have no excuse other than I'm forgetful and bull-headed at times.

So I uninstalled the incorrect driver and installed the correct one... and the result is STILL the same. I even added the line for downloaded bios rom as ninikos suggested. I will look around to see how OVMF works, if I run out of options, I will switch to legacy mode and use the mounting instructions to redo my boot partition.

I just tested passthrough with an OEM AMD 7350 and a windows guest. I am posting the facts as I recall

0. Host machine booted via UEFI, using generic kernel 4.4.157 on slackware64-14.2
1. The host was up for a few days
2. The 7350 was used for passthrough to a slackware-current and a Centos 7 guest
3. Fired up old forgotten windows 7 guest, normal bios guest, no OVMF for this one
4. Installed latest updates for windows .. waited few hours ... slackware has spoiled me with updates taking just a few minutes
5. Shut down the guest, and passed through the 7350 device and it's audio device via vfio
6. Tried to install latest AMD driver on the guest, the installer said that the card was not recognized
7. Manually installed the driver from 'Device Manager' via 'Have disk ...' method, pointed to C:\AMD\WHQL-Win8.1-Win7-Catalyst-15.7.1-Oct30\Packages\Drivers\Display\WB6A_INF\*.INF and the driver was installed. It prompted for reboot. After which ...
8. The host freezed :-( And it was a total freeze. No ssh, no respond to power off button, no REISUB, it just froze. dmseg logged something about disabling interrupt 21. Hold power button to power off the host, scary thing (especially when using raid). Powered up again.
9. Then I tried the following (after remembering that I use something similar for MacOS). The interesting part is the cpu option, but I am posting the whole configuration that I just tested. @lawnm0wer Don't use virtio for your disk if you don't know how to setup windows with floppy disk that has the windows virtio controller driver. Almost the same for virtio-net-pci, you need a windows driver to use it.
10. Aaaand ... it works! :-)


I don't know if the cpu option is the reason for the freeze or using the 7350 with linux guests before passing it to the windows guest.

well, I tried to follow what you did ninikos, I even went and managed to for real get the generic kernel bootable, but it went and panicked on me. I've hit my limit for tech frustrations, I don't have enough time these days to have the patience to deal with them, and it's not even fun for me.

It's been almost a solid month of frustration, I'm drained, and I'm sick of dealing with these issues only for more to shove their way into my face. I'm going make the switch from slack again...

But just for my desktop for now.

I will continue to be using slackware on my other devices. no matter what other distro I switch to, I always end up switching back to slack. I'll be back sometime to try GPU passthrough again, I just need some time to relax.

Thank you guys for everything you've done for me, hopefully the next times I see you again, the threads will be shorter than this.