Kernel[-2.6.31-0.dmz.8-liquorix-686 seems to be working pretty fine for me here...is this not the correct one to have??
Back to top

2.6.31-0.dmz.8 is the correct one - 2.6.30-7.dmz.1 is from the past branch.
Back to top

OK....Thanks I thought it was the most recent but like to check. It's flying on my sidux box. Thanks for taking the time to make it possible for us to have it.
Back to top

Installed 2.6.30-7 on my laptop, works fine.

However, my doughter bought a new laptop (Compaq HP 615 ) with the following Hardware :


With kernels 2.6.30 and 2.6. 31 kernels this machine dies immediately on bootup when acpi is on. The booting goes until the two graphics are shown and the message "Loading, please wait" comes up. Several seconds later the sreen goes blank, no further reaction.

When you boot however with acpi=off the machine boots somehow up but only one procssor is reckognised (as seen in above code-box) Obviously all modules and programs dealing with acpi or multiprocessor issuses fail to work also.

Well looks like since 2.6.30 kernels some heavy acpi-problems have been introduced which not only affect older but also brandnew laptops. Its not only related to the liquorix-kernels the sidux-kernels (and maybe all similar kernels) have that too.

For now I am using Kernel 2.6.29-4 liquoriyx kernel on this laptop. See below how this box is seen under this kernel:


regards

Reiner
Back to top

Interesting, try updating the bios on that laptop.
Back to top

@damentz: I have already looked for one, but without success. It is brandnew and shows a build date mid july.

regards

Reiner
Back to top

Unfortunately, the only type of users that have written feedback on any linux forum all used Ubuntu 9.04 as the latest. Ubuntu 9.04 only uses the 2.6.28 kernel so all those issues, if any, are irrelevant and not related to what is current.

Seeing that slh's kernel and mine both fail with your laptop means that the actual code for ACPI has regressed in Linux. All I can say now is to submit a bug report to the kernel project and hopefully someone looks at it upstream.

It may turn out that it's a configuration issue, but you'll need to test something like Ubuntu 9.10 alpha to discover that for me.
Back to top

@damentz:
Do you happen to know where I can get an 9.10 alpha version ? At Ubunto.com I only see. the 9.04.

regards

Reiner


PS: Found it in the meantime, downloading the alpha 6 (which will take me a while on slow dsl) and the test with that.
Back to top

Tested with it after download. It is pretty weird (what else can you expect from an aplha :-)) and I didn't get it booted up completely (Looks like some X-splash runs into a .constant loop, no terminal-screens available).
But it brought me some more boot-parameters to test => lapic, nolapic, noacpi

While nolapici on the actual 2.6.31 liquorix kernel had the same effect as acpi=off; with lapci and nocacpi I could boot up sometimes but usually by trying the next reboot it didn't work again. :-(
Even one time I got it booted bootet without any special parameter (?!=!) so now I am complete puzzled.
Can it be that those "half-intelligent" or Windows-similar BIOSes change internal settings themself ?
Will test further tomorrow

regards

Reiner
Back to top

@damentz:
Just installed your actual 2.6.31 kernel onto my main-machine.
I had many starnge dyings of kontact, kwallet-manager and icewasel (3.53) with the actual sidux-kernel. Iceweasel called manually from a terminal-console had prertty often segmentation faults and now even there were complainings about a wrong machnie-command.

So I decided to test your one and found accidentially a problem during boot-up. When my bluetooth-stick is connect at boot up the kernel dies shortly with the following messages:

I had this twice when i had that bluetooth stick plugind in when trying to boot up. One time I had it also without that stick, next time it booted through. This again really puzzles me.
Currently I am working with that kernel. Unfortunately iceweasel still dies (around 3 times) during typing of this port.
Maybe I will also go back to an earlier kernel on this machine too.

regards

Reiner
Back to top