Bonsai 2011 last shot - choices

[ongoto]

Hi folks

The script that manages all the preliminaries for shutting down and
then calls a binary to do the deed:
    /etc/rc.d/init.d/halt

This script is broken in so many places, I don't see how it works at all.
There are calls to functions in packages that aren't even installed:
    nut - Network UPS Tools Client Utilities
    nut-cgi - CGI utils for NUT
    nut-devel - Development for NUT Client
    nut-drivers-hal - Network UPS Tools HAL drivers
    nut-server - Network UPS Tools server

    apcupsd - Power management software for APC UPS hardware
    lvm2 - Logical Volume Manager administration tools
    mdadm - A tool for managing Soft RAID under Linux

One call is mis-named:
   kexec_command="/sbin/kexec"
Should be:
   kexec_command="/sbin/pkexec"

The next to the last line tests a variable $INIT_HALT that never gets initialized:
    HALTARGS="-i -d"
    [ "$INIT_HALT" != "HALT" ] && HALTARGS="$HALTARGS -p"

    exec $command $HALTARGS
It's looking for the word 'HALT', and if not found, adds an option to a call to a binary which does the actual shutdown: The test will always fail.
   command="/sbin/reboot" or,
   command="/sbin/halt"

There is one line that syncs the system clock and timezone:
    # update_boot_stage clock
    [ -x /sbin/hwclock ] && action "Syncing hardware clock to system time" /sbin/hwclock --systohc
The correct timezone is important here.

This is not only the situation for Bonzai, but for Gnome (which I use here) and
maybe others.  But they all shutdown ok.   


Then there's the choices the kernel itself has to make at shutdown.  Have a look:
    less /boot/System.map | grep shutdown
    less /boot/System.map | grep halt

[melodie]

Hi ongoto,

I thank you for this research you did. I am astonished that your post didn't get a reply from anyone since yesterday... well maybe it is too early.

I just looked more in detail in your explanations. I have tried this in full root console:

Code: [Select]

[root@herisson ~]# which kexec
which: no kexec in (/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/bin:/usr/local/sbin:/usr/lib/kde4/libexec)
[root@herisson ~]# which pkexec
/usr/bin/pkexec
[root@herisson ~]#
and this:

Code: [Select]

[root@herisson ~]# rpm -qf /usr/bin/pkexec
polkit-0.101-1pclos2011
[root@herisson ~]#
so it is not even /sbin/pkexec.  This might be due to recent changes in the way some packages (here polkit) have been setup.

The next to the last line tests a variable $INIT_HALT that never gets initialized:
    HALTARGS="-i -d"
    [ "$INIT_HALT" != "HALT" ] && HALTARGS="$HALTARGS -p"

    exec $command $HALTARGS
It's looking for the word 'HALT', and if not found, adds an option to a call to a binary which does the actual shutdown: The test will always fail.
   command="/sbin/reboot" or,
   command="/sbin/halt"

I am not sure I understand fully here, but I will ask French buddies to explain me.

Then there's the choices the kernel itself has to make at shutdown.  Have a look:
    less /boot/System.map | grep shutdown
    less /boot/System.map | grep halt

Ho ho !

Code: [Select]

