cracauer@
Developer
Is a theory forming in your mind that reasonably explains the evidences that I'm bringing to you ?
Can you confirm the two exact revisions that worked and didn't work?
Is a theory forming in your mind that reasonably explains the evidences that I'm bringing to you ?
p5 does not work. So,only p6 works. Isn't this interesting ?
Based on this text from the Supported Releases section of FreeBSD Security Information:Please tell me the first commit of the FreeBSD 14.0-RELEASE p6.
and looking through releng/14.0 commits I'm guessing it's d338712beb16ad7740bbd00bd93299a131a68045The Security Branch tags have names like releng/13.2. The corresponding builds have names like FreeBSD 13.2-RELEASE-p1.
# pkg info -I edk2-bhyve
edk2-bhyve-g202308_4 EDK2 Firmware for bhyve
#
Can you confirm the two exact revisions that worked and didn't work?
70eb00f17b310f599b60939c1afa326c7b2c390c
Based on this text from the Supported Releases section of FreeBSD Security Information:
and looking through releng/14.0 commits I'm guessing it's d338712beb16ad7740bbd00bd93299a131a68045
It might be best to wait for @cracauer to confirm though.
I'm also suffering from Window 10 VM not working since upgrading from Corvin's version of FreeBSD-13.2 to 14.1-RELEASE.
In my case, I'm trying to pass through the iGPU of the i7-9700T.
Could you post which version of edk2-bhyve you have installed?
For me, it is:
Bash:# pkg info -I edk2-bhyve edk2-bhyve-g202308_4 EDK2 Firmware for bhyve #
As you have an i9-9900K I'm secretly hoping you've stumbled upon a bug common to us both!
Based on this text from the Supported Releases section of FreeBSD Security Information:
and looking through releng/14.0 commits I'm guessing it's d338712beb16ad7740bbd00bd93299a131a68045
It might be best to wait for @cracauer to confirm though.
I'm also suffering from Window 10 VM not working since upgrading from Corvin's version of FreeBSD-13.2 to 14.1-RELEASE.
In my case, I'm trying to pass through the iGPU of the i7-9700T.
Could you post which version of edk2-bhyve you have installed?
For me, it is:
Bash:# pkg info -I edk2-bhyve edk2-bhyve-g202308_4 EDK2 Firmware for bhyve #
As you have an i9-9900K I'm secretly hoping you've stumbled upon a bug common to us both!
I meant that, unlike bileslav who is using a Ryzen 5900X, we are both using Intel 9th Gen CPUs and so maybe that is a common aspect in a potential bug that you might find.---> As you have an i9-9900K I'm secretly hoping you've stumbled upon a bug common to us both!
Which bug in common we have ?
14.0-RELEASE-p6 FreeBSD 14.0-RELEASE-p6 #32 releng/14.0-n265396-06497fbd52e2-dirty
06497fbd52e2
seems very much like:14.0-RELEASE-p2 FreeBSD 14.0-RELEASE-p2 #0 releng/14.0-n265396-06497fbd52e2
06497fbd52e2f138b7d590c8499d9cebad182850
just in case?Pretty sure the #15 represents your local build number. See this thread about it:
Kernel build number
Hello, What does the #0, #1, etc. found in the output of uname -v mean, exactly? I guess it's a kernel build number? Official builds all seem to be #0. I currently have FreeBSD 13.1-STABLE #4 stable/13-n250651-85983255c15. I upgraded my system today and went from a FreeBSD 13.1-STABLE #2 to a...forums.freebsd.org
I meant that, unlike bileslav who is using a Ryzen 5900X, we are both using Intel 9th Gen CPUs and so maybe that is a common aspect in a potential bug that you might find.
ziomario we need to use precise language here.
The p<n> numbers are not precise since they are not tagged in the git tree.
Could you please state which commit hashes you tested and the result?
# git checkout 06497fbd52e2f138b7d590c8499d9cebad182850
# make -j4 buildworld buildkernel
work in progress...
# sha256sum vmm.ko
c57645e8d1a43714bb899813567f4678dddd73ca55e5745f77daea8241126d48 vmm.ko
14-RELEASE-p6 #15 = d338712beb16ad7740bbd00bd93299a131a68045 = NO
How did he update to p6? From source, freebsd-update?The bileslav file always works,the default vmm.ko files offered by FreeBSD,never. But if bileslav told that it comes from 14.0-p6,
make cleanworld
after every commit checkout, before make buildworld buildkernel
? cleanworld Attempt to clean up targets built by a preceding
buildworld, or similar step, built from this source
directory.
By now, I'm a bit tired of this nonsense, bro. Really.The point is that the vmm.ko file has been given to me by bileslav. He told me the version of FreeBSD that he was using and it was the same as mine,14.0-p6. Infact my GPU started working as soon as I have exchanged mine with his. Now I'm trying to find,on the FreeBSD servers,the version of vmm.ko + the relative FreeBSD version that uses it,because I want to check if the same /and official/ version works or not or if the only file which make the GPU correctly work is the file that bileslav gave to me. Have you caught the point ? Until now I didn't find any vmm.ko offered by the various FreeBSD versions I tried working out of the box. But if I exchange the vmm.ko that's offered by them with mine,I can passthru my GPU,even of p7. I suppose it works like that until the end of the 14.0 branch. The bileslav file always works,the default vmm.ko files offered by FreeBSD,never. But if bileslav told that it comes from 14.0-p6,should I believe to him or not ? Something is not linear here. I also add that I'm pretty sure that the "magic" is inside the vmm.ko file of bileslav,because it starts working only when I use it. I mean,I tried to use various versions of the bhyve* files located under /usr/sbin,but they don't make any difference. The GPU passthru happens only if I use the bileslav vmm.ko damn file. Is it useful for you to know his sha256 to gather more informations about it ?
Code:# sha256sum vmm.ko c57645e8d1a43714bb899813567f4678dddd73ca55e5745f77daea8241126d48 vmm.ko
freebsd-updateHow did he update to p6? From source, freebsd-update?
Nopebileslav ever tried on a 15.0-CURRENT system?
Right.`make buildworld` cleans out first unless instructed not to.
freebsd-update
Nope
Right.
Building from source for some time now, last time I checked I had to cleanworld. To reduce build time I have meta mode enabled, but forgot about it.
So you might also want to try commit06497fbd52e2f138b7d590c8499d9cebad182850
just in case?
git checkout 06497fbd52e2f138b7d590c8499d9cebad182850
make -j8 buildworld buildkernel
make -j8 installworld installkernel
FreeBSD marietto 14.0-RELEASE-p2 FreeBSD 14.0-RELEASE-p2 #16 n265396-06497fbd52e2:
Wed Jul 10 14:20:44 CEST 2024 marietto@marietto:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
14.0-RELEASE-p6 FreeBSD 14.0-RELEASE-p6 #32 releng/14.0-n265396-06497fbd52e2-dirty
git checkout 06497fbd52e2f138b7d590c8499d9cebad182850-dirty