[CentOS] Centos 6.4 - doesnt power off with shutdown/poweroff cmd

2013-10-11 Thread Terre Porter
Hello,

 

I'm looking for help figuring out why I am having problems with shutting
down a machine.

 

I have tested the machine using Fedora 19 and Ubuntu 12 Live CD's and both
power down without issues. 

 

I added acpi.debug_level=1 to the grub boot as it was suggested to see more
info about ACPI in the logs

 

I found the following ACPI Errors in the /var/log/messages

 

Oct 11 11:51:36 plum kernel: ACPI Error (psargs-0359): [ECEN] Namespace
lookup failure, AE_NOT_FOUND

Oct 11 11:51:36 plum kernel: ACPI Error (psparse-0537): Method
parse/execution failed [\] (Node 81fdbeb0), AE_NOT_FOUND

 

Oct 11 11:51:36 plum kernel: ACPI: resource piix4_smbus [io  0x0b00-0x0b07]
conflicts with ACPI region SOR1 [io 0xb00-0xb0f]

Oct 11 11:51:36 plum kernel: ACPI: If an ACPI driver is available for this
device, you should use it instead of the native driver

 

I used the Centos 6.4 Live CD last night with no hard drive in the system. 

 

I photo'd the shutdown, here is the type up:

 

Sending all processes the TERM signal...

Sendng all processes the KILL signal...

Saving random seed:

Syncing hardware clock to system time

Turning off quotas:

umount2: Device or resource busy

umount: /dev/.initramfs/live: device is busy.

(In some cases useful info about processes that use 

 the device is found by lsof(8) or fuser(11))

init: Re-executing /sbin/init

Halting System...

r8169 :02:00.0: PME# enabled

ACPI: Preparing to enter system sleep state S5

ACPI Error (psargs-0359): [PPTS] Namespace lookup failure, AE_NOT_FOUND

ACPI Error (psparse-0537): Method parse/execution failed
[\_SB_.PCI0.SBRG.EPTS] (Node fff88019dbc8c68), AE_NOT_FOUND

ACPI Error (psparse-0537): Method parse/execution failed [\PTS_] (Node
88019d043560), AE_NOT_FOUND

ACPI Error (psparse-0537): Method parse/execution failed [\_PTS] (Node
88019dbcf9e8), AE_NOT_FOUND

Disabling non-boot CPUS...

SMP alternatives: switching to UP code

Power Down.

acpi_power_off called

 

The system doesn't power off, it just sits there. I have to hold the power
button in for it to shut down.

 

The same still occurs with a completed a fresh minimum install of Centos
6.4, installed the EPEL repo and did yum update.

 

I'm running the latest bios for the motherboard, and even tried going back
one version.

 

MB: 785GM-E51 (MS-7596 1.2) 

CPU: AMD Phenom II x4 945 3ghz 

1TB HD, 6 Gig Mem

 

Any ideas? 

 

(Besides using a baseball bat - I am considering it)

 

Here is some hardware info from the getinfo.sh script listed the forums.

 

== BEGIN uname -rmi ==

2.6.32-358.18.1.el6.x86_64 x86_64 x86_64

== END   uname -rmi ==

 

== BEGIN rpm -qa \*-release\* ==

centos-release-6-4.el6.centos.10.x86_64

epel-release-6-8.noarch

== END   rpm -qa \*-release\* ==

 

== BEGIN cat /etc/redhat-release ==

CentOS release 6.4 (Final)

== END   cat /etc/redhat-release ==

 

== BEGIN getenforce ==

Enforcing

== END   getenforce ==

 

== BEGIN rpm -qa kernel\* | sort ==

kernel-2.6.32-358.18.1.el6.x86_64

kernel-2.6.32-358.el6.x86_64

kernel-firmware-2.6.32-358.18.1.el6.noarch

== END   rpm -qa kernel\* | sort ==

 

== BEGIN lspci -nn ==

00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] RS880 Host Bridge
[1022:9601]

00:01.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780/RS880 PCI to
PCI bridge (int gfx) [1022:9602]

00:05.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780/RS880 PCI to
PCI bridge (PCIE port 1) [1022:9605]

00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] nee ATI
SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391]

00:12.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]

00:12.1 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0
USB OHCI1 Controller [1002:4398]

00:12.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI
SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396]

00:13.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]

00:13.1 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI SB7x0
USB OHCI1 Controller [1002:4398]

00:13.2 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI
SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396]

00:14.0 SMBus [0c05]: Advanced Micro Devices [AMD] nee ATI SBx00 SMBus
Controller [1002:4385] (rev 3c)

00:14.1 IDE interface [0101]: Advanced Micro Devices [AMD] nee ATI
SB7x0/SB8x0/SB9x0 IDE Controller [1002:439c]

00:14.2 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI SBx00
Azalia (Intel HDA) [1002:4383]

00:14.3 ISA bridge [0601]: Advanced Micro Devices [AMD] nee ATI
SB7x0/SB8x0/SB9x0 LPC host controller [1002:439d]

00:14.4 PCI bridge [0604]: Advanced Micro Devices [AMD] nee ATI SBx00 PCI to
PCI Bridge [1002:4384]

00:14.5 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI
SB7x0/SB8x0/SB9x0 USB OHCI2 Controller [1002:4399]

00:18.0 Host bridge 

Re: [CentOS] Centos 6.4 - doesnt power off with shutdown/poweroff cmd

2013-10-11 Thread Terre Porter
Same result, doesn't turn off.

Any other ideas?

-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
Of Andrew Wyatt
Sent: Friday, October 11, 2013 4:41 PM
To: CentOS mailing list
Subject: Re: [CentOS] Centos 6.4 - doesnt power off with shutdown/poweroff
cmd