$ less /boot/System.map | grep shutdown
c0107110 T iommu_shutdown_noop
c0107170 t i8259A_shutdown
c010f010 T tboot_shutdown
c0115220 t mce_shutdown
c011ca80 T native_machine_shutdown
c011cc40 T machine_shutdown
c011cc90 T machine_crash_shutdown
c0120120 T lapic_shutdown
c0125940 T native_machine_crash_shutdown
c0129160 t kvm_crash_shutdown
c0129180 t kvm_shutdown
c0150760 t kernel_shutdown_prepare
c0169370 T clockevents_shutdown
c0169fa0 T tick_shutdown_broadcast
c016a5e0 T tick_shutdown_broadcast_oneshot
c018abf0 t default_shutdown
c018acf0 t compat_irq_shutdown
c0194cc0 t ftrace_shutdown.clone.14
c01a5020 T blk_trace_shutdown
c01fac70 T generic_shutdown_super
c0276ae0 T security_socket_shutdown
c0277520 t cap_socket_shutdown
c02b7c30 t pci_device_shutdown
c02bf2d0 t pcie_port_shutdown_service
c02c2f60 T pci_msi_shutdown
c02c34c0 T pci_msix_shutdown
c0300344 T acpi_ut_subsystem_shutdown
c0306780 t pnp_device_shutdown
c030ee10 T tty_shutdown
c0317f70 t tty_port_shutdown
c0318cb0 t pty_unix98_shutdown
c0322500 t con_shutdown
c032a460 t uart_shutdown
c032ee00 t serial8250_shutdown
c03432f0 T device_shutdown
c0343dc0 T sysdev_shutdown
c03464a0 t platform_drv_shutdown
c034deb0 t isa_bus_shutdown
c0350110 t serio_shutdown
c0351c70 t i8042_shutdown
c0367c70 t cmos_do_shutdown
c0368370 t cmos_platform_shutdown
c03683a0 t cmos_pnp_shutdown
c0388540 t platform_driver_shutdown_shim
c0388570 t of_platform_device_shutdown
c038c980 T kernel_sock_shutdown
c038f470 T sys_shutdown
c0390040 T sock_no_shutdown
c03b8a10 t shutdown_scheduler_queue
c03b9380 T dev_shutdown
c03d7220 T tcp_shutdown
c03f92d0 T inet_shutdown
c041b040 t unix_shutdown
c0444dc8 r acpi_shutdown_map.31978
c052ae74 r __ksymtab_generic_shutdown_super
c052da5c r __ksymtab_tty_shutdown
c052e594 r __ksymtab_kernel_sock_shutdown
c052e724 r __ksymtab_sock_no_shutdown
c052f6bc r __ksymtab_tcp_shutdown
c052f994 r __ksymtab_inet_shutdown
c053380c r __kcrctab_generic_shutdown_super
c0534e00 r __kcrctab_tty_shutdown
c053539c r __kcrctab_kernel_sock_shutdown
c0535464 r __kcrctab_sock_no_shutdown
c0535c30 r __kcrctab_tcp_shutdown
c0535d9c r __kcrctab_inet_shutdown
c053cd2a r __kstrtab_generic_shutdown_super
c0544ddb r __kstrtab_tty_shutdown
c05484e8 r __kstrtab_kernel_sock_shutdown
c0548864 r __kstrtab_sock_no_shutdown
c054b123 r __kstrtab_tcp_shutdown
c054b90c r __kstrtab_inet_shutdown
c05c7474 D acpi_gbl_shutdown
c05d2ac0 d event_exit__shutdown
c05d2b20 d event_enter__shutdown
c05d2b80 d __syscall_meta__shutdown
c05d3a88 d types__shutdown
c05d3a90 d args__shutdown
c0613027 t trace_init_flags_enter__shutdown
c0613038 t trace_init_flags_exit__shutdown
c064bfc0 t __event_exit__shutdown
c064bfc4 t __event_enter__shutdown
c064c50c t __p_syscall_meta__shutdown
c064d878 t __initcall_trace_init_flags_exit__shutdownearly
c064d87c t __initcall_trace_init_flags_enter__shutdownearly
$


Code: [Select]

$ less /boot/System.map | grep halt
c0101e70 t lguest_safe_halt
c0110620 t halt
c011ca50 t native_machine_halt
c011cc80 T machine_halt
c0129350 t native_safe_halt
c0129360 t native_halt
c01508b0 T kernel_halt
c0316b90 t tty_ldisc_halt
c0530194 r __ksymtab_kernel_halt
c053619c r __kcrctab_kernel_halt
c053905d r __kstrtab_kernel_halt
c05e67c7 t no_halt
c062f1de t __setup_str_no_halt
c064c7c4 t __setup_no_halt
$

Is the System.map-<kernel-version> generated by the kernel package ? Then we could think that the previous kernel was doing the job in place of the halt file ?

I still don't see very well why it was also rebooting in my machine, as the timezone setup was the same... I didn't check if the time in the BIOS had been changed. :/

