On Mon, Sep 18, 2006 at 06:34:45PM -0800, Greg Madden wrote: > On Sun, 17 Sep 2006 19:16:34 +1000 > garrone <[EMAIL PROTECTED]> wrote: > > > On Sat, Sep 16, 2006 at 07:30:14PM -0400, Don Hayward wrote: > > > > > > > > > On Sat, 16 Sep 2006, Martin Jambor wrote: > > > > > > >On 9/16/06, garrone <[EMAIL PROTECTED]> wrote: > > > >>On Sat, Sep 16, 2006 at 11:57:44AM +0200, Martin Jambor wrote: > > > >>> Hi, > > > >>> > > > >>> On 9/16/06, garrone <[EMAIL PROTECTED]> wrote: > > > >>> >> >The command "shutdown -h" does not completely poweroff the > > > >>> >> >system for kernels 2.6.11, 2.6.12, and 2.6.16. However > > > >>> >> >2.6.8 does turn off as it should! > > > >>> >> > > > >>> >Thanks. I was momentarily excited that 2.6.8 worked but the > > > >>> >others didnt, suggesting that the problem was with the linux > > > >>> >kernel rather than the board. However the situation where some > > > >>> >kernel versions work and others don't now suggests to me that > > > >>> >the problem is more > > > >>likely > > > >>> >to be with the board than the kernel. The linux code seems to > > > >>> >follow the standard pretty closely. I tried 2.6.17 and that > > > >>> >does not work either. I am running bios 3.03. > > > >>> > > > >>> Maybe I am stating the obvious, but have you had a look at and > > > >>> compared the configurations of the kernels that do and don't > > > >>> work? > > > >>> > > > >>> I run vanilla kernels and whenever such problems arise (on both > > > >>> amd64 and i386) it is most certainly my configuration error, > > > >>> not a kernel version issue (there have been exceptions like > > > >>> burning through ATA etc. though). > > > >>> > > > >>> HTH > > > >>> > > > >>> Martin > > > >> > > > >>So what configuration options do you mean? When I debugged a > > > >>failing 2.6.12, my debug statements were definitely being executed > > > >>at the point where it was supposed to stop. > > > >>I did briefly look at the configuration, but didnt see anything. > > > >>These are standard debian pre-packaged images as well. > > > >>The ACPI config from zless /proc/config.gz | grep ACPI is > > > >> > > > >>CONFIG_X86_64_ACPI_NUMA=y > > > >># ACPI (Advanced Configuration and Power Interface) Support > > > >>CONFIG_ACPI=y > > > >>CONFIG_ACPI_SLEEP=y > > > >>CONFIG_ACPI_SLEEP_PROC_FS=y > > > >># CONFIG_ACPI_SLEEP_PROC_SLEEP is not set > > > >>CONFIG_ACPI_AC=m > > > >>CONFIG_ACPI_BATTERY=m > > > >>CONFIG_ACPI_BUTTON=m > > > >>CONFIG_ACPI_VIDEO=m > > > >>CONFIG_ACPI_HOTKEY=m > > > >>CONFIG_ACPI_FAN=m > > > >>CONFIG_ACPI_PROCESSOR=m > > > >>CONFIG_ACPI_HOTPLUG_CPU=y > > > >>CONFIG_ACPI_THERMAL=m > > > >>CONFIG_ACPI_NUMA=y > > > >>CONFIG_ACPI_ASUS=m > > > >>CONFIG_ACPI_IBM=m > > > >>CONFIG_ACPI_TOSHIBA=m > > > >>CONFIG_ACPI_BLACKLIST_YEAR=0 > > > >># CONFIG_ACPI_DEBUG is not set > > > >>CONFIG_ACPI_EC=y > > > >>CONFIG_ACPI_POWER=y > > > >>CONFIG_ACPI_SYSTEM=y > > > >>CONFIG_ACPI_CONTAINER=m > > > >>CONFIG_X86_POWERNOW_K8_ACPI=y > > > >>CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y > > > >>CONFIG_X86_ACPI_CPUFREQ=m > > > >># CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set > > > >>CONFIG_HOTPLUG_PCI_ACPI=m > > > >>CONFIG_HOTPLUG_PCI_ACPI_IBM=m > > > >>CONFIG_PNPACPI=y > > > >>CONFIG_SERIAL_8250_ACPI=y > > > >> > > > >>It all looks pretty set to me. > > > > > > > >Yeah, it really looks good. Any differences between the 2.6.8 > > > >config? > > > > > > > >I also recall encountering a motherboard that wouldn't shut down > > > >with ACPI and needed APM, didn't it go away? > > > > > > > > > > I also run stock kernels. Here is a diff from 2.6.15 to 2.6.16 for > > > ACPI configs. Do they look like the changes from 2.6.8? I don't > > > have a 2.6.8 to to look at. > > > > > > > > > > < # Linux kernel version: 2.6.15-1-amd64-k8-smp > > > < # Mon Mar 20 08:27:27 2006 > > > --- > > > ># Linux kernel version: 2.6.16 > > > ># Fri Aug 18 20:35:54 2006 > > > > > > > > > > >CONFIG_ACPI_SLEEP=y > > > >CONFIG_ACPI_SLEEP_PROC_FS=y > > > ># CONFIG_ACPI_SLEEP_PROC_SLEEP is not set > > > >CONFIG_ACPI_HOTPLUG_CPU=y > > > > > > They seem to be included in the 2.6.12 config listed above. > > > > > > Don > > > > > > > > > -- > > > Don.Hayward at pomobuli.net > > > > In reply to both Don and Martin. > > I had completely expurgitated the 2.6.8 from my system, > > but I downloaded it again, reinstalled it, rebooted in recovery mode, > > and saved the /proc/config.gz, > > then confirmed that it does indeed halt everything with shutdown -h. > > The ACPI options are set as follows: > > > > # ACPI (Advanced Configuration and Power Interface) Support > > CONFIG_ACPI=y > > CONFIG_ACPI_BOOT=y > > CONFIG_ACPI_INTERPRETER=y > > # CONFIG_ACPI_SLEEP is not set > > CONFIG_ACPI_AC=m > > CONFIG_ACPI_BATTERY=m > > CONFIG_ACPI_BUTTON=m > > CONFIG_ACPI_FAN=m > > CONFIG_ACPI_PROCESSOR=m > > CONFIG_ACPI_THERMAL=m > > CONFIG_ACPI_ASUS=m > > CONFIG_ACPI_TOSHIBA=m > > # CONFIG_ACPI_DEBUG is not set > > CONFIG_ACPI_BUS=y > > CONFIG_ACPI_EC=y > > CONFIG_ACPI_POWER=y > > CONFIG_ACPI_PCI=y > > CONFIG_ACPI_SYSTEM=y > > # CONFIG_SERIAL_8250_ACPI is not set > > > > The CONFIG_ACPI_SLEEP option is irrelevent, as we are not > > trying to send the system to sleep. > > > > ACPI is a standard. The kernel isn't supposed to vary from board to > > board. If the hardware doesnt poweroff when its told to, then its the > > fault of the hardware. It's up to the manufacturer > > to program their bios so their board shuts down properly. > > Perhaps we should try to find a tyan s2875 that actually works > > properly with multiple versions of linux. If there are none, > > then we know its the fault of the board design. > > > > Peter > > > > > > I don't have that board, but it happens with other boards. Try > running 'lsmod', the configs might be the same but the actual loaded > modules might be different. > > -- > Greg Madden > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > lsmod on a non-working system: Module Size Used by nvidia 5425720 12 ipv6 271904 18 thermal 17420 0 fan 7368 0 button 9824 0 processor 32584 1 thermal ac 7688 0 battery 12744 0 dm_snapshot 17336 0 dm_mirror 22312 0 dm_mod 57160 2 dm_snapshot,dm_mirror w83627hf 30032 0 hwmon_vid 4928 1 w83627hf i2c_isa 8064 1 w83627hf sr_mod 20068 0 sbp2 25284 0 ide_generic 3584 0 [permanent] raw1394 28384 0 dv1394 23416 0 eth1394 22920 0 bt878 14508 0 snd_ice1724 74496 0 snd_ice17xx_ak4xxx 6720 1 snd_ice1724 snd_ac97_codec 104636 1 snd_ice1724 snd_ac97_bus 4928 1 snd_ac97_codec snd_ak4114 12800 1 snd_ice1724 snd_pcm_oss 53856 0 snd_mixer_oss 19520 1 snd_pcm_oss snd_pcm 95176 4 snd_ice1724,snd_ac97_codec,snd_ak4114,snd_pcm_oss bttv 199484 1 bt878 video_buf 25540 1 bttv firmware_class 13568 1 bttv snd_timer 27208 1 snd_pcm snd_page_alloc 13328 1 snd_pcm compat_ioctl32 10880 1 bttv i2c_algo_bit 11464 1 bttv snd_ak4xxx_adda 9216 2 snd_ice1724,snd_ice17xx_ak4xxx v4l2_common 11776 2 bttv,compat_ioctl32 snd_mpu401_uart 10496 1 snd_ice1724 btcx_risc 7304 1 bttv ir_common 12676 1 bttv snd_rawmidi 29408 1 snd_mpu401_uart tveeprom 18832 1 bttv sata_sil 13704 0 psmouse 41612 0 i2c_amd756 9668 0 snd_seq_device 11792 1 snd_rawmidi shpchp 47712 0 i2c_amd8111 8320 0 videodev 13568 1 bttv serio_raw 10052 0 ide_cd 42784 0 cdrom 38456 2 sr_mod,ide_cd snd 62240 11 snd_ice1724,snd_ac97_codec,snd_ak4114,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_ak4xxx_adda,snd_mpu401_uart,snd_rawmidi,snd_seq_device ohci1394 35272 1 dv1394 pcspkr 6088 0 pci_hotplug 14084 1 shpchp libata 63512 1 sata_sil ieee1394 358008 5 sbp2,raw1394,dv1394,eth1394,ohci1394 i2c_core 25408 8 nvidia,w83627hf,i2c_isa,bttv,i2c_algo_bit,tveeprom,i2c_amd756,i2c_amd8111 hw_random 8296 0 e1000 109108 0 scsi_mod 148792 3 sr_mod,sbp2,libata ehci_hcd 33480 0 uhci_hcd 34208 0 ohci_hcd 22596 0 soundcore 13152 1 snd floppy 69256 0 ext3 132816 5 jbd 60904 1 ext3 mbcache 11848 1 ext3 ide_disk 18368 7 amd74xx 17264 0 [permanent] generic 7620 0 [permanent] ide_core 144568 5 ide_generic,ide_cd,ide_disk,amd74xx,generic evdev 12928 1
Cheers, Peter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