Try using the reboot=pci grub parameter.


On Fri, Oct 11, 2013 at 11:40 AM, Terre Porter  wrote:

> Hello,
>
>
>
> I'm looking for help figuring out why I am having problems with 
> shutting down a machine.
>
>
>
> I have tested the machine using Fedora 19 and Ubuntu 12 Live CD's and 
> both power down without issues.
>
>
>
> I added acpi.debug_level=1 to the grub boot as it was suggested to see 
> more info about ACPI in the logs
>
>
>
> I found the following ACPI Errors in the /var/log/messages
>
>
>
> Oct 11 11:51:36 plum kernel: ACPI Error (psargs-0359): [ECEN] 
> Namespace lookup failure, AE_NOT_FOUND
>
> Oct 11 11:51:36 plum kernel: ACPI Error (psparse-0537): Method 
> parse/execution failed [\] (Node 81fdbeb0), AE_NOT_FOUND
>
>
>
> Oct 11 11:51:36 plum kernel: ACPI: resource piix4_smbus [io  
> 0x0b00-0x0b07] conflicts with ACPI region SOR1 [io 0xb00-0xb0f]
>
> Oct 11 11:51:36 plum kernel: ACPI: If an ACPI driver is available for 
> this device, you should use it instead of the native driver
>
>
>
> I used the Centos 6.4 Live CD last night with no hard drive in the system.
>
>
>
> I photo'd the shutdown, here is the type up:
>
>
>
> Sending all processes the TERM signal...
>
> Sendng all processes the KILL signal...
>
> Saving random seed:
>
> Syncing hardware clock to system time
>
> Turning off quotas:
>
> umount2: Device or resource busy
>
> umount: /dev/.initramfs/live: device is busy.
>
> (In some cases useful info about processes that use
>
>  the device is found by lsof(8) or fuser(11))
>
> init: Re-executing /sbin/init
>
> Halting System...
>
> r8169 :02:00.0: PME# enabled
>
> ACPI: Preparing to enter system sleep state S5
>
> ACPI Error (psargs-0359): [PPTS] Namespace lookup failure, 
> AE_NOT_FOUND
>
> ACPI Error (psparse-0537): Method parse/execution failed 
> [\_SB_.PCI0.SBRG.EPTS] (Node fff88019dbc8c68), AE_NOT_FOUND
>
> ACPI Error (psparse-0537): Method parse/execution failed [\PTS_] (Node 
> 88019d043560), AE_NOT_FOUND
>
> ACPI Error (psparse-0537): Method parse/execution failed [\_PTS] (Node 
> 88019dbcf9e8), AE_NOT_FOUND
>
> Disabling non-boot CPUS...
>
> SMP alternatives: switching to UP code
>
> Power Down.
>
> acpi_power_off called
>
>
>
> The system doesn't power off, it just sits there. I have to hold the 
> power button in for it to shut down.
>
>
>
> The same still occurs with a completed a fresh minimum install of 
> Centos 6.4, installed the EPEL repo and did yum update.
>
>
>
> I'm running the latest bios for the motherboard, and even tried going 
> back one version.
>
>
>
> MB: 785GM-E51 (MS-7596 1.2)
>
> CPU: AMD Phenom II x4 945 3ghz
>
> 1TB HD, 6 Gig Mem
>
>
>
> Any ideas?
>
>
>
> (Besides using a baseball bat - I am considering it)
>
>
>
> Here is some hardware info from the getinfo.sh script listed the forums.
>
>
>
> == BEGIN uname -rmi ==
>
> 2.6.32-358.18.1.el6.x86_64 x86_64 x86_64
>
> == END   uname -rmi ==
>
>
>
> == BEGIN rpm -qa \*-release\* ==
>
> centos-release-6-4.el6.centos.10.x86_64
>
> epel-release-6-8.noarch
>
> == END   rpm -qa \*-release\* ==
>
>
>
> == BEGIN cat /etc/redhat-release ==
>
> CentOS release 6.4 (Final)
>
> == END   cat /etc/redhat-release ==
>
>
>
> == BEGIN getenforce ==
>
> Enforcing
>
> == END   getenforce ==
>
>
>
> == BEGIN rpm -qa kernel\* | sort ==
>
> kernel-2.6.32-358.18.1.el6.x86_64
>
> kernel-2.6.32-358.el6.x86_64
>
> kernel-firmware-2.6.32-358.18.1.el6.noarch
>
> == END   rpm -qa kernel\* | sort ==
>
>
>
> == BEGIN lspci -nn ==
>
> 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] RS880 Host 
> Bridge [1022:9601]
>
> 00:01.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780/RS880 
> PCI to PCI bridge (int gfx) [1022:9602]
>
> 00:05.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780/RS880 
> PCI to PCI bridge (PCIE port 1) [1022:9605]
>
> 00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] nee ATI
> SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391]
>
> 00:12.0 USB controller [0c03]: Advanced Micro Devices [AMD] nee ATI
> SB7x0/SB8x0/SB9x0

Re: [CentOS] VNC

2013-10-11 Thread Terre Porter
Try this, iptables dump from my fresh install, with ssh allow and the vnc
you referenced.

Terre

# Generated by iptables-save v1.4.7 on Fri Oct 11 17:39:52 2013
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [45:7091]
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports
5901:5903,6001:6003 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
# Completed on Fri Oct 11 17:39:52 2013



-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
Of Larry Martell
Sent: Friday, October 11, 2013 5:36 PM
To: CentOS mailing list
Subject: Re: [CentOS] VNC

On Fri, Oct 11, 2013 at 3:30 PM, Earl Ramirez wrote:

