Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by viking1304

  1. There is a small glitch at 00:10 (screenshot in attachment) that lasts less than a second, but it is very annoying. I know how to add proper patch with Clover Configurator in KextsToPatch, I know how to add it with text editor, I know how to patch binary with hex editor... I tried all of those methods, but that patch just doesn't help in this case. Any other ideas?
  2. Your config is still a battlefield. You still have a million and one thing that you do not need there. For audio, try to use layout 11 instead of 1 and clean ALL AppleHDA ALC 256 patches. Devices > Audio > Inject > 11 Kernel and Kext Patches > Kexts to Patch > AppleHDA ALC 256 #1 > disable Kernel and Kext Patches > Kexts to Patch > AppleHDA ALC 256 #2 > disable Kernel and Kext Patches > Kexts to Patch > AppleHDA ALC 256 #3 > disable Kernel and Kext Patches > Kexts to Patch > AppleHDA ALC 256 #4 > disable
  3. I never managed to fix second stage glitch. I tried every possible patch that I could found, but annoying glitch is always there. I reinstalled my system few times, used few different subversions of High Sierra... I even tried some strange methods like setting HorizontalSyncPulseWidth, since I read that it helped to some people. I just switched from HS to Mojave and from IntelGraphicsFixup to WhateverGreen, but that ugly glitch is still there. I even tried igfxrst=1which force drawing of Apple logo at 2nd boot stage instead of framebuffer copying, but it didn't helped. I tried using that switch with 10.13 2nd stage patch and without it. There is absolutely no difference whatever I try. Glitch lasts less than a second, but is very annoying. I will try to record a video and to upload it somewhere. I have no idea what else to try. EDIT: I just patched IOGraphicsFamily.kext/IOGraphicsFamily directly, but nothing changed (as expected). At least I can confirm that \x01\x00\x00\x75\x22 still exists in Mojave. EDIT2: I just found a post from RehabMan that states "The patch is not needed when using Lilu.kext + IntelGraphicsFixup.kext..." That explains why those patches not working for me. EDIT3: Video that shows described issue is in attachment. I cut first part of boot process and login prompt to make video smaller. Untitled.mov.zip
  4. You can't use those kexts on Mojave: IntelGraphicsFixup.kext IntelGraphicsDVMTFixup.kext Shiki.kext You need to use WhateverGreen with DVMT 32MB fix-up patch in your config instead. This patch needs correct DevicePath in order to work, so you need to find yours with gfxutil first. $ ./gfxutil -f IGPU DevicePath = PciRoot(0x0)/Pci(0x2,0x0) This is correct way to apply this patch Remove any other graphic patch that you have in your config. Do not use ApfsDriverLoader-64.efi and apfs.efi together. Same goes for HFSPlus.efi and VBoxHfs-64.efi. It is preferred to use ApfsDriverLoader-64.efi and HFSPlus.efi. At lest VBoxHfs is disabled in your config, but you need to remove apfs.efi. Your config looks like you added every patch that exists. Use only those that you really need. USBInjectAll.kext should not be used as a long term solution. As stated in USBInjectAll readme:
  5. I updated my macOS 10.13.6 to Mojave 10.14 Beta (18A337a) without any problem on my E7450 (model with discreet nVidia). Everything works, with some small issues. Some of those issues might be caused by VoodooPS2Controller (that I haven't used before), so I just switched back to ApplePS2Controller. Clover version: 4568 Injected kexts: Lilu.kext 1.2.6 WhateverGreen.kext 1.2.1 FakePCIID.kext 1.3.12 FakePCIID_Intel_HD_Graphics.kext 1.3.12 FakePCIID_XHCIMux.kext 1.3.12 FakeSMC.kext 6.26-344-g1cf53906.1787 ACPIBatteryManager.kext 1.81.4 AppleALC.kext 1.3.1 IntelMausiEthernet.kext 2.4.0d0 ApplePS2Controller.kext 1.5 Kexts in LE: DisableTurboBoostBattery.kext 2.1 AppleBacklightInjector.kext 0.9.0 BrcmFirmwareRepo.kext 2.2.10 BrcmPatchRAM2.kext 2.2.10 Legacy_Sierra_QMI_10.13.kext 1.4.0 WhateverGreen DVMT 32MB fixup patch (replaces IntelGraphicsDVMTFixup.kext): <key>Properties</key> <dict> <key>PciRoot(0x0)/Pci(0x2,0x0)</key> <dict> <key>framebuffer-fbmem</key> <data> AACQAA== </data> <key>framebuffer-patch-enable</key> <data> AQAAAA== </data> <key>framebuffer-stolenmem</key> <data> AAAwAQ== </data> </dict> </dict> You should check your graphics configuration and change Pci part to match your system if needed. This part is probably critical, since IntelGraphicsDVMTFixup will not work in Mojave. Only other Clover config change (compared to HS config) was removal of Inject Intel and other graphic patches (as suggested in some WhateverGreen thread on some other forum). I have external TP-Link UBS dongle (TL-WN725N), so I do not need Broadcom Wi-Fi kexts. Add them if you use Broadcom Wi-FI card. I need FakePCIID_XHCIMux and Legacy_Sierra_QMI in order to use DW5809e WWAN. Those are not needed if you do not have this WWAN or just do not want to use it. Most the issues that I noticed were related to keyboard and touchpad, so I reverted good old ApplePS2Controller. I absolutely need working Insert key. Other issues are software related. Some 3rd party icons are not always visible (TP-Link Wireless Utility, Logitech Control Center...) Caret (text currsor) is not always visible in Chrome address bar. It is invisible while key is pressed. It is shown on key release. It is very problematic when you need to change some text fast in address bar. Since I am using this for less than a day and my partition is freshly converted to APFS, I guess that SSD activity is related to spotlight indexing of my new drive. To summarize, Mojave works well on E7450. EDIT: Almost forgot. EAPDFix and CodecCommander are not needed since AppleALC now have full EAPD support for ALC293/ALC3235 and almost every other ALC model. EDIT 2: Flawlessly updated to Beta 9 (18A384a) with normal update. Haven't changed anything in kexts nor config. All Chrome Mojave related problems are solved with latest Chrome 69.0.3497.81. Latest Firefox 62.0 adopts Mojave color scheme. It is dark if you use dark Mojave appearance, and light if you are using light one.
  6. Let's try to communicate with device itself and check what we will get. If you device is used you might get a notification that resource is busy and you will not be able to use any of those commands. Since I haven't found a way to release previously used device under macOS I can only suggest you to restart your system and to open Terminal before trying to connect. Please note that delete doesn't work, so type commands slowly in order to avoid mistakes. If you made any mistake, just press enter and type whole command again. Restart your system, open Terminal and type: screen /dev/tty.wwan 115200 You will only get a cursor at top left corner. Type ATI5 and press Enter. You should get response from your modem. Something like this: Manufacturer: Sierra Wireless, Incorporated Model: EM7305 Revision: SWI9X15C_05.05.58.00 r27038 carmd-fwbuild1 2015/03/04 21:30:23 IMEI: 3X3XX605XX20XX2 IMEI SV: 18 FSN: FL5211XX23XX10 +GCAP: +CGSM OK Type AT!GSTATUS? and press Enter. You should get status report: !GSTATUS: Current Time: 5426 Temperature: 28 Bootup Time: 0 Mode: ONLINE System mode: LTE PS state: Attached LTE band: B20 LTE bw: 10 MHz LTE Rx chan: 6300 LTE Tx chan: 24300 EMM state: Registered Normal Service RRC state: RRC Idle IMS reg state: No Srv RSSI (dBm): -64 Tx Power: 0 RSRP (dBm): -93 TAC: 2XX5 (1XX73) RSRQ (dB): -9 Cell ID: 001XX8X0 (15XX2X2) SINR (dB): 2.6 OK What is your Mode? ONLINE, LOW POWER MODE or something else? Based on your PPP log I am 99.99% sure that you will not get LOW POWER MODE, but I want to be sure.
  7. @black.dragon74 I am very sorry, but looks like I jumped to conclusion (as usual). ROM value is actually masked before base64 encoding while I expected encoded value itself to be masked. I saw that SMBIOS values are set to XX-MASKED-XX, but I saw that ROM data is set to WFgtTUFTS0VELVhY, while I expected it to see XX-MASKED-XX there too. I thought it's base64 representation of newly generated ROM value, while it is actually base64 representation of XX-MASKED-XX. I would see that ROM value is changed if I was comparing config from archive with config I used to run a script, but I was already restored my original config just after script finished. Thank you for a great tool and sorry for a confusion I made.
  8. Hmm... Sat Mar 10 14:51:15 2018 : publish_entry SCDSet() failed: Success! Sat Mar 10 14:51:15 2018 : publish_entry SCDSet() failed: Success! Sat Mar 10 14:51:16 2018 : CCLWrite : AT\13 Sat Mar 10 14:51:16 2018 : CCLMatched : OK\13\10 Sat Mar 10 14:51:16 2018 : Initializing phone: ATE0V1&F&D2&C1S0=0 Sat Mar 10 14:51:16 2018 : CCLWrite : ATE0V1&F&D2&C1S0=0\13 Sat Mar 10 14:51:16 2018 : CCLMatched : OK\13\10 Sat Mar 10 14:51:16 2018 : Dialing: ATD*99***1# Sat Mar 10 14:51:16 2018 : CCLWrite : ATD*99***1#\13 Sat Mar 10 14:51:16 2018 : Waiting for connection Sat Mar 10 14:51:16 2018 : CCLMatched : CONNECT Sat Mar 10 14:51:16 2018 : Connection established Sat Mar 10 14:51:19 2018 : CCLExit: 0 Sat Mar 10 14:51:19 2018 : Serial connection established. Sat Mar 10 14:51:19 2018 : using link 0 Sat Mar 10 14:51:19 2018 : Using interface ppp0 Sat Mar 10 14:51:19 2018 : Connect: ppp0 <--> /dev/cu.wwan Sat Mar 10 14:51:20 2018 : sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x3b96a89d> <pcomp> <accomp>] Sat Mar 10 14:51:20 2018 : rcvd [LCP ConfReq id=0x0 <asyncmap 0x0> <auth chap MD5> <magic 0x465b0b6f> <pcomp> <accomp>] Sat Mar 10 14:51:20 2018 : No auth is possible Sat Mar 10 14:51:20 2018 : lcp_reqci: returning CONFREJ. This doesn't look like low power issue to me. I would say that it actually connects, but doesn't pass the protocol negotiation for some reason. I can see from your previous post that you are using Plus GSM. Have you tried to set your APN, but to left user and password blank as suggested? APN: plus Username: left blank Password: left blank btw. it's better to attach your log in your message, since some people would not bother to go to download host just to download your log.
  9. I am little paranoid about my serials, so I changed all of them first, since I didn't know that they are masked. At the end turns out that it actually was a good call, since manually entered ROM value in RtVariables is not masked. You can find debug archive in attachment. If you need anything else, just let me know. debug_8574.zip
  10. MiniDP works perfectly for me, even I am using MacBookAir7,2 without that patch. I just played Youtube video over both MiniDP and HDMI. Connects instantly on both and sound works without any problem. If you need any of my files for review, just let me know.
  11. Please go to System Preferences / Network, select your WWAN card, click on Advanced and go to PPP tab. Select Use verbose logging, apply everything and try to connect. Find and send your /var/log/ppp.log after that. Let's see what we can figure out from there.
  12. Before you give up, can you please check and post info about your card from Hardware / USB and Network / WWAN from System Information, so we can compare few things with info I am getting. Even I have different card (DW5809e) in different Dell laptop (E7450), some basic things should be same. Your card should be shown correctly in all of those places. My card is under USB 2.0 Bus inside Hardware / USB and info about it looks like this: Dell Wireless 5809e Gobi™ 4G LTE Mobile Broadband Card: Product ID: 0x81b1 Vendor ID: 0x413c (Dell Inc.) Version: 0.06 Speed: Up to 480 Mb/sec Manufacturer: Sierra Wireless, Incorporated Location ID: 0x1d180000 / 6 Current Available (mA): 500 Current Required (mA): 500 Extra Operating Current (mA): 0 Is your card shown under USB 3.0 or USB 2.0 Bus? Inside Network / WWAN I can see this info: WWAN Information: Dell_Wireless_5809e_Gobi____4G_: Device Version Number: 6 idProduct: 0x81b1 idVendor: 0x413c IMEI: 3535XXXXXX20XX2 IMSI: XX00XX00XX32XX4 locationID: 0x1d180000 @ 0 LOCK_STATE: UNLOCKED Manufacturer: Sierra Wireless, Incorporated Model: EM7305 Modem Software: SWI9X15C_05.05.58.00 r27038 carmd-fwbuild1 2015/03/04 21:30:23 Network Name: Unknown Serial#: 3X3XXXX53XXX9X2 WWAN_TYPE: GSM I am especially curios about your LOCK_STATE and Modem Software. Can you see your WWAN inside Network along with your Ehternet, WiFi and Bluetooth? Have you tried to use Default configuration without any Account Name or Password and empty APN?
  13. At the end I removed EAPDFix.kext and replaced it with CodecCommander.kext I had to modify Info.plist inside CodecCommander.kext, since there is no entry for my card ALC3235 (ALC293). <key>10ec_0293</key> <string>Realtek ALC3235</string> My codec dump is very similar to ALC292 dump (0x1a and 0x15 are basically same), so I just duplicated and adjusted ALC292 config. <key>Realtek ALC3235</key><dict> <key>Custom Commands</key> <array> <dict> <key>Command</key> <string>0x01a70724</string> <key>Comment</key> <string>Node 0x1a - Pin Control (In Enable / VRefEn)</string> <key>On Init</key> <true/> <key>On Sleep</key> <false/> <key>On Wake</key> <true/> </dict> <dict> <key>Command</key> <data> AVcIgw== </data> <key>Comment</key> <string>0x15 SET_UNSOLICITED_ENABLE 0x83</string> <key>On Init</key> <true/> <key>On Sleep</key> <false/> <key>On Wake</key> <true/> </dict> </array> <key>Perform Reset</key> <false/></dict> My speaker and headphones now works even after lid close.
  14. I hope that admins would not treat this post as off-topic, since purpose of this post is to help you and probably other people to change USBCOMP mode on their WWAN cards in order to use them under macOS. Looks like you do not have persistent storage enabled on your USB, you do not have universe repository added or both. If you have Windows machine, it's probably easiest to use LiLi (LinuxLive USB Creator). You can find instructions here. It is possible that persistent is not enabled by default, even if you created USB properly. You might need to check your grub config to see if persistent is enabled: /boot/grub/grub.cfg Your LIVE menu item probably looks something like this: menuentry "Ubuntu 16.04 LIVE" { set gfxpayload=keep linux /casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- initrd /casper/initrd.lz } Just add new menu entry that looks like this: menuentry "Ubuntu 16.04 LIVE persistent" { set gfxpayload=keep linux /casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash persistent --- initrd /casper/initrd.lz } In case it still doesn't work after all this, add universe repository and do update: sudo add-apt-repository universe sudo apt-get update
  15. I made a kext for HS based on what Hervé suggested to me, but card didn't work until I changed USBCOMP mode. You absolutely need to change card's USBCOMP mode (from Linux or Windows), since card can't work in macOS with it's default mode, even if kext is perfectly fine. I would recommend to set USBCOMP mode to 14, since that way card will work in macOS, Windows and Linux and you will probably not have to change it ever again. If you do not care about other OS, you can set it to either 14, 6 or 8 - all of them will work in macOS. It is probably easiest to change USBCOMP mode from Linux with swi_setusbcomp.pl script. Just use a Ubuntu USB stick with persistent storage and install those packages (even I am not sure if modem-manger-gui is actually needed): sudo apt-get install perl sudo apt-get install libuuid-tiny-perl sudo apt-get install libipc-shareable-perl sudo apt-get install modem-manager-gui Download script from here and run it like this: sudo perl swi_setusbcomp.pl --usbcomp=14 I changed PID value in my Legacy_Sierra_QMI_10.13.kext in order to make it work for you (in attachment), but it would only work after you change USBCOMP mode. Good luck. Legacy_Sierra_QMI_10.13.kext.zip
  16. When you press caps lock button for the first time, led on that button turns on and case is switched. When you press caps lock again, only thing that happens is that led turns off. Just try to remember that every time when you need to switch case, you should press caps lock button twice and you should be good.
  17. Few days ago I installed A18 for a quick test and I was prepared to restore A17 immediately, but everything works the same, so I decided to keep it. I have few slight issues, but those issues are same with both versions of BIOS. I also have a slight screen glitch on boot when progress bar is around 50%. It lasts about half of a second, but I still can notice it. Second stage boot patch just doesn't work for me. I am using 10.13 version of that patch (since I am on 10.13.2). I even tried to add new Clover flag HorizontalSyncPulseWidth (witch is introduced as second part of solution for that specific issue) with values of 100, 32 and 35, but none of them worked for me. I tired with Clover 4369 and Clover 4380. I have no idea what else to try, but you can try to use that patch alone or with HorizontalSyncPulseWidth=100 in boot params. Maybe it would work for you. I also have a slight problem with sound, but only if I close the lid when I am on battery. You can try to experiment with values inside EAPDFix.kext as Jake suggested to me to resolve similar issue. Brightness and trackpad works just fine here with both A18 and A17.
  18. I recently noticed that sometimes I have no sound. Everything starts to work as soon as I reboot. First thing that I suspected is that I have no sound after sleep. It turns out that if I choose Sleep from main menu, I have sound after wake, with or without power supply connected. Finally I figured out that if I close the lid while I am not on power supply, laptop goes to sleep (as expected), but I have no sound after wake. Everything looks correct in output screen even after sound stops working. I checked my config. Layout ID is 11 with Lilu and AppleALC and I have EAPDFix. Hibernation is properly disabled: System-wide power settings: Currently in use: standbydelay 10800 standby 1 womp 1 hibernatefile /dev/null powernap 1 gpuswitch 2 halfdim 1 networkoversleep 0 disksleep 10 sleep 1 autopoweroffdelay 28800 hibernatemode 0 autopoweroff 1 ttyskeepawake 1 displaysleep 10 lidwake 1 I am using patched files that Jake made from my origin while I was struggling with my first HS installation. Am I missing something obvious as usual? Should I try with patched files from latest E7450_Disable840M_A17_HS.zip instead?
  19. Thank you very much Hervé! I finally found some time for reading and experimenting and I successfully accomplished my goal to make DW5809e work in both High Sierra and Windows 10, since I have dual boot on E7450. Patch that you sent helped a lot. I might done some minor tweaks, but essentially I am using the same patch that you posted. Everything is actually very easy and can be done in few minutes when you have all information and when you know what you are doing. Funny thing is that for me it was easier to change USBCOMP mode from Linux then to make card properly loaded by OS. Looks like that use of FakePCIID_XHCIMux.kext instead of USBInjectAll.kext is always preferred way of solving issues with loading of internal USB devices. I found out that is better to use USBCOMP=14 instead 6 or 8, since it sets both 6 and 9 in same time. MacOS will use 6 and Windows 10 will continue to use cards default USBCOMP mode which is 9. Card debranding is not needed and I would not recommend it. I had to set APN, Account Name and Password manually. Connection is stable, but speed test shows only about 10 Mbps. I will need to investigate this. Also, I am not sure why network name is listed as Unknown even when I am connected. btw. looks like you were one of those lucky guys with high speed modems. I remember downloading a single 800x600px GIF image for 5 minutes at 2800 bauds.
  20. In previous post I sent you my complete Clover folder with all 3 file system drivers: HFSPlus.efi, apfs.efi and NTFS.efi (you would probably only need HFSPlus), patched files for E7450 that have both graphics and config that use those patches. All needed HS patches and drop tables are also properly added to that config. That should boot on any E7450 that have both graphics without any problem, as long as BIOS version is A17, USB device and used USB port works, USB is properly prepared and BIOS is correctly set. Since I was struggling with some issues myself when I installed HS for the first time, I would advice you to check all those things: 1. Are you sure that your E7450 have both intel and nvidia graphics and not only intel? If you only have intel you need different boot pack then those I sent. If you are not sure and do not have Windows installed, run some live Linux from USB and check. 2. Are you sure that you use A17 bios and not A15, or A18 that just came out? I don't know if A18 works since I haven't tried it yet, so please use A17. 3. Have you reset your BIOS to defaults and set necessary options? Check your BIOS. A17 should be displayed in System information. Load Defaults and set Boot List Option to UEFI, SATA Operation to AHCI and Enable Legacy Option ROMs. Do not apply DVMT patch, use IntelGraphicsDVMTFixup.kext (already in both, latest bootpack and in archive I sent). 4. Are you sure that your USB stick and ports works properly? Try to use another USB port and (or) another USB stick. 5. Are you sure that your USB is properly prepared? Try to remove everything and made new USB install from scratch.
  21. @quartz38 Few days ago I reinstalled HS 10.13.2 from scratch. Booting from USB and installation went without any problem. I took complete Clover folder from my USB, packed it and attached it for you. Please note that this one is not the same one I already sent to you over private message, which I made from latest generic EFI and latest bootpack that Jake posted. This one is slightly different, with different set of patched files. Those are also patched by Jake, but origin folder was from my machine. One of those should work on your machine. I guess it would be easiest to Mount EFI partition of your USB, delete complete Clover folder there and just paste this one from attachment. Just to be sure that everything is in right place. Also, please check those few things: 1. Check if this option is enabled in your BIOS. It must be turned ON 2. Use F12 every time during installation and be sure that you actually booting from USB 3. Check the Clover version (in the right bottom corner) and boot from USB 4. There will be two noticeable delays during boot. 5. After almost 2 minutes you should be on this screen Good luck! CLOVER_7450_HS.zip
  22. I reinstalled everything from scratch, but problem remains. Looks like some other people have similar problem on their macs https://discussions.apple.com/thread/8097885
  23. HS just require some different patches and more values set in config than old versions, but everything is basically the same. Installer structure is changed a little, but it should be still possible to use old mount/copy/paste method of creating USB if you want. I honestly prefer new method since it's faster and more clear (at least for me). Just use right version of bootpack that match your system and follow Jake's guide.
  24. Basically it's almost identical as Jake's bootpack, but I compile it myself. Some kexts are slightly newer then those from Jake's bootpack, config is slightly modified, but there is no real difference, since config and patches are made by Jake, with same selection of kexts. Since I had a lot of struggle in the beginning myself, I can tell you few things. Restore BIOS defaults, there is no need for that patch anymore (there is a kext in bootpack for that). Be sure that you are using UEFI and Enable Legacy Option ROMs. Create USB with createinstallmedia from terminal, do not use old method. If you already have Clover on your drive, during all install steps press F12 every time and select USB from boot menu - this one made me a lot of headaches. Follow Jakes instructions (just ignore everything related to updating of Sierra bootpack): https://osxlatitude.com/index.php?/topic/8506-dell-latitude-inspiron-precision-xps-clover-guide/?p=74275 Use this EFI https://osxlatitude.com/index.php?app=core&module=attach&section=attach&attach_id=16017 and this bootpack (if you have NVidia) https://osxlatitude.com/index.php?app=core&module=attach&section=attach&attach_id=16036 or this bootpack (if you have Intel only and do not have NVidia) https://osxlatitude.com/index.php?app=core&module=attach&section=attach&attach_id=16209 Please boot with verbose, until you finish installation.
  25. It is perfectly normal if progress bar not moving during booting of HS installation from USB for about 30-60 seconds. Please use verbose and if it looks that nothing happens after RAM disk initialization, please wait a little. It should continue after some time. Please have a little patience, but If it is stoped for more that 90 seconds, something is probably wrong.
  • Create New...