Having trouble rotating console screen

4 replies [Last post]
Patrick Mc(avery
Offline
Joined: 08/15/2011

Hi Everyone

I used to be able to rotate my Linux console so that if I typed ctrl-alt
F1 thru F6, I could access virtual terminals that were also rotated
vertically with my monitor.

I tried to run this:

sudo update-grub

And I am getting errors.

I altered my /etc/defalt/grub file before running update. Now I am not
sure if this is my error or something that is wrong otherwise.

If you have time, could you run sudo update-grub and let me know if you
have errors?

Here is my file, perhaps you can spot the error? I added the
"fbcon=rotate:1" part

Thanks for reading-Patrick

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX="fbcon=rotate:1"

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux-Libre (no patch required) and with any kernel
that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to
Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

# Trisquel comes without kernel recovery entries to improve security.
GRUB_DISABLE_RECOVERY=true

Magic Banana

I am a member!

I am a translator!

Offline
Joined: 07/24/2010

What are the errors you get?

Patrick Mc(avery
Offline
Joined: 08/15/2011

On 18-04-10 10:50 PM, name at domain wrote:
> What are the errors you get?

I have copied the results below,

I commented out the GRUB_HIDDEN_TIMEOUT at one point and this warning
went away but the error at line 203 is still there. The grub file that I
altered does not have a line 203

thanks

sudo update-grub
[sudo] password for patrick:
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when
GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Found linux image: /boot/vmlinuz-3.13.0-141-generic
Found initrd image: /boot/initrd.img-3.13.0-141-generic
No volume groups found
Found Slackware Linux (Slackware 14.2) on /dev/sda1
Found Trisquel GNU/Linux 7.0, Belenos (7.0) on /dev/sda2
Found Slackware Linux (Slackware 14.2) on /dev/sda3
error: syntax error.
error: Incorrect command.
error: syntax error.
Syntax error at line 203
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached.

Magic Banana

I am a member!

I am a translator!

Offline
Joined: 07/24/2010

It must be line 203 of /boot/grub/grub.cfg.new which is generated from /etc/default/grub and /etc/grub.d/* and would have become /boot/grub/grub.cfg if 'update-grub' had succeeded. Could you attach /boot/grub/grub.cfg.new ?

Patrick Mc(avery
Offline
Joined: 08/15/2011

Thanks again for responding to my post.

I don't know why I did not look at this file before posting, duh !

I know what is going wrong now. I posted awhile ago about how I was
trying out Salix because I did not want systemd and that I was sad to go.

I haven't gone. I am tri-booting at the moment but in reality only using
Trisquel.

Something is going wrong during the file generation. The
"fbcon=rotate:1" is ending up without a closing double quote.

This is a bug if it's worth looking into.

For me, the problem is solved. I am going to re-install with just
Trisquel. I have all of my data on another drive so it's easy to do.

Please see line 203 and the lines that came before it.

Have a great day-Patrick

submenu 'Advanced options for Slackware Linux (Slackware 14.2) (on
/dev/sda1)' $menuentry_id_option
'osprober-gnulinux-advanced-e0197120-d089-49cd-9fe9-2f9e42042ca3' {
menuentry 'Salix (on /dev/sda1)' --class gnu-linux --class gnu
--class os $menuentry_id_option
'osprober-gnulinux-/boot/vmlinuz--e0197120-d089-49cd-9fe9-2f9e42042ca3' {
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 e0197120-d089-49cd-9fe9-2f9e42042ca3
else
search --no-floppy --fs-uuid --set=root
e0197120-d089-49cd-9fe9-2f9e42042ca3
fi
linux /boot/vmlinuz root=/dev/sda3 ro quiet vt.default_utf8=1
vga = normal append ="fbcon=rotate:1 vt.default_utf8=0
}
}