>
> On Fri, 2013-10-11 at 15:18 -0600, Larry Martell wrote:
> > I'm trying to set up a VNC server using the instructions at
> >
> http://www.techrepublic.com/blog/linux-and-open-source/linux-101-easy-
> vnc-server-setup/
> > .
> >
> > I am up to step 6:
> >
> > Step 6: Edit iptables
> >
> > In order for the VNC connections to get through, you must allow them 
> > with iptables. To do this, open up the file /etc/sysconfig/iptables 
> > and add
> the
> > line:
> >
> > -A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports
> > 5901:5903,6001:6003 -j ACCEPT
> >
> > Save the file and restart iptables with the command:
> >
> > service iptables restart
> >
> > When I issue the restart command I get:
> >
> > iptables: Applying firewall rules: iptables-restore: line 1 failed
> >[FAILED]
> >
> > Note that I did not have an iptables file before but there is an 
> > iptables-config file.
> >
> > Can someone help me complete this configuration.
>
> Can you post the content of the file, I just edit the config file and 
> I didn't get any errors when I issue the command
>
> $ sudo /sbin/service iptables restart
>
>
As I wrote, there was no iptables file. I created one with just that one
line:

-A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports
5901:5903,6001:6003 -j ACCEPT
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] VNC

2013-10-11 Thread Terre Porter
The instructions out linked to has a type-o at the end says to connect to
ip:5801 should be 5901.

If your using a vnc client uvnc,  tightvnc..  try using just the ip without
the :port part or :1 for the 5901.

Try  lsof -i -P | grep -i "listen"

To see what ports are listening... 

Terre

-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
Of Larry Martell
Sent: Friday, October 11, 2013 6:05 PM
To: CentOS mailing list
Subject: Re: [CentOS] VNC

On Fri, Oct 11, 2013 at 3:42 PM, Terre Porter
wrote:

> Try this, iptables dump from my fresh install, with ssh allow and the 
> vnc you referenced.
>
> Terre
>
> # Generated by iptables-save v1.4.7 on Fri Oct 11 17:39:52 2013 
> *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT 
> [45:7091] -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A 
> INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -p tcp -m 
> state --state NEW -m tcp --dport 22 -j ACCEPT -A INPUT -m state 
> --state NEW -m tcp -p tcp -m multiport --dports
> 5901:5903,6001:6003 -j ACCEPT
> -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j 
> REJECT --reject-with icmp-host-prohibited COMMIT # Completed on Fri 
> Oct 11 17:39:52 2013
>
>
OK, with this file I'm getting connection timed out - before I was getting
connection refused so I guess that's some progress.

>
>
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On 
> Behalf Of Larry Martell
> Sent: Friday, October 11, 2013 5:36 PM
> To: CentOS mailing list
> Subject: Re: [CentOS] VNC
>
> On Fri, Oct 11, 2013 at 3:30 PM, Earl Ramirez  >wrote:
>
> >
> > On Fri, 2013-10-11 at 15:18 -0600, Larry Martell wrote:
> > > I'm trying to set up a VNC server using the instructions at
> > >
> > http://www.techrepublic.com/blog/linux-and-open-source/linux-101-eas
> > y-
> > vnc-server-setup/
> > > .
> > >
> > > I am up to step 6:
> > >
> > > Step 6: Edit iptables
> > >
> > > In order for the VNC connections to get through, you must allow 
> > > them with iptables. To do this, open up the file 
> > > /etc/sysconfig/iptables and add
> > the
> > > line:
> > >
> > > -A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports
> > > 5901:5903,6001:6003 -j ACCEPT
> > >
> > > Save the file and restart iptables with the command:
> > >
> > > service iptables restart
> > >
> > > When I issue the restart command I get:
> > >
> > > iptables: Applying firewall rules: iptables-restore: line 1 failed
> > >
> > > [FAILED]
> > >
> > > Note that I did not have an iptables file before but there is an 
> > > iptables-config file.
> > >
> > > Can someone help me complete this configuration.
> >
> > Can you post the content of the file, I just edit the config file 
> > and I didn't get any errors when I issue the command
> >
> > $ sudo /sbin/service iptables restart
> >
> >
> As I wrote, there was no iptables file. I created one with just that 
> one
> line:
>
> -A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports
> 5901:5903,6001:6003 -j ACCEPT
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] VNC

2013-10-11 Thread Terre Porter
You can specify the port with the IP by using the colon with the ip.

x.x.x.x:5901 or x.x.x.x:5902


-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
Of Larry Martell
Sent: Friday, October 11, 2013 6:35 PM
To: CentOS mailing list
Subject: Re: [CentOS] VNC

On Fri, Oct 11, 2013 at 4:26 PM, Terre Porter
wrote:

> The instructions out linked to has a type-o at the end says to connect 
> to
> ip:5801 should be 5901.
>
> If your using a vnc client uvnc,  tightvnc..  try using just the ip 
> without the :port part or :1 for the 5901.
>

I am unfortunately connecting from a windows box that I do not have admin
rights on.  I have to use the client provided, which is RealVNC Viewer. All
I can do is give the ip.


> Try  lsof -i -P | grep -i "listen"
>
> To see what ports are listening...
>


 [root@10 sysconfig]# lsof -i -P | grep -i "listen"  | grep vnc
Xvnc  22052   motor4u  IPv4 527366  0t0  TCP
localhost.localdomain:5901 (LISTEN)
Xvnc  22286   motor4u  IPv4 530145  0t0  TCP
localhost.localdomain:5902 (LISTEN)


