C172 pilot reported failing to activate runway lights with multiple approach efforts resulted in violation of safe altitude over populated areas.

Narrative

On arrival at L22 at approximately XA:20 local; I was unable to activate the pilot-controlled lighting. I am quite certain I was on the correct frequency XXX.X; and I've looked again for NOTAMs and didn't find anything.I was able to locate the airport using GPS and OBS mode; but on my first attempt saw the runway too late and initiated a go around. Similarly on my second attempt I located the airport but was too far right and made a second go around. On the third attempt I landed.On reviewing my flight track; during the second go around my GPS altitude indicates that I was 20 feet above a road between houses adjacent to the airport. I then climbed and my logs indicate I crossed over a house at the end of the road at 50 feet.At landing the track log indicates a GPS altitude of 3170 ft; while the airport datum 3224 ft. I therefore believe there is a 50ft difference between my GPS altitude and true altitude. During both go around executions I had the runway in sight; and it did not feel I was as low as 20 feet. Regardless; it was far lowered than I had intended to be; and my situational awareness of the houses to the south of the runway was limited. The go-around was late; and I was slightly conservative with the power due to my awareness of noise abatement. (This was my mistake; as safety trumps noise abatement).In hindsight; I should have diverted to PSP after not being able to activate the pilot-controlled lighting. I got lucky.Contributing factors include the early sunset due to the mountains (sunset was XB:52 local; but at XA:20 it was already dark); and earlier mechanical issues with a different plane that delayed my departure by 2 hours.In addition to my own leanings; I will contact the airport regarding the lighting.