I'm currently running clearos 6.7 on an ITX dual nic Intel(R) Atom(TM) CPU D2500 @ 1.86GHz works beautifully I might add, that said I threw 7.2 into a VM to take a good hard look and while I'm not a fan of the new dashboard, all the new features make this move worthwhile, Friday night I backed up all my data to prepare for a long day.
I rufus the image to a 14 gig USB stick and start the installation, and no matter what I do 1/2 way through the load I get a tsc fast calibration failed where I have to psychically shut off the machine and reboot into 6.7
Am I missing something ? Everything I've read on hardware requirements tells me I should have no issue upgrading this box, am I wrong ?
Thanks in advance
Chuck
I rufus the image to a 14 gig USB stick and start the installation, and no matter what I do 1/2 way through the load I get a tsc fast calibration failed where I have to psychically shut off the machine and reboot into 6.7
Am I missing something ? Everything I've read on hardware requirements tells me I should have no issue upgrading this box, am I wrong ?
Thanks in advance
Chuck
In Installation
Share this post:
Responses (7)
-
Accepted Answer
Certainly once installed you get about 3s to hit 'e' at which point you can edit the boot up line. The one I'd edit would be the line beginning "linux16 /vmlinuz....." and I'd append to it (or at least take out the "quiet" to make the start up more verbose).
I've no real experience of grub2 as I still run ClearOS 6.x. I have 7.x on a VM to play around with and this is where I do see the "e" option, just when it asks you which kernel you want to boot from. The menu comes from the file you've posted and the line you may want to play with is this one:
but it is probably better just to use the "e" option as this is only for the installation.linuxefi /images/pxeboot/vmlinuz inst.stage2=hd:LABEL=CLEAROS-7_2 quiet
Someone else has posted instructions to rebuild the grub2 menu here, but that is from a running linux system. -
Accepted Answer
HPET is a real shot in the dark and I only have it on my older m/b's. The option is called HPET Support on the Power management page but I suppose it could be called anything.
You may be able to edit the grub boot line on the stick but it is probably not the easiest way to go. During boot up a message will pop up and you have about three seconds to hit enter or, perhaps, any key. This allows you to select the kernel you want to boot from (if you have more than one) and edit the grub boot line as a one-off. You may only need it for installation. If you need it after that for each reboot, you can then edit the boot line permanently.
P.S. If you do routing in your sleep and possibly VoIP, please hang around this forum! -
Accepted Answer
Nick, this is the grub boot config from the install stick, this is what clear uses to boot and install correct ? If so I don't see the option you suggested.
set default="1"
function load_video {
insmod efi_gop
insmod efi_uga
insmod video_bochs
insmod video_cirrus
insmod all_video
}
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set timeout=60
### END /etc/grub.d/00_header ###
search --no-floppy --set=root -l 'ClearOS-7.2.0-x86_64'
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Install ClearOS 7.2.0' --class fedora --class gnu-linux --class gnu --class os {
linuxefi /images/pxeboot/vmlinuz inst.stage2=hd:LABEL=CLEAROS-7_2 quiet
initrdefi /images/pxeboot/initrd.img
}
menuentry 'Test this media & install ClearOS 7.2.0' --class fedora --class gnu-linux --class gnu --class os {
linuxefi /images/pxeboot/vmlinuz inst.stage2=hd:LABEL=CLEAROS-7_2 rd.live.check quiet
initrdefi /images/pxeboot/initrd.img
}
submenu 'Troubleshooting -->' {
menuentry 'Install ClearOS 7.2.0 in basic graphics mode' --class fedora --class gnu-linux --class gnu --class os {
linuxefi /images/pxeboot/vmlinuz inst.stage2=hd:LABEL=CLEAROS-7_2 xdriver=vesa nomodeset quiet
initrdefi /images/pxeboot/initrd.img
}
menuentry 'Rescue a ClearOS system' --class fedora --class gnu-linux --class gnu --class os {
linuxefi /images/pxeboot/vmlinuz inst.stage2=hd:LABEL=CLEAROS-7_2 rescue quiet
initrdefi /images/pxeboot/initrd.img
}
}
-
Accepted Answer
Nick Howitt wrote:
Hmm. I think it will be a case of googling around. The installation issues should be very similar to CentOS and probably EL7 which is why I used centos as a key word in the search. There were other suggestions such as changing the clocksource parameter in the grub boot line. This can be done as a one off or permanently. Another idea of mine is to look in the BIOS and see if you have an option for HPET/High Performance Event(?) TImer and see if you can turn it on.
HPET, don't recall seeing that in the bio's, be honest never heard of it till now, as soon as my wife gets off her daily addiction of crapbook I'll reboot that box and take a peak.
Lets say I go playing around with the grub boot line, would you edit right on the install stick or would I have to recompile the kernel ? I'm network guy, I know allot about this but it's not my forte, I could do routing and voip in my sleep, I do it everyday of my life, but compiling a new kernel is way out of my league and I'm not afraid to say so. -
Accepted Answer
Hmm. I think it will be a case of googling around. The installation issues should be very similar to CentOS and probably EL7 which is why I used centos as a key word in the search. There were other suggestions such as changing the clocksource parameter in the grub boot line. This can be done as a one off or permanently. Another idea of mine is to look in the BIOS and see if you have an option for HPET/High Performance Event(?) TImer and see if you can turn it on. -
Accepted Answer
Nick I apologize for the later response I ended up on an emergency service call in Joplin ( 100 miles away from me ) which when I get there the replacement router was sent to Tulsa, I retrieved it but can you sat cha ching
Looks like I'm on UEFI, I don't have a legacy option as for sata issue, only 2 slots and I'm only using one, 240 SSD this is the box I use for routing and filtering. -
Accepted Answer
I am trying googling tsc fast calibration failed installation centos and getting a few hits. One leads to a Ubuntu link here suggesting a SATA issue.
Also, are you using UEFI or legacy mode in your Bios?
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »