PCLinuxOS Openbox Bonsai 2011 for test

[AS]

posted a note here:
http://www.pclinuxos.com/forum/index.php/topic,93164.msg782811.html#msg782811

 

AS

[MrBill]

ok.  I first installed Bonsai from the CD.  Then I changed to kernel 2.6.37.4.bfs.  Then to kernel 2.6.38.8.no bfs.

Here is dmesg after each:

http://pastebin.com/f3DzQz5Z
http://pastebin.com/jxKTgN19
http://pastebin.com/dhwMM9pF

[MrBill]

I think the information provided by as is more valuable than my logs.  But I will try to link my message log if you think it will help.  But it is huge--with all history from first installation yesterday.  Tell me if I should try to link it.

But my experience is the same as as,  shutdown/reboot problem with 38.8.bfs and 38.8(no bfs), no problem with 37.4.bfs.

[djohnston]

Whether it's BFS, PAE or BFS PAE, or just the straight kernel, I've had no shutdown / reboot problems.  The only time this happened was with the live Bonsai testCD.

Melodie,

I just installed on a very old test box. Specs are AMD Duron @ 900mHz, only 320MB RAM. This is helped out by an ATI Radeon 9400GS video card. My experience is the same as Jeff's. Selecting Shutdown from Openbox menu on the liveCD resulted in a reboot, after removing the CD from the tray, and about 20 seconds had elapsed. After installation to hard drive, same 2.6.38.8.bfs kernel, shutdown worked normally, done from both the Openbox menu and from the login menu screen.

Performance is very snappy on this old machine. Slightly less than 200MB RAM used with the desktop loaded. Swap partition and ZRAM are, so far, untouched.

[MrBill]

YES

I think user as has found the solution.  See his post above.  I changed grub menu.lst to acpi=off and th reboot problem is gone on my Dell PIII machine with the 2.6.38.8.xxx kernel.  Simple!

So apparently some machines have an issue with acpi and the 38.8 kernel.  And melodie was on the right track with her original suggestion to change acpi=forced,  but "forced" did not work on my machine.

Everyone have a good weekend.  I'll visit back here on Monday.

[djohnston]

I think user as has found the solution.  See his post above.  I changed grub menu.lst to acpi=off and th reboot problem is gone on my Dell PIII machine with the 2.6.38.8.xxx kernel.  Simple!

So apparently some machines have an issue with acpi and the 38.8 kernel.  And melodie was on the right track with her original suggestion to change acpi=forced,  but "forced" did not work on my machine.

And you call yourself a novice, MrBill. Keep an eye out for Sluggo!

[ka9yhd]

Live CD runs great on my laptop, with the exception of the wireless.
I am using a wired connection for the moment.  Next step is to backup all of my files and install.

[AS]

YES

I think user as has found the solution.  See his post above.  I changed grub menu.lst to acpi=off and th reboot problem is gone on my Dell PIII machine with the 2.6.38.8.xxx kernel.  Simple!

So apparently some machines have an issue with acpi and the 38.8 kernel.  And melodie was on the right track with her original suggestion to change acpi=forced,  but "forced" did not work on my machine.

Everyone have a good weekend.  I'll visit back here on Monday.

... No ...
I don't think it's correct to say that some machine have an issue with acpi, the same machine work without any issue using the test3-KDE-iso that use the same kernel, the same udev packages and the same acpi packages.

The issue still need to be found. 

AS

[melodie]

YES

I think user as has found the solution.  See his post above.  I changed grub menu.lst to acpi=off and th reboot problem is gone on my Dell PIII machine with the 2.6.38.8.xxx kernel.  Simple!

So apparently some machines have an issue with acpi and the 38.8 kernel.  And melodie was on the right track with her original suggestion to change acpi=forced,  but "forced" did not work on my machine.

Everyone have a good weekend.  I'll visit back here on Monday.

... No ...
I don't think it's correct to say that some machine have an issue with acpi, the same machine work without any issue using the test3-KDE-iso that use the same kernel, the same udev packages and the same acpi packages.

The issue still need to be found. 

AS

Yes and no. The acpi issue on some motherboards is a very well known fact. It's very technical stuff so when I approached the problem, a few years ago, I stayd stucked at the part where some dev had written a patch for buggy acpi... I don't patche kernels (I have compiled 2 kernels a few years ago, just for the experience going through all the configuration menus).

A thread at kerneltrap here might interest you, even if as for myself you don't get it all ?
Patching kernel to work around buggy ACPI BIOS
http://kerneltrap.org/mailarchive/openbsd-misc/2010/5/11/2823

We here have a problem just because of the boot stanza in the menu.lst, as you have brilliantly found and explained us at the other thread.

The motherboard where I get the issue is a Dell : what are your's ?

MrBill:
Your first and last dmesg are ok. The second one shows errors, starting line 229:

ERROR: Unable to locate IOAPIC for GSI 13
pnp 00:03: [irq 13]
pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
pnp 00:04: [io  0x0061]
pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
pnp 00:05: [io  0x0070-0x007f]
ERROR: Unable to locate IOAPIC for GSI 8
pnp 00:05: [irq 8]
pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
pnp 00:06: [io  0x03f0-0x03f5]
pnp 00:06: [io  0x03f7]
ERROR: Unable to locate IOAPIC for GSI 6
pnp 00:06: [irq 6]
pnp 00:06: [dma 2]
pnp 00:06: Plug and Play ACPI device, IDs PNP0700 (active)
pnp 00:07: [io  0x0060]
pnp 00:07: [io  0x0064]
ERROR: Unable to locate IOAPIC for GSI 1
pnp 00:07: [irq 1]
pnp 00:07: Plug and Play ACPI device, IDs PNP0303 (active)
pnp 00:08: [io  0x03f8-0x03ff]
ERROR: Unable to locate IOAPIC for GSI 4
pnp 00:08: [irq 4]
pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
pnp 00:09: [io  0x02f8-0x02ff]
ERROR: Unable to locate IOAPIC for GSI 3
pnp 00:09: [irq 3]
pnp 00:09: Plug and Play ACPI device, IDs PNP0501 (active)
pnp 00:0a: [io  0x0378-0x037f]
pnp 00:0a: [io  0x0778-0x077f]
ERROR: Unable to locate IOAPIC for GSI 7

I don't know what is GSI... but I know more or less what IOAPIC is related to. http://en.wikipedia.org/wiki/Advanced_Programmable_Interrupt_Controller

with that one kernel, maybe would you try the option on kernel boot "noapci" (without the quotes, but just "as is").

The option I suggested before is not "acpi=forced" but "acpi=force". Sure it can also take the parameters "on" or "off". Or not to be there at all.

The kernel can also take other parameters such as "noapic", or "noapic nolapic"... here is a list, I give here mainly for "culture". I'm not able to understand most of the parameters presented there, but I still find it interesting to look at.
http://www.kernel.org/doc/Documentation/kernel-parameters.txt

Thanks to all,
Mélodie

[AS]

Although I know that some motherboard/BIOS may be bugged, think this not the case. As I wrote before my test machine is an EEE-BOX, see link for extended info, and it run without any issue using the same kernel from others iso, notably the test/test2/test3-pclinuxos-KDE-iso.
I had even deleted and later reinstalled the same kernel to be sure it was exactly the official kernel.

We here have a problem just because of the boot stanza in the menu.lst

sorry, I disagree here. I can use the same boot stanza on the test3-pclinuxos-kde-iso without the restart issue.

I believe that *some bug may exist in kernel 2.6.38.8, it show out using bonsai-test-iso, doesn't show using test3-kde-iso*, nothing less and nothing more right now.

I was thinking at a "kernel panic" at time of shutdown, (there exist some kernel parameter where you can set the restart time in case of kernel crash..),
but haven't found nothing relevant.

from sysctl -a | grep panic

kernel.panic = 0
kernel.panic_on_oops = 0
kernel.unknown_nmi_panic = 0
kernel.panic_on_unrecovered_nmi = 0
kernel.panic_on_io_nmi = 0
vm.panic_on_oom = 0

The use of ACPI=off turn out to change the commands used to turn off the PC, so, may be the ACPI=off may actually only hide the real issue.

This restart issue still need to be investigate a bit further.

AS

[melodie]

Hi AS,

I am happy you are coming for help. I would just add this to what you say : the kernel might have a bug, we also have to consider that the reboot after 20 seconds occurs only on a few machines, and might have not been noticed if there were not several people from the present forum to report about it. We can thank MrBill and his first report about that... having the same problem with the Dell P4 and pclos edu, Taco the same problem with Astronomy on his machine, we just thought our machines were the problem...

If you have things to suggest me to try, I will. Anyhow I can try the option acpi=off before remastering, and we can test... I might even try that with the pclos edu, as it would need a new test version now. (We got a problem with the pclosedu gdm theme refusing to load... )

