PCLinuxOS Openbox Bonsai 2011 for test

[jlf001]

While not a solution to the slow OpenBox menu update, I did find a temporary fix to quickly update the Openbox menu items, if "Reload Openbox" is not working.  After you install an application and exit Synaptic, open "My Documents" (PCManFM) and click on Applications in the left hand column.  Close PCManFM and go back to the OpenBox menu.  All newly installed applications should now be present.

Jeff

[djohnston]

I'm testing in VBox, but I haven't had any problems with shutdown. Shutdown from right-click menu works as it should. Haven't done anything with the installation today. Yesterday, I set speedboot back to auto in /etc/sysconfig/speedboot. Changed the tint2 clock to show AM/PM instead of the seconds counter. Re-installed VBox guest additions from the VBox menu, as the installed ones weren't working for me. I'm going to add Midori and uninstall Jumanji. Like Galen, it's just not for me.

So far, I've found no issues. I did change the Jumanji folder ownership in /etc/skel before installation. There just doesn't seem to be much control with Jumanji. No, I haven't looked up the customization options for it, other than the sample config on the Arch wiki.

[Taco.22]

Hi,

Not so good news, the history had disappeared from Synaptic. I will redo it starting from the last version that was working allright, I think I have understood it is the one as of 2010-11.

I'll install both one next each other on a hard drive in order to have the new configurations at hand whenever needed, each one will have a different label on the partition, which label will also be their title in grub menu.lst. I'll come back in a few days... Same for Education, I might have to redo it too. Unless other people find the same problem on other versions ? (Could it be a kernel problem ?)

Regards,
Mélodie

Just out of curiosity I downgraded the kernel to 2.6.37.4-pclosos1.bfs.  System now shuts down without rebooting after 20 seconds.  I don't know why - maybe bleeding edge issues?  I know that upgrading my other OB system to the latest kernel created all sorts of issues, so I have kept it at the 2.6.37 edition.   

[melodie]

Just out of curiosity I downgraded the kernel to 2.6.37.4-pclosos1.bfs.  System now shuts down without rebooting after 20 seconds.  I don't know why - maybe bleeding edge issues?  I know that upgrading my other OB system to the latest kernel created all sorts of issues, so I have kept it at the 2.6.37 edition.   

Hi Taco !

Ok, so you said in a former post :

BTW, I have a 2.7ghz P4 with 512mb of RAM and a 6gb HD.

I think I'll open a new thread somewhere (Software ?) about this issue and ask if other people meet with this also. I have met with this in a P 4 with cpu I think is 2.8 Ghz, with hyperthreading.

It would be nice if a few persons could try the kernels which are available in between the 2.6.37.4-pclosos1.bfs and the 2.6.38.8-pclosos1.bfs... I open Synaptic and check which ones we still have... ok, we don't have the former ones in the 2.6.38 serie, so...

