grub boot parameter to

[Bashing-om]

Hello people; I have a good one .

Where is the boot parameter reset ?
And what is the meaning of 'to' ?
The kernel boot line from /var/log/Xorg.0.log:

[ 54.546] Kernel command line: BOOT_IMAGE=(hd0,msdos1)/vmlinuz root=/dev/sda1 to

confirmed to be 'to' "

sysop@1404mini:~$ cat /proc/cmdline
BOOT_IMAGE=(hd0,msdos1)/vmlinuz root=/dev/sda1 to

Whereas the boot directives have 'ro' set:
/etc/fstab:

UUID=3a47f1f1-ed1f-4134-b6aa-be101a7d97b4 / ext4 errors=remount-ro 0 1

And in /boot/grub/grub.cfg

linux /boot/vmlinuz-3.13.0-100-generic root=UUID=3a47f1f1-ed1f-4134-b6aa-be101a7d97b4 ro text

My google-fu is failing me in this respect .

when all else fails

ask on the forum

[yetimon_64]

Hi Bashing-om,
I would suggest you check the file /etc/default/grub and check the line GRUB_CMDLINE_LINUX_DEFAULT or the line GRUB_CMDLINE_LINUX doesn't have a typo in it. I suspect there may be a typo somewhere as "r" and "t" are beside each other on the keyboard. I too have never seen "to" as a boot parameter.

If there is a typo in /etc/default/grub the xorg log you see "to" in may be picking it up as an error.
Regards, yeti

Edit: I would also suggest you double check any files in /etc/grub.d you may have at any time altered (if you have ever done so, that is)

[halogen2]

Normally the ro parameter comes from /etc/grub.d/10_linux so you might check there as well.

[Bashing-om]

yetimon_64; halogen2; Thanks guys.

This has really got me . And spurs on my thirst for knowledge.

I Find no faults in /etc/default/grub :

GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=false
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR="My-Work-14.04"
GRUB_CMDLINE_LINUX_DEFAULT="text"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (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,0xe fefefef"

# 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=1600x900

This configuration has worked well for a long period of time - huuuummm come to think of it -
I did not notice the 'to' until the new -100 kernel install . Will boot an older kernel and see .

Nor have I messed with the config files in /etc/grub.d/ in a very long while . But will take the time to look through them .. but, as the file /boot/grub/grub.cfg is clean I do not expect to find any errors .

This is on a 14.04 minimal solid/stable install with xfce as the DE. Be also aware that I have a too new graphics card that has no support in 14.04 and loading the vesa driver .

to Who is this masked man ?

an itch

I just gotta scratch

[yetimon_64]

...to Who is this masked man ?

an itch

I just gotta scratch

That has got me "scratching" my head as well .

I just looked at the kernel parameters available on kernel.org --here--, and no mention of any "to" parameter. "ro" is listed though.

But will take the time to look through them

I suggest you go straight to the file /etc/grub.d/10_linux for checking as I think halogen2 is correct about that being where that kernel parameter is set from. That may quicken your search up a bit, hopefully.

Edit: I just noted the "text" setting in the GRUB_CMDLINE_LINUX_DEFAULT line and am wondering if it means "text only". It may be related to that in some way ?

[Bashing-om]

@ yetimon_64;

Yeah ; I have spent several hours on this and have expended my google-fu. I have yet to find any hint what 'to' is.

And yes too on to= (t)ext (o)nly . I look over this system quite a lot and this is the 1st time this boot parameter has come to my attention.

Will continue to investigate, see what I can find out .
Will reboot with older kernel and will look through grub's config files ; and then report my findings.

together we can