Bug#432468: does not resume from suspend-to-RAM on toshiba satellite m70
On Thu, May 8, 2008 at 5:57 PM, maximilian attems <max@stro.at> wrote:
> any update on ath5k with 2.6.25?
The chip in this laptop is:
# ath_info c0200000
-==Device Information==-
MAC Version: 5213A (0x70)
MAC Revision: 5213A (0x78)
PHY Revision: 2112a (0x56)
-==EEPROM Information==-
EEPROM Version: 5.2
EEPROM Size: 16K
Regulatory Domain: 0x64
-==== Capabilities ====-
| 802.11a Support: no |
| 802.11b Support: yes |
| 802.11g Support: yes |
| RFKill Support: yes |
| 32KHz Crystal: no |
========================
GPIO registers: CR 00018000 DO 00000000 DI 00000017
which is not on the supported list at
http://madwifi.org/wiki/About/OpenHAL (there is something very similar
on the list, but you know how it is with wireless chips - that "A" at
the end could mean totally different internals). I tried it anyway,
with
linux-image-2.6.25-1-686 v. 2.6.25-1. The chip is recognized and an
interface created but it won't 'ifconfig up' or scan for APs.
May 8 20:20:29 boheme kernel: [ 10.102600] ath5k_pci 0000:04:02.0:
registered as 'phy0'
May 8 20:20:29 boheme kernel: [ 10.535239] ath5k phy0: Atheros
AR5213A chip found (MAC: 0x78, PHY: 0x45)
May 8 20:20:29 boheme kernel: [ 10.535301] ath5k phy0: RF2112A 2GHz
radio found (0x56)
May 8 20:20:29 boheme kernel: [ 11.115910] udev: renamed network
interface wlan0 to ath0
May 8 20:20:35 boheme kernel: [ 22.744264] ADDRCONF(NETDEV_UP):
ath0: link is not ready
In any case the Atheros drivers are irrelevant to the suspend problem,
because (as I said in the original bug report) the failure mode is
exactly the same if I do "echo mem > /sys/power/state" from an
init=/bin/sh boot. In fact, I get the same failure if I do that from
inside the initramfs, before any modules are loaded at all
(break=top). Again, 2.6.25-1.
Any chance of getting CONFIG_PM_TRACE turned on in Debian's kernel builds?
zw
Reply to: