[App_rpt-users] Fwd: Re: ACID install issue anyone seen this before? anyone know the centos default root password?

[Steve Gladden]

Stephen Rodgers wrote:
> Matt Beasant wrote:
>   
>> Thanks David and Doug for the info.
>>
>> But I'm not sure I agree that it is a hardware issue, with the greatest
>> of respect of course :-)
>>
>> The machine I am using is a Compaq EVO D510 - I have 6 of these all running
>> app_rpt. They all installed fine.
>>
>> This is the only one I had any issues installing the ACID setup on. This was
>> a reinstall as the HDD died and I fitted a new one and wanted to put app_rpt
>> on it.
>>
>> Unless something has changed recently on the ACID distro?
>>
>> Anyone?
>>
>> Thanks in advance,
>>
>> Matt
>> 2009/11/20 David McGough <kb4fxc at inttek.net>
>>
>>     
>>> Hi Doug,
>>>
>>> See below....
>>>
>>>
>>> On Fri, 20 Nov 2009, Doug Bade wrote:
>>>
>>>       
>>>> My reply went to Steve only, I am resending as it may help other
>>>>         
>>> folks....
>>>       
>>>> I need to get specifics on the chipset I am refering to....but I have
>>>> run into this stoppage as well and it is hardware related...
>>>>
>>>> Doug
>>>> KD8B
>>>>         
>>>>> Date: Fri, 20 Nov 2009 08:08:31 -0500
>>>>> To: Steve Gladden <steve at michiganbroadband.com>
>>>>> From: Doug Bade <kd8b at thebades.net>
>>>>> Subject: Re: [App_rpt-users] ACID install issue anyone seen this
>>>>> before? anyone know the centos default root password?
>>>>>
>>>>> There are issues with Centos and new Realtek ethernet chips. The OS
>>>>> invokes the wrong driver with flakey startup as one byproduct. If it
>>>>> does not finish updates and get the scripts for Allstar.. it stops
>>>>> and gives a prompt. I have this happening on ATOM motherboards...as
>>>>> the chipsets have some known issues...
>>>>>
>>>>> The solution is easy... I use a usb to ethernet adapter to build
>>>>> with that is known compatible and then when all is done add the
>>>>> drivers I need to fix the MB issue.. and pull the usb to etherent...
>>>>>
>>>>> Alternately on MB's I could.. I used an older PCI Intel Chipset NIC
>>>>> and get around it too...
>>>>>
>>>>> This may have something to do with it???
>>>>>           
>>>> Doug
>>>>
>>>>
>>>>
>>>>         
>>> <snip>
>>>
>>>
>>> Yep, I've noticed issues with the relatively old CentOS kernels and recent
>>> hardware, too....I switched to a "hand built" 2.6.30.5 kernel, on CentOS
>>> 5.x, and this resolved my problems.
>>>
>>> 73, David kb4fxc
>>>
>>>
>>>
>>> _______________________________________________
>>> App_rpt-users mailing list
>>> App_rpt-users at qrvc.com
>>> http://qrvc.com/mailman/listinfo/app_rpt-users
>>>
>>>       
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users at qrvc.com
>> http://qrvc.com/mailman/listinfo/app_rpt-users
>>     
>
>
> Log in to the failed setup and look at the log file, and then post where it failed:
>
> The default password should be 'setup' and there is a log
> of the install in /root/acid/acid-install.log.
>
> Compare notes with the rest of the users having issues.
>
>
> Steve
> WA6ZFT
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at qrvc.com
> http://qrvc.com/mailman/listinfo/app_rpt-users
>
>   
Just as per request and for comparing notes..
Digging in deeper reveals the no sources error
manually launching phase2 gies a little more detail:


make[3]: Leaving directory `/usr/src/zaptel/menuselect/mxml'
gcc -o menuselect menuselect.o strcompat.o menuselect_curses.o 
mxml/libmxml.a mxml/libmxml.a -lncurses
make[2]: Leaving directory `/usr/src/zaptel/menuselect'
make[1]: Leaving directory `/usr/src/zaptel/menuselect'
Generating input for menuselect ...
make[1]: Entering directory `/usr/src/zaptel'
echo "You do not appear to have the sources for the 
2.6.18-164.6.1.el5PAE kernel installed."
You do not appear to have the sources for the 2.6.18-164.6.1.el5PAE 
kernel installed.
exit 1
make[1]: *** [modules] Error 1
make[1]: Leaving directory `/usr/src/zaptel'
make: *** [all] Error 2
Failure: Unable to compile Zaptel 2
Fatal error: Unable to install Asterisk!
[root at test rc.d]#






-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.