There is one line that syncs the system clock and timezone:
    # update_boot_stage clock
    [ -x /sbin/hwclock ] && action "Syncing hardware clock to system time" /sbin/hwclock --systohc
The correct timezone is important here.

I have just added the kernel 2.6.38.8.pclos3.bfs to the install I did yesterday on the desktop Dell Pentium 4 HyperThreading, the system was installed with the timezone setup to Factory, and a while after reboot to the newer kernel : I went to get a coffee, answered to LKJ, then shutdown.

It has not rebooted !

It looks like you might have found the source of the problem ! (Or one of the sources). I'll make a new one with this setup, and hopefully we can say adios to this bug.

I hope the halt file will be fixed. Maybe should we (would you ?) report it at the broken packages section ?

Regards,
Mélodie

[djohnston]

Melodie,

Where is the screen blank done?

Code: [Select]

[darrel@Duron ~]$ xset -q
Keyboard Control:
  auto repeat:  on    key click percent:  0    LED mask:  00000000
  XKB indicators:
    00: Caps Lock:   off    01: Num Lock:    off    02: Scroll Lock: off
    03: Compose:     off    04: Kana:        off    05: Sleep:       off
    06: Suspend:     off    07: Mute:        off    08: Misc:        off
    09: Mail:        off    10: Charging:    off    11: Shift Lock:  off
    12: Group 2:     off    13: Mouse Keys:  off
  auto repeat delay:  660    repeat rate:  25
  auto repeating keys:  00ffffffdffffbbf
                        fadfffefffedffff
                        dfffffffffffffff
                        fff7ffffffffffff
  bell percent:  50    bell pitch:  400    bell duration:  100
Pointer Control:
  acceleration:  2/1    threshold:  4
Screen Saver:
  prefer blanking:  yes    allow exposures:  yes
  timeout:  600    cycle:  600
Colors:
  default colormap:  0x20    BlackPixel:  0    WhitePixel:  16777215
Font Path:
  catalogue:/etc/X11/fontpath.d,built-ins
DPMS (Energy Star):
  Standby: 600    Suspend: 600    Off: 600
  DPMS is Enabled
  Monitor is On
Font cache:
  Server does not have the FontCache Extension
[darrel@Duron ~]$

I've tried removing the Option "DPMS" line in the Device section of xorg.conf, but that made no difference. I've looked at some of the init scripts, but can't find where the screen blank is set. I don't have xset turned on in ~/.config/openbox/autostart.sh.

[melodie]

djohston, I never studied this feature. I found this page:
http://www.shallowsky.com/linux/x-screen-blanking.html

if that helps you, please let me know. And also what exactly do you notice as a behavior, and in what do you want to change it to ?

PS: it seems to me according to the reading that dpms on is set by default in Xorg (in hard... compiled with... ). I just looked into man xset and the solution you are seeking might as well be there. ie:

