Long Boot Times after Remaster

[newtotinycore]

TC 4.7.4 on old pentium 4

After using ezremaster and  tc-install to usb, new tc install works just like original.
However, at boot-up, after reaching the "Syslinux 4.0.5 EDD..." copy-rite page, there is an additional 5 minute pause before booting (compared to original tc system).
This has occurred twice.
Any ideas?

Thanks,
Bob

[Rich]

Hi newtotinycore
You might want to at least post your  syslinux.cfg (or is it extlinux.cfg) file.
Sounds like you set the timeout to 300 seconds.

[newtotinycore]

Hi Rich,
Here is my extlinux.conf file:

DEFAULT core
LABEL core
KERNEL /tce/boot/vmlinuz
APPEND initrd=/tce/boot/core.gz quiet  waitusb=5:UUID="b6660f18-311a-42cd-a016-f233b04a8a53" tce=UUID="b6660f18-311a-42cd-a016-f233b04a8a53"

I guess that "waitusb=5" means a 5 second wait?
My remastered tc has a very close to 5 minute delay compared to the original tc.
I haven't made any changes in the default values, anywhere.
Maybe, there is some default value being imported by ezremaster?

Thanks,
Bob

[Rich]

Hi newtotinycore

I guess that "waitusb=5" means a 5 second wait?

That's correct.
I don't see anything wrong in the config file. What changes did you make that required a remaster?

[newtotinycore]

Hi Rich,
The remaster is a very basic system to see how things work out.
Started with TinyCore 4.7.4, added a browser, epdfview, viewnior, acpi, iptables, tc-install, and ezremaster.
No changes to configuration files (except adding /usr/local/sbin/basic-firewall to bootlocal.sh.)

Maybe something involving default settings in 4.7.4?
Computer only has 2 gigs of ram, but tc runs fine after boot.
Thanks,
Bob

[Rich]

Hi newtotinycore
You could try using the  syslog  boot code. Then take a look through  /var/log/messages  which gives timing
information and see what's holding up the works.

[newtotinycore]

Hi Rich,
Added 'syslog' to end of APPEND line of code in extlinux.conf.
After reboot /var/log/messages shows about 500 lines of code (mostly occurring in first second),
however, total time period covered is only 5 seconds. (Problem is during prior 5 minutes).
Is this the 5 seconds from waitusb=5?

I could increase waitusb to 300, but it seems like that would just add another 5 minutes to boot time and
still not start logging until the 'problem' was finished.

Thanks,
Bob

[tinypoodle]

For more debugging you could use following boot params:

Code: [Select]

debug printk.time=y earlyprintk=vga,keep syslog
EDIT: Oh, and remove the "quiet", that doesn't help...

[newtotinycore]

Followed your advice, TinyPoodle.
The /var/log/messages still only cover 5 seconds, most message are in the first second, a few in the second second.

But right after the copy-write screen,"Loading/tce/boot/vmlinuz....." comes up and is quickly followed by
"Loading/tce/boot/core.gz.............................................." which continues for five minutes.

Looks like there is some difficulty loading core.gz.
I tried erasing another usb drive several times before installing the remastered tc 4.7.4.
Again, the new usb hangs for five minutes after the copy-write screen (versus 30 seconds for the usb that generated the remaster).

Anybody else having this difficulty?
Thanks,
Bob

[tinypoodle]

"Loading/tce/boot/core.gz.............................................." which continues for five minutes.

Please clarify what you mean. Do new dots continue to get printed? Or does it just stand still after a certain amount of dots?

Could you try to boot your remastered core.gz from a different boot medium?

[Rich]

Hi newtotinycore
What does this command return:

Code: [Select]

ls -lh /etc/sysconfig/tcedir/boot

[newtotinycore]

Rich,
Here is the command ouput:

 ls -lh /etc/sysconfig/tcedir/boot
total 70864
-rw-rw-r--    1 tc       staff      66.7M Feb 16 22:11 core.gz
drwxrwxr-x    2 tc       staff       4.0K Feb 16 22:12 extlinux/
-rw-rw-r--    1 tc       staff       2.4M Feb 16 22:11 vmlinuz

TinyPoodle,

"Loading/tce/boot/core.gz.............................................." which continues for five minutes.

Please clarify what you mean. Do new dots continue to get printed? Or does it just stand still after a certain amount of dots?

-Dots continue to get printed for 5 minutes

Could you try to boot your remastered core.gz from a different boot medium?

-I'm not clear what you mean by "boot remastered core.gz from a different boot medium".
Tried to install remastered TinyCore.iso to DVD, but DVD was not mountable.

However, belatedly I just realized that the remastered usb drives boot fine on a newer computer.
When I download and install TinyCore to a usb, tc boots fine from my old HP Pavilion.
But remastering TinyCore to another usb causes a 5 minute boot delay ( but only on old HP, not a newer machine).

Apparently, the old HP does not recognize something in the remaster.
There is no way TinyCore can support all hardware, especially hardware obsolete by modern standards.
If you have think solving this issue is important for others, I'm happy to work with you to figure it out.
Otherwise, I'm more than satisfied with the way TinyCore performs.

Thanks for your help, Rich and TinyPoodle,
Bob

[gerald_clark]

That is not tinycore taking 5 minutes.
That is the boot loader loading the initrd.
It sounds like it is loading using USB 1 mode.

[newtotinycore]

That is not tinycore taking 5 minutes.
That is the boot loader loading the initrd.
It sounds like it is loading using USB 1 mode.

That sounds reasonable.
The HP usb ports are USB 2.0.
Why TinyCore is booted using USB 2 mode, while the remaster is booted using
USB 1 is not clear to me.

I apologize for taking up forum time and space for an issue related to HP hardware instead of
TinyCore OS.

Thanks,
Bob

[tinypoodle]

-I'm not clear what you mean by "boot remastered core.gz from a different boot medium".
Tried to install remastered TinyCore.iso to DVD, but DVD was not mountable.

Any boot medium other than pendrive, i.e. cd, hdd, netboot

You need to burn .iso as image to cd