>
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On 
> Behalf Of Larry Martell
> Sent: Friday, October 11, 2013 6:05 PM
> To: CentOS mailing list
> Subject: Re: [CentOS] VNC
>
> On Fri, Oct 11, 2013 at 3:42 PM, Terre Porter
> wrote:
>
> > Try this, iptables dump from my fresh install, with ssh allow and 
> > the vnc you referenced.
> >
> > Terre
> >
> > # Generated by iptables-save v1.4.7 on Fri Oct 11 17:39:52 2013 
> > *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT 
> > [45:7091] -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A 
> > INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -p tcp -m 
> > state --state NEW -m tcp --dport 22 -j ACCEPT -A INPUT -m state 
> > --state NEW -m tcp -p tcp -m multiport --dports
> > 5901:5903,6001:6003 -j ACCEPT
> > -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j 
> > REJECT --reject-with icmp-host-prohibited COMMIT # Completed on Fri 
> > Oct 11 17:39:52 2013
> >
> >
> OK, with this file I'm getting connection timed out - before I was 
> getting connection refused so I guess that's some progress.
>
> >
> >
> > -Original Message-
> > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] 
> > On Behalf Of Larry Martell
> > Sent: Friday, October 11, 2013 5:36 PM
> > To: CentOS mailing list
> > Subject: Re: [CentOS] VNC
> >
> > On Fri, Oct 11, 2013 at 3:30 PM, Earl Ramirez 
> >  > >wrote:
> >
> > >
> > > On Fri, 2013-10-11 at 15:18 -0600, Larry Martell wrote:
> > > > I'm trying to set up a VNC server using the instructions at
> > > >
> > > http://www.techrepublic.com/blog/linux-and-open-source/linux-101-e
> > > as
> > > y-
> > > vnc-server-setup/
> > > > .
> > > >
> > > > I am up to step 6:
> > > >
> > > > Step 6: Edit iptables
> > > >
> > > > In order for the VNC connections to get through, you must allow 
> > > > them with iptables. To do this, open up the file 
> > > > /etc/sysconfig/iptables and add
> > > the
> > > > line:
> > > >
> > > > -A INPUT -m state --state NEW -m tcp -p tcp -m multiport 
> > > > --dports
> > > > 5901:5903,6001:6003 -j ACCEPT
> > > >
> > > > Save the file and restart iptables with the command:
> > > >
> > > > service iptables restart
> > > >
> > > > When I issue the restart command I get:
> > > >
> > > > iptables: Applying firewall rules: iptables-restore: line 1 
> > > > failed
> > > >
> > > > [FAILED]
> > > >
> > > > Note that I did not have an iptables file before but there is an 
> > > > iptables-config file.
> > > >
> > > > Can someone help me complete this configuration.
> > >
> > > Can you post the content of the file, I just edit the config file 
> > > and I didn't get any errors when I issue the command
> > >
> > > $ sudo /sbin/service iptables restart
> > >
> > >
> > As I wrote, there was no iptables file. I created one with just that 
> > one
> > line:
> >
> > -A INPUT -m state --state NEW -m tcp -p tcp -m multiport --dports
> > 5901:5903,6001:6003 -j ACCEPT
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > http://lists.centos.org/mailman/listinfo/centos
> >
> > ___
> > CentOS mailing list
> > CentOS@centos.org
> > http://lists.centos.org/mailman/listinfo/centos
> >
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6.4 - doesnt power off with shutdown/poweroff cmd

2013-10-11 Thread Terre Porter
I have the latest bios installed - DMI: MICRO-STAR INTERNATIONAL CO.,LTD 
MS-7596/785GM-E51 (MS-7596), BIOS V2.12 02/18/2011

However, I just used the ELRepo to install kernel-ml  (Linux version 
3.11.4-1.el6.elrepo.x86_64) and it shuts down fine,.. Of course, it has other 
errors - lol

So I'm leaning toward it’s a kernel bug with these 
kernel-2.6.32-358.18.1.el6.x86_64 and kernel-2.6.32-358.el6.x86_64 (the two 
installed by default)

Now I'm going to try to locate the kernel version list so I can see if I can 
get a smaller jump in version up to test with.

kernel-ml-3.11.4-1.el6.elrepo.x86_64 worked as expected on the shutdown, but 
has some other issues.

-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of 
James A. Peltier
Sent: Friday, October 11, 2013 6:58 PM
To: CentOS mailing list
Subject: Re: [CentOS] Centos 6.4 - doesnt power off with shutdown/poweroff cmd

Update your BIOS if there is one.  I've found that to often be the cause.