Thanks again !

[AS]

Hi AS,

I am happy you are coming for help. I would just add this to what you say : the kernel might have a bug, we also have to consider that the reboot after 20 seconds occurs only on a few machines, and might have not been noticed if there were not several people from the present forum to report about it. We can thank MrBill and his first report about that... having the same problem with the Dell P4 and pclos edu, Taco the same problem with Astronomy on his machine, we just thought our machines were the problem...

If you have things to suggest me to try, I will. Anyhow I can try the option acpi=off before remastering, and we can test... I might even try that with the pclos edu, as it would need a new test version now. (We got a problem with the pclosedu gdm theme refusing to load... )

Thanks again !

I have a question:

what's are the difference between test-openbox-bonsai, and test3-kde-iso, at kernel/system level ?
the first that come to my mind is zram, that I've noticed about ... may be others exists.

AS

[melodie]

I have a question:

what's are the difference between test-openbox-bonsai, and test3-kde-iso, at kernel/system level ?
the first that come to my mind is zram, that I've noticed about ... may be others exists.

AS

As far as I know it's the only addition. Otherwise, the shutdown, reboot, sleep and logout which are initiated with theses command lines:

        <item label="Log Out">
         <action name="SessionLogout">
            <prompt>yes</prompt>
         </action>
        </item>
      <item label="Reboot">
         <action name="Execute">
            <execute>dbus-send --system --dest=org.freedesktop.Hal --print-reply /org/freedesktop/Hal/devices/computer org.freedesktop.Hal.Device.SystemPowerManagement.Reboot</execute>
         </action>
        </item>     
       <item label="Shutdown">
         <action name="Execute">
            <execute>dbus-send --system --dest=org.freedesktop.Hal --print-reply /org/freedesktop/Hal/devices/computer org.freedesktop.Hal.Device.SystemPowerManagement.Shutdown</execute>
         </action>
        </item>   
        <separator />
      <item label="Suspend">
         <action name="Execute">
            <execute>dbus-send --system --dest=org.freedesktop.Hal --print-reply /org/freedesktop/Hal/devices/computer org.freedesktop.Hal.Device.SystemPowerManagement.Suspend int32:0</execute>
            </action>
      </item>

You can find them in the /home/user/.config/openbox/menu.xml file. In the versions with lxpanel, it is also in the file /usr/local/bin/shutdown-dialog.py, which is called from the button menu of the panel.

[AS]

You can find them in the /home/user/.config/openbox/menu.xml file. In the versions with lxpanel, it is also in the file /usr/local/bin/shutdown-dialog.py, which is called from the button menu of the panel.

wondering if we are speaking of the same thing ... can't find that file in pclinuxos-openbox-bonsai-test-2011-06-19.iso

 

[melodie]

You can find them in the /home/user/.config/openbox/menu.xml file. In the versions with lxpanel, it is also in the file /usr/local/bin/shutdown-dialog.py, which is called from the button menu of the panel.

wondering if we are speaking of the same thing ... can't find that file in pclinuxos-openbox-bonsai-test-2011-06-19.iso

 

The bonsai test iso does not have shutdown-dialog.py in the system anymore, because it is needed only for the shutdown menu which is located under the menu button of the Lxpanel. Exit lxpanel : no more need for shutdown-dialog.py.

You find theses commands in the file /home/guest/.config/openbox/menu.xml.

This gave me an idea :I started to look if I could get the new command lines from ArchCtk to work on PCLinuxOS. They use the ConsoleKit commands instead of the Hal commands.

For restart:
dbus-send --system --print-reply --dest=org.freedesktop.ConsoleKit /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Restart

For shutdown:
dbus-send --system --print-reply --dest=org.freedesktop.ConsoleKit /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop

For now, I get a "non-authorised" message, but I'll try to digg in that direction.
(The message: Error org.freedesktop.ConsoleKit.Manager.NotPrivileged: Not Authorized - I looked into /etc/dbus1/system.d/ConsoleKit.conf and compared with the one in ArchCtk, but they are identical)

I don't know if that could be the way to solve the problem but if I could get rid of Hal for theses commands it could be a good idea anyhow.

I would like to ask the persons who test here, how it goes on their machines whith shutdown, with the kernel 2.6.38.8.bfs, if they shutdown as root in console with the command "shutdown -h now"  (without the quotes) ?

Thanks.