/fglt/ - Friendly GNU/Linux Thread

journalctl -b -1

Will show you the logs from your entire last boot, scroll to the very bottom and you will likely see why it hung.

well I used gsettings list-schemas and it seemed to be the only one that had anything to do with desktop bacgrounds, I'll check again though

yea so I checked again and there doesn't appear to be a schema other than the org.gnome one which has anything to do with desktop backgrounds

Did you try this?

askubuntu.com/questions/380550/xubuntu-how-to-set-the-wallpaper-using-the-command-line

So I want to build and install new kernel on an old Debian laptop, so I don't need many features present in default kernel.

I followed this manual and compiled the kernel on my main rig in a user folder cyberciti.biz/tips/compiling-linux-kernel-26.html up until "sudo make modules_install", as I understand this will actually install kernel on my main rig.

So how do I install this kernel on my laptop now? Do I put it on a thumbrive, plug it into a lappy, cd into the kernel dir and run all of those commands after the "sudo make modules_install"?

How can I add an option to boot into older kernel in Grub in case something fucks up?

I'm not sure of what i'm supposed to see

Attached: 1512667793762.png (1128x261, 186K)

>39 output lines suppressed due to ratelimiting

lol idk
Maybe that's the network driver error from your first screenshot.

Is it compiled as a module? You can try to rmmod that shit before shutdown to see if its causing the hang. Its likely a known issue with a real solution if that is actually the problem, in which case you can probably just google it.

>in which case you can probably just google it
I have found nothing, that's why i came here...
But I will google for "rmmode" cause I don't understand..

Attached: 1530034078294.png (726x1006, 694K)

make modules_install will only install the kernel modules, you need to copy the kernel itself to /boot and configure grub it. You'll also probably need to generate an initramfs.

Debian probably has an official guide for how to do this, judging from your url
>linux-26
that's pretty old, don't follow that guide.

I would try and read the extra output that was suppressed or whatever.
journalctl -u systemd-shutdown

Might show it.