[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#343928: marked as done (linux-image-2.6.14-2-k7: Nforce2 motherboard no longer wakes up with nvram-wakeup)

Your message dated Mon, 13 Feb 2006 11:27:40 +0100
with message-id <20060213102740.GB14875@nancy>
and subject line Bug#343928: Wake-up problem is gone
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: linux-image-2.6.14-2-k7
Version: 2.6.14-5
Severity: normal

Hello

Since I've updated my kernel from 2.6.11 to 2.6.14, my computer no
longer wakes up.

My motherboard is an Asus A7N8X deluxe with nforce2 chipset

All values reported by nvram-wakeup are normal. They fit with what's
reported by the BIOS:

$ sudo nvram-wakeup 

All values are displayed as they are stored in the nvram/rtc.
(and do not correspond necessarily to the system date/time)

WakeUp  : Enabled (0x9C)
Hour    : 07 (0x07)
Minute  : 40 (0x28)
Second  : 00 (0x40)
Checksum: 0x128F

With kernel 2-6-11 and the same version of nvram-wakeup, my
motherboard wakes up normally (i.e. every day at the same hour).

When I switch to 2.6.14, my motherboard will stop waking up after 2 or
3 halt/wakeup cycles. 

Even changing the wake up time with the BIOS will not make my
motherboard wake up.

Thanks for any help.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-2-k7
Locale: LANG=en_IE@euro, LC_CTYPE=en_IE@euro (charmap=ISO-8859-15)

Versions of packages linux-image-2.6.14-2-k7 depends on:
ii  module-init-tools             3.2.2-1    tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-1   Yet Another mkInitRD

Versions of packages linux-image-2.6.14-2-k7 recommends:
ii  libc6-i686                    2.3.5-8.1  GNU C Library: Shared libraries [i

-- debconf information:
  linux-image-2.6.14-2-k7/preinst/elilo-initrd-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/postinst/old-system-map-link-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/postinst/depmod-error-initrd-2.6.14-2-k7: false
  linux-image-2.6.14-2-k7/postinst/depmod-error-2.6.14-2-k7: false
  linux-image-2.6.14-2-k7/postinst/old-dir-initrd-link-2.6.14-2-k7: true
* linux-image-2.6.14-2-k7/preinst/already-running-this-2.6.14-2-k7:
* linux-image-2.6.14-2-k7/postinst/bootloader-test-error-2.6.14-2-k7:
  linux-image-2.6.14-2-k7/prerm/would-invalidate-boot-loader-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/postinst/create-kimage-link-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/preinst/lilo-initrd-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/preinst/abort-overwrite-2.6.14-2-k7:
  linux-image-2.6.14-2-k7/postinst/bootloader-error-2.6.14-2-k7:
  linux-image-2.6.14-2-k7/preinst/overwriting-modules-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/prerm/removing-running-kernel-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/preinst/initrd-2.6.14-2-k7:
  linux-image-2.6.14-2-k7/preinst/lilo-has-ramdisk:
  linux-image-2.6.14-2-k7/preinst/failed-to-move-modules-2.6.14-2-k7:
  linux-image-2.6.14-2-k7/postinst/old-initrd-link-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/preinst/abort-install-2.6.14-2-k7:
  linux-image-2.6.14-2-k7/preinst/bootloader-initrd-2.6.14-2-k7: true
  linux-image-2.6.14-2-k7/postinst/kimage-is-a-directory:

--- End Message ---
--- Begin Message --- 
On Sat, 11 Feb 2006, Dominique Dumont wrote:

> 
> Hello
> 
> With recent version of kernel 2.5.15-1, the wake-up problem is gone:
> My computer wakes up normally. I don't really know what triggered the
> problem and what solved it.
> 
> I think you can close this bug.
> 
> Cheers

doing, thanks for your feedback.

-- 
maks

--- End Message ---
Reply to: