Pressing 'e' on Grub to pass a command boots my Debian system, how to make it permanent?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Pressing 'e' on Grub to pass a command boots my Debian system, how to make it permanent?
Hello LQ.
I'm having some issues with Debian Testing 'Stretch'.
This only happened when I installed a 'PolicyKit' to get an application running.
I have Gnome3 and XFCE installed, but currently only use XFCE due to low RAM - for now.
Since I don't have Plymouth installed, I get past Grub and Disk check then a black screen, I've done some research and found a temporary fix, by adding "video=LVDS-1:d" to the command list with 'e' on Grub it boots and lets me log in, I'm not sure why? Something to do with Xorg?
I'm looking to add this command into a file, so it's permanent on Grub, I looked in /etc/default/grub but adding the command in there does nothing.
Please help me.
40 custom is where you put custom menuitem stuff.
located
Code:
userx@voided1.what~>> ls /etc/grub.d
00_header 10_linux 20_linux_xen 30_os-prober 40_custom 41_custom README
inside file can look like this
Code:
userx@voided1.what~>> cat /etc/grub.d/40_custom
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry 'Slackware Linux (Slackware 14.2) (on /dev/sda1)' --class slackware --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-fa98942f-4219-4f0c-a9b1-0c3e2eda77e8' {
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 fa98942f-4219-4f0c-a9b1-0c3e2eda77e8
else
search --no-floppy --fs-uuid --set=root fa98942f-4219-4f0c-a9b1-0c3e2eda77e8
fi
linux /boot/vmlinuz-huge-4.4.23 root=/dev/sda1 ro
}
Now I just need to figure out why the 'PolicyKit' is giving me a black screen, although it could be many other problems since I did a whole system upgrade and dist-upgrade as well, and I'm not sure how to output debug info on the screen, and the keyboard is non functioning so I can't drop to a login with Alt+F2
Now I just need to figure out why the 'PolicyKit' is giving me a black screen, although it could be many other problems since I did a whole system upgrade and dist-upgrade as well, and I'm not sure how to output debug info on the screen, and the keyboard is non functioning so I can't drop to a login with Alt+F2
I have not played with policyKit in a long time. you have to look through it and look for user permissions user or root, hold on let me look into my archive. This is only an example taken from when I ran Debian. This was for automounting
you have to find the right pkla file or create your own in the proper directory. Sometimes you will even have to create the proper named directory first then put in it the properly named file with whatever needs to be inside it to get it to work.
search linux policykit and perhaps add words that describe what you're wanting to do with it.
NO KEYBOARD -
that maybe something else, kernel related.
I'm having some issues with Debian Testing 'Stretch'.
it's called testing for a reason.
if you're not familiar with the debian updating process (from a cursory glance at your writing i'd say something went more than just a little wrong), and if you are not aware of the implications behind that 'testing', you shouldn't use it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.