- Original Message -
| Same result, doesn't turn off.
| 
| Any other ideas?
| 
| -Original Message-
| From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On 
| Behalf Of Andrew Wyatt
| Sent: Friday, October 11, 2013 4:41 PM
| To: CentOS mailing list
| Subject: Re: [CentOS] Centos 6.4 - doesnt power off with 
| shutdown/poweroff cmd
| 
| Try using the reboot=pci grub parameter.
| 
| 
| On Fri, Oct 11, 2013 at 11:40 AM, Terre Porter 
|  wrote:
| 
| > Hello,
| >
| >
| >
| > I'm looking for help figuring out why I am having problems with 
| > shutting down a machine.
| >
| >
| >
| > I have tested the machine using Fedora 19 and Ubuntu 12 Live CD's 
| > and both power down without issues.
| >
| >
| >
| > I added acpi.debug_level=1 to the grub boot as it was suggested to 
| > see more info about ACPI in the logs
| >
| >
| >
| > I found the following ACPI Errors in the /var/log/messages
| >
| >
| >
| > Oct 11 11:51:36 plum kernel: ACPI Error (psargs-0359): [ECEN] 
| > Namespace lookup failure, AE_NOT_FOUND
| >
| > Oct 11 11:51:36 plum kernel: ACPI Error (psparse-0537): Method 
| > parse/execution failed [\] (Node 81fdbeb0), AE_NOT_FOUND
| >
| >
| >
| > Oct 11 11:51:36 plum kernel: ACPI: resource piix4_smbus [io 
| > 0x0b00-0x0b07] conflicts with ACPI region SOR1 [io 0xb00-0xb0f]
| >
| > Oct 11 11:51:36 plum kernel: ACPI: If an ACPI driver is available 
| > for this device, you should use it instead of the native driver
| >
| >
| >
| > I used the Centos 6.4 Live CD last night with no hard drive in the 
| > system.
| >
| >
| >
| > I photo'd the shutdown, here is the type up:
| >
| >
| >
| > Sending all processes the TERM signal...
| >
| > Sendng all processes the KILL signal...
| >
| > Saving random seed:
| >
| > Syncing hardware clock to system time
| >
| > Turning off quotas:
| >
| > umount2: Device or resource busy
| >
| > umount: /dev/.initramfs/live: device is busy.
| >
| > (In some cases useful info about processes that use
| >
| >  the device is found by lsof(8) or fuser(11))
| >
| > init: Re-executing /sbin/init
| >
| > Halting System...
| >
| > r8169 :02:00.0: PME# enabled
| >
| > ACPI: Preparing to enter system sleep state S5
| >
| > ACPI Error (psargs-0359): [PPTS] Namespace lookup failure, 
| > AE_NOT_FOUND
| >
| > ACPI Error (psparse-0537): Method parse/execution failed 
| > [\_SB_.PCI0.SBRG.EPTS] (Node fff88019dbc8c68), AE_NOT_FOUND
| >
| > ACPI Error (psparse-0537): Method parse/execution failed [\PTS_] 
| > (Node 88019d043560), AE_NOT_FOUND
| >
| > ACPI Error (psparse-0537): Method parse/execution failed [\_PTS] 
| > (Node 88019dbcf9e8), AE_NOT_FOUND
| >
| > Disabling non-boot CPUS...
| >
| > SMP alternatives: switching to UP code
| >
| > Power Down.
| >
| > acpi_power_off called
| >
| >
| >
| > The system doesn't power off, it just sits there. I have to hold the 
| > power button in for it to shut down.
| >
| >
| >
| > The same still occurs with a completed a fresh minimum install of 
| > Centos 6.4, installed the EPEL repo and did yum update.
| >
| >
| >
| > I'm running the latest bios for the motherboard, and even tried 
| > going back one version.
| >
| >
| >
| > MB: 785GM-E51 (MS-7596 1.2)
| >
| > CPU: AMD Phenom II x4 945 3ghz
| >
| > 1TB HD, 6 Gig Mem
| >
| >
| >
| > Any ideas?
| >
| >
| >
| > (Besides using a baseball bat - I am considering it)
| >
| >
| >
| > Here is some hardware info from the getinfo.sh script listed the 
| > forums.
| >
| >
| >
| > == BEGIN uname -

Re: [CentOS] VNC

2013-10-11 Thread Terre Porter
Humm,

Could windows machine be blocking the port going out? 

If your using putty as a ssh client you could try to port forward (5901,
5901) through the ssh session and then try to connect using localhost:5901
or localhost:5902 on the windows machine and see if you can connect.

It can be done with other ssh clients but I've only used putty, so I know it
can be done with it.

You might also compare some of the settings to this page
http://wiki.centos.org/HowTos/VNC-Server

You could try stopping the servers and running the vncserver in the console
to see if there are connections or errors - but I'm not sure with the
configuration your using if that is possible.

I'm not sure what else to offer.


-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
Of Larry Martell
Sent: Friday, October 11, 2013 7:13 PM
To: CentOS mailing list
Subject: Re: [CentOS] VNC

On Fri, Oct 11, 2013 at 4:45 PM, Terre Porter
wrote:

> You can specify the port with the IP by using the colon with the ip.
>
> x.x.x.x:5901 or x.x.x.x:5902
>

Those both give me connection refused (as opposed to without the port, where
I get connection timed out)


>
>
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On 
> Behalf Of Larry Martell
> Sent: Friday, October 11, 2013 6:35 PM
> To: CentOS mailing list
> Subject: Re: [CentOS] VNC
>
> On Fri, Oct 11, 2013 at 4:26 PM, Terre Porter
> wrote:
>
> > The instructions out linked to has a type-o at the end says to 
> > connect to
> > ip:5801 should be 5901.
> >
> > If your using a vnc client uvnc,  tightvnc..  try using just the ip 
> > without the :port part or :1 for the 5901.
> >
>
> I am unfortunately connecting from a windows box that I do not have 
> admin rights on.  I have to use the client provided, which is RealVNC 
> Viewer. All I can do is give the ip.
>
>
> > Try  lsof -i -P | grep -i "listen"
> >
> > To see what ports are listening...
> >
>
>
>  [root@10 sysconfig]# lsof -i -P | grep -i "listen"  | grep vnc
> Xvnc  22052   motor4u  IPv4 527366  0t0  TCP
> localhost.localdomain:5901 (LISTEN)
> Xvnc  22286   motor4u  IPv4 530145  0t0  TCP
> localhost.localdomain:5902 (LISTEN)
>
>
> >
> > -Original Message-
> > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] 
> > On Behalf Of Larry Martell
> > Sent: Friday, October 11, 2013 6:05 PM
> > To: CentOS mailing list
> > Subject: Re: [CentOS] VNC
> >
> > On Fri, Oct 11, 2013 at 3:42 PM, Terre Porter
> > wrote:
> >
> > > Try this, iptables dump from my fresh install, with ssh allow and 
> > > the vnc you referenced.
> > >
> > > Terre
> > >
> > > # Generated by iptables-save v1.4.7 on Fri Oct 11 17:39:52 2013 
> > > *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT 
> > > [45:7091] -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT 
> > > -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -p 
> > > tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT -A INPUT -m 
> > > state --state NEW -m tcp -p tcp -m multiport --dports
> > > 5901:5903,6001:6003 -j ACCEPT
> > > -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD 
> > > -j REJECT --reject-with icmp-host-prohibited COMMIT # Completed on 
> > > Fri Oct 11 17:39:52 2013
> > >
> > >
> > OK, with this file I'm getting connection timed out - before I was 
> > getting connection refused so I guess that's some progress.
> >
> > >
> > >
> > > -Original Message-
> > > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org]
> > > On Behalf Of Larry Martell
> > > Sent: Friday, October 11, 2013 5:36 PM
> > > To: CentOS mailing list
> > > Subject: Re: [CentOS] VNC
> > >
> > > On Fri, Oct 11, 2013 at 3:30 PM, Earl Ramirez 
> > >  > > >wrote:
> > >
> > > >
> > > > On Fri, 2013-10-11 at 15:18 -0600, Larry Martell wrote:
> > > > > I'm trying to set up a VNC server using the instructions at
> > > > >
> > > > http://www.techrepublic.com/blog/linux-and-open-source/linux-101
> > > > -e
> > > > as
> > > > y-
> > > > vnc-server-setup/
> > > > > .
> > > > >
> > > > > I am up to step 6:
> > > > >
> > > > > Step 6: Edit iptables
> > > > >
> > > > &

[CentOS] 3.11.5 kernel compile

2013-10-14 Thread Terre Porter
Hey all,

 

I have just compiled the 3.11.5 kernel from kernel.org to fix the ACPI wont
shutdown issue, but I have a couple errors in dmesg I am trying to figure
out.

 

Can anyone point me in the right direction?

 

The errors are:

 

1:

dm_mod: module verification failed: signature and/or required key missing -
tainting kernel

 

2:

[drm] VGACON disable radeon kernel modesetting.

[drm:radeon_init] *ERROR* No UMS support in radeon module!

 

 

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] 3.11.5 kernel compile

2013-10-14 Thread Terre Porter

Humm, since I'm not using a desktop I'm not really wanting to install the
full graphics driver.


-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
Of Patrick Stueck
Sent: Monday, October 14, 2013 2:24 PM
To: CentOS mailing list
Subject: Re: [CentOS] 3.11.5 kernel compile

I believe that you need to use the ATI Radeon beta drivers for the 3.11
kernel branch, I had to anyways.

*__*
*Patrick Stueck*
*Systems Engineer
*(636) 448-5886
RedHat Certified System Administrator | Microsoft Certified Professional
Amateur Radio:  KDØIGO | LinkedIn:  http://www.linkedin.com/in/pstueck
*Confidentiality Notice:
*This E-mail (including attachments) is covered by the Electronic
Communications Privacy Act, 18 U.S.C. §§ 2510-2521, is confidential and may
contain confidential and privledged materials, legally privileged and
protected from disclosure.  This e-mail is intended only for the addressee
named above.  If you are not the intended recipient, you are hereby notified
that any retention, dissemination, distribution, or copying of this
communication is strictly prohibited.  Please reply to the sender that you
have received the message in error, then delete it and any and all copies of
it.


On Mon, Oct 14, 2013 at 12:53 PM, Terre Porter  wrote:

> Hey all,
>
>
>
> I have just compiled the 3.11.5 kernel from kernel.org to fix the ACPI 
> wont shutdown issue, but I have a couple errors in dmesg I am trying 
> to figure out.
>
>
>
> Can anyone point me in the right direction?
>
>
>
> The errors are:
>
>
>
> 1:
>
> dm_mod: module verification failed: signature and/or required key 
> missing - tainting kernel
>
>
>
> 2:
>
> [drm] VGACON disable radeon kernel modesetting.
>
> [drm:radeon_init] *ERROR* No UMS support in radeon module!
>
>
>
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] 3.11.5 kernel compile

2013-10-14 Thread Terre Porter
Akemi,

I installed the ELRepo's kernel-ml and I don't get the dm_mod error, so that
leans toward it likely being something in my kernel build config... 

I started with that kernel, but was unsure about running it in production,
but then again I'm unsure about running the one I built in production - lol.

I do get the Radeon error though.

And I noticed something else I get on both kernels,  "FATAL: Module
scsi_wait_scan not found."

Ugh, getting closer to just buying a new MB.


-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
Of Akemi Yagi
Sent: Monday, October 14, 2013 2:58 PM
To: CentOS mailing list
Subject: Re: [CentOS] 3.11.5 kernel compile

On Mon, Oct 14, 2013 at 10:53 AM, Terre Porter
 wrote:

> I have just compiled the 3.11.5 kernel from kernel.org to fix the ACPI 
> wont shutdown issue, but I have a couple errors in dmesg I am trying 
> to figure out.

> Can anyone point me in the right direction?

Can you give ELRepo's kernel-ml [1] a try to see if you get the same error?
It is currently at 3.11.4 but I'm sure 3.11.5 will be released real soon
now.

Akemi

[1] http://elrepo.org/tiki/kernel-ml
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] 3.11.5 kernel compile

2013-10-14 Thread Terre Porter

I tried the reboot=pci, same result ...

The system doesn't power off, it just sits there. I have to hold the power
button in for it to shut down.

It works in Fedora, Ubuntu, and the new kernel. However, I hate the changes
in Fedora (all the init.d stuff changes) and Ubuntu I haven't used enough to
be comfortable to use in a firewall machine.

