[SOLVED] Confusing Local Time

[tinypoodle]

You can use "vga=ask" to see if the kernel will prompt you at the very beginning of boot.

[Rich]

Hi ordep
When you enter your boot codes at the boot prompt, you need to enter   tc tz=whatever vga=whatever
After you have booted, entering   showbootcodes   at the command line will show you if your boot
codes where seen.

[coreplayer2]

I'm confused, isn't Philippine Time  +8 hours  (not -8 hours) ??

[tinypoodle]

"-" in tz means ahead of UTC.

[curaga]

Just to be sure, you mean bootcodes entered in the installer window don't get passed? (and not those entered for the live cd session, at the cd's boot prompt)

[ordep]

Just up from a bad bout of flue.

OK then:

-- Booting from the live CD with bootcodes "noutc tz=PHT-8 vga=791" brings up TCL
-- with these settings showing correct Manla time and resolution.

-- Installing TCL to a USB flash drive with bootcodes "noutc tz=PHT-8 vga=791"
-- installs TCL correctly with those codes and when booting from flash
-- drive time is set correctly to Manila time and resolution.

-- Installing TCL to a hard drive with bootcodes "noutc tz=PHT-8 vga=791"
-- installs TCL with time set to UTC and incorrect, unusable large
-- resolution.

-- Installing TCL from the flash drive to the hard drive with bootcodes
-- "noutc tz=PHT-8 vga=791" installs TCL with time showing as PHT, however,
-- 8 hours off and correct resolution. Time can easily be corrected with
-- command "date -s "HH:MM". showbootcodes shows none of the given codes.

I cannot show the bootcodes in HD installation since I am running now TCL
on the HD from the flash drive install which I would have to destroy again with a new
install from the CD since booting from the CD it will always mount the HD
TCL partion which I am not able to unmount. 

If I know how to boot from the CD w/o mounting the TCL HD partion I can make
an install on another partion. TCL will not install if on a given drive a partion
is mounted.

[tinypoodle]

Compare your bootloader config files.
Boot code "base" to prevent automounting.

[curaga]

I'll leave the bug in the installer for Brian.

Please edit your bootloader config file directly, no need to do repeat installs.

[ordep]

Found the file I had saved the bootcodes of HD install:

$ showbootcodes
BOOT_IMAGE=TCL-sdb9 ro root=819 quiet vt.default_utf8=1

Given codes

noswap noutc tz-PHT-8 vga=791

are all missing unlike in flash drive install or on CD boot. they show with "showbootcodes" command.

[Juanito]

..which would tend to indicate that your hd install is not reading the boot codes from where you expect...

[tinypoodle]

Found the file I had saved the bootcodes of HD install:

$ showbootcodes
BOOT_IMAGE=TCL-sdb9 ro root=819 quiet vt.default_utf8=1

It appears to me you have some rather uncommon boot codes there, are you sure about those?
Why would you want to use "ro" with tc??

[ordep]

I made a new install from the CD booted with "base" to a new partition on the drive. The only codes given were those already mentioned and the outcome is the same. The codes are not acted on. I did not put "ro"
or anything else that shows in showbootcodes.

[curaga]

Those bootcodes definitely don't come from our installer. Do you have an old install somewhere, made by a third party util?

[ordep]

Those bootcodes definitely don't come from our installer. Do you have an old install somewhere, made by a third party util?

Nothing of that sort. I made at least 6 installs of TCL always on a newly formatted partition and now once more on another partion.

On that drive I have my working box Salix and VL7 for testing. It is a brand new SATA drive.
On a second IDE HD I have the latest KNOPPIX installed.

[tinypoodle]

While you get the output of 'showbootcodes' as posted above, what is the output of 'uname -a'?