eSaF Posted April 13, 2023 Share Posted April 13, 2023 Ok try this EFI and let me know any progress. To clear the NvRAM, if you don't see it at the Boot Menu, hit the Space Bar and you will see the Icon, just move the cursor on it and hit enter which will induce a reboot and you should be good from there on. EFI.zip 1 Quote Link to comment Share on other sites More sharing options...
miliuco Posted April 13, 2023 Share Posted April 13, 2023 @Slice But the Inspiron 3650 is a desktop. So I choose desktop framebuffer. Quote Link to comment Share on other sites More sharing options...
aben Posted April 13, 2023 Share Posted April 13, 2023 If this is an AiO setup, then @Slice recommendation is correct, LVDS (and eDp) connectors are usually used to drive panels of laptops and AiO devices. OP should be using mobile connectors too, I think. 1 Quote Link to comment Share on other sites More sharing options...
eSaF Posted April 13, 2023 Share Posted April 13, 2023 I forgot to add your Graphics Properties in Device Properties to your Original EFI Folder so if that last one I sent you don't work, try this. EFI.zip 1 Quote Link to comment Share on other sites More sharing options...
Alan Sojan Posted April 13, 2023 Author Share Posted April 13, 2023 Hey, I tried it but there's still no graphics acceleration Quote Link to comment Share on other sites More sharing options...
Alan Sojan Posted April 13, 2023 Author Share Posted April 13, 2023 1 hour ago, eSaF said: I forgot to add your Graphics Properties in Device Properties to your Original EFI Folder so if that last one I sent you don't work, try this. EFI.zip 4.87 MB · 2 downloads Quote Link to comment Share on other sites More sharing options...
eSaF Posted April 13, 2023 Share Posted April 13, 2023 What is this in your last post above, did you get anything to work? Quote Link to comment Share on other sites More sharing options...
Alan Sojan Posted April 13, 2023 Author Share Posted April 13, 2023 3 minutes ago, eSaF said: What is this in your last post above, did you get anything to work? Yes it's booting, but there is still no graphics acceleration working Quote Link to comment Share on other sites More sharing options...
eSaF Posted April 13, 2023 Share Posted April 13, 2023 8 minutes ago, Alan Sojan said: Yes it's booting, but there is still no graphics acceleration working Sorry man I am fresh out of ideas, hopefully someone else can offer a solution to fix the graphics problem. 1 Quote Link to comment Share on other sites More sharing options...
Alan Sojan Posted April 13, 2023 Author Share Posted April 13, 2023 2 minutes ago, eSaF said: Sorry man I am fresh out of ideas, hopefully someone else can offer a solution to fix the graphics problem. Okay, however thank you so much for your help. Very grateful! 1 Quote Link to comment Share on other sites More sharing options...
miliuco Posted April 13, 2023 Share Posted April 13, 2023 (edited) @Alan Sojan Working over the last EFI uploaded by @eSaF, replacing only config.plist, here you have 2 files, config1.plist and config2.plist. Try first config1.plist, replacing the current config.plist (don't forget to rename config1.plist >> config.plist). Comment if it's working well. If config1.plist fails, try config2.plist in the same way (replacing current config.plist and renaming config1.plist to config.plist). config1.plist has framebuffer for mobile Intel 530. config2.plist has framebuffer for NUC Intel 530. Uploaded files deleted. Edited April 14, 2023 by miliuco 1 Quote Link to comment Share on other sites More sharing options...
Alan Sojan Posted April 14, 2023 Author Share Posted April 14, 2023 12 hours ago, miliuco said: @Alan Sojan Working over the last EFI uploaded by @eSaF, replacing only config.plist, here you have 2 files, config1.plist and config2.plist. Try first config1.plist, replacing the current config.plist (don't forget to rename config1.plist >> config.plist). Comment if it's working well. If config1.plist fails, try config2.plist in the same way (replacing current config.plist and renaming config1.plist to config.plist). config1.plist has framebuffer for mobile Intel 530. config2.plist has framebuffer for NUC Intel 530. config1.plist 18.45 kB · 1 download config2.plist 18.45 kB · 1 download I tried both but both arent working? Im not sure if I'm doing something wrong. I have windows installed on this machine as well if that can maybe help with this problem. Quote Link to comment Share on other sites More sharing options...
feartech Posted April 14, 2023 Share Posted April 14, 2023 8 minutes ago, Alan Sojan said: I tried both but both arent working? Im not sure if I'm doing something wrong. I have windows installed on this machine as well if that can maybe help with this problem. probably because of this boot argument: -igfxvesa Quote Link to comment Share on other sites More sharing options...
Alan Sojan Posted April 14, 2023 Author Share Posted April 14, 2023 4 minutes ago, feartech said: probably because of this boot argument: -igfxvesa I will remove it and try. Quote Link to comment Share on other sites More sharing options...
miliuco Posted April 14, 2023 Share Posted April 14, 2023 (edited) @feartech What a mistake! I hadn't noticed this boot arg. Of course @Alan Sojan has to remove it, as long as you have it on there will be no graphic acceleration regardless of the framebuffer. @Alan Sojan These are the 2 config.plist previously uploaded, with -igfxvesa removed. config1.plist config2.plist Edited April 14, 2023 by miliuco 2 Quote Link to comment Share on other sites More sharing options...
Alan Sojan Posted April 14, 2023 Author Share Posted April 14, 2023 11 minutes ago, miliuco said: @feartech What a mistake! I hadn't noticed this boot arg. Of course @Alan Sojan has to remove it, as long as you have it on there will be no graphic acceleration regardless of the framebuffer. I have tried both and removed the boot argument on both of them it's still not working. Quote Link to comment Share on other sites More sharing options...
miliuco Posted April 14, 2023 Share Posted April 14, 2023 1 minute ago, Alan Sojan said: I have tried both and removed the boot argument on both of them it's still not working. config1 and config2? Do you still have 6 MB in the iGPU vram? Quote Link to comment Share on other sites More sharing options...
Alan Sojan Posted April 14, 2023 Author Share Posted April 14, 2023 2 minutes ago, miliuco said: config1 and config2? Do you still have 6 MB in the iGPU vram? Yes I tried both, and it has 6 MB in the Graphics Quote Link to comment Share on other sites More sharing options...
eSaF Posted April 14, 2023 Share Posted April 14, 2023 I know this maybe a bit of stretch but is the BIOS the latest version for the motherboard? With all the tips/fixes offered, at least one should have cured the problem in my opinion. Quote Link to comment Share on other sites More sharing options...
Alan Sojan Posted April 14, 2023 Author Share Posted April 14, 2023 32 minutes ago, eSaF said: I know this maybe a bit of stretch but is the BIOS the latest version for the motherboard? With all the tips/fixes offered, at least one should have cured the problem in my opinion. Yes, I am on the latest BIOS version. I'm not sure if this affects anything but, I am using a VGA monitor with a HDMI adaptor. Quote Link to comment Share on other sites More sharing options...
deeveedee Posted April 14, 2023 Share Posted April 14, 2023 (edited) @Alan Sojan For properly working VGA with HD530, you may need boot-arg igfxagdc=0 (same as DeviceProperty disable-agdc). Also, I did a quick scan of the various config.plists posted in this thread: config.plist is missing framebuffer-patch-enable (so video patches are not applied) and it specifies a frame buffer with zero connectors (see here), config1.plist and config2.plist have incorrect framebuffers (needs to be Little Endian). Edited April 14, 2023 by deeveedee 2 Quote Link to comment Share on other sites More sharing options...
miliuco Posted April 14, 2023 Share Posted April 14, 2023 (edited) Thanks @deeveedee for your notes. I change the framebuffer of both config.plist to little endian (19160002 >> 02001619 and 19160000 >> 00001619, right?). Also adding igfxagdc=0 boot arg. About framebuffer-patch-enable, both files have it with data value of 01000000, must be 00000001? Other config.plist files are missing framebuffer-patch-enable, as you say. Edited April 14, 2023 by miliuco 2 Quote Link to comment Share on other sites More sharing options...
deeveedee Posted April 14, 2023 Share Posted April 14, 2023 (edited) <01000000> is correct. It's Little Endian representation of 0x00000001. Edited April 14, 2023 by deeveedee 3 Quote Link to comment Share on other sites More sharing options...
miliuco Posted April 14, 2023 Share Posted April 14, 2023 @Alan Sojan With changes by @deeveedee. I cross my fingers. config2.plist config1.plist 1 Quote Link to comment Share on other sites More sharing options...
Alan Sojan Posted April 14, 2023 Author Share Posted April 14, 2023 27 minutes ago, miliuco said: @Alan Sojan With changes by @deeveedee. I cross my fingers. config2.plist 18.45 kB · 1 download config1.plist 18.45 kB · 1 download Hey, I tried config1.plist it loads up the code and turns off my monitor 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.