Page: Previous  1, 2, 3  Next

deach
Status: Contributor
Joined: 08 Sep 2008
Posts: 66
Reply Quote
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
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 1007
Reply Quote
2.6.31-0.dmz.8 is the correct one - 2.6.30-7.dmz.1 is from the past branch.
Back to top
deach
Status: Contributor
Joined: 08 Sep 2008
Posts: 66
Reply Quote
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
reiner
Status: Contributor
Joined: 28 Jul 2009
Posts: 119
Location: Germany
Reply Quote
Installed 2.6.30-7 on my laptop, works fine.

However, my doughter bought a new laptop (Compaq HP 615 ) with the following Hardware :
:: Code ::
Host/Kernel/OS  "CarmensHP615" running Linux 2.6.31-1.slh.1-sidux-amd64 x86_64 [ sidux 2009-02 Αιθήρ - kde-full - (200907141427) ]
CPU Info        AMD AthlonX2 DualCore QL-64 512 KB cache flags( sse3 nx lm svm ) clocked at [ 2100.277 MHz ]
Videocard       ATI RS780M/RS780MN [Radeon HD 3200 Graphics]  tty resolution ( 128x48 )
Network cards   Marvell Device 4357, at port: 3000
                Broadcom BCM4312 802.11b/g
Processes 91 | Uptime 10min | Memory 153.2/3712.6MB | HDD Hitachi HTS54323 Size 320GB (9%used) | Runlevel 5 | Client Shell | Infobash v3.25


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:
:: Code ::
System:    Host CarmensHP615 Kernel 2.6.29-4.dmz.4-liquorix-amd64 x86_64 (64 bit) Distro sidux 2009-02 Αιθήρ - kde-full - (200907141427)
CPU:       Dual core AMD AthlonX2 DualCore QL-64 (SMP) cache 1024 KB flags (sse3 nx lm svm) bmips 8411.2
           Clock Speeds: (1) 2100.00 MHz (2) 1050.00 MHz
Graphics:  Card ATI RS780M/RS780MN [Radeon HD 3200 Graphics] tty res: 128x48
Audio:     Card ATI SBx00 Azalia (Intel HDA) driver HDA Intel
           Sound: Advanced Linux Sound Architecture Version 1.0.18a
Network:   Card-1 Marvell Device 4357 driver sky2 at port 3000
           Card-2 Broadcom BCM4312 802.11b/g
Disks:     HDD Total Size: 320.1GB (9.1% used) 1: /dev/sda Hitachi HTS54323 320.1GB 36C
Partition: ID:/ size: 245G used: 3.7G (2%) ID:swap-1 size: 8.58GB used: 0.00GB (0%)
Sensors:   System Temperatures: cpu: 60.0C mobo: 30.0C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes 102 Uptime 3 min Memory 148.8/3712.6MB Client Shell inxi 1.1.13


regards

Reiner
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 1007
Reply Quote
:: Quote ::
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.


Interesting, try updating the bios on that laptop.
Back to top
reiner
Status: Contributor
Joined: 28 Jul 2009
Posts: 119
Location: Germany
Reply Quote
@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
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 1007
Reply Quote
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
reiner
Status: Contributor
Joined: 28 Jul 2009
Posts: 119
Location: Germany
Reply Quote
@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
reiner
Status: Contributor
Joined: 28 Jul 2009
Posts: 119
Location: Germany
Reply Quote
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
reiner
Status: Contributor
Joined: 28 Jul 2009
Posts: 119
Location: Germany
Reply Quote
@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:
:: Code ::
kinit: no resume image
sh: can not kill pid 434 No such process
init: line 253 can't open /root/dev/console: no such file
kernel panic - not syncing: Attempted to kill init


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
Display posts from previous:   
Page: Previous  1, 2, 3  Next
All times are GMT - 8 Hours