I'm trying to compile a custom Linux Kernel but when I get to the last step and compiling VMLinux.o,
the make process gets killed and shows error137, which means that I'm out of memory.
I'm on 4gb RAM, a core2duo and have compiled Kernels before without any issues.

The issue started when I was editing make menu config so I must have done something that makes the compilation require more RAM.
i've already tried ''make -j1'' to compile the Kernel but I still get the same issue.

(P.S I'm doing it from an live image of Linux Mint so I don't have a swap partition but that hasn't been a problem until now.)

yes, especially optimization may require a lot of RAM. Anyway, if you can add swap try it. and shut down anything else (if possible). Even you can try it without GUI.

1 members found this post helpful.

Worked, all good now except when i'm trying to ''ip link'' to my ethernet/wi-fi i can't find any of them. What part of the ''menuconfig'' is used in order for eth0/wi-fi to show up, do you know?

Does ip link throw an error? Also, make sure you enabled support for IPv4/IPv6 and Ethernet, and if they are built as modules, make sure they're locked and loaded. Well, I mean, preferably not locked but you get the idea.

I think it comes under Drivers. You need to include the specific drivers for your cards. lspci -v should show you what they are.

I was always told that network drivers should be compiled and loaded as modules, not built in, because sometimes they need to load firmware which might not be available until the root filesystem has been mounted. But I don't know if that still applies

That's what I do with my network drivers that aren't the default TCP/IP stack or Ethernet drivers. I keep those baked in because I once had a bad experience and needed them.

In addition to hazel's tip about using lspci -v, check the "Kernel driver in use field" and "Kernel modules" and see if you did in fact build them, but they aren't working for some reason. Might save you a rebuild.