fabiosun
-
Posts
11,274 -
Joined
-
Days Won
533
Content Type
Profiles
Forums
Events
Downloads
Everything posted by fabiosun
-
Beta 4 is here. I have also installed Nvidia driver (patched) to have dual display and a minimal functionality on display graphics as I have had in Mojave or in Catalina Installation notes Same open core 060 latest release debug version with all kext and drivers updated During first installation step I have used old Penryn args for VM config
-
-
@tsongzin these preliminary steps of your learning curve, I will suggest to understand well which parameters in vfio.conf and in blacklist.conf inhibit your system to a proper use of shell in host During tests, adding cards or moving it or only change some parameters in vm could produce problem to access to host from other pc So our safe (without reinstalling all or unmounting/mounting spare gfx card is the chance to be able to modify things via shell another matter for me is to understand why you block all that stuff and what kind of advantages you get from this type of configuration, with you I mean most of you who in part followed my guide 🙂
-
Post your vfio.conf also lspci -nnk but i think if you followed pavos github you block things he is blocking because he starts or started in the past his guest from web interface on another pc i can be wrong...
-
I think he is blocking to much stuff it is also in Proxmox wiki..but we can do in a different way 🙂
-
I am using only my guest to use my thread ripper machine Sometimes during my "bleeding edge test" I have problem and I have to use a spare pc to solve normally I turn on my thread ripper and when shell is available I execute from it qm start 100 to start my main VM when I have used to add in vfio.conf my GPU or to blacklist nouveau or Nvidia drivers.. my system to boot needs of a spare pc or an automatic vm 100 booting option enable you can see it in macos86.it you tube channel 🙂 check framed window..there only 2 verbose initial lines and then vm starts in automatic way in big window no block are there and I see regular verbose and shell
-
remove it from vfio.conf also you can try to unblacklist amdgpu from blacklist.conf in my rig I do not use any block and it works
-
@tsongzif it is a PCIE card it could be happen it changed your passed id number..overall if your mb PCIE slot are "shared"
-
@meina222 it is good 🙂 thanks
-
Thank you and don't worry risk is mine 🙂 I will try ands see if it boots
-
text popup means send a file via link
-
no you don't have to register you can upload file for free without registration
-
@meina222I use this free service: https://www.myairbridge.com
-
@tsongzI have no experience with this kind of stuff..I received this error:
-
@meina222 to post compiled kernel as deb file is not possible?
-
About opencore we are talking about 060 release in Italian forum section i have installed o60 release debug version with no problem at all
-
If I have understood well it is possible to use if you do not use zfs..and so..is it available a compiled kernel in this way? I would like to test if it adds some opportunity to pass bridge or pcieport.. I think it is a qemu problem than kernel..but I am not sure of this my assertion 🙂
-
aggiornato anche qui alla release (debug) tutto ok
-
I will do more 🙂 attached ioreg with patched 23 firmware and 50 untouched tb_ioreg.zip
-
you can use ssdt to refine some aspect, but not necessary for Host cpu.. Oc developer have done some modify which allows us to boot with a minimal set of "old" vanilla patches and have our cpu recognised as AMD Thread ripper in many app Aestetycally much better than Penryn core duo output with 64 cores 🙂
-
@Driftwoodand that one is the red pill answer 🙂 but if you want to see how deep the white rabbit hole is.. (Matrix film) 🙂 blue pill here 🙂
-
in this weekend I have flashed many firmware found on the net (GitHub) I will put here the exact name of these files but not the direct link that you can find easily googling 1) TitanRidgeMacOSFirmware.bin (DSM2 firmware I think) 2) TitanRidgeNVM23-Elias64Fr-Mod.bin (Eliasfr caseSj firmware I think) 3) TitanRidgeNVM43-Elias64Fr-Mod.bin (Eliasfr caseSj firmware I think) 4) original v43 firmware (stock in my board) 5) original v50 firmware (updated via Gigabyte windows updater utility) fast analysis : with all firmware I have the same driver loaded in windows, but with all of these I can't see any device connected to TB output, I have no thunderbolt devices and I have tried only with two different USB type c devices with 1) in OSX I see only 15eb if I do not boot before in windows and I have a pretty full ioreg with all we need..with bad naming with 2) I have the best result in OSX, no need to boot in windows before and I have the pretty same IOREG (full of stuff) with always bad naming with 3) I have a minimal ioreg similar to original not patched version (identical, and this le me think it is an original firmware) with 4) and 5) the same minimal ioreg in OSX I have verified thanks to @thenightflyer for this that I have the same his ioreg in many parts except for naming and some voices, I think because he is on x299 system which support better ssdt part Any idea to how solve this puzzle will be accepted 🙂 attached 2 images for clarification, on the right x299 working ones
-
and also for me is not useful to block all that stuff in blacklist.conf and in vfio.conf but I can't say for sure because many of you and Proxmoxwiki advice to do that... maybe I am lucky 🙂
-
@tsongz are you sure you need all those ssdt to have cpu as host booting fine? In my MSI board no need for any of these ssdt, only to configure vm config and config.plist in open core properly (for owned hardware I mean)
