Fwd: Re: ACID install issue anyone seen this before? anyone know the centos default root password?
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@michiganbroadband.com> From: Doug Bade <kd8b@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
At 12:07 AM 11/20/2009, you wrote:
Anyone seen this before? anyone know the Centos default root password?
Meanwhile I'm going to try this on a 3Ghz all Intel much faster and see if the radio drop outs are indeed gone or if they're all still there and if in the same way or different...
Or not... just tried installing ACID on two different *new* systems.. On both systems it goes and does everything updates & all.. I think it even compiles asterisk.. or sor sure at least starts into that process..
There's some sort of 'error right before it goes to the login screen but goes by in less than 1/2 second.. Hitting shit+pageup shows some scrollback but not the error..
Whie instlling ACID It goes straight to a login screen right after install and never EVER prompts for anything at all.. Anyone know the default root password on ACID if the install is doing this?
Strange this happened a few days ago on one of the slower test systems... My only choice was to reboot and start all over again.. and it worked the 2nd time..
Just tried 4 times here and each time it seems to do everything including all of the updates (centos).. then just goes to a login prompt.. (I'm positive it's re formatting the hard drive during the install. I've also tried other install media..
rebooting just comes back to login again.. it somehow installed having not prompted for anything and it set a root password.
Tried two computers total of 5 times this evening same result. It's almost as if some web resource is down and the install is bailing and doing some other default action along with setting up a password for root on it's own.
everything seems to install and just goes to a login prompt never having asked for anything like it normally does where it asks for your node number/pass and callsign.
Centos's LiveCD root password 12qwaszx does not work.
Thanks!! Steve
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
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@michiganbroadband.com> From: Doug Bade <kd8b@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
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@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@michiganbroadband.com> From: Doug Bade <kd8b@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@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
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@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@michiganbroadband.com> From: Doug Bade <kd8b@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@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
------------------------------------------------------------------------
_______________________________________________ App_rpt-users mailing list App_rpt-users@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
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@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@michiganbroadband.com> From: Doug Bade <kd8b@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@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
------------------------------------------------------------------------
_______________________________________________ App_rpt-users mailing list App_rpt-users@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@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@test rc.d]# -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Steve Gladden wrote:
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@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@michiganbroadband.com> From: Doug Bade <kd8b@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@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
------------------------------------------------------------------------
_______________________________________________ App_rpt-users mailing list App_rpt-users@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@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@test rc.d]#
Whoops I forgot to include what was actually requested... this: tail acid-install.log Thu Nov 19 22:19:10 PST 2009:Getting files.tar.gz from http://dl.allstarlink.org... Thu Nov 19 22:19:21 PST 2009:Fatal error: Unable to install Asterisk! Fri Nov 20 10:47:21 PST 2009:****** Phase 2 post install ****** Fri Nov 20 10:47:22 PST 2009:Getting asterisk install script from http://dl.allstarlink.org... Fri Nov 20 10:47:22 PST 2009:Getting files.tar.gz from http://dl.allstarlink.org... Fri Nov 20 10:47:40 PST 2009:Fatal error: Unable to install Asterisk! Fri Nov 20 11:52:47 PST 2009:****** Phase 2 post install ****** Fri Nov 20 11:52:48 PST 2009:Getting asterisk install script from http://dl.allstarlink.org... Fri Nov 20 11:52:49 PST 2009:Getting files.tar.gz from http://dl.allstarlink.org... Fri Nov 20 11:53:02 PST 2009:Fatal error: Unable to install Asterisk! -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
On Fri, 20 Nov 2009, Steve Gladden wrote: <snip>
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@test rc.d]#
Hi Steve, Yes, I had the same problem that the kernel source code wasn't installed when I did an ACID install a few months ago. But, this is easy to fix.
From a root prompt, just install the package using yum....A command like:
yum install kernel-PAE-devel.i686 Also, I'll upload my "cooked" 2.6.30.5 kernel tonight and send you a link. It should be easy enough to install... BTW, I seem to remember needing some other packages, too....But, I don't recall which at the moment. 73, David kb4fxc
David McGough wrote:
On Fri, 20 Nov 2009, Steve Gladden wrote: <snip>
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@test rc.d]#
Hi Steve,
Yes, I had the same problem that the kernel source code wasn't installed when I did an ACID install a few months ago. But, this is easy to fix.
From a root prompt, just install the package using yum....A command like:
yum install kernel-PAE-devel.i686
Also, I'll upload my "cooked" 2.6.30.5 kernel tonight and send you a link. It should be easy enough to install...
BTW, I seem to remember needing some other packages, too....But, I don't recall which at the moment.
73, David kb4fxc
Thanks David! What CPU is it optimized for? I'm testting on Pentium-2s Pentium-3s Intel Q6700s and a newer Xeon this weekend. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
David McGough wrote:
On Fri, 20 Nov 2009, Steve Gladden wrote: <snip>
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@test rc.d]#
Hi Steve,
Yes, I had the same problem that the kernel source code wasn't installed when I did an ACID install a few months ago. But, this is easy to fix.
From a root prompt, just install the package using yum....A command like:
yum install kernel-PAE-devel.i686
Also, I'll upload my "cooked" 2.6.30.5 kernel tonight and send you a link. It should be easy enough to install...
BTW, I seem to remember needing some other packages, too....But, I don't recall which at the moment.
73, David kb4fxc
Way off topic but here's what I'm working on at the moment: I'm trying to roll a few of my own kernels (2.6.31.6) <http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.31.6.tar.bz2> but keep tripping over myself somehow.. Far as I can tell I have included everything I should need for drives and filesystem support yet it won't mount the filesystem. Having same issue on two systems I tried to make my own kernel for. I should be able to figure this out. Don't want to hijack the topic too badly ;-) One system is the P3 450Mhz box with plain old IDE hard drive. Other system is Intel Q6700 (2.67Ghz) with NVIDIA SATA (I specifically enabled this in kernel tried it with & without it compiled in (generic IDE)). Also having same problem on older IDE only system. I have to be missing something really basic. And of course the centos stock kernels are working fine.. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
David McGough wrote:
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@michiganbroadband.com> From: Doug Bade <kd8b@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@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
I'm trying to go with the hand built kernel now to get around this.. + I wanted to build a kernel anyway.. Not done it in awhile and it shows.. I've been unable to make a kernel so far that wil mount the existing installation.. Even though I've been sure to include the IDE/Sata and ext2/3/4 in the kernel. I'm a little new with udev and all this new stuff from the last 5 years.. Might be why it's not working yet. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
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@michiganbroadband.com> From: Doug Bade <kd8b@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
At 12:07 AM 11/20/2009, you wrote:
Anyone seen this before? anyone know the Centos default root password?
Meanwhile I'm going to try this on a 3Ghz all Intel much faster and see if the radio drop outs are indeed gone or if they're all still there and if in the same way or different...
Or not... just tried installing ACID on two different *new* systems.. On both systems it goes and does everything updates & all.. I think it even compiles asterisk.. or sor sure at least starts into that process..
There's some sort of 'error right before it goes to the login screen but goes by in less than 1/2 second.. Hitting shit+pageup shows some scrollback but not the error..
Whie instlling ACID It goes straight to a login screen right after install and never EVER prompts for anything at all.. Anyone know the default root password on ACID if the install is doing this?
Strange this happened a few days ago on one of the slower test systems... My only choice was to reboot and start all over again.. and it worked the 2nd time..
Just tried 4 times here and each time it seems to do everything including all of the updates (centos).. then just goes to a login prompt.. (I'm positive it's re formatting the hard drive during the install. I've also tried other install media..
rebooting just comes back to login again.. it somehow installed having not prompted for anything and it set a root password.
Tried two computers total of 5 times this evening same result. It's almost as if some web resource is down and the install is bailing and doing some other default action along with setting up a password for root on it's own.
everything seems to install and just goes to a login prompt never having asked for anything like it normally does where it asks for your node number/pass and callsign.
Centos's LiveCD root password 12qwaszx does not work.
Thanks!! Steve
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
Hi Doug thanks for the info but nope it's certainly not that issue here :-) I've also tried multiple computers/ethernet cards yesterday and had the problem throughout.. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
participants (5)
-
David McGough -
Doug Bade -
Matt Beasant -
Stephen Rodgers -
Steve Gladden