Pressing 'e' on Grub to pass a command boots my Debian system, how to make it permanent?

Conch · 11-12-2016, 08:03 AM

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.

Kind regards,
Conch.

BW-userx · 11-12-2016, 08:06 AM

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
}

Conch · 11-12-2016, 08:18 AM

Thank you BW-userx!

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

BW-userx · 11-12-2016, 08:57 AM

Quote:

Originally Posted by Conch

Thank you BW-userx!

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

Code:

#[Allow Automount]
#Identity=unix-group:plugdev
#Action=org.freedesktop.udisks2.filesystem-mount
#ResultAny=yes
#ResultInactive=yes
#ResultActive=yes

[Allow Automount]
Identity=unix-group:plugdev
Action=org.freedesktop.udisks2.filesystem-mount*
ResultAny=yes
ResultInactive=yes
ResultActive=yes

[Allow Eject]
Identity=unix-group:plugdev
Action=org.freedesktop.udisks2.eject-media*
ResultAny=yes
ResultInactive=yes
ResultActive=yes

[Allow Mounting of fstab]
Identity=unix-group:plugdev
Action=org.freedesktop.udisks2.filesystem-fstab*
ResultAny=yes
ResultInactive=yes
ResultActive=yes

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.

ondoho · 11-12-2016, 09:38 AM

Quote:

Originally Posted by Conch

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.

goumba · 11-12-2016, 09:47 AM

The Debian way to do this would be to run dpkg-reconfigure

Code:

dpkg-reconfigure grub-efi

or grub-pc for older BIOS based PCs.

Add your kernel parameter when it prompts for the "Linux command line".

That will make sure it gets permanently added in the right place, and it will also update the grub configuration file for you.