Contribute
Register

Mojave 10.14.5 installation on LG gram 17 stuck

Status
Not open for further replies.
One more question... for any of you that has gotten this to work. Has anyone been successful with a Costco version of the product? The updates from the LG Update program are different versions for myself and some others than what's listed by rdmitry, which makes me wonder if the BIOS might be different too. The model number is slightly different. It's 17Z990-R.AAS7U1. The non-Costco version is 8U1. My BIOS is W1ZD1210 X64 and SMBIOS is 3.01. I can't figure out what I need to change to force it to look for updates for the standard rather than Costco model. At least this would explain why some of us can't get this to work. Thanks.
 
As a bit of an update for @Bobrz and others still struggling, one thing I've discovered is that you need (or at least *I* needed) to use a m.2 SATA drive, not an M.2 NVMe drive for your initial install. It's taken me a month, but I finally have an at least partially working system, and I'm finishing up the install now and moving on to a 15" gram for my wife.
 
It's taken me a month, but I finally have an at least partially working system, and I'm finishing up the install now and moving on to a 15" gram for my wife.

Okay, make that an essentially fully working system. I needed to download the driver for my TPLink T2U Nano to get WiFi working, but now everything is working great, with the limitations noted earlier in the thread. I also can't get Messages/FaceTime working (despite checking all the usual suspects), but I don't really ever use them anyway, so I'm not too concerned.

Also, @Bobrz seems to be concerned about not getting the same updates from LG, but I only had a single update from LG, and the problem was solely the NVMe vs. SATA issue.
 
Last edited:
UnknownWraith,

Thanks for the help. By any chance, did you try installing to an external drive? I figured NVMe would be a problem, so my logic was to try to install to an external and then move it all over once I had a success. Not having any luck with that either. I've tried two different machines, so it's not that. Any special boot options?
 
I answered my question. Trying to install to a USB drive was the problem. I didn't have an extra m.2 sata drive laying around, so I thought I'd install to a USB drive then move the install to the NVMe drive I bought for this. As soon as I tried installing directly to the internal drive I had a success. Now I just have to figure out how to make it bootable then install the NVMe driver. I said early on that I hadn't done a Hackintosh for a long time, and things have changed. It was a heck of a learning experience. UnknownWraith, a special thanks to you for your help. Your 2nd post is what got me thinking of the USB drive.
 
@Bobrz No problem. Sorry I didn't have a chance to get back to you earlier. OS X won't let you use an external drive as a system drive. It's been that way for a loooong time. To make a drive bootable, simply install Clover onto it. Make sure you clone your Clover config to the drive you want to boot from and tell OS X/Clover to always boot from the last booted volume (unless you change it during the countdown).
 
UnknownWraith, I guess I got tripped up by what I'm used to. I've got a 2010 MBP (unibody) and it's no problem on there. Done it many times. Anyway, a couple more questions for you if you're kind enough for a little more help.
1. What did you use to get the touchpad working? Mine does nothing currently. From what I've seen there are several different kexts around for this, but I'm soooo tired of experimenting with this thing. If it wasn't such a nice computer I think I would've thrown in the towel.
2. You mentioned installing to a non-NVMe drive initially. I've done that. What was your process for installing to the NVMe drive afterwards?
And sincerely, thanks for the help. It's really nice having someone willing to take a little time to help.
 
@Bobrz I didn't have to do anything to get the trackpad to work. It's an I2C trackpad, so it should work just fine, provided you're using the correct kexts (VoodooI2C and VoodooI2CHID). Make sure you have used the last Clover config zip file, not the first one, as the original one didn't have the trackpad working yet. I have noticed that it has occasional hiccups and isn't 100% supported for 3 and 4 finger gestures, but it does basic 1-3 finger gestures fine, other than occasionally needing you to lift your finger and try to move the cursor again (I think it's some kind of odd focus issue, since the cursor vanishes when you're typing). It's possible that this is because of conflicts between VoodooI2C and VoodooPS2, which I've heard of in the past, but it appears that the keyboard is PS/2, so you need VoodooPS2 unless you're using an external keyboard. I will eventually experiment and confirm that's the case, but I'd say it's about a 97% chance it is, and while it's annoying, it's not generally more than a nuisance.

As for the NVMe drive, my system drive is a high-end 500GB m.2 SATA drive and I've got a 500GB 970 EVO Plus NVMe drive that I'm currently using as a data drive. The SATA drive is fast enough that my applications all load for the frist time without any real wait (after the first load, times are cut in about half); the worst offenders being my development IDE (4 seconds, including loading last used tabs), CAD software (7 seconds including loading a file with two complicated parts), and FCP (11 seconds, including loading a simple project with some plugins used). I'm sure that I could just duplicate the system drive onto the NVMe drive, but I just don't see the need, personally (it's more effort than it's worth, IMHO). If I need a larger data drive, I can always swap it out (though that'd probably be for a huge video project, which I'd more likely just use an external thunderbolt disk array for, and use proxy clips on the fast 500GB drive for everything but final render). With 40GB of RAM (you can swap the 8GB module for a 32GB Samsung M471A4G43MB1-CTD module and then tell Clover you have 2 16GB M471A4G43MB1-CTD modules @ 2400MHz, plus the soldered-on 8GB using the info you see for the manufacturer "0" DIMM out of the factory, which isn't really a DIMM), the system drive is really just used to load programs and data that doesn't benefit from the faster drive (video goes on the faster drive), since the machine doesn't need to use swap space (which you don't really want to be used on a SSD anyway).
 
Last edited:
UnknownWraith, thanks. Got the trackpad working. On the drives, are you saying you can have a mix of SATA and NVMe in the same system? I thought I'd seen elsewhere that you couldn't mix the two. That'd make things easier. I've got a road trip today, but I'll be fooling around with this more over the next few days. All I've really got left is to make the existing drive bootable, then get everything over to the NVMe drive. This is all pretty exciting. The Gram is a really nice machine, other than coming with Windows. Of course, the next challenge will be getting it to run Catalina, but I think I'll just bask in Mojave for awhile. Thanks again for the help. Hopefully I'm done after these few tasks I mentioned, but keep an eye out for a bit, ok? You've been more help than anyone else here, and I appreciate it. Wish I could return the favor. Out of curiosity, are you running a Costco version or a regular?
 
It's possible that this is because of conflicts between VoodooI2C and VoodooPS2, which I've heard of in the past, but it appears that the keyboard is PS/2, so you need VoodooPS2 unless you're using an external keyboard. I will eventually experiment and confirm that's the case, but I'd say it's about a 97% chance it is, and while it's annoying, it's not generally more than a nuisance.

Just to update, I did look at ioreg and the keyboard is definitely PS/2. Unfortunately, VoodooPS2Controller registers an ApplePS2MouseDevice, whether or not your system has a matching device, and I believe that's what causes the weird trackpad hiccups (I've read in the past in other threads that having both registered can cause conflicts that create the system to sometimes not register your finger on the trackpad; short of using an external keyboard or mouse and removing the other device's kext, I haven't heard of a way to fix this conflict).
 
Last edited:
Status
Not open for further replies.
Back
Top