[Solved] KVMFR module doesnt load correctly on boot
kvmfr module doesnt appear to be loaded correctly on boot
contents of
/etc/dracut.conf.d/kvmfr.conf
contents of /etc/modprobe.d/kvmfr.conf
ive been able to verify that the kvmfr module is loaded on boot, as lsmod reports
however /dev/kvmfr0 is not present on boot, when unloading the module and doing sudo modprobe kvmfr static_size_mb=64 its loaded and usable with looking glass.34 Replies
@HikariKnight
can you reboot and give me
sudo dmesg | grep kvmfr
should show
there is also a complaint about SELinux but the type enforcement we have fixes that as it loads later and systemd is trying to revert our settings for kvmfrhmm so the module should be loaded š¤
ls -la /dev | grep kvminteresting to note yours says creating 1 static devices
mine says 0
oh wait yeah
hmm
does your
/etc/dracut.conf.d/kvmfr.conf start with that empty space or is that you accidentally adding it in the message?thats how it starts
apparently
try remove the empty space at the beginning
then do
rpm-ostree initramfs --enable
and wait for that to finishenable what
it gives me a no command specified
sorry
there
ah
right
its already enabled, do i just reboot
because your dracut conf file is
but should be
if what you told me is correct
yes, ive removed the empty space now
ok try reboot and check dmesg again
still says 0
still no /dev/kvmfr0 present
that is so weird
ive basically followed what the ujust command did, but ran manually
since the ujust commands seem to not run correctly
hmm
runs fine for me
what error do you get with the ujust?
it errors after asking to regenerate initramfs
but im not sure if its supposed to do anything after that
oh thats fine, that just the rpm-ostree sending exit 1 because initramfs is already enabled
and ujust reads that as an error with the script even if it is not
try reboot without changing the modprobe conf
see if it generates it then
will do
essentially leave it at 128
Okay, doing that now
that should just work since i just used it myself
I'll be damned it did
most likely an invisible character then from when you ran it manually
I must've messed something up myself then
Likely
you can try change the size to 64 if you want, only reason we put it to 128 is because 4k will work with it and looking-glass wont crash if you use a dummy plug that supports it if a game goes like "oh you use 1080p but your display supports 4k, you want it in 4k right?!"
yeah i dont use a dummy plug, i just have the gpu plugged into the back of my monitor
yeah so it will be a non issue for you
i recommend changing the static size to whats best for your resolution then
š
i'll mark this as fixed now
solved
whatever you call it
i marked it
ah
im a stoop
answeroverflow is great, it lets us index #bazzite-help to search engines