https://bugzilla.novell.com/show_bug.cgi?id=619754 https://bugzilla.novell.com/show_bug.cgi?id=619754#c71 --- Comment #71 from Russ Fineman <upscope@nwi.net> 2010-09-10 18:48:31 UTC --- I finally got to play with this yesterday. Configuration: Intel DX48BT2 motherboard, Intel flash Bios, four GB DDR3, Nvidia GeForce 8400GS, 320 GB Seagate Sata Drive (openSuse 11.2), 320 GB Seagate (openSUSE 11.4), 1 TB Seagate Sata Drive (openSUSE 11.3) Also external 1TB MyBook (Backups for all three internal drives) and a 230 GB external Maxstor in a Pata to usb converter chassis. (11.3 production backup and also a paration for XP on VirtualBox. Windows XP not installed at this time. I completely reinstalled the git kernel (2.6.36-rc3-12-default+) using full path names. Saw no errors in make, just some warnings. make ended and came to command line. No completed successfully type message. did all the steps outlined above and restarted 11.3 with git kernel, nomodeset and No KMS in Initrd=yes. 11.3 System: Typed sudo shutdown -t5 -h now and also without the -t parameter, still hangs at powerdown message. Also tried with su and init 3 level, same results on both versions (2.6.34-12-default and 2.6.36-rc3-12-default+). Then I tryed again (both ways) with the acpi logging increased as per comment #11. Stops at powerdown does not post the sleep message on the line after like it did in August (comment 11, 12). Also checked the button (Shutdown) itself and both suspend to RAm and Disk are unchecked (off). 11.4 System had same results as 11.3. Using Nvidia 256-53 driver on 11.3 and 260.19.04 beta now on 11.4. Problems on both were seen with no Nvidia or Nouveau drivers installed. were usin nv driver. Is it possible something in the code is looking at something wrong in the BIOS? Anything else we can test? I will check Intel again for BIOS updates but updating maybe a last resort. Thanks again and my time should be OK this next week for testing. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.