Jonathan Thornburg wrote on Sat, Dec 01, 2007 at 11:30:41PM +0000:
> I have a more favorable experience to report, albeit on a T41p:
Me too using a T41p, so let's compare. See also my other post.
> With 4.2 (both -release and now -stable), suspend works perfectly.
> [Under 4.1 suspend would hang the system unless I switched to the
> 'vesa' Xorg driver; this was workable, but meant I lost any hardware
> video acceleration.]
4.1 not tested, don't remember exact details about 4.2-release,
4.2-stable not tested.
> Some details:
> IBM/Lenovo ThinkPad T41p, model 2373-221
IBM Thinkpad T41p (Type 2373-GKG S/N 99-95BGD 04/12)
> I have *only) OpenBSD on the disk, with no DOS or IBM "recovery partition"
> (I wiped the latter to give more space for OpenBSD)
Me too (ooops... i did not even notice any IBM recovery partition
while installing OpenBSD... Seems i wanted to get rid of Windows XP asap :).
> Suspend works fine via either Fn-F4 or 'zzz', under console or under X.
> X autoconfigures (I do *not* have an /etc/X11/xorg.conf) to 1400x1050
[...]
Yes, that's the hardware panel size reported by the BIOS.
> X restores the screen display fine after a suspend/resume cycle.
Not so for me.
As i said in my previous posting, it does not even suspend for me.
(unless... see below.)
Apparently, the xorg.conf file changes nothing. Usually, i have
xorg.conf in use because some idi^H^H^H nice guy in our internal
IT department ordered german keyboards (grrr). But without xorg.conf,
all i said in my previous posting still applies.
BUT, when i log in to X and run
# apmd -d
in one xterm and
# zzz
in another, the ThinkPad suspends properly
and Fn-F4 resumes properly without any video mode breakage.
In /var/log/messages, i find:
apmd: battery status: unknown. external power status: connected. \
estimated battery life: 0%
apmd: system resumed from APM sleep
apmd: battery status: high. external power status: not connected. \
estimated battery life: 100%
apmd: system resumed from APM sleep
So zzz works fine both with AC and battery, Fn-F4 and close/open LCD
work fine for both suspend and resume from X - but only if apmd is
running -, and Fn-F4 and close/open LCD work fine for suspend and resume
from console mode no matter whether apmd is running or not. But neither
Fn-F4 nor close LCD suspend from X without apmd, instead they both
kill the video mode.
Now i suspect i should start feeling silly...
We are supposed to run apmd if we want to suspend from X, are we not?
Any rocks round here, to crawl under?
For completeless, let's compare dmesgs:
> dmesg follows:
> OpenBSD 4.2-stable (GENERIC) #1: Sat Nov 17 10:05:47 GMT 2007
> [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
OpenBSD 4.2-current (GENERIC) #65: Mon Oct 15 16:36:09 CEST 2007
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
> real mem = 535785472 (510MB)
> avail mem = 510443520 (486MB)
real mem = 1072656384 (1022MB)
avail mem = 1029431296 (981MB)
> bios0 at mainbus0: AT/286+ BIOS, date 04/07/04, BIOS32 rev. 0 @ 0xfd750,
> SMBIOS rev. 2.33 @ 0xe0010 (61 entries)
> bios0: vendor IBM version "1RETC2WW (3.03 )" date 04/07/2004
> bios0: IBM 2373221
bios0 at mainbus0: AT/286+ BIOS, date 10/13/05, BIOS32 rev. 0 @ 0xfd750, SMBIOS
rev. 2.33 @ 0xe0010 (61 entries)
bios0: vendor IBM version "1RETDNWW (3.19 )" date 10/13/2005
bios0: IBM 2373GKG
> bios0: ROM list: 0xc0000/0x10000 0xd0000/0x1000 0xd1000/0x1000
> 0xdc000/0x4000! 0xe0000/0x10000
bios0: ROM list: 0xc0000/0x10000 0xdc000/0x4000! 0xe0000/0x10000
> wd0: 16-sector PIO, LBA, 57231MB, 117210240 sectors
wd0: 16-sector PIO, LBA, 53522MB, 109614447 sectors
> cd0 at scsibus0 targ 0 lun 0: <TOSHIBA, DVD-ROM SD-R9012, 1121> SCSI0 5/cdrom
> removable
cd0 at scsibus0 targ 0 lun 0: <HL-DT-ST, RW/DVD GCC-4242N, 0201> SCSI0 5/cdrom
removable
spdmem0 at iic0 addr 0x50: 512MB DDR SDRAM non-parity PC2700CL2.5
spdmem1 at iic0 addr 0x51: 512MB DDR SDRAM non-parity PC2700CL2.5
spdmem2 at iic0 addr 0x55: unknown
> fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
don't have any