I'd be willing to try anything if you have some ideas.

Here is the shutdown text I receive; this was when I had the acpi debug
flags enabled.

Sending all processes the TERM signal...
Sendng all processes the KILL signal...
Saving random seed:
Syncing hardware clock to system time
Turning off quotas:
umount2: Device or resource busy
umount: /dev/.initramfs/live: device is busy.
(In some cases useful info about processes that use 
 the device is found by lsof(8) or fuser(11))
init: Re-executing /sbin/init
Halting System...
r8169 :02:00.0: PME# enabled
ACPI: Preparing to enter system sleep state S5
ACPI Error (psargs-0359): [PPTS] Namespace lookup failure, AE_NOT_FOUND
ACPI Error (psparse-0537): Method parse/execution failed
[\_SB_.PCI0.SBRG.EPTS] (Node fff88019dbc8c68), AE_NOT_FOUND
ACPI Error (psparse-0537): Method parse/execution failed [\PTS_] (Node
88019d043560), AE_NOT_FOUND
ACPI Error (psparse-0537): Method parse/execution failed [\_PTS] (Node
88019dbcf9e8), AE_NOT_FOUND
Disabling non-boot CPUS...
SMP alternatives: switching to UP code
Power Down.
acpi_power_off called



-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
Of Jim Perrin
Sent: Monday, October 14, 2013 4:08 PM
To: CentOS mailing list
Subject: Re: [CentOS] 3.11.5 kernel compile

On 10/14/2013 12:53 PM, Terre Porter wrote:

> I have just compiled the 3.11.5 kernel from kernel.org to fix the ACPI 
> wont shutdown issue, but I have a couple errors in dmesg I am trying 
> to figure out.

Out of curiosity, what shutdown issue? There are several options for
shutdown/reboot that can be passed to the standard kernel which fix issues
like this. (reboot=pci in grub.conf for example)



--
Jim Perrin
The CentOS Project | http://www.centos.org
twitter: @BitIntegrity | GPG Key: FA09AD77
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] 3.11.5 kernel compile

2013-10-14 Thread Terre Porter

That is good info; I'll give them a try.

Thanks


-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
Of Jim Perrin
Sent: Monday, October 14, 2013 4:38 PM
To: CentOS mailing list
Subject: Re: [CentOS] 3.11.5 kernel compile

On 10/14/2013 03:22 PM, Terre Porter wrote:
> 
> I tried the reboot=pci, same result ...
> 
> The system doesn't power off, it just sits there. I have to hold the 
> power button in for it to shut down.
> 
> It works in Fedora, Ubuntu, and the new kernel. However, I hate the 
> changes in Fedora (all the init.d stuff changes) and Ubuntu I haven't 
> used enough to be comfortable to use in a firewall machine.
> 
> I'd be willing to try anything if you have some ideas.
> 


There are several reboot options you could try. They're defined in
/usr/share/doc/kernel-doc-2.6.32/Documentation/x86/x86_64/boot-options.txt

so you could have reboot=bios, reboot=triple, reboot=kbd, reboot=acpi, etc.

Supposedly you can stack them as well, but I prefer cycling through them to
find the one that works, and using it.



--
Jim Perrin
The CentOS Project | http://www.centos.org
twitter: @BitIntegrity | GPG Key: FA09AD77
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] Firewall/Gateway Hardware Question

2013-10-15 Thread Terre Porter
I've given up on getting the other machine to work so I'm looking at
building a new one.

The machine will be a firewall/gateway running NAT, Web Proxy with
Dansguardian, DHCP, DNS, NTP and VPN (~6 clients). 

I read so much about VPN encryption and the processor needs, now I am unsure
if this will work.

