MSI Neo4 FI hangs without acpi=off

Please attach the output from "sudo dmidecode", then see if there is a BIOS
upgrade available for your system

Created an attachment (id=4175)
dmidecode output

If possible, please upgrade to Dapper's 2.6.15-8 kernel. If you do not want to
upgrade to Dapper, then you can also wait for the Dapper Flight 2 CD's, which
are due out within the next few days.

Let me know if this bug still exists with this kernel.

Just re-installed my desktop machine, it's now running dapper flight 3 + all updates. I'm running kernel 2.6.15-14-686. The problem has gotten worse since breezy :). Now it doesn't boot anymore, it just freezes at the very first line when booting. "Uncompressing Linux...Okay. Booting the kernel." After displaying this line, it just sits there. When i boot with acpi=off, it works, but i have to press the power button to shut the machine down when i want it to power off, it doesn't shut down itself anymore ( which it still did with the breezy kernel )

Please let me know if i can do something!

Just tried 2.6.15-15-686. Issue still persists.

Please try the commands at

https://wiki.ubuntu.com/DebuggingIRQProblems

Specifically, let me know if pci=noacpi works for you. If it does, I can disable ACPI for your particular machine (based on the dmidecode output).

You should see if there is a custom DSDT for your machine, which may allow ACPI to work.

    * Boot the system with the noapic boot parameter: NOT OK
    * Boot the system with the pci=routeirq: NOT OK
    * Boot the system with the pci=noacpi boot parameter: NOT OK
    * Boot the system with the acpi=off boot parameter: WORKS

It seems like only disabling acpi makes the system boot.. Ofcourse then it doesn't shut down automatically when i want to power off my system...

Anything else i could try?

2.6.15-16:

I still have to disable ACPI in order to boot, but my machine shuts down by itself now again, i don't have to press the power button anymore.. :)

Any chance of you running the amd64 variant on your machine?

That is correct! :)

So you are running it? I ask because in a previous comment you mentioned -686 kernel.

Yeah i am, works fine except for the acpi thingy.. I'm not running 64bit userland, it's all 32-bit ( still not all too fine with w32codecs and stuff ;) )

Oh wait.. i'm running 686, not x86_64 :$ Sorry.. I thought there was a 32bit and amd64 variant of my mobo :$ stupid me :$

But can you test the amd64 liveCD to see if the problem still occurs there?

Just tried with the AMD64 Flight4 livecd, same thing.. just hangs there.

2.6.15-18, no change

2.6.15-19, no change

I have a biostar tforce4 u 775 with the nforce4 chipset for intel and an intel 805 dual core cpu and get the exact same problem even as of 2.6.15-26 using the 64bit xeon kernel.

This bug may be fixed in the current edgy developement system. In an effort to track this bug to our latest distribution, it is being targeted for edgy.

Please confirm whether this bug exists in edgy. If not, then please re-attach all related output (e.g. dmesg, oops output) while under edgy.

Latest Edgy CD's can be downloaded from:

http://cdimage.ubuntu.com/releases/edgy/knot-1/

If this image does not boot from you, you can also download a current daily build from:

http://cdimage.ubuntu.com/daily-live/current/

Note that it may only be necessary to boot the LiveCD to see if your bug is fixed. In this case, you do not need to upgrade your installed system at all to confirm it. Certain bugs may require that you do an actual installation.

I am running Edgy knot 3 amd64 on a Turion 64X2 processor. I have this exact problem, I can only boot with acpi=off.

I tried SuSE in frustration, same problem when using kernel 2.6.16 with smp, (supports the dual core), but can boot with acpi using the default kernel (without smp dual core support).

Perhaps an older kernel would work better? I also had this difficulty in booting dapper-drake amd64, but never tried installing that and stepping down to the non smp kernel...

Please try the latest edgy kernel (available some time today): 2.6.17-8.22

Same problem here.
Ubuntu boots only with acpi=off.

I have a Samsung X60 T2300 Chane.

http://www.samsungpc.com/products/x60/x60.htm

I've been trying to use ACPI since Dapper Flight ?, using every kernel since then.
Currently, I am using edgy knot 3, kernel 2.6.17-7 / -10.

I have recompiled the DSDT: no warnings, no errors.

A few annotations:

With no additional boot parameters, ubuntu freezes at
* Loading ACPI modules...
(only pressing the power button works).

Using the quiet option, there is a further error message:
PCI: Cannot allocate resource region 8 of bridge ???:?? [a few numbers]
But none of the options above (i.e. pci=noacpi etc.) work except acpi=off.

According to http://www.linux-on-laptops.com/samsung.html, it seems to work with Debian and OpenSuSE 10.1:
http://oogametogamie.dyndns.org/x60/laptop-samsung-x60.html
http://www.schusdziarra.de/Linux/X60.html

I have tried Bios versions 05xa, 07xa and 08xa (the newest Bios), but no changes.

I have attached the output of dmesg (the error messages of sdhci, introduced in 2.6.17-10 are already reported).

Thanks for any help!
Johannes

Hmm, probably the ACPI error on my system is unrelated to the former posts.
There seems to be a problem in the ACPI | video module.
I've have recompiled the kernel, disabling the video module and APM.
Now ACPI works flawlessly.

Anyway, I have opened a new bug report which describes this behaviour:
https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.17/+bug/64308

Thanks,
Johannes

I've just installed Ubuntu Edgy Beta1, and it boots without problems! So this is fixed for me. Thanks!

This IS NOT fixed in Edgy. My Nforce4 system still freezes at boot on:
[17179572.964000] ACPI: Looking for DSDT ... not found!

https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.17/+bug/71189

I am willing to help fix this. Why is this bug dormant?

Updates to the following packages on, I think, 13 Dec 2006 fixed this problem on my machine:

linux-libc-dev_2.6.17.1-10.34_i386.deb
linux-image-2.6.17-10-generic_2.6.17.1-10.34_i386.deb
linux-headers-2.6.17-10-generic_2.6.17.1-10.34_i386.deb
linux-headers-2.6.17-10_2.6.17.1-10.34_i386.deb

I've upgraded my mobo since then, and i'm no longer using this motherboard. The new board ( an asrock ) boots just fine. I can reproduce this bug anymore.. But since our friend kkrev says it's fixed, i guess this can be finally closed ;)

Thanks!

This can be closed if it's not already. cant see... :)

Just cleaning up tasks per the last sets of comments. Thanks.