Page 1 of 1

FAA Won't Boot

Posted: 20 Feb 2015, 14:41
by frenchy
I have a couple of old machines perfect for Porteus.The first desktop booted from a USB build without problem The Asus 751LX will not boot from the same usb or a disc I burned using a new build. I get.
Loading vmlinux
Loading initrd.vz.ready
[0. 000000]tsc:fast TSC calibration failed
It's running Windows Vista Home Premium 32 bit

Re: Won't Boot

Posted: 20 Feb 2015, 16:38
by donald
TSC= Time Stamp Counter.
Normally this shouldn't stop booting...did you wait ~a min. to check if it will continue?
If not,you can try to boot with "clocksource=acpi_pm"
At the splash-screen hit the tab-key and add clocksource=acpi_pm
=========================================================
the list of avaialble clocksource(s):
$ cat /sys/devices/system/clocksource/clocksource0/available_clocksource

Re: Won't Boot

Posted: 21 Feb 2015, 17:35
by frenchy
Can't do anything sadly if freezes the screen,every time.

Re: FAA Won't Boot

Posted: 22 Feb 2015, 10:01
by fanthom
please do as follows:
a) on the boot menu press TAB then add 'debug' code and show me video of booting process or picture of last lines displayed on the scree
b) boot any other linux (Ubuntu maybe) and run 'lsmod' 'lspci -knn' and 'dmesg' commands -> post their output to pastebin.com -> link here

thank you

Re: FAA Won't Boot

Posted: 22 Feb 2015, 22:47
by frenchy
Sorted thanks.After hours of web searching it was a bios value that needed changing.Working OK as I type

Re: FAA Won't Boot

Posted: 13 Jul 2015, 21:26
by kernelpanic
Hi people,

I have same problem
when I boot wit porteus, "fast tsc calibration failed" message show up and freezes.
then I have open debug mode and take a picture where it stop.

you can click the link bellow to see last part pat of the debug output
https://drive.google.com/file/d/0Bz87q3 ... sp=sharing

my pc model is dell inspiron 13-7312

Could you please help me about this issue.

Re: FAA Won't Boot

Posted: 14 Jul 2015, 06:45
by kernelpanic
frenchy wrote:Sorted thanks.After hours of web searching it was a bios value that needed changing.Working OK as I type
which value in your bios changed and fixed it.