32 or 64-bit Centos 6.2 ISOs

[darmock]

We we are starting to build of PBX in a Flash 2.0.6.2.1 A few show stoppers but I suspect we can deal with them over the next few days. Still puzzled by the keyboard problems with 6.0/6.1 as it is NOT consistent and only seems to effect certain machines. (Ward and I dont a machine between us that it causes problems on and there are a lot of machines!) We have several new strategies to try to combat this problem. We will be modifying the kickstart files somewhat and moving the downloader program off the ISO and into the piaf repo. This will allow us to modify it between ISO releases.

We are also going to modify the piafdl program to support gui or text modes when installing PIAF. Thus you will see a new screen, when piaf2062 is released, that will ask you if you want TEXT or GUI. The TEXT mode will be default and the GUI will not. You will have to use the right cursor key to select the GUI. If this does not work you have one of the affected machines. If it does work you should not have one of the affected machines. We will also support a command line mode that will allow you to select text or GUI


I doubt that this will be out till after the holidays.


Tom

 

[fizadmin]

What specifically worthwhile does Centos 6.2 bring to the table?

 

[wardmundy]

Google is your friend...

http://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.2

 

[fizadmin]

I know that - first thing I looked at.

What worthwhile advantages does it bring for PIAF?

 

[darmock]

Other than it is the latest and people will upgrade to it regardless of what we do? Nothing I can think of. If your existing 6.1 PIAF system works then keep it. I see no pressing reason to do a yum update at all. If you are doing a new install with PIAF 20612 ISO you will have an in place upgrade to centos 6.2 occur regardless.

Really OS upgrades should only ever affect new installs and not existing ones. However there are so many that come from windoze and refuse to learn that in general updates to existing system and rarely required and indeed should only be done when there is a VERIFIED and REAL security threat an that upgrading your entire os is the ONLY way to fix it. Sorry can't remember that last time this occurred with the proviso of VERIFIED and REAL.

Beyond that there is no list other than the one ward points out I noticed our 2 dev machines video works a lot better under 6.2 but THAT IS ALL and that only applies to gnome.

So the short answer is none.

Tom

 

[darmock]

So we are finalizing PBX in a Flash 20621. It contains the latest version of Centos 6.2 (stable). There are a number of changes including some new methodologies which should not be apparent to end users.

Our download program has been modified to allow for a command line option that will disable the GUI and use a text based install. This is in response to the <1% of systems that have a keyboard error. Initially if you cant use the arrow keys to make a selection during the initial install you will be dumped to the command line. Simply enter piafdl -txt and the install will start again in text only mode.

No ideas why this problem occurs however the only way we can debug it is if someone permanently donates a system that has this error. We cannot duplicate it on any of the 25 odd machines that are available to us. Also we cant make it happen in vmware workstation 8/prox/xen. Thus if we dont have a machine that does it we cant fix it.

Just finished uploading the final 32 bit ISO into our private SVN server and it MAY propagate into regular PIAF space prior to Christmas. If not then next week. 64 bit ISO is still being worked on as it has some different problems compared to the 32bit one.

All of the programs in PIAF space must be updated to recognize and use centos 6.2 so be patient with that.

Until the new programs are uploaded you may notice some odd things.

The rest of the PIAF dev team have already left for the holidays so.......


Tom

 

[fizadmin]

No ideas why this problem occurs however the only way we can debug it is if someone permanently donates a system that has this error. We cannot duplicate it on any of the 25 odd machines that are available to us. Also we cant make it happen in vmware workstation 8/prox/xen. Thus if we dont have a machine that does it we cant fix it.

Maybe some of those affected could try out swapping the keyboard for a USB keyboard (or, if using USB keyboards, swap it for a regular PC din plug one), and see if that makes a difference?

 

[wardmundy]

Merry Christmas



:santab::santab::santab::santab::santab:

 

[darmock]

I agree however when we posted a suggested fix earlier I had one response. Other than the emails we have been getting demanding a fix I have no other suggestions. Only way is to run some of the debug tools we have on one of the machines that seem to be affected. Unfortunately this seems to be a physical problem with certain types of hardware which does NOT lend itself to remote debugging. Thus need a machine that this problem exists on. Also I know of several different machines of the same model and the problem does not exist consistently thus.......

So the dev team has gone as far as we can with the resources we have. Really end of story.... bugs me as I like to fix things but we have all been down the path of "well send me a patch and we will try it on out machine" This method of development just does not work for us. So for the moment once the new ISO gets out you have a workaround as opposed to a fix.


regards to all

Tom

 

[fizadmin]

Also I know of several different machines of the same model and the problem does not exist consistently thus.......

I saw that, and that's why I was thinking that it could be keyboard type related, i.e. USB vs earlier DIN connectors. I've seen similar before, and it was related to how some motherboards (or rather, older BIOS') handle USB keyboards.

I just figured if you have more reports coming in, asking what type of keyboard they are using is probably a good way to target or eliminate variables.

Downloading the new PIAF/Centos as we speak. Ready to test! Woohoo!

 

[Gotenks]

If you are doing a new install with PIAF 20612 ISO you will have an in place upgrade to centos 6.2 occur regardless.

Tom

This occurred when I installed a couple days ago, it says I've got 6.2 without manually updating. This must be different than upgrading to the newest kernel which breaks asterisk. Am I okay?

 

[darmock]

No Idea. Generally it is the people with centos 6.1 and then do a yum update outside of update-source who have problems. Does not happen to every one and not on all machines. Too much randomness for my liking but it is what it is. We have been told by the pwoers that be in Centos that this will be the last major upgrade for a few months so......

Old 6.1 and 6.0 versions of the iso automatically install centos 6.2 except for the kernels which are excluded. If you upgrade the kernels by hand to 6.2 then you MAY have to recompile asterisk AND dahdi.

There is no advantage what so ever to upgrade an existing Centso 6.1 box at ALL.

Tom

 

[darmock]

I saw that, and that's why I was thinking that it could be keyboard type related, i.e. USB vs earlier DIN connectors. I've seen similar before, and it was related to how some motherboards (or rather, older BIOS') handle USB keyboards.

I just figured if you have more reports coming in, asking what type of keyboard they are using is probably a good way to target or eliminate variables.

Downloading the new PIAF/Centos as we speak. Ready to test! Woohoo!

Yup could be.... Centos 6.x uses some new USB technology which I suspect is flakey. That being said our primary dev machines use usb keyboards. We actually tried it on almost all of our lab machines with both usb and ps2 keyboards. No results. One of the reasons I am going to wash my hands of it till we get a box in the lab that has this problem or someone comes up with a solutions. Wasted way too much time on this. Oh well back to the 64 bit 6.2 ISO

Tom

 

[wardmundy]

64-bit PIAF 2.0.6.2.1 ISO is now available on SourceForge.