I can get this for AMD FX-8120 Zambezi 3.1GHz Socket AM3+ 125W Eight-Core
Desktop Processor for under $120 (it's on sale), would it work ?

Any thoughts?

Thanks,
Terre


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Firewall/Gateway Hardware Question

2013-10-15 Thread Terre Porter
I've not worked with Atom processors but I'll look in to it.

Thanks for the info.


-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
Of SilverTip257
Sent: Tuesday, October 15, 2013 12:36 PM
To: CentOS mailing list
Subject: Re: [CentOS] Firewall/Gateway Hardware Question

On Tue, Oct 15, 2013 at 12:29 PM, Terre Porter  wrote:

> I've given up on getting the other machine to work so I'm looking at 
> building a new one.
>
> The machine will be a firewall/gateway running NAT, Web Proxy with 
> Dansguardian, DHCP, DNS, NTP and VPN (~6 clients).
>
> I read so much about VPN encryption and the processor needs, now I am 
> unsure if this will work.
>

You'll likely need to determine how many VPN tunnels you're going to run
simultaneously and then find benchmarks on the web.


>
> I can get this for AMD FX-8120 Zambezi 3.1GHz Socket AM3+ 125W Eight-Core
> Desktop Processor for under $120 (it's on sale), would it work ?
>

Seems like overkill to me.

I'd suggest more along the lines of an Atom-CPU based system.  One of those
mini-ITX setups that use 20W or thereabouts.

Just my two cents.


>
> Any thoughts?
>
> Thanks,
> Terre
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>



-- 
---~~.~~---
Mike
//  SilverTip257  //
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Firewall/Gateway Hardware Question

2013-10-15 Thread Terre Porter
Interesting looking hardware... thanks for the info

-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of 
S.Tindall
Sent: Tuesday, October 15, 2013 8:29 PM
To: CentOS mailing list
Subject: Re: [CentOS] Firewall/Gateway Hardware Question

On Tue, 2013-10-15 at 18:05 -0400, SilverTip257 wrote:

> @Steve:
> Based on your statement, I figure you do not have a crypto accelerator 
> and the CPU is handling all the crypto.  Correct?

> @Terre:
> I don't know how VIA C7 CPUs stack up against the Intel Atom CPUs in 
> terms of performance, but they're low power consuming x86 processors.  
> And there's the VIA Padlock [0] security/encryption engine.

> AMD Geode CPUs like those in PC Engines ALIX [1] hardware have an 
> integrated crypto accelerator [2].  If it wasn't for your web proxy 
> requirements, etc an ALIX might fit the bill (with the right embedded 
> OS - think Voyage Linux). You're better off with the hardware you're 
> researching right now though.
> 
> [0] http://www.via.com.tw/en/initiatives/padlock/hardware.jsp
> [1] http://www.pcengines.ch/alix.htm
> [2] 
> http://www.twam.info/hardware/alix/using-geodes-aes-engine-on-alix3d3

You should look at the single board computers sold by Soekris Engineering.

 http://soekris.com

Specifically the net6501 series:

 http://soekris.com/products/net6501.html

 Specifications:

  •  600 Mhz to 1.6 Ghz Intel Atom E6xx single chip processor
 with EG20T companion chip
  •  512 to 2048 Mbyte DDR2-SDRAM, soldered on board
  •  2x SATA 3 Gbit interfaces with +5V and +12V power header
  •  4x Intel 82574L Gigabit Ethernet ports, Auto-MDIX RJ-45,
 protected to 700W/40A Surge
  •  2x Serial ports, DB9 and 10 pins internal header
  •  USB 2.0 interface, 2x internal, 1x external port, bootable
  •  1 Full Mini-PCI Express shared with mSATA socket.
  •  1 USB only Mini-PCI Express shared with mSATA socket
  •  2x PCI Express Slots, right angle
  •  16 bit general purpose I/O, 24 pins header, connected to FPGA

...in either a tiny or a rackable box.

The number of lan slots can be increased above 4 by using expansion cards.

Steve



___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Firewall/Gateway Hardware Question

2013-10-15 Thread Terre Porter
I have must have been in a hardware vacuum, have a clue any of that hardware
you mentioned.

Added it to the research list - haha!

Thanks

-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
Of SilverTip257
Sent: Tuesday, October 15, 2013 6:05 PM
To: CentOS mailing list
Subject: Re: [CentOS] Firewall/Gateway Hardware Question

On Tue, Oct 15, 2013 at 2:31 PM, Steve Clark  wrote:

> Hi,
>
> we are running 51 ipsec vpns on an Atom D510 at 1.66ghz and the load 
> average is .07.
>

@Steve:
Based on your statement, I figure you do not have a crypto accelerator and
the CPU is handling all the crypto.  Correct?

@Terre:
I don't know how VIA C7 CPUs stack up against the Intel Atom CPUs in terms
of performance, but they're low power consuming x86 processors.  And there's
the VIA Padlock [0] security/encryption engine.

AMD Geode CPUs like those in PC Engines ALIX [1] hardware have an integrated
crypto accelerator [2].  If it wasn't for your web proxy requirements, etc
an ALIX might fit the bill (with the right embedded OS - think Voyage
Linux). You're better off with the hardware you're researching right now
though.

[0] http://www.via.com.tw/en/initiatives/padlock/hardware.jsp
[1] http://www.pcengines.ch/alix.htm
[2] http://www.twam.info/hardware/alix/using-geodes-aes-engine-on-alix3d3


>
> HTH,
> Steve
>
> On 10/15/2013 02:13 PM, Terre Porter wrote:
> > I've not worked with Atom processors but I'll look in to it.
> >
> > Thanks for the info.
> >
> >
> > -Original Message-
> > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] 
> > On
> Behalf
> > Of SilverTip257
> > Sent: Tuesday, October 15, 2013 12:36 PM
> > To: CentOS mailing list
> > Subject: Re: [CentOS] Firewall/Gateway Hardware Question
> >
> > On Tue, Oct 15, 2013 at 12:29 PM, Terre Porter <
> tpor...@webpage-builders.com
> >> wrote:
> >> I've given up on getting the other machine to work so I'm looking 
> >> at building a new one.
> >>
> >> The machine will be a firewall/gateway running NAT, Web Proxy with 
> >> Dansguardian, DHCP, DNS, NTP and VPN (~6 clients).
> >>
> >> I read so much about VPN encryption and the processor needs, now I 
> >> am unsure if this will work.
> >>
> > You'll likely need to determine how many VPN tunnels you're going to 
> > run simultaneously and then find benchmarks on the web.
> >
> >
> >> I can get this for AMD FX-8120 Zambezi 3.1GHz Socket AM3+ 125W
> Eight-Core
> >> Desktop Processor for under $120 (it's on sale), would it work ?
> >>
> > Seems like overkill to me.
> >
> > I'd suggest more along the lines of an Atom-CPU based system.  One 
> > of
> those
> > mini-ITX setups that use 20W or thereabouts.
> >
> > Just my two cents.
> >
> >
> >> Any thoughts?
> >>
> >> Thanks,
> >> Terre
> >>
> >>
> >> ___
> >> CentOS mailing list
> >> CentOS@centos.org
> >> http://lists.centos.org/mailman/listinfo/centos
> >>
> >
> >
>
>
> --
> Stephen Clark
> *NetWolves*
> Director of Technology
> Phone: 813-579-3200
> Fax: 813-882-0209
> Email: steve.cl...@netwolves.com
> http://www.netwolves.com
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>



--
---~~.~~---
Mike
//  SilverTip257  //
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos