Search results

dont run any vm that has that igpu passed through. remove any blacklists remove the vfio-driver loading for the igpu. just like in the tutorials but then in reverse. and then show the output of dmesg | grep amdgpu you will find the name of the vbios file being used if the motherboard supplies...

My advice would be is to first not blacklist it and not pass it through and also not load vfio drivers at any stage. let your host system figure out which vbios file to use. or do you get greeted with an error message that a VBIOS file could not be found in your host's dmesg? I have had that...

although it threw an error this mount -t evivarfs I was able to run the proxmox-boot-tool now

thank you leesteken. it did hint me more into the right direction. I was able to use the proxmox iso debug installer which I exited to enter a shell then I was able to update the /etc/kernel/cmdline using the steps found below...

I run the latest proxmox with root on zfs I locked myself out of the system by having added too many kernel cmdline parameters (/etc/kernel/cmdline) related to the disabling of the display. So I tried using the rescue boot option on the most recent pve iso but it errors out stating it can not...

I see you are still blacklisting the amdgpu driver? or perhaps not blacklisting it but having the vfio-pci being used for your igpu instead. the idea is to have it load normally to be able to see in the dmesg which BIOS rom file is loaded as supplied by the firmware on the motherboard. But...

ahh well you know the age old saying. give a man enough to drink and he will start reading up out of sheer boredom :) So in order to work from the top down you indeed need to revert a few steps back in order for me to be able to help out. If things never worked on the host then I am not sure I...

ok. it looks like you are missing a lot of command line parameters but that is of later concern. also I did not see the amd driver being correctly loaded. So please make sure they are on the host by disabling blacklisting and any VM that might want to use it. then on the host (no VM just yet...

btw, I never got an email regarding this mention. I think the forum is either broken or somehow I am shadowbanned. or anything in between for that matter.

you see, rather than focusing on the Vm it self I would like to tackle this potential problem from the top down. For example I have tried many configurations for VMs and I like the linux way of booting in where I can see things go right or wrong. Now if we get a linux VM up and running then we...

what specific tutorial are you referring to? Please remember I am just soo busy that sometimes I have time to write a long wided answer like I do now. But reading up on long threads has never been my strong point if I enter as an advice giver rather than the needer of advice. So. Please show...

I will still try and help. what specific hurdle are you facing at the moment? If you can be forthcoming then that saves me from reading up on a thread of which I have read sooooo many already. some of them end up in success while most just end up abandoned after a while.

it can never be on the proxmox side as proxmox is just a layer on top of debian which is just yet another lay on linux. Please be more specific. Also ubuntu also failed for me while I was at 90% of reaching my goal. So once again if you are serious about this issue then please be serious...

the concept is the same for non grub boot I think. this is my line after I have sanitized a bit (perhaps still more can be removed just not the nomodeset) quiet amd_iommu=on iommu=pt initcall_blacklist=sysfb_init video=simplefb ff video=vesafb ff video=efifb ff video=vesa ff disable_vga=1...

what worked for my AMD Ryzen 3 PRO 4350GE with Radeon Graphics is to add nomodeset to the kernel commandline it has a ton of other stuff there too that I am not certain is really needed but nomodeset was the last part of the puzzle. i also had to find the gpu rom file. i found one while...

You my esteemed sir are a rock star!! saved my day

I no longer want to pass through a GPU to a VM that does not really need it. I mean come on Skethup 2017 you do not need a GPU. Is there any way I can make it so that my windows VM thinks there is an actual GPU? I do not mind if some software breaks. I just want to get past this sketchup barrier

I second help by an expert. A use case would be for openwrt to do it's magic while runningbas container

I think I confirmed the proxmox GUI syslog is reading from the journal I added a line echo 'hello' | systemd-cat and it showed up in the GUI syslog. it was also present in /var/log/syslog but there it did not show like it did in the GUI.

Interesting suggestion, thank you. For new comers like me it's rather difficult to tell what is current and what is depreciated