qaz@lemmy.world to Programmer Humor@programming.devEnglish · 12 days agoPeak homelabbinglemmy.worldimagemessage-square32linkfedilinkarrow-up1624
arrow-up1624imagePeak homelabbinglemmy.worldqaz@lemmy.world to Programmer Humor@programming.devEnglish · 12 days agomessage-square32linkfedilink
minus-squarefuckwit_mcbumcrumble@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up130·12 days ago not turning off going to sleep when lid closed Rookie maneuver.
minus-squareStovetop@lemmy.worldlinkfedilinkarrow-up80·12 days agoCould be an overheating concern maybe. Some laptops weren’t designed to run with the lid closed, if it inhibits the air flow.
minus-squareover_clox@lemmy.worldlinkfedilinkarrow-up93·12 days agoAs right as that might be, it’s on carpet! I don’t believe they put much thought into airflow and overheating…
minus-squareMajorasMaskForever@lemmy.worldlinkfedilinkEnglisharrow-up9·12 days agoI can’t tell for sure, but it looks like a Lenovo y510p. Or at least it looks very similar to the one I owned back in the day. There was a vent in the hinge, and these things would absolutely cook themselves with the lid closed
minus-squarezourn@lemmy.worldlinkfedilinkarrow-up3·12 days agoI’m currently using a y510p as a home lab. Every update resets the shutdown-on-lid-close setting. Had to set up a cron job to re-disable it on boot.
minus-squareWhyJiffie@sh.itjust.workslinkfedilinkEnglisharrow-up1·11 days agoI’m pretty sure there is a regular systemd config option for that
Rookie maneuver.
Could be an overheating concern maybe. Some laptops weren’t designed to run with the lid closed, if it inhibits the air flow.
As right as that might be, it’s on carpet!
I don’t believe they put much thought into airflow and overheating…
I can’t tell for sure, but it looks like a Lenovo y510p. Or at least it looks very similar to the one I owned back in the day.
There was a vent in the hinge, and these things would absolutely cook themselves with the lid closed
I’m currently using a y510p as a home lab. Every update resets the shutdown-on-lid-close setting. Had to set up a cron job to re-disable it on boot.
I’m pretty sure there is a regular systemd config option for that