[s  {blank|noblank}]

       -dpms   The -dpms option disables DPMS (Energy Star) features.

       +dpms   The +dpms option enables DPMS (Energy Star) features.

       dpms flags...
               The  dpms option allows the DPMS (Energy Star) parameters to be
               set.  The option can take up to three numerical values, or  the
               `force'  flag  followed  by  a  DPMS  state.  The `force' flags
               forces the server to immediately switch to the DPMS state spec‐
               ified.   The  DPMS  state  can  be one of `standby', `suspend',
               `off', or `on'.  When numerical values are given, they set  the
               inactivity  period (in units of seconds) before the three modes
               are activated.  The first value  given  is  for  the  `standby'
               mode,  the  second  is for the `suspend' mode, and the third is
               for the `off' mode.  Setting these  values  implicitly  enables
               the DPMS features.  A value of zero disables a particular mode.

?

[Yankee]

PS: it seems to me according to the reading that dpms on is set by default in Xorg (in hard... compiled with... ). I just looked into man xset and the solution you are seeking might as well be there. ie:

@djohnston

Code: [Select]

# the screen will be off if inactive during 10 minutes
# on éteint l'écran après 10mn d'inactivité
#xset dpms 0 0 600 &
# uncomment the next two lines only and screen stays on after 10 minutes
#xset s off &
#xset -dpms &

The above is from my autostart.sh      The last 3 lines are something Texstar posted.
Should keep the screen on if uncommented for the last two lines.

I'm also trying to use "xset dpms force off" for a Standby command.   The screen keeps
turning back on after about 30 seconds.   Need to find the larger documentation to give
the command a permanent option.   I haven't noticed that in the "turnoffmonitor"
package yet.


FYI

[djohnston]

Code: [Select]

# the screen will be off if inactive during 10 minutes
# on éteint l'écran après 10mn d'inactivité
#xset dpms 0 0 600 &
# uncomment the next two lines only and screen stays on after 10 minutes
#xset s off &
#xset -dpms &

The above is from my autostart.sh      The last 3 lines are something Texstar posted.
Should keep the screen on if uncommented for the last two lines.

I'm also trying to use "xset dpms force off" for a Standby command.   The screen keeps
turning back on after about 30 seconds.   Need to find the larger documentation to give
the command a permanent option.   I haven't noticed that in the "turnoffmonitor"
package yet.

I tried the two lines Tex posted. Still got a blank screen after 10 minutes. I exchanged xset dpms force off & for xset -dpms & and got a blank screen immediately after logging in. Mouse movement brought the screen back. Still got a screen blank after 10 minutes.

Melodie, there's no screen blank set in xorg.conf. But, I'm still getting a blank screen after 10 minutes. I just want to turn that off. It must be in an init script somewhere, but I haven't located it yet. I'll keep looking.

[Yankee]

I tried the two lines Tex posted. Still got a blank screen after 10 minutes. I exchanged xset dpms force off & for xset -dpms & and got a blank screen immediately after logging in. Mouse movement brought the screen back. Still got a screen blank after 10 minutes.

Always works on my machine.   Uncomment the one line above those 2 lines.   Should say
xset dpms 0 0 0 &

That's supposed to disable it too.   I think that the setting is a default setting unless you
change it then.

[djohnston]

Always works on my machine.   Uncomment the one line above those 2 lines.   Should say
xset dpms 0 0 0 &

That's supposed to disable it too.   I think that the setting is a default setting unless you
change it then.

Well, I don't know. It's not working here. Here's the relevant portion of autostart.sh:

Code: [Select]

# the screen will be off if inactive during 10 minutes
#xset dpms 0 0 600 &

#uncomment next 2 lines and screen stays on after 10 minutes
#xset off &
#xset -dpms &
#xset dpms force off &
xset dpms 0 0 600 & has always been commented. I tried uncommenting xset off & and xset -dpms &, then logging out and back in. Screen blanked after 10 minutes. I then commented those two lines and uncommented xset dpms force off &, logged out and back in. Screen blanked immediately after login, but mouse movement brought it back. Screen blanked again after 10 minutes. I'll try what you suggested.

I know I can turn this behavior off by installing xscreensaver and setting the right parameters, but that seems like overkill, and tends to defeat the purpose of running Bonsai. I'll keep looking.

[Yankee]

Always works on my machine.   Uncomment the one line above those 2 lines.   Should say
xset dpms 0 0 0 &

That's supposed to disable it too.   I think that the setting is a default setting unless you
change it then.

Well, I don't know. It's not working here. Here's the relevant portion of autostart.sh:

Code: [Select]

# the screen will be off if inactive during 10 minutes
#xset dpms 0 0 600 &

#uncomment next 2 lines and screen stays on after 10 minutes
#xset off &
#xset -dpms &
#xset dpms force off &
xset dpms 0 0 600 & has always been commented. I tried uncommenting xset off & and xset -dpms &, then logging out and back in. Screen blanked after 10 minutes. I then commented those two lines and uncommented xset dpms force off &, logged out and back in. Screen blanked immediately after login, but mouse movement brought it back. Screen blanked again after 10 minutes. I'll try what you suggested.

I know I can turn this behavior off by installing xscreensaver and setting the right parameters, but that seems like overkill, and tends to defeat the purpose of running Bonsai. I'll keep looking.

Hi,

The "xset dpms force off" command isn't part of the solution.   It's a command line to force
a screen to shut off from terminal.   I'm trying to use it on the OpenBox menu with obmenu,
so far so good.   

xset s off &
xset -dpms &

Uncommented the above should work, the "s" is req'd.   Nothing else should uncommented.
Take # out before the command will run the command on that line.

Or,

xset dpms 0 0 0 &

Uncommented the above should work, the "0" is req'd not the "600".   Nothing else should uncommented.


I think I saw a typo and that's why neither would work.   Double check the typo and it should
work.   Don't put "xset dpms force off" in the autostart.sh because if you uncomment it, it will run,
it's meant to be run from the command line.

Regards,

Patrick

[melodie]

Hi,

I borrowed most of theses configs from another distro and didn't know how to use xset or the purpose of dpms. This is where now I am interested about your question and start to see where it goes to (watch a movie without having the screen that turns black if I don't type on a key ?)

So you can uncomment what you need (except the paragraph for the xcompmgr effects if you want to be able to use them, but this is explained in that one part), and you can add commands to this autostart.sh file at will. I will try Ferdes Fides suggest and use "xset dpms 0 0 0 &" next time I watch a movie on one of my machines. Then I will tell you how it goes here ! ^^

[melodie]

Or,

xset dpms 0 0 0 &

Uncommented the above should work, the "0" is req'd not the "600".   Nothing else should uncommented.


I think I saw a typo and that's why neither would work.   Double check the typo and it should
work.   Don't put "xset dpms force off" in the autostart.sh because if you uncomment it, it will run,
it's meant to be run from the command line.

Regards,

Patrick

Hi Patrick,
You give me ideas for the next set of configuration files... thanks for your help on this matter.

[Yankee]

Or,

xset dpms 0 0 0 &

Uncommented the above should work, the "0" is req'd not the "600".   Nothing else should uncommented.


I think I saw a typo and that's why neither would work.   Double check the typo and it should
work.   Don't put "xset dpms force off" in the autostart.sh because if you uncomment it, it will run,
it's meant to be run from the command line.

Regards,

Patrick

Hi Patrick,
You give me ideas for the next set of configuration files... thanks for your help on this matter.

Hi,

When I run xset dpms......something.......   it acts differently from the command line than if
it activates at boot.    When activated at boot everything goes off in 10 minutes, from the
command line little things like CPU charts moving will turn the screen back on.   My observation
on my machine here.   Never had it black out a movie yet.    "xset dpms force standby" just
isn't as strong as a Screensaver program.   Still needs a little testing, you know.

Regards,

Patrick

[melodie]

Hi,

I just never ran it up to now. I didn't have the xscreensaver installed either and was living with this... a movie once a while as otherwise I watch on another machine which I am not the one who manages it. I'll let you do the tests for this one and let us know what is best and or more relevant.

Regards,
Mélodie

[djohnston]

Take # out before the command will run the command on that line.

Way ahead of you on that one, Patrick. But I do appreciate the effort of a full explanation.

xset s off &
xset -dpms &

Or,

xset dpms 0 0 0 &

Okay, I tried uncommenting just the line xset dpms 0 0 0 &. Did a reboot this time and logged back in. When I next checked the screen, it had blanked.

So, I commented out that line, and uncommented these lines, in the order you gave them.

xset s off &
xset -dpms &

Bingo! We have a winner. That's the combination I've been looking for. Although the xset man page isn't very big, I was getting tired of re-reading it. For the time being, anyway. And ya just gotta love this line, towards the end of the man page:

Note that not all X implementations are guaranteed to honor all of these options.

An invitation to experimentation? Well, my experimenting's done for now. I really appreciate your help with this, Patrick. Now I won't have to use the lazy solution of installing xscreensaver, starting the daemon from a script at login, and turning all the screen blanking options off.

[melodie]

An invitation to experimentation? Well, my experimenting's done for now. I really appreciate your help with this, Patrick. Now I won't have to use the lazy solution of installing xscreensaver, starting the daemon from a script at login, and turning all the screen blanking options off.

Good idea. I'll have to add theses options (default commented) in the next configuration files provided with openbox-menu.