List,
Did not get any response from the first attempt, so thought I'd ask again.
I've been bugged by the fact that the dpms function will not work on this machine, and perhaps now I have some clue as to why. Looking at the Xorg.0.log, I see where "Open APM failed (/dev/apm_bios) (No such file or directory)" which tells me perhaps this is the reason why it won't turn off the monitor. Also, this line prior to the other. `fonts.dir' not found (or not valid) in "/usr/X11R6/lib/X11/fonts/local/". That part I can maybe fix, but I have no clue what should be in the /dev/apm. The only thing that will happen is the monitor will go into screeensaver mode, or if no saver selected, it will do nothing, not even blank.
What should the /dev/apm contain? Where does it pick up the info as to what should be in there, from a probe of the hardware? That said, does the fact that I'm using a custom video driver from ATI make any difference?
Thanks for any help.....
On Sat, 2005-09-24 at 18:05 -0400, Sam Drinkard wrote:
List,
Did not get any response from the first attempt, so thought I'd ask again.
I've been bugged by the fact that the dpms function will not work onthis machine, and perhaps now I have some clue as to why. Looking at the Xorg.0.log, I see where "Open APM failed (/dev/apm_bios) (No such file or directory)" which tells me perhaps this is the reason why it won't turn off the monitor. Also, this line prior to the other. `fonts.dir' not found (or not valid) in "/usr/X11R6/lib/X11/fonts/local/". That part I can maybe fix, but I have no clue what should be in the /dev/apm. The only thing that will happen is the monitor will go into screeensaver mode, or if no saver selected, it will do nothing, not even blank.
What should the /dev/apm contain? Where does it pick up the info asto what should be in there, from a probe of the hardware? That said, does the fact that I'm using a custom video driver from ATI make any difference?
Thanks for any help.....
Sam-
On my laptop, which is using ACPI (default with the newer distros/kernels), I see see the same message in my Xorg.0.log
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
However, I do see the following from DPMS
(II) Loading extension DPMS (**) Option "dpms" (**) RADEON(0): DPMS enabled
Do you have
Option "dpms"
in your monitor line of xorg.conf?
Alternatively, if your computer has apm bios, you can add
acpi=off
to the kernel entry in /etc/grub.conf and reboot. Some server class hardware (machines with ServerWorks chipsets) don't have an apm bios.
Also, Are you running the screensaver? If you are running Gnome, go to Preferences > Screensaver and in the Advanced tab, make sure that Power Management Enabled is selected.
Hope this helps.
Thanks for the info Sean. There is / was no entry in the xorg.conf indicating dpms or apm either. I added the dpms under the monitor 0 section. I'd already checked to see if the screensaver had dpms enabled and it was. Now if it does not work, I'll start thinking even more about this mobo having problems. I have already gotten numerous messages during post that the core voltage on cpu0 and cpu1 were either overvoltage or undervoltage, and after hearing a relatively loud "pop" a few days ago, even more suspicios. Have never seen that with any mobo, and I've been thru a few in the past 30 years. I'd hate to see a pair of 3.0G Xeons get toasted by a faulty voltage regulator, and I still need to investigate the pop noise and see if I can find the capacitor that shot. Never ever will I buy a Tyan board.. just not the quality of the Asus boards.
Hello all,
When we upgrade no matter what server type (hardware) from 4.0 to 4.1 CentOS our systems lock up on reboot .. Anyone else seeing this ??
If so what's the fix?
BRW
On Saturday 24 September 2005 21:23, Brian Watters wrote:
Hello all,
When we upgrade no matter what server type (hardware) from 4.0 to 4.1 CentOS our systems lock up on reboot .. Anyone else seeing this ??
Nope - have not seen that and we upgraded quite a few boxes 4.0 -> 4.1 How did you perform the upgrade? Can you post the exact output you're getting before the system locks up?
Peter.
On 9/24/05, Brian Watters brwatters@abs-internet.com wrote:
Hello all,
When we upgrade no matter what server type (hardware) from 4.0 to 4.1 CentOS our systems lock up on reboot .. Anyone else seeing this ??
Works fine here.
If so what's the fix?
Need more information to offer realistic advice. What third party software is installed, anything consistent between the machines that lock, and non-standard kernel modules, etc. How far the reboot procedure does it get. Can you ssh in or is it completely non-responsive.
You will be required to provide details for us to provide help.
-- Jim Perrin System Administrator - UIT Ft Gordon & US Army Signal Center
We are unable to get CentOS 4.x Postgres to work .. It gives the following error when we attempt to start ..
Sep 24 18:20:28 abs250 postgresql: Starting postgresql service: failed
Ideas??
BRW
On 9/24/05, Brian Watters brwatters@abs-internet.com wrote:
We are unable to get CentOS 4.x Postgres to work .. It gives the following error when we attempt to start ..
Sep 24 18:20:28 abs250 postgresql: Starting postgresql service: failed
Ideas??
You can check your log files for more detail. As wild speculation made without any details, I'd assume selinux is enabled and blocking access to a file. There was a problem with the selinux policy and postgresql. I don't recall if that was fixed or not, as I don't use postgresql.
-- Jim Perrin System Administrator - UIT Ft Gordon & US Army Signal Center
On Sat, 2005-09-24 at 21:32 -0400, Jim Perrin wrote:
On 9/24/05, Brian Watters brwatters@abs-internet.com wrote:
We are unable to get CentOS 4.x Postgres to work .. It gives the following error when we attempt to start ..
Sep 24 18:20:28 abs250 postgresql: Starting postgresql service: failed
Ideas??
You can check your log files for more detail. As wild speculation made without any details, I'd assume selinux is enabled and blocking access to a file. There was a problem with the selinux policy and postgresql. I don't recall if that was fixed or not, as I don't use postgresql.
If they would switch PGLOG from /dev/null to /var/lib/pgsql for default you might actually log something useful :-)
grep "/dev/null" /etc/init.d/postgresql
Ted
If they would switch PGLOG from /dev/null to /var/lib/pgsql for default you might actually log something useful :-)
wow.. god forbid that happen :-P
I wasn't aware they did that. Still, if it doesn't even start there may be hints in /var/log/messages, or possibly an selinux error to confirm my wild speculation. Thanks for the pointer on the logging though. That's good to know.
grep "/dev/null" /etc/init.d/postgresql
Ted
-- Jim Perrin System Administrator - UIT Ft Gordon & US Army Signal Center
just remember that if you modify /etc/init.d/postgresql the next time you update postgresql via rpm, it will blow away your changes to it.
cheers!
On 9/25/05, Jim Perrin jperrin@gmail.com wrote:
If they would switch PGLOG from /dev/null to /var/lib/pgsql for default you might actually log something useful :-)
wow.. god forbid that happen :-P
I wasn't aware they did that. Still, if it doesn't even start there may be hints in /var/log/messages, or possibly an selinux error to confirm my wild speculation. Thanks for the pointer on the logging though. That's good to know.
grep "/dev/null" /etc/init.d/postgresql
Ted
-- Jim Perrin System Administrator - UIT Ft Gordon & US Army Signal Center _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Sat, 24 Sep 2005, Brian Watters wrote:
We are unable to get CentOS 4.x Postgres to work .. It gives the following error when we attempt to start ..
Sep 24 18:20:28 abs250 postgresql: Starting postgresql service: failed
Ideas??
Sure: Manually strace a start attempt, not using the canned initscript, and see why it is dying.
- Russ Herrold
-
Brian Watters -
data zone -
Jim Perrin -
Peter Arremann -
R P Herrold -
Sam Drinkard -
Sean O'Connell -
Ted Kaczmarek