MandrivaUsers.org : MB reports shutdown failure - MandrivaUsers.org

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

MB reports shutdown failure

#1 User is offline   angst 

  • Linux newbie forever
  • Group: Members
  • Posts: 55
  • Joined: 17-September 04

Posted 10 November 2011 - 04:16 PM

My HDD with Mandriva 2010.2 died so I purchase a new drive and decided to install 2011. Install went fine and I managed to get updates after using easy-urpmi to find working update servers. Also got rid of that butt ugly Rosa simple launcher. Anyway...

When I restart my computer after shutting down with 2011 my MB BIOS reports a boot failure and to reset BIOS to defaults. Doing so is the only way to get the system to boot again. With my Windows 7 HDD installed I have no problems shutting down and restarting.

Where should I look to fix this? ACPI or APM settings? Somewhere else? Are there logs I should be looking at?

    ****Warning: System BOOT Fail ****
Your system last boot fail or POST interrupted.
Please enter setup to load Default and reboot again.


Motherboard is Asus P5N72-T Premium.

This post has been edited by angst: 10 November 2011 - 09:35 PM

Kidnappster Nerd: "The internet is about the free exchange and sale of other peoples ideas". (Futurama)
--
Mandriva 2011
0

#2 User is offline   Kieth 

  • A Mandriva learner
  • Group: Members
  • Posts: 1,251
  • Joined: 15-November 02

Posted 10 November 2011 - 09:31 PM

Looking at /var/log/syslog might help.

Kieth
0

#3 User is offline   daniewicz 

  • the dude abides
  • Group: Members
  • Posts: 1,897
  • Joined: 01-August 04

Posted 10 November 2011 - 11:19 PM

/var/log/messages
0

#4 User is offline   angst 

  • Linux newbie forever
  • Group: Members
  • Posts: 55
  • Joined: 17-September 04

Posted 10 November 2011 - 11:53 PM

I tried various acpi apm options. Tried lilo vice grub.

Here is a cut of the syslog from shortly before rebooting.

This seems notable but I don't know what to do with it or if it is the problem.
Nov 10 14:23:21 localhost kernel: ACPI: resource nForce2_smbus [io  0x1c00-0x1c3f] conflicts with ACPI region SM00 [io 0x1c00-0x1c05]
Nov 10 14:23:21 localhost kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov 10 14:23:21 localhost kernel: ACPI: resource nForce2_smbus [io  0x1c80-0x1cbf] conflicts with ACPI region SM01 [io 0x1c80-0x1c85]
Nov 10 14:23:21 localhost kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver 



Edited to remove to much probably useless info. see next post.

This post has been edited by angst: 12 November 2011 - 05:19 PM

Kidnappster Nerd: "The internet is about the free exchange and sale of other peoples ideas". (Futurama)
--
Mandriva 2011
0

#5 User is offline   angst 

  • Linux newbie forever
  • Group: Members
  • Posts: 55
  • Joined: 17-September 04

Posted 12 November 2011 - 05:32 PM

After much wailing and gnashing of teeth it looks like this may be a linux kernel bug which affects some Asus motherboards.
Kidnappster Nerd: "The internet is about the free exchange and sale of other peoples ideas". (Futurama)
--
Mandriva 2011
0

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users