Else, what in the configuration of the kernel could explain the difference ? (I don't meet with the issue in my current machine where the latest kernel is installed, a laptop with Celeron inside, and I suppose the people who do have the issue may have the same type of machine ?)

[Taco.22]

Hi Melodie,

Maybe you would consider 2.6.37 as the default rather than 2.6.38 as the later seems to conflict with non duo-core computers.  You could have a help link on the desktop to an html file that a browser would open that explains that the kernel can be upgraded depending on hardware.  I will probably set Blackcat up with the earlier kernel so that all hardware is supported.  There are still a lot of P3/4 'puters out there - two out of our three pcs are P4. 

As an aside, I have noticed an error message during boot with the earlier kernel that goes something along the line of -

conflicting fb hw usage nouveaufb vs vesa vga - removing generic driver

It goes by very quickly so I hope I got it all.  Anyway, is there anything relevant to it?
   

[melodie]

Hi Melodie,

Maybe you would consider 2.6.37 as the default rather than 2.6.38 as the later seems to conflict with non duo-core computers.  You could have a help link on the desktop to an html file that a browser would open that explains that the kernel can be upgraded depending on hardware.  I will probably set Blackcat up with the earlier kernel so that all hardware is supported.  There are still a lot of P3/4 'puters out there - two out of our three pcs are P4.  

As an aside, I have noticed an error message during boot with the earlier kernel that goes something along the line of -

conflicting fb hw usage nouveaufb vs vesa vga - removing generic driver

It goes by very quickly so I hope I got it all.  Anyway, is there anything relevant to it?
  

Hi,

I am not going to consider changing kernel (for the final version anyhow, but for a next test maybe... ) until we do a thread about this issue and have talks with other forum members (Textar will probably look at it too if several other people confirm). At last, Texstar might as well do something to ensure no one will get this kind of problem, for any of the community versions. At the moment, I am not able to start this thread, but if you wish to start it at Software section, it's ok for me.

Note just this : it's not a "non dual-core" issue : we don't know yet. My Intel Celeron is ok with last kernel : never reboots when I order a shutdown. I get this only on the P 4, a Dell, with Hyperthreading (2 virtual cores).

For the message error you noticed, I don't know if it's relevant. It does not look relevant, but all error messages should be provided, as some problems may sometimes cover others.

Regards,
Mélodie

[Taco.22]

Hi Melodie,

I think you might be right regarding the duo-core thing.  Hyperthreading could be the issue - Celeron and others don't have that feature.  It may be that 2.6.38 is not happy with P4 HT.  Or something like that!  I guess I could start a thread along those lines in Software if you think it would help.

Regarding the error message - just something I noted with the change of kernel.  Hasn't had any discernible affect, but thought I would throw it in the pot regardless.   

[melodie]

Hi Taco,

Just 3 feedbacks don't give enough clues to the source of the problem. We know some get the issue, some don't, with the same kernel version, on different machines.

MrBill, could you come back tell us what the specs of your machines are please ? cpu, ram ? Thanks !

Taco, I can't concentrate on a new thread now, so please go ahead : start it, and come back here give the link ? Thank you very much.

[Taco.22]

Melodie,

As I wrote, thus did you reply.  The thread is up at http://www.pclinuxos.com/forum/index.php/topic,93164.0.html.  I hope I worded it up OK.  We will see what comes out of it.

[melodie]

Taco : perfect, thanks !

[gseaman]

Melodie,

As I wrote, thus did you reply.  The thread is up at http://www.pclinuxos.com/forum/index.php/topic,93164.0.html.  I hope I worded it up OK.  We will see what comes out of it.

Have you tried a 2.6.38.8 kernel that is not bfs?

Galen

[melodie]

Have you tried a 2.6.38.8 kernel that is not bfs?

Galen

Hi Galen,

I haven't. Taco, would you try ? Galen you don't have any machine that reboots by itself do you ? I can't test at the moment because I have to do some new installs at first floor... have a desktop with no Internet connection and I need to do some machine moves first (I have one configured and placed elsewhere, well it's complicated to explain but in few words : it will need a few days).

Thanks for the idea, it could work.

Regards,
Mélodie

[gseaman]

Have you tried a 2.6.38.8 kernel that is not bfs?

Galen

Hi Galen,

I haven't. Taco, would you try ? Galen you don't have any machine that reboots by itself do you ? I can't test at the moment because I have to do some new installs at first floor... have a desktop with no Internet connection and I need to do some machine moves first (I have one configured and placed elsewhere, well it's complicated to explain but in few words : it will need a few days).

Thanks for the idea, it could work.

Regards,
Mélodie

Unfortunately, I can't reproduce this error. My older machines are put away. I have a dual core Intel laptop and a quad-core AMD desktop. I haven't tested with the desktop, but if you need me too, I will.

I made the suggestion, because there were some strange freeze-ups with bfs on the newer 2.6.39? kernels, until the problem was fixed. It may be that a lesser problem existed in 2.6.38 that didn't get fixed. If that is the case, a non-bfs kernel for default may be best until we move to 2.6.39 / 3.0.

Galen

[MrBill]

OK I have tried various livecd's again to be sure of the shutdown behavior.
I tried these on two machines -- 1)Dell PIII-1000, 512meg and 2)Gigabyte motherboard, Celeron-1.6 420L (Conroe single core), 2gig.
I get the same results on both machines wrt shutdown/reboot behavior.

The official 2010.11 Bonsai works as it should on both machines.  (As do 2010 versions of LXDE and Xfce.)
The Openbox Bonsai 2011.6.19 test version reboots at 20sec on BOTH machines.
The Openbox full 2011.6.13 RC test version reboots at 20sec on BOTH machines.

The official E17 Enlightenment Lite version 2010.12 works as it should on both machines.
Test version e17 with k2.6.38.4 (from smurfslover on 2011.5.07) reboots at 20sec on BOTH machines.

[melodie]

Hi,

MrBill, would you mind testing Galen's suggestion ? I mean install the 2.6.38.8.pclos1 : non-bfs, reboot to it, and then after doing a few things in the machine, try a shutdown on one or the other, or on the 2 machines you have presented to us ?

That could help us narrow the problem ?

Galen, if you wish to test on your desktop, but I'm not sure about what we are seeking for... if you can take the time.

Thanks to all,
Mélodie